Develop Bugs

Rebooting to fastboot on CM10.1?

Having a small issue with my device, and I could do with getting in to fastboot to troubleshoot.
I have TWRP installed along with a nightly version of CM10.1, When I try ADB reboot bootloader The device reboots, flashes the first bootscreen for a second(Orange and White Kindle Fire) and then shuts itself down.
Any suggestions that don't involve getting a fastboot cable? I can make one if I have too, but I would rather try and find out why it wont work this way.

Nvmd

So, you don't see the blue Kindle Fire logo at all?

I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.

Jackering said:
I see the Orange and white, then the Blue and White, and then it boots, When I try and reboot to bootloader, I see the Orange and White, and then it shuts down.
Click to expand...
Click to collapse
Why don't you use the volume button to access recovery?
Hashcode said:
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and keep pressing until the logo turns BLUE. Wait a moment and you should enter recovery.
Click to expand...
Click to collapse

I can enter recovery fine, I want to get in to Fastboot to test something.

Jackering said:
I can enter recovery fine, I want to get in to Fastboot to test something.
Click to expand...
Click to collapse
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?

soupmagnet said:
If your device boots into recovery, you can issue the "reboot bootloader" command from there
If you are able to get into fastboot from there, you know it's the nightly version of CM10.1 that is the problem and not the bootloader. If that's the case, install a different ROM.
[Edit:] For curiosity's sake, what "troubleshooting" are you expecting to do in fastboot?
Click to expand...
Click to collapse
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.

Jackering said:
From ADB on the device?
Edit; I get a message "Error: Command not found" or something like that trying to run it on the device.
I just wish to test a reboot to fastboot mode, thats all :good:
Edit2:
Just noticed that when in recovery, Windows Device Manager has an ! next to "Amazon KindleFire2" Yet, There is no ! once booted, Interesting.
Click to expand...
Click to collapse
Oh nevermind, I was wrong. Typically you would use 'idme' to change the bootmode then reboot, but 'idme' isn't included in our version of TWRP. I thought maybe it could be pushed to recovery then executed, but I keep getting a "Segmentation fault" error on this version when trying it on my end. I'm not sure what's causing that other than perhaps this version wasn't made with 'idme' in mind, but that's purely speculation on my part. If you had any other device than a Kindle Fire 2 you wouldn't have any problem accessing fastboot, but as it stands now, I think your only option (to get into fastboot) is to acquire a factory cable or install a different ROM.
But even with fastboot, that's still not addressing your original problem. The fastboot binary is really only useful for overwrite\ing partitions and changing the bootmode. Whatever your problem is, it will likely be fixed by installing a non-nightly version of CM10.1 (nightly = not so stable).
As for your device manager, later versions of TWRP have different hardware IDs than that of the stock OS. Just add the hardware ID to your 'android_winusb.inf' and reinstall it.

soupmagnet said:
Why don't you use the volume button to access recovery?
Click to expand...
Click to collapse
Btw- we don't have volume buttons. Drives me nuts
Sent from my SGH-I727 using Tapatalk 2

Broken android when trying to enter recovery

Hi!
Today I unlocked bootloader and installed a custom rom and everything went fine.
Now, when I tried to flash the camera mod app, I couldn't enter TWRP. When trying to do it with the restart option it shows a broken android and I have to remove battery to get the phone running again. Manual (holidng down vol button + power button, as well as holding down buttons and releasing them for 1s) is also not working.
The phone works fine, but I would like to have TWRP working.
Can I just reinstall twrp like the first time?
Thank you

Jojo5678 said:
Hi!
Today I unlocked bootloader and installed a custom rom and everything went fine.
Now, when I tried to flash the camera mod app, I couldn't enter TWRP. When trying to do it with the restart option it shows a broken android and I have to remove battery to get the phone running again. Manual (holidng down vol button + power button, as well as holding down buttons and releasing them for 1s) is also not working.
The phone works fine, but I would like to have TWRP working.
Can I just reinstall twrp like the first time?
Thank you
Click to expand...
Click to collapse
What device? H811? Needs to know more about what software you flashed.
If you can get into fastboot you can push twrp there.

