yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] passlogin:
Potential fix for "checking ADB status"

Like some others on here, I kept getting stuck on checking ADB status while using the NRT and I figured out a way to fix it.

I am using a nexus 7 2012 32gb wifi 4.3, running windows 7 64 bit and it's possbile the ADB drivers being installed by the NRT were 32 bit, although I'm not entirely sure...regardless here's what I did to fix it:

-First disable Windows Automatic Driver Installation (you can re-enable it after the fix). Guide here

-Follow step 1 of the Full driver installation guide within the NRT and reboot

-Install the essential ADB driver install found here

-Plug in your nexus 7, run the essential ADB driver program and let it install the correct driver

You should know be able to proceed using NRT without any hiccups, particularly on the "checking ADB status" bits.

Regards
[Nexus 7 Android Development] mla123:
Please help

I was using this tool to return to stock from a unlocked rooted 4.2.2 nexus 7 (tilapia).

This tool downloaded and flashed 4.3.

After bootloader and radio were flashed I got error, something like boot img not found and the device stayed stuck in bootloader only.

When I Select Start it says Booting Failed, when I select Recovery it says Booting Failed

Only Power Off and Restart to Bootloader Options work. I see only the screen with Product name, variant etc

Can anybody please guide on how to get the device booting normally again?
[Nexus 7 Android Development] WugFresh:
Flash Stock + Unroot with 'can't boot up'. Maybe also consider enabling force flash mode in the toolkit options menu first.

{{ WugFresh }}
[Nexus 7 Android Development] mla123:
Thanks for the quick reply. I managed to solve the problem manually using the following guide

http://xdaforums.com/showthread.php?t=1907796

The image downloaded by the toolkit was correct. But I think the problem while using the toolkit was at this step --

fastboot -w update image-nakasig-jwr66v.zip

somehow this step was not getting executed. but this step worked correctly when executed manually.
[Nexus 7 Android Development] WugFresh:
I don't see how that its possible for that command not to execute, as I have tested those scripts extensively, but I am happy to hear you got it resolved. I will look into it regardless.

{{ WugFresh }}
[Nexus 7 Android Development] limpet:
Mine too.

I backed up everything I wanted to back up, then ran the toolkit. I accepted the offer to update from 1.6.4 to 1.6.6 and let it download a couple of things. No problems at all.

Started 1.6.6 and tested the drivers which were stiill functional. Downloaded the 4.3 factory image, flashed it, then rerooted.

Thanks again!
[Nexus 7 Android Development] 762x51:
Hate to be that guy, but can someone give me the steps needed to update my Nexus 7 v1 running 4.2.2, already rooted and unlocked to 4.3 using the toolkit? Preferably without needing to reinstall everything? When I try to update OTA it just reboots to the dead android with the triangle screen and I need to power off and on again.
[Nexus 7 Android Development] danvee:
Why not do what I did: download CleanROM (4.3) for the Nexus 7 and flash using TWRP?

Saves a lot of steps and is basically a rooted stock 4.3.
[Nexus 7 Android Development] limpet:
I think it's better to just grit your teeth and reinstall it all.

The N7 will be a lot happier with the cruft cleared out.
[Nexus 7 Android Development] barbo:
Thanks for your suggestion, passlogin. I won't be and to try it for a few days though. I appreciate you working about your solution.
[Nexus 7 Android Development] WugFresh:
v1.6.8 is live. Enjoy!

{{ WugFresh }}
[Nexus 7 Android Development] digixmax:
Were you in the same situation as [MENTION=2909466]762x51[/MENTION] -- and re-installing stock 4.2.2 using NRT 1.6.x worked for you?

Given that "restore recovery" failed, I am concerned that "restore stock" might run into a similar problem and might leave the N7 in a bricked state.

---------- Post added at 08:47 AM ---------- Previous post was at 08:16 AM ----------

