Related
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
I've been trying to get anything to recognize my Hero on my PC for the past few days.
What I've tried:
Installing HTC Sync
Installing Android SDK
Installing the HTC HERO DIAG drivers
Doing ##DIAG# and not doing it.
...And all different combinations of those. The problem is I can't get QPST, CDMA Workshop, UniCDMA, or QXDM, etc to recognize it. The Hero synced to the HTC Sync a couple times, but nothing else. It won't even assign a COM port on the computer.
The phone is also rooted, which, I wouldn't think would make much difference, but I'm running out of ideas here.
Any help is really appreciated.
Did you install the regular HTC drivers ? Go to your device manager and see if it says android phone when its plugged in if its there tell it to update driver and point it to the folder called HTC drivers located in the HTC sync program directory.
I tried to do that but the driver wizard said that it could not find any drivers that were better than the ones already installed. (or something to that effect)
EDIT: Ah! I don't know what happened but it appeared on COM5 as "HTC Diagnostic Interface". That may be what I needed. We'll see.
I get the same thing, says "Windows has determined the driver software for your device is up to date."
"HTC Dream Composite ADB Interface" <--???
Exactly the same for me.
Device not recognized, Remove and reinstall HTC Sync and manually selecting drivers, Device wiping and trying again, using a different USB port, using a different cable, reinstalling windows!!!!!, using a different computer, Pulling out my hair!!!!!
Nothing works!!!
However, It did used to ask for mounting and unmounting the SD when plugged in but it has NEVER found HTC sync on my PC.
Now, all I get is Charging battery on the Hero and device not recognized on the PC.
Device manager politely tells me "Windows has stopped this device because it has reported problems. (Code 43)"
My system is Windows 7 X64 and my Hero Has run both the shipped ROM and now a cooked 2.1.
Please help me!
I have never been able to sync my Hero on any of my Win7 machines. I have been able to sync sporadically with my work XP Pro SP3 machine though. However, since flashing the AOSP 1.6 rom, HTC sync isn't recognizing my phone anymore. I can however mount the SD card.
Problems connecting Evo to PC
Same problem, but on EVO... Anyone ever figure it out??
I should elaborate I suppose lol... Everything *worked* fine, and then suddenly, appearantly for no reason, it just stopped... Device manager now calls the HTC diag driver an unknown usb device and gives the same warning message as above. And when I try to update the driver, gives the same message about it being up to date...
I have not been able to get ADB to work on my phone since the first time I flashed 2.2, when plugged in it will do the "do you want to turn on usb storage" message and it works fine.
You all might want to try installing the android adb drivers. Its a well know issue with the htc drivers. If you click on my avatar and go to my post you can find my thread on how to install adb on windows 7 32/64 and xp. Adb works fine for me and sync as well. The adb drivers might help out. Well good luck.
Edit: Running Aosp's 3/26 gb build RA1.7 Jason m's 806 kernel kifno build prop tweak -mp
Yea it's Me Again With The
Modified Hero
Tramline said:
Exactly the same for me.
Device not recognized, Remove and reinstall HTC Sync and manually selecting drivers, Device wiping and trying again, using a different USB port, using a different cable, reinstalling windows!!!!!, using a different computer, Pulling out my hair!!!!!
Nothing works!!!
However, It did used to ask for mounting and unmounting the SD when plugged in but it has NEVER found HTC sync on my PC.
Now, all I get is Charging battery on the Hero and device not recognized on the PC.
Device manager politely tells me "Windows has stopped this device because it has reported problems. (Code 43)"
My system is Windows 7 X64 and my Hero Has run both the shipped ROM and now a cooked 2.1.
Please help me!
Click to expand...
Click to collapse
more than likely it is your usb cable has been damaged.
i had the same problem, i went to my provider and got a new usb cable for it. (they gave it to me for free, no questions) no more problems at all, works like a charm.
i still have the old cable too, it will not recognize the hero on the computer. in fact if i plug the cable in without the phone, the cable itself actually comes up and says unrecognized device. but it works great for charging.
When I connect my hero (VillainRom 10) to my PC (Win7 64) all I get is a "USB Device not recognized" error, the phone is being charged, but I get not ADB connection.
Plus, I get the "connect to PC" dropdown on the phone, selecting something (e.g. disk drive) has no effect however.
It really randomly stops working and as randomly works again for a short period of time.
I have tried different USB ports, the cable that shipped with the Hero and a normal miniUSB cable, HTC drivers and those that come with the SDK, removing battery while connected, restarting Phone and PC etc etc.
Once I saw that some dust gathered in the Hero's USB port, so I removed it and it worked after that. Some time later it stopped working however and I can't get it working again although everything is perfectly clean.
This is especially annoying since I started developing a game for Android and debugging is almost impossible now :[
All help is greatly appreciated!
Have you tried...
adb kill-server
adb start-server
(adb devices)
I had the same issue under Linux, where this helped, I don't know about Windows though (doesn't hurt to try though)
I had this the other day, go to Device Manager, find the ADB device, and then get it to download drivers of the net. For me, the drivers downloaded where for the HTC Dream, but still, it worked and now I have the ADB connection works
Hope this helps
I had a similar problem and I solved it by installing HTC Sync.
^ +1
installing HTC Sync worked for me
Thanks for all those tips, but I actually tried all of them, restarted adb server, I can't load new drivers via device manager because my Hero is not being displayed as ADB device but as "Unknown" (but I manually tried different drivers) and I also have HTC Sync installed.
You have some other ideas?
(meanwhile I'll try some stuff myself if I have time)
Could it be the USB cable?
I uninstalled HTC Sync, uninstalled ALL usb drivers (except keyboard and mouse, using usbdeview) installed VillainRom 12 on my Hero, downloaded and installed HTC Sync and 64-bit drivers from softpedia and now it seems to work more or less stable.
I hope it continues to do so and that this here may help someone else!
Argh!
stopped working after reboot...
now it's switching from nothing happening at all when I plug it in, showing me the "Device not recognized" error, or, in very few cases, working for several seconds, then loosing the connection.
I start to believe that this is a hardware defect, but why did it use to work in the past then??
Thanks alot for your help!
Not using a 64 bit machine worked for me. Although it took 5 computers, this fixed the problem for me.
(should note I was also having troubles rooting on my x64 machines.)
Defn shouldn't have upgraded everything to 64-bit. Doh!
Sent from my Super Duper EzHero using XDA App
Tried on a 32-bit XP laptop - didn't work :[
but thx
edit: tried on another win7 x64 laptop - nothing happened at all !?
i've been on ALL the same problem with you
and i'm tiring to find the way out
hope anyone can help us too....
Good to hear I'm not alone! Let me know if you find out something (whatever it is)!
2 days ago it suddenly worked perfectly as if nothing had happened all the while.
programmed happily... next day pc boot - good ol' "device not recognized"
it seems to be exactly this problem:
http://blogs.msdn.com/b/usbcoreblog...cted-or-comes-up-as-unknown-device_3f00_.aspx
now I/we need to find out what causes this on the hero
somthing that could have to do sth with it working 2 days ago is that my hero's battery was completely drained and it was force-shut down. Only after attaching power I could boot the hero. Then also the usb connection (with adb) worked.
very strange...
edit:
someone else seems to have the exact same problem on linux (so it's os independant)
http://forum.xda-developers.com/showthread.php?t=653295
another guy with a potentially interesting solution in post #7
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7211035
which leads to this:
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
(I will try it nao
update: got it working (let's see how long by doing the following)
(you'll need the android sdk for it)
shut down hero
remove and reinsert battery
boot into fastboot (Hold [back] and [power] key)
open cmd
cd into the andoid sdk tools dir (for me cd C:\android-sdk-windows\tools)
exectute "fastboot oem boot"
let hero boot
now you should have at least adb connection, now unplug and plug hero and you should have full connection (sd-card, whatever you want)
if that didn't help you can try the stuff from this link (posted that earlier already):
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
(I had planned to do all the steps, but the first one already fixed it - strange)
edit:
works on 1 other PC I've tested so far - will try our car's pc next
update: stopped working again, not even fastboot was able to connect
removing the battery while in fast boot while being plugged to the pc and reinserting the battery fixed it
strange strange...
Remove phone from PC
Uninstall htc sync
Run usbdeview-x64 and remove any htc (or unrecognised usb devices)
Restart
Reinstall HTC Sync - latest version .33 or something
Plug in phone (allow it to get drivers from windows update etc, if not use the ones in the HTC Sync folder)
I did this several times but it didn't help as my problem is a problem of the hero, not of the pc not finding the right drivers.
Send it back for repair then...
I will first try fixing it myself
Ok so a little background. After hearing about the Carbon backup app a while ago I decided to install it and followed the instructions to do so. One of these steps is to change the normal USB drivers to the ATB ones from the Android SDK. I did this and it all went well without a hitch. However I came to add some movies on to my nexus 7 today and it would only recognize my device in PTP mode (as per the Carbon app requires). I proceeded as normal but found that I could not create a new folder for my films. When i tried i was faced with this error:
However I found that I could create a new folder in one of the existing sub-directories so I proceeded with that. I started copying the movie files over and got another pop up looking like this:
After clickking yes I was soon faced with another error screen:
This happens for nearly every video file i have tried to transfer. I have tried uninstalling the ADB drivers and letting windows install the default drivers it used the first time, however now it will not find any driver software for my nexus 7 unless I point it to the ADB drivers. Whenever I try to connect my device as an MTP device instead of PTP windows will not recognise it and nothing will show up in my computer. Is there any way that i can defer back to the default drivers and use my device on MTP instead of PTP?
Just for a bit of extra info, the same problem is occurring on my nexus 4.
Thanks
Hmm, i have adb drivhttp://forum.xda-developers.com/showthread.php?t=2214386alongside stock drivers for mtp as im sure many do n do not face this problem.
Have you uninstalled the backup app and cleaned the registry?
Try going in to device manager and enable 'show hidden devices' and search for any leftover usb drivers or interface that might interfere with the stock drivers. As a last resort you can download your usb chipset drivers, then uninstall all chipset drivers and usb devices including those hidden, then reinstall the chipset and other drivers u may need. Eg.printer drivers, then try again.
Previously i had a sony erricson phone and it's SE's software screwed up the usb interface n i wasnt able to connect anythin thru usb mtp. That helped me. Alternatively, if u have system restore on you can try restoring to a date before this all happened.
Also, check your device for any apps or settings that might interfere usb functions like usb debugging altho it's rare. Not sure what you did but you might have semi/permanently broken some settings in the device...if you had an earlier backup which was flawless, try restoring to that first. Remember to play safe when doing all troubleshooting, windows isnt exactly smart with device drivers =< worse case you have to reset both the usb drivers and device if nothing works...
Unrelated but might help http://forum.xda-developers.com/showthread.php?t=2214386
Or
http://forum.xda-developers.com/showpost.php?p=39752670&postcount=5
i faced the same problem last week. what i do is go through step by step like what nexus root toolkit suggest. start from scratch. remove all previous drivers and reinstall. Follow to the letter what it says. So the problem is just probably of a bad driver stuff. Remember to restart too.
put in a new SSD and got Windows 8.1, did a fresh install on a new hard-drive, everything's been working great, My nexus 4 has worked with with ADB./Fastboot and I've been able to transfer files to and from it in MTP mode. Been like that for about 4 days until about 3 hours ago, I had Windows Explorer crash, had to run Task Manager, end the process, and then manually restart explorer.exe My device was plugged in when this happened, and afterwards, I noticed that I could no longer see my Nexus 4 under the Devices & Drives section of "This Computer" (My Computer had a better ring to it lol) First I tried rebooting both my laptop and my Nexus 4, then I tried uninstalled the drivers, rebooting, re-installing, and then rebooting again. Did that like 4 times now, each time re-downloading the drivers, and doing an MD5 hash to create a Checksum, and checking them each time. Also to no avail. ADB shows my device serial number when i enter : ADB Devices, but says it's unauthorized, so if I try anything like: ADB Reboot Bootloader, it says Device is not authorized.
So ! I don't understand wtf is going on. Was working fine before. The drivers are up to date, I just flashed the Official OTA image, and was on the leaked image prior to that. Then earlier this evening I switched to the newest version of the Nexus 5 Port, and everything was still working fine, hadn't made any changes in a couple hours before this happened. When I install the drivers, It acts like it worked. Instead of saying "NEXUS 4" under Other Devices in my Device Manager, it says Composite ADB Interface under Android Devices and MTP under Portable Devices. Sometimes tho the MTP entry will still show the Yellow Exclamation Point. But goes away. Don't know whats up with that either.
Also, it wont let me install drivers unless I am in MTP mode, which Usually you can install them regardless (tho I never tried in Camera mode, I am just assuming about that one) Usually I install drivers without MTP or Camera modes checked, but now if I try it, it says that Windows Cant find the Drivers, even tho I am obviously browsing for them myself and selecting them. And just now I tried updating instead of re-installing them, and it keeps saying that Windows has determined they are the most up to date.
So I am out of I ideas. I even updated windows media player cause that's what fixed my issue on Day 1 of running Windows 8.1 when it wouldn't recognize it at all. So I don't know. Sorry for the long post but I wanted to make sure I got everything in there so hopefully someone can narrow down what the issue is. Cause I've been at it for 3 hours, haven't slept yet, my Nexus 5 gets here today, and I need to get this fixed before I sell it to my buddy. Its brand new, only 15 days old.*
Any thoughts ?*
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
ADB Devices, but says it's unauthorized
Click to expand...
Click to collapse
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
eksasol said:
First, connect your Nexus 4 and use Device Manager to uninstall both MTP and ADB devices, make sure to check the box to delete the driver files as well. Then uninstall any other usb or adb drivers for other Android devices.
Then disable USB Debugging on the phone and get MTP to work first, Windows should be able to install it automatically.
For ADB, Windows 8 will not allow to install unsigned driver. To install unsigned driver, reboot Windows 8 into Advanced startup and press F7 at the menu to disable driver signature (Google it if you don't know how). Although you could install Google USB driver which is signed I think, I recommend using Universal Naked Driver (link in sig.)
You need to authorize it from your phone, when you connect your phone to the PC with USB Debugging turned on, a toast message on the phone will ask you to authorize the device.
Click to expand...
Click to collapse
ok I am gonna try that now. And as far as the part about my phone being unauthorized. I already knew about the notification that pops up, i was waiting for it to happen. Never did tho. Maybe it will happen after I do the rest of what you said. thanks, i will post my results in a min
no matter what i do, i cant get MTP working. When i uninstall the ADB entry in Device Manager it gives me the check-box option for removing drivers as well, but not on MTP. And now it wont even give me the option to uninstall, update, or anything at all, even tho I uninstalled it already so it should at least give me the option to install drivers. Even tho it's showing up in Device Manager as a Portable device, if I look in Printers and Devices, it shows up as unspecified device. Disabled USB Debugging, and all that. it says its working but it wont show up in My Computer>Devices and Drives still. For some reason ever once in awhile it will pop up with the Yellow Exclamation Point tho, only for a brief second tho. other then that, its shows it like it's running correctly. Also, nothing pops up saying that windows is installing drivers when i plug it in. Which in Win 7, XP, etc, it always did. Does this not happen in Windows 8.1 ?
Also, under Driver Details, which is the only option it lets me click on MTP, it says the drivers are from 2006 lol
Update - Just reinstalled the drivers for ADB and enabled USB Debugging, and everything is still saying its working even tho its not. But when I take my phone out of MTP mode it shows up in device manager under "Other Devices" as Nexus4, with a Yellow Exclamation, and it gives me the option to update drivers, so i tried, but it says Windows Can't find my driver. This is very frustrating.
Had this problem aswell, which was caused by the N version of Windows 8 versions.
These versions dont have Windows Media Player istalled, which is needed for MTP to work.
So to fix your problem you need to download that latest Windows Media Player (WMP) from microsoft and install that.
I dont have the N version, I have WMP installed, i mentioend your fix in the OP. Had to update it, and it worked. It was working fine for the last few days, then it stopped working suddenly
double post, sorry. dont know why that happened.
Vouch. Since I use win8.1 (no n version) Mtp doesnt work. I tried all known drivers, disabled driver signature and so on. The only working combination for me is Usb Debugging + PTP. Then I use file manager to cut the files. Airdroid would be an alternative as well.
update - SOLVED * Kind of.....I say kind of cause I still don't know what caused it but apparently Flashing to the Nexus 5 Port fixed the issue lol. I am assuming something pertaining to the way USB connectivity is controlled by Android got corrupted, and a fresh install was in order. Whatever it was, it worked and i am back in business. thanks to all those who attempted to help.
Sent From My Nexus 4 via XDA Premium 4