Hmmm i flashed xperia phones locked bootloader twrp on my h818 and i got this error too so it means it changed the recovery but can't start it?
Sent from my LG-H818

Vseprz said:
What device? H811? Needs to know more about what software you flashed.
If you can get into fastboot you can push twrp there.
Click to expand...
Click to collapse
H815 EUR. I installed the 2.8.7.0 and the 2.8.6.1 from https://dl.twrp.me/h815/. I tried it multiple times with these 2 versions and everytime I get the same error.
Connecting it to pc and entering recovery works without a problem, though.
Edit: I flashed Genisys 3.7

Jojo5678 said:
H815 EUR. I installed the 2.8.7.0 and the 2.8.6.1 from https://dl.twrp.me/h815/. I tried it multiple times with these 2 versions and everytime I get the same error.
Connecting it to pc and entering recovery works without a problem, though.
Edit: I flashed Genisys 3.7
Click to expand...
Click to collapse
So you can get into twrp with "adb reboot recovery"?
Your problem is you can not access it from neither the rebooter app nor the hardware buttons?
When using the harware buttons, hold vol down then press and hold power until the logo shows up. Release power for a second then press and hold again.

Vseprz said:
So you can get into twrp with "adb reboot recovery"?
Your problem is you can not access it from neither the rebooter app nor the hardware buttons?
When using the harware buttons, hold vol down then press and hold power until the logo shows up. Release power for a second then press and hold again.
Click to expand...
Click to collapse
Correct, I can get in twrp with "adb reboot recovery"
I was releasing both the volume and power buttons. Tried it again, but I came to a menu where I could only choose whether to delete all data (factory reset) or not. When choosing NO, the phone proceeded to boot normally.

Jojo5678 said:
Correct, I can get in twrp with "adb reboot recovery"
I was releasing both the volume and power buttons. Tried it again, but I came to a menu where I could only choose whether to delete all data (factory reset) or not. When choosing NO, the phone proceeded to boot normally.
Click to expand...
Click to collapse
That menu is perfectly normal. You have to select okay. Because you have a custom recovery it will not factory reset your phone but rather boot you into twrp.

Vseprz said:
That menu is perfectly normal. You have to select okay. Because you have a custom recovery it will not factory reset your phone but rather boot you into twrp.
Click to expand...
Click to collapse
Oh wow thank you very much. Everything works now

[Solved] Unlocked Bootloader now having trouble

I unlocked the bootloader and installed TWRP Recovery using the OP3 Tool. However now the phone will not boot unless I press the power button a few times. When it does boot I get the "Your device is not safe message", if I boot from here I get the OnePlus logo with the "powered by android" text but then it just shuts off. If I use the volume keys to select something else, I get nothing, the fastboot mode just gets stuck on the fastboot until I turn the device off, recovery just reboots to the "Your device is not safe screen".
Any help would be wonderful

McreativeH said:
I unlocked the bootloader and installed TWRP Recovery using the OP3 Tool. However now the phone will not boot unless I press the power button a few times. When it does boot I get the "Your device is not safe message", if I boot from here I get the OnePlus logo with the "powered by android" text but then it just shuts off. If I use the volume keys to select something else, I get nothing, the fastboot mode just gets stuck on the fastboot until I turn the device off, recovery just reboots to the "Your device is not safe screen".
Any help would be wonderful
Click to expand...
Click to collapse
Did you flash anything while you were unlocking the bootloader? The message is shown when the bootloader is unlocked so that is ok. Your phone, however, should turn on by long pressing the power button. You're getting a bootloop, If I were in such a situation I'd use the fastboot mode to flash the stock firmware again to get the phone working...

mharis05 said:
Did you flash anything while you were unlocking the bootloader? The message is shown when the bootloader is unlocked so that is ok. Your phone, however, should turn on by long pressing the power button. You're getting a bootloop, If I were in such a situation I'd use the fastboot mode to flash the stock firmware again to get the phone working...
Click to expand...
Click to collapse
I managed to get it working in the end by reflashing the stock recovery image ???? thank you for the help

