Database Users

Stuck on "Warning Bootloader Unlocked" Screen after OTA

I bought my first phone from Swappa a couple days ago, and figured I would go ahead and by a rooted/unlocked RAZR M and start messing with ROMS.
When I booted the phone, and got connected to my WiFi network it said I had an OTA, so I went ahead and installed it, (now I know that one should avoid OTAs on rooted phones), but now its stuck on the Warning Bootloader Unlocked screen. I do a hard reset (power + volume up/down), it boots, its done, I unlock the screen, it shuts down, repeat. I can't get it unstuck.
This is my first experience with any sort of unlocked or rooted phone, so I have no idea what I'm doing.
Please help

http://www.droidrzr.com/index.php/topic/16812-droid-razr-m-utility-120-windowsmaclinux/ as long as your BOOTLOADER IS UNLOCKED run this

Which option am I supposed to choose (1-6)? I can't boot into it normally, its stuck on the Warning Bootloader Unlocked screen.

Kruger2147 said:
Which option am I supposed to choose (1-6)? I can't boot into it normally, its stuck on the Warning Bootloader Unlocked screen.
Click to expand...
Click to collapse
When your phone turns off hold all three buttons then go into ap fastboot and use option one
Sent from my XT907 using Tapatalk 2

Kruger2147 said:
Which option am I supposed to choose (1-6)? I can't boot into it normally, its stuck on the Warning Bootloader Unlocked screen.
Click to expand...
Click to collapse
You need to be in fastboot, before connecting the phone to the computer and starting the utility. Brandon gave you the key combo to do it.

I got it fixed, and it upgraded to 4.1.2, then went to install Eclipse ROM, the install failed so I hit ++++ back+++++ and then rebooted from the recovery menu, and now it's stuck in the Warning Bootloader Unlocked screen again. Hard reset doesn't work, it reboots back into the Warning screen, and the utility that was posted earlier isn't connecting to recover the device.
What now?
Sent from my SCH-I535 using Tapatalk 2

Kruger2147 said:
I got it fixed, and it upgraded to 4.1.2, then went to install Eclipse ROM, the install failed so I hit ++++ back+++++ and then rebooted from the recovery menu, and now it's stuck in the Warning Bootloader Unlocked screen again. Hard reset doesn't work, it reboots back into the Warning screen, and the utility that was posted earlier isn't connecting to recover the device.
What now?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Boot back into fastboot and use the utility again. The utility won't work unless you're in fastboot, and for heaven's sake, make a backup of your stock ROM, before flashing anything new. If you had a saved ROM, this would be easy. After Eclipse failed to install (it has been well documented that a straight install of Eclipse through TWRP or CWM usually won't install), you could have easily gone to the main menu in recovery and clicked "restore" and restored with zero issues.

Kruger2147 said:
I got it fixed, and it upgraded to 4.1.2, then went to install Eclipse ROM, the install failed so I hit ++++ back+++++ and then rebooted from the recovery menu, and now it's stuck in the Warning Bootloader Unlocked screen again. Hard reset doesn't work, it reboots back into the Warning screen, and the utility that was posted earlier isn't connecting to recover the device.
What now?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
always make a backup man, safe yourself some time.

I can get it to boot into Fastboot no problem, but when I go to run the script its not recognizing that the phone is connected. The phone says "Connect USB
Data Cable" even when its connected. I'm not sure which side is failing to see the connection, the phone or computer.

Kruger2147 said:
I can get it to boot into Fastboot no problem, but when I go to run the script its not recognizing that the phone is connected. The phone says "Connect USB
Data Cable" even when its connected. I'm not sure which side is failing to see the connection, the phone or computer.
Click to expand...
Click to collapse
Make sure your driver's are up to date
Sent from my XT907 using Tapatalk 2

