yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] limpet:
I suspect you will find that those files are still on the Nexus after removing the USB stick. I think sda1 is in internal memory.

USB OTG Helper seems to do the same thing. It creates a directory in internal memory instead of mounting an external drive.
[Nexus 7 Android Development] LINKSLOVESANDROID:
can i root 4.2 with this? and how would i flash a compatible recovery? i checked the files and it doesnt seem to flash an image. it flashes a zip. anny ideas? thanks in advance
[Nexus 7 Android Development] starfighter1948:
You're right. Stickmount indicates the card is mounted to sdcard/usbstorage/sda1 and I was fooled by being able to copy files to what I presumed was the actual sdcard but is just internal storage. I checked the memory stick on my laptop and the files and directory I thought I'd created on the Nexus 7 where not present, and I cannot see directories and files copied to the memory stick using my laptop on the Nexus 7. Stickmount thinks it has mounted the sdcard, as it tells you where it is, perhaps the problem is associated with busybox, ie the mount command is dummied out and misinforming stickmount that the USB stick is actually mounted.

Apologies guys for getting your hopes up. My only excuse is that once you're start drawing your pension your old grey cells start during off fast!

Update: dmesg shows that the memory stick is recognised and is not write protected, and suggests it should be sda1 but as far as I can see there is no mount point. Stickmount seems to recognise the memory stick has been inserted but presumably its mount command is referencing a /dev/block that is no longer present or fails to mount. Surprisingly stickmount is not catching the error returned when it issues the mount command otherwise it would not indicate success.

starfighter1948
[Nexus 7 Android Development] leebo:
I am not home right now, so I can't check, but I'm certain the exe I ended up clicking on my pc was only 2.3 megs. I suppose that's not the full tool kit, but it's what I've used twice (three Times now) to root my Nexus 7.

Also, I was asking where in Windows 7 does your download end up. But sometime after I posted I realized it depends on which browser you use.

I was not able to find the download in time to use it, but I will look again when I return home.

Anyway, I accepted the update to JB 4.2 and used "any build" to re root.

Thanks for your patience. It must get frustrating answering the same questions.
[Nexus 7 Android Development] nbakken81:
+1
[Nexus 7 Android Development] WugFresh:
Just remember, every time an FAQ gets asked again a baby unicorn dies: :p

http://www.wugfresh.com/nrt/faqs/does-v1-5-5-toolkit-work-on-rooting-android-4-2-builds-yet/

Regarding flashing a custom recovery, just check the button under the root button. It will flash TWRP by default, but you can change it to CWM or any newly released recovery you want in the toolkits option menu.

{{ WugFresh }}
[Nexus 7 Android Development] Mallikanth:
+1

And also perhaps search within the thread.

You must have the patience of a saint. :angel:

