I'm trying to sideload the new OTA, but for some reason when Nexus Root Toolkit gets to the point where it actually tries to sideload it, ADB disconnects. I went into the driver software and it's a microsoft driver. I've tried replacing it with the Google USB driver but windows just says "Windows has determined this is the best driver for your device" and doesn't let me. Has anyone else had this problem? I've been trying all day.
This worked for me
I had the same problem...I uninstalled the phone in device manager, installed HiSuite then connected the phone and the drivers installed properly. Now it works great. I can't post the link due lack of posts
Koush universal driver
I had the same issue, tried lots of different drivers, installed the google one through the SDK manager, their website, tried the Hisuite thing. The only thing that worked for me was the universal ADB driver by koush. I cant link it because apparently i havent made many posts on this forum or something, but if you google it, you'll find it real quick.
hopefully that works.
dzuck89 said:
I had the same issue, tried lots of different drivers, installed the google one through the SDK manager, their website, tried the Hisuite thing. The only thing that worked for me was the universal ADB driver by koush. I cant link it because apparently i havent made many posts on this forum or something, but if you google it, you'll find it real quick.
hopefully that works.
Click to expand...
Click to collapse
Yeah, either way, it's a driver issue
I had the same issue on Mac computer. I just switched to different USB port and it worked
Related
Hi,
I have been messing with this for a few weeks now.
I have a magic 32B, spl 0004
I don't know how but i got cyanogenmod 4.2.5 on my phone.
But then i tried to use the update app and it fails.
It seems that there are 2 problems.
1. my recovery is still the stock one
2. i just cant seem to get a good connection with my computer.
Every time i try something its waiting for device.
Or with adb devices its an empty list.
i used a windows vista machine and a windows 7 machine
Is there someone who is willing to help me get this done?
I checked threads about, usb drivers, installing adb, installing recovery.img, installing cyanogen.
But there is always a step that just doesn't go according to the manuals.
i was about to give up, but i just really want this to work.
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
justbenjp said:
As you have already stated you have a stock recovery.img on the phone, to get the cyanogenmod updater program to work you need a custom one, the instructions to install this can be found on cyanogenmod.com in the downloads section.
If you are having problems getting the phone to connect to the pc make sure the drivers have installed correctly, you can download them at the link bellow incase you cant find them, by default they dont download with the sdk anymore, dont know why :-|
http://rapidshare.com/files/315790307/usb_driver.rar.html
Click to expand...
Click to collapse
I have tried to install a custom recovery, but when i follow the steps i cant seem to connect to my phone via CMD.
When i check the drivers.. i'm not sure its 100% correct.
I have installed the once before.
and now he doesn't ask me for the drivers anymore.
but neither do i see it in the devicemanager, the way its being described in the manuals.
just something else involving android, but not ADB
i have tried to follow the manual, and threats about how to get the driver right..
but with this, i also have had problems with the steps..
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
justbenjp said:
On your phone go into settings....applications....Development and make sure
you have USB debugging enabled
Click to expand...
Click to collapse
I have done this..
I will try again on a vista machine which i havent used for this yet
anheuer said:
I have done this..
I will try again on a vista machine which i havent used for this yet
Click to expand...
Click to collapse
Great.. it would not install the SDK..
So back on my windows 7 machine..
still getting device not found in CMD - adb devices
connected with usb debugging on..
cant see anything in device manager, but the system also doesnt ask for drivers...
I went into fastboot and then it asked me for drivers..
Now i do have
Android phone - Android Bootloader interface
but in any other situation, it does not show anything or ask anything.
I just keep getting device not found...
so i am new to android and i decided " hey why don't i try to root my nexus" so i tried and i cant get any father that checking if the computer can see my device which it cant for some reason. so i went online i figured out that i don't have the usb driver for android. so after that i tried to down load then and i even installed them and restarted my computer and it still wont work. so if any one can help me with my problem it would be greatly appreciated.
On Home Screen, press menu>settings>applications>development and make sure USB debugging is checked.
What OS you running?
Specs would help, where did you get your drivers? What other software have you tried?
i turned on the debugging and it still hasnt worked
i am running xp. i downloaded the android sdk from here
developer.android.com
i just want to put the modaco desire rom on my phone that my onl reason for wanting to root. i really like the sense ui
I am having a similar problem, so i might as well use this thread instead of creating a new one.
I have a dual boot computer, win7 and fedora, both have SDK. I unlocked my nexus one with windows, as i noticed the commands were considerably easier, or at least they don't work when i plug the linux ones into fedora.
Last night i was going to push the undervolt kernel so i plugged my n1 while in win7, It instantly came up complaining about drivers, which i had already installed and had previously worked, i went to re-install them, and windows says they are up to date, but still no luck recognising the device (Debugging mode is definately on)
So i switched to fedora, no driver pop ups obviously, but when i try to push the kernel through, it does not recognise the device.
In the bootloader it says "fastboot usb" while plugged in.
I can't pinpoint when it stopped working, but the last time i used fastboot was to put the RA recovery, since then i flashed CM 5.0.2, CM 5.0.3.1, the desire rom, and used a nandroid restore to get back to 5.0.3.1
Anyone got any ideas? Without fastboot i am pretty much restricted to flashing .zip files from the recovery.
yeah i cant even unlock mine its so frustrating
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
drbrendin said:
temperbad said:
Me either. I'm coming from windows and flashed the heck out of that. The instructions seem super easy, but the darn thing wont recognize phone to root... and there is no real good instructions on the driver part. Yes USB debug is enabled... sucks cause I want that desire rom, if 10.1 is working that is...[/QUOTE
Yeah I know how you feel its so frustrating I tried all day yesterdAY too
Click to expand...
Click to collapse
I tried all day too like a gazillion times.... and wonder does everyone have driver issues? I tried with my XP computer and windows 7, no go, then I read posts people having the same issue, then they just post " nevermind got it" and didn't even write what they did to get it.......
Click to expand...
Click to collapse
not everyone is a dev
Ok, I have my Nexus One set up so I can use with via Windows 7 (desktop) or Ubuntu (Laptop).
The Linux part is a bit more involved, but since everyone is running Windows (unless I missed something), I will work there.
First of all, your phone needs to be in Dev mode (which was covered earlier).
With the phone UNPLUGGED from the PC, uninstall any previous SDK installs you have and be sure to remove the directory.
Then, install the SDK found here: SDK
Install this SDK and let it complete the install, which will include downloading for a bit. You need to do this since the SDK package above does NOT include the right drivers!!!
Once this has been completed, plug your phone into the computer via USB. Your computer will find a new device, however, it cannot locate the drivers for it. Browse and point the installer to:
DRIVE:\PATH_TO_android-sdk-windows\usb_driver
Don't go any further than this!!
Now, let it do it's thing and you should have a new device in the device manager called:
Android Phone
...|_Android Composite ADB Interface
Now, go to the command prompt and change to the following directory:
DRIVE:\PATH_TO_android-sdk-windows\tools
There, you will find adb.exe
Type:
adb devices
and you should see:
List of devices attached
HT019P801614 device
If not, something got screwed up and would need to dig further to help ya.
Ok ill give this a try once get home from school
nexus one root.
Ok assuming that you have the android sdk installed correctly, try rooting your phone via the superboot method. The first link below has a full detailed guide for rooting the nexus one and I believe has all of the device drivers for those who have not been able to get them running well. If you still have trouble getting the drivers working checkout the second link. Anyone who is relatively new to working with the sdk and is not familiar with working the commands check out the third link. Read the entire thread! it is very helpful.
1) http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
2) http://forum.xda-developers.com/showthread.php?t=613217
3) http://forum.xda-developers.com/showthread.php?t=619153
If you have any questions PM me on xda. I'll try and help in anyway, it took my like two days to actually root my nexus, I wasnt familiar with using ADB and Fastboot to root.
One thing I know I was having problems with since I came from the G1 was that the new SDK has to actually be installed via an .exe now. I was used to it all being in a zip so I kept trying to load up what I thought were the right USB drivers, but they were actually the 1.6 drivers I already had. So make sure to run the .exe that comes with the SDK.
ok so while i was downloading the sdk a notification came up that said that it could not rename the directory. is this bad?
i am having an issue with installing the right driver as well. my computer keeps installing the nexus one as a "mass storage device". i have uninstalled and reinstalled a few times but no luck. i have the phone set to debug mode, using XP btw. any help would be appreciated.
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
My Evo gave me grief for a solid hour when I first got it. Followed the walkthrough here and one of the contingency plans worked like a charm.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Thanks, but it is not a driver problem as the drivers are installed correctly and ADB can see the phone connected.
I tried on 3 different PC's, replaced US cables. everything failed.
I think something is up with my unit which will be going back tomorrow.
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
So it worked fine before you rooted it?
Yes, SuperOneClick is using ADB to push the root files, so i assume ADB worked then.
I am also getting constant device reboots (random) so i think there is a hardware problem. i'll take it back tomorrow.
I had drivers installed, but the set of drivers PDAnet ended up installing for me fixed the issue. Till I get my paycheck, I won't be able to play with it
clubtech said:
Here is a mystery that never happened to me before.
Got the phone yesterday, rooted it and restored my apps.
Today i noticed that when i plug the phone in (USB debugging enabled, drivers from motoroal installed), i can see the device under "Android ADB composite device" but when i use "adb devices" from the command prompt, i get:
List of devices attached
TA20706TVK offline
I am not able to do anything else as the device is offline ?!?
I tried on 3 different PC's running Windows 7, windows 2003 server, windows XP, all with the same results.
Anyone has any idea what's going on?
Click to expand...
Click to collapse
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
I am now on my 4th phone - so will be waiting for things to simmer down before I go back to modding again, but the other 3 have all had the same issue after using the superoneclick to root.
Once root is done all ADB access goes away. Something is amiss.
edit: More specifically my 4th atrix.
airbillion said:
I have the same issue! I had rooted my device and everything was fine. I wanted to try DG's new deodexed rom, but I can't get ADB to work anymore. My device is found but it is always offline. I have tried multiple computers and usb cables with no luck. Is there any solution? What could have happened, is ther something wrong with my Atrix? It was working fine before, but now I can't get adb to get my device "online". I uninstalled the drivers and reinstalled the many times without any luck. Please HELP!
Click to expand...
Click to collapse
I ended replacing the phone as I had other problems with it. Now a adb works fine even after root.
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
SNadler said:
Have you tried to unroot and root again being sure to click ause third party apps before you reboot?
Click to expand...
Click to collapse
It does not solve the problem.
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
airbillion said:
Is this a software or hardware problem? I lost adb after root and i have had no getting it back. I dont want to have to exchange my device for another, but i might have to. Any other ideas?
Click to expand...
Click to collapse
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
clubtech said:
I am not sure. ADB died on my 1st device after rooting it BUT the device was also having other issues of random rebooting at least 4-10 times a day. So i replaced it and the 2nd device does not have any issue and i rooted it the same way.
I have ADB working and it does not have the random reboot the issue.
The only thing i did not do on the 2nd device is used SuperOneClick to enable none market apps like i did with the 1st device.
I am not sure if that's what made the difference. I did enable sideloading by manually editing the settings.db file.
Click to expand...
Click to collapse
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
airbillion said:
I havent had any hardware problems at all with my atrix. I did enable sideloading via the superoneclick though. The loss of adb pisses me off. I did hard reset my device once, but i did that because adb wasnt working and i thought a hard reset would fix it. I hope there is a fix soon though, i hate having to exchange my atrix for another one. Maybe something happened to a system file that enables adb?
Click to expand...
Click to collapse
I tried restoring my device to factory default several times. It did not solve the ADB problem and not my random reboot problem (even with zero 3rd party apps installed).
I tried installing ADBWireless from the market - no go.
I googled and found a command to run via local terminal to force ADB to stay up - no go.
I finally came to a conclusion that a) I have bad hardware because my device was rebooting b) i can't fix the ADB problem without a full SBF file which we don't have.
Went to at&t, got it replaced. no more reboots. rooted with superoneclick and did not do the sideload fix from that app.
Then i manually edited the settings.db file to allow sideloading and been running fine ever since.
Clubtech,
Thanks for the file! It works for me!
Here is a post on the fix: http://forum.xda-developers.com/showpost.php?p=11738847&postcount=1
Can anyone explain this for a noob? i just want aRoot to work and the HDMI cable thing to work... the oneclickroot worked but nothing else will and i think it is because ADB is not recognized...
]Hey everybody,
i wanted to switch from cm9 to cm10. after i managed to return to stock rom and recovery and successfully updated to stock ics, still with root available, i cannot connect my tpt to my pc, which is necessary to install adb drivers to further load the new cwm.
i've been trying and reading posts for several hours now, but there is just no way the tpt gets recognized in win7. i always get the message:
'unknown device'. device has been stopped. code 43.'
Click to expand...
Click to collapse
so far i've tried everything i could find in several posts out there, and yes, sync with pc is enabled as well as usb debugging.
i tried to install android_winsub.inf (both from lenovo adb driver package and the android sdk) and edited it as suggested in some other posts, but still no luck.
i also did a reset and tried it with two other pcs - still no luck.
any ideas?
danjac said:
]Hey everybody,
i wanted to switch from cm9 to cm10. after i managed to return to stock rom and recovery and successfully updated to stock ics, still with root available, i cannot connect my tpt to my pc, which is necessary to install adb drivers to further load the new cwm.
i've been trying and reading posts for several hours now, but there is just no way the tpt gets recognized in win7. i always get the message:
so far i've tried everything i could find in several posts out there, and yes, sync with pc is enabled as well as usb debugging.
i tried to install android_winsub.inf (both from lenovo adb driver package and the android sdk) and edited it as suggested in some other posts, but still no luck.
i also did a reset and tried it with two other pcs - still no luck.
any ideas?
Click to expand...
Click to collapse
Hi, are you sure that you heve correct USB IDs added to adb driver (android_winsub.inf)? I found out that it changes when I installed different CWM and CM version. I had similar problem recently.
HaliG1 said:
Hi, are you sure that you heve correct USB IDs added to adb driver (android_winsub.inf)? I found out that it changes when I installed different CWM and CM version. I had similar problem recently.
Click to expand...
Click to collapse
well, i read about it. it was said that one should just open the 'details tab' (device manager...) and read out the id when plugged in. unfortunately, i get nothing there. so the problem must be somewhere else.
but nevertheless, thank you for your hint/idea.
I have seen this issue before when i have not used the stock USB cable supplied by Lenovo.
dcshoecomp said:
I have seen this issue before when i have not used the stock USB cable supplied by Lenovo.
Click to expand...
Click to collapse
I tried several cables, ports and pcs... nothing worked. By now I believe it's my loose mini-usb-port, it's probably still ok for charging the tablet but not for data transfer - it is the only explanation i can think of so far. So sooner or later I might need the dock.
Nevertheless, I managed to install the new cwm and cm10 by using the terminal emulator. So there is no urgent need to get that working again.
Have you tried a wireless ADB app?
This worked for me when ADB via USB cable quit working after flashing a new ROM.
Sent from my LG-VM670 using Tapatalk 2
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Ste_JDM said:
Howdy,
My question is, does Odin not work with Windows 8.1 in general? If you have managed to get Odin to register that a device has been connected was there any special way you managed to get around this?
Some background:
I mentioned this issue in the noob friendly section but it seems I am the only one having the issue there. So I'm asking around here if anyone has had this issue under Windows 8.1. All I wish to do is flash the unbranded firmware to remove carrier bloat-ware.
I've downloaded Odin 9.07/9/10 and have the same result, that the device just does not appear.
System is running Win8.1 and has driver signature disabled.
Kies is installed and picks up the device without error
Phone has USB debugging on and appears under 'Device Manager' when in Download mode.
I've had a look around and found nothing with this issue, watched folks do it in various videos too but they were using Win7.
Thanks for reading!
Click to expand...
Click to collapse
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Install the Samsung usb drivers!
Odin works fine on my windows 8.1 computer.
ernani said:
My guess is that you need to install Samsung's USB drivers for your device. Have a look at the instructions at this, and this page. I suspect that you haven't installed SAMSUNG's Android ADB Interface Driver (look at OP of the second thread), which is used by Odin if I'm not mistaken to talk to your phone and push the images you want via ADB.
Click to expand...
Click to collapse
That was it. Thanks so much! I removed Kies, rebooted, installed the driver from samsung and rebooted again, after that Odin worked like a charm.