yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] gokart2:
@WugFresh....curious as to what your doing in the next update about the bootloader issue. Since the new botloader is wanted in order to cold boot to bootloader/recovery without freeze....are you going to keep the previous bootloader installed until the end of the root process so everything goes fluid? Then flash the new bootloader after the fastboot reboot?
[Nexus 7 Android Development] WugFresh:
I honestly haven't decided yet because a lot of people seem to have no problems with the new bootloader.

However for those people who do have problems with the new bootloader, reflashing the new one at the end of the process would probably be a bad idea because then all the other toolkit features which rely on the "fastboot boot" cmd wouldn't work.

Part of me thinks that the issue is related to USB ports although I haven't collected enough evidence to firmly back up that assertion. It seems that users who try using USB 3.0 ports with the toolkit experience more inconsistencies than those who use USB 2.0 ports. Like I said, I am only partially convinced that this has anything to do with it, so I still need a universal solution.

I guess I will have to program in some logic, or make it a user option regarding what to do with the bootloader.

{{ WugFresh }}
[Nexus 7 Android Development] maigre:
In my case, the USB port wasn't USB 3. It was one of the front of the desktop machine USB ports, fwiw, so I'm going to try the back of the machine. Unrelated to NRT, I have some problems doing file transfers with those same front ports. Most files do fine, but some don't and Windows give me an message saying that it can't copy the file(s.) I end up using AirDroid, which has its issues, too, but at least the files get to their destinations. I also have problems with USB file transfers over my 4 year old MacBook Pro. So I suppose it's possible that the Nexus 7 has some USB problems.

I'd like to avoid another case of having to flash to stock and starting over. I want to let the device try an OTA update, though that failed last time around. But now the OS doesn't prompt me anymore.
[Nexus 7 Android Development] TedT100:
I have tried a dozen methods of deleting the !readytoflash folder but none seem to stick, has anyone else had this issue? Sorry if this has been previously answered.
[Nexus 7 Android Development] WugFresh:
Have you tried "Shift + delete" in windows explorer with your device connected via usb? Or if you have a good app like Root Explorer you should be able to delete it. If not hit me up on gchat and I will help you.

{{ WugFresh }}
[Nexus 7 Android Development] marshalllaw:
Just tried your app on my 4.1.2 nexus 7. Worked like a charm without having to flash the old bootloader.

FYI: I used the usb2 ports at the front of my computer.

Looking forward to using your app on my galaxy nexus :).

Keep up the good work!
[Nexus 7 Android Development] CBers:
NRT Updater doesn't work

@WugFresh - just tried the NRT Updater (Wug_Updater.exe), to update from 1.53 to 1.54, but it did nothing after the download, other than sit there on the screen for 5 minutes until I closed it:

I can download and install latest version, but the NRT Updater would be better.

I couldn't find any log files anywhere, are there any ??

UPDATE: I tried what you suggested about the spaces in the folder name here and found that I had to remove the space in the "WugFresh Development" folder name to "WugFreshDevelopment".

The update then worked OK.

Perhaps some more thought needs to go into the updating process, but I know what to do for future reference.

Thanks for a great toolkit.
[Nexus 7 Android Development] WugFresh:
Yeah... It was a mistake. It wasn't like I wanted to make fixing the path a prerequisite for updating. A lot of thought and time went into the update process, it was very frustrating to discover that mistake. I explicitly state the information on my site.. So I am not sure why you decided to bring it to my attention.

Either way... Glad to hear you got it figured out.

{{ WugFresh }}
[Nexus 7 Android Development] justinangil:
This solution works perfectly with 1.5.4

FYI Coming from OTA 4.1.2. Was previously unlocked and rooted.
[Nexus 7 Android Development] rodem77:
Hi, I've a question:

since android 4.0 is possible to apply an OTA using ADB from stock recovery. With this tool, it is possible to apply an OTA using flash.zip command in advanced utility?

Yes in all situation (all stock without unlock and root) or only if I've unlocked bootloader or rooted device? Thankyou.
[Nexus 7 Android Development] dirtyhamster73:
Wug, I apologize if the answer to my question is right in front of my face, I am rather confused about what your plan is for the toolkit....in the future, if I needed to go back to stock, will there be an option for me to select 4.1.2 with the new bootloader? Again, sorry if you've already stated your plan. Thanks!
[Nexus 7 Android Development] WugFresh:
Yes. No worries, the answer isn't right in front of your face, I haven't made my plans entirely clear yet for the next version. Without explaining the exact details I will say this - I will always make everything a user option. I have no intention of making any feature in the toolkit force a decision on the end user without their explicit knowledge and consent.

