Everytime i connect my desire via USB charging/disk drive mode and enable USB debugging unrevoked3 forever shows "waiting for device". ALready downloaded and installed the hacked HBOOT drivers located here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
But they still dont work. I tried searching online but found no answers. I cant even root the phone and proceed to flashing any custom recovery or ROM. A little help please?
Hi guys, hopefully someone can help.
I rooted the phone using unrevoked and now have clockworkmod recovery on the phone. Tonight I tried to connect the phone to the android SDK with no success.
Windows device manager only shows it as an Android Phone. Everytime I try to manually install the SDK usb drivers, it comes up with a message saying drivers aren't available. I have deleted and reinstalled the SDK usb drivers and have also deleted the android phone from the device manager as well as USBDView. Have had no success whatsoever.
How can I get ADB commands working again on the phone?
EDIT - SOLVED - Apparently I had to reinstall HTC Sync and it worked! strange how these things work!
I can't connect adb on any 4.2.2 ROMS, i understand theres a new security feature in 4.2.2 that should prompt you to confirm your PCs RSA key, but i never get this prompt. Also, ktoonsez kernel seems to bypass the security, as it allows me to connect without ever seeing the prompt. But any other kernel, no prompt, and all adb commands show device offline.
I do have the latest version of adb (1.0.31) and the latest sdk etc.., i also can't connect to adb using the USB cable either. I've tried reinstalling drivers, rebooting... nothing seems to be working.
any suggestions?
Edit: got it working. Can't say i know exactly what i did to fix it, but i'll try to reiterate what i just did. Clean flashed a new ROM, in developer options > root access set to Apps and ADB, make sure Android debugging is enabled, make sure USB debugging notify is enabled, then turn on adb wireless. Then on my pc connect to adb using "adb connect 192.168.1.x", adb devices shows device still offline. Then connected my phone to my pc through usb and i got the prompt. FINALLY lol
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
CZ Eddie said:
I'm sure you already did this, but you didn't mention it.
In a lot of 4.2.2 ROM's, you have to go into Developer Options and change from "Root access for Apps Only" to "Root Access for Apps and ADB".
Not all 4.2.2 ROM's do this, but some of them do.
I could not ADB from my computer to my 4.2.2 until I changed that selection.
Also, some new ROM's have the built-in Superuser which includes an ADB option in its settings.
Click to expand...
Click to collapse
Tried it, no luck.
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
CZ Eddie said:
Maybe try this?
https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq
Click to expand...
Click to collapse
I appreciate the input but all that post says is that you must be on the latest SDK version which I mentioned I already was
Hi, I am attempting to root my new M8 with the Toolkit method found here, http://theunlockr.com/2014/04/19/roo...-method-video/. My issues arise very early on in the process when running "Step 3: Get Token ID." At this point, I receive this message, "error: device not found." So I assume this must be a driver issue.
Side note: I have developer enabled, I have USB debugging enabled, I am using stock data cable, I've attempted all 3 USB ports, I've already uninstalled and reinstalled drivers, I've attempted Kush's universal drivers, I've tried uninstalling HTC sync, and I made sure I extracted .rar files to desktop. Any more ideas?
Thanks, Jack
Does your device manager register an unknown device with a yellow warning icon next to it?
i'm trying to flash CM12, but every adb command errors out and my devices is listed as "unauthorized" when i run adb devices. i understand that normally i would restart in Android and allow USB debugging. but.. i accidentally wiped my device while i was in Recovery mode.
According to the CM docs on secure USB debugging:
if you see error: device unauthorized while attempting to use adb in recovery, restart to Android and authorize the connection.
Click to expand...
Click to collapse
but since I wiped my device, I am stuck in recovery with USB debugging disabled. i tried booting from sd, but it just errors out . so i'm stuck. anyone have any advice?