So... I have been stuck with a HTC One E9+ for many months with a lock screen that I literally can't unlock, and flashed TWRP but can't be used because of locked bootloader, I had finally discovered a way to get the unlock token. Here's a little bit of story. I tried to run 'fastboot oem get_identifier_token' in bootloader mode, but the phone returned unknown command. I had tried that when everything was normal. I had check the settings in developer options, and there is nothing related to unlocking bootloader inside there. Until recently, I had discovered 'fastboot oem rebootRUU' from other blog post.
All in all, if you couldn't get the bootloader unlock token in bootloader mode, try to get it in RUU mode.
Good luck!
Hi, i tried to run the command "fastboot oem rebootRUU" but no code appeared.
My razer phone, after the OEM unlock, unlocked it using two-party commands, wrote it into the lineage OS system, and then, cheap, used "fast boot flashing lock_critical" FastBoot flashing lock " After locking the mobile phone, it was found that the "Developer Options" had changed to not allow OEM to unlock. Now the mobile phone is restarted indefinitely, using the "fast boot flash unlock" FastBoot flashing unlock_critical " It can't be unlocked. Unable to write to the official firmware, nor can it start properly! Help, gods! Help me!:crying::crying::crying:
Ive follow the unlock method on xda for unlocking realme x bootloader... but when i tried to flash the powerd shell comment "fastboot flashing unlock" command the phone get out form fastboot mode and says press any button to reboot and the powerdshell showing ""Comment writing failed"
but the indepth test showing application showing submitted successfully.....!!!!
my fon is 6/64 with chines rom RMX1901_11_A.21
Use cmd prompt instead of powershell. Try other bootloader unlocking commands, I don't remember which worked for me, Google search it
maybe use cmd amd don't forget to turn on "enable oem unlock" in the developer options
Hey new to android and looking for root my pixel 2 xl.
Following this guide https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Using windows 10, ADB and fastboot version 29.0.6-6198805, android version 8.0.0 security patch level Sept 5, 2017.
OEM unlocking and USB debugging checked.
Enter command "adb reboot bootloader" takes me into the bootloader screen.
Enter command "fastboot flashing unlock_critical" gives me error "FAILED (Write to device failed (Too many links))" "fastboot: error: Command failed"
Phone resets.
Have searched past threads suggesting to use different USB ports and cables. Tried several cables and every port with no luck. Any idea whats causing the error? Thanks
ente2323 said:
Hey new to android and looking for root my pixel 2 xl.
Following this guide https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Using windows 10, ADB and fastboot version 29.0.6-6198805, android version 8.0.0 security patch level Sept 5, 2017.
OEM unlocking and USB debugging checked.
Enter command "adb reboot bootloader" takes me into the bootloader screen.
Enter command "fastboot flashing unlock_critical" gives me error "FAILED (Write to device failed (Too many links))" "fastboot: error: Command failed"
Phone resets.
Have searched past threads suggesting to use different USB ports and cables. Tried several cables and every port with no luck. Any idea whats causing the error? Thanks
Click to expand...
Click to collapse
Did you try just
fastboot flashing unlock first?
Tulsadiver said:
Did you try just
fastboot flashing unlock first?
Click to expand...
Click to collapse
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
ente2323 said:
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
Click to expand...
Click to collapse
Maybe trying to update your firmware to something closer to current. You're about 3 years out of date....
ente2323 said:
Yes I tried commands "fastboot flashing unlock" as well as "fastboot flashing unlock_critical". Both commands give the exact same error.
The command "adb devices" does recognize that the phone is plugged in. Also the drivers are up to date.
Click to expand...
Click to collapse
Are you using Powershell or command prompt for your interface?
Badger50 said:
Are you using Powershell or command prompt for your interface?
Click to expand...
Click to collapse
I'm using command prompt.
Tulsadiver said:
Maybe trying to update your firmware to something closer to current. You're about 3 years out of date....
Click to expand...
Click to collapse
ente2323 said:
I'm using command prompt.
Click to expand...
Click to collapse
Then i would suggest that you update your firmware via OTA as Tulsadiver suggested. Then try your unlocking command "fastboot flashing unlock"
The critical one is no longer needed after the 9.0 update. Good luck. :good:
ente2323 said:
I'm using command prompt.
Click to expand...
Click to collapse
Do you see your serial number when you type:
fastboot devices
Badger50 said:
Then i would suggest that you update your firmware via OTA as Tulsadiver suggested. Then try your unlocking command "fastboot flashing unlock"
The critical one is no longer needed after the 9.0 update. Good luck. :good:
Click to expand...
Click to collapse
Thanks I will consider upgrading the firmware if there is no other solution. I am going to see if I can solve the problem on 8.0 for now.
Tulsadiver said:
Do you see your serial number when you type:
fastboot devices
Click to expand...
Click to collapse
Entering the command "fastboot devices" gives me nothing. When I try "adb devices" my serial number is displayed.
ente2323 said:
Thanks I will consider upgrading the firmware if there is no other solution. I am going to see if I can solve the problem on 8.0 for now.
Entering the command "fastboot devices" gives me nothing. When I try "adb devices" my serial number is displayed.
Click to expand...
Click to collapse
Are you in fastboot mode or bootloader mode when your typing "fastboot devices"???
Badger50 said:
Are you in fastboot mode or bootloader mode when your typing "fastboot devices"???
Click to expand...
Click to collapse
I'm not sure of the difference. The screen I attempt to unlock reads FastBoot Mode in red. Fastboot devices is now displaying my phones serial. Adb devices no longer displays serial.
I cannot remember if I had fastboot mode loaded earlier when I attempted the command "Fastboot devices". It is now displaying serial when enter the command while in fastboot mode.
ente2323 said:
I'm not sure of the difference. The screen I attempt to unlock reads FastBoot Mode in red. Fastboot devices is now displaying my phones serial. Adb devices no longer displays serial.
I cannot remember if I had fastboot mode loaded earlier when I attempted the command "Fastboot devices". It is now displaying serial when enter the command while in fastboot mode.
Click to expand...
Click to collapse
Fastboot mode, or bootloader mode as some call it, is when you enter it when the phone is shut off with the power + volume down buttons, or from ADB reboot bootloader when your phone is on. ADB devices will not work in fastboot/bootloader mode. Conversly speaking, fastboot devices will not work while your in your OS with the phone on. All your fastboot commands must be done from fastboot/bootloader mode. :good:
I'd try out the pixel all in one tool, it makes these things dummy proof. But really, take the OTA and get your phone updated first.
Hi everyone, I recently bought a 2xl pixel and it's updated to Android 10, and I want to change rom (basically why I like to see how much can be done)but I have the problem that it is Verizon version, I have tried to unlock it with the methods I have seen, but I have seen that it depends on the Android version.I would like to know if there is a way to unlock the OEM unlock in order to unlock the bootloader. My model is the Google Pixel 2XL 128GB. Thanks in advance
Joseft1 said:
Hi everyone, I recently bought a 2xl pixel and it's updated to Android 10, and I want to change rom (basically why I like to see how much can be done)but I have the problem that it is Verizon version, I have tried to unlock it with the methods I have seen, but I have seen that it depends on the Android version.I would like to know if there is a way to unlock the OEM unlock in order to unlock the bootloader. My model is the Google Pixel 2XL 128GB. Thanks in advance
Click to expand...
Click to collapse
Sorry to say, if your device is a Verizon carrier variant (not purchased directly from Google), then you will not be able to unlock the bootloader at this time (or likely ever)....
To be sure:
after enabling "Developer Options" if you can't enable the "OEM UNLOCKING" toggle, your bootloader is not unlockable.
So I'm using that app bugjaeger adb otg, I pretty much doing everything right, oem unlock enabled on target device, USB debugging enabled on both devices, reboot target device into bootloader, on host device I do "fastboot oem unlock" and then it tells me to enter command again and it says it goes to but it doesnt give me the popup window to actually unlock the boot
Did you follow the steps in Motorola website? Did you receive unlock code on email?
Can't you unlock with a computer?
You need to enter that unlock data on their website and if it works they should return an unlock code to your email which then you enter that code with the oem unlock command.
Here's an example of the final command:
"fastboot oem unlock 86yy8uufyuwhvr77836vvvj6e"
mrsiri said:
Did you follow the steps in Motorola website? Did you receive unlock code on email?
Can't you unlock with a computer?
You need to enter that unlock data on their website and if it works they should return an unlock code to your email which then you enter that code with the oem unlock command.
Here's an example of the final command:
"fastboot oem unlock 86yy8uufyuwhvr77836vvvj6e"
Click to expand...
Click to collapse
you know how to close the bootloader
dan12121z said:
you know how to close the bootloader
Click to expand...
Click to collapse
Yeah. you just press volume buttons till the start option appears.
Otherwise just inout this command "fastboot reboot". It should start booting your rom, if not then input this command first: "fastboot oem fb mode clear" and then "fastboot reboot".