yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] mdamaged:
So then you got it flash and boot then? And no problem, glad to help.
[Nexus 7 (2013) Android Development] mdpatterson:
Yes, as I type this my google accout is restoring, also I installed SU from TWRP before I did fastboot reboot. for some reason I thought that after I did fastboot system etc.. that thats all I needed because I erased the sys. Anyways after reboot, had to get back to bootloader, before hand I was prompted with the "there is no SU installed, would you like to install it?" so then the way i understand it is that when I wiped the system.img before, Su was obviously wiped. so i flashed su again. and finished the process with success. and i believe now i just need to go the play store and download busybox correct?
[Nexus 7 (2013) Android Development] mdamaged:
Yes, busybox is used by many root-enabled apps, though some apps provide their own busybox bins, it's good to have a full install of it. FWIW, I use the Normal install as opposed to the Smart install.
[Nexus 7 (2013) Android Development] mdpatterson:
I saw that last time...when I set up my device initially. I didnt want to mess up my device so I just went the normal route. what are the pros and cons
[Nexus 7 (2013) Android Development] mdamaged:
You know, I'm not really sure, I googled it till my head exploded, and noone seemed to be able to give a definitive answer, but from what I've gleened, I think one method uses symlinks and the other doesn't, or maybe it looks to see what's already installed and what's not and only installs what's missing/outdated, I dunno, all I know is I always use Normal and never had one issue with it, so there you go, maybe.

Also, make sure the install goes into /system/xbin.
[Nexus 7 (2013) Android Development] mdpatterson:
ok, will do. thanks again, badass work.
[Nexus 7 (2013) Android Development] WugFresh:
Try using flash stock + unroot with "softbricked" checked.. As long as you can get fastboot to work.. Then that should work for you. Your device is fine and you will be able to fix it.. You just have to get fastboot working.. That's really your only obstacle.

If you are running Linux and you already have the SDK setup properly (meaning you added adb and fadtboot to your path).. Then you could just skip using my toolkit all together for flashing stock.. just execute the flash-all.sh script which is included in the factory pack (just extract the pack first).

If you want to use the toolkit which automates everything.. You may want to try it on a windows comp instead if Wine is giving you problems.

Hope that helps.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] WugFresh:
Oh sweet. Looks like you already got it resolved.

Thanks to those who helped out. :)
[Nexus 7 (2013) Android Development] WugFresh:
I think smart install checks whats on there first. I have used both normal install and smart install in the past - and they both worked great for me.. So it's really whatever. :)

{{ WugFresh }}
[Nexus 7 (2013) Android Development] mdpatterson:
Thanks WugFresh, I think this is like you said in another post and mine that wine has worked for some, but not all. for whatever reason wine just wasnt working for me. thanks for help. Still count on WugFresh for my nexus 5 on my wife's surface tablet. keep up the good work
[Nexus 7 (2013) Android Development] e2zippo:
Just got my N7 back from repairs and used your toolkit to root and unlock again and flash CleanRom, and the process is to simple now, everything just worked, many many thanks! :good::good:
[Nexus 7 (2013) Android Development] DaveC1964:
I tried to use this tool but no go. I have a new N7 with the latest OTA update. It unlocked the bootloader fine, then rebooted into fastboot (says bootloader: unlocked"). Then at the stage "Booting modified boot.img to enable.." it just hangs forever (the first time the HDD was accessing but after a very long time stopped then did nothing). I had to hold the power button on the tab for awhile to restart. If I try the whole thing again I get the same result. The tool looks good but the error checking could be better. It will just sit there forever not saying what the problem is. When I yanked out the USB realizing that the process froze The app said "rooting". Another time it said "temporarily booting TWRP". It didn't realize the tab was no longer connected.

Any idea what the problem is? I did the whole "driver dance" and check and that was ok. USB debugging was enabled too.
[Nexus 7 (2013) Android Development] WugFresh:
Indicative of you selecting the wrong device or build. Be careful with the N7.. There are four versions to choose from. Make use of autodetect since your drivers are already configured.

Yeah.. Yanking the cord after it completes a check will behave the way you described.. I can't program it to consistently check connectivity.. Nor do I want to include extra redundant checks.

Report back after you confirm your device selection and try again. Cheers.
[Nexus 7 (2013) Android Development] DaveC1964:
Hi,

In the instructions it said something to the effect of "look in the about phone section for device model" which is what I did. It just said "Nexus 7" and nothing else so that is what I selected. You are right, that is the wrong model, so the instruction there was a bit confusing to noobs. I just did the autodetect and it worked fine and rooted.

As far as some kind of indicator it may have been useful for some kind of 4 line window with text showing what the tool is doing. This way we would know if/what it is doing or if it has froze etc. While that is fine about not doing redundancy checks to see if some knucklehead has pulled out the cable (although sometimes dodgy cables can have intermittent connections) the status text could be useful. Just an idea though, it is no big deal as mostof the time the tool will "just work".

Thanks.
[Nexus 7 (2013) Android Development] brainimpact:
I just used this because for some reason my drivers were messed up preventing me from getting the permission to allow my PC access so could not use ADB.

This tool sorted it all out for me no problem. :good:

I hate it made me lazy though stopping me from unlocking and flashing a recovery manually using Command line, damn you automation :eek:
[Nexus 7 (2013) Android Development] WugFresh:
Check out the toolkits options menu. There is a feature called "live log" which is exactly what you are describing. It shows the adb/fastboot cmds being run and their corresponding output.

Thanks for feedback about the device/model select instructions. Not sure how I should change the info to make it more clear though.

Cheers.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] catexecutive:
Hello Wug,

