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.
Related
When going through the adb commands and i type in fastboot oem unlock the command window says waiting for device but on the device nothing at all happens. Ive tried doing it in mtp and ptp modes but still nothing happens. device has never been rooted or unlocked before. On marshmallow and latest june security patch, please help
Wetbreadguy said:
tried doing it in mtp and ptp modes
Click to expand...
Click to collapse
It can only work in fastboot mode (when off press power+vol.dn).
The fastboot devices command must return your N7's serial number. If not, run it as root/admin and/or install a new driver and fastboot app or use NRT.
k23m said:
It can only work in fastboot mode (when off press power+vol.dn).
The fastboot devices command must return your N7's serial number. If not, run it as root/admin and/or install a new driver and fastboot app or use NRT.
Click to expand...
Click to collapse
I do have it in fastboot mode when i run the commands, i just originally set it in mtp or ptp modes.
Hi,
I'm new here so forgive me if I've posted this incorrectly.
I am trying to follow the rooting guides for the Pixel 6. I've rooted many phones before and been fine with unlocking bootloaders but the Pixel 6 is giving me some grief.
I have enabled developer options > OEM unlocking.
I have rebooted to bootloader and I am connected to the device.
I have verified I can see the device through `fastboot devices`.
I have updated my platform tools to 31.0.3.
Whenever I run `fastboot flashing unlock` I simply get the fastboot help/options outputted to the console and nothing happens on the device.
If I run `fastboot oem unlock` the command fails saying it's an invalid command (as expected).
Has anybody encountered this when unlocking their bootloader? Any advice here greatly appreciated.
Thanks,
Scott
nevermind misread
If you're on Windows, are you using PowerShell by accident? Use the Command Prompt instead.
Is USB debugging turned on? I think it must be if it is detecting your device but I can't remember for sure if it will detect device without it being on.
scojac said:
Hi,
I'm new here so forgive me if I've posted this incorrectly.
I am trying to follow the rooting guides for the Pixel 6. I've rooted many phones before and been fine with unlocking bootloaders but the Pixel 6 is giving me some grief.
I have enabled developer options > OEM unlocking.
I have rebooted to bootloader and I am connected to the device.
I have verified I can see the device through `fastboot devices`.
I have updated my platform tools to 31.0.3.
Whenever I run `fastboot flashing unlock` I simply get the fastboot help/options outputted to the console and nothing happens on the device.
If I run `fastboot oem unlock` the command fails saying it's an invalid command (as expected).
Has anybody encountered this when unlocking their bootloader? Any advice here greatly appreciated.
Thanks,
Scott
Click to expand...
Click to collapse
If you are using powershell on windows you have to type ./fastboot flashing unlock
freebee269 said:
If you are using powershell on windows you have to type ./fastboot flashing unlock
Click to expand...
Click to collapse
Well I'll be damned. This worked. Thanks man.
scojac said:
Well I'll be damned. This worked. Thanks man.
Click to expand...
Click to collapse
You're welcome! Glad it was simple. I haven't investigated but some executable commands seem to work fine in PowerShell and others don't. I'm guessing there's a potential security issue with commands compiled to work specifically with Command Prompt since PowerShell is newer and likely Microsoft considers it more secure.
freebee269 said:
If you are using powershell on windows you have to type ./fastboot flashing unlock
Click to expand...
Click to collapse
Ah, thank you! Now let's see if I remember that in the future.
Good story with happy ending! Cheers to all above!
I'm attempting to follow this guide here https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/ and I'm finding myself having issues at step #5. ADB picks up my device while it's on no issue but when I reboot into bootloader, it no longer picks up my device to get the unlock code.
Anyone know what the issue could be? Any help is appreciated.
Edit: when I use the command "fastboot oem get_unloock_code" the CMD window says "Waiting for any device"
You don't have fastboot drivers.
craznazn said:
You don't have fastboot drivers.
Click to expand...
Click to collapse
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
MushroomElm said:
I installed ADB and Fastboot through this, does it not include Fastboot? When I open CMD in the install folder and use "fastboot --version" I get " eac51f2bb6a8-android " https://developer.android.com/studio/releases/platform-tools
Edit: Believe I've got it now..Had to go to Windows 10 optional Updates and select Google Bootlader Interface. After that, I was able to get my unlock code.
Click to expand...
Click to collapse
Glad you figured it out
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
check if you have the last fastboot version - platform-tools_r33.0.1
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Have you checked Device Manager to see if there's any unknown devices?
bengoodall.raw said:
Hey! I'm currently trying to flash a custom rom on my 9 pro from 11.2.10.10 and i've unlocked the bootloader. ADB commans are working fine, but as soon as I boot into the bootloader and type "fastboot flash boot "recovery.img"" it just doesn't do anything, no "downloading..." text or anything. I then tried to use any other fastboot commands and nothing works, (to be clear, my device is being recognized, "fastboot devices" does show my device. but no other command works, either doesn't do anything, or gives me an error.
any help would be much appreciated
Click to expand...
Click to collapse
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
CZ Eddie said:
Assuming you're using the latest adb & fastboot versions, what happens when you type "fastboot devices"? Does it show your device?
Click to expand...
Click to collapse
Yep, shows my device
Sometimes it does but when I unplug then replug it shows adb bootloader interface
razercortex said:
Have you checked Device Manager to see if there's any unknown devices?
Click to expand...
Click to collapse
Yep I have the latest version
GabrielSousa said:
check if you have the last fastboot version - platform-tools_r33.0.1
Click to expand...
Click to collapse
bengoodall.raw said:
Yep, shows my device
Click to expand...
Click to collapse
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
bengoodall.raw said:
Yep I have the latest version
Click to expand...
Click to collapse
Try running those commands on another PC and let us know if it works.
CZ Eddie said:
Does it work with ANY fastboot commands at all?
Such as "fastboot reboot"?
Click to expand...
Click to collapse
Nope, that doesn't work either
Didn't work either 🫤
razercortex said:
Try running those commands on another PC and let us know if it works.
Click to expand...
Click to collapse
bengoodall.raw said:
gives me an error.
Click to expand...
Click to collapse
Screenshot of the error?
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
GloriamSemper said:
I had similar issues and found out it was because I was executing the commands in the bootloader instead of fastbootd mode. Try running them in fastbootd mode instead?
Click to expand...
Click to collapse
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
I'm kind of curious how unlocking the bootloader worked but using other commands doesn't.
ekin_strops said:
Ermm, you're SUPPOSED to run the commands in "bootloader" mode, not fastbootD mode.
Click to expand...
Click to collapse
I know wierd, right? None the less, certain fastboot commands were only successful for my 2127 in fastbootd
hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.
"fastboot set_active other" to switch slot
I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.
HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?
kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)
ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files
Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?
cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done