Droid Turbo stuck on "WARNING BOOTLOADER UNLOCKED" screen - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

I installed CM 13 on my Droid Turbo after unlocking the bootloader with Sunshine. Everything was going fine until I tried to flash the Open Google Apps zip and I got into a loop with some of the Gapps crashing and I couldn't do anything. I researched this online and they (can't find where now) said to use TWRP to reset the device. So I went into "wipe" on TWRP and under "advanced wipe" I chose "System", "dalvik / art" and "cache" and rebooted the system. Now I've been stuck on the "WARNING BOOTLOADER UNLOCKED" screen for over an hour.
The other thing I have going against me is the power button does not work in anyway whatsoever (before and after I unlocked the bootloader).
Does anyone have any ideas?

You wiped the system partition, which means you erased your phone's operating system. This is why your phone is having trouble booting said operating system. Re-flash CM13 followed by your gapps (flash them sequentially. Don't boot the phone until both are flashed) and you should be fine.

I just went through this. Here's what worked for me, I'm on mobile and your milage may vary, you'll probably want to double check my work.
Get
Minimal adb and fast boot
Motorola turbo USB drivers
Twrp, cm13 20160517 if using nightly, gapps Pico, and in my case SuperSU
Hold power till off
Power up while holding power down
Google for the proper commands to accomplish the following
Fast boot twrp in place for recovery
Edit, boot into twrp.
Adb push cm13 zip
Adb push gapps Pico zip
Adb push SuperSU zip if needed
Edit,reboot back into recovery
Flash cm13, gapps Pico, SuperSU in that order
Reboot, wait for cm13 to load as long as it takes.
Edit, boot into twrp before adb push.

orangestrontium said:
I installed CM 13 on my Droid Turbo after unlocking the bootloader with Sunshine. Everything was going fine until I tried to flash the Open Google Apps zip and I got into a loop with some of the Gapps crashing and I couldn't do anything. I researched this online and they (can't find where now) said to use TWRP to reset the device. So I went into "wipe" on TWRP and under "advanced wipe" I chose "System", "dalvik / art" and "cache" and rebooted the system. Now I've been stuck on the "WARNING BOOTLOADER UNLOCKED" screen for over an hour.
The other thing I have going against me is the power button does not work in anyway whatsoever (before and after I unlocked the bootloader).
Does anyone have any ideas?
Click to expand...
Click to collapse
Since you have no power button this becomes tricky. You can try using adb but don't know if it will work as your phone sits. The only thing I can think of is let your phone die completely once it is off totally plug it in to charge while holding the down vol. Button this will bring you to bootloader where you can use adb commands to start recovery and go into twrp where you can reflash the system and gapps

Grynch13 said:
Since you have no power button this becomes tricky. You can try using adb but don't know if it will work as your phone sits. The only thing I can think of is let your phone die completely once it is off totally plug it in to charge while holding the down vol. Button this will bring you to bootloader where you can use adb commands to start recovery and go into twrp where you can reflash the system and gapps
Click to expand...
Click to collapse
This worked seamlessly, thanks!

I was in the same situation, and your advice got me to drain the battery and get back into recovery mode, so thanks for that! But, when I connected the USB cable, and tried ADB commands, it doesn't recognize my device (it has always recognized it in the past). Any advice? Thanks so much!

Related

[Q] Can't boot into recovery or erase recovery (TRIED ERASING CACHE)

