Database Info

[Q] Error Device not found while using ADB.

Trying to use adb to root my phone that is on 1.85.
I start up adb just fine but when I try to do anything else I get Error device not found. Here are all the things I've tried and noticed.
1. I tried using the commands "adb kill-server" and then "adb start-server" to no avail.
2. I tried uninstalling then restarting the google usb drivers to no avail.
3. Under device manager the phone isn't recognized as a debugging device.
Any ideas what I should next? I feel like I have tried everything. I had no problems using it with my GS2.

I had an issue last night with it not recognizing my phone from the start. I had to install the HTC Sync software and it updated the drivers. After that, it recognized my phone... well, it did when I finally check debugging mode.
You can also kill adb by going into task manager and killing it, then cmd back into your adb folder and and run "adb shell" to restart it and it then should recognize your device.

Red5 said:
I had an issue last night with it not recognizing my phone from the start. I had to install the HTC Sync software and it updated the drivers. After that, it recognized my phone... well, it did when I finally check debugging mode.
You can also kill adb by going into task manager and killing it, then cmd back into your adb folder and and run "adb shell" to restart it and it then should recognize your device.
Click to expand...
Click to collapse
I tired the latter and that didn't work either.
I'll install the HTC Sync software and report back.

I would download the official HTC drivers for the phone start there.
Cant post outside links yet but ya goto the htc website.
Then make sure you kill the HTC in your taskbar. Or you will get a different error if two ADB's are running.

Red5 said:
I had an issue last night with it not recognizing my phone from the start. I had to install the HTC Sync software and it updated the drivers. After that, it recognized my phone... well, it did when I finally check debugging mode.
You can also kill adb by going into task manager and killing it, then cmd back into your adb folder and and run "adb shell" to restart it and it then should recognize your device.
Click to expand...
Click to collapse
Installing the htc sync software then restarting the computer worked.
Did a adb devices command and it showed up.
Thanks.
Now on to rooting 1.85 (which apparently is a doozy)

Struggled w/ same issue last night using Windows 7. Tried everything, reinstalling drivers etc. Drove me nuts for about an hour & 1/2. Woke up this morning to find this tool. Was unlocked in 10 minutes.
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Sent from my HTC One X using xda premium

doin-it said:
Struggled w/ same issue last night using Windows 7. Tried everything, reinstalling drivers etc. Drove me nuts for about an hour & 1/2. Woke up this morning to find this tool. Was unlocked in 10 minutes.
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
He's on 1.85 which is not rooted yet (well it can be which is what hes trying to do now). That unlock tool wont work for him because hes not rooted.

Adb help needed.

I have a pc setup for andriod. I have used this pc several times with no problems.
4 or 5 days ago I flashed the latest twrp recovery all went well.
Yesterday I tried to dump my apks, nothing I tried worked. Adb devices showed nothing. I googled till I wore the paint from the keys and still nothing. Ive searched the threads and nothing seems to help. I have xp, win7, win8, laptops, desktops....nothing sees the phone.
Any ideas? I assume its a ms update or net framework issue but honestly Im frustrated to the point I want to smash something, hard to think clearly when Im so agitated.
Everything worked just fine the only changes are latest twrp and testing a new rom but I cant see the rom being the problem, pc wise just some ms updates for security and virus definitions.
Beer money or hookers if you can help

I hate to do this but is USB debugging on?
Sent from my HTC One X

Also, check the usual things such as cable, USB port, reboot PC.
Also disabling HTC sync is worth a shot, as is reinstalling HTC Sync Manager.
Sent from my HTC One X

danielsaenz said:
I hate to do this but is USB debugging on?
Sent from my HTC One X
Click to expand...
Click to collapse
Debugging is on
Sync is not installed on the andriod pc to reduce problems.
Have tried 2 cables and different usb ports, it wont connect on 5 pc in my house so I have to think its on the phones end but honestly Im out of ideas other than a big hammer.

Grnfinger said:
Debugging is on
Sync is not installed on the andriod pc to reduce problems.
Have tried 2 cables and different usb ports, it wont connect on 5 pc in my house so I have to think its on the end but Im honestly out of ideas other than a big hammer.
Click to expand...
Click to collapse
re-install sync. after the install make sure it's disabled/not running

Reinstalling sync was no help....this is one tough nut to crack

Firewall issue? Undo the security update?

gunnyman said:
Firewall issue? Undo the security update?
Click to expand...
Click to collapse
no firewall...
Progress ( I think)
adb works if phone is booted up, did a adb devices and it showed
adb will not work in fastboot mode and it used to. I rolled back Windows prior to updates, 4 days back to when I flashed twrp and it did not help.
I have a spare hdd debating on a fresh OS install with minimum crap installed,
Maybe I should take this as a sign and not make a add on
appreciate the help Gunny