Regarding the Flashing stock feature, that will always flash the stock factory image google provides (w/o any modifications - downloaded directly from their servers). The only time I may consider swapping in the old bootloader in is when rooting, but I am still not set on that idea yet as I am getting mixed results (lots of people successfully rooting without this step). I think I will just program in an additional step that will simply ask the end user if the root was successful, and if it wasn't it will run through the process again - flashing the old bootloader.

But yeah - I will never taint the flash stock feature to do anything else except what the name implies: Flash the stock factory image.

Hope that clears things up a little. :)

{{ WugFresh }}
[Nexus 7 Android Development] dirtyhamster73:
It more than clears things up! I was one of the people who had no issues re-rooting after the 4.1.2 update, I even forgot to change the model to 4.1.2, it was on 4.1.1. Thank You very much. I appreciate it.
[Nexus 7 Android Development] WugFresh:
Also, I hunted down all the old and new factory image packages on my external hard drives and organized them on goo.im here

http://goo.im/devs/WugFresh/stock

So maybe in the next release I will make the flash stock feature have a pull down menu, so that the end user can select any factory image with the "auto-download, extract and flash" feature, rather than just the latest one available. I think that might be a good idea.

{{ WugFresh }}
[Nexus 7 Android Development] dirtyhamster73:
That sounds like a genius idea to me!!
[Nexus 7 Android Development] spongaweb:
Having a slight problem with USB debugging being enabled. I cant access my Android OS and stuck at fastboot. How do you enable USB debugging through fastboot or ADB mode, not able to really flash anything with any of the tools. Enabling USB debugging mode basically.
[Nexus 7 Android Development] WugFresh:
Fastboot communicates with your device when its in bootloader mode regardless of usb debugging. ADB on the other hand communicates with your device when its on with USB debugging. If you are unable to boot your device into the OS, use the "Flash Stock + Unroot" button with "can't boot up" and it will walk you through restoring your device. Follow the steps in the driver guide that pertain to configuring your device in bootloader mode if your device isn't getting recognized in bootloader mode.

{{ WugFresh }}
[Nexus 7 Android Development] golfinggino:
I just picked up my second Nexus 7 today my first 1 is unlocked rooted running Paranoid Android 2.2 with the latest Franco kernel I plan to unlock this Nexus 7 and put on a custom ROM my question is it is currently on Android 4.1 .1 should I try to do an ota update to 4.1 .2 and unlock and root from here or should I just unlock and root from 4.1 .1

My question is which is easier
[Nexus 7 Android Development] maigre:
I've mentioned that I'm among those who couldn't get to 4.1.2 rooted via NRT. I'd gone back to 4.1.1 and rooted that.

After not doing so for a few days, the device prompted me to do an OTA upgrade a little while ago. I let it do it and got to 4.1.2. Last time I tried the OTA, it failed, maybe because I had the CWM recovery installed. I'm not sure. This time around, it was stock. Anyways, I rooted with NRT without using the older bootloader and got to 4.1.2 this time quickly without problem, except for one possible thing.

The differences were stock vs. CWM recovery and the USB port on the Windows machine. Last time, I used one of the front ports; this time, I used a rear one.

The possible, but unlikely problem is that when prompted by NRT to open SuperSU and update the binaries, SuperSU gave me a warning that it couldn't find them and that this wasn't a good thing. Maybe the WiFi connection hadn't kicked in, yet. It then closed. I reopened and got no messages of any sort. Maybe that's because it had been rooted before with 4.1.1 and they were already there. I'm not sure. I'm assuming this is not an issue.

Bottom line, all seems well this time around.
[Nexus 7 Android Development] teonghan:
I just successfully rooted my Nexus 7 (stock, JB 4.1.2) using Wug's Nexus Root Toolkit. Unlocking was OK the 1st time but I need to restart the toolkit once when my 1st attempt hang (toolkit hangs in Windows 7 64bit during rebooting to bootloader after I press the root button) and my Nexus 7 showed not sign of rebooting. 2nd attempt was smooth sailing. Anyway, thanks for creating such an awesome tool and make our life easier.
[Nexus 7 Android Development] justen7723:
I just used this yesterday. No problems at all. Was on stock 4.1.1 took the ota to 4.1.2, then used the toolkit with not one problem. Thank you!!!

This thread should b stickied IMO.
[Nexus 7 Android Development] spongaweb:
Cha, ching and we no longer have a brick. Problem rooting now but a little reading shows I probably just need to change the bootloader
[Nexus 7 Android Development] digixmax:
FWIW, my N7 was on 4.1.1 & rooted (using NRT v1.5.3); took the OTA 4.1.2 (and lost SU), then re-rooted using NRT v1.5.4 (and regained SU) w/o any apparent issue.
[Nexus 7 Android Development] AgeOfPanic:
Hi guys, today I rooted my Nexus 7 running 4.1.2 succesfully. Before that I did multiple backups with and without system apps etc. My question is whether I can restore the backup or will that cause me to loose root? If yes, which backup should I choose (preferably as close to pre root as possible)?
[Nexus 7 Android Development] WugFresh:
I have always recommended against batch restoring system data, it can lead to unforseen problems. I would restore the backup with just user data and take the extra time to manually reconfigure your system apps. No, it will not effect root at all.

{{ WugFresh }}
[Nexus 7 Android Development] squarejp:
I tried to root my OTA updated Galaxy Nexus 4.1.2 but unsuccessful. There is no root access but the SuperSU is still there.

I tried to clean flash the Nexus 7 to 4.1.2 but still can't root. No Clue at all.

I use both Windows Vista and Windows 7 Ultimate 64Bit systems. Both failed to root the 4.1.2 Galaxy Nexsus and Nexus 7.
[Nexus 7 Android Development] WugFresh:
From my website:http://www.wugfresh.com/dev/nexus-root-toolkit/

Important notice - For users having problems rooting 4.1.2:

Most users reported no difficulties rooting their 4.1.2 builds with the toolkit (just by selecting the correct android build/version in the pull down menu and pressing the root button) - however if you are having problems try this solution: http://xdaforums.com/showpost.php?p=32789382&postcount=1199

I am not sure why it works for some users without doing this and for others this is needed. Hopefully I will figure it out soon so I can roll out a fix in v1.5.5.

It seems that the issue may be related to USB 3.0 ports - consider trying a USB 2.0 port instead

Hope that helps.

{{ WugFresh }}
[Nexus 7 Android Development] squarejp:
Both of my windows 7 and Vista systems are still using USB 2.0 not 3.0.
[Nexus 7 Android Development] WugFresh:
Ok, that is only part of the suggestions. Did you try reverting to the older bootloader. I provided a list of suggestions... please try all of them first. I linked to the post in what you just quoted.

Here it is again, against you missed it: http://xdaforums.com/showpost.php?p=32789382&postcount=1199

{{ WugFresh }}
[Nexus 7 Android Development] squarejp:
I tried to flash back to the older bootloader, it says ADB device was not found.
[Nexus 7 Android Development] WugFresh:
Regardless of what method you use, the toolkit, or manually - you need to configure your drivers first. If it says adb device not found, that means the program can't communicate with your device, so it has absolutely no way of rooting it. Please note, that the message that says your ADB device was not found also provides a list of suggestions on how to go about rectifying that situation, primarily - following the driver guide. I put as much information as I could in that driver guide, and I can't provide any additional support on that. If you spend the time to read the suggestions, and try all three driver solutions, to no avail; then you can try contacting me via gchat, and if I am available I may be able to offer you assistance. I would greatly appreciate it if you tried following the instructions and the suggestions I provide in the toolkit first - rather than reporting your experience encountering a pre-scripted message boxes that I personally programmed into the toolkit to explicitly tell end-users what to do to fix a specific issue moving forward. I am sorry you are having some difficulties but please try the things the toolkit explains first. I hope you get it figured out. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] squarejp:
Okay, I have realized the issue. It is because of the Team Win Project menu. Since there are no further instruction to deal with TWP, I finally discovered that I must need to do the following:

Select Root and follow all the toolkit instructions

When Team View Project pops up, select INSTALL

