yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] johnhimm:
No, my bad. The stock image is NOT released on the Google Servers for the N7 2013 edition (FLO) only the original N7.
[Nexus 7 Android Development] WugFresh:
Stock recovery gets reflashed afterwards. The reason the toolkit did this is because fastboot boot twrp 2.6.0.0 has been reported to not work properly on many nexus devices, so the toolkit just flashes it and reflashes stock recovery. However on the original Nexus7, the default behavior is to use temporary TWRP because I have tested it on that device and it would with 4.3.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
There is not to my knowledge. Do you have a link? Last time I checked the google factory image website, it does not have factory image packages for the new Nexus7 devices.

That is why I coded in that message.

{{ WugFresh }}
[Nexus 7 Android Development] danvee:
That was going to be my next question.... Wondering how you got it....
[Nexus 7 Android Development] Lachaine:
Well this was my question, why it did not reflashed the stock recovery? The twrp was flash, not temporary. I just flash the stock recovery using your toolkit recovery.img 31/12/2008 or this is not the thing to do, to get the stock recovery.
[Nexus 7 Android Development] WugFresh:
If you have a nexus7 2013 then there is no stock recovery img available yet for it to flash. If you have the original Nexus7 it should have reflashed stock recovery.

{{ WugFresh }}
[Nexus 7 Android Development] Lachaine:
well I have the nexus 7 2012 not the 2013. And it did not reflash the stock recovery. (first pass was twrp temporary, second pass, it flash permanent twrp) I try several time, and only solution was to install manually.

I just double check that I choose the nexus 7 wi-fi, and not nexus 7 v2 wi-fi in the toolkit.

I just test the function restore stock recovery in the toolkit, and there was no file, so it is starting downloading the recovery-stock-nakasi-4.3.0-jwr

So when using root (and not with custom recovery) there is no link to downloaded if it is not there, and put by default the twrp. I will try to root this time with the downloaded file

---------- Post added at 11:08 AM ---------- Previous post was at 10:49 AM ----------

Still flash the twrp by default, no stock recovery.

---------- Post added at 11:21 AM ---------- Previous post was at 11:08 AM ----------

Function restore stock recovery is working, boot/flash image, recovery, and file is working. But if you use root function without check the custom recovery, it put twrp by default, and not the stock.
[Nexus 7 Android Development] TadeoNYC:
Site is crashed again, here is link to Goo as well http://goo.im/devs/WugFresh/NexusRootToolkit/NRT_v1.6.6.sfx.exe
[Nexus 7 Android Development] WugFresh:
I will see if I can reproduce this, if so I will fix it. Not sure why it's happening, but I will certainly look into it

{{ WugFresh }}
[Nexus 7 Android Development] Nitsson:
Sorted. Just had to use 'Flash Stock + Unroot' for a bootloop device, followed by unlock and root. Works like a charm now.
[Nexus 7 Android Development] cpomd:
Failed to update

I have a Nexus 7 (2012) ver4.22 and rooted it on V164 of your Toolkit. I have now updated to v166 and attempted to update to V4.3 unsuccessfully. I think I havent done too much damage but when i check for updates it says the last one was in 1970? If its possible please give general advice and perhaps point me to a tutorial.

Tia
[Nexus 7 Android Development] WugFresh:
Just use "flash stock + unroot".

{{ WugFresh }}
[Nexus 7 Android Development] mwhite5471:
Online now....anytime you're ready.
[Nexus 7 Android Development] david251:
Had a question that I wonder if anyone can help me with. I have a nexus 4 (T-mobile US). I just got it yesterday and last night it upgraded Android to 4.3 (JWR66V). Today, I opened NRT (I already had it for a Nexus months ago running 4.2.2) and it updated. I was able to unlock the bootloader with no problems. When I try to root and select the option for custom recovery, it seems to run through the process (rebooting a few times, messages saying "pushing files" and "rooting"). The last thing I see on the phone is Android lying on his back, hood open and what looks like a red triangle? It stays there for about 2 or 3 minutes, then reboots. After that I get nothing more from NRT. The phone seems to work just fine, but there is no custom recovery on it and Root Checker says there is no root access.

Any ideas what I'm doing wrong?
[Nexus 7 Android Development] NLBeev:
You can root N7 with kit 1.6.4.

Http://Www.wugfresh.com ; quick tips.