Hi I am trying to work through the process of rooting my HTC One.
I have some experience with android as I've rooted three different phones now, the One is the only one giving me trouble :/
So I got the bootloader unlocked via the HTC Dev method, and now I'm trying to get recovery to work. I've flashed CWM, CWMT, and TWRP, and no matter which I try I can't boot into recovery via "adb reboot recovery" or via the HBOOT menu. When I try the phone just goes through a regular reboot. I can't use ROM Manager to do it either naturally since I don't have root yet (need recovery to install SuperSU).
However ROM Manager does show I have CWM and TWRP installed (both? weird) so I tried to start over by doing "fastboot erase recovery" but it says
FAILED: (remote: not allowed)
I tried "fastboot erase cache" before and after flashing a recovery and nothing at all changes.
Any ideas? Could I have missed something really simple and stupid? I'm pulling all my hair out trying to figure this out.
I heard some people got it to work by flashing the recovery to the boot partition, but until I get assurance that isn't a terrible horrible idea (like it seems) I don't want to try that.
EDIT: yes, the "fast boot" option in the power menu is already disabled.
I had the same issue. Solved it by disabling the fast boot option within the OS. Under power options.
Worth a shot.
Sent from my HTC One using xda app-developers app
ar3na said:
I had the same issue. Solved it by disabling the fast boot option within the OS. Under power options.
Worth a shot.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply but that option is already disabled
I was facing the same problem, however, what I did was turn on fast boot under settings right after I flashed the recovery.
Then, I rebooted back into the bootloader and I now had ***TAMPERED*** at the top of my screen. I afterwards selected reboot into recovery and bam, I now had TWRP on my phone.
WeegeeNumbuh1 said:
I was facing the same problem, however, what I did was turn on fast boot under settings right after I flashed the recovery.
Then, I rebooted back into the bootloader and I now had ***TAMPERED*** at the top of my screen. I afterwards selected reboot into recovery and bam, I now had TWRP on my phone.
Click to expand...
Click to collapse
Just tried that, didn't work
Also why would you have TAMPERED at the top? Did you change anything else to get that like flash a different HBOOT or fastboot or something?
I'm about to throw this thing out the window -___-
SOLVED
Hallelujah, I got it!
I did nothing differently, but eventually it worked...very weird, but at least I got it! The final iteration to get it working was this:
1. Turn off fast boot option in power menu
2. Boot into bootloader via power menu, then power + vol down
3. go into fastboot
4. from a cmd window, fastboot flash recovery recovery.img
5. fastboot erase cache
6. from the menu, boot into recovery
7. phone boots to the OS instead of recovery
8. boot back into the bootloader via power menu, power + vol down
9. TAMPERED shows up, boot into recovery and it works!
note that i never used adb reboot recovery or adb reboot bootloader, idk if that matters, but I did everything from the phone.
thanks for all your help!
For what it's worth, I use ROM Toolbox's Reboot to recovery option and it works. Though I can see where you'd need to boot to recovery from startup.
TheShadowZero said:
Hallelujah, I got it!
I did nothing differently, but eventually it worked...very weird, but at least I got it! The final iteration to get it working was this:
1. Turn off fast boot option in power menu
2. Boot into bootloader via power menu, then power + vol down
3. go into fastboot
4. from a cmd window, fastboot flash recovery recovery.img
5. fastboot erase cache
6. from the menu, boot into recovery
7. phone boots to the OS instead of recovery
8. boot back into the bootloader via power menu, power + vol down
9. TAMPERED shows up, boot into recovery and it works!
note that i never used adb reboot recovery or adb reboot bootloader, idk if that matters, but I did everything from the phone.
thanks for all your help!
Click to expand...
Click to collapse
this worked very well for me, thanks
TheShadowZero said:
Hallelujah, I got it!
I did nothing differently, but eventually it worked...very weird, but at least I got it! The final iteration to get it working was this:
1. Turn off fast boot option in power menu
2. Boot into bootloader via power menu, then power + vol down
3. go into fastboot
4. from a cmd window, fastboot flash recovery recovery.img
5. fastboot erase cache
6. from the menu, boot into recovery
7. phone boots to the OS instead of recovery
8. boot back into the bootloader via power menu, power + vol down
9. TAMPERED shows up, boot into recovery and it works!
note that i never used adb reboot recovery or adb reboot bootloader, idk if that matters, but I did everything from the phone.
thanks for all your help!
Click to expand...
Click to collapse
Thank you very much dear sir/ma'am.
This worked like a charm where nothing else had worked before!

[q] lg l90 d415

