yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] leebo:
I'm guessing this has been asked and answered, but with 135 pages I'm not finding it. I wish it was made clear on page 1.

I have a N7, stock, rooted using NRT ver. 1.5.2. There is no "checking for update" in that version. I am downloading 1.5.4 now, and hoping it will overwrite the previous version as it does not show up in add/remove programs (Win7 64). I did find manual uninstall instructions in post #1335, but when I checked file associations inWin7, there is nothing listed for Wugg or Nexus. I have not unlocked it nor installed any custom recovery like cwm. I only rooted it so I can run apps that require root.

I am unsure if I can accept the update that keeps popping up on my N7. There are lots of posts recently that say no, you have to find and download a zip of the update because using the ota will lose root. However, the OP seems to imply that most people CAN install the ota update and that only some are having issues rooting after that.

So should I first try the ota and re-root using 1.5.4? And if it is recommended to find that zip instead, why is it not linked in the op?

Thanks.
[Nexus 7 Android Development] MarkRain:
Great tool, thank you very much!!

I have a Nexus S and i used NRT to flash the latest jelly bean release, 4.1.2... but now i have a question:

Should i change the "model type" in the program? If yes...how do i set it to JB 4.1.2? it won't show up in the list...
[Nexus 7 Android Development] WugFresh:
This is entirely my fault. Its hard coded in the toolkit but its not in the list. I must have been sleep deprived when I compiled the final 1.5.4 version and thought it was there but it wasn't (facepalm). You can use "Any Build" mode for now to root it. I have no class tomorrow so I will pump out another update with the latest fixes (v1.5.5) and leave integrating NexusQ support for v1.6.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
In the toolkit itself, go to the Options menu, there you will find options for file associations. If you checked in Windows and didn't find any, my guess is that there are no associations. They are disabled by default.

You can take the OTA, assuming your device is stock. Since you just have used root to run root apps, the OTA should take. Unless the user apps you used did things like overclock/undervolt your device. In that case you should just "Flash Stock + Unroot" and use the latest 4.1.2 factory image from google.

Yes, taking the OTA will make you loose root. Just re-root afterwards. Try the suggestion in the OP if it doesn't work first try.

I am assuming you are talking about a 4.1.2 flashable update.zip? You could do it that way if you wanted. There is more than one way to update. I haven't mentioned using a 4.1.2 flashable update.zip in this thread yet, but yeah you can flash it with custom recovery if you wanted - or use the toolkits "flash zips" button in advanced utilities.

Why is it in not in the OP? This is a program for performing tasks with various files, not also providing the various files you may want to flash for every single Nexus device. That would make this program way to big if I started doing that - and would make it nearly impossible for me to keep updated. It's very easy to search for files to flash - the toolkit will take care of flashing them; and its up to the end user to decide what they want to flash - not me to decide. The toolkit will only include the files it needs to perform its core functions, like the files for rooting, alternate recoveries, stock recoveries, modified boot.img's etc.

Hope that helps clarify your questions. Cheers. :)

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Did you get this resolved? I would recommend trying again.. or unpacking the factory image package (unzipping it) and flashing just the system.img with the toolkit's advanced utilities 'flash to system' button.