Http://www.androidpolice.com
[Nexus 7 Android Development] niav:
Like Lachaine I also have got the TWRP recovery flashed on an original Nexus 7 when I rooted 4.3. I did not have the flash recovery box checked. Can you tell me how to reflash the stock recovery and will this procedure result in data loss? Thanks in advance.
[Nexus 7 Android Development] alan sh:
I''ve just used v 1.6.6 to push TWRP and root my unlocked 4.3 stock build. It all went very well. I've now got a custom Rom and Kernel on and I'm happy with my original N7 (apart from the fact that the speaker buzzes at me - but that's nothing to do with roms).

Alan
[Nexus 7 Android Development] Lachaine:
In the toolkit go to, advance utilities, restore stock recovery. No data loss
[Nexus 7 Android Development] niav:
Thanks Lachaine. Does restoring stock recovery wipe the device?
[Nexus 7 Android Development] Lachaine:
No wiping, no destroy, no loss data.
[Nexus 7 Android Development] niav:
Thanks again.
[Nexus 7 Android Development] barbo:
Still stuck on "checking ADB status"

I posted the quote below and Wug said to wait for 1.6.6. I waited and have just tried again with the 1.6.6 version and have the exact same problem. Basically, I rooted with NRT (I think 1.5.something) months ago and now I just keep getting hung up on "checking ADB status". I have tried all four of the driver install methods NUMEROUS times and the same thing happens.

My knowledge is very low but I am good at following directions. I checked and I still am rooted and unlocked (with NRT). I can't believe I am the only one with this problem.

Question: should I be on MTP or PTP when using NRT or doesn't it matter?

Thanks for any help.
[Nexus 7 Android Development] cpomd:
Ran the above and updated to 4.3 and got a male voice reading to me and everything was sluggish. I managed to get into settings and no voice but everything seems to require a double tap and scrolling up or down requires pinching the screen and its very slow?
[Nexus 7 Android Development] niav:
I have done this. To check if it was successful I chose Reboot Recovery from the Toolkit. I get an Android on his back with a red triangle and the phrase "No Command." under him. Is this to be expected?
[Nexus 7 Android Development] WugFresh:
I have heard this reported by more than one user, I am looking into it and will roll out another release asap to resolve this occurrence. Many users have reported complete success though. I am confident I will figure it out either way. Stay tuned.

{{ WugFresh }}
[Nexus 7 Android Development] Lachaine:
Yes
[Nexus 7 Android Development] digixmax:
Same here, after I reverted to stock recovery so as to do the 4.3 update.

My update to 4.3 also failed mid-stream of installation (horizontal android with red mark on its tummy).

Should I assume that these two problems are related?
[Nexus 7 Android Development] melfunn:
I got it to work. In the toolkit go to Options. Highlight "Temporary Utilizing TWRP to complete the operation". Check ab, img & zip in Associate file Types. Apply and run Root(with Custom Recovery). Profit.
[Nexus 7 Android Development] digixmax:
Good for you, but please do not quote some other post that is about some other entirely different issue.
[Nexus 7 Android Development] melfunn:
Sorry. I'll try to do better next time. Please forgive me.
[Nexus 7 Android Development] stewarta:
If ADB does not connect

Went crazy trying to get the 'ADB devices' command in the COMMAND PROMPT to recognize the Nexus 7 when NRT 1.666 could not.

The answer is unplug from the PC, then to go into the NX7 Settings >> Storage >> and from the top right icon set the device as a camera. It will then connect fine. Grrr!
[Nexus 7 Android Development] TheByteSmasher:
For those having issues Mounting their Nexus 7 as MTP (at least 2012) in Windoze 7.. Check out this thread:

http://xdaforums.com/showthread.php?t=2390296
[Nexus 7 Android Development] svan71:
Happened to me

Try return to stock again, but try another usb cable on a different port....worked for me
[Nexus 7 Android Development] BTr_RJ:
Here on my Nexus 4 and 7v1 everything was ok, rooting was never so easy... back to the HIDE SOFT KEYS (damn good tool) thanks WUG!
[Nexus 7 Android Development] dragxdk:
wug is the best, thanks for your hardwork :thumbup:

tapatalk
[Nexus 7 Android Development] yaatzek:
My antivirus (fsecure) blocks wug_updater on latest 1.6.6 saying there's a trojan inside and delete's it. Does it happen to you also?
[Nexus 7 Android Development] dragxdk:
i have f secure on my pc and no problem, strange ? :confused:

tapatalk
[Nexus 7 Android Development] menomenic:
roottoolkit nexus 4.3

hello,

WugFresh

When using your toolkit with my nexus 10 android 4.3 it can't root the device.

Everything goes fine it unlocks my device but when rooting almost on the end i get a android on his back with a red !.

And on my computer it says connect your device.

When i reboot the device there is no supersu or whatever installed.

No Worry i got the problem go to settings in the nexus root toolkit than go to custom recovery and select utilize clockworkmod touch recovery by koush
[Nexus 7 Android Development] Toronadian:
So I'm trying to use the toolkit to flash stock and unroot to 4.3, but when I do that, it goes into fastboot mode and just stays there while on my computer in a window when the scripts are running it says that I should wait for it to run reboot by itself. I waited but nothing happened.

Also, when I choose to flash stock, I keep selecting download the image for me, so does it just overwrite the one I downloaded earlier, and whereabouts is it?
[Nexus 7 Android Development] digixmax:
I am using NRT 1.6.6.

Given my above problem with flashing back to stock recovery, would "Flash stock & unroot" work?
[Nexus 7 Android Development] rhodareyes:
does this toolkit comes with busybox after rooting
[Nexus 7 Android Development] ilegales:
Hi Wugs or someone else

.I was going from a rooted 4.2.2 to 4.3 when it stopped at the fastboot mode stage

where you have the options of recovery mode = start and power off

well i tried the start loads of times and it did not start so in the end i thought i would power off and start over

sadly the nexus never ever comes back on again

i only see a black screen and cannot do the power and vol up or down

pc does not recognise it but i dont have mabe the correct drivers

please can this device come back from its deep sleep

please some pointers what to do
[Nexus 7 Android Development] tamanaco:
Error!... I have a N7 running JB 4.2.2 with TWRP 2.6.0.0, Bootloader unlocked, Custom Recovery and rooted using this toolkit. No other system updates that I can think of other other than root and the Voodoo OTA Rootkeeper. I have not installed any zip files via Custom Recovery or have a custom kernel running Got the message about the OTA and decided to update. The first thing I did was used the Toolkit to restore the Stock Recovery. Rebooted and started the OTA. About half way through the process I get the dead Android with a red triangle with a !. I rebooted the N7 and noticed that when I boot into recovery I now get the same dead Android. My guess is that the recovery installation failed, so I got the 4.2.2 recovery image and flashed using adb. Well, the dead android still there when I boot into recovery. I decided to use GooManager to re-install TWRP 2.6.0.0 and so I'm back to where I started. TWRP recovery boots fine, but I'm still running 4.2.2. Any suggestion as to what steps I should follow and what images I should use to update to JB 4.3?
[Nexus 7 Android Development] rupchatterjee:
Bricked and Formatted OS

Hi I have formatted My Device (Nexus 7 3G 2012), formatted, Formatted OS. TWRP asks for password, does not install any ROM. Device gets hanged in Booting Downloaded Image and PC in stays in "Waiting for your device". Please suggest
[Nexus 7 Android Development] htc6500uk:
Excellent tool - sorted out my Nexus 7 first time after OTA had de-rooted it.

Many thanks.
[Nexus 7 Android Development] barbo:
Still no luck with drivers

Thanks for trying to help me, svan71 ... I tried a different cable and different port (front and back) and no luck.

BTW, this might be a clue to my problem (?) - when I try to install the drivers using solution #4 it says I have the latest and I move to the bootloader install section (6). When I press "reboot bootloader" it doesn't reboot my N7 - nothing happens except the "rebooting bootlaoder" box which hangs and freezes NRT. So, I have been shutting down my tablet and putting it into bootloader via the hard buttons and shutting down NRY with task manager. Then I come back and continue with solution #4 and # 6 which also says drivers are up to date and the driver test always hangs on "checking ADB Status" and NRT needs to be shut via task manager again.

Where am I going wrong?
[Nexus 7 Android Development] digixmax:
How do you determine which recovery is in emmc?

And how do you flash stock recovery manually?

Thanks.
[Nexus 7 Android Development] mwhite5471:
Any ETA on the dead android w/ red triangle fix (failure of TWRP to load)?

I have build JSS15J btw on my N7 v2.
[Nexus 7 Android Development] Stransky:
Hi

Not sure that the toolkit works with the V2 Nexus, and that Is why you are having the problem with TWRP. It only shows JWR66V firmware in the menu.

Stransky
[Nexus 7 Android Development] ALD3:
Not sure if this is the same but for me, I have always had to manually boot into bootloader. Then click OK to check it again. Same with restarting it. I restart it when toolkit is waiting for it and let toolkit find it. Mine has always been that way, works but I have to manually do it as toolkit ask for it. Maybe this will help.
[Nexus 7 Android Development] jdagreek:
I had this problem on my N7 v2

first I went to Goomanager and reloaded the script ...

then I used the Nexus Restore program ... I was back to perfect
[Nexus 7 Android Development] ninjames:
Still no fix for rooting Nexus 4 4.3 with stock recovery? I read several pages back that it had to do with TWRP having an error. Is that fixed yet? I don't really know how to flash TWRP itself to do this so yeah ..
[Nexus 7 Android Development] WugFresh:
Well to flash twrp itself you can with advanced utilities flash recovery button. But in regards to your question, yes I did say that yesterday, it takes some time to code. I am trying to get v1.6.7 out tonight ideally but I am not sure yet.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Tonight I believe.

{{ WugFresh }}
[Nexus 7 Android Development] Amarali123:
Coming from PAC, I wanted to go ahead and revert back to stock using your tool. For some reason, downloading the .zip of the 4.3 image off Google's site didn't work -- the command prompt kept saying that boot.sig and a few others weren't found. So I went into the archive and extracted those in the same folder and it went ahead and flashed it, but I got stuck on the boot-up animation for over 20 minutes.

I went into the Toolkit again and chose flash stock/unroot but with the boot loop option checked and after a few operations went well, I got a archive does not contain boot.sig, recovery.sig and system.sig; error: out of memory.

Recovery gets me to a dead droid with a red triangle. Can't flash a custom recover either, because the device isn't adb recognized by the kit (I guess because I can't turn on USB debugging).

What do I do :confused:
[Nexus 7 Android Development] ShaneAR:
Has anyone ever lost root for no apparent reason?

I was on stock 4.3 unlocked (Original N7) and did the root process. It all seemed fine as I installed some apps I use when rooted (adaway, Titanium Backup, Trikstermod etc) and they seemed fine. Then, all the sudden root was gone. Weird.

Anyway, I'm going to run it again and go from there...

EDIT: Rerooting didn't help. So, I'll try unrooting and back to stock, then try again.

EDIT # 2: Out of curiosity, has the install process for busybox been changed? It's been awhile since I've last used this, but it installed in seconds compared to a minute or so previously...

EDIT 3: Found out the issue was with M-kernel. a58 and a59 break root. Not sure yet about a60.
[Nexus 7 Android Development] melfunn:
For those trying to use the Root w/ Recovery button and ending up stuck w/ the dead android man instead of the TWRP menu, try, in options, checking img and zip boxes under Associated files. That helped me to load the TWRP menu and thus install the root zip file. It's worth a try.
[Nexus 7 Android Development] barbo:
one step forward, two steps back

Well... I decided to try using my laptop instead of my desktop and voila: I got past the adb checking (finally). All looked well and then just like Amarali123, the command prompt said a few files (boot, recovery, system sigs) were not in the archive then it continued on a bit and everything stopped at this: sending 'system' then after at least 20 of nothing happening, I closed the command window and hit Flash stock & root but this time from "soft brick" then I got an error message saying "fastboot stopped working", Then it said rebooting into bootloader failed. Will 1.6.7 help me when it comes out? I don't have the knowledge of others regarding extracting and flashing stuff so I think I am out of tricks.
[Nexus 7 Android Development] Thompcd:
I also had this problem, it seemed like it went into a deep sleep and the power button wouldn't wake it. I was trying to unlock, and then it seemed to just... stop.

All I did was make sure to hold the power ONLY for like 20-30 seconds (seemed like an eternity) and then it finally resumed normal bootup.
[Nexus 7 Android Development] Amarali123:
I woke up to a potentially bricked device, what the flux? I actually finally got stock Android 4.3 and rooted it just fine last night. The device was running okay and everything. I went to sleep and woke up to a powered off PC and the N4's LED showing red. The PC now recognizes the device as QSHUSB_DLOAD and it just won't power up anymore.

Funny, because it must have happened out of thin air (mostly).
[Nexus 7 Android Development] cpomd:
conclusion

I have posted about how slow and unuseable it was after doing the above to 4.3 but cannot find it (finger problems maybe) so in conclusion I followed above instructions except that this time I flashed stock 4.22 which allowed me to update to 4.3 alls well that ends well. many thanks
[Nexus 7 Android Development] mmvic:
Thanks for this Wig!

Just rooted my new nexus7 v2, what a great tool

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
[Nexus 7 Android Development] AlexM555:
Thanks for the 4.3 update in your 1.6.6 toolkit.... My Asus Nexus 7 updated without a hitch and runs beautifully!

Edit: I am surprised that my OTA 4.3.3 update went without a hitch and updated my Nexus 7 without any errors. It was then a simple matter to run WugFresh's 1.6.6 toolkit to root my tablet.... In previous updates, I would get an error message when I'd try to do the OTA. This time, everything ran without a hitch....weird, but welcome. :)
[Nexus 7 Android Development] capitansky:
thanks amazing update
[Nexus 7 Android Development] mwhite5471:
How did you do this without getting the dead android?

Did the TWRP screen load up OK?
[Nexus 7 Android Development] xhepera:
I was unlocked and rooted with Toolkit v 1.6.3

Running stock 4.2.2 with TWRP recovery and Franco kernel. N7 2012.

I used 1.66 to restore the stock recovery. Rebooted. Tapped on the install update button (in the 4.3 ota notification bar) and the install started, then failed.

So I restored the stock kernel. Now I have no notification and checking status shows that I am up to date, even though I have 4.2.2.

Also, I tried booting into recovery and get the dead android with red exclamation and a "no command" error message. So I restored TWRP and at least have a recovery now.

So, any pointers on how I might be able to get the ota again; and any ideas as to why stock recovery won't boot? Well, actually I guess the ota is still in my /cache directory; but how to activate it?

Thanks!﻿
[Nexus 7 Android Development] melfunn:
If you are trying to use root with recovery and ends up with dead android man and not the TWRP menu, try this. In Options, check the img & zip boxes under Associated File extension. It worked for me.
[Nexus 7 Android Development] digixmax:
This did not work for me in restoring stock recovery.

---------- Post added at 05:28 PM ---------- Previous post was at 05:22 PM ----------

Go to Settings->Apps->All, force stop and clear data for GoogleServiceFramework, then go to About Tablet->System Update to check update, you should get 4.3 to download again.

[Afterward, if you have problem downloading/updating apps from the GooglePlay store, go to Settings->Accounts and delete then re-add your Google account].

But unless you have stock recovery restored, installation of 4.3 will continue to fail. At this point it appears that the only potential way to restore stock recovery is to restore stock ROM (and it would be great to get confirmation from someone who has taken this path with NRT 1.6.x), or simply to wait for the problem to get fixed in some next release of NRT.
[Nexus 7 Android Development] mmvic:
I did get the dead android,

I think this is what I did...

Unplug it, hold power button to turn off.

Boot into fastboot by holding vol down and power, push power button once screen comes on.

On tool kit go to advanced settings, in middle column click fastboot then boot into recovery, latest update.

In twrp just restart system.

Then continue to root

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
[Nexus 7 Android Development] xhepera:
Thanks for the reply, Digixmax. My understanding is that the GoogleServiceFramework hack messed up notifications. Not so?

Re having a stock recovery; I did restore the stock recovery but am unable to boot into it. Dead android with (!). :( Which is why I reflashed TWRP for the time being.
[Nexus 7 Android Development] digixmax:
I have not encountered issue with notification.

Same here.
[Nexus 7 Android Development] c0080900v:
I haven't re-rooted my N7 since the 4.2.2 ota update. Pretty sure it broke root, I'm on 4.3 OTA now.

Would I have to re-unlock my bootloader, my bootloader's still unlocked. So I'm wondering if I should bother, or unroot and re-root it.

The only thing is I want to back-up my Plants VS Zombies progress/profiles before proceeding. ES File Explorer couldn't back it up, Titanium Requires root pretty sure. How should I go about this without losing the progress, it's the only thing I don't want to lose, I've got myself covered for everything else.
[Nexus 7 Android Development] Sblesh:
Theoretically with the new play services and "app data" in Google account you should be able to delete PvZ and reinstall it without losing data, because the app data save score achievements etc on cloud.

But I'm not sure, so be careful!
[Nexus 7 Android Development] c0080900v:
Pretty sure the app dev/game dev has to support app data sync.

I only have my N7 as my only Android device.

I'll try it on a friend's phone, with their permission of course. Login and install PvZ in hopes that the data syncs over just to verify.

Thank you for your reply and trying to assist, much appreciated.