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.
Related
I'm trying to flash TWRP as a step to installing KitKat but I'm getting stuck booting into fastboot/bootloader trying to install the TWRP Recovery.
After I've installed the adb and fastboot files (15sec ADB Installer v1.3) I connect my tablet and open command in the directory folder and when I type "fastboot devices" all I get back is:
C:\adb
What am I doing wrong? I already have TWRP.blob inside the folder directory but I can't use fastboot to install it because it is not showing my device
I installed 15 seconds ADB Installer v1.3
I installed it on Win 7 64bit Lenovo G560 laptop
I unlocked the tablet myself using the Asus Unlock utility
I only have USB 2.0
I'm not sure if the tablet is in fastboot because I'm not cold starting it. I'm just connecting it to my PC and then opening a command window inside the adb files folder C:/adb
My tablet is running on Android JB 4.2.1 Build 10.6.1.14.10
I started the bootloader to get into fastboot and when it does I'm getting this message
"key driver not found...booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol"
as well as the three bootloader icons
What can I do now because typing "fastboot devices" is returning nothing and typing "fastboot continue" or "fastboot reboot" just brings up the message "< waiting for device > " but nothing happens beyond this.
vnomad said:
I'm trying to flash TWRP as a step to installing KitKat but I'm getting stuck booting into fastboot/bootloader trying to install the TWRP Recovery.
After I've installed the adb and fastboot files (15sec ADB Installer v1.3) I connect my tablet and open command in the directory folder and when I type "fastboot devices" all I get back is:
C:\adb
What am I doing wrong? I already have TWRP.blob inside the folder directory but I can't use fastboot to install it because it is not showing my device
I installed 15 seconds ADB Installer v1.3
I installed it on Win 7 64bit Lenovo G560 laptop
I unlocked the tablet myself using the Asus Unlock utility
I only have USB 2.0
I'm not sure if the tablet is in fastboot because I'm not cold starting it. I'm just connecting it to my PC and then opening a command window inside the adb files folder C:/adb
My tablet is running on Android JB 4.2.1 Build 10.6.1.14.10
I started the bootloader to get into fastboot and when it does I'm getting this message
"key driver not found...booting OS
Android cardhu-user bootloader (1.00 e) released by "WW_epad-10.6.1.14.10-20130801" A03
Starting Fastboot USB download protocol"
as well as the three bootloader icons
What can I do now because typing "fastboot devices" is returning nothing and typing "fastboot continue" or "fastboot reboot" just brings up the message "< waiting for device > " but nothing happens beyond this.
Click to expand...
Click to collapse
Open Device Manager on your PC. Near the top you should find an entry for a fastboot connected device (your tablet needs to be connected via USB in fastboot mode and yes, you are there when you see the three icons). If there's a yellow triangle next to it, you do not have the correct driver.
Try the ones from this post or try the tool, it's fastboot with training wheels
http://forum.xda-developers.com/showthread.php?t=2646279
If the driver checks out ok (no yellow triangle) you may have an incompatible USB cable. Is it the original charging cable?
berndblb said:
Open Device Manager on your PC. Near the top you should find an entry for a fastboot connected device (your tablet needs to be connected via USB in fastboot mode and yes, you are there when you see the three icons). If there's a yellow triangle next to it, you do not have the correct driver.
Try the ones from this post or try the tool, it's fastboot with training wheels
http://forum.xda-developers.com/showthread.php?t=2646279
If the driver checks out ok (no yellow triangle) you may have an incompatible USB cable. Is it the original charging cable?
Click to expand...
Click to collapse
In Device Manager the ASUS is no longer showing a yellow triangle and it appears to have the right drivers installed. The problem I'm having now is that when I uninstall the drivers for the Asus TF700 in Device Manager I reconnect the device and Windows (7) automatically installs the same drivers. I have even tried "Updating the Drivers" by navigating to the folder where I have (correct) Windows Drivers provided in thread above but I receive a message that device has the most up to date drivers (paraphrasing). I have also tried to do the same thing by navigating to a folder where I have Google Universal Drivers 0.73 installed but again I cannot seem to install them.
How can I override Windows from automatically installing the other drivers or is there a system folder I could send the correct drivers to when installing.
im trying to enter fastboot from bootloader but every time i select it, it just reloads the bootloader. everything else works fine.
the bootloader IS fastboot mode.
Well when I run fastboot protocol nothing happens
strker45 said:
Well when I run fastboot protocol nothing happens
Click to expand...
Click to collapse
Get into Bootloader. (I use ADB command: ADB Reboot Bootloader)
Use the volume down button to select "Fastboot Protocol."
It is deceptive as the screen on your Shield won't change.
Use your fastboot commands now. See if that works.
You need to make sure your fastboot and adb drivers are installed and recognized.
Also need fastboot on your pc of course. Good luck.
Once again, the bootloader is fastboot on your tablet, if you are on that screen then you can use fastboot if the above conditions are met.
Same symptom here.
When Android is loaded, Win10 finds it as both MTP and USB debugging device. adb is reporting back. All well.
However, when shield is in fastboot mode, fastboot finds nothing.
In my case reason was driver:
when connected in fastboot mode, win10 wants to install an
Android Device -Android Bootloader Interface
=> you see this in device manager
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Reconnect your shield.
In my case this worked.
Hope this helps
vrmuhr said:
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Click to expand...
Click to collapse
Thank you, worked very well for me.
Hi, i have tf101g b90 sbk2,
went into soft brick because I installed first CWM recovery and then TWRP not corrected. The shell must be reinstalled. adb works well and read the device with your correct serial number. . The problem is fastboot, i write fastboot device in prompt and I see nothing. When I give a command, I read 'waiting for any device. I think . I think the drivers are installed well with nacked drivers,
when it is in adb mode i have installed driver asus transformer adb interface, when in fastboot mode i have installed driver asus fastboot interface. To go to fastboot mode I press both volume buttons and the serial number of device becomes 1111111111111111111, thinking that this is the correct serial for fastboot mode. At this point I think the problems are: either I need the root (which I can not do), or the drivers are installed badly (even if I do not think), or I do not go correctly in fastboot mode. The strange thing is that in adb I go well but in fastboot no. In the end I would like to run the fastboot flashall command. Thank you
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
J0hncramer said:
Hey there masterfully smart megabrains of the XDA world, I've gotten myself into a bit of a pickle. I accidentally chose the OTA option from Magisk when I hadnt just installed an OTA update. Now my phone when i restart it it just sits spinning the Oneplus logo.
I do have access to Fastboot.
I do have access to Recovery.
I only have stock Recovery, no TWRP installed.
I did not have USB debugging enabled before this issue happened.
ADB is installed and I have my drivers installed, but when I use powershell to enter the command adb devices my device isnt listed when I have the phone connected via USB and in Fastboot mode. When I check device manager Android Device is just listed rather than the device name, so I'm not sure what else I can do to get my device to be recognized correctly. I feel like if i could just get ADB to recognize my device, i could fastboot flash the stock rom. Or if there is a way to swap to the other boot slot I think that would also save me. I've been trying to google and search around but I'm having trouble finding the answers I seek, so please megabrains, save me!
Click to expand...
Click to collapse
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
LokifiedMee said:
You shouldn't type adb devices in fastboot mode. It won't show. Instead type (fastboot devices).
Click to expand...
Click to collapse
I just tried fastboot devices in powershell while the phone is connected via USB in fastboot mode and nothing was listed
Edit: i was able to get fastboot to work, I had to do the following steps i found on stack exchange to get my device to show up properly in device manager:
https://stackoverflow.com/questions/8588595/android-fastboot-devices-not-returning-device
Open device manager
Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
Update driver
Browse my computer for driver software
Let me pick from a list of devices, select List All Devices
Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
Choose "Android Bootloader Interface"
Click "yes" when it says that driver might not be compatible
Click to expand...
Click to collapse
With fastboot working and issues in device manager solved I was able to get TWRP loaded to my phone via fastboot and change my boot slot to get back into the phone
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.