[One Plus family] Stuck after unlock Bootloader waiting for device

[freechelmi]

assisting people in Unlocking bootloaders is hard :-)
Every manufacturer has a different GUI and instructions
Let's focus on oneplus on this issue

OAI guides well to the screen where the user have to choose to unlock with the volume and power button

Then the next step is " fastboot reboot" -> Not needed , one plus reboot itself and wipe until rebooting stock rom

Then OAI is stuck here , it wait to isse fastboot reboot command

Next step tells the user to reenable adb

we tell the user to shut down the phone , and manually reboot to fastboot ?

[freechelmi]

But If you go manually to fastboot , OAI will finally issue the "fastboot reboot " command and you go again to stock ROM :-)

[MagicLike]

Hmmm ok, there are (probably) multiple issues here...
First of all please tell me what OnePlus Model you have.

[tsterbak]

Hey @freechelmi, thank you for rising the issue!
Indeed, it should not reboot with fastboot after unlocking. This will be fixed in the next release. Would you be interested in testing the new version?

[MagicLike]

This will be fixed in the next release.

If it is ok, I will open a PR soon! (I would take the stuff out of my bacon config)

[MagicLike]

This will be fixed in the next release.

If it is ok, I will open a PR soon! (I would take the stuff out of my bacon config)

@tsterbak I just realised, that my PR #111 needs to be merged first before addressing this issue, as it makes changes to all existing configs...

[MagicLike]

@tsterbak If it is fine, I will make the changes to all OnePlus configs now and open a PR soon...

[tsterbak]

@tsterbak If it is fine, I will make the changes to all OnePlus configs now and open a PR soon...

Great! Create a branch from the release branch if possible (#119).

[MagicLike]

Great! Create a branch from the release branch if possible (#119).

Already done! ^^ #120

[MagicLike]

fixed in b12f239

[MagicLike]

This can now be closed - it will be implemented in the next release.

[tsterbak]

This can now be closed - it will be implemented in the next release.

No hurry to close issues. For an issue like this where a lot of things can go wrong, I prefer to get the feedback from the reporting person :)

[MagicLike]

This can now be closed - it will be implemented in the next release.

No hurry to close issues. For an issue like this where a lot of things can go wrong, I prefer to get the feedback from the reporting person :)

Alright ^^

[tsterbak]

Hey @freechelmi, the latest release should have fixed this issue. If you want, you can give it a try 🙂

[MagicLike]

@freechelmi Was the issue fixed with that update?

[tsterbak]

Any news on this?

[freechelmi]

Sorry for my lack of answers , tested again with 0.5.1 and we jump correctly to , so fixed

[tsterbak]

Sorry for my lack of answers , tested again with 0.5.1 and we jump correctly to , so fixed

Thanks a lot for testing again! Great that it works now! :)