I can't seem to unlock the bootloader for some reason - Nexus 6P Q&A, Help & Troubleshooting

I'm not an Android rooting noob (my rooting goes back to OG Moto Droid in late 2009) and I'm sure it's something ridiculously simple I'm missing but I can't get my bootloader to unlock. I've tried ADB/Fastboot, WUG's Nexus Root Toolkit, and Chevy's Android Job Box. Nothing works.
I got my 6P today, SIM'ed it up, booted up, logged in, enabled USB debugging, installed the drivers, and let it update. When I opened WUG's NRT, I saw that I had an Android build one step later than the NRT. Mine's MD80BL and K is the latest in the NRT. I thought that shouldn't be a problem and selected the "any build" option with the Nexus 6P. I went through the installing drivers process and can access the file structure of the phone through W10.
I then went to the unlock bootloader option, clicked through the prompts until the phone rebooted into the bootloader and clicked the OK button to unlock the bootloader. About two seconds later a window popped up on my desktop telling me my bootloader was unlocked, my data was wiped, and I would have to go through the setup process on the phone. Excellent, except my phone booted right back to my stock homepage. I tried again with the same result.
I then tried it manually using ADB/Fastboot. The "fastboot devices" showed a connected device which I assume is my 6P since I have nothing else Android connected. When I type in "fastboot flashing unlock" I get all the fastboot commands/options as if I typed an unknown command. "Fastboot oem unlock" didn't work either. I went and downloaded the latest SDK and retried everything with the same result.
Here's my Build Number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's what I get when I try to use fastboot to unlock the bootloader.
Any help will be much appreciated. I expect I'm going to feel stupid when my mistake is pointed out but I'm here to learn.

Upgrade your adb/flashboot setup. Probably too old.
You must allow the option to unlock, then go to fastboot, the run the command, with an updated version of fastboot command.

Ah, I see. The SDK Manager is not installing into my SDK directory. I'll copy/paste, retry, and report back. Thank you!

Now I get this message that unlocking the bootloader isn't allowed.

Narsil007 said:
Now I get this message that unlocking the bootloader isn't allowed.
Click to expand...
Click to collapse
Go to developer options & turn on the option that says enable bootloader unlock and retry.

Ha! I do feel stupid.
Thank you very much!!

You are very welcome!!!

Related

N7 (3G, 2012) bricked? Boot mode, no recovery. N Toolkit doesn't flash.

Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.
Anyone?
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.

ASUS ZE550KL - My phone is the god to failure =]

Hello everyone,
First of all, I apologize if this post is in the wrong section. Also I'd like to say how awesome it is everyone that is involved in these projects.
My Issue is I can't get ANYTHING to work, I have tried so many roms that apparently work for my phone and I always, foot errors, signature errors though the adb. I have tried every program to unlock bootloader but apparently does not work unless you are running V2 551 2.40.*.* so I went and downloaded this, and wants again can't flash the ROM. The unlock bootloader was weird, I went through all the installation and I don't even know if it worked to be honest. I can boot into the phone via power and volume down, and get a menu that includes, apply apps from ADB, wipe/restore phone, fastboot mode * which goes as far as my phone saying *FASTBOOT !!!* then thats it will not continue. The power and volume up does the same thing. So basically I'm starting to think this piece of crap phone will never have a decent operating system on it. The phone is in developer mode and USB debugging is on also. * Basically have done every single tutorial I can find and nothing works*. Also the twrp doesn't even work. I have even tried flashing back to an older version on the phone and get the same ADB errors. I have installed all the ADB and also minimal adb and fastboot and all drivers for the phone as well. * TRYING NOT TO MISS ANYTHING*
My phone specs:
Model: ASUS_z00LD
Android: 5.0.2
Baseband Version: 202c10_10.0.0_160120
Kernel: 3.10.49-gec27b65
Build: LRX22G.WW_user_1.17.40.1106_20160202044030520_2015052101030010000300001
IMAGES:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hope it works
Did you try to unlock bootloader the official way? I myself unlocked the ZE550kl following this thread http://forum.xda-developers.com/zenfone-2-laser/general/ze600kl-official-bootloader-unlock-t3273263
You can check if bootloader is lock or not from fastboot by entering "adb>fastboot oem device-info" should show up somewhere between the lines "Device unlocked: true"
After unlock only then you can install Official recovery TWRP 3.0.0-0 from here http://forum.xda-developers.com/zen...recovery-twrp-3-0-0-0-touch-recovery-t3317513 .
If needed TWRP will also help you root your phone once is installed.
Good luck!

Need help, after downgrade and official update