I tried 1.6.8 just now, "restore stock recovery" still yields same result: horizontal android with red-triangle error when rebooting into recovery and when installing OTA 4.3.
[Nexus 7 Android Development] tamanaco:
Thanks Wug, I must admit ignorance... I thought that after telling the Toolkit that my N7 WiFi had JB 4.2.2 JDQ39 that selecting Flash Stock + Unroot would install the JB 4.2.2 Stock image. Well, after failing to restore the Stock Recovery to install the OTA JWR66V-from-JDQ39 from the N7... I decided to go back to stock. To my surprise while in JB 4.2.2 selecting Flash Stock + Unroot actually installs JWR66V as Stock. Basically the 4.3 JWR66V OTA is applied via the Toolkit. Maybe I'm a little slow, but this was not clear to me. Maybe it should say somewhere in the instructions that it also updates to the "current" JB stock version. I thought I that button was going to make my phone a virgin 4.2.2 giving me the opportunity to apply the OTA from the N7. Oh well, you learn something new every day. Thanks again.
[Nexus 7 Android Development] limpet:
[MENTION=2909466]762x51[/MENTION] asked for "steps needed to update my Nexus 7 v1 running 4.2.2, already rooted and unlocked to 4.3 using the toolkit?"

I was in same state.

I backed up everything I wanted to back up, then ran the toolkit. Accepted offer to update from 1.6.4 to 1.6.6 and let it download a couple of things.

Started 1.6.6 and tested the drivers (Step 3 of "Full Driver Installation...") which were still functional.

Then pressed "Flash Stock + Unroot" which offered to download 4.3 factory image. Did that and flashed it. After it booted, I reenabled USB debugging and tested the drivers again.

Then pressed "Root" (with custom recovery unchecked). After boot, set up wifi and took care of Busybox and SuperSU.

This is just what I did when 4.2.2 was released which also went off without a hitch.
[Nexus 7 Android Development] WugFresh:
Please read the FAQs on my site in regards to updating/getting OTAs. Sometimes just flashinh stock recovery isn't enough to take an OTA.

And please recognize, that the Red-Triangle Android is NOT an error. That is STOCK RECOVERY. To bring up the stock recovery menu from that interface on your device simply hold down Volume Down and Press the power button.

By restoring stock recovery, seeing that Red-Triangle Android is exactly what should happen.

I feel like this is one of the biggest misconceptions ever, so I really ought to emphasize this somewhere, as that screen really looks like something went wrong. I honestly think Google should change that image entirely, or have the device show some text.

So to be clear, restore stock recovery did NOT fail. It worked. What didn't work for you was taking the OTA. This could be due to a number of reasons.

The easiest way to upgrade to 4.3 if the OTA isn't working is to use "Flash stock + unroot". This will wipe your data so backup first.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
When you select Flash Stock Unroot, that interface clearly has another pull down menu for the stock images available to flash, by default the latest build available is selected, but there are multiple options.

By telling your toolkit that your device has a certain build, it understands what it needs to do perform operations. Flashing stock can be used to upgrade, downgrade or restore the same stock you currently have.

Look at the flash stock interface more closely. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] digixmax:
I did a "Flash stock + unroot" and am now on stock 4.3.

I am a bit surprised though that Google auto-restore did not kick in after Google account setup and automatically re-download my apps.
[Nexus 7 Android Development] limpet:
I was irritated when it did that when I updated to 4.2.2. I prefer to take the opportunity to clean up my system and get some space back. This time (4.3) it behaved like yours. Much happier!
[Nexus 7 Android Development] jpcalhoun:
Yeap, that's what I did and it works great.

---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------

Anyone having trouble downloading the latest 1.6.8...I can't seem to get on Wug's site.
[Nexus 7 Android Development] hazwheel:
Don't know how, but when holding buttons to manually get to fastboot menu, a "download mode" Inside a graphic was displayed on the screen, not been able to get it back and never seen it before!
[Nexus 7 Android Development] WugFresh:
Yeah, that's for use with odin. Its power button while holding volume down.

Fastboot mode is both volume up and volume + power.

{{ WugFresh }}
[Nexus 7 Android Development] Phoenix84118:
I see it doesn't list the Nexus One, will it support it?
[Nexus 7 Android Development] FiveOhFour:
Awesome, and you should clarify when you add that to the OP that to access manual input click launch under advanced utilities, it took me a minute before i looked there for it and most using the tool arent familiar with it to know that. I will uninstall the drivers that are sucessfuly working and see if the auto driver install works when using the cmd line. So you are saying just auto install but dont trust the adb check failing and when run manually you suspect it will find the device just fine?

---------- Post added at 01:47 PM ---------- Previous post was at 01:45 PM ----------

Great news bro congrats!!!! Love seeing success through community effort and teamwork, and i love that its the little things
[Nexus 7 Android Development] WugFresh:
I know exactly what it means. Not just progress. A solution. Totally an oversight by me. But now my mind is at peace. Now I would really like people with 64bit machines to just use the auto-installed drivers and see if it still works using the

adb start-server

Solution.

{{ WugFresh }}
[Nexus 7 Android Development] t-readyroc:
I'm unlocked & rooted using this program, but I think the permanent CWM flash may have failed. After rebooting after root (verified through installation of ROM mgr), I tried to use the instructions in this post (p.25 this thread) to flash the new CWM. It didn't look like it failed, so I used ROM mgr to reboot to recovery, & I got the image of the dead alien w/the red exclamation point.

Then I held in power & up-volume, & saw the stock recovery instructions to reboot. What step do I need to take next?
[Nexus 7 Android Development] kenikh:
Yes. I just unlocked and rooted mine. Again, I selected JRO03C even though I am on JRO03D.
[Nexus 7 Android Development] WugFresh:
I would advise simply trying to flash it again.

{{ WugFresh }}
[Nexus 7 Android Development] nicksoph:
Works !
[Nexus 7 Android Development] t-readyroc:
Hey WugFresh - yeah, tried that 3x now w/the same result. Should I maybe try flashing the CWM included w/ROM Mgr first?
[Nexus 7 Android Development] WugFresh:
Yes. Try that.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Added to the OP (please refer users to this post or the OP if the question is asked again):

IF THE PROGRAM IS STALLING ON YOU (FOR ADB CHECK):

Restart the toolkit

On the main interface hit the "Launch" button to open Advanced utilities

In the advanced utilities interface; hit the "Launch CMD Prompt" button

Type the following cmd

adb start-server

Now you should be able to use any of the utilities in the toolkit without it stalling.

This extra step is just a temporary solution, until I release v1.5.3; then this won't be necessary.

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Victory is mine, successful ADB check using the auto install drivers
[Nexus 7 Android Development] Fall Guy:
Shouldn't that be adb start-server
[Nexus 7 Android Development] nicksoph:
I think the stock rom messes with the bootloader so you might want to try searching for - recovery-from-boot.p
[Nexus 7 Android Development] t-readyroc:
Thanks. That worked. It even flashed 6.0.0.6; I think the issue may be that the image linked was the touch image? Because it prompted me to pay for a touch upgrade after flashing from Rom Mgr.

Thanks again; great tool.
[Nexus 7 Android Development] WugFresh:
Whoops.. yes.

{{ WugFresh }}
[Nexus 7 Android Development] nikon120:
Yep, SDK is installed. I saw you found the solution, but still wanted to reply. :p

I ran into this same exact problem when I tried to flash TWRP. I ended up using the Root & CWM feature on this tool to flash CWM over the bad recovery flash.
[Nexus 7 Android Development] clockcycle:
Thanks for the confirmation, I'm at work, didn't want to install the toolkit on this PC, would prefer to play with it at home. But since the "official" CWM recovery is available in Rom Manager, I wanted to try it out, but wanted to verify I could revert if need be before doing so ;)
[Nexus 7 Android Development] WugFresh:
The rooting process in this toolkit takes care of recovery-from-boot.p

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
I saw this conversation earlier. The stock recovery is actually included in the package. What you are showing in that screenshot is the pre-screen for downloading the full factory image. You do not have to download any additional files to just restore the stock recovery. You can just use the restore stock recovery button in the advanced utilities.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Edit:

Sure. I will work on supporting this device in the next release.

{{ WugFresh }}
[Nexus 7 Android Development] bunnahabhain:
I will get my unrooted and locked Nexus 7 with Android 4.2.2 tomowrow and i want to install a 4.3 custom ROM. For rooting and unlocking i am just installing this NRT. Since i am new to the nexus 7 can anybody tell me what the latest bootloader and radio is and if there are flashable zips of either one of them?

Edit: Sorry [MENTION=3110798]WugFresh[/MENTION] i dind't intend to quote your post. That was an accident :/
[Nexus 7 Android Development] alan sh:
Is it just me? The changelog stops at 1.6.4 when you click on the link on page 1 of this post.

