Hello,
I have problem with my phone and adb, I have installed all driver for my htc, adb, fastboot,.. but when I try to check for connected devices in adb via adb devices command the list is empty even if windows recognize the device. I have tried it in Ubuntu, but the situation is same.
I don't know whats wrong, because it works for my Gnex and GTab.
Did you enable USB debugging on the phone
Sent from my HTC Desire using xda app-developers app
that was the first thing i made
well my phone is seen by adb when it's runing (in system) but it is not seen in fastboot mode
icefun said:
well my phone is seen by adb when it's runing (in system) but it is not seen in fastboot mode
Click to expand...
Click to collapse
...and it is perfectly OK.
The adb tool on your PC needs a adb daemon running on your device: this happens when the Android system is running (or a Recovery with adb daemon). When you are in fastboot mode the Android system has not really started loading yet, so there is no adb daemon to talk to your adb tool on PC -- hence your phone is 'not seen' by adb.
But it is seen by fastboot tool (another part of Android SDK tools) at this stage. So in fastboot mode you can flash images and do other stuff: just not with adb tool, but fastboot tool.
Well thx for eplaining my bad i thought that it will respond to adb devices like my other devices
PLS Close this thread
Related
Hey guys, I'm trying to get adb and fastboot working under Linux. I added udev rules for adb, fastboot and flashmode(idk if this one was really necessary). Adb and fastboot are already working with my other devices, but does not seem to recognize my Xperia Play, adb devices in terminal lists nothing, same thing with fastboot devices. I tried using flashtool, it says my device is connected using fastboot and when i try to flash lupus kernel flashtool shoots an error saying my device needs to be connected with fastboot.
My Xperia is running Ics/Paranoid 4.0.4 and debugging mode is turned on
What can possibly be wrong here? Any Ideas?
Check the drivers. It could be giving you those errors because of the drivers you're using. Try to update them.
I just accidentally wiped my SD card and my system and now I don't know how to get a rom onto my phone due to the lack of an SD card slot. Can anyone help me get a rom on the internal so I can flash? I have TWRP still but I have no clue how to get a rom to my sd card. Am I screwed? Cause I read a forum that had to have usb-debugging on and I have no system lol. Thank you guys so much
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
First use TWRP not fastboot. Once you are in recovery plug the phone in and type "adb devices" (without the quotes) in command prompt or terminal. If it returns with letters and numbers (can't remember might be a combination of both) your good to go. Type "adb push c:\downloads\Rom.zip /sdcard" type out the directory where the file is instead of downloads change it to where your rom is. If you type adb devices and nothing happens you need to work on your drivers.
jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
mickeyflip said:
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Cool story he's trying to use adb not fastboot two totally different things.
DR3W5K1 said:
Cool story he's trying to use adb not fastboot two totally different things.
Click to expand...
Click to collapse
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
mickeyflip said:
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
Click to expand...
Click to collapse
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
DR3W5K1 said:
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
Click to expand...
Click to collapse
No worries - it's possible that they do. But the drivers I linked are the ones that worked for me consistently. The Samsung ones seemed to stop working each time I disconnected the handset and plugged it back in via USB.
In any case, those are the only ones I have installed right now and everything is working great for me connection/recognition wise.
Any luck yet jtl_777?
To push files to the handset, use the command: adb push filename.ext destination-folder
Explained further here: http://developer.android.com/tools/help/adb.html#copyfiles
Just for future reference so people reading these threads don't get super confused, your computer won't recognize your phone through adb commands unless you are in adb sideload through your custom recovery, or if you're booted up and running in an operating system. You could also use adb push commands in your custom recovery. This has nothing to do with drivers or whatnot. If in bootloader your device isn't recognized through adb commands, that's completely normal, because it never would be, but your device should be recognized in bootloader with fastboot commands.
IF your phone is NOT recognized in your booted up phone, or in adb sideload through your custom recovery, or with adb push commands in your custom recovery, with adb commands, then you have driver issues.
ALSO IF your phone is NOT recognized while in bootloader, with fastboot commands, then you have driver issues.
To answer the OP's question:
If you have an unlocked bootloader and you are in TWRP, you can mount your phone onto your computer and copy and paste the rom zip onto the phone and then install it through TWRP once on the phone. If that doesn't work, then you can try using adb push commands while in TWRP (or maybe need to be in adb sideload through TWRP) to push the rom to your sd card and then run it through TWRP. If that doesn't work, you can also try flashing the rom zip through bootloader with fastboot commands, but all these commands might be device specific, that's why I won't tell you the commands I know for the HTC One X, but the processes are the same no matter what. Hope that helps
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Pirateghost said:
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Click to expand...
Click to collapse
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
EsoteRIcalfreaK said:
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
Click to expand...
Click to collapse
Adb shell as well as numerous other commands work just fine
Sent from my Nexus 5
I've installed ADB/Fastboot/USB Drivers from http://forum.xda-developers.com/showthread.php?t=2588979 (tried both 1.3 and 1.4.2 versions.
Booted my SW3 into Fastboot (whitescreen, with fastboot written on it) - attached to the PC, Device shows up as SAMSUNG Android Phone > Android ADB Interface
Ran CMD as an Administrator.
Typed, adb reboot bootloader.... Error: device '<null>' not found.
Typed adb devices... not listed.
Okay, so using a driver stripper (and windows program uninstaller), removed all Samsung phone USB drivers, KIES and existing ADB drivers. Re-ran the top tool to re-install everything. Repeated process, still showing up as SAMSUNG Android Phone > Android ADB Interface. Still not detected.
No idea at all what's going on here. I've tried cleaning the drivers multiple times. Other USB ports (2.0 & 3.0). Tried manually updating the driver to Google Inc. driver variants (9.0-11.0)
Really appreciate any help here.
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
woschirmer said:
if you're into bootloader you have to type fastboot devices , adb only works outside fastboot in system mode
Click to expand...
Click to collapse
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Sideburnt said:
Mind if I pick your brain on that point. I'm used to ADB on a smartphone, I really expected this to be similar but there's clearly some catches.
I don't think I'm into bootloader yet because the command 'adb reboot bootloader, or adb reboot-bootloader' doesn't do anything other than throw the error mentioned above.
However, typing fastboot devices gives me.
14442D38F870562 fastboot
But this doesn't allow me to process to run through the other ADB commands I need to complete. 'adb devices' still lists nothing.
In short, I'm trying to downgrade my SW3 to LCA32, as required to turn on the NFC functionality https://github.com/pimpimmi/LibreAlarm/wiki/How-to-install-NFC-on-Sony-Smartwatch-3
It's to assist in enhancing a medical device that uses NFC.
Click to expand...
Click to collapse
Okay progress, I see what you mean now adb reboot bootloader doesn't work. But fastboot reboot bootloader does. This is allowing me to move through the necessary TWRP and img steps. Thanks.
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
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: