Database Users

[Q] Stock 4.2.2. refusing to ADB to then root

I had a windows 7 PC perfectly working in booting a Nexus 7 to flash and root etc, it did a Nexus 4 last week.
There is some problem with drivers and 4.2.2. specifically. My story was it was 4.1.2. rooted and it was refusing to OTA update but I wasn't bothered due to the bugs/performance in 4.1.1 so I waited til 4.2.2. came along. The N7 refused to take OTA 4.2.2. I got the Android icon with the Red icon out its belly and it would boot back as 4.1.2 every time.
So using Nexus Rootkit I did a "stock flash+unroot" to 4.2.1 and then let it did a OTA to 4.2.2 and that worked so I have a stock 4.2.2 but not it won't root, it would do that ADB bootloader type stuff. I've tried updating driving umpteen times but it like it simply won't obey ADB type commands? I'm not a rooting expert I just used the toolkit and howtos.
So stuck.
In hindsight as it WAS doing ADB at 4.2.1 I should have rooted and then otarootkeeper then OTA to 4.2.2. but I didn't know 4.2.2 rooting fails.
Any ideas?

same for me!!!
Help...

Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2

can root a stock 4.2.2 - it works!
I fixed it!
I'd been trying toolkit all of its options and none worked. So I followed this guide which contains an error which is irrelevant.
http://m.ibtimes.co.uk/root-nexus7-official-android422-jdq39-jellybean-ota-434720.html
Do its step 1. It downloads the Google USB drivers - THEY WORK. This is the problem with other guides they point to drivers which don't work.
Ignore its step 2 because you find step 1 includes fastboot so you don't need to get it separate. I lost a lot of time on that one problem because the link to that shared file fastboot.zip won't download so I hunted and found another and when I was going to copy to the required destination in step 2 I found the fastboot file alreadt there! So ignore step 2
Step 3. Now I downloaded it on the Nexus 7 itself and mine was in /sdcard/Downloads or you can copy on the PC and then copy it over to the N7 via USB cable.
Step 4. Press and hold power off you get option select power off.
Step 5. At the step 1 you'll see WHERE it is installing the SDK to, you need to go to that folder in this step 5 as described.
Step 6. As describe, press vol down and power button together and keep them hold. Then a menu screen shows mine had been unlocked from before. Now dont't touch the N7. Go to Windows machine.
Step 7. My Windows Pc doesn't have command prompt option inside a folder so I opened command prompt and CD down to where step 1 was.
Step 8. Type that command. Mine simply worked fperfectly first time. It had a copying type command which looked happy.
Step 9. Back on the N7 hit the vol up button til you see a "recovery" type word on screen.
Step 10 and 11 as described.
Step 12. Now is the next area where howto guide is wrong / misleading, I had on my screen some gibberish folders and an "update.zip" not the supersu zip from step 3. Initially I tried the update.zip and it went crazy but fortunately a hard power-off got me fixed so then next time I looked around for the supersu zip. So of the stuff on-scren where was like 0/ type folder so I selected that THEN I could see the sdcard/download folder I could go down to and then select the zip file. The /sdcard folder isn't showing firstly you have to go /0 and then you see it.
Step 13 do it.
Then get it booted and then go into Supersu app and run it and then make sure you install voodoo root keeper app and select it to preserve root.
So I've got a vanilla 4.2.2. with root and so far it all works. Features which kept me on 4.1.2 like PPP-widget simply work.
Phew.
I've spent about 15 hours on this trying to eliminate my own dumbness as the cause.
I think basically the ADB drivers in the Toolkits are bumb, ignore them they don't work I think the Android SDK with its Google USB drivers are the ones which work with 4.2.2 I guess the Toolkits need to be updated.

nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The problem seems to be drivers. The N7 stock 4.2.2 simply refuses to respond to Root Toolkit its drivers are simply not working, the N7 is ignoring to get into fastboot. I figured it out see my later post.
I think 4.2.2. is too new for toolkits and people's 4.2.2. rooting guides are buggy and relate to old old instructioned since outdated and in error. By trial+error I figured it.

nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Addtional my N7 did OTA receive the 4.1.2 to 4.2.2 update I even went into the /cache and the file name had version names to match so OTA was thinking itself capable. I think in some unlock / root past event I'd something screwed something up and OTA simply weren't working full stop. I did though manage to use Toolkit to get to stock 4.2.1 and then the drivers in the toolkit then don't work with 4.2.2, that's the broken bit. If you use Android SDK Google USB drivers, they work and you have to use command prompt fastboot as in the HOWTO I just posted to get it all working.
Toolkit drives broken with 4.2.2.

dont use a root toolkit. do it the right way, there arent any issue.
fastboot oem unlock, fastboot flash a recovery, flash the su binaries or a custom rom, reboot. thats it.

FYI - I've found that to use the toolkit (the 4.0.0 toolkit is what I used), you need to replace the adb-toolkit.exe (or whatever adb.exe is called in your toolkit) with the adb.exe that comes in the SDK (after you've updated your SDK, of course).
Otherwise, ADB shows as "offline" in the toolkit menu.
Hope that helps someone...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

The issue is what you typed is gibberish to most including me.
Sent from my Nexus 7 using xda app-developers app

[Q] adb offline nexus 7 4.2.2

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.

[Q] No Luck with Nexus 7 Toolkit

My Rom version is 4.2.2. And I have upgraded the toolkit to v4.3.9, the latest one.
I was able to unlock the bootloader. However, I couldn't root my Nexus 7.
Nexus 7 gets stuck at "booting the downloaded image", while the toolkit was showing "Waiting for adb Mode".
Luckily, the Nexus 7 wasn't bricked though. I was able to boot into the official image, by holding the power button for a long time.
I tried many times with different options in the Toolkit. Still got no luck. Many suggestions are welcome. Thanks.

