I think I already know the answer to this, but figured I would ask anyway.
I have the Nexus 7 tablet with 4.1.1 and Build Number JRO03D, and using [Toolkit] Nexus Root Toolkit v1.5.2.
There are only two options for the N7 tablet, [JRN84D] and [JRO03C], I'm taking a guess that I will not be able to root until the tool kit is updated, correct?
I have the SDK installed with the following options:
Toolkit Error for ADB Device:
Required 64-bit Drivers
DSoS said:
I think I already know the answer to this, but figured I would ask anyway.
I have the Nexus 7 tablet with 4.1.1 and Build Number JRO03D, and using [Toolkit] Nexus Root Toolkit v1.5.2.
There are only two options for the N7 tablet, [JRN84D] and [JRO03C], I'm taking a guess that I will not be able to root until the tool kit is updated, correct?
Click to expand...
Click to collapse
Please close this, I figured it out.
I had missed the comment about the 64-bit drivers.
Drivers Tip:
If you are getting hung any of the processes and you are on a 64bit operating system, it is advised to uninstall the drivers configured by the toolkit completely using USBDeview and then re-configuring them with the 64bit drivers posted here: http://forum.xda-developers.com/atta...9&d=1342290861
Click to expand...
Click to collapse
Once those were installed, I was able to continue and I am now Rooted with CWM. \(^▽^@)ノ
Sorry for the inconvenience!
Thank You,
DSoS
Re-open - link to drivers is dead
DSoS said:
Please close this, I figured it out.
I had missed the comment about the 64-bit drivers.
Once those were installed, I was able to continue and I am now Rooted with CWM. \(^▽^@)ノ
Sorry for the inconvenience!
Thank You,
DSoS
Click to expand...
Click to collapse
The link provided goes to a 404. Can the correct link be published?
stickplayer said:
The link provided goes to a 404. Can the correct link be published?
Click to expand...
Click to collapse
For the record, This one seems to work: http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=20&s=16
Select "Others" from the "Select OS" dropdown, then expand the "USB" option.
FIX Adb - device not found
Adb driver installer did it for me found and installed missing driver for my Nexus 7.
Now problem Solved.
God is Gr8
adbdriver.com/downloads/
Related
My nexus cannot be rooted because the adb drivers WON'T install.
I downloaded the sdk and installed the google usb drivers.
But, when my PC finds NEW hardware I point to the google usb drivers and I get the error CANNOT INSTALL HARDWARE. Running VISTA.
I have been reading and trying everything but I just cannot figure it out.
I finally said I will just have to post and HOPE you guys can give me a hand here.
Thanks.
My nexus cannot be rooted because the adb drivers WON'T install.
I downloaded the sdk and installed the google usb drivers.
But, when my PC finds NEW hardware I point to the google usb drivers and I get the error CANNOT INSTALL HARDWARE. Running VISTA.
I have been reading and trying everything but I just cannot figure it out.
I finally said I will just have to post and HOPE you guys can give me a hand here.
Thanks.
BTW, Im on 2.1.3. Is that why perhaps I'm having issues?
JasjarMan said:
My nexus cannot be rooted because the adb drivers WON'T install.
I downloaded the sdk and installed the google usb drivers.
But, when my PC finds NEW hardware I point to the google usb drivers and I get the error CANNOT INSTALL HARDWARE. Running VISTA.
I have been reading and trying everything but I just cannot figure it out.
I finally said I will just have to post and HOPE you guys can give me a hand here.
Thanks.
Click to expand...
Click to collapse
JasjarMan said:
BTW, Im on 2.1.3. Is that why perhaps I'm having issues?
Click to expand...
Click to collapse
try installing the drivers this way, i havent seen this not work for any android phone. install the free pdanet software from their site onto your computer http://junefabrics.com/android/ follow the instructions that they give you. it will install the proper drivers in a few minutes. btw, pdanet is a tethering program that works side by side with a android app, but you dont need it. you are just using it so that itll install the driver. good luck!
btw, you can get the answer here too http://forum.xda-developers.com/showpost.php?p=12657095&postcount=2
i answered you in your other thread with the same title
http://forum.xda-developers.com/showpost.php?p=12657038&postcount=3
simms22 said:
i answered you in your other thread with the same title
http://forum.xda-developers.com/showpost.php?p=12657038&postcount=3
Click to expand...
Click to collapse
THANKS, GOT IT! Now when I type adb shell it works, BUT than I type SU and I get PERMISSION DENIED?
I just want some SIMPLE instruction and I don't find anything.
Btw, I cant get SUPERSUSER installed. I did go to the market and installed it that way and I can see it in the app drawer but now what?
You have to flash superuser.zip in recovery (install zip from sdcard then choose zip from sdcard and you have to choose your superuser.zip on your internal memory). BEFORE you have to mount /system in recovery.
Sent from my Nexus S using Tapatalk
I don't want to look rude, but I think both of these threads will be cleaned in less than a few hours...
JasjarMan said:
THANKS, GOT IT! Now when I type adb shell it works, BUT than I type SU and I get PERMISSION DENIED?
I just want some SIMPLE instruction and I don't find anything.
Click to expand...
Click to collapse
I don't want to be rude. But
Why for ****s sake are you so damn desperate.
It seems like you demand something.
And just flash a custom rom and you will have superuser
Sent from my Google Nexus S using XDA App
Howdy,
I noticed that when I plugged my N7 into the USB Port on my PC running Win 7 Professional 32-bit w/SP1, that I got a message that the device was not recognized... So I looked around and found this thread offering an ASUS-provided Windows USB Driver:
http://forum.xda-developers.com/showthread.php?t=1796165
I downloaded it and went into Device Manager in Windows, found the Unknown device, and attempted to update the driver (note: I've done these steps before for other devices, so this wasn't new to me) but Windows keeps telling me that the driver I have is the one that I want:
"Windows has determined the driver software for your device is up to date"
Yeah right...
I tried manually installing it by right-clicking on the .INF file and clicking install but get the following message:
"The INF file you selected does not support this method of installation"
So... now I don't know what to do next...
I want to be able to copy files from my computer to the N7 via USB ... and I think I need a driver to enable the connection...
Help!
Hmm, I would grab the nexus 7 all in one toolkit and install drivers from there, see if that works!
Sent from my HTC One X
===================
HTC One X
Google Nexus 7
lukems said:
Hmm, I would grab the nexus 7 all in one toolkit and install drivers from there, see if that works!
Click to expand...
Click to collapse
Thanks for your reply... I may give that a try ...
I thought that I had read in one thread an advisement to stay away from the toolkit... but it may have been regarding something different (2nd post in thread):
http://forum.xda-developers.com/showthread.php?t=1957057
Was the author of the 2nd post talking about something different?
Can you please provide a link to the best thread/site to grab said toolkit...?
Thanks
Sent from my Nexus 7 using xda app-developers app
Try restarting your windows 7 then plugging in the Nexus while it is fully powered off. When you turn on the Nexus it should be recognized. This worked for me. Maybe some drivers are loaded from the tablet.
Or, just avoid toolkits.
Make sure you enable USB debugging and if it was not enabled, installing the Asus drivers again.
You could also try the Windows USB drivers provided by Google.
As it may help others. here's Google's instructions for Installing a USB Driver. Where the instructions refer to "<sdk>\extras\google\usb_driver\" swap that out with wherever you extracted the USB driver to.
OldDogEyes said:
Thanks for your reply... I may give that a try ...
I thought that I had read in one thread an advisement to stay away from the toolkit... but it may have been regarding something different (2nd post in thread):
http://forum.xda-developers.com/showthread.php?t=1957057
Was the author of the 2nd post talking about something different?
Can you please provide a link to the best thread/site to grab said toolkit...?
Thanks
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Sure you have to trust the person who makes the toolkit, but I've used the nexus 7 one for drivers and its been fine. The toolkit was under android development I believe, I can't link it atm as I'm on my phone, but if u want it, pm me and il dig.out the link
Sent from my HTC One X
===================
HTC One X
Google Nexus 7
#update - i'm idiot, my problem was when choosing the driver, i clicked sdk->extras->google->->usb_driver->i386 when i should have stopped at the usb_driver folder
I can second jinx100. I had a similar problem where the update driver wizard told me it was unable to find the driver even though i tried pointing it to both the google and asus (same thing?). Anyway in the end I just did a reboot of the laptop, connected the nexus 7 and everything was good to go.
Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Installing Windows 7 Drivers Please wait
Operation Started
android_winusb.inf
The resource loader cache doesn't have loaded MUI entry.
1
0
An Error Occured. Returning to Main Menu.
---------------------------------------------------------------------------------
If you got the message [the resource loader cache doesn't have loaded mui entry]
during the installation procedure dont worry as the drivers have been installed.
Click to expand...
Click to collapse
PCServe said:
Hi guys,
I currently have a problem with my ADB which doesn't seem to work with Windows 8. I set up everything as I did on Windows 7 before (including Environment Variables), but the ADB doesn't detect my Nexus 7 (List of devices attached is empty)
I think it might be a driver issue (see the screenshot attached). I also tried it with my HTC One X and it doesn't detect it either.
Does anyone have any idea how to get it to work? My devices are both unrooted and locked.
I wanted to install the upgrade to Android 4.2 for the N7.
Hopefully somebody can help me.
Thanks in advance!
EDIT:
I btw also tried the Nexus 7 Toolkit from here and I also installed the Google Drivers through Android SDK.
When trying to install the drivers through Nexus 7 Toolkit the following error occurs:
Click to expand...
Click to collapse
Do you have Android SDK installed?, if so try the following, you're using Windows 8, right?
On the 'old' Windows Desktop, right-click on the bottom left corner
> Select 'Command Prompt (Admin)'
> type ' devmgmt.msc '
> Right click on the driver with warning sign and select update driver > select BROWSE and go to the extras\google\usb_driver\ folder of your SDK and then update the driver. Did that resolve the issue?
It works for the Nexus 7 when it's running, not in fastboot though
PCServe said:
It works for the Nexus 7 when it's running, not in fastboot though
Click to expand...
Click to collapse
Have you rebooted the PC since installing the drivers?, if not give that a go and try again, they may need a reboot to complete the installation.
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
Windows was unable to install your Nexus
Windows could not find driver software for your device.
If you know the manufacturer of your device, you can visit its website and check the support section for driver software.
Click to expand...
Click to collapse
I also tried the drivers from ASUS with the same result.
PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
Did you try browsing to the driver location instead of letting Windows find the driver?
This driver has helped others
http://forum.xda-developers.com/showthread.php?t=1766220
PCServe said:
Yes, I tried to restart the computer as well as the tablet several times. When the system is running on the N7, the drivers are detected and everything works fine, even ADB. But in fastboot it shows the warning sign in Device Manager and when I try installing the drivers either from the SDK Google Drivers or the Nexus 7 Toolkit drivers it says
I also tried the drivers from ASUS with the same result.
Click to expand...
Click to collapse
turn off driver signing and then do it.Mine works fine in Windows 8..check this for reference:-
http://forums.mydigitallife.info/th...ble-driver-signature-enforcement-in-Windows-8
Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!
PCServe said:
Thanks, using unsigned drivers worked perfectly
Device Manager says I have a Galaxy Nexus though, but patching the update worked anyway!
Thanks alot!
Click to expand...
Click to collapse
Glad to be of help
✪✪✪ [ROOT] [Restore] [OneClick OR Manual] [PC] [MAC] Kwongger's FLO Noob Root Kit ✪✪✪
EVERYBODY!
WE ARE BACK DUE TO POPULAR DEMAND!!!
Kwongger's All-In-One FLO Noob Root/Restore Kit FOR PC and Mac
YES! We are ADB FREE!!!
Why we are back:
I really feel accomplished when I acutally do the commands myself! Apparently so do others, we are back B****ES!
I felt that I didn't get the help I needed/wanted as a n00b on XDA, this is a new account FYI, so I like to make n00b kits with AWESOME instructions, ENJOY!!!
FYI: I want to provide the best possible support that I can (even though this is free)
DOWNLOAD v3
Hey! The ONE-CLICK/Restore update is currently uploading!
Instructions in post #2, Change-log in post #3.
DISCLAIMER:
By downloading the files, you accept the fact that I am NOT in anyway responsible for what YOU do to YOUR device, unless it starts shooting lasers at iOS devices, then all the credit is mine . Really,in all seriousness, this procedure is a BEGINNER procedure, I am simply providing instructions and TOOLS! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!!!
Manual ROOT Instructions!
(If you want One-Click, then Just double-click either the Flo ROOT by Kwongger.bat (to root) or the Flo RESTORE.bat for a out-of-box restoration!
I’ll make a video soonish.
Driver Installation!
To Install The Drivers Fresh
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Devices in the left pane.
Locate and expand Other device in the right pane.
Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
Select Browse my computer for driver software and click Next.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to install the driver.
Follow the Instructions!
Upgrade Existing Drivers
Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:
Connect your Android-powered device to your computer's USB port.
Right-click on Computer from your desktop or Windows Explorer, and select Manage.
Select Device Manager in the left pane of the Computer Management window.
Locate and expand Android Phone in the right pane.
Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
Select Install from a list or specific location and click Next.
Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
Click Browse and locate the USB driver folder. (The Google USB Driver is located in<sdk>\extras\google\usb_driver\.)
Click Next to upgrade the driver
Follow the Instructions!
Click to expand...
Click to collapse
Unlocking The Boot Loader!
1. Enable USB Debugging on your Nexus 7 in Development Settings
2. Open yourself a Command Prompt (or Terminal for MAC) in the Kwongger Nexus 7 folder!
a. Hold down shift
b. Right Click in the folder
c. Click Open Command Window/Prompt here
3. Boot into the bootloader using:
Code:
adb reboot bootloader
!!!!!!!!!!!NOTICE!!!!!!!!!!!!!!!
The next step will FACTORY RESET your device!!!
4. Once it is in the bootloader, enter this:
Code:
fastboot oem unlock
5. It will now ask you if you do, in fact, want to unlock your bootloader. Use Volume up/down to select YES and hit power to Confirm.
6. Your Nexus 7 FHD now has an Unlocked Bootloader.
7. IMPORTANT:
Reboot the device!
Click to expand...
Click to collapse
Choose either TWRP or CWM!
Installing TWRP!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7twrp.img
note: if you change the name use that in the .img part
3. Done!!!
Installing Clockwork Mod Recovery!!!
1. Get into Your bootloader Again. (Above)
2. Type the following to flash the Team Win Recovery Project version 2.6:
Code:
fastboot flash recovery nexus7CWM.img
note: if you change the name use that in the .img part
3. Done!!!
Click to expand...
Click to collapse
Rooting on Android 4.3!!!
.01 Copy The SuperSU.zip to the internal storage of your device.
1. Boot in to your bootloader and use the volume keys to select Recovery and use the Power button to confirm.
1a. RECOMMENDED: Tap BACKUP and Swype to confirm to make a backup of your current, UNROOTED n7.
2. Tap INSTALL.
3. Navigate to where you put the SuperSU.zip
4. Tap the zip.
5. Swype to confirm the flash!
6. If all goes well (no reason that I know that it shouldn’t) YOUR NEXUS 7 IS ROOTED!!!!
Click to expand...
Click to collapse
CONGRATS!!!!!!!!!!!!!
v1
Nothing New! This is 1.0
Click to expand...
Click to collapse
v2
I updated the Fastboot and ADB because some people were having some issues, it seems to have fixed the issues.
Click to expand...
Click to collapse
v3
I added the ever popular Mac Support! AND Clockwork Mod Recover, I don't know it is touch or not XD, could someone check? Just type
Code:
fastboot boot recovery nexus7CWM.img
and let me know! Thanks in advance.
Click to expand...
Click to collapse
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
That's weird. I will update it.
Sent from my HTCONE using XDA Premium HD app
Actually!
Are you on 32bit? I included 64bit.
I like that you moved it to General!!!
I always thought that the DEVELOPMENT threads should be only used for KERNELS/ROMS
THANK YOU
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
EvanVanVan said:
Hey man, thanks for the instructions but could you clarify that you have to restart/boot up completely after unlocking the bootloader? I was still in fastboot after unlocking it when I flashed TWRP, and now TWRP is asking for a password, failing on all operations and I'm stuck in a bootloop.
Click to expand...
Click to collapse
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Kwongger said:
Dang Dude, I am sorry. I just went ahead and put that in. :/
I want to help you with this.
Can you get into the boot loader or anything? Maybe if you can get TWRP working, I can send you a Nandroid of a stock, one (Once I get mine )
Click to expand...
Click to collapse
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Gabik123 said:
I'm on windows 8 and have all the drivers installed but when I try and use the command "adb reboot bootloader" I get "error: device offline"
---------- Post added at 08:30 AM ---------- Previous post was at 08:12 AM ----------
I got it to work using the normal android sdk download. I couldn't get it to work using just the files I downloaded from you.
Click to expand...
Click to collapse
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
EvanVanVan said:
Just found the solution in another thread: Open TWRP, Format Data first, then Factory Reset, finally reboot. I knew it wasn't a long term problem but I'm glad I didn't have to wait for Google to release Factory Images lol.
Click to expand...
Click to collapse
AWESOME!!!!!!!!!!
I feel better now XD
jmill75 said:
I am having this issue in windows 8 also, "offline" but I am getting the same thing using android sdk. Can someone provide some assistance please. Not sure why having such an issue.
Click to expand...
Click to collapse
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Kwongger said:
I don't know... I have Windows 7. I also have NO IDEA why this would happen... Try using a port on the back of the PC (desktop) . If that doesn't do it, try USB 3.0 (if you have it). Also, if you are using the Stock cord, try other cords. That is all I can think of... :/
Click to expand...
Click to collapse
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
RubenRybnik said:
There is a way to disable driver verification after rebooting in windows 8. I had to do this with my SGSIII and Win 8 x64, just google around for it, bet that's the problem.
Click to expand...
Click to collapse
Thanks! I will find it and add it to the instructions with credit.
Sent from my HTCONE using XDA Premium HD app
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
androidfr33k said:
I see the pack includes the tools for MAC. I am on 10.8.4. Has anyone tried this on a MAC yet? I will be doing so later.
Click to expand...
Click to collapse
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Looks like SuperSU came with the TWRP image(no need to copy it over separately). I tried to reboot from TWRP after updating the recovery and it forced me to flash SuperSU to root.
Nxxx said:
Wait how would you do this on mac? Does the same .zip file work or would I need a different one? If you get it working please post a tutorial!
Click to expand...
Click to collapse
I included Mac ADB... But not fastboot, you would need Fastboot as well, i'll get a Mac pack up tonight.
disregard....
working great! thanks OP
Hi,
I just got my nexus 10 and the drivers for mtp are not installing right now the device gets installed as acer adb interface.
please help.
mtp is ticked tried changing from mtp to camera and back doesnt help.
The third post in this thread has links for the drivers
http://forum.xda-developers.com/showthread.php?t=2670400
You will probably need to manually update them
Happy flashing!
demkantor said:
The third post in this thread has links for the drivers
http://forum.xda-developers.com/showthread.php?t=2670400
You will probably need to manually update them
Happy flashing!
Click to expand...
Click to collapse
Hi thanks for the tip got adb working with naked drivers but which ones should i use for mtp it doesnt work with google ones...
I would recommend downloading the SDK (should also be linked) and then run it and update the drivers from there
demkantor said:
I would recommend downloading the SDK (should also be linked) and then run it and update the drivers from there
Click to expand...
Click to collapse
got any idea why it keeps showing up as an Acer device
Dark Passenger said:
got any idea why it keeps showing up as an Acer device
Click to expand...
Click to collapse
Windows chose the wrong ones, it happens
Go to device manager, look for all the usb drivers, plug in tablet and see which one pops up, then manually update (should be in the naked driver folder or SDK if you updated it)