{{ WugFresh }}
[Nexus 7 Android Development] truthkillszz:
I am going to try manually flashing system tonight if i have time after doing my CIS homework
[Nexus 7 Android Development] TheByteSmasher:
Bricked my N7! Not sure how I did it.. but stuck on Google screen.. no ability to get to bootloader... :( probably have to get another one.... Tried installing Paranoid...

never deleted bootloader or anything! Any Ideas??

BTW @WUG would you update the SuperSu to 0.9.6 please?
[Nexus 7 Android Development] WugFresh:
Yes, I will update it. Thanks for the heads up. Hit me up on gchat about your N7, maybe we can bring it back from the dead.

{{ WugFresh }}
[Nexus 7 Android Development] TheByteSmasher:
Maybe

It's worth a shot... but I think it's hard bricked. :crying:
[Nexus 7 Android Development] MarkRain:
Thank you for the explanation! no problem, i'll wait for the new update, thank you again!
[Nexus 7 Android Development] TheByteSmasher:
Anyone know if a nandroid from a 16 gb N7 will work on a 32gb N7?
[Nexus 7 Android Development] leebo:
Of course it did not work. When it comes to technology, it seems like the failure rate is over 50% on the first try, no matter what device.

After the so called "root" process was finished, your application popped up a message on the computer:

"Open Super SU and it will prompt you to update the binaries"

Nope. Didn't happen. Tried re-booting the device, still nada. So I tried your second tip:

"The problem is related to the new bootloader. I will make an update soon that flashes the older bootloader during the root process. For whatever reason the new bootloader does not play nicely with the fastboot boot cmd. I plan on notifying google directly, but for now the solution is as follows:

1. Download the older Nexus 7 bootloader: http://wug.rootxs.com/misc/bootloader-grouper-3.34.img

2. Use the advanced utilities flash to bootloader button and flash that older bootloader

3. Try rooting again

4. Win!"

Still no updating of any binaries in Super SU, but Busybox did re-install and Titainium BU works, so thank you.

Well, I didn't mean for you to include files in your program, just maybe a running faq. All these replies of people trying to troubleshoot on their own fogs things up. There are several posts claiming using the ota can cause root to fail, when in fact apparently you found the cause to be in the bootloader version.

Anyway, you do have that info in the OP so thanks again for taking the time to answer me.

But again, just fyi, my Nexus 7 is stock, no mods other than it was previously rooted (using an older version of NRT). I guess it was unlocked after all, but that's it. And I still had to download and flash the older bootloader.:laugh:
[Nexus 7 Android Development] WugFresh:
Okay. Yeah, you're entirely right about me creating a running FAQ. I need to set aside some time to do that, I just always prioritize coding over supplemental material.. But an FAQ would help everyone. Regardless, glad you got it figured out. Cheers

{{ WugFresh }}
[Nexus 7 Android Development] landstander:
@WugFresh

I just saw that TWRP 2.3.1.1 for the Nexus 7 has been released, and fixes an issue with booting into recovery under the 3.41 bootloader. Sounds like it might relate to some of the trouble which has been reported in this thread.
[Nexus 7 Android Development] WugFresh:
Sweet. Thanks for the information.

{{ WugFresh }}
[Nexus 7 Android Development] TheByteSmasher:
Ahhhhhhhhhhhh

All the Promises!!! Going into update withdrawal!!!!!!!!!!!!!!!:cyclops::eek::eek:
[Nexus 7 Android Development] WugFresh:
Sorry, I have school work too. :/ I got a good deal coded today though. It sucks that I couldn't get it finished completely in one day, but I will get it done asap.

{{ WugFresh }}
[Nexus 7 Android Development] Mallikanth:
WIndows 7 64bit running the Toolkit worked a treat for my Nexus 7 16GB. SImple, easy and quick.

*Insert sexual joke here*

However, that Nexus has since gone back as I'm waiting for the 32GB release next week(ish) and I'm about to update my PC to Windows 8. Note: Not a fresh install, just an upgrade.

So my Question is - Does anyone yet know if the Toolkit works under Windows 8 and if so are there any special steps to take?

Many Thanks.
[Nexus 7 Android Development] WugFresh:
The short answer to your question is Yes - The toolkit will work on Windows 8.

I will make sure this works on every Windows release (XP and up).

Regarding the key difference of Win8 in respects to this toolkit - its the change Microsoft made for how the OS deals with drivers:

Win8 (by default) will not allow you to install unsigned drivers (at ALL) without the end-user doing some BCDEDIT hacks first (to boot it into 'Test Mode'), however (luckily) this won't actually be necessary for my program because I have confirmed that the digitally signed Galaxy Nexus Samsung Drivers actually work well on all the Nexus devices (including the Nexus 7 by Asus) on Win8 builds. The new driver guide in latest version actually knows this already (I programmed the logic in), and will detect that your computer is running Win8 and then recommend that driver solution to you (Driver Solution #2). I knew Win8 was just around the corner so I took the preemptive initiatives necessary to ensure everything would work properly once it was released. If for some reason people are having problems getting the Signed drivers to install, I can release an update which will automate booting Win8 into test mode temporarily to allow the unsigned drivers to be installed, however I don't think this will be necessary.

So, if you used any other driver solution except #2 then my guess is that you will have to reconfigure your drivers again after the upgrade. That's it regarding instructions. Cheers. :)

{{ WugFresh }}
[Nexus 7 Android Development] Mallikanth:
Fantastic news!

Thanks for your foresight and all your hard work!

:cool:

[EDIT] Donation sent (3FF06332S5212450F)
[Nexus 7 Android Development] Mallikanth:
Just dropping a line in to say this fantastic toolkit worked with 64bit WIndows 8 Pro (Upgrade from Win7 64bit)

Had a few problems with signed ADB drivers not working and even Wugs detailed instructions from within the toolkit didn't work for me.

I installed his Samsung drivers and then the USB drivers from the Asus site and everything just worked fine! :)
[Nexus 7 Android Development] WugFresh:
@SteveC485