thanks for your great tool.

Might you please update the PhilZ-recovery-image for the Nexus 7 (2013)-Wifi-version (flo)

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/flo

Your version: philz_touch_6.19.3-flo.zip

Current: philz_touch_6.25.0-flo.zip
[Nexus 7 (2013) Android Development] WugFresh:
Thanks for reminder. I will try and get that up later today. I actually have to code a bit more too to really integrate philz properly with all the kits features. I overlooked something's in the last release. I will at least update the version ASAP. For now use "alternate recovery" option and select that latest one.
[Nexus 7 (2013) Android Development] rahlquist:
Before I send my 3 month old n7 back for warranty work wanted to run this by you fine folks who are smarter than myself.

I had not bothered to unlock or root this device till today. I decided it was time and downloaded the app. Got the drivers working and hit unlock, rebooted to fastboot, hit the button for the unlock and the instruction screen flashed by real fast, it then went to the reboot screen. I found that odd but picked up my n7, selected yes and hit the power button. I waited 12 minutes and nothing happened. All that hitting the power button did for me effectively is cause the volume keys to stop letting me change the selection from yes to no. I gave it another 10 mins then finally powered it off.

Since then its still locked, I can get into fastboot but nothing will unlock it, and consequently nothing can flash to fix it and it wont boot past the google or the 4 color animation. I even tried the force flash option with softbrick/bootloop and that didnt work https://www.dropbox.com/s/clpq0666kedviyg/flash.jpg

Any thoughts or suggestions before I send it off?

Thanks!

EDIT:

Found the answer http://xdaforums.com/showpost.php?p=45083114&postcount=17

Just placing it in case anyone else has the issue.
[Nexus 7 (2013) Android Development] Scottchy014:
For all those who wish to do a factory restore and Relock their Nexus, I've put together a video for you on my YouTube channel. I used the Nexus Root Toolkit and it's awesome! Thanks [MENTION=3110798]WugFresh[/MENTION] ! Here is the link: http://goo.gl/xtTClF Enjoy!
[Nexus 7 (2013) Android Development] richarddwyer10:
This toolkit is a work of art, I'm very impressed good work.
[Nexus 7 (2013) Android Development] cujo6801:
Easy as 1 2 3.....

I had my 7 rooted in minutes..

Here's a late thank you... :D

Sent from the "DOG" pound
[Nexus 7 (2013) Android Development] yethz:
if anyone is having problem with wugfresh NRT homepage not loading, try the SoftPedia mirror download link ;)

http://www.softpedia.com/progDownload/Galaxy-Nexus-Root-Toolkit-Download-213077.html
[Nexus 7 (2013) Android Development] WugFresh:
Yeah. Thanks. Once this craziness with Bluehost settles down I will be looking to switch my host. Knocked my site and millions of others offline with no direct answers or support.

Sorry about the unexpected downtime.

{{ WugFresh }}
[Nexus 7 (2013) Android Development] PieceofSlice:
Hey, my Nexus 7 is having some pretty big problems. I was wondering if you could take a look at this thread if you had some time http://http://xdaforums.com/showthread.php?t=2716839