Go to the SD Card Directory and select !ReadyToFlash

Select CWM-SuperSU-v0.94.zip and run it

VOLLA ROOTED!!!! and reboot back to the Android!

Thanks WugFresh for your tool but I think there should be a script following the TWP to specifically activate the root installation
[Nexus 7 Android Development] WugFresh:
There is.. It's fully automated if everything is done properly. No user interaction is necessary in recovery if you select the right build. Any Build mode requires you to do those steps but provide instructions. Regardless glad you figured it out.

{{ WugFresh }}
[Nexus 7 Android Development] rodem77:
Hi, with user data do you mean also apps manually installed and apps data? To avoid unforseen problem how kind of backup option do you recommend? A nandroid backup after root include all data, is good to use a nandroid backup to restore a system with problem or is better to do for example a clean install and later restore only some data? Thankyou.
[Nexus 7 Android Development] ace-user:
not sure what's happening but when it's in fastboot mode my nexus 7 just stucks at "booting download image" for quite some time now and my computer just shows "waiting for your device to finish booting back up"..any ideas??
[Nexus 7 Android Development] kosai:
Switching Recoveries?

Could someone tell me how to switch Recovery from TWRP to CWM using this tool? Will selecting the "Root and also flash" option work after selecting CWM in options work even though I am already rooted with TWRP or will this cause an issue?

Thanks.
[Nexus 7 Android Development] WugFresh:
That would work, you could also use advanced utilities "flash to recovery" button and select the TWRP img file for your device.

{{ WugFresh }}
[Nexus 7 Android Development] kosai:
Thanks Wug. Awesome tool you've made here, I sent a request to get this stickied (finally) and it looks like it's done.
[Nexus 7 Android Development] WugFresh:
Sorry, I assumed you were talking about creating an android backup file with the toolkit. Regarding nandroids, those are the best backup solution, because they are full image of your entire setup.

If you make a full nandroid on a device that is running properly, then restoring that nandroid when you are having problems is a good and easy way to try and fix that problem. If the problem persists, then re-flashing stock first, and then just restoring user data from your backup might be a better solution.

User data, means everything that isn't a system app (system apps are things like - the default email client, contacts... ; they reside in /system/app). If you are rooted you can use a good explorer app like "Root Explorer" and see all your user apps in the directory /data/app

If you are backing up data, to later restore it on a different ROM or a newer android build.. Then you do NOT wan't to restore system data, because it will overwrite all those system apps that are unique to that ROM or newer android build with the system apps backed up in your nandroid. In that case you would want to selectively restore just the "data" partition.

Hope that explains things a little better. Cheers.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Yay! I got a sticky. Thank you, and thanks to everyone else who requested this thread get one.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
This solution applies to all problems regarding it getting stuck or stalled at booting download image, or the booting download image not working successfully: http://xdaforums.com/showpost.php?p=32789382&postcount=1199

{{ WugFresh }}
[Nexus 7 Android Development] rodem77:
Yes I unlocked and created a nandroid with the toolkit and yes now I've learned the difference between data type. Thankyou.
[Nexus 7 Android Development] AgeOfPanic:
I tried restoring everything including the system data as well ;) (stubborn I know). Still lost my Google account settings and some of the apps. However, for the rest it seems to run fine. Thank you for your help and the tool. Stickmount is great.
[Nexus 7 Android Development] Vasya4:
Hi, I have Nexus S Baseband version I9020XXKL1 which just received an OTA update to 4.1.2 (Build number JZ054K). Can I use this toolkit to root it or it's incompatible since my version is not listed? I thought it might be the same as I9020T but I could be wrong and don't want to brick the phone.

Thanks!
[Nexus 7 Android Development] CBers:
I mentioned it here as I didn't know about your website until after.

Thanks.
[Nexus 7 Android Development] Gibsonflyingv:
Alright, I unlocked and rooted a long while back with wugfresh. I recently had an issue so I needed to go back to stock. So, of course I went and unlocked and rooted again. I have a problem though. Whenever I try to install a custom rom, it will flash successfully, but it will just stick at the boot animation for forever. I've tried both TWRP and CWM, but still the same issue, I've tried different roms too. Am I missing something really stupid? I hope some one can help me out. Thanks in advance if you can.
[Nexus 7 Android Development] WugFresh:
Are you using the toolkits "flash zips" button ("file on my computer") with the default suggestions for ROMs? If not, try that. Basically the toolkit will recommend and automate wiping data, cache and dalvik first before flashing a ROM. If you aren't doing that, it can cause bootloops. Obviously make sure to backup stuff before wiping.. If you are using the toolkit with the default suggestions it will also back everything up for you.