Dont waste any more time with toolkits. take 5 minutes to learn how to do it manually

Pirateghost said:
Dont waste any more time with toolkits. take 5 minutes to learn how to do it manually
Click to expand...
Click to collapse
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.

ejj3 said:
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
Click to expand...
Click to collapse
Now that your N7 is already unlocked, all you need is a recovery... Download this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.3.1-grouper.img
Also make sure that you have the android sdk installed. It's easy enough to find.
Open the platform-tools folder, hold shift and right click; then choose "open command window here"
Make sure that your N7 is rebooted into the bootloader and run the command "fastboot flash recovery recoveryname.img" replacing recoveryname with the name of the recovery.
After that, follow the instructions to flash any custom rom or supersu from recovery... I'm sure that there are more detailed instructions elsewhere, but that's all you really need at the moment...

ejj3 said:
@Pirateghost, is there any good guide for this? Most of google search results point to this toolkit.
It is working now. I had to run Windows on the bare metal of my macbook. It won't work when Windows is running within a virtual machine.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=2150661
And you DONT need windows to use fast boot or adb
Sent from my Galaxy Nexus

Unlocking the Nexus 7 (2013) Bootloader

This is the same as any other Nexus device.
WARNING. As is normally the case, this WILL factory reset your device.
Install the Android SDK (and Google USB driver).
Android SDK
Google USB Driver (Windows)
Enable USB debugging on the Nexus 7.
Unlock Developer Options by going to Settings > About Tablet and clicking on the build number seven times.
Go to Settings > Developer Options and check USB debugging. Click OK on the warning.
Connect the Nexus 7 via USB and reboot the Nexus 7 into the bootloader.
Note: Users have reported failures and "Access is Denied" errors when connected via USB 3.0 ports so use USB 1.1 or 2.0 to be on the safe side.
Open a command line / terminal and navigate to your SDK platform-tools directory.
Enter
Code:
adb reboot bootloader
and hit enter.
Once the Nexus 7 boots to the bootloader, unlock it
At the command line / terminal enter
Code:
fastboot oem unlock
and press enter.
On the Nexus 7, use the volume up button to select 'Yes' on the 'Unlock bootloader?' screen.
Press the power button to save your choice and verify on the next screen that you see 'LOCK STATE - UNLOCKED' at the bottom.
Use your volume keys to select 'Start' and click the power button to factory reset and reboot.
Enjoy your unlocked bootloader!

Do you have the usb drivers installed? That happened to me ("old" n7) when I didn't have the usb drivers installed.

may need to update your drivers for it to be able to see the device.
when you try adb devices while it is on does it kick back the device id number?
i haven't tried yet as i knew the drivers out currently would be an issue.

gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?

gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.

mrancier said:
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
Click to expand...
Click to collapse
I updated my SDK when 4.3 dropped but I did have to go snag the Google USB driver and install it to get the N7 to be recognized.

ATGAdmin said:
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
Click to expand...
Click to collapse
1. You may be right (as far as my posts go) but how am I to ever make a dev post if I'm not allowed to make a first post in a dev forum?
2. This /is/ a dev-related post.
3. My feelings wouldn't be hurt if the mods felt the need to move the post.

Yeah I had to install the google usb drivers from the SDK in device manager of Windows to get the n7 recognized.

Thanx. Just got home with my new nexus 7....bootloader now unlocked :highfive:

Nevermind it literally is that as the command.
Sent from my Nexus 7 using Tapatalk 4 Beta

keynith said:
Can you update it with the commands? So people don't have to search
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The commands are there...
Also, unlocked mine not 5 minutes after opening on Ubuntu 13.10.

no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery

Worked great thanks!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
smirkis said:
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Click to expand...
Click to collapse
Make sure you update your files from the SDK Manager. It had updated USB driver which from there it would install the proper drive and then it worked form me.

The trick, as stated in the Nexus Toolkit after driver install, is that you need to change the tablets usb settings from MTP to PTP. Tablet was immediately seen using "old" nexus toolkit universal usb drivers (old = i did not download the new SDK). I choose toro 4.2.2 (because it doesn't matter for unlocking) and then told it to unlock. worked like a charm.
Now the question is ... how long does it take to reboot cause mine is taking forever!!!
OK it booted. So yeah the Nexus 7 Toolkit ver 5.0 worked just fine to at least unlock. I did not root (4.3 still too buggy) or install a custom recovery yet.

Stock recovery, pretty please?
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!

My body and my 7 are ready for a recovery!
Thank you!

treoo0_1 said:
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
Click to expand...
Click to collapse
I'd be happy to, but am having a hard time finding the correct ADB command.

isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch

adb pull
jc monkeyballs said:
I'd be happy to, but am having a hard time finding the correct ADB command.
Click to expand...
Click to collapse
Can you use
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example:
Code:
adb pull /system/recovery.img C:\Android\Local
Thanks for offering to help!
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Lpuboy87 said:
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
Click to expand...
Click to collapse
Yep. Razor.
Branch = Razor
codename = Asus flo
Wifi Model: ME371K

followed the first post and it worked....used this for the commands
ADB Commands
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
treoo0_1 said:
Yep. Razor.
Click to expand...
Click to collapse
yeah thought so. :good::highfive:

[Q] Ach! Doh! I did it. I bricked my N7 while going 4.4 to 4.3

I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?

Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?

I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app

Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.

Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.

Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.

nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped

The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.