yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] dirtyhamster73:
I don't have the ota root keeper app, so I can cross that off the list. This is driving me nuts! I just keep doing the steps over and over again with the same results, can't get in to SU and no root access.
[Nexus 7 Android Development] fallenmk4:
I've had this issue since before the update so I just gave up, I was successful in unlocking my nexus but it will not root I just keep getting that error and I've tried well over 20 times including other toolkits as well. I figure I'm just not allowed to root this :/ and I'm 4.1.2.
[Nexus 7 Android Development] dirtyhamster73:
I can't tell you how many times I've used this root kit, successfully...a million times, never had an issue.

Wug.....is it possible to uninstall this.update and go back to 1.5.4?

---------- Post added at 01:08 PM ---------- Previous post was at 12:48 PM ----------

FINALLY!!!! Not sure what exactly happened that made it work this time but this is what I did:

I wiped the N7, ( I had to go in to the play store and uninstall SU, it wasn't getting deleted when I wiped and for some reason I think the problem I was having was related to SU)then I unrooted, locked it back up, wiped again, unlocked, wiped again, rooted, wiped again. Boom, everything is fine and running as it should. Whew... that was scary....lol

By the way, this was happening on my 16gb N7, the 32Gb had no issues. Don't know what or why there would be a difference between the two :/
[Nexus 7 Android Development] spthacker:
I couldn't get my new 32gb to root, same su prob I downloaded it off another thread and flashed it manually via trwp and all was fine

Bricked/Rasbean N7

---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------

Have to add my 16gb rooted just fine a couple of months ago and has now been successfully restored to standard via nrt for my other half to use :)

Bricked/Rasbean N7
[Nexus 7 Android Development] SteveC485:
I had the same issue initially, thought I was going to go nuts. I too fixed it by re-flashing stock, re-locking, and I used a different Toolkit download from another computer with any android build checked, and it all worked like it was supposed to . I think sometimes the gremlins get into things we would rather not have them in. I have not yet tried the new version on either computer. Be sure you do this in airplane mode too, you don't need interruptions in the process with an errant email or some notification showing up on the doorstep.
[Nexus 7 Android Development] WugFresh:
Then re-flash stock and try rooting again. Also try an alternate USB port. I can assure you, this program will work to root your device.

{{ WugFresh }}
[Nexus 7 Android Development] crunchienuts:
Just successfully unlocked and rooted my 16GB N7 with the toolkit. Everything went without a hitch and I couldn't have asked for a more straightforward and intuitive toolkit. Keep up the great work Wug!
[Nexus 7 Android Development] jbird92113:
Toolkit question

I just wanted to mention that this tool was super easy and simple to use, so thanks wugfresh. One question about the toolkit. I recently unlocked and rooted my nexus 7 device however i didn't check the permenant CWM, does that mean I can't flash any Roms? If yes and I need to run the permanent CWM can I just check the box that says permanent and re-root or is there a different method I need t follow.

Thanks,

Jbird
[Nexus 7 Android Development] WugFresh:
You can still flash ROM's with the toolkit using the "Flash zips" button, which utilizes temporary TWRP to flash them. You just can't flash zips without a computer. If you wan't permanent alternate recovery (so you can use recovery without a computer.. and just boot into it on your device: bootloader mode > recovery) then yes, you can just run the root script again with that box checked. The toolkit is defaulted to flash TWRP not CWM. If you want CWM then go to the toolkits option menu and change it CWM.

You can also flash alternate recovery using advanced utilities "flash to recovery" button (in the flash to partition section), and flash any recovery image you want. The choice is yours. Either method will work.

{{ WugFresh }}
[Nexus 7 Android Development] Groof:
I've been racking up 10 posts just so I can post in this thread, heh.

After having my Nexus 7 for a week or so, I finally got around to wanting to root it. Mostly for Titanium Backup, because it's made my phone life a lot easier and I figured the same could apply to a tablet (this is my first one). So I decided to check this tool out and for the most part it was working fine. Backing up and unlocking it was a breeze and went without a hiccup. However, when trying to root it I kept getting stuck at the "Please wait for your device to reboot..." screen. Seeing so many people having this issue, I read and searched the thread over and over to find solutions and tried all I could find, but none seemed to do the trick.

I gave up for the rest of the day and tried again the next morning, same issues. So I figured, let's try to reinstall the program and I redownloaded the installer (amazingly frustrating with my slow internet, took me 4 hours to get it down) and did the install. Pressed the root button and a couple minutes later a smile was put on my face. SuperSU existed and binaries updated. Finally I can put my mind at ease with some backups, hehe.

