Hello,
I have previously rooted my nexus 7 32 gb with the exact same computer that I have now and with the same exact software (Wugfresh Toolkit 1.6.2) and when I was finished previously, I set the drivers back to their stock google drivers that would be used as if I didn't change any of the drivers. I recently had issues updating to 4.2.2 and had to flash back a stock rom to get everything working again, now I have to re-root and re-flash my recovery.
When I now follow the same exact steps now, I keep installing an android composite adb interface instead of the android adb interface, which I know you need to restart the bootloader. I have tried rebooting after every step, removing every android driver, nearly everything and keep getting the google made android composite adb interface instead of Wug's android adb interface. I am running windows 7 64 bit. So anyway, does anyone have any ideas, and yes I have looked at other threads for this, but none of them really give me the answer to this question.
Thanks
Fishwithadeagle said:
Hello,
I have previously rooted my nexus 7 32 gb with the exact same computer that I have now and with the same exact software (Wugfresh Toolkit 1.6.2) and when I was finished previously, I set the drivers back to their stock google drivers that would be used as if I didn't change any of the drivers. I recently had issues updating to 4.2.2 and had to flash back a stock rom to get everything working again, now I have to re-root and re-flash my recovery.
When I now follow the same exact steps now, I keep installing an android composite adb interface instead of the android adb interface, which I know you need to restart the bootloader. I have tried rebooting after every step, removing every android driver, nearly everything and keep getting the google made android composite adb interface instead of Wug's android adb interface. I am running windows 7 64 bit. So anyway, does anyone have any ideas, and yes I have looked at other threads for this, but none of them really give me the answer to this question.
Thanks
Click to expand...
Click to collapse
There are new drivers for adb. Try looking for them in wug's toolkit thread.
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.
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
Last week my nexus 7 asked my permission to download kit kat, I said yes and it crashed and now I only get the google opening page it was rooted by my brother who owned it before me, the tablet is not recognized when I plug it into my computer either, can anyone point me to where I can find the drivers online and the os as well. Thank you in advance.
Install Wug toolkit and install the drivers that way... You can also return to stock via the toolkit.
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.