I've tried numerous ways of trying to get it back to factory settings, but nothing has worked. I'd really appreciate your input :)
[Nexus 7 (2013) Android Development] AKShotgun:
Why does Nexus Root Toolkit keep saying unknown chunk type while writing the system to the device? How do i fix this?
[Nexus 7 (2013) Android Development] mdamaged:
I can only guess, but it may be there is a fastboot in your path taking precedence over the one Wug uses and is incompatible.
[Nexus 7 (2013) Android Development] AKShotgun:
This is about the only program and the only device I use on this computer. I wouldn't see how any other fastboot related thing would be on here
[Nexus 7 (2013) Android Development] mdamaged:
Not sure if it would cause that error, but make sure you are selecting the Nexus 7 v2 rom to flash, some make the mistake of selecting the Nexus 7 one which is for 2012 model, try a different USB port, cable, don't use a hub, and don't use a USB3 port. Other than those things, not sure what else.

EDIT: Oh maybe you got a corrupted download, so maybe uninstall and delete any remnants of NRT, and redownload and reinstall.
[Nexus 7 (2013) Android Development] AKShotgun:
I tried downloading a different version of a android (4.4.0 KRT160) and it flashed just fine. But now im having this weird problem of 4.4.2 not downloading in the system updates section of about tablet.
[Nexus 7 (2013) Android Development] Martin Mystere:
Does this just root device without cleaning everything (leave everything as it is) or it will clean everything so I'll have to install everything from the beginning?
[Nexus 7 (2013) Android Development] Cuzz1369:
Rooting doesn't wipe anything. Unlocking the bootloader does wipe everything though. So if you are already unlocked you are safe to root without losing anything.
[Nexus 7 (2013) Android Development] Martin Mystere:
I didn't do anything with my Nexus so far, so does it man that use of this toolkit will wipe everything? And could be rooting done without unlocking bootloader?
[Nexus 7 (2013) Android Development] mdamaged:
Theoretically, if there is an exploit in the system one can root without unlocking bootloader, but this method for the N7 2013 is not something I am aware of being in use, there is one for the N10 and the old N7 (not sure to what extent they are successful), so I do not have a link or anything for you since I simply could not find anything that can exploit kitkat on the N7 2013 that seems legit.

That being said, you can simply make a backup of your data using Helium (or android backup, though I recommend Helium), unlock the bootloader, root, then restore your app data, you can then even relock/unlock the bootloader if you so please using bootlocker without wiping it again. Frankly, you might as well leave it unlocked, when your unit bootloops one day, you'll be glad it's unlocked.
[Nexus 7 (2013) Android Development] Cuzz1369:
Take the advice above or there is a backup feature in this toolkit too. I've never used it but basically(I think) it does a nandroid backup to your PC I think and then you can unlock your boot loader, wipe the device, root it then restore the backup.
[Nexus 7 (2013) Android Development] Narcotrix:
Just to say "Thanks"

Well, I don't have anything to ask, for once...

My Nexus 7 (2013) was on rooted stock 4.4.2. I did use the toolkit from Wugfresh, everything working as expected... Nothing new, until last night, I noticed a unknown icon in the notifications : "Google announcing an update ! Nice !"

I told the device to install it, it rebooted and ... well nothing happened.

Tonight I tried Wugfresh method 1 from his faq's (you have to read them - short but extreme valuable info in my opinion!!) I followed the instructions and in no time, my device was updated to 4.4.3 & unrooted.

I re-applied root, and now, everything is still there and it works as if nothing ever changed.

Impressive little tool !

Thanks Wugfresh for the development of this excellent piece of software !
[Nexus 7 (2013) Android Development] asish2006:
What exactly will this toolkit take back up of?

Will it take the back up of apps plus data ,songs ,videos ? Anyone ?
[Nexus 7 (2013) Android Development] m+a+r+k:
I just wanted to bring to your attention that your choice of BusyBox Installer (Stericon) failed to install when I updated to Android 4.4.3 and Rooted afterwards.

SuperSu was OK but BusyBox would not install. Trying to install from Play Store also failed giving an incompatible update error.

I tried JRummy Apps Inc. BusyBox Installer and it worked.

Also, the APN backup app doesn't work any more - it doesn't have permission to write a APN file apparently.

Nexus 7 2013 4.4.3
[Nexus 7 (2013) Android Development] WugFresh:
Thank you for the info. I will look into it. If I can reproduce the problem I will develop or integrate another solution.
[Nexus 7 (2013) Android Development] NeoGodSpeed:
Screen Capture