This was all on 1.5.4 by the way, so I'm sure most of these issues are solved by now, but I felt like sharing anyhow.

Many many thanks to WugFresh for all the hard work and putting together such an amazing tool and making it so easy for everyone! :)
[Nexus 7 Android Development] TheByteSmasher:
That's happened to me before. Ended up taking unit back to stock then rooting again. Also try deleting the ready to flash folder on "SD card" then rerooting
[Nexus 7 Android Development] rodem77:
Hi, I've a nexus s i9023, in the past i wrote you that I had a problem to root my phone (with version 1.5.3) and later i've readed other post about nexus s with same problem in rooting, maybe that there is some problem with rooting procedure? I used your tool to install driver and to unlock without problem, I'm also using your tool to backup and to boot with temporary TWRP when i need always without problem, my only problem was with root like this user. If i can help with more information please let me know.

Thankyou

---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------

I will try this. Thankyou.
[Nexus 7 Android Development] WugFresh:
Lots of users have rooted successfully with this toolkit, so I don't think its the root procedure... That said, you can try using "Any Build" mode in the device list - which doesn't rely on full automation and basically instructs the end user to flash certain zips in recovery (this should work 100% of the time, regardless of what android build you are on). Also, please use version 1.5.5 of my toolkit (the latest version). There was in fact a problem in v1.5.4 that prevented some users from using the toolkit successfully on certain builds due to the outdated TWRP files utilized in that legacy release.

If flashing stock and trying again with my latest toolkit doesn't work. Please notify me again via pm or something, and I will see if I can help you troubleshoot the solution.

Also I recommend trying alternate USB ports if you are having inconsistent results - in particular it may be best to use USB 2.0 vs 3.0 ports, and preferably back ports on desktops (I don't have hard evidence to back up this assertion - just a lot of user feedback).

{{ WugFresh }}
[Nexus 7 Android Development] scotthallisgod:
nexus 7 32gb updated ota to 4.1.2 and then unlocked/rooted fairly easily.

the only snag I hit was when removing the drivers in order to reinstall, for some reason the step where you reinstall the drivers I kept getting a 103 error saying no android device present. I reinstalled the drivers I had on there and the checking mechanism said they were fine anyway...so cheers! it worked fine after that.
[Nexus 7 Android Development] iAndroidOS:
Hi, i can't root my nexus 7, it boots into bootloader (it's unlocked fyi) and the toolkit just shows waiting for your device to finish booting up and my nexus just sits on the bootloader. When i was done with waiting, i just pressed the power button, and it booted up normally, but there is no supersu, but the toolkit said that it's rooted. Any suggestions ?
[Nexus 7 Android Development] bbgt2:
Change USB ports, I had to after unlocking then rooting. Until ur pc or laptop actually sees the N7 as connected nothing will happen.
[Nexus 7 Android Development] MrRedPants:
Same here - Having same problem on 8GB Nexus 7

Solved by changing USB ports (and seeing that TWRP flash up temporarily makes me want that on my 7!)
[Nexus 7 Android Development] scotthallisgod:
Can anyone help with the best way to go about updating with this zip file for the nexus 7 camera?

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

I unlocked/rooted with wugfresh toolkit. Trying to understand how to do this through the GUI while still keeping it as simple as possible.

Am I right in saying what we need to do is reboot in fastboot mode, and flash the .zip file? Is that all the GUI is doing in the background?

Through the GUI would I go to Launch--> Flash zip-->THEME/MOD? ROM is just a custom OS which is not what we are doing here, simply modifying a text document with the .zip file

TIA...
[Nexus 7 Android Development] jbird92113:
Thank you so much for replying. I was thinking about using this rom (http://xdaforums.com/showthread.php?t=1788518). Do I just download the zip file for ROM sgt7-10-20121104-EXPERIMENTAL-grouper-cdesai.zip and the GApps A and include them into the flash zips section? SOrry for the newbie questions just never done it before and concerned that i will brick my nexus...
[Nexus 7 Android Development] bbgt2:
Why not just flash thru recovery?
[Nexus 7 Android Development] WugFresh:
Flashable zip files are meant to flashed in recovery. For ROMs you typically wipe data, cache, and dalvik first before flashing - whereas for themes and mods you typically wipe cache (and sometimes dalvik too - for safe measure) first.

You just put the zip on your sdcard somewhere, boot into recovery and flash/install the zip.

So yes: bbgt2 is correct.

The toolkit however is designed to streamline this process even further. It essentially accomplishes the procedures however through an automate process. If you use the "Flash zips" with "file is on this computer" it will bring up an interface for flashing zips, and also allow you to select other options to perform with the process in one go. There are also default configurations - so for you, flashing a camera zip is considered a MOD - if you use the default options it would have you backup your system in case you want to revert back to a point before the mod, and it will also performs the wipes I suggested. Basically it automates all those tasks that you would do in recovery but all in one go. This was made possible by the awesome people who created TWRP, in particular Open Recovery Script, which is a specialized syntax for automating tasks in TWRP. Basically the way the toolkit flashes these zips and performs all those tasks.. is that it converts all those checkboxes and options you set on the Flash manager interface into a UNIX open recovery script that is then pushed the devices cache/recovery directory - which TWRP reads in when its booted (on next boot into TWRP).

So to reiterate how you would do it in the toolkit.

Flash zips button with "File is on computer"

Select any options you want

and let the toolkit take care of the rest.

Or, just do it in recovery. The choice is yours. If you don't have TWRP/CWM flashed.. you can use the toolkit to boot it temporarily, or if you do have it, you can use the reboot recovery button in the Quick tools section for a quick way to get into recovery.

Hope that helps. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Yes, and consider using the recommend settings for ROM. That said.... I would recommend flashing just the ROM, letting your device boot up once.. then doing the Gapps. Doing both in one go (although the toolkit makes this possible) is not recommended and can cause problems. No worries man.. everyone is a newbie at some point. I learn something new about android and windows everyday it seems. Gotta start somewhere. :)

edit:

Also to be clear, hard bricking your Nexus is HIGHLY unlikely.. unless you physically smash it with a brick. The worst case scenario is usually a softbrick or a bootloop, in which case the "Flash Stock + Unroot" button with that option selected will help you restore your device back to square one... so no worries if that happens.

{{ WugFresh }}
[Nexus 7 Android Development] mrmond:
Forgive this extremely noobish question as I only got my 32gb Nexus 7 today and my brain isn't working to great owing to it being 3:30 am.

If I install this program and click Root, is that all I need to have a fully rooted device for apps that need super user ? I don't mind if it wipes it first as long as it ends up like when I first turned it on and rooted.
[Nexus 7 Android Development] WugFresh:
You need to unlock first.

Unlock then root. Generic instructions can be found on my website.

{{ WugFresh }}
[Nexus 7 Android Development] jbird92113:
Thanks again WugFresh, you have calmed some of my nerves regarding the bricking of my device. If you don't mind I may send you some screenshots of your app prior installing the ROM to ensure I prepped it correctly :)
[Nexus 7 Android Development] WugFresh:
An attempt to dispell fears of "bricking" a Nexus device

You are free to post whatever you want. But to be clear, the toolkit either works or does nothing - there is no in between. Maybe this is a weird thing to say as a developer - but I try my hardest to follow the same philosophy that I adhere to in my studies at school; that being - the Hippocratic Oath:

... I digress /tangent:

The toolkit checks connectivity before doing any procedure, so it's not like it can do something half way - or the end user can do something "wrong". Either it will perform the task you are trying to perform, or if you haven't configured your drivers yet properly or your usb connection is unstable... it will just give you a message and/or ultimately do nothing at all.

The main way people screw up a device are by interrupting a flashing process.. like:

Unplugging the device half way through flashing stock.