I'm running Fuduntu Linux, the script worked the first time, but not the second. I'll trying running it on my girlfriends computer with Windows when I get home tonight.
EDIT: Never mind my girlfriend fixed it while as was at work, looks like my computer was being stupid. Thanks for all your help guys.
Sent from my SCH-I535 using Tapatalk 2

how did you get out the stuck mode..
Kruger2147 said:
I'm running Fuduntu Linux, the script worked the first time, but not the second. I'll trying running it on my girlfriends computer with Windows when I get home tonight.
EDIT: Never mind my girlfriend fixed it while as was at work, looks like my computer was being stupid. Thanks for all your help guys.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
hi, can you tell me how did you get out from the stuck mode, i am in the stuck mode now..

locked bootloader wont unlock

Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers

truebattleaxe said:
Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers
Click to expand...
Click to collapse
also I wanted to add. I have the android sdk installed and all drivers installed properly. as well as adb/fastboot.

Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
hey slow cobra. yes fastboot does recognize the device. however fastboot oem unlock doesn't do anything.

Stuck in fastboot

Hi, everyone!
Yesterday I wanted to update my rooted Nexus (2012, Wifi) to 4.3 Android. So I tried a "Back to stock" using Nexus Root Toolkit. After that the Nexus is stuck in fastboot mode, if I turn it on I see the Google logo, but green square with the START appears and the only option that works (other that POWER OFF) is Restart bootloader.
I tried many of the methods (hard reset, fastbooting an img using commands) I found but nothing seems to work, it's just stuck
Cheers

Try with you nexus toolkit to unlock first. This worked for me.

Need help same problem!
Nothing helps ..
I was going to flash stock and unroot N7 wifi so i can uppdate to 4.3
But it didnt work and im stuck in fastboot mode.
Reset dosent work
Trying reflashing dosent work
Use nexus toolkit 1.73
tried restore stock kernel and waited 10 min.. but only sais booting downloaded image
Tried unlock (Device where already unlocked) and loc
EDIT: I got it fixed... i reflashed same build 4,2 and it did work
so i tried again to flash 4.3 and got same ****
and finally i did force flash mode and installed 4.3
Ps. i did restart pc and n7 inbetween all steps

stuck to fastboot
qblu said:
Try with you nexus toolkit to unlock first. This worked for me.
Click to expand...
Click to collapse
hi i need help on this, i tried to flash android 4.4 krt16s on my nexus 7 2nd gen using the nexus root toolkit. but unfortunately the flashing failed and now i'm stuck on the fastboot mode. i tried to i tried to press the start (coz its the only option enabled for me) but its stuck on the google screen, now its not booting up, i tried to turn it off and turn it on again but its still stuck on the google screen. please help me get it back to normal working condition :crying:

Stuck in fastboot ot fail the ota or bootloop all can be fixed by downloading google stock nexus image and letting toolkit flash it. Ull be going back to stock without root but then u have a working device and a solid bass then start your tinkering again.
I do soft brick just for fun and fix it later so i know how bad things can get.
Sent from my Nexus 7 using xda app-developers app

[Bricked?] Can't get to bootloader after trying to unlock with NRT

