Database Develop

Nexus One ADB Driver Endless Reinstalls

I have 2 Nexus One's. The first was rooted and I had the ADB USB driver (v3) installed on my Windows XP Pro SP3 desktop and all worked fine.
I now have a second Nexus One. I rooted it, and after turning on "USB debugging" and wanting to use it with ADB, the driver USB installed again. But now I get constant "Found New Hardware Wizard" install loops, for both phones with "USB debugging" turned on.
Every time I plug either phone in, or reboot, Windows wants to reinstall the ADB driver. Right after it completes a driver install it wants to do it again.
Solutions I've tried; I have rebooted after install, uninstalled the drivers from Device Manager, deleted the drivers manually from the registry, removed any possibly associated hidden drivers that were marked error in Device Manager, and combinations of the above in various order.
I know that USB driver install loops on Windows can happen to any type of device, not just the Nexus, but in my case it's only on the ADB driver for Nexus One.
Can anyone suggest what I can do other than what I listed to stop the ADB driver endless install loop, or what is causing it?
Thank you.

ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...

johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
No, I haven't found a solution to this yet. And you are the only person here that has replied.
I did contact Google and HTC and asked for their help. But since the phone is rooted I got the expected replies from both, that rooting violates warranty so they refused to help. I was expecting that, but have heard that the occasional tech support person at Google will still offer support within reason. But not in my case.
If and when I figure this out, I'll post it here to help you out.

johng75 said:
ever find a resolution for this? im having the exact same issue.
my phone was purchased used, already rooted and bootloader unlocked...
if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...
i can see the phone through ADB thou....
ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
Click to expand...
Click to collapse
Hi JohnG75,
Just wanted to let you know my constant ADB driver reinstalls have stopped. But unfortunately I have nothing constructive to point out as a solution. I spent hours online researching for a possible solution, and found nothing worthwhile yet. I've posted in several places and got no helpful replies other than trying System Restore and going back to a point before this happened. Of course that's hardly a guaranteed fix, plus you loose any other updates and installs you have made since then.
In my case, I left "USB debugging" turned off on my phone since I wrote you last, and the only thing that has changed system wise for me, is I have installed 2 unrelated device drivers since, and MS has pushed out a security update. So today when I turned "USB debugging" back on in the phone, it did a single device install, and it didn't repeat. So hopefully this resolves it for me.
If I were to take a guess as to what appears to have solved it in my case, I would say it was the new unrelated device driver installs. Perhaps it cleared whatever was wrong in the device driver system. So maybe if you were to install some new device driver you need, or uninstall an existing one, reboot and then reinstall that same device driver, perhaps it will clear whatever is messed up in your device drivers.
Sorry I can't be of more help, and my suggestion is only a guess based on my only recent system changes.
There is very little documented solutions to this problem out there, only lots of people that have complained about the same type of problem, with every sort of device you can think of. And the solutions documented are always specific to those exact devices.

[Q] At wits end!! Please Help.

OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!

You could try on another computer which doesn't run Vista

tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...

His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..

tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.

[Q] AT&T HTC One COMPLETELY wiped...

