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
So The toolkit is not loading drivers from the menu, I am familiar with using it, version 4.0.0. Used the pdanet download it errors out now, Its install was removing the wireless when installed in the last couple of days.
I have had this all working with the pdanet, but had to do several restores to get wireless back, each one after loading the pdanet again and loosing wireless.
Running Android 4.2.0 rooted and boot unlocked.
So I was able to load the adb drivers with the NexusRoot kit 1.6.1 WugFresh
frankleee said:
So The toolkit is not loading drivers from the menu, I am familiar with using it, version 4.0.0. Used the pdanet download it errors out now, Its install was removing the wireless when installed in the last couple of days.
I have had this all working with the pdanet, but had to do several restores to get wireless back, each one after loading the pdanet again and loosing wireless.
Running Android 4.2.0 rooted and boot unlocked.
So I was able to load the adb drivers with the NexusRoot kit 1.6.1 WugFresh
Click to expand...
Click to collapse
Still can't get mine to work.. and i started with Wug in win8 x64
Phk said:
Still can't get mine to work.. and i started with Wug in win8 x64
Click to expand...
Click to collapse
There is a thread on here someplace - sorry, you'll have to search for it (I don't remember where it is) - but the gist of it is that Windows 8 mandatory requirement of using signed drivers is the root of the problem.
The thread in question details a rather involved method for turning off the signed driver requirements in Windows 8.
An alternative to this approach - which is arguably at least as much effort, if not more - is to use your PC hardware without Windows 8: boot a version of Linux (such as Ubuntu) from a USB key. The same thing could be accomplished from a Linux "Live CD" so long as you keep copies of the Linux versions of fastboot & adb (plus any dynamically-linked shared libs not in the distro as needed) lying around.
(Yes, I realize that suggesting the latter to someone that uttered the word "toolkit" is probably a waste of typing. But the Windows 8 issue is generic to everyone, and others besides the OP may read this post.)
[Edit] See this old post by WugFresh
http://forum.xda-developers.com/showpost.php?p=33288005&postcount=1368
and possibly a couple posts after it in the same thread. I'm not sure if this is the issue or not, but it is clearly evident that WugFresh has been aware of it for some time.
Is there some reason you are not asking this question in WugFresh's thread?
Excellent.... It works now
Thanks
Phk said:
Excellent.... It works now
Thanks
Click to expand...
Click to collapse
Good news.
For the benefit of others, what steps did you take?
uninstalled the driver several times until the option "delete driver" also appears in the uninstall
reboot
plug cable
manually choose new driver
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.
Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?
myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers
I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.
how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.
Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:
leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.
did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:
Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.
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.
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