Hi guys,
Looking for a genuis here...I've spent the last few days trying to work this puzzle out:
Installing GrapheneOS onto Pixel 3 phone using Windows 10, using command line tools only. Android Studio is not installed on the PC.
Here's what I've done so far...downloaded:
The Pixel image - GrapheneOS stable channel for Pixel 3
ADB & fastboot
First we downloaded fastboot (ADB, Android SDK platform-tools for Windows): https://developer.android.com/studio/releases/platform-tools - had an issue with the fastboot flashing unlock command...it doesnt unlock the device, instead says <waiting for any device>
Then we deleted the SDK platform tool and installed Minimal ADB & Fastboot and the same darn issue happened - the fastboot flashing unlock command doesnt unlock the device... command prompt says <waiting for any device>
The device is carrier unlocked, OEM unlocking enabled, USB debugging enabled, File transfer (MTP) mode on.
The following commands work with the SDK platform-tools & minimal ADB & Fastboot: adb devices, adb reboot bootloader
The block is the command: fastboot flashing unlock as we keep getting <waiting for device>.
Tried to fix this myself, here's what has been tried so far (not necessarily in this order):
Checked Fastboot version... fastboot --version works for both downloads so it's recognising it! Wahoo.
Used command prompt & powershell - when it gets to the fastboot flashing unlock command the response is always <waiting for device>
Checked the PATH (in control panel / advanced setting) and made sure environmental variable goes to the right folder
Downloaded Google USB Driver - nothing changed, we already had up-to-date drivers
Tried to change the fastboot script, click to open the fastboot file, when I click "open" the command prompt pops up, red error message flashes then the command prompt window closes in the blink of an eye. I then turned off Windows secuirty setting for app, same thing still happens.
Tried all USB ports with USB-C cable - same error <waiting for device>
Tried all USB ports with anotehr USB-C cable - same error <waiting for device>
Please help!
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
jwoegerbauer said:
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
Click to expand...
Click to collapse
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Redsquirrel77 said:
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Click to expand...
Click to collapse
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
jwoegerbauer said:
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
Click to expand...
Click to collapse
Thanks so much, I think we are getting closer to success!
Qualcomm USB driver downloaded and successfully installed.
Update since the Qualcomm USB driver download:
adb reboot bootloader command works - phone goes into fastboot mode
fastboot devices - no response (new command line)
fastboot - -version shows version and installation
fastboot flashing unlock response is still <waiting for any device>
Used command adb shell getprop ro.boot.cid and response is 00000000
Response should be 11111111 if it's a Google phone...is this my issue? Or does it help explain why fastboot isn't working?
Fastboot operates on device's bootloader only if unlocking bootloader isn't denied. Makes sense,, doesn't it?
Me and all my friends always test this by running
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported" <- on some devices: adb shell "getprop sys.oem_unlock_allowed"
If returned value is 1 - or true, then it's supported otherwise it's not.
Hi,
I don't know if it will help but try this.
PROBLEM
I tried all manner of ADB drivers and fastboot drivers for the last 4 hours just so that I am able to oem unlock this OnePlus device.
I have all OnePlus drivers installed. I have the ADB drivers installed from here. With all these I was able to run adb commands on the phone when it was on including commanding the phone to enter into EDL mode, commanding the phone to reboot into bootloader (fastboot mode). However in once in Fastboot mode, I could not communicate with phone and all I got was "waiting for device".
SOLUTION THAT WORKED FOR ME
It could be a computer brand model. Turns out the problem was not Windows. The problem was not Oneplus. The problem was my Lenovo Thinkpad which apparently requires its own Lenovo USB drivers.
If at all you're on Lenovo machine and you're stuck on "waiting for device" in Fastboot mode despite trying everything, then try installing Lenovo USB Drivers. I would recommend installing the generic ADB drivers first from here. Then installing the Lenovo drivers that are specific to you machine from here. Mine is Thinkpad.
I really hope this helps if not you, then someone else just about to pull their hair out.
Related
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
Use "fastboot" to connect to phone booted into HBOOT
When your phone is in HBOOT then it only accepts commands from the application "fastboot".
It also handles fastboot commands different depending if you are in Fastboot or Bootloader mode.
Search XDA for fastboot for your operating system.
A Windows system might recognize your phone as"adb device" as fastboot uses the same drivers as adb. However, your phone has another USB id and so the command adb will not find it.
Best regards,
Catherall
When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.
I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.
Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.
Hey guys, as stated in the title i am unable to unlock my bootloader. The adb devices works up to the point where i boot into fastboot or recovery then it stops working. If i use the command it just says "waiting for any device" I want to install TWRP and change to LineageOS but the bootloader is bottlenecking me hard... any tips would be much appreciated!
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
jwoegerbauer said:
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
Click to expand...
Click to collapse
Thank you for your response, found the problem. It was the Qualcom drivers not being signed so after i put test mode on on PC it worked. Thanks for the advice!
Hey! I need help, please. I'm trying to unlock bootloader of the Moto C XT1756, it has a MT6735. So, I tried in Windows and in Linux (linux with 2 pc). And the problem is next.
I installed ADB and Fastboot (I tried minimal, 15 seconds, platfoorm tools, all). So, ADB detects the device, I can use any adb command like the "adb reboot bootloader". It reboot in fastboot mode and if I use "fastboot devices" it is detected. But when i'm trying to use "fastboot oem get_unlock_data" it says me "failed, unknown command." It happen also with any oem command. I don't know how to proceed. If someone can help me, i'll be grateful. Thanks for read
Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.
Oh. So, I'll test your ADB-FASTBOOT installer, really thanks!
Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.
jwoegerbauer said:
Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.
Click to expand...
Click to collapse
Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.
I see you didn't get it.
Manufacturers implement ADB and/or Fastboot with version what corresponds to their ideas.
Hence in your case some ADB and/or Fastboot commands may work or not.
Oh. So, this phone can't be unlocked?
Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"
jwoegerbauer said:
Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"
Click to expand...
Click to collapse
I didn't get the second sentence. "Use Motorola's "Android USB Driver". Btw, I used "mfastboot.exe devices" and it recognizes my phone, then "mfastboot.exe oem get_unlock_data" and it keeps saying "failed: unknown command."
Update: I tried three different wires. Three different PC (Including Linux-PC) and the error is the same. I can't understand it. It have an option "Unlock OEM" in Developer Settings (so, I think that the manufacturer allows unlock) I can't do nothing.
Using Samsung Android 11 default ROM - nothing modified. I'm trying to boot custom recovery (twrp) temporarily from PC console.
What I did to set up adb and fastboot:
OEM unlocked, usb debugging active, not rooted.
I installed latest ADB and Fastboot. Also installed Samsung USB drivers. Samsung doesn't provide fastboot drivers, and I've read on some thread that AOSP drivers are used for that. So, I'm using Google's Bootloader Interface installed via Device Manager, because plenty of guides suggest that online.
Problem:
I can use adb when phone's on. But when it comes to fastboot, I can get into it by 'adb reboot bootloader' and, i can see the device is listed using 'fastboot devices', but i can't really do anything at all other than that command.
I tried 'fastboot oem device-info', 'fastboot boot twrp.img'. I don't get any error messages. When I execute a command, the command just stays there on the terminal like it is busy executing. Waiting for over 15 minutes and there's no change.
Ex: When I executed the boot command, the console output was stuck at 'Sending boot.img', without any progress.
Additional info:
I've got Ryzen CPU, and I applied some USB fix bat to change some registry entries. No change.
All my ports are USB 3 and I'm on Win 10, and I've seen threads where they say USB 2 is preferable.
TLDR: Seemingly nothing's wrong, except no fastboot command really seems to be executing other than the one to list connected devices.
AFAIK Samsung does not know a Fastboot mode, but there is the so-called Odin/Download mode besides the Recovery mode.