(Ok, That's an Angel but there is no saint smiley ok? lol)

Keep up the excellent work, Wug.
[Nexus 7 Android Development] rushter:
That part of your toolkit just doesn't seem to work for me anymore. Everytime I try to enter recovery I get the gutted Android with the red belly. Lol.

Just noticed tonight that after my update to 4.2 on my Nexus 7 the other day (I did have to take an xml file I had modified back to the original version to upgrade.) All appeared to go well finally but I had a few issues getting there.

First, since I had TWRP on there I had to take it back to stock recovery. CHECK

Second, as I said I had to change an xml file back to the original. I saved the original so CHECK

Thirdly, After downloading the update, as the OTA came up but did not download (I don't know why that failed). So I downloaded the update from google. Then the update finally took.

So here's what's going on now.

I just noticed today that my charger is no longer charging the Nexus 7 in two to three hours or less. It is now taking over an hour to barely go 5-7% up. Other threads say to pull the battery and plug right back in - not too easy to do with a closed Nexus 7.

Everything seems a bit unresponsive. Syncs with gmail widget is sooo slow. Directories under /sdcard are all gone and now only three directories remain /0 /obb and one other I couldn't remember the name of.

Any ways - to my point. I forgot (I know, kick me) to run a backup before updating. I wasn't too worried because of your toolkit. Now here's the question(s) - I want to take this thing back to being unrooted and back to a previous version. The let the OTA go through and bring me up to date completely, then re-root. Is this plausible/doable? And quickly? I know you have the Unroot and return to stock thing there but will that delete everything/factory reset the device. I am ok with wiping it clean and starting over if needed. I have Ti Backup etc. So unroot and return to stock button. Will that take it back to any previous version of my choosing? I am worried that the directory restructuring that Google did with the 4.2 update will screw this up a bit.
[Nexus 7 Android Development] N@th_OC:
Hi man,

Just flash the stock 4.2 OTA that you can find here: https://developers.google.com/android/nexus/images

Then donwload latest SuperSu and latest TWRP and use fastboot to root it again.
[Nexus 7 Android Development] rushter:
Being the idiot that I am I would love to see how to do what you just told me to using Wug's toolkit. Is that possible?

I know he has a directory with the images somewhere. Just download what you linked to and put in his directory?

Told you - i b idiot. lol
[Nexus 7 Android Development] digixmax:
Can "Flash Stock + Unroot" be used to go back to 4.1.2 from 4.2 (rooted)?
[Nexus 7 Android Development] Mallikanth:
Yes.

---------- Post added at 04:10 PM ---------- Previous post was at 04:09 PM ----------

Yes.

Browse to the image.
[Nexus 7 Android Development] SteveC485:
I guess this doesn't relate specifically to Wugs' Toolkit. But since I am having a couple of issues with my laptop I use for rooting (I have little confidence it won't die in the middle of something and have not yet assembled the $$$ to get the new laptop I want), I decided to use the rom in this link.

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

It is stock rooted 4.2. I did a complete, full wipe, clean install from twrp. I was on sgt 7 rom with franco kernel. I now have a fully functional rooted 4.2 system. This rom works slick as anything. I have very few of the alleged 4.2 issues. So, at least this is a way to go 4.2 without any re-root issues. Yes it's a bit of a pain to do a full wipe, but if you backup everything on the PC, or with the sd card backup in the tool kit, (be aware this can take some time depending on how much stuff you have) issues can be eased up s bunch. Just be aware 4,2 will land your stuff in a new storage 0 or just a 0 folder. You will have to manually move the stuff from 0 to trwp>backup for recovery to be able to see it, or for you to have it wherever you need whatever there is in 0 you need.

I did use Wugs' tool kit and aside from a couple of self inflicted issues, aside from the laptop issues, it worked and I'm sure to download the new 1.6 when it comes out. Hopefully I won't have to use it until I get a new machine.
[Nexus 7 Android Development] Rrrracer:
Hey Wug, I just wanted to take a quick minute and thank you for the toolkit. Just got my 7 and had it rooted within a few minutes, it worked perfectly with no hiccups and now the device is really rocking-- so THANK YOU!! Have a great one!
[Nexus 7 Android Development] ezas:
I haven't been in this thread for a long time. But awhile back the toolkit got me out of a problem.

And catching up on the last 10 pages or so and seeing how helpful and patient WUG is I took the time to hit his web site and send a small donation.

I'm looking forward to his future work.

Sent from my Nexus 7

4.2 Stock Rooted - leanKernel .06
[Nexus 7 Android Development] synnyster:
The download link doesn't seem to work. None of the links for his faq work either. Is it just me?
[Nexus 7 Android Development] limpet:
I downloaded a copy and read the faq earlier today,

Now at: http://www.wugfresh.com/dev/nexus-root-toolkit/

I get this:

This website is offline

No cached version is available

What's wrong?

The most likely causes:

The server is down for maintenance

There may be a network problem

The site may be experiencing excessive load

---
[Nexus 7 Android Development] WugFresh:
[Previous message about my host redacted] My website was down, I fixed it.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Hey everyone. I am really sorry about my website, but I will fix it asap. I have one more test tomorrow morning in biocompatibility and then I am on break basically. Then I will finish v1.6 (which is basically almost done). My site going down now is like the worst time, because I can't do anything about it this moment, I have to study... but whatever.

[Comments about host redacted, looks like it was my fault]

You can download v1.5.5 still from here: http://www.softpedia.com/get/Mobile-Phone-Tools/Others/Galaxy-Nexus-Root-Toolkit.shtml

{{ WugFresh }}
[Nexus 7 Android Development] evaradar:
Good luck Wug. Can't wait for v1.6. Is there a preview of the change log?
[Nexus 7 Android Development] n7of9:
i thought i'd put this here just in case it helps anyone out:

version 1.5.5 works on N4 so far as deleting and updating your drivers...i used the PDANet drivers on Windows 8 (even though it said not recommended) because i was having issues with the Google drivers, and then i ran the Full Driver Test and it all worked
[Nexus 7 Android Development] nalab1:
Hi!

Im new to the Nexus7 (although not flashing custom roms etc!) and wondered if the Toolkit Version 1.5.5 will unlock/root version 4.2?

Sorry if this is a bit Noob!

Regards,

Alan
[Nexus 7 Android Development] Mallikanth:
Yes it will.

---------- Post added at 11:38 AM ---------- Previous post was at 11:37 AM ----------

Indeed it does work as previously described in this thread. :)
[Nexus 7 Android Development] nalab1:
Hi Mallikanth,

Thank-you for the reply! I asked as I am hoping to get a 32gb N7 for Christmas. I presume that it will come with 4.2 or or perhaps they are still shipping with 4.1.2. If it does arrive with 4.1.2 would it be better to do the OTA upgrade to 4.2 and then unlock/root 4.2?

Regards,

Alan
[Nexus 7 Android Development] Mallikanth:
Personally I would do the later.
[Nexus 7 Android Development] Vondis:
Pardon my noobness but what exactly needs to be done in order to get it to stop wanting to do a OTA update when there is no update to be had? I searched this thread and the discussion about the OTA issue wasn't very elaborate
[Nexus 7 Android Development] Mogul345:
WugFresh,

Thanks for the tool! I've used it over the past couple days to Root/CWM/Flash back to stock for OTA's my Nexus 7, and the tool works pretty good.

However, you got a couple bugs you might want to fix:

It displays odd behavior if you install into a path which has spaces in it (ex. D:\Nexus 7\Wugs Root Toolkit\). When restoring to stock, it'll act as if it's d/l'ing the stock image, but won't save it and then the batch script will error off with no indication of failure. Looks like you need to surround your paths in quotes in your app.

In general, needs more state checking/error timeouts. It's possible to get it into a state where it's waiting for the device to enter a certain state (such as bootloader) but if it never gets there, the app will just hang, and you have to choose "End Task" in Task Manager to get out of the state.

You can launch multiple instances of the app, and then things just don't seem to work at all. I got into this state accidentally b/c I had a ton of windows open and had an instance open but buried beneath an explorer window. Might want to add a check on app start for an already running process with the same name.

Other than that, nice work! It's really helped me get up to speed with working with Nexus devices!
[Nexus 7 Android Development] ferris2375:
Sorry if it's been asked, but my Nexus 7 is a different version from those that I can select with this tool. Should I not use it until it's updated?

My N7 is JRO03D
[Nexus 7 Android Development] wyattyoss:
Would also like to know. I've never accepted a system update before, but as I was searching the forum, I subconsciously clicked accept.
[Nexus 7 Android Development] CooLoserTech:
this made things a WHOLE LOT easier for a noob like me
[Nexus 7 Android Development] FiveOhFour:
I unlocked and rooted my nexus 7 just fine with that version, although i think the version before that is the earliest one to use and shouldnt be used with the initial shipping version if i recall right.
[Nexus 7 Android Development] kampf:
I unlocked and rooted my GSM yakju device and updated it to 4.1 using NRT 1.4. I updated to 1.5, then Android 4.1.1 with the update file from Google. I lost root and now I'm trying to use NRT 1.5.2, but I'm encountering issues with the ADB status.

I'm using Window s7 64-bit, and the previously installed software worked great once I went through all of the driver installation steps. There seem to be 64-bit issues, but downloading and running the 64-bit PDANet installer only gets me more confused.

I've done so, after removing the Samsung and Galaxy Nexus devices using USBDview, but the issues continue even if PDANet is working.

Any suggestions? Wait until 1.5.3?
[Nexus 7 Android Development] Roachie:
Kind of newb with this and kind of cautious but when starting this it tells me to give the build number, mine is not in the list. its JRO03D the 1 close is the C version but not sure if i can use this ? (dont wanna break my nexus on the first day :P )
[Nexus 7 Android Development] htowngator:
Are we able to still get root if the device updated to 4.1.1 out of the box?
[Nexus 7 Android Development] FiveOhFour:
I would give it a shot again, start clean. After you installed the 64bit drivers from pdanet and you were following the step by step guide, you didnt allow it to re-install the other drivers again by clicking the auto install by any chance did you?

---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------

Yes just leave it selected to the JRO03C, the rev.D is just the updated 4.1.1 version, the second update. It works just fine, it was a very minor update. I updated directly from 4.1.1 as well with the JRO03D build.
[Nexus 7 Android Development] kampf:
I may have let it reinstall.

I'm in an environment where I have a bunch of workstations that I can image and can use "frozen" software to restore a workstation to its unaltered state on reboot.

On an instance of Windows 7 32-bit I am still having issues with NRT and the ADB Devices screen hanging after installing it, running the automatic driver installation, and connecting the device. It finds the USB Composite, and the first Galaxy Nexus, but doesn't install the second Galaxy Nexus instance. (phone is set up as MTP with USB Debugging on).

I am going to try a few more things, including manually setting it up.
[Nexus 7 Android Development] htowngator:
I selected the 4.1.1 JRO06D before I saw your message but it all worked out anyway.

Unlocked, rooted, and good to go.
[Nexus 7 Android Development] ferris2375:
Yeah well I'm running v D and this tool won't root for me. It unlocked my bootloader but root, no luck.

It hangs on booting the image so I eventually have to manually restart, then it says pushing Superuser.apk but it never actually installs it, just busy box. Once it's finished, my phone isn't rooted. Annoying.
[Nexus 7 Android Development] Roachie:
Thanks for the quick answer :)

(edit, seems to work, canceled the ADB test and went on and everything seems ok :) ) now ready for teh root!