Does it show adb devices while in fastboot? Also, check your device manager while your phone is in fastboot and make sure you don't have any unknown devices.
Sent from my HTC One X

[SOLVED] USB still not recognized (ICS Leak)

Edit:
This problem has been solved. For any of you that are having issues with ADB recognizing your phone, even after you have uninstalled and reinstalled the correct drivers (As I had done several times on 2 computers), a factory reset might be your answer. So, if you are on ICS leak, and the last thing you want to do is try to FXZ back to 2.3.6...Try wiping data/factory reset first. It solved my problem once and for all.
------------------------------------------------------------------------------------------------
First, I must say that I have already found similar threads of this type, and some even with solutions, but I still cannot fix this problem.
I am on ICS Leak on my AT&T Atrix 2 and everything is running great, aside from one thing. I cannot get my computer to recognize my device. When I plug it in, it will charge, but I get no USB options in my notification bar on my phone. I have tried other solutions, and I have installed the necessary drivers, (Windows 7), I have uninstalled and reinstalled, and rebooted with no luck. If anyone could help me, that would be great! Let me know if any more details are needed...

Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?

I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done

Garnerj013 said:
Recognition problem solved. Root script still hanging at *daemon started successfully*
Debugging is on, Stay awake on, Install from unknown sources on, drivers installed, what else could be the problem?
Click to expand...
Click to collapse
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Sent from my phone's mind

Drgravy said:
First off if you found similar threads post in them, no need to start a new thread
I'm guessing you are trying to root?
if you are, the script takes a while to run your phone will reboot several times it will tell you when it is done
Click to expand...
Click to collapse
Sorry about the new thread. Blame it on the n00b status. I have rooted with this method before on the same model phone with ICS leak and it worked after a few unsuccessful tries. It usually shows some activity in the command prompt, but this time it is hanging at *daemon started successfully*
alteredlikeness said:
adb devices command showing your device? If so, try again.. and wait, like drgravy said.
Or do what leif said and switch between the 3 different usb connection types and wait for the drivers to install.. and try putting it in mtp or ptp mode to run the root batch file..
Click to expand...
Click to collapse
I've tried in every connection mode, and I have the drivers installed. I've been trying every way possible. Also, for simplicity sake, could you tell me how to use the adb devices command? I'm tech savvy but pretty green to the development/programming side of things.

leifemagnuson said:
I had to uninstall drivers and all moto services. Then plug in phone let it look for install drivers. It failed on one of them. I then installed the moto portal disconnected my phone, rebooted computer and phone, plugged it back in and it worked. Good luck.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Also, once i uninstall Motorola Device Manager, do I have to manually uninstall more drivers, or does that get them all? If not, how do I manually uninstall the drivers?

http://forum.xda-developers.com/showthread.php?p=29609879
I was having the exact same issue where it was hanging at daemon started successfully. Was totally a driver issue. Follow the link in my link...
I would suggest completely uninstalling everything Moto from your PC, rebooting and then follow the steps again, being sure to install those new drivers that are linked in that post.
Edit: I'm trying to remember when I did it....but I seem to recall having a bit of weirdness when I installed the new drivers. I had the install driver wizard pop up while I was installing the drivers from the moto driver executable. I just let the wizard sit there and wait while the moto driver installer did its thing.

