Database Users

Nexus 7 Bootloader Locked!

After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:

AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.

simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?

Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.

Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.

dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.

pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb

try do it on another pc

AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?

Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.

AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img

Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S

AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)

Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!

Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.

pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S

Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.

Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!

After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.

ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2

[Q] Stuck in FTM Mode?

Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")​
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?

Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.

Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2

joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.

OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!

Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2

drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem

ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install

same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help

need to unroot nexus 10 to send back in for exchange

I went to back up and reset and selected factory reset data. it doesnt appear to be unrooted as right when i boot it up the google screen shows an unlock symbol. is there an easy way to unroot it?

biotin5000 said:
I went to back up and reset and selected factory reset data. it doesnt appear to be unrooted as right when i boot it up the google screen shows an unlock symbol. is there an easy way to unroot it?
Click to expand...
Click to collapse
If you just want the lock icon gone the command is: fastboot OEM lock
Executed via the USB cable and fastboot.exe
Here is info on how to get back to stock if not already:
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2

bigmatty said:
If you just want the lock icon gone the command is: fastboot OEM lock
Executed via the USB cable and fastboot.exe
Here is info on how to get back to stock if not already:
http://forum.xda-developers.com/showpost.php?p=38995903&postcount=2
Click to expand...
Click to collapse
when i use the root checker program to check it says that i am not rooted, but i still have that unlock on start up. i did the factory restore like i said in the op. I have never used fastboot can i use the nexus. i just used a program called nexus root toolkit to do it for me automatically. should i be good?

biotin5000 said:
when i use the root checker program to check it says that i am not rooted, but i still have that unlock on start up. i did the factory restore like i said in the op. I have never used fastboot can i use the nexus. i just used a program called nexus root toolkit to do it for me automatically. should i be good?
Click to expand...
Click to collapse
The unlock icon does not mean that the tablet is rooted, it means your boot loader is unlocked. See a couple posts back for a easy way to re lock it or use of the money tool kits...
Sent from my Nexus 10 using Tapatalk HD

Yes, my guess is the toolkit actually originally executed 'fastboot oem unlock' behind the scenes

stock nexus 7 stuck in boot loop

i read that it can be fixed by unlocking and rooting. problem is it is a friends and he doesn't know what version of android is on it. also can't put it in usb debugging.

Install this using Fastboot which does not require USB debugging. Simply download the factory images package then extract into the ADB folder. Typing "flash-all.bat" will flash all stock images including the boot, recovery, system and data.

thank you that worked

waiting for device
Username invalid said:
using Fastboot which does not require USB debugging. Simply download the factory images package then extract into the ADB folder. Typing "flash-all.bat" will flash all stock images including the boot, recovery, system and data.
Click to expand...
Click to collapse
I tried doing this and looked pretty promising because I have the same exact problem, but the terminal just says that it is waiting for device and does not budge. I have tried rebooting both computer and device. Neither work. Any other suggestions?
I tried again and now it says erasing 'boot'... and hangs there..
Is there any way to enable USB debugging or ADB through the command line fastboot?

curioux said:
I tried doing this and looked pretty promising because I have the same exact problem, but the terminal just says that it is waiting for device and does not budge. I have tried rebooting both computer and device. Neither work. Any other suggestions?
I tried again and now it says erasing 'boot'... and hangs there..
Is there any way to enable USB debugging or ADB through the command line fastboot?
Click to expand...
Click to collapse
Is your bootloader unlocked? If not boot into fastboot mode and type the command fastboot OEM unlock follow the prompt on the tablet and it will reboot now try the flashall.bat again. There is no way to enable USB debugging without selecting it from the menu that's a question that has been asked many times before
Sent from my C5303 using xda app-developers app

No. Sorry I forgot to mention that. My bootloader is not unlocked. And when I tried to do the fastboot OEM unlock, that is the only time the screen changes and gives me the option to unlock. When I scroll to yes and push the power button, the terminal says erasing user data and then it just gets stuck there.
I suspect that there is some kind of reading or writing problem.
Sent from my SGH-T889 using Tapatalk

curioux said:
No. Sorry I forgot to mention that. My bootloader is not unlocked. And when I tried to do the fastboot OEM unlock, that is the only time the screen changes and gives me the option to unlock. When I scroll to yes and push the power button, the terminal says erasing user data and then it just gets stuck there.
I suspect that there is some kind of reading or writing problem.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
OK if the bootloader won't unlock that sounds like a corrupted nand partition which would mean the internal memory is unwritable. One more suggestion try downloading wugfresh NRT use the unroot back to stock option tick soft bricked and force write. I'm not sure it will work with a locked bootloader.
Sent from my C5303 using xda app-developers app