Edit 2 : Root worked! thanks allot!!!!!!! :)
[Nexus 7 Android Development] kampf:
I did successfully re-root using NRT 1.5.2, a Windows 7 32-bit machine, and the manual driver install method.

Hopefully Lightflow Lite will start working better now, and I've also flashed the new CWM and updated the SU binaries, so it's confirmed as root

Thanks for the support and I look forward to the updated versions, as I might be getting the SO a Nexus 7 for her upcoming birthday.
[Nexus 7 Android Development] wyattyoss:
I just got this. I tried to do it and everything worked fine.
[Nexus 7 Android Development] clockcycle:
crash...

Uh oh, first crash ever after unlocking bootloader and rooting (w/o CWM).. :crying:
[Nexus 7 Android Development] movieaddict:
DOES IT usually hang on Checking ADB status? its been doing it awhile???? how long should i let it do this??
[Nexus 7 Android Development] BennyJr:
Mine is stuck on 'checking adb status'
[Nexus 7 Android Development] jklitten:
Also seem to be stuck on "Checking ADB Status."

Edit: Trying manual method right now.
[Nexus 7 Android Development] nalab1:
Hi Mallikanth,

Kool... roll on Christmas!

Regards,

Alan
[Nexus 7 Android Development] Mallikanth:
Not a problem.