After downloading CM11 and GApps, I put it in my SD card and went into my recovery cwm9 by using an app. I got in and tried to flash my zips but I couldn't find them. Before I actually tried to flash them I did this first:
Wipe cache ( only required on first installation )
Wipe Dalcik cache ( only required on first installation )
Format /system and optionally /data ( Only necessary if coming from stock or a different ROM )
So when I rebooted I was greeted by getting stuck at the T-mobile boot splash.
I don't know how to get into recovery manually. I can't try to use download mode because I used fastboot. When I get into fastboot I tried using ADB to boot into recovery but device is not found when I'm in fastboot.
Please help me, I literally just got this phone and wanted to flash a custom rom because the LG stock is disgusting.
nemesis101x said:
After downloading CM11 and GApps, I put it in my SD card and went into my recovery cwm9 by using an app. I got in and tried to flash my zips but I couldn't find them. Before I actually tried to flash them I did this first:
Wipe cache ( only required on first installation )
Wipe Dalcik cache ( only required on first installation )
Format /system and optionally /data ( Only necessary if coming from stock or a different ROM )
So when I rebooted I was greeted by getting stuck at the T-mobile boot splash.
I don't know how to get into recovery manually. I can't try to use download mode because I used fastboot. When I get into fastboot I tried using ADB to boot into recovery but device is not found when I'm in fastboot.
Please help me, I literally just got this phone and wanted to flash a custom rom because the LG stock is disgusting.
Click to expand...
Click to collapse
See FAQ thread for getting into recovery.
[SIZE=+1]Q14: I've flashed a custom recovery but what are the key combos to get there?[/SIZE]
Power off the device
Press and hold Power + Volume down
When the LG logo appears on the screen, quickly release the Power button, still holding the Volume down button, and press and hold Power again until the "Factory Reset" screen appears. Don't worry, this won't reset the device.
Use the volume keys to navigate up and down and Power to select. Scroll down and select "Yes" and repeat once more. It may take up to 10 seconds for the device to boot to recovery.
I've now gotten into the recovery and installed both cyanogenmod and GApps. I've actually had to change the rom found here:
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-11-lg-l90-lg-d415-t2871371
I've had to change the updater script that contained "w7" to "w7ds" because it said my device wasn't w7 and that it was w7ds.
I've rebooted and now it's just stuck on the cyanogenmod boot screen.
What do?
nemesis101x said:
I've now gotten into the recovery and installed both cyanogenmod and GApps. I've actually had to change the rom found here:
http://forum.xda-developers.com/lg-l90/development/rom-cyanogenmod-11-lg-l90-lg-d415-t2871371
I've had to change the updater script that contained "w7" to "w7ds" because it said my device wasn't w7 and that it was w7ds.
I've rebooted and now it's just stuck on the cyanogenmod boot screen.
What do?
Click to expand...
Click to collapse
You've got an older recovery it seems. Download Philz-Touch from my thread, the link you posted, or get TWRP from this thread
Since you're having booting issues, use fastboot to flash the recovery.
Thing is when I'm in fastboot, ADB won't detect my device. I've only gotten it to detect my device once and that's when I was unlocking my bootloader. I don't know how to do it again.
So what do I do? BTW, thanks for helping me.
Edit: I formatted everything again and tried to reinstall the cyanogenmod and GApps. Seems like I just had to wait for the boot screen.
nemesis101x said:
Thing is when I'm in fastboot, ADB won't detect my device. I've only gotten it to detect my device once and that's when I was unlocking my bootloader. I don't know how to do it again.
So what do I do? BTW, thanks for helping me.
Click to expand...
Click to collapse
Put device in fastboot mode. ADB can't detect the device when it's in fastboot mode.
Type:
Code:
fastboot devices
You should see a listing similar to "adb devices" output.
Copy recovery image to the same folder fastboot is in. Then type:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot boot recovery.img
First one will only write the recovery image to the device. The second on will write the image to the device and should then boot the device to the recovery.
EDIT:
Yes, the first boot takes a couple minutes.
Seems I just had to wait for bootscreen.
How do I turn data on and off?
nemesis101x said:
Seems I just had to wait for bootscreen.
How do I turn data on and off?
Click to expand...
Click to collapse
easiest way to explain. Go to Settings and toggle Mobile Networks off/on.
There are several ways. I'm guessing you're new to CyanogenMod ROMs?
shinobisoft said:
easiest way to explain. Go to Settings and toggle Mobile Networks off/on.
Click to expand...
Click to collapse
Well, yeah, but a faster way. Like in LG in the notification bar there was a button that would turn data on and off. Does cyanogenmod have anything like that similarly?
nemesis101x said:
Well, yeah, but a faster way. Like in LG in the notification bar there was a button that would turn data on and off. Does cyanogenmod have anything like that similarly?
Click to expand...
Click to collapse
Quick Tiles. Pull down statusbar and press upper right corner image. There should be a tile already there for data
Sent from my LG-D415 using Tapatalk
shinobisoft said:
Quick Tiles. Pull down statusbar and press upper right corner image. There should be a tile already there for data
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Yeah, I got it.
Thank you for all your help!