The issue is related to the new bootloader in version 4.1.2 and the outdated TWRP img file the toolkit currently uses. You can flash the 4.1.1 bootloader after flashing 4.1.2 and then re-root, or wait for the next toolkit update (v1.5.5) which will fix these problems.

**Edit**

Also, as a sidenote: Using "Any Build" mode should be your first troubleshooting option if you are having problems rooting with the toolkit ever.

{{ WugFresh }}
[Nexus 7 Android Development] n7of9:
i just updated my ROM to 4.1.2...do i need to update my bootloader?
[Nexus 7 Android Development] mullemulle86:
If you want the opportunity to cold boot in to recovery yes. If not not

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Nexus 7 Android Development] WugFresh:
Right. Those drivers from Asus are the same drivers included in the toolkit here:

\data\Drivers\RAW_Drivers\Google_Drivers

They would get installed if you followed Driver Solution #3. they are the same drivers google provides in the SDK, they are not made by Samsung - nor are they digitally signed.

In order for you to have installed them on Windows 8 - you would have had to boot your computer in Test Mode, either using BCDEDIT cmds or through the boot options menu. Just curious how you actually went about doing it, because if you didn't enable Test Mode then you didn't install those raw driver files.

{{ WugFresh }}
[Nexus 7 Android Development] SteveC485:
I suspect if I take the ota upgrade (it's getting to be a pita telling it to install later) that I'll have a stock ROM 4.1.2 Nexus 7 with an unlocked bootloader. So if I understand this, I need to take the OTA, flash the older bootloader, test the driver, update driver if needed and use the root button

Another question. When I use the XP version desktop, there is something called "Trusted Software" that pops up in the download of the older bootloader (from the link in your OP) telling me I need to let windows find a file to open the file with, whereupon it tells me windows can't open the file. I am a bit hesitant to put the file from the laptop (where it would not load) and copy to the desktop in the right place.
[Nexus 7 Android Development] WugFresh:
Yes, if your drivers are already configured you can skip those steps regarding drivers.

The bootloader is an img file, my guess is that your XP computer has no software to deal with that file extension. Why its considering an img file "Software" makes no sense - but basically what is happening is that

upon download completion your computer is trying to open that file and doesn't know how to

. Or maybe you do have software on that XP machine that deals with img files, and its trying to mount the file as virtual CD but then it fails because its not packaged like a standard iso file - its built for android not windows.

My guess is that you are using a horrible browser like internet explorer on your XP machine and for whatever reason its trying to auto-open the file upon download completion. Instead - download it with a good browser like chrome/firefox.. then it will just download it (as it should) and it will reside in whatever the default download directory is.

{{ WugFresh }}
[Nexus 7 Android Development] Mallikanth:
To be honest I did so many uninstalls, re-installs and re-boots I've totally forgotten the exact sequence of events. I do know, however, I did not boot into a Test mode (Not that I know how too).

Always with Option #2 (the only one I ever did) it finished fine but 'Samsung' was never available when manually selecting a driver (I emailed some screenshots to you at the time).

Anyway it's all resolved now - Thanks yet again for a wonderfully useful tool. I promote it's usage whenever I can.
[Nexus 7 Android Development] SteveC485:
Well, you are right. I had been configuring Chrome and using it lately (have not yet sorted through the resulting bookmark maze). I happened to, from force of habit I suppose, simply clicked IE and I was there when I tried downloading the bootloader. I went to chrome and the "Trusted software" thing wasn't there and everything worked. This desktop is used by several family members, and I am going to get a new laptop in the next couple of days that I will do all of the modding things I want to do on, as I am now pretty sure my old laptop is about to die. Anyway your Toolkit worked just fine, and re rooted the 4.1.2 update.

I now have the sgt7 ROM and the Trinity DerKernel. The 7 is now a different device altogether.

One other question. How are all of the tool kit functions going to be affected with WIndows 8? I ask because Staples has a screaming,too good to pass up sale on a new HP with Windows 8 I may well buy.

Thanks again for your time and effort:o
[Nexus 7 Android Development] WugFresh:
It will work on Windows 8, the driver guide will recommend the signed driver solution. To install unsigned drivers you need to boot Win8 in test mode. I may add an option to automate that in the next release, but I don't think it will be needed. I am running Win8 Pro right now, it works.

{{ WugFresh }}
[Nexus 7 Android Development] anirudh15891:
regarding the samsung driver installation

Hey i have a problem regarding the Samsung driver installation.

The visual guide would open but the Samsung USB driver installation would not open. I am running windows 8 and I am having trouble with this. What do you think the problem is? any solutions to this?

thank you soo much
[Nexus 7 Android Development] Baldyl0cks:
Can I use this to unlock/root my Nexus 7 and keep stock recovery instead of CWM?

if so will I get update notifications/downloads? (and use voodoo to keep root when applying?)

Thanks in advance!
[Nexus 7 Android Development] WugFresh:
Yes. Select the option to root without flashing cwm.

{{ WugFresh }}
[Nexus 7 Android Development] B-Mod:
Small donation your way for this helpful tool.

9P6682154N0890511 confirmation #. Thanks.........Brian
[Nexus 7 Android Development] ghostcorps:
Thanks!!!

Donated $5. I wish I could do more but I'm pretty skint at the moment.
[Nexus 7 Android Development] NZtechfreak:
Good point. I like to think it is good for people to have a nice introduction to some command prompt stuff though :)