McreativeH said:
I managed to get it working in the end by reflashing the stock recovery image ???? thank you for the help
Click to expand...
Click to collapse
Awesome! Enjoy :good:

Oneplus 5t dead after update.

Hey
I installed the recent upgrade to my OP 5T and now the phone is not getting switched on, only the 1+ logo appears on pressing the power button and soon after it gets switched off.
I have tried the 'Volume Up + Power' button combination and fastloader screen appears, i tried to enter recovery mode but it just gets switched off after the 1+ logo when i select recovery mode.
OP5T_Unbrick_tool_dumpling ... not working:
The battery is getting charged normally and this is an android upgrade issue. I am a newbie, any help would be appreciated.
Thanks

A possibility could be that you tried to do stock update local method through twrp or custom recovery... That's similar to what happened on mine when I did that on the first beta 10 update. If so I flashed latest stock recovery through the fastboot menu by plugging into computer and using ADB fastboot command "fastboot flash recovery" minus brackets and dragged the recovery over and pressed enter.
It appears to do it as the update launched some sort of boot script but can't be carried out without stock recovery leading to a sort of boot loop.
Also I found while trying to fix this if I updated from a ROM where it didn't have treble support or wiped the vendor (I did when panicking lol). I had to firstly install the stock ROM that introduced treble then install the beta 10 update.
Sorry if that was all pointless or irellivent but hope you get ur problem fixed soon.

Question OnePlus 9 Pro and TWRP issues

Apparently power + vol up + vol down pushed me right into fastboot, I was trying just vol-up or vol-down with power.
{Mod edit}
I just flashed TWRP after unlocking my phone like I have with every other OnePlus I've owned but after the "Flash Current TWRP option" and rebooting I'm stuck at an unresponsive pin screen. Nothing I do seems to receive input and locking/unlocking for a swipe to unlock is unresponsive as well. I tried rebooting to fastboot so I can reflash but it immediately jumps into TWRP.
Has anyone has this issue with the 9 Pro? This is my 3rd OP phone to do this process and the first I've had this issue with. Thanks!

pmarco99 said:
Apparently power + vol up + vol down pushed me right into fastboot, I was trying just vol-up or vol-down with power.
I just flashed TWRP after unlocking my phone like I have with every other OnePlus I've owned but after the "Flash Current TWRP option" and rebooting I'm stuck at an unresponsive pin screen. Nothing I do seems to receive input and locking/unlocking for a swipe to unlock is unresponsive as well. I tried rebooting to fastboot so I can reflash but it immediately jumps into TWRP.
Has anyone has this issue with the 9 Pro? This is my 3rd OP phone to do this process and the first I've had this issue with. Thanks!
Click to expand...
Click to collapse
You must be on Android 12 if it's doing that. TWRP isn't ready for a12 yet. You can only boot it not flash it on a12

pmarco99 said:
Apparently power + vol up + vol down pushed me right into fastboot, I was trying just vol-up or vol-down with power.
I just flashed TWRP after unlocking my phone like I have with every other OnePlus I've owned but after the "Flash Current TWRP option" and rebooting I'm stuck at an unresponsive pin screen. Nothing I do seems to receive input and locking/unlocking for a swipe to unlock is unresponsive as well. I tried rebooting to fastboot so I can reflash but it immediately jumps into TWRP.
Has anyone has this issue with the 9 Pro? This is my 3rd OP phone to do this process and the first I've had this issue with. Thanks!
Click to expand...
Click to collapse
Personally, I can only boot but not flash, even on OOS11.
When I boot on it, the touchscreen works while if I flash and boot on it, the touchscreen does not work.

Yeah there is no reason nowadays to flash TWRP on OnePlus phones. I haven't in the last two.

Also, haven't flashed twrp in a while; I only boot it!

schmeggy929 said:
Yeah there is no reason nowadays to flash TWRP on OnePlus phones. I haven't in the last two.
Click to expand...
Click to collapse
I need to flash an update. I figured I needed TWRP. Can I just flash it through adb or will it brick?

SeeTurtle said:
I need to flash an update. I figured I needed TWRP. Can I just flash it through adb or will it brick?
Click to expand...
Click to collapse
What update