Hello,
My Nexus 5X stopped working few hours after Andriod 7.0 update.
It is not really a bootloop but would get stuck at google dot animation. Phone boots to fastboot and recovery.
I have tried adb sideload. It would install successful but get stuck again at animation.
I am trying my luck with fastboot.
My device bootloader is locked. To unlock it I need to use "fastboot oem unlock" or "fastboot flashing unlock".
Both these commands give me Failed (remote: oem unlock is not allowed).
Please help. How to fix this?
Believe you have to check the "OEM unlock" box in developer settings, than try "fastboot OEM unlock"
Sent from my Nexus 5X using Tapatalk
I unfortunately don't have access to Developer mode now without it booting. Also "fastboot OEM unlock " is not working.
The problem really exists. Also, for me as for other users.
https://productforums.google.com/forum/#!topicsearchin/nexus/nexus$205x$20bootloop
Related
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.
good friends after an update my google pixel stays in boot loop I have tried several ways to unlock the bootloader to install a stock rom from flashboot but every time i try to unlock the bootloader it tells me that i have to activate or unlock the oem option
I tried to do it with the adb flashtool but it gives me error
c:\adb>fastboot oem unlock
FAILED <remote: oem unlock is not allowed>
finished. total time: 0.044s
c:\adb>
I can not enter the Android system either from my Google Pixel since it is damaged the same to activate the option of OEM
I need someone to help me with this problem because the phone does not let me do anything for the fastboot because the bootloader and the OEM are blocked
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
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.
Hey, has anyone been able to unlock the boot loader yet? I enabled the "OEM Unlocking" option in the Developer Options and I used abd to load the bootloader but when I run "fastboot flashing unlock" or "fastboot oem unlock", it gives:
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Running
adb shell "getprop ro.oem_unlock_supported"
Click to expand...
Click to collapse
returns 1 so I don't get why it doesn't unlock for me.
Any help is appreciated as I want to run Magisk.
Ziikmar said:
Hey, has anyone been able to unlock the boot loader yet? I enabled the "OEM Unlocking" option in the Developer Options and I used abd to load the bootloader but when I run "fastboot flashing unlock" or "fastboot oem unlock", it gives:
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Running
returns 1 so I don't get why it doesn't unlock for me.
Any help is appreciated as I want to run Magisk.
Click to expand...
Click to collapse
Hey! Have you solved your problem? I'm having the same issue. Some websites say you need to use Mi Unlock Tool but I get a message that reads "request parameter error" and some websites say you also need to wait for 7 days before you can unlock the bootloader.
¿Alguien lo ha desbloqueado finalmente?
Has anyone succeeded in unlocking boot loader ???
nobody? id like to get one but not if bootloader is not unlockable
A shame. Really wanted this phone, but not without root.