[Q] Bricked after TWRP backup?

Following a YouTube video, code 4dwguHoxTvo, I think I might have bricked my tablet.
I ran the script provided at rootjunkysdl, got USB drivers working, and booted into TWRP recovery. I made a backup, but the guy in the video doesn't mention that you need pico gapps until he's already doing it. So I rebooted to copy over pico and now I'm in a reboot loop. "=> Normal boot" with the Amazon logo.
On bootup it shows up in device manager under Other as "MT65xx Preloader", then disappears when it reboots again.
If I hold power and both volume buttons I get "=> Fastboot mode..." but I don't know if I can do anything w/ that.
How did this happen if I didn't flash anything, just backed up?

Recovery Refuses to Stick

Hoping I can get some help with the same issue.
I sent my 6P back in for a warranty repaid so I'm using this phone (XT1095) for now. I'd like to put LineageOS on it and root with Magisk BUT I'm having a ridiculous time getting TWRP to flash.
I certainly know how to flash images via fastboot and have done it for years but this is seriously pissing me off lol.
I got the code from Moto and unlocked the bootloader. I tried a simple "fastboot flash recovery _____.img", I've tried "fastboot boot _____.img".
At first, I was booting back into the system first but now I've tried it both ways. Regardless of what I do, after flashing the recovery, it boots into the system. The ONLY I can get this thing into recovery is if I boot into the system and just use "adb reboot recovery" but it's obviously the stock recovery because the phone keeps overwriting TWRP upon boot.
Just so we're clear:
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Volume button to boot into recovery
Result = Boots into system
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Fastboot reboot bootloader
5. Bootloader reboots
6. Volume button to boot into recovery
Result = Boots into system
1. Fastboot boot _____.img
Result = Boots into system
If it helps at all, upon flashing recovery I get this message 100% of the time "mismatched partition size", similar to the case on this thread: https://goo.gl/6Nm9cu
By dumb luck I found where someone used the "fastboot boot ____.img" with a pretty old version and it worked just fine. I'll root and such with that and upgrade the recovery later.
jonzey231 said:
Just so we're clear:
1. Reboot into bootloader
2. Confirm bootloader unlocked
3. Fastboot flash recovery _____.img
4. Volume button to boot into recovery
Result = Boots into system
Click to expand...
Click to collapse
For clarification of step 4. I think recovery is the second or third option in bootloader. You are hitting volume down twice and then volume up correct
Volume up selects.
The mismatched partition size doesn't matter everyone gets that error.
Visi0nofExcellence2 said:
For clarification of step 4. I think recovery is the second or third option in bootloader. You are hitting volume down twice and then volume up correct
Volume up selects.
The mismatched partition size doesn't matter everyone gets that error.
Click to expand...
Click to collapse
You know what, I am so used to newer devices like N6 and 6P that I completely overlooked that the Volume Up button was the selector instead of the power button. It was rebooting into the system EVERY TIME because I was hitting the power button. Recovery installed successfully and running LineageOS with Magisk with Android Pay and Direct TV Now working just fine.
Thanks for your help and I'll be sure to actually READ from now on :laugh::laugh:

Is there ANY way to install TWRP without the keypress combo to bootloader?

I have a Verizon Tab S2 sm-t817v. I have successfully flash TWRP to it via Odin probably 20 times. Problem is i have a sticky vol up key. So when the tablet reboots it doesn't detect the keypress, it either reboots normally, or if im unlucky it boots to the 4 option recovery and erases my tablet. Is there anyway to reboot straight to bootloader to allow TWRP to install, perhaps using ADB?
Admins/Moderator move this post if its in the wrong place. Thanks.
adb reboot bootloader

Categories

Resources