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
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.
Hello guys:
One month ago i bought a Redmi note 8 pro, when it comes after a long time (almost 3 weeks) it comes with bootloader opened so i couldn use for example NFC pay. I looked for information to lock the bootloader i followed steps and bootloader was closed but phone was bricked too, so only can put smarthphone in fastboot or in recovery mode. I tried flash some roms by Fastboot using CMD in pc but appears this message
C:\adb>fastboot flash system system.img
target reported max download size of 134217728 bytes
erasing 'system'...
FAILED (remote: not allowed in locked state)
finished. total time: 0.004s
that was expected because bootloader is closed, but now i dont know if its posible to unlock bootloader and flash a new rom or beeing bootloader closed, flash a new rom for unbrick the phone.
To solve this problem I heard something abou autoriced xiaomi accounts and something about waiting seven days for unlock but i dont know nothing about it.
Thank you guys.
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Sythel4 said:
Have you tried the stock firmware and flash tool?
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I have tried to flash with fastboot and with miflash pro, and it always fails, I imagine that the flash tool will do the same as miflash pro and it will also fail, I will try anyway.
Thank you.
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Sythel4 said:
Try and give me a feedback
Sent from my SM-A705FN using Tapatalk
Click to expand...
Click to collapse
I'm sorry for answering late, but I'm very busy with the current health situation.
What I have done is focus on unlocking the bootloader, and later will flash a new rom.
To unlock the device i have download "mi flash unlock tool"
Software recognice my phone
Click on "unlock">"unlock anyway">"unlock anyway"
Verifying device-ok
Unlocking-Fail
Couldn´t unlock
Please add your account in MIUI´s Settings > Developers option > Mi Unlock status
This way doesnt work.
I try by fastboot and cmd commands
Fastboot devices
Ok is connected and recognized
fastboot oem device-info
...
time 0.002s
Failed (remote: Unknown command)
fastboot oem unlock
...
time 18.455s
FAILED (Remote: GetVar Variable Not Found)
(Smartphone disconect and rebboy on recovery mode)
And well...I dont know what to do now.
It won't unlock because your device is already unlocked. You need to flash stock rom from custom recovery. Install custom recovery via adb. when you go back to stock rom device will be oem locked again. Also original account that was used to oem unlock device may be required that is why it might be failing.
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919 (useful software here)
After flashing stock rom In fastboot try
Linux: adb fastboot-linux oem lock
OSX: adb fastboot-mac oem lock
Windows: adb fastboot-windows.exe oem lock
Hi there,
I try to install lineageos on my xperia xz2 compact but i dont manage to get the bootloader unlocked.
The rooting status says : Bootloader unlock allowed: Yes. so i thought it should be fine but in fastboot mode the command
Code:
fastboot oem unlock <unlockcode>
gives me:
Code:
...
FAILED (remote: Command not allowed)
finished. total time: 0.069s
I tried with flashtool (found this in some forums) but i get some error as well. Even though i am not sure to use this program properly and I also got some
"No device is registered in Flashtool. You can only flash devices."
error message there.
any ideas?
problem solved, I didn't know that I would have to enable "oem unlock" in the device's developper options. what a fail..
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.
Hello,
today i got a Moto E20 for debugging my webservices. I habe to Unlock the Bootloader for that.
I enabled the Developer-Menu in Android and the oem_unlock and usb-debugging in the settings.
When i boot the device into fastboot all seems OK... i get a connection with adb and fastboot to the device.
But all "fastboot oem XXX" commands just reply
fastboot oem device_info
...
OKAY [ 0.000s ]
finished. total time: 0.000s
Click to expand...
Click to collapse
That is the default reply for
fastboot oem get_unlock_data
fastboot oem device_info
just with different timings...
Any suggestions?
Bootloader version is aruba-1bfa2a4-2021
SW-Version: motorola/aruba_reteu/aruba:11/RON31.266-20/63893
kind regards
Sven
you are in the fastbootd mode .. the correct mode would be in the bootloader mode (adb reboot bootloader) ..
unfortunately it still does not work - the relevant command does not seem to work (fastboot oem get_unlock_data) -
motorola via support says it can not be unlocked .. but i certainly dont believe that - the e40 for example can be ..
the reteu firmware might be limited ..