yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] demandarin:
Update: progress of sorts.

I figured how to get adb recognized. Seems I can only get it to recognize my device in adb when i use your option to boot into temp recovery(twrp). Pop up came up on my PC for android adb. So I choose automatic install for drivers. Once it was done, I went into your option to flash zip. Now adb device recognized and said pushing Team Shogun AOzkP rom(rom I chose). On my device, on fastboot screen, it said booting downloaded image. The PC portion finished but my device didn't seem to boot anything up. I rebooted and still stuck on Google screen. So I tried again. This time I wanted to push the rom file to my /sdcard folder on device. So I can try to see if trap will flash it. Well it pushed the file to my device and PC said it was finished. Now ill use your tool to boot I to temp recovery again and see if rom is in there now. If it is, them ill try to flash it with twrp. Man, I hope this works..lol. its progress though ;)

Update: tried flashing zip. PC said it was done but was a no go on nexus. Tried pushing the rom to /sdcard. PC said pushing file then said done. Once I booted back into temp. Twrp recovery, no file actually got pushed. Oh well...lol. at least adb commands were recognized. I even tried rooting my device just in case. Said it did but didn't make any difference.

I'm through with this device for tonight. :)
[Nexus 7 Android Development] Dubbin1:
Hey Boss any news on this new update?
[Nexus 7 Android Development] ddxfish:
Excellent. Took about 5 minutes to do with the one click solution, went without errors. This was so easy to do on my new Nexus 7. Here are my details:

WugFresh one click root version 1.5.3

OS: JB 4.1.1

build number: JRO03S (I told the root kit program that it was JRO03D because the JRO03S was not listed, had no problems)

Hardware: Nexus 7 16gb

Thanks to all of the geniuses that made this possible!

<3
[Nexus 7 Android Development] demandarin:
More progress but still failing.

I was able to permanently flash a custom recovery, Twrp. Then after several failed attempts, I was finally able to "push" a couple roms to "/" of my device. I pushed team EOS and team shogun rom. I can see them within twrp to install. But when I go to install/flash, it fails.

It says:

E: Unable to mount. '/cache' ( tw_mount)

INSTALL /Teamshogun_AOKP_v4.zip..

FInding update package...

E: unknown volume for path [/TeamShogun_AOKP_v4.zip]

E: can't mount /TeamShogun_AOKP_v4.zip

Verifying file systems...

Verifying partition sizes...

E: Unable to mount '/cache' (tw_mount)

Error flashing zip 'TeamShogun_AOKP_v4.zip'

Any ideas?

Update: lmfao

Well I was thinking, let me use twrp file manager to copy the rom from '/' to '/sdcard'. I did that. Now file is on /sdcard. So I tried to flash again. Now it went through true process and said successful. I haven't booted it up yet to see but looking good so far. Will post back shortly if it worked and I'm finally up and running again on my 2nd. Nexus.

Update 2: I'm up and running again. Dang..lmao took me long enough. Much thanks to Wugfresh and especially Mozgus. They gave me the ideas to try. Especially with Mozgus recent suggestions. He was in same situation as me and got it working. Through determination, I finally have it working again. Much thanks to XDA crew ;)

If anyone finds themselves in similar situation, you can look at My previous posts to see how I solved it. Or I could detail it again in one post if needed.
[Nexus 7 Android Development] yococs:
can't get to recovery mode

sir just unlocked and rooted but i cant seem to get to recovery mode.... when i go to recovery mode i get stuck in an android with an exclamation point in his chest, can you help me on this? thanks
[Nexus 7 Android Development] demandarin:
Did you install a custom recovery like Cwm or Twrp to your device?
[Nexus 7 Android Development] ekanix20:
Does this work for 4.1.2?
[Nexus 7 Android Development] WugFresh:
Yes, the toolkit will unlock and root it. Use "Any Build" Mode. Once google releases the official factory image packages I will add official support so you can use all the toolkit features. Or if someone could send me a nandroid or link me to the ota update zip I can work on getting it officially supported now.

{{ WugFresh }}
[Nexus 7 Android Development] harjon:
Have both a Nexus 7 and Galaxy Nexus. I have used this tool to unlock the bootloaders and root the devices on 4.1.1

I'm not into changing roms, just want root for things like titanium backup, reboot apps, market enabler, etc..

Keeping that in mind, my recovery I kept stock.

Correct me if I'm wrong, but in order to update I should -

1) make a backup with titanium backup

2) Unroot and re-stock image the device

3) Upgrade to 4.1.2

4) root the device which will again reflash the phone (once support is added to the wug toolkit)

5) restore my backup

Am I missing anything?
[Nexus 7 Android Development] pixelens:
Here's the link to the OTA update zip. http://v21.lscache1.c.android.clien...signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
[Nexus 7 Android Development] WugFresh:
Sweet, thank you! I will try and roll out v1.5.4 late tonight or tomorrow.

Edit... whoops. Looks like I need a nandroid. (just the boot.img from it). Sorry for asking for that zip.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Ok, so I am releasing v1.5.4 tomorrow for sure. :)

It will include official support for the N7 4.1.2 as well as all the other latest builds for all the supported devices.

I fixed some small bugs as well as took away the "Always on Top" attribute for the "Please be patient" splash screens when performing long backup operations, as requested by someone in this thread. I have been working on some new features but they wont be ready until v1.6. This is just a small update.

To update the toolkit when I release it tomorrow, just go to "Help" in the toolkit and select "About..." that will prompt the updater.

I am scared that we are going to crash the server containing the update... but we will see I guess. More info on that tomorrow. :) Now back to midterms for me :/

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Duplicate post... not sure how to delete on here?

{{ WugFresh }}
[Nexus 7 Android Development] charlieMOGUL:
You're not missing anything, it's just too much.

If your bootloader is unlocked, and you are rooted, you can easily install the update from Google manually.

To apply the update (a bit out of scope in this thread) boot into recovery mode (adb reboot recovery), press power + volume up, select apply update from ADB, and enter adb sideload <filename_of_update.zip>. That's it.

Afterwards you can re-apply root using the toolkit. Works perfectly.

Tested with 4.1.1 -> 4.1.2

Good luck,

charlieMOGUL
[Nexus 7 Android Development] rodem77:
In order to update with official OTA you don't need to unroot, to have the OTA you have to avoid to change stock recovery (so if you used temporary ones from the toolkit is ok) and to avoid any change to system partition. For example, busybox if is installed in directory System\bin can modify your system partiton and in this case, also if you unroot, you can't have official OTA. If you have done some modification to the system partition the only way to have an official OTA is to flash the original system partion from a backup or from an official google rom.

Anyway, if you wait that OTA is out and you download it from XDA, you can flash it using a temporary recovery without ony unroot or system partition re-flash.

In both cases, a backup is always a good idea!
[Nexus 7 Android Development] ZuperMario:
Hello,

so if i used WNRT with UNLOCK button, and ROOT button + CUSTOM RECOVERY flag, i receive OTA updates?

Thanks.
[Nexus 7 Android Development] rodem77:
No, this flag mean mean that you've flashed a custom recovery (with this flag the tool permanently flash a custom recovery overwriting the stock recovery) and you can't get the official OTA.

To better understand all, read here:

http://xdaforums.com/showthread.php?p=29733879#post29733879

But this is not a big problem, using your custom recovery you'll be able to flash the OTA. The only difference is that you have to manually download this OTA, copy it in your SD memory, restart your tablet with custom recovery and flash this file.

You can also use the toolkit with the same results.

---------- Post added at 02:39 PM ---------- Previous post was at 02:35 PM ----------

With this new version do you expect to have a better compatibility also with Nexus S 9023? In a previous post I wrote that with your tool I had no problem to install driver and to unlock but I had problem to root. Thankyou.
[Nexus 7 Android Development] arkhan11:
The guide in my signature is not automatic but it works with any version :)

It uses the wugfresh toolkit drivers so thanks to him.
[Nexus 7 Android Development] BriVG:
Wugs,

just looking through the file structure of 1.5.3 and I don't see a stock recovery for Toro in the stock recovery folder, am I missing something?
[Nexus 7 Android Development] arkhan11:
If you want I could host the toolkit in some of my cloud storage accounts. Just ask. It seems there are many people waiting for.

Anyway, about the update, my build is JRO03S so I think I have to wait.

Correct?

---------- Post added at 04:27 PM ---------- Previous post was at 04:18 PM ----------

This is right if you have stock recovery. Isn't it?
[Nexus 7 Android Development] coldheater:
Your link is down :(.
[Nexus 7 Android Development] WugFresh:
Is the link still down for you? I think my fears were realized though. Everyone trying to get the update (which I haven't published just yet) and its basically like a DDOS attack on my server. The way I built it though this shouldn't happen. The actual update file will be hosted on another server. The toolkit checks my server for a small ini file which gives it the location of the download, the hashvalue, and its version number. Then it downloads it from the other server, checks its integrity, and installs it. I would be surprised if lots of request on such a small file would knock out my servers. If it does, that is really lame and I should probably switch my host account.

People please hold off on trying to update until I announce here that it is published. I am going to contact my host and warn them in advance what it happening.. maybe they can dedicate me some more bandwidth or something.

Stay tuned.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
I have the vzn gnex, and I used the 4.0.2. maguro stock recovery with success (for OTA updating etc) for that build, so I didn't bother with the toro one to try and save space. For the new toro build the new recovery will be included. You are not missing anything. Some files are used more than once.

{{ WugFresh }}
[Nexus 7 Android Development] BriVG:
Good to hear, thankz:)
[Nexus 7 Android Development] WugFresh:
Ok, I think I came up with a solution so my servers wont crash again during the update. I will be monitoring it heavily once I release it.

{{ WugFresh }}
[Nexus 7 Android Development] limpet:
I rooted with Toolkit 1.5.2 so I used that to flash the update zip. In Advanced Utilities under "Flash zips w.Temp CWM" I selected "File is already on sdcard" and clicked on "THEME/MOD zip." Followed instructions to clear caches and flash the file.

Rebooted as shown in the screenshot. Root was lost so I loaded Toolkit 1.5.3 and clicked on "Root" (with custom recovery not checked). All seems well, USB OTG is working fine. Thanks WUG.
[Nexus 7 Android Development] dude_uuk:
Where is v1.5.4? OP still says 1.5.3 :)

I am already in 4.1.2 but lost root. I am hoping that I can use this to root my device since 1.5.4 will support 4.1.2. Thanks.
[Nexus 7 Android Development] WugFresh:
You can root it with v1.5.3 using the "Any Build" mode from the pull down menu. 1.5.4 will be out soon, I just had to work longer on it today because google just released 4.1.2 for the Gnex as well. Once its up the OP will be completely updated with all the info.

{{ WugFresh }}
[Nexus 7 Android Development] limpet:
The zip I used:

http://android.clients.google.com/p...signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
[Nexus 7 Android Development] dude_uuk:
Multiple thanks mr. Wugs. Honna try that now.:)

---------- Post added at 09:08 AM ---------- Previous post was at 08:44 AM ----------

One more question, when installing busybox which installation i have to choose? is it smart install or normal install?
[Nexus 7 Android Development] WugFresh:
Personally I use "smart install" and I set the "will be installed to" to /system/xbin - but its a user choice.

{{ WugFresh }}
[Nexus 7 Android Development] arkhan11:
Is this option better to avoid reinstalling busybox after the update? I've busybox installed in /system/bin
[Nexus 7 Android Development] snipe2nite:
Thanks again WugFresh for being such a solid person and providing a great toolkit!!! I have PMed a mod to get your thread on the stickies list being your toolkit is 2nd2none. You have helped lots of people, provided updates FREE of charge, always responding to questions and keeping it real 24/7!! I have learned lots from you just reading this thread, much respect to you my dude..... :highfive: :highfive:
[Nexus 7 Android Development] Deusex74:
hi,i just got my new nexus 7 with latest JB on it.

Does your tool works with JB too,so i can root without problems?

