Hi, I searched for an answer but I didn't find it, so I created this thread.
My Z00A is running on the latest official OTA version perfectly fine. It is unlocked but bricked once and I successfully unbricked it.
I installed Intel Android driver and adb on windows 10.
Booted in Android, adb sees my device when I enter "adb devices".
In the bootloader, when I enter "fastboot devices", fastboot leaves a bank space and open a new command line and if I enter any other command it says < waiting for device >.
It looks like Windows 10 didn't let the driver work properly. I downloaded the drivers from ASUS and manually installed the bootloader interface driver via legacy wizard. Then, I uninstalled the old one and now fastboot is functional.
Related
Hi,
I realize a lot of people might have the same problem as I have, but haven't found the answer after searching for many hours. So here's my problem:
windows vista x64
installed android SDK and all related drivers
GN is recognized with correct driver in both fastboot mode and regular "on" mode.
GN is recognized as a device in regular on-mode with 'adb devices'
GN is recognized as a device in fastboot mode with 'fastboot-windows devices'
HOWEVER, when GN is put into fastboot mode, NO devices are found with 'adb devices' even though the icon for 'safely removing hardware' pops up with 'Android ADB Interface', which means the driver is correctly installed.
Someone please help explain why the device is not recognized by 'adb devices' command under fastboot mode even though it's recognized by the computer!
Summary:
GN is found with 'adb devices' for normal boot, but GN is not found under 'adb devices' for fastboot mode. I have reinstalled the android ADB driver, but still the same problem.
I am stressed out! Please help me
I have noticed exactly what you are talking about however what I have found is that it doesn't seem to need to be able to respond to the adb devices command. I was still able to unlock,root and flash multiple different boot.img and radio.img files through fastboot without the computer returning the device while in fastboot. Hope this helps.
Justin
P.S. while you are in fastboot mode it seems you may be looking for something different than standard adb commands. Fastboot is primarily used in this situation so a command for you will typically look something like this"
fastboot-windows flash boot boot.img
or
fastboot-windows flash radio radio.img (the radio.img and boot.img files used in these examples you would want located in the same folder as fastboot-windows)
if you want to try the software out without flashing it "permanently" try:
fastboot-windows radio radio.img (just forget the flash portion)
for unlocking the bootloader the command will look something like this:
fastboot-windows oem unlock
ADB isn't used in fastboot mode, fastboot.exe is.
ADB is for when the phone is running Android or recovery only.
Phone doesn't recognize ADB in fastboot
Phone doesn't recognize ADB in fastboot - have used every conceivable method - downloaded Samsung drivers. Downloaded PDANet. Uninstalled Samsung and tried Naked Samsung. I got the phone unlocked. But I CANNOT get the PC 64 to recognize ADB when I am in fastboot. HELPPPPPPP. I've been working on this for TWO DAYS, and it is RUINING my Christmas holiday.
Have you tried the driver installation/troubleshooting section of this post?
Unfortunately, yes. I tried the Samsung drivers. Then I tried the PDANet. I also tried the Samsung naked drivers. I was sure that MSKIPS toolkit was going to work, but when I typed in "2" for rooting, NOTHING happened. I'm at my wits end.
HeathCliffR said:
Phone doesn't recognize ADB in fastboot - have used every conceivable method - downloaded Samsung drivers. Downloaded PDANet. Uninstalled Samsung and tried Naked Samsung. I got the phone unlocked. But I CANNOT get the PC 64 to recognize ADB when I am in fastboot. HELPPPPPPP. I've been working on this for TWO DAYS, and it is RUINING my Christmas holiday.
Click to expand...
Click to collapse
Of course it doesn't.
AS STATED MULTIPLE TIMES IN THIS THREAD, YOU MUST USE FASTBOOT.EXE.
Please, read thread then reply.
When phone is turned ON - use adb
When in FASTBOOT mode - use (surprise surprise) fastboot
When phone is turned on or in recovery - use adb (check it with "adb devices" ,without " in cmd)
When in FASTBOOT mode - use fastboot (check it with "fastboot devices" ,without " in cmd)
In order to work fastboot you must have the fastboot.exe preferably in the same folder with adb
Try this
I tried installing PDAnet but no Joy.. but went to device manager and selected adb drivers and samsung from the list and that did the trick...
so I'm trying to fastboot flash TWRP. That way I can root it after the custom recovery is set up.
My HTC is S-OFF, I installed android studio for the adb fastboot command prompt. Then installed all HTC drivers. I then plugged in my HTC into my pc which is running windows 10 via USB port which are 3.0
I opened up the folder where the fastboot was installed when I downloaded android studio. Then I pushed shift and right clicked and chose open command promp. I then typed: adb devices
The command prompt runs and it shows my HTC in the device list. Then I typed: adb reboot bootloader. It boots to the fastboot.
And so here is my problem........... once I boots to fastboot I thenjoy again type: adb devices. Cmd runs and the device list is blank. I checked my drivers and device in device manager and everything is fine. Even I'm fastboot it reads the drivers no problem.
I've tried everything. I've read to try reinstalling the drivers, try installing universal drivers, try different USB cables, try different USB ports that arent 3.0 port, I even tried a different adb fastboot software and still came up with the same outcome. I've read a bunch of different threads and just can't find anything. I am just stuck I don't know what to do. And am asking for help please. I would really appreciate the help and guidance. Because....... this s**t is driving me crazy haha. I've rooted galaxies and have my s5 on lollipop rooted. But
I'm still a noob and especially with HTC. So please some one lend me a helping head I am at a complete loss.
Whisperz6662 said:
so I'm trying to fastboot flash TWRP. That way I can root it after the custom recovery is set up.
My HTC is S-OFF, I installed android studio for the adb fastboot command prompt. Then installed all HTC drivers. I then plugged in my HTC into my pc which is running windows 10 via USB port which are 3.0
I opened up the folder where the fastboot was installed when I downloaded android studio. Then I pushed shift and right clicked and chose open command promp. I then typed: adb devices
The command prompt runs and it shows my HTC in the device list. Then I typed: adb reboot bootloader. It boots to the fastboot.
And so here is my problem........... once I boots to fastboot I thenjoy again type: adb devices. Cmd runs and the device list is blank. I checked my drivers and device in device manager and everything is fine. Even I'm fastboot it reads the drivers no problem.
I've tried everything. I've read to try reinstalling the drivers, try installing universal drivers, try different USB cables, try different USB ports that arent 3.0 port, I even tried a different adb fastboot software and still came up with the same outcome. I've read a bunch of different threads and just can't find anything. I am just stuck I don't know what to do. And am asking for help please. I would really appreciate the help and guidance. Because....... this s**t is driving me crazy haha. I've rooted galaxies and have my s5 on lollipop rooted. But
I'm still a noob and especially with HTC. So please some one lend me a helping head I am at a complete loss.
Click to expand...
Click to collapse
You're using the wrong command.
You can't use adb commands when booted to bootloader, only while booted to system, as you did the first time.
Once you do adb reboot bootloader use fastboot devices and your phone will show in cmd. You need to use fastboot commands while booted to bootloader.
xunholyx said:
You're using the wrong command.
You can't use adb commands when booted to bootloader, only while booted to system, as you did the first time.
Once you do adb reboot bootloader use fastboot devices and your phone will show in cmd. You need to use fastboot commands while booted to bootloader.
Click to expand...
Click to collapse
Wow that was so simple...... (face palm)
You are a saint haha. Thank you very much that was getting to me. It did show up was able to flash twrp.
No where did I see anything about typing fastboot in cmd instead of adb while phone was in fastboot. Well it might of and I might of just not of understood it when I read it. Again thank you I appreciate it
hello all,
I am trying to install android 2.0 preview. I installed android studio and I am able to get device listed using "adb devices" command.
I am able to enter boot loader using "adb reboot-bootloader" as well.
but in boot loader when I try to run fastboot oem then it says "waiting for an device".
also "fastboot devices" does not return anything.
E:\Android\sdk\platform-tools>fastboot oem unlock
< waiting for any device >
I can see "Kedacom USB device" is installed while in bootloader mode. can anyone help me? thanks
I am using windows 10
Same here, not detected by '
Code:
adb devices
' or '
Code:
fastboot devices
'. Windroid toolkit stuck at "rebooting device" while it is in Fastboot mode, and if you reboot it manually, it gets stuck at "unlocking device". Drivers are installed, maybe not properly?not properly?
adb devices works for my case after downloading latest sdk. but fastboot is no go.
windows xp ???
Sorry forgot to add that details - windows 10
Have you found a way to resolve this?
A little background info...
I bought a used Nexus 5x and received it running the stock rom with the bootloader unlocked. Not sure if the device was properly unrooted and returned to stock. It was running 7.1.2 out of the box. Also, I took the latest security update a few days ago, before attempting to root. I wanted to do some homework on the device before attempting root. It's been a while since I rooted a device. And wanted to refresh my memory.
When I began the process, I was having trouble getting my windows 7 PC (64) to recognize the device via adb. I did a little reading and found out my driver's needed to be updated. After I updated them the device could now be recognized in adb (yes, I did remember to enable USB debugging). Verified working by returning serial number after typing the adb devices command. So I was confident I could no proceed with flashing TWRP via fastboot.
The problem...
So now that I verified adb working and talking to my device I then typed adb reboot bootloader to access the bootloader (cause I honestly didn't want to disconnect the device and have to press buttons). The device successfully booted into the bootloader. My next step was to type fastboot devices in the command line but this is where the problem I'm having is. The device is not recognized. So I unplugged the device from the PC, opened a new command window in the platform-tools folder where fastboot resides, rebooted the device back into the bootloader, reconnected the device to the PC and attempted the fastboot devices command again and nothing, no device. I execute the command fastboot flash recovery TWRP.xx.xxxx.img and the command window says waiting for device or something like that. I am not sure what steps to take next. I've never had a problem getting a PC to recognize a device in bootloader mode before. I am pretty sure my environments are set up correctly. Is it something with the device? Is there a way to correct this? I'm really lost as to what to do here. I cannot root because I cannot flash custom recovery because I cannot get my PC to recognize the device in fastboot. Please, any help is appreciated. I'm stumped.
Update.
Resolved. Used a different pc with a fresh adb environment. Worked on the first try to flash twrp and super su.
ADB command not recognized
Hi there, i'm facing a similar problem. My 5x went into bootloop. It was on stock. After going through XDA posts, I was preparing to flash stock rom once again to see if that works. So I installed in my Windows 10 - SDK tools / platform. We I used command for ADB the command prompt say device listed, but does not come up with serial number. But when fastboot command is given, it returns with a serial number.
My question is what went wrong? My PC also dose not shows 5x in the explorer, despite installing drivers.
I would also like to know how to enable USB debugging when your phone is bricked?
Looking forward to any suggestions.....thanks upfront....
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: