Related
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.
I have a htc sensation 4g with hboot 1.27.1100 I've unlocked the bootloader flashed recovery, and rooted the phone.
I'm trying to gain s-off by running controlbear, and using the paper clip trick, but after controlbear reboots the phone it gives me this message : Connect device and install drivers.
I'm assuming it's referring to the device drivers for the phone which are already installed. If it's referring to some other driver I don't know what one it's talking about.
I noticed while using adb it also would not recognize the device, though I was still able to use it to communicate with the phone. Was thinking that might have something to do with it.
Any help would be appreciated.
HTC's 4.0 update really screwed my phone up...Just bumping, don't know what proper etiquette is on this forum for bumps, if it was to early i'm sure i'll hear about it, and will reserve myself for future post.
make sure you have usb debugging on i had the same issue and i didnt have it on so give that a try good luck
contractedkill said:
make sure you have usb debugging on i had the same issue and i didnt have it on so give that a try good luck
Click to expand...
Click to collapse
i have a problem. i have a htc evo 3d cdma rooted unlocked and my computer is windows 7 with the htc driver.... i want to be s off i finally got controlbear to work untill i get to the arrow screen then it says resetting connecting 1 2 open device manager and check adb and fastboot drivers. so i opened device manager and looked and windows sees it as a portable device and i tried to install the htc driver but i dont know where it is on the computer and it doesnt show up when i pick from a list of drivers. please help i cant find a solution
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
hi,
i've been trying to s-off with rumrunner, and one of the pre-requisites is to remove htcsync. after doing so, i can't see my phone with adb. i've tried installing htc drivers and reinstalling adb/fastboot files, but still isn't working. also i tried reinstalling htcsync but again, still not working.
any ideas?
thanks in advance!
I keep having this problem lately. I just keep trying to reconnect the usb until it works. I'd like a fix too.
Sent from my rotary phone.
Did you enabled usb debugging. If not that should be the problem
Sent from my HTC One S
aye, usb debugging is enabled and i've given adb SU access etc.
sometimes when i put in adb devices, it shows as a number + emulation... does that help diagnose the issue?
fixed this by re-flashing my stock rom, reinstalling htcsync and updating android sdk. uninstalled htcsync, went back to my daily rom (twistedkat) and i still have adb usage. odd.
I keep getting error device not found with adb tools on two different verizon m8's ?
I was using adb tools 1.0.31 and never had any problem until tonight and my one m8 I had obtained s-off on it a bit over a week ago with no problem at all. I tried to firewater s-off another m8 that belongs to a friend and his keeps getting error device not found and mine does the same thing. My computer has froze up 2 times in the last 2 days I"am on windows 7 I used system restore and went back 5 days no difference.
I even tried another version of adb tools, then I tried my other computer which it never freezes up and same deal on it with multiple versions of adb tools. I have updated all drivers and done all that rebooted over and over I have even removed java on both computers and installed new versions. Really pulling my hair out on this. Even tried multiple usb ports on both computers.
I have also constantly been checking device manager and there are no conflicts on anything and all drivers keep showing that they are the newest driver.
I could see if it was doing it on just the one m8, but on mine also which it was working fine on it just days ago.
Anyone have any ideas ?
You did remember to enable USB debugging, did you? [emoji6]
Sent from my HTC6525LVW using Tapatalk
berndblb said:
You did remember to enable USB debugging, did you? [emoji6]
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yes I even tried unchecking it then powering off restarting and rechecking it, actually did that all a couple times to rule it out.
Do you see the Android ADB interface in device manager, or are there any yellow exclamation marks there?
For ADB to work you need:
- ADB access on in Developer Settings (USB Debugging)
- The ADB application
- Drivers for your Windows PC for the ADB device to be recognized
You've stated you've done point 1, I don't doubt you have point 2, you need to work on point 3.
Note: The last possibility is you have some external program blocking your access. I've seen some draconian firewalls block USB.
jskup said:
Do you see the Android ADB interface in device manager, or are there any yellow exclamation marks there?
For ADB to work you need:
- ADB access on in Developer Settings (USB Debugging)
- The ADB application
- Drivers for your Windows PC for the ADB device to be recognized
You've stated you've done point 1, I don't doubt you have point 2, you need to work on point 3.
Note: The last possibility is you have some external program blocking your access. I've seen some draconian firewalls block USB.
Click to expand...
Click to collapse
If your talking about my htc it showed working fine and I tried to update the driver and it showed I have the newest driver available. I went through everything on device manager and everything was working fine, and no exclamation marks. Like I said it was working fine as I used it to firewater s-off an at&t m8 2 weeks ago and it worked fine for it. And I did the firewater on 2 other htc phones in the last 2 months. Also I have used the same adb tools for like the last year with no problems. Also I have not changed any programs, and I have used the same antivirus and firewall for the last 2 years so it should not be blocking it.
This is all why it has me stumped ?
It's not as bad as all that.
The next thing I'd do would be to uninstall and reinstall whatever method gave you the drivers. If you installed the HTC Sync software, uninstall and reinstall. If you used some other method, such as the Minimal ADB and Fastboot package, I'd uninstall and reinstall it.
I have to deal with drivers all the time at work. This sort of thing can happen. Windows makes this process more complicated than it is in Linux.
Roefastford said:
I keep getting error device not found with adb tools on two different verizon m8's ?
Click to expand...
Click to collapse
Have you tried a different USB cable?
Doc Ames said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes tried multiple cables and multiple usb ports. With android system running they pick up the phone as a storage device also. It makes no sense. Going to try unistalling drivers and reinstalling as the other guy suggested.
jskup said:
It's not as bad as all that.
The next thing I'd do would be to uninstall and reinstall whatever method gave you the drivers. If you installed the HTC Sync software, uninstall and reinstall. If you used some other method, such as the Minimal ADB and Fastboot package, I'd uninstall and reinstall it.
I have to deal with drivers all the time at work. This sort of thing can happen. Windows makes this process more complicated than it is in Linux.
Click to expand...
Click to collapse
I will try uninstalling and reinstalling the drivers and see if that fixes the problem, thanks.
Figured it out. I was trying to run firewater from bootloader lol, and not with android running. Ok I guess I really messed that up lol.