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
Related
Hi guys,
I'm trying to unlock the bootloader on my H815. I can reboot the bootloader but when I try the "fastboot oem device-id" command I just get "<waiting for device>". After that I need to pull the battery to reboot.
Has anyone else had this problem, any idea how to get past it?
**Corrupt zip removed**
syztemlord said:
Hi guys,
I'm trying to unlock the bootloader on my H815. I can reboot the bootloader but when I try the "fastboot oem device-id" command I just get "<waiting for device>". After that I need to pull the battery to reboot.
Has anyone else had this problem, any idea how to get past it?
Click to expand...
Click to collapse
Download and install the ADB & fastboot setup file I have attached. Allow admin rights at prompt and enter Y twice when prompted for ADB and fastboot, allow install with system wide support; close command prompt.
Reopen command prompt and re run "fastboot oem device-id" command.
Loggsie
Hi,
Thanks for that. Could you re-upload the file though. Says zip is corrupt.
syztemlord said:
Hi,
Thanks for that. Could you re-upload the file though. Says zip is corrupt.
Click to expand...
Click to collapse
I'll remove the corrupt zip.
Try a download from Google, search for "adb-setup-1.3.zip" it should be the top link for Google Drive.
Loggsie
On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.
Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs
I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.
You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*
It work till fastboot. Still stuck at "waiting for device".
PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you
That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.
I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive:
I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything, I haven't even ever been to the home screen. What can I do to fix this?
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
https://developer.android.com/studio/run/win-usb
Get Android SDK Platform Tools for latest ADB and fastboot tool
https://developer.android.com/studio/releases/platform-tools
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
It says "Waiting for any device" the problem is that it's not recognized by the computer.
Thank you ! Same problem. This is halp! after first run, works. Question, can I block it now? and how please... fastboot flashashing lock ?
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
Hello. Same problem. ( I bought a refurbished Razer phone one from the official razer eBay page, and it's stuck on download mode. I haven't tried flashing anything). It helped me. Now I can block back? fastboot flashashing lock ? Please, sorry my english...
EDIT: The links did not copy paste appropriately. I fixed them now.
These are all posts from various places in this thread:
https://forums.redflagdeals.com/raz...b-1yr-warranty-8gb-64gb-octacore-9-0-2336958/
"Find the driver here:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
unzip the files/folder to a location you will remember
Follow the instructions below, point the windows driver update to the .inf file in that folder then driver will install. Make sure you have the latest Android platform tools, the link is also in the PDF below.
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
open a command prompt from within the Android sdk folder while the phone is still in download mode (phone stays and reboots to download mode through each process below making the process fairly easy)
type: fastboot devices
your phone should show up once drivers are installed correctly
type: fastboot flashing unlock
use the phone vol + - and power to select yes
phone should stay in download mode
type: fastboot flashing unlock_critical
use vol + - and power to select yes
phone should stay in download mode
Download the firmware image below or if you want to try the following command type: fastboot set_active a && fastboot reboot
to see if the phone boots, not sure if all the phones have Android installed. One poster below seems to and also seems to have his bootloader unlocked. This won't be the case for everyone. If phone does not boot continue downloading the firmware to install it
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-6033.zip
unzip all the files and put them in the android sdk folder, from the same command prompt if you're on Windows
type: flash_all.bat
For Mac type: flash_all.sh
Will take a few minutes but firmware will install. These instructions are for RFD members that do not either 1) want the hassle of RMA or 2) take a chance at voiding the warranty (any phone flashing via adb is frowned upon by Razer)"
------------------------------------------------------------
"Yes. Reverse the locking procedure. Put phone back into Download mode (from power off, press and hold Vol up and then plug phone into computer) then issue fastboot commands to lock boatloader starting with critical."
------------------------------------------------------------
"if you have a ryzen pc and getting some error while unlocking... dont plug the phone in at the beginning... type the command when it says [waiting for device] then plug it in ... also dont forget to unlock critical right after"
Now I can block back? fastboot flashashing lock ?
ShadowVlican said:
Get the Google USB Driver and make sure your Razer phone is installed with these drivers
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...
Click to expand...
Click to collapse
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
365Thanks said:
it helped, now it is loaded; but after each reboot it writes, the phone is unlocked and that it is unsafe. can it be blocked back, is it safe that everything continues to work? please write what commands to enter?
Click to expand...
Click to collapse
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Open command prompt to that folder and run these commands
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
from what i've gathered from other threads with similar problems, that's the jist of it...[/QUOTE]
flopticalcube said:
Repeat the unlock commands using lock instead of unlock but in reverse order so:
fastboot flashing lock_critical
fastboot flashing lock
again you must place the phone in download mode (powered off...hold volume down key down...plug in) between each command and follow the onscreen instructions.
Click to expand...
Click to collapse
after each command you need to disconnect from the computer? fastboot flashing unlock
fastboot flashing unlock_critical
fastboot set_active a
I used to enter these commands , the instructions were only after 1
I did not turn off the phone and the question on the screen was only after the first command. I probably entered only 1 command <if it was necessary to disconnect phone? ... thank you for help.
Sudo.
If ur using linux - run it with sudo. always run fastboot with sudo
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot set_active a
error: Device does not support slots
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.
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