So, instead of uninstalling all that is Moto on my laptop, I moved the Moto Device Driver executable and the batch files (with Su and Superuser.apk and all the extras to my desktop. Ran the moto executable and plugged my phone in to install the drivers and rebooted the computer. Still nothing. Do i need adb on my desktop to root my phone? I'm getting flustered with this. It really should be working one way or the other....

Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app

devilhunter47 said:
Same issue for me..i reinstalled drivers and connected the phone in media transfer mode..rest of procedure same..am successfuly rooted now
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I tried and tried to reinstall the drivers, and even installing them on a different PC didn't work. Finally, I did a factory reset, and the phone was recognized by ADB. Thankfully, I am now rooted and on SCv7!! (Thanks to Jimbridgman, Ikrasner, and a couple other devs.) Thank you all.

ADB Can't find Device

I have tried everything and I can not get my device to show up in ADB for the life of me. I have verified my supercid thru adb, but can't get my device to show up. I've installed htc sync, updated drivers, even downloaded the tool multiple times. I thought I read back when I rooted that i needed to uninstall htc sync, is this correct?

Nobody? Come on guys help a brother out.
Sent from my HTC One X using xda premium

louslugger15 said:
Nobody? Come on guys help a brother out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
TRy ending task on htc sync, a different usb port, and different usb cable, and make sure its not usb3.0.

I'm pulling what's left of my hair out over this, too. I've tried uninstalling all drivers and HTC software, and not letting Windows install the default drivers. I've changed USB ports. I've tried reinstall HTC sync only, but the phone still doesn't show up in adb. Device is recognized both booted into the ROM and in recovery/bootloader, just not by adb.
Grr
Running cleanrom 6
Windows 7 64bit
USB debugging is on.
Sent from my Transformer TF101 using xda premium

How did you ever root your phone if adb doesn't recognize it?
Sent from Xparent Red using my Venomized Evita

That's the weird part. I have root, recovery, but for whatever reason I can't get adb and my phone to talk.
Sent from my HTC One X using xda premium

Its funny you having these problems... I usually have no trouble with adb, however last night I tried to s-off my cousins hox... Fastboot works fine, when I get to the adb push it won't recognize in adb. So I tried mine, won't recognize... Rebooted both phones and my computer. No go..
So I tried my wife's computer... No go...
I don't understand either
Edit: while I was at it I tried cleanrom, dirty ROM, and cm10.1
Sent from my HTC One XL using Tapatalk 2

I have this problem too when I am trying to get adb devices with windows 8 64bit. My devices always appears offline. But when I trying with windows 7 32bit, viola.. its work! Maybe there is something wrong with 64bit platform (or just mine?)
Sent from my HTC One X

Are you guys trying adb commands? Or just stopping when "adb devices" returns nothing? Because I noticed this when I upgraded everything on my phone this past weekend.
I was able to ruu, push files, etc., but "adb devices" returned nothing. I was on 64-bit Win7 with USB 3.0.

I've tried windows XP and windows 7... Tried shooting a bunch of adb commands with no success... "Device not found"
I've always had success with adb, as I use it quite often for the custom sense lockscreens
Sent from my HTC One XL using Tapatalk 2

I had this problem a little while ago. Only a reinstall of windows helped:banghead:. During the meantime though I booted up a virtual machine and ran the commands through it.
Sent from Xparent Red using my Venomized Evita

That's an idea, a virtual machine.
I pulled an antique desktop out of the closet that ran on some ancient version of xp and solved that problem. I never got over "devices not found" on any other new computer with my hoxl or wifeys x+. I tried everything everyone will ever tell you.. Random assortment of usb cables, ports, installed HTC sync and HTC sync manager a trillion times, tried creating a file with my hexadecimal I'd number in them.. Even tried running the cmd or Adb as administrator.
In the words of jcase: windows sucks. Fix your environment.

InflatedTitan said:
I've tried windows XP and windows 7... Tried shooting a bunch of adb commands with no success... "Device not found"
I've always had success with adb, as I use it quite often for the custom sense lockscreens
Click to expand...
Click to collapse
Did you check Task Manager and kill all HTC and adb functions? HTC sync keeping stuff running even when you close it. That worked for me.

My phone wasn't coming up as "Android Phone" or "HTC" in the "Device Manager" on Windows 7. Would only show it as "G:/" under "Portable Devices" thus disabling me from installing the proper drivers.
[SOLVED]
I plugged my phone in, and uninstalled G:/ in device manager (Your letter may be different).
Then I went into "Disk Management" and found the removable drive G:/. Right click and go into which ever option was to change the letter. Go ahead and pick another letter (make sure it's different from any other drives you may have, I went with Z).
Unplugged my device, made sure debugging was on, and plugged it back in. Device Manager now shows my phone as "Android Phone" Success!

iElvis said:
Did you check Task Manager and kill all HTC and adb functions? HTC sync keeping stuff running even when you close it. That worked for me.
Click to expand...
Click to collapse
Noo I can't believe it slipped my mind.. About to be home... Will try
Sent from my HTC One XL using Tapatalk 2

I got mine working last night, but I have to be honest that I have no idea exactly what it is that worked. Here's what I did:
Uninstall HTC Sync and ALL HTC stuff.
Toggle developer modes on and off a few times
Reinstall HTC Sync
Windows tries to install drivers, but I forced it to uninstall them.
Manually install the drivers included with HTC Sync
And... it works now. I'm not sure what was different this time around, but I won't complain.
Sent from my Transformer TF101 using xda premium

I also noticed this when I tried to flash CleanROM 6 from Newt's JB. Neither Newt's nor CR6 (installed successfully without adb) were recognized on PCs and ports I had used to root my Evita. I think this has something to do with JB or the "debloated" versions.
When I connect my Evita, I no longer receive the charge/drive/tether toast notification. USB debugging is set in settings. Had to install "adbWireless" app to get adb to work properly, and of course that means that I have two devices connected via adb/fastboot if I reboot to recovery or bootloader. What a PITA, I will try on a USB 2.0 port to see if that has any more success.
****EDIT-RESOLVED****Like belyle, I had to force USB debugging off, and this took several attempts. Even with Developer Options turned off, USB debugging would turn itself on when the phone was plugged in to the computer via USB. Somehow this locked the phone from being recognized. Finally got USB debugging shut off, and manually turned it on again and adb/fastboot worked normally. I did not have to uninstall or reinstall anything. I am currently running CR6.
As I mentioned before, this is something that was set by default on a cooked ROM and think that is what is causing this issue.

I'm sorry for activating an old thread, but I've had the same issues and the fix for me was to use my USB 2.0 port instead of the USB 3.0 ports on my laptop. As soon as I plugged it into a USB 2.0 slot the phone booted right up without issue and could be seen through ADB, plugged it back into the USB 3.0 and "error: device not found" kept coming back. Moved back to the USB 2.0 slot and no issues whatsoever. Funny how USB 3.0 is supposed to be backwards compatible, but yet my phone doesn't work on it.

herschwolf said:
I'm sorry for activating an old thread, but I've had the same issues and the fix for me was to use my USB 2.0 port instead of the USB 3.0 ports on my laptop. As soon as I plugged it into a USB 2.0 slot the phone booted right up without issue and could be seen through ADB, plugged it back into the USB 3.0 and "error: device not found" kept coming back. Moved back to the USB 2.0 slot and no issues whatsoever. Funny how USB 3.0 is supposed to be backwards compatible, but yet my phone doesn't work on it.
Click to expand...
Click to collapse
This has been posted so many times.
Sent from Xparent Red using my Venomized Evita

WookieFan said:
I also noticed this when I tried to flash CleanROM 6 from Newt's JB. Neither Newt's nor CR6 (installed successfully without adb) were recognized on PCs and ports I had used to root my Evita. I think this has something to do with JB or the "debloated" versions.
Its something to do with JB. I tried to uninstall, reinstall drivers/HTC Sync, different USB port (all 2.0 on my PC), all the usual stuff. None of that worked. The only thing that got it to work was reverting to an ICS nandroid. After that, adb recognized immediately. Did the s-off and went back to the JB nandroid. Again, adb doesn't work (although fastboot does).
Click to expand...
Click to collapse
Click to expand...
Click to collapse

help with fastboot.

I previously unlocked my bootloader, installed oxygen 11 (am on beta 4) . I want to install PA but I can't get fastboot on my machine. Shouldnt it be as simple as instilling adb and fastboot as well as the oneplus drivers? I've done everything I can think of and the majority of times ,I ended with an exclamation point in device manager and couldn't get the correct driver installed. I tried SDK etc.. more so... Android composite adb isn't showing in device manager. I might just use my laptop.
Any quick ideas on how to fix though? Thanks

There are lots of guides and links to the minimal adb/fastboot packages here on XDA. I will say it's a heck of a lot easier on Linux or even Mac, but typically the issue is that you want to have your device drivers installed first, then connect your phone (switch it between charging, file transfer, and MTP modes and let it install each of them fully to the device manager while it's plugged in), then install adb, enable debugging, plug in, run "adb devices" and trust the RSA fingerprint, and let it install that side of things to device manager as well.
I'd start by uninstalling all of the instances of the device in your system first to start over. You might even try plugging it in with no drivers installed first to see if it loads working generic drivers.
Man, I do not miss Windows.

I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...

Make sure you have the latest Android Platform Tools installed...
https://developer.android.com/studio/releases/platform-tools

satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Try revoking all adb authorizations and then try to plug it in and run "adb devices" to regenerate an authorization maybe? Is the problem only with fastboot or is adb also broken? You are running fastboot commands in the bootloader instead of adb commands, right?

satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Any luck? I'm having the same issue. Just managed to get my phone unlocked from tmo, and for the life of me can't get windows to recognize my device in fastboot. After an uninstall of the device in device manager, and plugging it back in fastboot. It appears under other devices as simply android with a question mark icon top left, and a yellow triangle bottom right. Manually pointing to either the drivers from 15 sec minimal adb & fastboot google drivers, or selecting all devices>have disk>and pointing too the inf of the driver downloaded straight from google results in the yellow triangle going away, but the question mark still remains, and it's still listed under other>Android. So I suspect for some reason or another the drivers aren't installing properly. Usually (having to have to do this with other devices) has worked in the past. I've had win 10 mess up loads of things most notably my dl speed once. Some bug had it capped at like 24 kb/sec (shudders). Just for comparison what Windows version are you on?
Tried dl ubuntu to boot from usb and try that. Then I ran into issues dl the iso. Couldn't catch a break yesterday I guess. I'll try again after work today, and report back. Don't like the idea of having to boot linux just for fastboot. Might a vm, but I'm not sure that would work considering windows doesn't recognize the device to pass it through, but we shall see. I will say this just about over win10.
Also Idk if it matters, but I had Android studio installed before this as well. Might be time for a fresh install it's been a while.
Sent from my OnePlus8TMO using XDA Labs