Develop Bugs

[Q] Unlocking bootloader failed [SOLVED]

I've installed all the correct drivers and followed all the instructions, typed in 'fastboot.exe -i 0x0fce getvar version' in cmd and it responds correctly, but when I type 'fastboot.exe -i 0x0fce oem unlock 0x8953C6AC2154D8C9' to unlock the bootloader, it always gives me the same error;
FAILED <remote: oem unlock failed!>
can someone help me?

in dialer: *#*#SERVICE#*#* > service info > configuration > Rooting status. whats written under it? whats phone model r800(?)?

Try flash tool
Sent from my R800x using xda premium

I used xda rom hub to unlock my booloader.
Sent from my Xperia Play

Stevethemann said:
I've installed all the correct drivers and followed all the instructions, typed in 'fastboot.exe -i 0x0fce getvar version' in cmd and it responds correctly, but when I type 'fastboot.exe -i 0x0fce oem unlock 0x8953C6AC2154D8C9' to unlock the bootloader, it always gives me the same error;
FAILED <remote: oem unlock failed!>
can someone help me?
Click to expand...
Click to collapse
Have you double checked your unlock code? Or have you checked the root status like darkharbinger81 said. Both are common mistakes. Very easy to check too.

Bootloader unlocked: Yes.
R800i
Android version 4.0.2.a.0.42
Do I need to root it first? And the same error surfaces for my Xperia Sola... MT27i, stock 6.1.1.B.1.54, BL unlock: yes

Stevethemann said:
Bootloader unlocked: Yes.
R800i
Android version 4.0.2.a.0.42
Do I need to root it first? And the same error surfaces for my Xperia Sola... MT27i, stock 6.1.1.B.1.54, BL unlock: yes
Click to expand...
Click to collapse
Stevethemann said:
I've installed all the correct drivers and followed all the instructions, typed in 'fastboot.exe -i 0x0fce getvar version' in cmd and it responds correctly, but when I type 'fastboot.exe -i 0x0fce oem unlock 0x8953C6AC2154D8C9' to unlock the bootloader, it always gives me the same error;
FAILED <remote: oem unlock failed!>
can someone help me?
Click to expand...
Click to collapse
Check (and doublecheck) what IMEI number you entered in Sony's site.
Type in dialer *#*# 7378423#*#* , go to service info> configuration and check your IMEI.
And IMPORTANT, that number will be 15 digits, but in Sony's site for bootloader unlocking you enter only 14 digits (ignore last digit)
If that fail, try some other thing:
-put usb cable in back usb ports of your motherboard
-try different usb cable
And finaly, as i recall, try by typing 0xfce instead of 0x0fce ( 'fastboot.exe -i 0xfce oem unlock 0xKEY)

Okay I went through the whole procedure again, double checked everything, the website gave me a different code and it worked this time. Thanks everybody!

Info needed for Unified Toolkit

If anyone can give me the following information it would be useful in adding the Pixel C to the Unified Android Toolkit.
1. Is the "Allow OEM unlock" option present in the developer options (needs checking before bootloader can be unlocked)?
2. What is the key combo to boot the device to fastboot mode manually?
3. Is it a standard bootloader screen (i.e. down volume and power to boot to recovery)?
4. What instructions do you get on the device after running fastboot flashing unlock to unlock the bootloader?
If anyone can fill in any of the information or add anything that would be useful then please do..
Mark.

1. Is the "Allow OEM unlock" option present in the developer options (needs checking before bootloader can be unlocked)?
A: Yes
2. What is the key combo to boot the device to fastboot mode manually?
A: Power + Volume down (when in landscape). The bootloader has an option to "Switch to fastboot mode" which you select with volume down and then the power button. It will switch to a screen that says "Waiting for fastboot command..." with no option to go back.
3. Is it a standard bootloader screen (i.e. down volume and power to boot to recovery)?
A: Yes. Here is a picture of it: https://goo.gl/photos/YQ5FVKf6HAWQWwd5A
4. What instructions do you get on the device after running fastboot flashing unlock to unlock the bootloader?
A: You are given the option to press power to unlock the bootloader or volume down to cancel. The device then says the bootloader is unlocked and it will reboot in 30 seconds. After that, you get the recovery robot with an "Erasing" dialog.

oRAirwolf said:
1. Is the "Allow OEM unlock" option present in the developer options (needs checking before bootloader can be unlocked)?
A: Yes
2. What is the key combo to boot the device to fastboot mode manually?
A: Power + Volume down (when in landscape). The bootloader has an option to "Switch to fastboot mode" which you select with volume down and then the power button. It will switch to a screen that says "Waiting for fastboot command..." with no option to go back.
3. Is it a standard bootloader screen (i.e. down volume and power to boot to recovery)?
A: Yes. Here is a picture of it: https://goo.gl/photos/YQ5FVKf6HAWQWwd5A
4. What instructions do you get on the device after running fastboot flashing unlock to unlock the bootloader?
A: You are given the option to press power to unlock the bootloader or volume down to cancel. The device then says the bootloader is unlocked and it will reboot in 30 seconds. After that, you get the recovery robot with an "Erasing" dialog.
Click to expand...
Click to collapse
Thanks for the quick response. Just need a bit more info about the actual bootloader.
Do you know if fastboot commands can be sent after booting to the bootloader mode? Or do you have to boot to bootloader and then select "switch to fastboot" to accept an input? If you have used adb with the device could you run adb reboot bootloader and tell me if the device goes to the bootloader or the fastboot screen.
I also need error messages when unlocking. If you (or someone else) could run the following that would be great.
1. With "Allow OEM unlock" NOT ticked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
2. With the device already bootloader unlocked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
I think thats all thats needed for now to make a basic toolkit for the Pixel C to unlock, backup data, flash stock image, etc. If a custom recovery becomes available then it will then be very simple to add a root process.
Mark.

I am heading to bed but if nobody has replied before I get to work this afternoon, I will be happy to get answers to the rest of your questions.

oRAirwolf said:
I am heading to bed but if nobody has replied before I get to work this afternoon, I will be happy to get answers to the rest of your questions.
Click to expand...
Click to collapse
Thanks I appreciate it.
Mark.

mskip said:
Thanks for the quick response. Just need a bit more info about the actual bootloader.
Do you know if fastboot commands can be sent after booting to the bootloader mode? Or do you have to boot to bootloader and then select "switch to fastboot" to accept an input? If you have used adb with the device could you run adb reboot bootloader and tell me if the device goes to the bootloader or the fastboot screen.
I also need error messages when unlocking. If you (or someone else) could run the following that would be great.
1. With "Allow OEM unlock" NOT ticked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
2. With the device already bootloader unlocked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
I think thats all thats needed for now to make a basic toolkit for the Pixel C to unlock, backup data, flash stock image, etc. If a custom recovery becomes available then it will then be very simple to add a root process.
Mark.
Click to expand...
Click to collapse
If I boot into the bootloader, I am unable to issue fastboot commands until I select "Switch to fastboot mode."
Using ADB, when I issue the "adb reboot bootloader" command when the device is on normally, it goes directly to the fastboot screen and says "Waiting for fastboot command..."
When "Allow OEM unlock" is not ticked and I boot to fastboot and issue "fastboot flashing unlock," I get no error message on the device, but I do see the following in the command prompt:
Code:
C:\>fastboot flashing unlock
...
FAILED (remote: Device already unlocked)
finished. total time: 0.005s
When "Allow OEM unlock" is not ticked, the bootloader is unlocked, I boot to fastboot, and issue "fastboot flashing lock," I get no error message on the device, but I do see the following in the command prompt:
Code:
C:\>fastboot flashing lock
...
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.020s
When the bootloader is unlocked and in the fastboot screen, if I issue "fastboot flashing unlock," I get no error message on the device, but I do see the following in the command prompt:
Code:
C:\>fastboot flashing unlock
...
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
Let me know if there is anything else you need.

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly

How can I unlock the bootloader?

I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?

How unlock the bootloader?My HTC U20 5G no download mode in bootloader !!!!!
Try
fastboot oem get_identifier_token --- error
fastboot flashing unlock --- error
fastboot oem unlock --- error

Yes I have the same problem. I thought it was Win 10, so I tried Win 7 as well, but got the same error there too.

Check if "USB debugging" and "OEM unlocking" are activated in Developer options

iourikil said:
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
Click to expand...
Click to collapse
Yes, both options are activated (at least in my case).
Both commands "fastboot flashing unlock" and "fastboot oem unlock" result in "FAILED (remote: 'unknown command'), fastboot: error: Command failed".

I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s

iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
Click to expand...
Click to collapse
It also works with the U19e, very annoying that they changed it.

iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
Click to expand...
Click to collapse
In U20 fastboot can't use this way and In bootloader no download mode to select. >"<

elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
for anyone that might come across this problem. I had the same issue trying to use fastboot to relock my bootloader. Found the answer on another forum. I was using adb to reboot to fastboot mode to run the command. This was the problem. I needed to reboot to the bootloader to run the command

elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.

Hi there,
Just wanted to check in and see if anyone has managed to get bootloader unlocked?
Or is the htc u20 out of luck....

arcslt18 said:
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Click to expand...
Click to collapse
can you teach me how to do that?
thank you

mofish said:
can you teach me how to do that?
thank you
Click to expand...
Click to collapse
Hi, Just manually enter the fast boot mode with power key+Volume Up or Down depending upon the model and make, You can search this online how to enter Bootloader mode for one particular device. Once you are in Bootloader, Try Fastboot mode and Enter your commands. Should work

Anyone figure this out on Nord n200 5g T-Mobile variant? Please help

Issues in bootloader unlocking

Hello!
I'm trying to root a Moto G 5G Plus (XT2075-3) but for some reason bootloader unlocking fails.
adb and fastboot seems to be working just fine. I'm using the latest platform tools & motorola USB drivers.
So I was able to get the unlock code with fastboot oem get_unlock_data command and successfully generated an unique unlock key for my device.
The issue is that fastboot oem unlock command returns me the following:
fastboot oem unlock MY_UNLOCK_KEY_HERE
FAILED (remote: '')
fastboot: error: Command failed
Does anybody have any idea what is causing this? Been trying to reinstall drivers, generate a new unlock key but nothing seems to help. Could it be possible that the unlock key is invalid or does it seem more like a driver related issue?
I've rooted few XT2075-3 phones in the past and never had such issues before...
Any thoughts or ideas how to fix this would be much appreciated!
Thanks in advance,
Han

Han Cello said:
Hello!
I'm trying to root a Moto G 5G Plus (XT2075-3) but for some reason bootloader unlocking fails.
adb and fastboot seems to be working just fine. I'm using the latest platform tools & motorola USB drivers.
So I was able to get the unlock code with fastboot oem get_unlock_data command and successfully generated an unique unlock key for my device.
The issue is that fastboot oem unlock command returns me the following:
fastboot oem unlock MY_UNLOCK_KEY_HERE
FAILED (remote: '')
fastboot: error: Command failed
Does anybody have any idea what is causing this? Been trying to reinstall drivers, generate a new unlock key but nothing seems to help. Could it be possible that the unlock key is invalid or does it seem more like a driver related issue?
I've rooted few XT2075-3 phones in the past and never had such issues before...
Any thoughts or ideas how to fix this would be much appreciated!
Thanks in advance,
Han
Click to expand...
Click to collapse
Did you tick OEM unlocking in developer options?

Hi,
Yeah, OEM unlocking is enabled in developer options.