Maybe add link to guide in your first post?
[Nexus 7 Android Development] FiveOhFour:
The link to the tool seems to be down, any mirrors?

If anyone could click my name and email me the tool directly i'd appreciate it, or just send to backupemail86 at gmail dot com, thanks for all the hard work
[Nexus 7 Android Development] WugFresh:
http://www.softpedia.com/progDownload/Galaxy-Nexus-Root-Toolkit-Download-213077.html

{{ WugFresh }}
[Nexus 7 Android Development] FiveOhFour:
Thanks so much man, I didn't even think that site was a possibility, I tried.searching fore bugging you but when Googling the file name I just got a million threads to a million sites created by you on every android related site in existence, it seems you are quite the popular fellow :-P thank you kindly
[Nexus 7 Android Development] WugFresh:
Sure I would be more than happy to. I will add it tomorrow when I wake up. I went out with some friends tonight so there is a few too many drinks in me now.. lol. It would be cool if you made it a bit clearer in your guide that the SDK is not required for the toolkit, and that Temp CWM is an alternate solution to the one you posted. Thanks again for creating the guide. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Updated the OP with a new link to the Softpedia download page. Looks like Goo.im keeps going down. I will check out some alternate file hosting solutions.

{{ WugFresh }}
[Nexus 7 Android Development] nicksoph:
Two Processes when ADB.exe is called

Hi and thanks for a nicely put together thing.

I did find one thing that seemed strange - whenever the toolkit called ADB.exe I would see two 32 bit ADB processes start in Task Manager? one of which would then close a few seconds later, the other would stay open and whatever message the toolkit had on the screen (eg - Waiting for device) would stay there until I Ended the process in Task Manager when the program would continue normally.

Im using 64bit win7 on an i7 with Hyperthreading turned on and I suspect this might relate but thats pretty much a guess.

Thanks again

nick
[Nexus 7 Android Development] Nitsson:
Thanks. Downloaded 1.5.2 after the 4.1.1 OTA update where I lost root. A mere 15 minutes later it was sorted again.

Great work!
[Nexus 7 Android Development] neilrl79:
Just wanted to say that nothing could be easier than this toolkit! Thank you.
[Nexus 7 Android Development] landstander:
WugFresh,

Just curious... do you have any plans to add support for TeamWin Recovery (TWRP)? The reason I ask is that it (unlike Clockwork) now supports encrypted data partitions for the Galaxy Nexus, which is a godsend for those of us making use of this feature.

