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.
ok, I'm not really a noob but I'm having a horrible time w/ drivers for my Epic.
I had almost a 3 or 4 day long project to get drivers to load and work for my samsung moment..
I have uninstalled them and am now trying to get drivers to install and work for my Epic so that I can 'one click root' and install clockwork mod recovery.
My dilemma is, the drivers that are available here for the Epic seem to install fine. After I restart the computer, I put the phone in USB debug mode, then plug it in.
The drivers attempt to install, the computer recognizes the "Samsung SPH-D700" but in the right side of the window it says "failed"...
been trying all weekend to get this working.
I'm using Win7 64bit Ultimate FWIW..
When I had this problem w/ my samsung moment, Part of the culprit was the USB cable so i ran down to radio shack and purchased a $20 cable out of necessity. I'm using that same cable as well. The one that came with the phone is at work and unavailable at this time.
Thanks for the help
http://randomtechinfo.com/epic/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
I had better luck with these drivers in xp than the other two that were "confirmed" working. They worked once, then I removed them and reinstalled moment flashing software, then removed that and tried reinstalling the drivers. It wasn't working. There was something on the phone the drivers wasn't recognising. I flushed them out and installed the link above and it worked like a champ. I don't know if you'll have any luck with 64bit os. It's worth a try. Also, did you try changing to a different usb port?
Yeah I tried using different USB pets and no luck.
Are you using the stock cable that came with the phone ?
I'll try the drivers from the link you posted and report back. I can always run then in compatibility mode if need be.
Thanks.
Sent from my SPH-D700 using XDA App
Ive tried the one that comes with the evo. It's flaky but sometimes works. The one that usually always works, don't know where the epuc one is, is the over prices official one at a corporate sprint store.
Anyone know why? Is this because of the bootloader on 4.2 that Adb is able to see it. I plug in my 4.2 Nexus 7 and it's detected etc by the system. The 4.1 device is not really seen. I can see the composite device but no portable thing saying Nexus 7.
It's been a while since I flashed up to 4.2. Do I need the bootloader on there first or can I just nuke the N7 and flash a rom and worry about the bootloader after? I'm figure the Adb I got, something like 1.0.31 or something can't talk to older 4.1... That's my guess.
I am using WUGS too and did the driver test. Works perfectly on my 4.2 N7 but nothing at all on the 4.1 N7...
install the universal_naked driver through windows device manager
http://forum.xda-developers.com/showthread.php?t=1766220
making sure you got the latest android ADB folder wouldnt hurt either.
http://developer.android.com/sdk/index.html#win-bundle
the bootloader/rom/etc wont affect the computer reading the tablet or not.
jt.one said:
install the universal_naked driver through windows device manager
http://forum.xda-developers.com/showthread.php?t=1766220
making sure you got the latest android ADB folder wouldnt hurt either.
http://developer.android.com/sdk/index.html#win-bundle
the bootloader/rom/etc wont affect the computer reading the tablet or not.
Click to expand...
Click to collapse
Thanks for links and info.
Sent from my Nexus 7 using Tapatalk 2
Hello.
I am having a problem with ADB and Bootloader drivers with my Nexus 4.
I've been sitting here the whole day trying to work it out but no luck (no tutorial helped me from google or xda)
Basically, the problem is ADB isn't working correctly and bootloader drivers are not recognized as well.
When I connect my device to my PC it finds the right driver (Android Composite ADB Interface) but when I try to use "adb devices" it returns "xxxxxxx(device serial number) offline"
When I go to bootloader mode the driver could not be found nor installed manually (when I direct to the directory with the driver it doesn't find it)
I want to downgrade 4.3 to 4.2.2 and cannot do it without the bootloader driver or ADB.
Strange thing is though, I have another Nexus 4 device with 4.2.2 (PAC Rom) and it's working flawlessly from the same computer.
1 more thing is, I've been trying to get to the point where I can approve my pc (RSA) without luck - been trying to delete the .android directory from my PC and also /Android/Misc/ADB directory from the phone, but nothing let me to that stage again.
I've tried 3 PCS, 1 Mac and no luck with anything.
Tried with Pac Rom and PA399 RC2 - AK KERNEL and regular ROM kernel.
No luck with anything.
What can I do that I haven't done yet?
Please Help.
Guy.
well i've been sitting and investigatin the whole day today as well without any luck.
already thinking about a malfunction with ths usb connection on the phone's side as the other nexus 4 device connects just fine with ADB, Fastboot etc.,
Can anyone shad some light?
Thank you!
Well, If anyone is experiencing the same issue I have found a solution.
Flashing a bootloader resolves the issue.
Hope this helps someone.
GuyZapPa said:
Well, If anyone is experiencing the same issue I have found a solution.
Flashing a bootloader resolves the issue.
Hope this helps someone.
Click to expand...
Click to collapse
I'll just point out that while flashing a new bootloader resolved the issue the op was having. What he has done is probably bypassed the problem.
The issue will not have been on his phone but with a driver conflict on his computer.
By flashing a new bootloader, the hardware id's will probably have changed allowing the correct drivers to function this time.
To op
Enabling hidden devices in device manager will probably show a few hidden android devices which was the cause of your initial problems
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I'll just point out that while flashing a new bootloader resolved the issue the op was having. What he has done is probably bypassed the problem.
The issue will not have been on his phone but with a driver conflict on his computer.
By flashing a new bootloader, the hardware id's will probably have changed allowing the correct drivers to function this time.
To op
Enabling hidden devices in device manager will probably show a few hidden android devices which was the cause of your initial problems
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, I am not sure that flashing the bootloader bypassed the problem, I am pretty sure it solved it.
I am saying that because I have deleted every possible driver, reinstalled, did not help.
Connected the phone to a new virtual machine I've created and was having same problem.
Tried it on a Mac, Same thing.
I've been dealing with this for quite some time, so I'm pretty sure flashing a bootloader solves the problem for people having it (not too many, as I've searched on the subject pretty much everywhere and no one ever said to flash a bootloader.)
I do apologise. I wasn't aware you had tried connecting via different os's
99% of these cannot connect issues are driver related.
Looks like you are the unlucky 1%
Though I am glad you got it sorted.
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I do apologise. I wasn't aware you had tried connecting via different os's
99% of these cannot connect issues are driver related.
Looks like you are the unlucky 1%
Though I am glad you got it sorted.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I thought just like you, and every tutorial or explanation on the web points to a driver problem.
It's all good, and as I said, hope it'll help others that suffer from the same problem
Good week.
Guy
Before anyone complains id like to say that i have done research into this and searched through the forums for a thread on the same matter but i have not found one.
I have recently purchased a Nexus 4 (the most well designed and premium feeling phone ive ever owned) running completely stock unrooted android 5.0.2, however upon connecting it to two different laptops i have been unable to access my files on the device or connect to the nexus root toolkit to root it.
device manager tells me that it recognises the device but the drivers are not installed. all the phone does is charge when its plugged in unless i turn on usb debugging and this only makes the noise that it makes when any device is inserted.
any help with this will be much appreciated, cheers
smiley118118 said:
Before anyone complains id like to say that i have done research into this and searched through the forums for a thread on the same matter but i have not found one.
I have recently purchased a Nexus 4 (the most well designed and premium feeling phone ive ever owned) running completely stock unrooted android 5.0.2, however upon connecting it to two different laptops i have been unable to access my files on the device or connect to the nexus root toolkit to root it.
device manager tells me that it recognises the device but the drivers are not installed. all the phone does is charge when its plugged in unless i turn on usb debugging and this only makes the noise that it makes when any device is inserted.
any help with this will be much appreciated, cheers
Click to expand...
Click to collapse
Google 15 second adb install xda. That will install drivers as well as adb and fastboot. You don't need nrt to root it. Flash the twrp image in fastboot, then flash supersu in twrp. http://techerrata.com/browse/twrp2/mako. http://download.chainfire.eu/693/SuperSU/BETA-SuperSU-v2.44.zip
Sent from my Nexus 9 using XDA Free mobile app