Database Develop

Unable to unlock N6 bootloader (Android 6.0.1 Build MMB29X) [resolved]

Hi,
I am unable to unlock the bootloader on my Nexus 6, which was purchased new from Amazon.com. Or more accurately, I can issue the fastboot flashing unlock command without error, but my phone still says LOCKED and screen is frozen for 60 seconds.
I have followed the various HOWTOs on this website to the best of my ability:
1. Installed latest Android SDK tools(25.1.4.rc1), Platform-tools (24rc2) & Java8. I originally installed with the 23.1 platform-tools but then moved to the preview channel release when I had no luck.
2. USB debugging and OEM unlocking are both ON
3. Both "adb device" and "fastboot device" show my phone's serial number when in their respective modes, so I know communication is good between my laptop and phone.
How to replicate problem:
a. With my phone connected, I first issued "adb reboot bootloader". My phone then sucessfully changes to the AP Fastboot Flash Mode (Secure) screen. Beneath the green BATTERY OK (Charging) are the lines
Device is LOCKED. Status Code: 2
Transfer Mode: USB Connected
b. I then type "fastboot flashing unlock" and the output is
...
OKAY [ 0.016s]
finished. total time: 0.016s
However my phone does not ask me if I want to unlock. In fact, the screen then appears to be frozen -- pressing the volume up and down buttons does not change the power button selection menu. If I try to issue any other fastboot command, it says FAILED (command write failed (Unknown error)) finished. total time: 5.017s
The screen is frozen for 60 seconds. After that, the bootloader screen is once again functional (I can change menu options again) and I can issue new fastboot commands, such as 'fastboot reboot'
However, the device still says LOCKED and will refreeze for 60 seconds if I type 'fastboot flashing unlock'
Any suggestions would be appreciated!
Thank you.

type fastboot oem unlock to unlock your bootloader, then follow instruction. But beware, this will wipe your device

TMG1961 said:
type fastboot oem unlock to unlock your bootloader, then follow instruction. But beware, this will wipe your device
Click to expand...
Click to collapse
In newer versions of fastboot, the command is fastboot flashing unlock, not OEM unlock.
Code:
$ ./fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.

@webtrader,
@TMG1961 was trying to help you. Have you tried his recommendation before replying?

cam30era said:
@webtrader,
@TMG1961 was trying to help you. Have you tried his recommendation before replying?
Click to expand...
Click to collapse
No, I had not. I tried using fastboot oem unlock on an older version of the SDK toolkit and that had failed, but I had not tried using oem unlock again on the latest version, having noticed that "oem unlock" was no longer listed as an option.
I just tried it now on the latest SDK toolkit and it does indeed work for me. :good:
Thank you to the both of you for helping me out!

webtrader said:
No, I had not. I tried using fastboot oem unlock on an older version of the SDK toolkit and that had failed, but I had not tried using oem unlock again on the latest version, having noticed that "oem unlock" was no longer listed as an option.
I just tried it now on the latest SDK toolkit and it does indeed work for me. :good:
Thank you to the both of you for helping me out!
Click to expand...
Click to collapse
Welcome

i do believe the "fastboot flashing unlock" is for when a manufacture issues a binary token kinda of like how HTC does it. If the Nexus or any phone that is not carrier branded, "fastboot oem unlock" will be the command to pass.

OEM Unlock Command Failed - "Not supported command in current status"

I recently reverted to stock so I can start from scratch and install everything over again. After all that and booting into android, I checked the ADB and OEM Unlock options in my settings. Then I rebooted into the bootloader and entered the "fastboot OEM unlock" command I followed the on-screen instructions and selected "yes" to continue. The command prompt then shows the following:
(bootloader) Unlocking bootloader...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 24.776s
I've googled this for about an hour and a half and can't seem to find an answer. Any help would be greatly appreciated.

I don't know if it's a typo, but you said you "booted into android" which to me suggests normal android system.
(which might explain why you needed adb...you don't need to enable adb for fastboot mode)
How about booting into fastboot / bootloader mode instead and try your commands there.
(press/hold power and volume down buttons to get to fastboot/bootloader mode)
Sorry if I'm misunderstanding and you are in fact attempting this in fastboot/bootloader mode.
also type a "fastboot devices" command to make sure fastboot is working between phone and pc

Someone else posted exactly this question a few months ago.
Answer? The device was already unlocked.
http://forum.xda-developers.com/nexus-6/help/help-bootloader-unlock-t3349455

I figured that might be the case. I assumed flashing the factory image also re-locked the bootloader.

You had it right. I booted the Android system. I was following the steps on the All-In-One Beginner's guide which included enabling adb. But as for me running the unlock command, I was in the bootloader when trying that.
@dahawthorne gave me the right answer in saying the device is already unlocked. Now I have a separate issue where I can't complete the rooting process, but I'll post a separate thread if I can't figure that out.

Nexus 6 soft bricked - OEM Unlocking enabled / Bootloader Locked

I rooted my Nexus 6 in an attempt to install nethunter linux distro by Kali. I was using the Nexus Root Toolkit v2.1.9. The phone will connect to PC and I can get it to load into fastboot with the normal options available but the bootloader is locked. When attempting to use any recovery option the phone boots to the "Google" logo and then flashes the android icon laying down with the red triangle and the words "No command" then shuts off. I have searched numerous threads and articles on the internet I keep getting stuck at the bootloader locked.
Nexus Root Toolkit v2.1.9
Masterlists:
- LatestToolkitFiles.ini 3150
- AndroidDeviceListFull.ini 3150
- AndroidDeviceListFlash.ini 3150
SHAMU-SHAMU: Android 7.1.1 - Build: N6F26U
Live log initiated [2017-08-16]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G22HSLB fastboot
+ Fastboot Device Connected
+ Bootloader Status: Locked.
adb devices
fastboot devices
ZX1G22HSLB fastboot
+ OEM Unlocking Enabled
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
ZX1G22HSLB fastboot
+ Fastboot Device Connected
+ Bootloader Status: Locked.
+ OEM Unlocking Enabled
fastboot oem unlock
Rebooting your device...

First thing to do is ditch the toolkit. Learn how to use ADB via the command line. Second thing to do is download an OTA image from Google and sideload it. That should restore your device to operating condition, despite the bootloader being locked. All data on the device will be wiped when doing this.

I have used the ADB / Fastboot cmd lines within powershell but each time I try to flash the bootloader I get the
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)

Are you in recovery mode when trying to sideload the OTA? If not, you need to be. The only command needed is "adb sideload [ota]".

As long as Allow OEM unlock is checked in developer options, you can unlock the bootloader via fastboot, with fastboot oem unlock.

@Char_G: I guess I read "OEM Unlocking Enabled" differently, i.e. wrong, when I attempted to help him.

Strephon Alkhalikoi said:
@Char_G: I guess I read "OEM Unlocking Enabled" differently, i.e. wrong, when I attempted to help him.
Click to expand...
Click to collapse
I've always unlocked my bootloader as soon as I got the device so I've never seen that particular text before, I'm assuming it means that he's checked that box but I don't know for sure lol

when running the command in powershell i get
PS C:\Users\n0n3m\Desktop\android-sdk-windows\platform-tools> ./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
the phone will no longer stay on the android with the red triangle to allow me into the recovery mode option to select sideload with adb

n0n3mulat0ry said:
when running the command in powershell i get
PS C:\Users\n0n3m\Desktop\android-sdk-windows\platform-tools> ./fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.003s
the phone will no longer stay on the android with the red triangle to allow me into the recovery mode option to select sideload with adb
Click to expand...
Click to collapse
Sounds like it flash stock recovery hold power button and press the volume up key that should allow you to select adb sideload in recovery
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------
Jnewell05 said:
Sounds like it flash stock recovery hold power button and press the volume up key that should allow you to select adb sideload in recovery
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
But you saying that it won't stay on screen long enough to get into recovery.. that's strange. I haven't experienced this before
Sent from my Nexus 6 using Tapatalk

Have you fixed your issue?

Huawei P9 stuck In bootloop

what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.

lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock

lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s

lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options

zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's

lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off

zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?

So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.

ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS

Fastboot remote command not allowed

I'm trying to unlock the bootloader. I got fastboot and adb to respond correctly. Here is what happens when I try:
Code:
C:\WINDOWS\system32>fastboot -i 0x0fce oem unlock 0x0FF21ECC85757B85
...
FAILED (remote: Command not allowed)
finished. total time: 0.068s
Any advice? I checked and my bootloader can be unlocked.
Aside question:
For some reason 'adb reboot fastboot' simply reboots the phone but 'adb reboot bootloader' boots into fastboot (so that fastboot devices responds correctly)

LuminousOne said:
I'm trying to unlock the bootloader. Any advice?
Click to expand...
Click to collapse
Developer options, OEM unlock - enable.
If it's greyed out then you may not be able to unlock.
Some phones sold though service providers have unlock disabled, no workround.

Didgesteve said:
Developer options, OEM unlock - enable.
If it's greyed out then you may not be able to unlock.
Some phones sold though service providers have unlock disabled, no workround.
Click to expand...
Click to collapse
My phone had the same problem showing the "OEM unlock" option greyed out.
Activating WiFi and checking for "system updates" fixed it for me, and I successfully unlocked the phone.