The battery dying while flashing a ROM (shouldn't be a problem on nexus devices with the usb plugged into a power usb-port/charger)

An end-user being really impatient the first time they experience what appears to be a bootloop (boot animation repeating continuously to seemingly no-end), and battery pulls pre-emptively (rather than waiting at least 5-10 minutes to see if it just boots up on its own)

Or, other common occurrences like:

An end-user trying to do too many things at once - like flashing a bunch of zips in recovery all in one go.

An end-user/aspiring dev/modder trying to set permissions (or even worse set them recursively) on various file systems without actually knowing what they are doing (I am guilty of this myself.. it's how I had my first soft brick back when I had a Droid-X).

Or modifying core system files without knowing what you are doing or being prepared to-face the consequences/repercussions.

That said.. in all of those incidences - as long as the end user can get back into bootloader mode, re-flashing stock provides a simple all-inclusive fix to those soft-bricking problems. Furthermore on Samsung devices end-users are even given "a reserve parachute" - that being, ODIN - which allows one to restore their device with an ODIN tar package regardless of whether or not they can get into bootloader mode (just download/odin mode).

So again... to be clear. If you really want to hard brick a Nexus - chances are you will need to physically smash it with a brick. That's not to say that its entirely impossible to do from a software end (I suppose anything is possible) - but most of the time its a hardware issue if its a real hard brick.

Hope that helps put some fears to rest. Cheers :)

{{ WugFresh }}
[Nexus 7 Android Development] Finguz:
Many thanks WugFresh, it does exactly what it says on the tin ( At least I assume it would/does, if it came in a tin ... )!

I particularly like the fact that you don't dangle a carrot and then ask for donations to get the latest version.

Have several pints on me :good: :cool:
[Nexus 7 Android Development] jbird92113:
Understood and thanks for the response
[Nexus 7 Android Development] scotthallisgod:
Many thanks for the response. I mainly do not want to wipe and start all over (i just wiped/unlocked/rooted 2 days ago) just to do save some time on some text editing in an xml file. The MOD seems pretty easy to do manually. This post was extremely helpful in knowing what is going on behind the scenes. Obviously the N7 doesn't have an SD card so I have the zip on the hard disk in the download folder, curious if that would work or if it wouldn't because installing the zip would cause a data wipe?

Thanks so much for the informative post.
[Nexus 7 Android Development] luckylui:
I wanna thank you sir for the great unlocking process! Easy as pie. Thanks a million!!
[Nexus 7 Android Development] Kid_droid:
I Just got my nexus 7 last night running 4.1.2...I wanted to use USB and a few rooted apps like titanium, beats and phone app but stay on stock.

My question is if I root now would i be able to receive over the air updates when rooted since i know the 4.2 update is due this month at some point.

Would accepting over the air updates while rooted brick the nexus 7 or just lose root and root again ?

Thanks in advance.
[Nexus 7 Android Development] blue_bullet:
New Version 1.5.5 got me root

I got nailed by the 4.1.2 upgrade as I did not have voodoo OTA Rootkeeper installed. I was rooted on 4.1.1 but 4.1.2 put me back to unrooted. Using version 1.5.4 I could not root my Nexus 7 16GB. Was not asked about binaries in SuperSU and busybox could not install b/c I was not rooted. Today I saw Version 1.5.5 was out there. I downloaded, unzipped and installed the new version and selected the ROOT option. I was already unlocked. It rooted the device. SuperSU did not ask about binaries, but busybox installed successfully. I then uninstalled SuperSU and reinstalled it. Upon reinstallation I was asked to update the binaries. In short I am rooted again and can use StickMount (requires root) to read and write files to a usb thumb drive with my OTG cable. I thought it was r/o but I can modify existing files on the thumb drive. Thanks WugFresh for all your work.
[Nexus 7 Android Development] WugFresh:
Glad it worked for you. I actually modified that text about the binaries in v1.5.5, stating that "it may ask you to update the binaries" - rather than "it will ask you to...". The reason it didn't ask you to update the binaries is because they were already the latest available binaries (since the new toolkit release now flashes 0.97 SuperSU and binaries - which at the time of the release were the latest available.) My guess is that you just assumed it said the exact same thing as last time because you were already use to it. Either-way, there is no harm in re-installing SuperSU once you are already rooted.. makes no difference. But yeah, I think I forgot to include that minor change in the changelog. I made that change when the same thing happened to me and then quickly realized I was being silly for including that text in first place - because things only ask you to update when an update is actually available/necessary (doh..). :)

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
As far as the process is concerned; the sdcard is equivalent to internal storage. Same difference. Both are storage partitions, the only difference is that sdcard cards are considered "external" storage. Consider a computer.. you can install a program that resides on the main hard drive, but you can just as easily install it from a flash drive.. make sense?

I think the path to your download folder (correct me if I am wrong) is still /sdcard/download, regardless of the fact that the N7 doesn't have an sdcard slot.

Regarding your last statement/question; "...because installing the zip would cause a data wipe?" - I am not sure where you are getting this from. Installing a zip file just does whatever that zip is intended to do... it sounds like in your case it is just something that replaces an XML file... so I am not sure where you are getting this idea that it's going to wipe? Typically zips don't wipe anything, they may delete some select files... like for-instance a zip for Deodexing a ROM would delete all the ODEX files... but they don't wipe stuff. That would be like installing Firefox on your computer and it wiping your hard drive (won't happen). It's up to the end user to wipe partitions (user option).. you can do it through the toolkit, or in recovery by selecting the "Wipe" button and then specifying what you want to wipe.

Hope that clarifies things...

{{ WugFresh }}
[Nexus 7 Android Development] kona786:
I just used this toolkit to unlock and root my Galaxy Nexus - it said it would wipe my device...BUT IT DIDN'T! All settings and apps remained.

Anyone else get this - it's rooted so I'm happy.