Alan
[Nexus 7 Android Development] totti_07:
Your toolkit is just the best. I was nervous about rooting again after I switched to 4.3 but your toolkit just makes life so easy. Thanks!
[Nexus 7 Android Development] kbocek:
1.6.8 Root Failed

I'm trying to reroot my Galaxy Nexus after an OTA update to 4.3. 1.6.6 worked great on 4.2.2 on this phone but now after wiping/unlocking and selecting root (three times!) SuperSU and Root Checker both tell me I still don't have root.

Anyone have any thoughts?

Edit:

I performed a Flash Stock + Unroot followed by the normal Unlock then Root procedure and it worked. The only difference was the first time I manually put the phone into fastboot. This time (and with 4.2.2) I let the script put the phone into fastboot.

When the script failed, after the "Rooting" message, the phone displayed the Google red triangle. This time (and with 4.2.2) it displayed some custom text while rooting.

Thanks for a great tool.
[Nexus 7 Android Development] JackMetal:
Nexus 7 v2

Wug, first I wanted to say thanks for an awesome tool. I am definitely going to donate!!

I usually root before I do anything else, but unfortunately I jumped the gun and installed all of my apps and configured everything to match my old tablet, so I now have a fully loaded Nexus 32G to backup.. ;) So.... I'm on my final backup before I unlock and root. Just to test everything out, I've done 3 backups: 1) Android Backup, 2) Android Backup with System Apps + Data and 3) Android Backup with System Apps + Data AND Shared Data. LOL - I know, it's overkill, but I was playing around with each to see how it went.

Question: Once I Unlock the bootloader (which will erase the tablet) and root, I can just do a restore of my full Android Backup with the System Apps + Data and Shared Data and it will be fully loaded back to where I am now with it rooted, correct?

Thanks again for this great tool.. I wish I had a tool like this that would work on my old Acer A500 tablet. I need to get that one set up permanently in my workout room connected to the flat-screen TV and use this new Nexus just for travel! :)
[Nexus 7 Android Development] ocariee:
same here, i doubt something error when pushing root files

after booting the image thing, it reboots my device, fine, but when it says waiting for your device... it doesnt really, it skips to "device", at this stage*, my device is still starting the system, but it says "pushing root files", then "rebooting your device to bootloader", but it is actually still starting the system with a nice X in the middle of the screen, right then i reboot to bootloader manually, ok now it really checks my fastboot, but after all i still cant open supersu, it says im not rooted yet.

*At that stage I also tried to unplug my device, but it still passed "waiting for your device", "device" and "pushing root files", thats why i doubt something wrong in here.

It worked well when I first root before 4.3, but now, I have tried over five times but still not working, so please contact me (ocariee@gmail.com), please fix the bug or help me if i did anything wrong, I cant live without root, I have so many apps that need root...

BTW, I didn't re-unlock my device, I'm not sure if this matters. Since my device is unlocked already, I think I only have to re-root, so i didn't re-unlock, as this wipes all the things.

Moreover, the backup function is not working as well, it says backed up 0MB...(poker face)

Anyway I would like to thank for the tool, it's like an all in one tool, it has everything, but maybe it is not perfect yet, at least it is not working on my device.
[Nexus 7 Android Development] kbocek:
I had already wiped my phone so wiping it one more time wasn't a problem. The phone backup itself worked fine. However the SMS backup function did *not* work. I didn't bother to check the backup directory on my PC. It was empty. So I lost my messages. Fortunately, not the end of the world. However, that function is not working as advertised.
[Nexus 7 Android Development] carpenter311:
USB debugging is on and uninstalled old drivers/ reinstalled new still can't get adb to see my N7? Am I doing something wrong? CM.10.1.2
[Nexus 7 Android Development] buffjam9011:
Which method did you use to isntall the adb drivers? I had to use option #3 (RAW).
[Nexus 7 Android Development] carpenter311:
OK I didn't even think to try a differ option. Thanks will try again later
[Nexus 7 Android Development] c0080900v:
I'm still seeking help/answer on this.

The last time I rooted it was on 4.2.1, 4.2.2 broke root access since and stuck with stock since. Should I unroot and re-root since my bootloader's still unlocked?

Or how should I proceed from here?

I'm currently on 4.3 with bootloader unlocked. SuperSU was still here even when root broke after the 4.2.2/4.3 ota updates.
[Nexus 7 Android Development] WugFresh:
Just root. That's all.