WugFresh

have you had time to checkout screen capture recording to extend time to hours or make it unlimited? instead of 180 sec.
[Nexus 7 (2013) Android Development] WugFresh:
Unfortunately its a restriction that Google explicitly integrated into their adb screenrecord command. You can't enter values above 180.

What I could do however is make an automated scrip that instantly starts recording another 180 sec right after the one before it finishes; so basically you would end up with a bunch of consecutive 180 sec clips. Then you could string them together with some editing software.

Would that help?
[Nexus 7 (2013) Android Development] SnakeFist2005:
Will asus know the bootloader was unlocked then relocked? In case i have to send it in for warranty.
[Nexus 7 (2013) Android Development] mdamaged:
There is no counter, once re-locked, they won't have a clue.
[Nexus 7 (2013) Android Development] SnakeFist2005:
Thanks. Wish HTC did that, no they put tampered on their bootloader lol.

This will be an easy root lol unlock flash twrp and then flash SuperSU thru twrp.
[Nexus 7 (2013) Android Development] mdamaged:
Nexus devices are specifically designed to be developer friendly.
[Nexus 7 (2013) Android Development] :
Still downloads the old build. Latest is here:

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/flo
[Nexus 7 (2013) Android Development] iTchill:
Top notch toolkit ,super easy , great job !!!
[Nexus 7 (2013) Android Development] mertzi:
Hello!

Recently I rarely can download any img-files through the toolkit. I think it only concerns files stored at androidfilehost.com. In the toolkit these downloads only go to 1% then I get an "OK!" and then "mismatch". I don't think it's related to my AV, downloading manually works fine so it's not a big problem, just thought I should report it.
[Nexus 7 (2013) Android Development] marcox92:
New release

try to update : it did not work

try to download : links are crazy and finally got a "chrome bloked the file because it holds a virus !

Help
[Nexus 7 (2013) Android Development] Calabrese1984:
Rooted Nexus 7 2013 (wifi)

About a month ago I rooted my Nexus 7 with twrp recovery using wugfresh's tool kit. That was easy enough. Now that the Update 4.4.3 rolled out, I've been trying to update with no success. I tried undoing and uninstalling Xposed framework, uninstalled anything having to do with that, and I restored factory recovery!

But still keep getting and Error when trying to install 4.4.3!

Some error with an app process, unexpected data in the updated.zip, status 7.

I really need help!!! I just want to put it back to stock totally so I can update normally with no issues!

Please, Any help would be really appreciated!
[Nexus 7 (2013) Android Development] marcox92:
hudge mistake

A bit bothered by peronnal issues I try to relax sitting with my computer and try to change the ROM of my Nexus 2013 wifi

I misclic on the image of the rom and the device was flashed with a wrong file.

I was surprised, no error occurs as my device was not unlocked.

But when the wugs tool kit says restart device, it freezes on "GOOGLE"

I try to boot with power. wol- I had jsut then the opportunity to restart or powwer of

The device is not anymore recocgnized but the PC ?

I red somewhere possibilitées to use Linux to try other tools but better ask her if someone has an idea?

Thanks
[Nexus 7 (2013) Android Development] Hnk1:
You do not need to worry!

Firstly you will need to unlock device in order to run a custom ROM. this tool kit has an option from where you can unlock your boot loader. Try that or you can use adb commands with fastboot manually.

However, I'll suggest you go back to stock ROM and then go for a custom ROM.

If you want to revert back to Nexus 7 stock ROM, you just need to open the wug kit and click on "nexus is soft bricked" or something like that and then choose on revert back to stock . This should work for you. The kit would automatically download all the files and flash the latest build available. Make sure you choose correct device in wug kits while flashing a ROM.

If wug supposingly fails, you can do it manually by downloading Google image and using manual commands to fix your device.

This would fix your nexus. Once fixed, you can put a custom recovery to install custom ROMs.

Be advised, unlocking boot loader would wipe all your data.

If you still are confused or need help, you can just quote me and I'll try to help you with step by step guide.

I suggest you look into the general forum /this thread which would have all the details for your queries.

Good luck
[Nexus 7 (2013) Android Development] marcox92:
Bricked device

Sorry, my english is probably not good enough and my first explanation was confuse

The stage I am after that wrong flash is that device is not rseen by the PC