I too am getting my 32gb N7 for Xmas, but Santa must have come early and as I work from home I've been errrr 'testing' it already and re hiding it. ;)
[Nexus 7 Android Development] k5mitch:
Help

Stuck, I got the bootloader unlocked, Im stuck at the rooting part, Waiting for device to reboot. I have to manually reboot it and no busy box or super user.

Nexus 7 4.2
[Nexus 7 Android Development] WugFresh:
I am guessing you selected the wrong device. Use Any Build mode for NEXUS 7, not GALAXY NEXUS, or any of the other devices.

This is a common mistake it seems, which is why in v1.6 the device and build selection will be separated in two combo boxes.

{{ WugFresh }}
[Nexus 7 Android Development] k5mitch:
The zip files are there

buzybox.zip

superus.zip

/sdcard/!readt to flash/root_files
[Nexus 7 Android Development] WugFresh:
Flash the zips... "Any Build" mode instructs you to flash them, its not automated like it is when the build is officially supported.

{{ WugFresh }}
[Nexus 7 Android Development] k5mitch:
OK let me check.

---------- Post added at 05:44 AM ---------- Previous post was at 05:36 AM ----------

my bad Thanks!
[Nexus 7 Android Development] diba320:
Rooted my new N7 without problems with the tool.
[Nexus 7 Android Development] tamanaco:
When 1.6 is released is it going to include a SuperUser app that supports the multi-user function of 4.2 or is this something I need to install separately?
[Nexus 7 Android Development] Mallikanth:
I would imagine that it will come with the latest SuperSU app as the previous versions have, and if it didn't cover multi user support then the app will just be updated separately like any other app.