a friend of mine went out and got the HTC One, we rooted it and put on a nightly of CM 10.2 - and the phone worked relatively well, very well in fact, except the MMS/Group messaging was causing the phone to lockup and reboot. we've had a group message going on for an eternity involving a few of our friends, so many times a day this would happen.
not knowing what to do, i suggested he download a new rom, the stable or the latest nightly, and erase everything, and reinstall. somewhere in the process he erased everything - including the new rom, the phone is completely blank and in a boot loop. we can boot into fastboot or into the recovery.
and, we are Mac guys, except for an older Vista laptop i have. (to give you an idea on it's age, it has a 25gb hdd).
when we had first rooted it, i used MTP to copy the new rom over to the phone. the stock rom was still in place, the xfer went fine. but now there's no rom on the device, MTP doesn't work, the computer sees it as a 'One' but has no driver, and i'm at a bit of a loss.
i have tried to install the HTC SyncManager to get the phone to connect to my Vista machine with no luck, every time i connect Windows tries to look for a driver and it fails. somewhere in the forums i found a 'universal driver kit' which said it covered the HTC One (called it a Google Nexus Device, but recognized it at least).
however, my admittedly weak knowledge of fastboot and adb has proven not enough to get a new rom on the phone. i don't know if it's drivers or my lacking skillset, and i'd love any suggestions on taking a completely wiped HTC One with Koush's CWM on it, and getting a rom on it.
thanks.

dorf71 said:
a friend of mine went out and got the HTC One, we rooted it and put on a nightly of CM 10.2 - and the phone worked relatively well, very well in fact, except the MMS/Group messaging was causing the phone to lockup and reboot. we've had a group message going on for an eternity involving a few of our friends, so many times a day this would happen.
not knowing what to do, i suggested he download a new rom, the stable or the latest nightly, and erase everything, and reinstall. somewhere in the process he erased everything - including the new rom, the phone is completely blank and in a boot loop. we can boot into fastboot or into the recovery.
and, we are Mac guys, except for an older Vista laptop i have. (to give you an idea on it's age, it has a 25gb hdd).
when we had first rooted it, i used MTP to copy the new rom over to the phone. the stock rom was still in place, the xfer went fine. but now there's no rom on the device, MTP doesn't work, the computer sees it as a 'One' but has no driver, and i'm at a bit of a loss.
i have tried to install the HTC SyncManager to get the phone to connect to my Vista machine with no luck, every time i connect Windows tries to look for a driver and it fails. somewhere in the forums i found a 'universal driver kit' which said it covered the HTC One (called it a Google Nexus Device, but recognized it at least).
however, my admittedly weak knowledge of fastboot and adb has proven not enough to get a new rom on the phone. i don't know if it's drivers or my lacking skillset, and i'd love any suggestions on taking a completely wiped HTC One with Koush's CWM on it, and getting a rom on it.
thanks.
Click to expand...
Click to collapse
1. Download Parallels Desktop for Mac & a copy of Windows 7 x86 (torrents available)
2. Install Android SDK to Windows C drive (exactly to C:/)
3. Download the AT&T RUU here to C:/. (The RUU is an .exe you run with the phone connected to pc in recovery to flash it.) Note: you may run into errors once or twice flashing it, but keep trying and it should eventually work.
4. Connect phone to pc and boot into recovery
5. Run the RUU you downloaded
6. After you finish the flash, reboot your phone if it doesn't automatically.
7. Your phone should now have stock AT&T running.
I hope this helps. -Mike

[Q] HTC One Driver Problems

Basically, I have posted this exact same problem here months ago, but with not a lot of help. I came here to get help and I intend of leaving with a bit of some. Basically, I rooted my HTC One, turned S-On, and finally installed Cyanogen Mod. Everything was working for the most part. I remember being able to attach my phone to my PC and being able to transfer files over to my phone. Recently that has been working out so well. I try to transfer files from my PC to my phone, such as music/videos/etc, but my phone doesn't show up. I can go to device manager and see my HTC One under other devices with the caution triangle, so basically my device is read to be connected to my PC but is lacking the drivers to use it. Like I said before, I have posted this problem on other forums before, and I have been sent the link to the drivers. I've installed HTC drivers, USB drivers, HTC One Sync, and so much more, but none of that has worked. All that happens is that my phone will connect to my PC, charge, be noticed by the PC but is completely unusable from PC to phone. On the phones side, it's 100% okay. No problems other than the simple nightly bugs, but I know it's the ROM version I am using. I reverted to the last known stable Cyanogen Mod, and the one previous to that. That hasn't fixed the problem as well. I'm running out of idea's and I'm just looking for some help. If you can help, rather then posting a link for drivers and thinking I'm retarded, please do so. I will appreciate it to the fullest. As for that, that is all I have to say. Please help, and all help is appreciated.

PlasticSandals said:
Basically, I have posted this exact same problem here months ago, but with not a lot of help. I came here to get help and I intend of leaving with a bit of some. Basically, I rooted my HTC One, turned S-On, and finally installed Cyanogen Mod. Everything was working for the most part. I remember being able to attach my phone to my PC and being able to transfer files over to my phone. Recently that has been working out so well. I try to transfer files from my PC to my phone, such as music/videos/etc, but my phone doesn't show up. I can go to device manager and see my HTC One under other devices with the caution triangle, so basically my device is read to be connected to my PC but is lacking the drivers to use it. Like I said before, I have posted this problem on other forums before, and I have been sent the link to the drivers. I've installed HTC drivers, USB drivers, HTC One Sync, and so much more, but none of that has worked. All that happens is that my phone will connect to my PC, charge, be noticed by the PC but is completely unusable from PC to phone. On the phones side, it's 100% okay. No problems other than the simple nightly bugs, but I know it's the ROM version I am using. I reverted to the last known stable Cyanogen Mod, and the one previous to that. That hasn't fixed the problem as well. I'm running out of idea's and I'm just looking for some help. If you can help, rather then posting a link for drivers and thinking I'm retarded, please do so. I will appreciate it to the fullest. As for that, that is all I have to say. Please help, and all help is appreciated.
Click to expand...
Click to collapse
Ok,
I think the best thing we can to in this case is the classic troubleshooting.
Try different USB Cables, slots on your PC, DON'T connect it to a USB HUB (I think you already know that.. I just mentioned it to ensure that)
Make a backup and flash the stock Sense ROM
If you can get a connection to your PC .. Cyanogen causes this issue
That was to determine wheter it's your phone or your computer that causes this issue. Pretty basic.
Uninstall your drivers from the device manager interface
Uninstall everything that is related to your HTC One(HTCSync, maybe Kies or other programs like this, Every driver)
Now, make a registry clean to reinstall everything on a clean way
Use Wise Registry Cleaner
Proceed a computer reboot
Now, download the latest version of HTC Sync
Install it with every driver component.
Then uninstall HTC Sync WITHOUT the drivers
Plug in your phone and wait until other drivers are installed
If that's done, try if the connection works

[Q] Help... Please. HTC One M7 not connecting to computer after wipe

I know this is not really what this website is designed for but I could really do with your help as the Pros!
Okay, so I wiped my HTC One M7 because I wanted to put a different custom ROM on there, no big deal, done it a 100 times right? Well I guess I must have done it wrong this time (Maybe I ticked too many boxes?) because this time it completely formatted my phone, I mean, including the TWRP back up restore points and all the ROM zips I had in their own little folders on my internal SD card. Anyway, no big deal I just plug it into the same computer I always use (this was actually the 3rd time I had wiped and put a new ROM on today as I am just trying new ones :good: so I know the PC is fine) and it comes up with "Installing driver" but instead if it being called "HTC One M7" or whatever it usually says it just says "Android". At this point I am starting to panic a tiny bit... Anyway after about 3 min it fails and "Android" has changed to "htc MTP Device" and I cant get on to it put a ROM on there to give it a OS.
So! Troubleshoot mode activate!!!!! I start Googling, try a few different solutions, couple of Cab file installs and the like but nothing! So I un-install everything HTC related: the HTC Sync Manager and the HTC Driver Manger and even the APKs I had... Everything! An then unplug my phone and start installing them again, plug in the phone and..... NOTHING!! Exact same thing happens. I even tried using a different computer, then installed all the HTC driver stuff on it and it still didn't work. So I start to cry a little bit but then I remembered something I did for a few Salesmen that worked for the company I work for a few years ago! They wanted to get data off a USB stick and onto their Samsung tablets, I bought them a USB Female to Samsung port and it saw it as another data drive, will I have to do that with a USB Female to OEM cable? Will that even work? As it is still sorta seen as a HTC so at least it knows what it is, I refuse to think that it is done for!... Is it?

TheAnarchyRule said:
I know this is not really what this website is designed for but I could really do with your help as the Pros!
Okay, so I wiped my HTC One M7 because I wanted to put a different custom ROM on there, no big deal, done it a 100 times right? Well I guess I must have done it wrong this time (Maybe I ticked too many boxes?) because this time it completely formatted my phone, I mean, including the TWRP back up restore points and all the ROM zips I had in their own little folders on my internal SD card. Anyway, no big deal I just plug it into the same computer I always use (this was actually the 3rd time I had wiped and put a new ROM on today as I am just trying new ones :good: so I know the PC is fine) and it comes up with "Installing driver" but instead if it being called "HTC One M7" or whatever it usually says it just says "Android". At this point I am starting to panic a tiny bit... Anyway after about 3 min it fails and "Android" has changed to "htc MTP Device" and I cant get on to it put a ROM on there to give it a OS.
So! Troubleshoot mode activate!!!!! I start Googling, try a few different solutions, couple of Cab file installs and the like but nothing! So I un-install everything HTC related: the HTC Sync Manager and the HTC Driver Manger and even the APKs I had... Everything! An then unplug my phone and start installing them again, plug in the phone and..... NOTHING!! Exact same thing happens. I even tried using a different computer, then installed all the HTC driver stuff on it and it still didn't work. So I start to cry a little bit but then I remembered something I did for a few Salesmen that worked for the company I work for a few years ago! They wanted to get data off a USB stick and onto their Samsung tablets, I bought them a USB Female to Samsung port and it saw it as another data drive, will I have to do that with a USB Female to OEM cable? Will that even work? As it is still sorta seen as a HTC so at least it knows what it is, I refuse to think that it is done for!... Is it?
Click to expand...
Click to collapse
looks like a driver issue. uninstall everything and install HTC drivers manually. See FAQ #2 of nkk71's guide (linked in my signature). Once your drivers are fixed, flash latest twrp version 2.8.6.0 (assuming you have the M7 GSM). Boot in twrp 2.8.6.0 main menu, you'll be able to see your phone storage from your computer like if it was a usb stick. Drag and drop your rom.zip or your nandroid backup and flash it or restore it (as applicable).

alray said:
looks like a driver issue. uninstall everything and install HTC drivers manually. See FAQ #2 of nkk71's guide (linked in my signature). Once your drivers are fixed, flash latest twrp version 2.8.6.0 (assuming you have the M7 GSM). Boot in twrp 2.8.6.0 main menu, you'll be able to see your phone storage from your computer like if it was a usb stick. Drag and drop your rom.zip or your nandroid backup and flash it or restore it (as applicable).
Click to expand...
Click to collapse
Thanks for getting back to me, I tried that but I cant install the driver manually either, it comes up with the attached error.

TheAnarchyRule said:
Thanks for getting back to me, I tried that but I cant install the driver manually either, it comes up with the attached error.
Click to expand...
Click to collapse
Okay I have fixed it!!!! I had to plug it in at the TWRP stage and then I had to change its driver setting to a "General USB Storage Device" then it activated and renamed itself to "One" and dropped down into the USB Controllers menu. Now I can browse it and put a ROM on it!
Thanks for your help!