So I have a nexus 10 32gb that I got yesterday that I updated to 4.4.4 and I wanted to root it so I could get some apps that I love to use. Here's what happened:
Everything was going smoothly with nexus root toolkit. I set up adb and all of the drivers. Everything with that was working and I made sure to check nexus 10 with 4.4.4 in the drop down. I press the unlock bootloader button and the device says it's going into bootloader mode, but it just goes to a black screen. Then a message pops up saying I have to factory reset if i'm on 4.4.4, but that never shows up on the tablet, so I just hit OK. Then the device supposedly reboots, but now it's stuck in a bootloop and whenever I hold down the buttons to go into the bootloader the screen will turn black and the device will vibrate once after I hold the buttons for a while, then it tries to reboot again and gets stuck bootlooping. Then I try the factory reset method through the nexus root toolkit, but fastboot fails to see the device since I can't get it into the bootloader! It also doesn't show up as the correct device when it is bootlooping and connected to my computer.
Am I scewed if i can't get to the bootloader? I don't know what went wrong. I just got it yesterday and assumed it would be super easy to root since it's a nexus device. :'(
Any help/ suggestions would be great.

You are correct, nexus devices are super easy to root especially without a toolkit, most rooting issues I've seen on any nexus device has been due to the use of a toolkit so I would advise not to use it.
Currently you need to get into bootloader so you can flash a custom recovery with fastboot and then flash ROM of choice from there
Try adb reboot bootloader while in bootloop but I have a feeling this won't work. So if not try powering on holding volume down, even try with volume up, just keep trying button combos to get it to boot into bootloader.
For further help try here
http://forum.xda-developers.com/showthread.php?t=2670400
But keep trying to get into bootloader
Sent from my Nexus 4 using XDA Premium 4 mobile app

Try power and both volume buttons at the same time if you haven't already.

sfobrien said:
Try power and both volume buttons at the same time if you haven't already.
Click to expand...
Click to collapse
I have actually been trying that. I just let it die while it was bootlooping, so hopefully when it gets a little charge I can try to get it to go into the bootloader again. I have a feeling there's a bigger issue than that though.

Bootloop and cannot boot into recovery

Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.

Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Are you saying that you did not have OEM Unlock turned on or have USB debugging enabled in developer options? Is your phone recognized by ADB when you are connected to your PC? When you enter the Bootloader, can you select ADB Sideload with bootlooping? I have been trying to help a couple of people with this issue for the past few days Also, when you enter the Bootloader does your 6P show DOWNLOAD MODE is Disabled?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode

met911 said:
Yes, i never enabled it because i did not know it exists. My phone is not detected by ADB and download mode is disabled.
How can i can selected ADB sideload if i cannot enter recovery mode
Click to expand...
Click to collapse
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Try this:
Press and hold the POWER BUTTON + VOLUME UP and continue to hold them. Watch the screen. Does it still continue to bootloop or does a screen show up that says "NO COMMAND"? If the NO COMMAND screen is displayed, let your device sit without doing anything. There are some devices that have sat at this screen, rebooted on its own and booted back into the OS. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.

met911 said:
It showed no command once and then rebooted into bootloop again.
Tried it again after and it did not show no command. just went into bootloop.
Click to expand...
Click to collapse
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Once the NO COMMAND showed up on the screen did you release the buttons or continue to hold them? I.should have clairified that before hand. Sorry.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.

met911 said:
I continued to hold them at the beginning but nothing happened. it was rebooting again and again without showing the no command. once i released them, then the no command showed up.
Click to expand...
Click to collapse
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
After the No COMMAND showed up, did it continue to bootloop by itself after sitting at the No COMMAND screen?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. i left it as you mentioned and it went into bootloop. Even the one time i managed to get it in recovery mode and made factory reset and wipe cache partition. I did not get it to be detected by ADB as debugging was not enabled in the setting menu.
This recovery mode is really useless if you cannot start the phone. Its supposed to be RECOVERY mode but its completely useless.
Previously, you could just unlock the bootloader and flash new image. Now it must be enabled in the setting in a phone that does not even work.

The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
The only option you have with a locked Bootloader is to attempt to ADB sideload a zip or OTA and that's only if you could select adb sideload from recovery. When you open the Bootloader does your device show that DOWNLOAD MODE is DISABLED? Also, have you checked to see if you can issue any fastboot commands while in the Bootloader?
Sorry, I asked about the Download Mode showing disabled again. I've read so much about this and so many threads I forgot. Try this for me:
Open the Bootloader
Type this fastboot command:
Fastboot oem ramdump enable
Fastboot reboot Bootloader
Power down
Power up to the Bootloader
Try selecting adb sideload again and see what it does.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
You are asking the same questions again. YES, download mode is disabled.
after the first command, it tells me "locked device to enable ramdump"
I tried adb sideload but did not work because its not enabled in the phone settings as i already mentioned before.

I apologize for asking the same questions. I got confused on which thread I was posting in. I have been trying to help someone else with the same issue.
Sent from my Nexus 6 using XDA-Developers mobile app

Adb sideload won't work in bootloader mode, only in recovery. The only thing that will work in bootloader mode is fastboot but seeing as the bootloader is locked (with no way to unlock it) you can't use fastboot. If you can't get into recovery there's nothing you can do except send the phone for repair.

But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.

met911 said:
But how can anyone troubleshoot any phone if the OS is not working. This new way of security is simply impossible.
So if the OS fails like my case, i am screwed.
Click to expand...
Click to collapse
I'm not sure what you mean by new security, this has been standard fare for some time now. I'm sure if your phone was stolen you'd be thanking this security feature because it'd mean that the thief couldn't possibly access your data.
People in the know usually go into the settings menu and tick the "allow oem unlocking" box even if they don't plan on unlocking the bootloader at that time, there's a slight security risk but it's insurance against situations like this.
And what you're saying isn't entirely true; even if the OS fails the phone can usually still boot into recovery which would mean being able to revive it via adb sideload. What you're experiencing is relatively unusual, not being able to boot into the recovery as well as the OS means you're basically screwed.
If there's anything to take away from this it's that electronic devices fail sometimes. If you can handle the security risk it's worth ticking that box in the settings menu, or even completely unlocking the bootloader, to give yourself some insurance against these rare situations.

Same problem
met911 said:
Hi Guys,
My nexus 6p is running stock firmware with no root or any custom rom or recovery.
Suddenly, while i was browsing the internet on my phone, it restarted and went into bootloop through the google logo.
I tried to boot into bootloader and then tried to go to recovery mode from the bootloader but it went again into bootloop.
I then tried to download the latest image and tried to flash it but was surprised that i cannot unlock the bootloader except from inside phone settings (if it was working) which is very inconvenient.
Any thoughts as recovery mode is not working to be able to reset to factory settings and cannot flash any rom or original firmware as it's locked.
Click to expand...
Click to collapse
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me

ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.

ADEORA said:
I am having the same problem! I was watching videos on youtube and suddenly my 6p shut down and went into bootloop, I was able to boot it back up after hard resetting it. Few days after, it went into bootloop and now it cannot go into recovery mode. Please let me know if you found a solution to this madness. It is killing me
Click to expand...
Click to collapse
uodii said:
My phone just did the same thing yesterday morning. I'm currently waiting for Hauwei support to get online because Google wont do anything for me since it's been about 13 months (Google only offers a 12 month warranty). Hoping for the best, but without being able to access Recovery makes me very doubtful.
Click to expand...
Click to collapse
You both might want to take a read of http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921 - it has many people who have experienced the issue you both have. tl;dr - you'll probably need to contact goog/huwaei for a replacement.

Had the exactly same issue the day before yesterday, tried every possible way to flash different versions of images, none worked. My warranty expired 2 weeks ago, so both google and huawei told me that I am on my own for this.

Wow.. I feel for you all. I've had the exact same thing happen some weeks ago, phone freezing, then reboot, then couple of days later bootloop, then able to flash and reinstall, then after one final bootloop with the phone unable to 'take' the flashing through recovery, etc, etc. I've been playing with xda since the days of Froyo and that was the first time I had to send a phone back under warranty.
I was just about to try to manually rebuild the whole partition system at the block level but I'm glad I could send it for repairs. You might have a chance if you go as low as that. Good luck
* edit * I got the TWRP to stick by flashing it in Fastboot a couple of times in a row at that time, then I was adapting a Linux guide on reformatting and repairing drives partitions and all that through an adb shell.I did not get it to work yet before sending it, though.