Either way, thanx for making your toolkit available! :)
[Nexus 7 Android Development] neilrl79:
The tool itself already has the ability to flash whatever recovery you want to use, you just need the twrprecovery.img
[Nexus 7 Android Development] jasoraso:
Thanks for the tool, WUG.

Just a note that I also had a problem getting drivers installed for the Nexus 7 on my Win7/64 PC. I ended up using the PDANet drivers posted in the early pages of this thread.

Everything else worked great. I unlocked/rooted with the 2nd OEM update already installed (JRO03D).

Used app "Quickboot" to reboot into CWR - worked great.

Thanks!
[Nexus 7 Android Development] golfinggino:
I still can't get this to work it looks like the drivers load correctly but when I click the unlock button it says checking adb and stays saying this I am still not sure why it I'd not working for me
[Nexus 7 Android Development] xopher.hunter:
I just want to give a big thanks to the OP. I am generally pretty tech savvy however I have bricked my nexus 7 twice within the first hours of using it (driver issues and LCD density pro) and both times your tool has saved my ass. Thank you
[Nexus 7 Android Development] caanda45:
Thanks wug, a little appreciation of your work...Confirmation number: 70K63339UD623533A

I just rooted, when the cwm situation is cleared up can I run the tool and just put on cwm with the permanent cwm option?

Thanks again, great tool!!!!:cool:
[Nexus 7 Android Development] FiveOhFour:
Would love to see this, any chance of it coming to fruition?
[Nexus 7 Android Development] WugFresh:
Not sure why its not starting, but the exe resides here:

\data\Drivers\Samsung_Drivers\Samsung_Drivers.exe

So you can just launch it. I will see if I can reproduce this on my Win8 machines but I haven't had that happen yet. Maybe its due to some changes in UAC. Do you have UAC enabled? I think its enabled by default. I always disable UAC right away - its like the first thing I do. "yes windows, I wan't to do exactly what I said I just wanted to do"

{{ WugFresh }}
[Nexus 7 Android Development] anirudh15891:
wont work

I have tried that as well and it wont open up. I went there and tried to open it and it would just ask me if i am sure I want to open it and I would press yes and then it wont do anything after that. I tried opening it as an administrator and that didnt work either.

any other way !? :(
[Nexus 7 Android Development] WugFresh:
You have tried disabling UAC?

Run > UserAccountControlSettings.exe > "Never notify" > restart computer

That is just an exe file downloaded directly from Samsung. Have you hashchecked your toolkit download... are you sure you have a complete download. You can grab the same exe from Samsung's website:

http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW#content2

click "software" then exe to download.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Also... check if its running already. Maybe you have lots of instances trying to open because you never waited the first time. Try checking your task manager. Kill the processes if they exist and then try again. That program may be lagging to start and you just weren't patient.

{{ WugFresh }}
[Nexus 7 Android Development] anirudh15891:
:(

This is getting ridiculous. I have tried everything you just said. I even downloaded another one and it still wont work. I have changed the user control to off and even downloaded the Samsung software directly from the site and it will still not open. non of the rooting methods are working. neither this one nor the other ones available in nexus 7 forum. Win 8 has got to do something with this. I even checked if multiple ones are open.. but they are not.

I am completely dumbfounded and not sure what is going on. any other suggestions? if not thank you soo much for your help and time. really appreciate it.
[Nexus 7 Android Development] WugFresh:
Like I said, I am running Win8 on multiple machines and don't have this problem, so it must be related to something else with your setup/configuration. That said, yes.. there are multiple trouble shooting options. Here are two to start with.

Troubleshooting Option #1:

Try again running it compatibility mode:

Right click the exe > "Troubleshoot compatibility" > "Try recommended settings" > "Test the program..."

If that still doesn't work, you really might want to consider re-installing Win8: it's not a good sign if you can't run exe's...

Troubleshooting Option #2:

You can use the RAW unsigned drivers instead if you enable Test Mode on Win8:

Open a cmd prompt as an Admin and enter the following cmds:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

Then restart your computer, or if you are feeling extra nerdy type this into cmd prompt to restart:

shutdown /r /t 1

Then use the Driver Solution #3.

Then after you are all done, if you wan't to revert back to Winows8 default driver behavior and disable test mode, then open a cmd prompt again as an Admin and enter the following cmds:

bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF

Then restart your computer again.

Let me know how that works for you.

{{ WugFresh }}