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.

Need help

I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it

Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.

Ok, Ill give a try.

I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?

I found the best way to get the driver installed is to install HTC sync

Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?

Is there battery actually low? Just shut down the phone and charge it up.

When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?

Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.

[Q] Can't connect phone to PC

I posted this before but didn't get much response and I still have this problem. I rooted my phone using the 1.85 method, and am currently rooted, but not unlocked. I've tried to unlock the bootloader, but since device manager does not detect the device I can't unlock it. The phone charges when connected to the PC (IO panel, not front), but the connection type does not appear in the notification pull-down, and device manager does not display the device. This wasn't true before rooting, and now that my PC can't detect the phone I can't unlock and I can't copy over files from my PC to my phone. I have current drivers successfully installed, and I haven't updated any software beyond stock on my phone (1.85, 4.0.3), though AT&T has tried to push an update on my phone this morning.
How can I solve my problem? This is my first Android phone, and I wanted to unlock the bootloader to be able to flash ROMs and develop my own, but at the moment it isn't possible.

Yarok said:
I posted this before but didn't get much response and I still have this problem. I rooted my phone using the 1.85 method, and am currently rooted, but not unlocked. I've tried to unlock the bootloader, but since device manager does not detect the device I can't unlock it. The phone charges when connected to the PC (IO panel, not front), but the connection type does not appear in the notification pull-down, and device manager does not display the device. This wasn't true before rooting, and now that my PC can't detect the phone I can't unlock and I can't copy over files from my PC to my phone. I have current drivers successfully installed, and I haven't updated any software beyond stock on my phone (1.85, 4.0.3), though AT&T has tried to push an update on my phone this morning.
How can I solve my problem? This is my first Android phone, and I wanted to unlock the bootloader to be able to flash ROMs and develop my own, but at the moment it isn't possible.
Click to expand...
Click to collapse
Did you turn on usb debugging? And after you connect ur phone did you try adb to see if your phone is detected
Sent from my HTC One X using xda premium

abhipati said:
Did you turn on usb debugging? And after you connect ur phone did you try adb to see if your phone is detected
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, USB debugging is on. I tried adb using this guide (http :// www . thesuperusersguide . com/adb-backup--restore.html sorry can't post links), but once I paste in “adb backup –apk –shared –all –f /backup/mybackup.ab," I get back adb: unable to connect for backup."

Yarok said:
Yes, USB debugging is on. I tried adb using this guide (http :// www . thesuperusersguide . com/adb-backup--restore.html sorry can't post links), but once I paste in “adb backup –apk –shared –all –f /backup/mybackup.ab," I get back adb: unable to connect for backup."
Click to expand...
Click to collapse
When you type adb devices, what do u get output
Sent from my HTC One X using xda premium

In 1.85, there was the option to default your connection type. It may be set to charge only. Check your settings. This may be the issue.

abhipati said:
When you type adb devices, what do u get output
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
XNine said:
In 1.85, there was the option to default your connection type. It may be set to charge only. Check your settings. This may be the issue.
Click to expand...
Click to collapse
As it seems the USB port I was using wasn't connected properly to the motherboard, so I had to do some tinkering there. It all worked out though*, thanks for the help.
*Except that I accidentally installed the OTA update instead of postponing it and removing notifications... Now begins the wait for a 2.23 root method. Woe is me.

Fastboot Not Recognized

Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.

chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL

Venomtester said:
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.

Windows XP makes life easier

chriscerv90 said:
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Click to expand...
Click to collapse
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL

Venomtester said:
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.

chriscerv90 said:
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
Click to expand...
Click to collapse
I know this may sound silly at this point but did you try moving it to a different usb port? I have seen that work before.
AT&T HTC OneX
Android 4.1.1
ViperXL

try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.

I had to use a different Micro-USB cable to get it work. Try that.

Yeah I actually have tried all those steps. Thanks for the replies guy. I check out that application.
I'm starting to think something is wrong with my HOX
Sent from my HTC One X using xda app-developers app

DvineLord said:
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Click to expand...
Click to collapse
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:

glad you got it fixed, check out his other apps they are life savers and they work how "real" windows apps should work.

I have the same problem
chriscerv90 said:
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
Click to expand...
Click to collapse
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??

abhilashlinge said:
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
Click to expand...
Click to collapse
If your on Windows 8 problems will occur but there are methods you need to look into. Windows 7 is your ally.
First Uninstalled the drivers for the device using the program in the previous post. Second, make sure your cable is working correctly. Third, make sure you have the correct drivers for you phone on the computer - - HTC Sync causes problems sometimes. Fourth, plug in the phone in while it's on and let the drivers install correctly. Fifth, place the phone in fastboot and let drivers install. Should work.
Remember sometimes you need to restart your computer and try different USB ports. Some users have said 3.0 ports cause problems.
Good luck.
Sent from my SM-N900A using XDA Premium 4 mobile app

chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
I ws installing a Ruu zip but process got failed and hboot version changed to 1.54.000 . my device is in now relocked status and bootloader is not reconised by hp envy. adb still showing my device my i lost fastboot mode completely. Any solution there???
I already tried several drivers method. Error is something HTCAND4 in driver events log.

What did u do?

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