{{ WugFresh }}
[Nexus 7 Android Development] Gibsonflyingv:
I'll give it a try. Thanks again man.

---------- Post added at 01:20 PM ---------- Previous post was at 12:39 PM ----------

Alright, I did what you said. Tried to use the utility to flash Kaos Droid 3.8.0, I've been sitting at the boot animation for 10 mins now :(

It also won't enter recovery now. It sits at the "Google" screen instead of going into recover.
[Nexus 7 Android Development] WugFresh:
Try flashing the older bootloader.

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 flashing the zip again.

4. Win!

{{ WugFresh }}
[Nexus 7 Android Development] Gibsonflyingv:
Alright, flashed that, tried again. Hung at the boot animation again... dafuq is wrong with this pos. I'm gonna have to flash to stock again since it cant find my backup either -.-
[Nexus 7 Android Development] WugFresh:
I was going to recommend flashing stock as your next course of action regardless.

{{ WugFresh }}
[Nexus 7 Android Development] Gibsonflyingv:
I've flashed back to stock a few times since this has happened. I had this happen to me yesterday late, so I couldn't post, but that was my first line of action. I've checked root too just to make sure I'm not off my rocker and its rooted... so, I'm speechless.
[Nexus 7 Android Development] WugFresh:
Hmm... try doing it all in TWRP yourself, without the toolkit, and after you flash a ROM, wipe data and dalvik again. Give it a while to do boot up, even if it appears to be bootlooping. When you erase dalvik it needs to rebuild it, and sometimes may appear to bootloop.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Also, to be clear. You are just trying to flash one ROM.zip.. like you aren't trying to perform multiple operation before first boot.. like also installing gapps, or restoring data right? Because sometimes trying to do too many things at once can cause problems.

{{ WugFresh }}
[Nexus 7 Android Development] Gibsonflyingv:
Generally I've been giving it 10 mins. I've never had my tab take longer than 5 really, but if thats not long enough tell me.

KaosDroid is installed via aroma, so it may do all together. I'll try and install another with just the rom first and gapps after a reboot.
[Nexus 7 Android Development] nexusplexus:
Do I have to go through the 'Driver Installation' if I've already installed the Nexus 7 toolkit and the Android SDK?

TIA!
[Nexus 7 Android Development] Gibsonflyingv:
Well, good news. I successfully got liquidbean to flash. Maybe it just doesn't like flashing kaos right off the bat. I'm going to try Kaos now, and I'll update later. Thank you for sticking with me on this.
[Nexus 7 Android Development] WugFresh:
Try step 3 of the driver guide.. The driver test. If it works then you can proceed to use the toolkit.

{{ WugFresh }}
[Nexus 7 Android Development] WugFresh:
Cool, glad you got it figured out. No problem. Yeah, multi flashing is a known cause for bootlooping, just keep that in mind in the future if you ever experience that again. Cheers. :)

{{ WugFresh }}
[Nexus 7 Android Development] Gibsonflyingv:
WE HAVE BOOT! I LOVE YOU MAN! Thanks for stickin with me though, seriously.
[Nexus 7 Android Development] ComputersWelcome:
Thanks again for this, I had to install drivers for Nexus 7 on this program, then use the other toolkit for the relock and back to stock.
[Nexus 7 Android Development] snipe2nite:
Solid work Wug, glad it finally got stickied!!! You deserve it my dude, much respect..... :good: :good: <~~~~2 thumbs uP for your work
[Nexus 7 Android Development] talltexan:
Frustrated, this is the first device i have not been able to root or figure out why i cannot root. I have rooted many devices, starting with the G1 so i am not a n00b. I stripped my computer of all the drivers , reinstalled drivers, tried switching it to camera connection rather than media and still cannot get darn thing to root. Whenever i run the toolkit the drivers test out and i run through all the root instructions but when i try and run SuperSU it tells me that its not installed. I am running 4.1.2 just got the Nexus a week ago.