Folks, after a successful downgrade to 6.01 and re-lock the bootloader, i can install all ota's, but the one thing is, that the device will always stays on bootloader after reboot. Right now, i am on the latest MM and will update now to N. Everything works fine. This device must be locked.
I need manually press "START" to reboot into system or recovery mode.
I want to stay on originally software. How can this issue be fixed?
Try connecting your device to your computer, then whilst your device is at the bootloader, in the adb terminal on your computer type 'fastboot oem fb_mode_clear' (without quotes). This may allow your device to reboot properly.
echo92 said:
Try connecting your device to your computer, then whilst your device is at the bootloader, in the adb terminal on your computer type 'fastboot oem fb_mode_clear' (without quotes). This may allow your device to reboot properly.
Click to expand...
Click to collapse
Good job, works, right now
After the latest update to 7.0/NPJ25.93-14/16 it shows instead logo, ID=Bad key, this device is unlocked bla bla bla, but it isn't. Once i did this serveral month ago, it works but not now. MM does not shows a bad key.
i know i can flash a logo to cover this but it should be in original state. Screenshots follows_
After the latest update to 7.0/NPJ25.93-14/16 it shows instead logo, ID=Bad key, this device is unlocked bla bla bla, but it isn't. Once i did this serveral month ago, it works but not now. MM does not shows a bad key.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone help?
Gesendet von meinem Moto G (4) mit Tapatalk
No need to worry about,
after N update, everyone's phone has "bad key" ..
Just ignore it, it's nothing..

Can't Unlock Boot Loader. Enable OEM Unlocking.

I am currently unable to unlock the boot loader on my phone. The OEM Unlocking setting will not work. Earlier I tried to root my phone but I failed. I accidentally wiped the whole phone. I had to repair it by installing a factory stock rom(POTTER_NPN25.137-35). I have unlocked the developers settings and turned on USB Debugging. However I cannot turn on OEM Unlocking.
OEM Ulocking
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure what do to can someone please help me.
LeoG360 said:
I am currently unable to unlock the boot loader on my phone. The OEM Unlocking setting will not work. Earlier I tried to root my phone but I failed. I accidentally wiped the whole phone. I had to repair it by installing a factory stock rom(POTTER_NPN25.137-35). I have unlocked the developers settings and turned on USB Debugging. However I cannot turn on OEM Unlocking.
OEM Ulocking
I am not sure what do to can someone please help me.
Click to expand...
Click to collapse
Its already turned on. Just follow the steps of unlocking the bootloader. You will surely be able to unlock it!
Good Luck!!
I relocked myself and I have the option to unlock again. I'd suggest trying what Harshal0512 said.
LeoG360 said:
I am currently unable to unlock the boot loader on my phone. The OEM Unlocking setting will not work. Earlier I tried to root my phone but I failed. I accidentally wiped the whole phone. I had to repair it by installing a factory stock rom(POTTER_NPN25.137-35). I have unlocked the developers settings and turned on USB Debugging. However I cannot turn on OEM Unlocking.
OEM Ulocking
I am not sure what do to can someone please help me.
Click to expand...
Click to collapse
What does it show in the bootloader screen? Most likely, you have unlocked the bootloader successfully (thus the wipe, which is normal), now you just need to root it.
Sure hope this isn't something with King(o)root or a similar "one click" tool... most of those will not work, and some will even brick a Moto device.
I checked the boot loader and it is unlocked. I am not in the process of rooting it the device. Thank you all for you help.

Boot Up Question

Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
vik123 said:
Hi, I picked up this phone through a private sale and, while it works fine, I noticed a couple of things during boot up. This first flashed on the screen:
Then it went away and the following flashed on the screen:
Then it went to the main screen. Does this mean that something has been loaded onto the phone? What should I do to get it back to factory?
Thanks in advance.
Click to expand...
Click to collapse
The first screen indicates the bootloader is unlocked.
The second means you are not stock but running a custom ROM.
Back to stock -> https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
vik123 said:
Thank you for the link. I checked it but I am not sure which file to download. Sorry, I am not very familiar with all of this and I am nervous about bricking my phone.
Click to expand...
Click to collapse
Plug your phone into your PC using a good USB 3.0 cable after you reboot into the bootloader (do this by holding down volume down and power button at once. Also, use a type a to c cable, the essential phone stock USB c to c cable doesn't work that well for flashing stuff).
Then install the drivers for this phone from here on a windows system: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
Then install minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=745425885120698566
Then, download the latest back to stock zip from here:
https://www.androidfilehost.com/?fid=745425885120698566
Unzip into the folder you installed minimal adb and fastboot into, and then open minimal adb and fastboot. In the command window that pops up, type "flash-all.bat && fastboot -w" and then hit enter. This will reflash all the stock partitions and wipe all data.
After you get the stock essential phone firmware booting, you can reboot into the bootloader and run "fastboot -w" and then "fastboot flashing lock" to relock the boatloader if you plan on keeping the stock unmodified firmware.
Credit goes to @aer0zer0 for the dump of the latest firmware.
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
I can't believe the previous owner was such a jerk. I always return phones to full stock and relock the bootloader if I plan to sell a phone.
vik123 said:
Thank you so much. I followed the instructions and, while there were some nervous moments, managed to get it back to stock.
Click to expand...
Click to collapse
Hey no problem, always glad to help, especially since the situation you were in was caused by the previous owner not caring to flash stock and relock the bootloader before he sold you the phone. Seems like a careless thing to do, especially since he could've sold the phone to someone who wouldn't be tech savvy enough to restore stock.
The seller was really nice so I have a hard time calling him a jerk, but yeah, it was a careless thing to do. If it wasn't for this community I would probably have been screwed.
Thanks again everybody.

Categories

Resources