Thanks in advance ....
[Nexus 7 Android Development] modstorm:
Read a page back it says to select the 'Any Build' option
[Nexus 7 Android Development] dirtyhamster73:
I updated my Nexus 7 to 4.1.2 with twrp and then re-rooted with wugfresh tool kit and forgot to change it to "any build"...it rooted fine, no problems with the the old build on the nexus 7. (I forget the build but I believe it was : "(JRO03D)"
[Nexus 7 Android Development] TheBronze:
First, excellent tool! Thanks for all your hard work

I've installed 4.1.2 via side loading.

I boot unlocked my nexus 7 manually via ADB.

Then I started on a fresh PC, did the driver install (which was excellent) and the proceded to do the root without the custom recovery.

It goes through the process fine but doesn't seem to actually be able to load TWRP. Instead, it just boots back into the regular image.

I've tried this with ANY as well as 4.1.1.

Has any one else had this same behavior?

Thanks!
[Nexus 7 Android Development] trungdtdev:
I updated my Nexus 7 to 4.1.2 with twrp and then re-rooted with wugfresh with uncheck Custom Recovery all perfect !

But when i reboot to Recovery Fail TWRP not load... :( Someone guide me to install TWRP for 4.1.2 thanks in advance !
[Nexus 7 Android Development] rodem77:
If you reboot after 4.1.2 uptate you lost you custom recovery, I think that you had to use root option with "check" custom recovery. But you can flash custom recovery again using advanced features of the toolkit.
[Nexus 7 Android Development] dirtyhamster73:
I keep checking the toolkit by clicking on "help" to see if the update is out and I'm getting "can't access update server. If this continues contact wugfresh". Is this pop up suppose to happen? Or is it just my toolkit? Thanks!
[Nexus 7 Android Development] trungdtdev:
I'm flash openrecovery-twrp-2.2.2.0-grouper.img but still error (the red triangle picture and just freezes) can't boot from Revovery mode ! someone help me
[Nexus 7 Android Development] WugFresh:
I discovered that my updater wont work if there are spaces in the path to the toolkit. Frustrating because I can't simply update the updater (catch 22). I will enable the update now, and then post the full version in the OP.

If you want to take just the update, you will need to move the toolkit folder to a path with no spaces in it.

The default directory is:

C:\Program Files\WugFresh Development or C:\Program Files (x86)\WugFresh Development

Both of those paths have spaces in them. Just move it to something like C:\NRT and then the update will pass the hashcheck step and work.

The full version will be posted in the OP shortly.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Version 1.5.4 is up now. I am going to spend more time getting FAQs together now, and making the OP complete.

{{ WugFresh }}
[Nexus 7 Android Development] dirtyhamster73:
Who's better than you? Nobody, that's who :) Thank you so much!
[Nexus 7 Android Development] caplang:
Just installed v.1.5.3 last night, moved to C:\NRT, when I opened NRT, it asked for Update.

It's worked. I just don't have good internet connection, so I will do update later.

Thanks, WugFresh. Great tool.
[Nexus 7 Android Development] rodem77:
I think that you have the stock recovery, it is able to replace itself after every reboot, you have to rename/delete a file to avoid this.

Read this:

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

"If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p"

Did you tried also with the new version of the toolkit and the new version of TWRP?

http://www.teamw.in/project/twrp2

And another question, if you use advanced utility of the toolkit, you are able to reboot in temporary TWRP? Consider that if you permanently flash a custom recovery you'll not be able to have official OTA (anyway you can flash them manually with TWRP temparary or pemanent).
[Nexus 7 Android Development] ZuperMario:
BusyBox

Hello,

after rooting with this nice tool, i have a new icon: BusyBox Free. Starting the app, i read:

"BusyBox null is installed"

and

"BusyBox is installed to sh; <stdin>[1]: : not found"

with 2 buttons: Install and Uninstall.

What is this app for?

And i have to "Install" or just do nothing?

Thanks!
[Nexus 7 Android Development] iamelton:
u should install it.. busybox is the swiss army knife that acts as the supporting app for many other utility apps..
[Nexus 7 Android Development] arkhan11:
if I update to 4.1.2 my nexus 7, will I have to reinstall busybox? I've installed it in /system/bin
[Nexus 7 Android Development] TheBronze:
Wug, thanks for taking the time to update the tool!

Hm. Still having the same issue where it says it is booting into TWRP but just boots 4.1.2 instead. I updaed to 1.5.4 and selected the correct build in the tool. i also verified that the version, JZO54K, is correct.

This is with no prior root on 4.1.1, so I'm wondering if there isn't some file that others before me have had set an ACL on when they rooted on that version that has either moved or...?

Questions:

Can I still drop back down to 4.1.0 with this tool now that I am on 4.1.2

Should I drop to 4.1.0, root, then update to 4.1.2?

Is it possible that side loading via ADB is causing this to behave differently tha if it was an OTA update?

Can I have a puppy?

Thanks! (especially if I get the puppy)
[Nexus 7 Android Development] damagedgoods:
Awesome

Hi Wug,

Just used 1.5.4 to unlock and root my Nexus 7 (C90) and I have to say you've done a sterling job sir. Everything about the process from start to finish was painless, angst free and fully informative. If only my tf300t was so easy to play with.

I see you wanted people to post if their JB version wasn't listed and I'm sure you're aware of this already but JRO03S isn't listed.

Thanks again for all your work.

@dirtyhamster73: Best user name I've seen here by a standard mile. Good effort :P
[Nexus 7 Android Development] Maneth:
Very good toolkit, it is very useful :)
[Nexus 7 Android Development] ghalibmeer:
ive unlocked using the kit but its not rooting the tab ... it completes all procedures but in the end its the same tried three four times ... plz help
[Nexus 7 Android Development] maigre:
I'm having a similar problem. I had rooted 4.1.1 with NRT with no problem whatsoever. Now, I've installed the 4.1.2 update via the zip file mentioned in this thread. I was able to do that by installing from zip in CWM recovery mode, but haven't been able to restore root since then via NRT. It goes through its process which hangs while waiting for the device to reboot. I manually complete the reboot by holding the power and volume buttons simultaneously. But, though the messages are what I'd expect to see, rooting is unsuccessful. I'm hoping that I won't have to go back to stock and start over again.

