Database Users

[HOW-TO]Unlock the Bootloader on the Nvidia Shield

Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.

I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1

themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.

fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.

gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.

ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148

gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.

chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.

shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post

chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!

shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.

I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs

thx. works nice.

wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks

wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!

why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..

so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.

mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk

BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.

Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.

Bootloader Unlocked

OK so I have an issue that I just cannot seem to fix. I've followed Max Lee's guide to unlocking the bootloader, obtaining root, and getting twrp. I've followed the written and video instructions to the t and a few guides in here, I have installed and updated the proper drivers and sdk tools, but my hitch is when I type the "fastboot oem Unlock" command, it says it finishes but my device doesn't reboot and ask if I want to proceed to unlock my bootloader, instead it just stays on the fastboot logo and does nothing until I restart it. This happens on both my mac and my pc so I'm not sure what the issue is I have usb debugging enabled and the allow oem Unlock slider is in the on position, any help or advice 8s greatly appreciated, thank you.
Sent from my ONE A2005 using Tapatalk

do you run an actual version of sdk-tools? fastboot recognized your phone, right? You can test it with following command: fastboot devices
Output is something like this:
33a0cde4 fastboot
Click to expand...
Click to collapse

nevermind i just fixed it, thanks

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

I want to know how to downgrade.

I am using Oreo.
But there are too many bugs.
So I want to downgrade.
I want to go back to 7.1.
I tried to find a way.
I do not really know.
Press Volume Down + Power to enter fast boot mode.
With ADB, if you use 'fastboot devices'
Nothing happens.
Developer option, OEM off, all done.
I want to know how to downgrade.

yuhanyanghaeng said:
I am using Oreo.
But there are too many bugs.
So I want to downgrade.
I want to go back to 7.1.
I tried to find a way.
I do not really know.
Press Volume Down + Power to enter fast boot mode.
With ADB, if you use 'fastboot devices'
Nothing happens.
Developer option, OEM off, all done.
I want to know how to downgrade.
Click to expand...
Click to collapse
Follow the instruction provided by Essential:
https://www.essential.com/developer/current-builds

Developer otpion and OEM unlocking are off? Why? That shouldnt be needed.
Download current build from link provide above ^^(current build)
extract the files to your "adb/fastboot/platform tools folder on pc"
connect the phone to computer using usb cable.
Open adb on computer
type adb reboot bootloader
when in bootloader verify fastboot works
"fastboot devices"
if your device shows up double click the flash all script for your OS.
Profit

Hi
By me the same.
When I Type adb reboot Bootloader the Phone starts new and boot up the system.
When I manually Boot into Bootloader the Phone were not found in Fastboot.
Developer option, OEMunlocking , all on.

samy1111 said:
Hi
By me the same.
When I Type adb reboot Bootloader the Phone starts new and boot up the system.
When I manually Boot into Bootloader the Phone were not found in Fastboot.
Developer option, OEMunlocking , all on.
Click to expand...
Click to collapse
I had the same problem. adb worked, fastboot did not. Installing the PH-1 drivers from the Essential support site fixed it.

Device Status "locked" in Fastboot even after OEM unlocking enabled

Just bought a used Pixel 4 to try and flash lineage 17.1 but can't get OEM unlocking to actually work. The enable switch is in the on position and adb recognizes the device but when I try to enter fastboot either by adb reboot bootloader or volume down + power on, the device status comes up in green text "locked." The phone is a G020I and came to me running android 11 with a build number RP1A.20005.004. Is this too new of a phone and wont be able to be flashed? From what I understand, if the bootloader stays locked, I can't even flash a factory image of android 10, correct?

You have to unlock bootloader using fastboot command from pc...

gpvecchi said:
You have to unlock bootloader using fastboot command from pc...
Click to expand...
Click to collapse
Fastboot commands wont work. adb commands will but as soon as I try adb reboot bootloader to get to the point where I can enter fastboot flashing unlock, I get the result in the pics below.

You need to install Google usb driver to use Fastboot

2WildFirE said:
You need to install Google usb driver to use Fastboot
Click to expand...
Click to collapse
Ok, in trying to do that, I get the message from windows that their driver is the most up to date and won't let me install from the file I try to choose. See the pics below.

I had the same issue, updating the USB drivers rc13 did the trick.

GTOJim said:
I had the same issue, updating the USB drivers rc13 did the trick.
Click to expand...
Click to collapse
LInk for that update?

Here you go: https://www.thecustomdroid.com/google-android-usb-drivers/

Finally got it. Windows had to recognize it as a generic device in order to force a driver. If it saw it as Pixel 4 it would stop. Now that I have lineage flashed on it, just need to figure out how to get mms to work. Apparently that is a common problem too.