Wug's tool say 'no divice attached and when I check USB connexions on computer I had nothing.

When I turn on device with Power and VOL - , I have Three options

RESTART Bootloader

Recovery Mode

Power Off

Start

If I choose "Recovery Mode",

Answer is "No command"

this is my hudge trouble !!!
[Nexus 7 (2013) Android Development] Hnk1:
I will try to use as easy English as possible !

Oh it seems fine , I remember in your last post you mentioned your boot loader is locked. YOU CAN'T have custom recovery if you have Locked boot loader. The fact you see no command if you try to boot into recovery shows you still have STOCK(from Google ) recovery which only accepts commands via adb/fastboot manually using command prompt.

WHAT YOU NEED TO DO :

1. UNLOCK BOOTLOADER

2. USE WUGFRESH OR MANUAL METHOD TO FLASH NEXUS IMAGE.

you should boot into BOOTLOADER and may choose restart bootloader. Many commands are given in bootloader. Go into advanced mode/section of wugfresh kit and check "device/phone is in bootloader" and then try to unlock boot loader first and then try to use the kit to flash nexus image to fix it. To confirm you have unlocked boot loader, you will see an unlocked padlock on Google screen / in boot loader your status would be UNLOCKED.

The fact it is booting into bootloader shows you can easily fix it.

OR

Read this for information:

https://developers.google.com/android/nexus/images

TO UNLOCK BOOTLOADER,

1.Download platform tools (fastboot)

http://forums.androidcentral.com/at...9107-how-oem-unlock-galaxy-nexus-fastboot.zip

2. Extract them using winrar

3. Go into extracted folder.

4. Hold Ctrl+shift and then right click in platform tools folder and select "open command prompt here"

5.MAKE SURE YOUR DEVICE IS CONNECTED AND YOU ARE IN BOOTLOADER MODE(POWER+ VOLUME DOWN)

6. Write this command in command prompt

FASTBOOT OEM UNLOCK

YOU ARE UNLOCKED!

FOR FLASHING NEXUS

STEP 1 :

download nexus 7 image from here :

https://dl.google.com/dl/android/aosp/razor-ktu84p-factory-b1b2c0da.tgz

STEP 2:

EXTRACT this file using 7zip or WINRAR. I use winrar on PC

Remember first time when you will extract it, you will get a TAR file. Use winrar again to extract it and you'll get 4-5 files in which one would be flash-all.boot.

STEP 3: Connect your nexus and boot into bootloader by power+volume down .

STEP 4 : ONCE you are in it, just run flash.boot and wait 2 minutes. Ignore warnings on command prompt that file is missing. JUST WAIT .

IF IN CASE YOU ARE STILL LOCKED; above both methods will fail.

Alternatively you can unlock boot loader manually and then use wugfresh ; use wugfresh to unlock and then manually flash image or do both manually or with wugfrwsh. It wouldn't matter!
[Nexus 7 (2013) Android Development] marcox92:
I Understand all your advice but they ALL are based on the fact that the Tools on the PC see the Nexus 7 connected

But in any way i switch it on (recovery, etc..) nothing happens. Device is not visible on the pc.

and any action with Wug ask for the device

How can I make the device visible
[Nexus 7 (2013) Android Development] Hnk1:
I am supposing you have installed adb/boot loader drivers from Google . http://developer.android.com/sdk/win-usb.html

I always have problems installing these drivers on windows 8.

These are apart from normal drivers !

If you have drivers and still you can't seem to find the nexus device, you might need to give it to a tech who knows JTAG. Other than that I think I can't be of help!

However, I strongly still feel your nexus isn't permenantly bricked and you are just leaving an important step or something! With recovery clearly being shown and you can easily boot into boot loader, I don't suppose it can't be fixed by you ....

Try changing cables and USB port you use for connection etc and I hope this works for you !

All the best
[Nexus 7 (2013) Android Development] WugFresh:
+1, basically to recover your device you would use "Flash Stock + Unroot" with "softbrick" mode.

Then follow the instructions. You just need your comp to see your device when its in bootloader mode.

Make use of device manager, plug/unplug to see what comes up. And use the toolkits quick tools "Devices" (fastboot) to check connectivity.

You basically need to follow the driver guide from the steps that just deal with it in bootloader mode. Try different ports and cables.

Unless the actual physical usb port on your device is borked, then you should be able to resurrect it.

Cheers.

{{ WugFresh }}