Now that I've had this thing rooted for a couple of months, I don't like not having that access and control anymore.
[Nexus 7 Android Development] ghalibmeer:
yes its stuck on "waiting for the device to reboot" and i have to do it manually ...
[Nexus 7 Android Development] maigre:
I've got a good backup, so I decided to flash to stock (I chose 4.1.2) and start over again...

... and it's hanging on the reboot during this phase, too. The console shows a message from NRT that says to be patient with this, that it could be 5-10 minutes, but it's been about 15 already and nothing's happening. I'm going to let it sit for a few hours, but I'm definitely concerned.

I noticed that during the flash to stock process that there were a few errors related to missing files (boot.sig, recovery.sig and system.sig), but at the end, there were no messages that suggest anything other than success.

I just used the buttons to let it boot and nothing had happened. The flash to stock had failed.

So now, I'm flashing back to 4.1.1 and it appears to have worked. I'm back to stock 4.1.1. So, at least for some of us, there appears to be problems with the 03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip updated from 4.1.1 to 4.1.2 and the zip that NRT downloads for 4.1.2, which may be the same one.
[Nexus 7 Android Development] maigre:
Continuing on, I did the OTA update from 4.1.1 to 4.1.2 on the restored to stock device. No problem there.

But then, unlocked, trying to root caused the same problems I was having earlier. The process gets stuck at the reboot. Then, when I manually boot, NRT continues, supposedly pushing the rooting files to the device, but nothing seems to happen. Rebooting after that gets stuck again. When I manually continue, I boot into an unlocked, but not rooted Nexus 7.

Any ideas as to what might be stopping this from working?
[Nexus 7 Android Development] rampino:
remount failed here when pushing super su.. so no root at all :/
[Nexus 7 Android Development] pughie:
I had a similar issue after installing 4.1.2 I was unlocked but no root... I then downgraded my boot loader to the version from 4.1.1 and had no issue at all and am both unlocked and rooted on 4.1.2 :confused:
[Nexus 7 Android Development] maigre:
How did you do that, by indicating that your device has 4.1.1 in the NRT interface?

I went back to 4.1.1 and rerooted there and am restoring my backup now.
[Nexus 7 Android Development] rodem77:
I had a similar problem on nexus s, you can use the toolkit to unlock 4.1.2 then with the toolkit start temporary cwm (or Twrp) and manually download and flash SuperSU. At this point you are unloked and rooted with 4.1.2.
[Nexus 7 Android Development] WugFresh:
This shouldn't be necessary at all. Can someone please elaborate on what's happening specifically when running the root script on 4.1.2. And also what happens when you use "Any Build" mode.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
To be clear. There should be no problems rooting the 4.1.2 build with the toolkit. Just make sure to select that build first. Use the "Change..." button and select the 4.1.2 build.

{{ WugFresh }}
[Nexus 7 Android Development] dirtyhamster73:
I used the toolkit this morning (1.5.4) for a friend's galaxy nexus (sideloaded 4.1.2) and my 2nd N7,(4.1.2) both went flawlessly. Thanks for the updated version!

Also, I forgot to change the version on the toolkit to 4.1.2 for my 1st N7, the toolkit was on 4.1.1, and all went fine....almost had a heart attack when in the middle of it rooting I happen to look and see I didn't change it from 4.1.1 to 4.1.2....but it went perfect :)