In short - nothing to worry about - just carry on as normal. :D
[Nexus 7 Android Development] WugFresh:
Some info on v1.6

Correct. Thanks to S0up at Goo.im I learned how to interface with their JSON API in a way I can use with the toolkit to automate a bunch of things I was hardcoding previously. Some code I wrote last night is making what I would like to do very promising.

If all goes well, I believe v1.6 will come with an online/offline toolkit mode. If the offline mode is selected, it will just use the latest toolkit files available in the local directories (so that will mean the latest SuperSU as of now), however if "online" mode is selected, then the toolkit will actually do a check to see if a later SuperSU is available, and if so, it will download it first. The same sort of method will be implemented for all the features, including checking to see if there are new android versions... So that means (no more waiting for me to push a toolkit update to see things like the latest builds supported; assuming no major changes need to be made).

In short, the toolkit will be able to automatically grab the latest files it needs, without me having to push a full update. With this new system, I can focus future development on adding and improving toolkit features, rather than playing catch up with all the latest builds etc.

All of this automation will be great for the future, but I have a long day ahead of me to get it all coded the way I want. That said, I am pretty confident I can pull it off based on what I tried last night. Stay tuned ^_^

{{ WugFresh }}
[Nexus 7 Android Development] Mallikanth:
Sounds awesome Wug!
[Nexus 7 Android Development] porkovich:
Hi all i just want to ask for some help. I read part of the thread but anyway i am new to Android. I have updated my tablet to 4.2 (OTA) but am very dissapointed with the result, tablet is not responcive enough and other crazy things.

I would like to downgrade to 4.1.2, was all fine with it. The tablet is stock (never rooted or something). My question: if i am right, to do it i NEED TO UNLOCK the device and use the FLASH STOCK + UNROOT ? RIght ?

Please someone to confirm it, or correct me if something is wrong .... thanks in advance !
[Nexus 7 Android Development] leebo:
OK, I maybe wasn't clear the first time. I'm back home and what I meant to ask was:

Where does your updater download the updated files to when downloading the update on a PC? I am not asking where it puts files on a Nexus device.

I launched your updater, it showed it was downloading the update Downloading: updater_NRT_v1.5.5exe.

Download complete!

Then it just sits there. It does not update NRT. So I have now downloaded the update three times, each one was over 300 megs, and the files are sitting somewhere taking up space on my HD. Where?
[Nexus 7 Android Development] Mallikanth:
Sorry, I'm not clear on what you're asking so I'll cover all eventualities...

Are you asking where is your download of the toolkit?

It's whenever your browser keeps it's downloaded files, assuming it didn't ask you at the time.

Your download folder in your user profile (If you're using Windows), perhaps?

Are you asking where it is when installed?

Once it's installed most of these large files are in Wugs Toolkit data folder. The toolkit does everything automatically - you'll rarely have reason to play with those files directly.

Are you asking what happened after an update of a previous version of the Toolkit?

Well, with this one I'm of little help I'm afraid as I've only done this once and to be honest I didn't really notice what happened. The update seemed pretty automatic to me with few prompts. If you are indeed updating an older version of the toolkit and it's not working for whatever reason, try uninstalling the old one and downloading the full package again and re-installing it?

Another option is NOT to run the manual updater manually and just let it look for an update when you launch the Toolkit.

---------- Post added at 06:57 PM ---------- Previous post was at 06:54 PM ----------

You're correct. However you must realise your device will be wiped.

Perhaps you have an app or widget not working well with 4.2 as it's been widely reported as as fast if not faster than 4.1.2
[Nexus 7 Android Development] porkovich:
So , i can ONLY unlock, and don't need to ROOT in order to use Flash Stock + Unroot command. ( sorry that i am sounding like an idiot, but the word unroot in the command is bothering me :D )
[Nexus 7 Android Development] tamanaco:
Thanks for clarifying and pardon my ignorance as I have not used your toolkit yet. I just got my N7, applied the 4.2 OTA and installed a few apps. After reading "some" of this thread I decided to wait for the next release of your toolkit before proceeding with the unlocking and rooting. Two more question, regarding the future toolkit automatically grabbing the latest files... would I be able to tell, via the toolkit UI, the version of the components before I push them to my device? Second... maybe I'm missing the obvious, but with other Android devices that I have unlocked... the unlocking process did not wipe my device. Is there something "special" about the N7 that requires the wiping of data during the unlocking process? Thanks again.