I'm having issues unlocking my bootloader on my new Pixel 4XL after following the pretty cut and dry instructions. I turn on OEM unlocking to allow the bootloader to be unlocked. I turn on USB debugging. I type a command in the PowerShell of SDK tools ./adb reboot bootloader. It takes me to the fastboot screen of the Pixel. But from there nothing else works. I type ./fastboot devices or ./fastboot flashing unlock, which returns waiting for any device or it doesn't return anything. It just goes back to the original command prompt. Device status says Locked in green. So I'm not sure why it won't unlock. Anyone have any suggestions?
JimmyL216 said:
I'm having issues unlocking my bootloader on my new Pixel 4XL after following the pretty cut and dry instructions. I turn on OEM unlocking to allow the bootloader to be unlocked. I turn on USB debugging. I type a command in the PowerShell of SDK tools ./adb reboot bootloader. It takes me to the fastboot screen of the Pixel. But from there nothing else works. I type ./fastboot devices or ./fastboot flashing unlock, which returns waiting for any device or it doesn't return anything. It just goes back to the original command prompt. Device status says Locked in green. So I'm not sure why it won't unlock. Anyone have any suggestions?
Click to expand...
Click to collapse
Try using command prompt instead of PowerShell.
Try using a different cord.
Try using a different USB port.
Make sure your Platform Tools are up-to-date.
Make sure USB drivers are up-to-date.
fastboot flashing unlock should work
Related
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.
Hi Guys
I am unable to unlock my bootloader. I have downloaded adb and fastboot drivers. I connect device. run adb devices, device details are displayed. i then run command to reboot into the bootloader. it reboots into the bootloader. when i run fastboot unlock oem nothing happens.
I have enabled the developer options, USB debug, OEM unlock, Advanced reboot
is there something I am not doing right?
adb is working in your system but fastboot is not working.
Check your drivers properly, they are not installed properly.
search for how to install adb and fastboot drivers on windows. There is no problem in windows xp but in windows 10 as in my case, you need to activate the developer option in setting and manually install the drivers. Go to device manager and check if your device is showing as android device when you go to fastboot mode.
ismailf007 said:
Hi Guys
I am unable to unlock my bootloader. I have downloaded adb and fastboot drivers. I connect device. run adb devices, device details are displayed. i then run command to reboot into the bootloader. it reboots into the bootloader. when i run fastboot unlock oem nothing happens.
I have enabled the developer options, USB debug, OEM unlock, Advanced reboot
is there something I am not doing right?
Click to expand...
Click to collapse
Did you type fastboot devices?
It should show you that your phone is connected.
Then you can run the unlock command.
Sent from my OnePlus3T using XDA Labs
ismailf007 said:
Hi Guys
I am unable to unlock my bootloader. I have downloaded adb and fastboot drivers. I connect device. run adb devices, device details are displayed. i then run command to reboot into the bootloader. it reboots into the bootloader. when i run fastboot unlock oem nothing happens.
I have enabled the developer options, USB debug, OEM unlock, Advanced reboot
is there something I am not doing right?
Click to expand...
Click to collapse
the correct command is "fastboot oem unlock"
Hi Guys it was the fastboot drivers. After installing it correctly it worked 100%. Assistance is highly appreciated
I just received my 6 pro and want to prepare my 4xl to sell. I flashed the latest software and the phone is 100% stock now and the bootloader will not lock. In fastboot I get a serial number when I run "fastboot devices". My platform tools are up to date, usb debugging is on. When I run "fastboot flashing lock" I get a string of fastboot command options. Any iseads? I've never had this happen.
Thanks for anything
Figured it out. Sdk must have been outdated
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
DeeSkye said:
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
Click to expand...
Click to collapse
Did you find a way? I tried everything but I couldn't get into fastboot
No way to enter fastboot mode for oppo phones. Now I use Oppo A74 4G version. Cannot enter fastboot mode. It's locked by Oppo. And they don't give bootloader code for unlock BL. Only way is to change phone
I've been trying run fastboot too. 4 hours later I find this thread. That explains it
Last Oppo phone I buy I guess.
Did you manage to find a workaround for this by chance?
Has anyone tried rebooting from recovery to then enter fastboor or?
Im gonna look into myself soon...
Ive seen this issue before on a different phone but cant remember how they bypassed it
Perhaps yall can try to find a post where they did so.. maybe it'll work on this phone too.
I was able too get to fastboot mode. The phone labels it "recoveryd mode", however, fastboot commands work.
1st. Connect phone and confirm ADB is connected by using "ADB devices" command.
2nd. Enter "adb reboot fastboot bootloader"
Phone will reboot into "recoveryd mode". It looks exactly like the normal recovery mode except the title displayed after you select the language and fastboot commands will work.
However, I still have not found out how to unlock the bootloader, so it does me no good.
try doing adb reboot fastboot or adb reboot bootloader
fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
guys ,, fails
when trying to boot to fastboot and not fastbootd
Hi,
I just ordered a Pixel 5 on eBay, and it came with the bootloader unlocked. I would like to lock it again, but have been unsuccessful in my attempts so far.
I followed the guide on Nerds Chalk--
https://nerdschalk.com/pixel-xl-relock-bootloader/
I was able to connect the phone to the PC and boot the Pixel into bootloader mode using PowerShell.
But I tried the command 'fastboot oem lock', and the response was "Waiting for devices..."
Any help with troubleshooting this?
dylhill28 said:
Hi,
I just ordered a Pixel 5 on eBay, and it came with the bootloader unlocked. I would like to lock it again, but have been unsuccessful in my attempts so far.
I followed the guide on Nerds Chalk--
https://nerdschalk.com/pixel-xl-relock-bootloader/
I was able to connect the phone to the PC and boot the Pixel into bootloader mode using PowerShell.
But I tried the command 'fastboot oem lock', and the response was "Waiting for devices..."
Any help with troubleshooting this?
Click to expand...
Click to collapse
The correct command is fastboot flashing lock
If you're seeing Waiting for devices... this means that fastboot does not see the device, most likely because you don't have the correct drivers installed.