I'm trying to root my nexus 7 with nexus root toolkit but I keep getting the ADB not found even tho the drivers are installed I tried all 3 driver installs that nexus tool kit provides and followed the instructions, but still can't get it to work uninstalled everything a few times and retried a few times and still nothing, so I don't know what I'm suppose to do. I even tried asus drivers and other drivers to see if it would work but still not luck.
PDAnet drivers have worked 100% for me. Google them and try it, they work perfectly in fastboot, adb and with the Nexus toolkit. Does install a little program that's easily disabled/uninstalled. The drivers will still be there if you uninstall it. Good luck
Sent from my Nexus S using xda premium
I'm afraid if your USB debuging is turned on or what. Does your laptop find the device as a media device??
You should've asked this question under the Nexus root toolkit thread as you are facing a problem regurding it. Next time please try to read the forum rules.It's better not to start a new thread whten there is already thread about it. And please try to make a good use of the search option.
Related
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.
hi,
im in need of help, i just bought my nexus 7, within the first hour of course i wanted to unlock, root and flash CWM on it, this is what happened, i downloaded the files necessary, went on cmd on my computer and fallowed some simple directions and i unlocked it, the problem started when i couldnt copy and paste the CWM file onto my nexus 7 it just wouldnt copy, so i went to do install the drivers for my nexus 7 on device manager, and my computer sees my nexus 7 as my previous tablet samsung tab 2, now after trying to make it work, my computer wont recognize the device at all,
so im trying to get it back to stock, factory rom when everything was working okay, because i think i somehow renamed the device as my old tablet samsung tab 2, im suprised as it still works fine, however i cant transfer files over, and i cant root because the toolkit program on my computer wont recognize the nexus 7, if there is a simple method to fix this problem or bring my nexus 7 to the way i bought it please do tell, it will be highly appreciated,
Thanx
It sounds like the drivers got messed up.
Get http://forum.xda-developers.com/showthread.php?t=1766475
it includes a tool & instructions for fixing the drivers under the "full driver installation guide".
You can also download a stock image here https://developers.google.com/android/nexus/images#nakasi
I think uninstalling the previous drivers with USBDview (step 1 in the full driver installation guide) will help.
Note that while it says "guide" it includes buttons for launching included programs and scripts.
Use Wugs toolkit, click on the big button to install drivers manually/automatic I think is how it's labeled.
One of the first step offers a tool to view and delete drivers and it even specifically tells you which drivers to delete to prevent it being misrecognized and/or having conflicts.
Once you've uninstalled those just follow the instructions to install the correct ones. Once they're uninstalled you will see it in device manager as something else until you install the new drivers.
Sent from my ADR6425LVW using xda premium
Well unlocking the boot loader is possible but when rooting the nexus 7 gets stuck in fastboot when its suppose to be rebooting its self oh well I been at it all night so now I realized its impossible
Sent from my Nexus 7 using xda app-developers app
Use the toolkit, worked great for me. I couldnt get the adb right so I tried that. My nexus 4 was easy without the toolkit though..
Sent from my Nexus 4
I get a error saying failed <remote: <>
Sent from my Nexus 7 using xda app-developers app
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
I'll just go to yahoo answers I'll have more help there
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If you unlocked the bootloader and you're having trouble rooting your device then I don't see you being able to relock the device either, which is critical to do before returning it as technically an unlocked device is out of warranty.
And you say no one is helping you, but you haven't provided any information at all. We have no idea what you did to even cause that error, and you were recommended just to use a toolkit if you want, as that is an easy approach, and you haven't responded on whether you have done that either.
Exactly, how is anyone supposed to help if you don't tell us what you did.
How did you unlock fast boot? What did you try to get rooted?........etc
User is informed of multiple posts. So hopefully, with your help, the root issue can get resolved.
User MUST tell people exactly the steps taken to replicate the error. Including PC type and Operating System.
I hope we do not see duplicated posts anymore.
So if some of you more experienced users, can do some "hand holding" and walk him through the steps, then it will be appreciated. As clearly, he has issues on his own.
Do it for XDA...
MD
bftb0 said:
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
Click to expand...
Click to collapse
I agree 100% on Toolkits
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
arclight25 said:
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
Click to expand...
Click to collapse
Yeah, this was my problem.. That's the only reason I used the toolkit. It wouldnt install right after downloading USB driver through SDK . got me pissed off and uninstalled every driver, and installed my nexus 4 all over also. Some how that one went easy..
Sent from my Nexus 4
LOL op went to yahoo answer, hilarious!
If he is still reading this, USE THE GOD DAMN TOOLKIT FFS, its pretty much idiot proof.
Yea, toolkit is the only way to go.
I think he is stuck in the same place I am stuck in. Whenever I get to the "Reboot Bootloader" in the Toolkit, it fails to go any further. I've made a thread about it here: http://forum.xda-developers.com/showthread.php?p=37524971
The toolkit isn't for everyone, unless of course I'm doing something wrong.
as long as toolkit detects your device, you can simply flash the google image and have everything reset, i dont see how that isnt for everyone honestly......
I used Wugfresh's toolkit and everything worked easily. I dont know any other way to do it, and the toolkit makes it easy for Gnex or Nexus 7.
My PC couldn't see my nexus and I noticed this problem before I knew of an update and yet the update was that same day....
Anyhow the PC wouldn't see the nexus but every other device it does see. We're talking mint 13 mint 11 win7 and Xp... All saw the device prior. So I couldn't get the 4.3 update because fastboot didn't work either. I brick proofed my options prime if anybody knows what that is like you know that I know drivers and fastboot lol. So anyway I need drivers I think so I delete them and reinstall ..we forgot what the first attempt looked like but after trying many times and using the nexus tool kit to delete all the old drivers or installed drivers I then reinstall with error. It reads windows could install driver properly or close to that and the device was labeled as nexus 4 adb but it had a exclamation mark in yellow below it and it didn't work. Hard to believe that it can't be seen on Linux at all of course I don't know the tricky tricks I usually plug it in and boom it ask me what I want to do with it and no now nothing.. Also notable is the fact that I was on stick type Roms and then went to cm10 with LTE enabled and of course older radios since then it seems no connection. Maybe it's my cord but I tried two... I hope it a cord issue. . I
Sent from my Nexus 4 4.3 ota with no root now and no recovery at all using xda premium
Edit. After shining my led light into the end of the cord I only can see 4 of the 5 prongs inside the device end of the USB cord. So I guess that's my problem which sucks cause I deleted the drivers I installed before. Oh well... Have 4.3?
Hi,
I'm currently ran into a very frustrating driver problem with my nexus and i was looking for some help.
I an having trouble with my nexus when i was in the middle of rooting it i had just unlocked it using Wugfresh's root toolkit when the drivers i used were no longer recognized it as as an ADB device and i couldn't carry on my rooting, i have tried reinstalling the drivers multiple times and it doesn't work and it has gotten to a point where it names it as unrecognized so i cannot even transfer files to it anymore, could anyone help me.
P.S. if you want more details about what i did ask me.
Benthrax said:
Hi,
I'm currently ran into a very frustrating driver problem with my nexus and i was looking for some help.
I an having trouble with my nexus when i was in the middle of rooting it i had just unlocked it using Wugfresh's root toolkit when the drivers i used were no longer recognized it as as an ADB device and i couldn't carry on my rooting, i have tried reinstalling the drivers multiple times and it doesn't work and it has gotten to a point where it names it as unrecognized so i cannot even transfer files to it anymore, could anyone help me.
P.S. if you want more details about what i did ask me.
Click to expand...
Click to collapse
Ran into same problem with this ****Wug's thing. Trash it and use Skipsoft Unified Android Toolkit instead. Took me a long time to erase all traces of Wurst. You need to uninstall and delete the Wurst' driver in device manager for Skipsoft to work.