{{ WugFresh }}
[Nexus 7 Android Development] ocariee:
Now I think I should have rooted. I posted that I thought there was something wrong when pushing files to my device. I downloaded a root file which look like what i need from http://xdaforums.com/showthread.php?t=2376978 and flash it manually after the toolkit stuck in TWRP Recovery. However, now I have another problem, I can't update the binaries in the Super SU as the toolkit told me to. Apps are still not working, Titanium Backup recognize me as a root user, but I can't backup any apps, it says insufficient free storage space, but I actually have over 4GB space. Please help, it just stuck in "Installing, please wait..." while I was trying to update binaries, and never ends, over 5minutes, over 50 minutes, still installing? no way man this is so wrong! Anyone have any clues? What should I do?? This is the last step!! I've been working on rooting my device for two days!!:(

By the way, I also still can't go to recovery mode after root, but I can open BusyBox. This is strange, it seems like rooted but not 100%, I can open some apps that need root, but I cant use titanium backup to backup apps, and I can't go to recovery mode. What's going on?? I'm going crazy..
[Nexus 7 Android Development] hazwheel:
Oh, I thought Odin was samsung specific! You live and learn eh
[Nexus 7 Android Development] JackMetal:
Well..... Everything worked great except for a restore. The backups worked, Unlock and root with the new TWRP recovery worked fine, but when I attempted to restore any of the backups from before root they didn't work at all. It looked like it was working on the laptop, but it never did restore anything at all, so I'm back to having to install and configure 'everything' from scratch. That's a bummer!

Any ideas?

Thanks!
[Nexus 7 Android Development] CerB:
Trying to download your toolkit, but no file exits it ssays ?
[Nexus 7 Android Development] WugFresh:
Can you be more specific. What type of backup did you make. How big is the backup. What happens exactly when you try to restore it.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
I thought odin was Samsung specific as well.. You are saying you entered download mode on a nexus7??

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
If your device is behaving strangely, you should just reflash stock and root again. Use flash stock + unroot. Then root.

{{ WugFresh }}
[Nexus 7 Android Development] JackMetal:
Sure... As mentioned in one of my previous posts, "I've done 3 backups: 1st) Android Backup (1 Gig), 2nd) Android Backup with System Apps + Data (1.4 Gig) and 3rd) Android Backup with System Apps + Data AND Shared Data (24.4 Gig)."

I attempted a restore of each of them and they all did the same thing - It asked for the desktop backup password on the tablet and looked like it was doing the restore from the laptop, but on the tablet I saw it flash by saying Restore Started and then about a second later Restore Finished or maybe it was Restore Completed. It did exactly the same on all 3 attempts to restore each of the different backups.

My process was as follows:

1st, I did each of the backups and they all completed successfully (of course the 3rd one took quite a while) ;)

Then I unlocked the bootloader via your tool, installed root and the custom recovery via the tool and attempted a restore of each of the previous backups.
[Nexus 7 Android Development] hazwheel:
Yes, and I don't know how in did it, I was booting up, and I held the buttons to enter fast boot and a square graphic appeared in the middle of the screen with the words "download mode" in the middle!

---------- Post added at 02:24 PM ---------- Previous post was at 02:20 PM ----------
[Nexus 7 Android Development] WugFresh:
That is really weird. You should try to reproduce it some how and then make your own xda thread... That could be really useful.

{{ WugFresh }}
[Nexus 7 Android Development] didi0815:
Hi, first also thanks again to Wug for making this software that I have used successfully before.

Now I have the following problem using 1.6.8 on a Nexus 3G:

Starting with unlocked rooted 4.2.2 I tried directly to "Flash Stock + Unroot" to 4.3.0

During the process I got (see picture, long time from erasing user data resulted from a attempt to copy the content of the window of the DOS box and was not the case in other attempts!):

and the Nexus 7 was in Bootloop

Trying to bring it back using Option Soft-Bricked/Bootloop did not work using 4.3.0 but worked using 4.2.2 again.

I repeated the process 2 times ("Flash Stock + Unroot" to 4.3.0 after rooting 4.2.2. again) and it was always the same.

Now I'm on 4.2.2 stock and wait for OTA update to 4.3