Captain Sweatpants said:
OK if the bootloader won't unlock that sounds like a corrupted nand partition which would mean the internal memory is unwritable. One more suggestion try downloading wugfresh NRT use the unroot back to stock option tick soft bricked and force write. I'm not sure it will work with a locked bootloader.
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
I have attached a screen shot of what I got when I tried the NRT unroot. It appears as though you were right, and that it is not going to work with a locked bootloader.

curioux said:
I have attached a screen shot of what I got when I tried the NRT unroot. It appears as though you were right, and that it is not going to work with a locked bootloader.
Click to expand...
Click to collapse
OK well it looks like you are at the new motherboard stage then. Fastboot OEM unlock failing is a pretty sure sign that the internal memory of your nexus has become corrupted and it is no longer possible to read from or write to the tablet. If you have warranty now would be a good time to use it. If not eBay is a relatively cheap place to get a replacement motherboard. Sorry I can't be of more help than that
Sent from my C5303 using xda app-developers app

Soft Bricked Nexus 6P with locked bootloader

I have a Nexus 6P running stock android, with a locked bootloader and I've only ever installed OTA updates. After installing an OTA update to NRD09U from my phone, I got the "Your Device is Corrupt. It can't be trusted and may not work properly," message. Attempting to press the power button to continue simply reboots the phone starting the process again. Obviously, because I can't even boot into android proper, I'm unable to enable developer mode or the other necessary settings in order to unlock my bootloader, so I'm stuck in a loop. I've tried sideloading a rescue OTA but I'm unable to flash an image because my phone isn't being recognized as an ADB device, even though the Android Bootloader entry shows up in my device manager as it's supposed. Even more puzzling is the fact that my phone shows up correctly as a fastboot device; typing "adb devices" returns an empty list, while typing "fastboot devices" lists the serial number of my phone as expected. I've tried a number of troubleshooting methods to fix this, including uninstalling the drivers from the device manager, and reinstalling them manually from a .zip obtained directly from google, but I still can't get my phone to be recognized as an ADB device so I'm still stuck.. I've tried contacting Google directly to get them to service my phone, but because the device is corrupted, they're telling me that my phone was rooted and that it wouldn't be covered under warranty, so they wanted to charge me almost $400 to fix it. I've read on some posts here and elsewhere that using the "fastboot format ***" works for some users with locked bootloaders, but it fails due to my bootloader being locked when I tried it myself.
So the way I see it in order to fix my phone I either need to find a method to unlock the bootloader manually using ADB/Fastboot/some other method that doesn't require OEM unlock or USB debugging, or I need to find away to get my device to be recognized as an ADB device so I can sideload the image. Anyone have any ideas how I can do this? Or some alternate solutions?
When I enter recovery mode, my system version is as follows: angler/angler/7.0/NRD09U
Thanks in advance.

Make sure you are using Android SDK tools and is up to date
Sent from my Nexus 6P using Tapatalk
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
Have you tried factory reset?
Sent from my Nexus 6P using Tapatalk

Enter stock recovery with the lying down Android. Use to side buttons to enter the menu. That's when ADB will work only.

gjkrisa said:
Make sure you are using Android SDK tools and is up to date
Click to expand...
Click to collapse
Everything should be up to date. I installed the SDK today, and I installed USB drivers from both the SDK manager and manually.
Factory reset fails, taking me back to the corrupted screen, which in turn brings me back to a bootloop.
Gazontop said:
Enter stock recovery with the lying down Android. Use to side buttons to enter the menu. That's when ADB will work only.
Click to expand...
Click to collapse
As soon as I enter recovery mode, my computer completely stops recognizing that the 6P is plugged in. It makes a sound like the device has been disconnected and there is nothing in the device manager.

If you're u don't OEM Unlocking or Bootloader unlocked then your at a lose...sell it for parts
Sent from my Pixel XL using Tapatalk

I think Google should fix this it's a defect in the memory most likely or a ****ty update
Sent from my Nexus 6P using Tapatalk

gjkrisa said:
I think Google should fix this it's a defect in the memory most likely or a ****ty update
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is it still under warranty?

tech_head said:
Is it still under warranty?
Click to expand...
Click to collapse
It was supposed to have been, but Google basically accused me of having rooted my phone even though the bootloader is still locked, and OEM is still locked too and I've never touched any of these settings.