yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] mskip:
UPDATE

V4.0.0 is finished and undergoing testing so unless there is a disaster it will be released tonight and posted in the 1st post.

The toolkit will support both si-fi and gsm models upto and including the latest 4.2.1 build and I have added some extra stability to the root routines to hopefully fix some peoples problem with rooting. The addition will basically look for and remove any previous root files if found which is what I think is causing problems as the people who cannot root via adb seem to be rooting fine via recovery. The only difference with the recovery files is the deletion of previous root files.

I have also added adb sideload rooting/unrooting ability and alot more things I wont go into now.

Keep refreshing tonight or look for a twitter or g+ post when released.

Mark.
[Nexus 7 Android Development] mskip:
Ughh trust you to spot something that hasnt been mentioned in about 5 months lol.

I was just about to upload V4.0.0 with exactly the same mistakes so I had t ogo and change everything before you pulled me up on it again :p

Thanks for the catch :)

Mark.
[Nexus 7 Android Development] Harkunwar:
ohh lol :D. Upload fast. Need to root my tab :\
[Nexus 7 Android Development] mkdr:
My N7 wants to install a ~1MB OTA update, will that brick my device if it's rooted and already on 4.2.1?
[Nexus 7 Android Development] bostonbassman78:
Backup your root with voodoo root keeper and no it shouldn't brick it at all may lose root if u don't backing up

Sent from my Paranoid N7
[Nexus 7 Android Development] mskip:
GOOGLE NEXUS 7 TOOLKIT V4.0.0 [5TH DEC 2012] RELEASED!!

ChangeLog:

ToolKit v4.0.0 (5th November 2012)

+Added support upto JB 4.2.1 for wi-fi only model

+Added support upto JB 4.2.1 for gsm/hspa+ model

+Updated SuperSU to 0.99 (thanks to chainfire)

+Added stability to all root routines (any previous root files are deleted before root is installed)

+Updated cwm Touch Recovery to 6.0.1.9 (adb sideloading supported)

+Updated twrp Recovery to 2.3.2.1

+Added option to install root files via adb sideload in recovery

+Added (are you already unlocked) question to 1-CLICK for quicker run time

+Added all google images to download/flash section (uploaded to my goo.im developer page so they wont be broken)

+Added choice to format/leave userdata partition when flashing google image

+Added boot Stock Recovery to boot options

+Updated version checker to work on future updates

Lots and lots of updates and improvements to this version.

Enjoy :)

Mark.
[Nexus 7 Android Development] nava88:
Only for install? I cant see it in the autoupdater
[Nexus 7 Android Development] TheByteSmasher:
Yay you!:D
[Nexus 7 Android Development] Milamber33:
Hopefully that will shut up all the idiots who have been complaining about the whole donation for auto update thing, at least for a while.

Thanks Mark, your work is much appreciated. :)
[Nexus 7 Android Development] mskip:
Auto Updater is live now.

Mark.
[Nexus 7 Android Development] mskip:
I really dont care about it anymore mate its the way I work, it's the fastest way by far of releasing updates and it wont be changing.

You can't make everyone happy no matter what you do I just hope some people find my work useful :)

Mark.
[Nexus 7 Android Development] bostonbassman78:
I absolutely love your work this has made everything so simple my six year old daughter could do it :D

Sent from my Paranoid N7
[Nexus 7 Android Development] Milamber33:
... Not sure I would let a 6 year old do this sort of thing with a phone worth hundreds of dollars. :p
[Nexus 7 Android Development] bostonbassman78:
I wouldn't really let her but i was just saying ya know but on another note you would surprised at how easily this girl can run all my devices like she has owned them for years lol

Sent from my Paranoid N7
[Nexus 7 Android Development] yanksrock1000:
Huh...kinda strange. I downloaded v4.0.0, and then my computer became painstakingly slow, then my Norton Anti Virus deleted it because it was a "risk"....not sure why.
[Nexus 7 Android Development] Milamber33:
There's your problem. I'm a computer technician, and roughly 9 out of 10 computers I deal with that get a virus on them have Norton. You're better off with literally anything else. Even McAfee is better than Norton, though it's the other 1 out of 10 that gets a virus on it.

Bottom line, either get yourself a real antivirus product, or at least get rid of Norton and use Microsoft Security Essentials. It does a better job.
[Nexus 7 Android Development] 08G8V8:
I went from stock 4.2.1 and went through the process to unlock, root, and flash CWM. Bootloader is unlocked, I have root access. When I boot into the fastboot mode and click up to select recovery and hit the power button, it goes to a screen with the Android guy on his back and a red triangle with the ! in the center.

I went back into the toolkit and re-flashed CWM recovery, and after it said it completed sucessfully, before I unhooked the tablet from my computer, I selected recovery and hit the power button, and it DID go into CWM so I figured I was good to go, so I picked the reboot option.

I shut down the tablet, booted into fastboot mode again, selected recovery and hit power and I get the same Android guy on his back and red triangle.

What am I doing wrong?

On my Samsung GS3, I hold the volume up and power key to get into CWM recovery. I tried this on the Nexus, but did nothing. I held both volume buttons and power button, and also did the down volume and power button, and get to the fastboot mode but get the same end result when trying to select recovery.

Please help. Thanks
[Nexus 7 Android Development] Milamber33:
What's happening is that you haven't deleted or renamed the recovery restore files (option 5), so every time you boot into Android, it's wiping CWM and restoring the stock recovery.
[Nexus 7 Android Development] 08G8V8:
I was wondering what "rename" option was for. I was going to do the #8 1-click option, but wasn't sure about the "rename" portion of that option.

So, I need to go back into the toolkit and perform #5 to do the rename, then do #6 to flash CWM?

Is that the correct steps?

THANKS!
[Nexus 7 Android Development] Milamber33:
Yes.
[Nexus 7 Android Development] 08G8V8:
Got it. Thanks so much. Time to go to bed and will flash CleanRom tomorrow. This set me back tonight, but glad I got it resolved.
[Nexus 7 Android Development] Milamber33:
Ironically, I believe CleanROM already has the recovery restore files removed, and it certainly has root already applied, so you could have saved yourself a lot of the work you did today by just flashing straight to that as soon as you unlocked the device.

On the other hand, it's a good learning experience to go through everything the hard way at least once. :)
[Nexus 7 Android Development] 08G8V8:
Yeah, I am definitely a rookie at this stuff. I was just sort of following the steps I needed to do on my GS3.

The red triangle did freak me out at first, but felt better when it let me reboot without it being bricked.

Definitely time for bed. I still have a lot of reading to do on here, so and there is SOOOOO much to read. Will pick it up tomorrow.
[Nexus 7 Android Development] smt8544:
Just to clarify, 8gb Wi-Fi Nexus 7's are now incorporated in the 16/32gb Wi-Fi device category, correct?
[Nexus 7 Android Development] Milamber33:
The toolkit doesn't care about the amount of storage, just whether it's wifi only or 3G. So yes.
[Nexus 7 Android Development] mskip:
Sorry I totally forgot there was an 8GB wifi model lol I will add it to the top of the first post but as milamber said it doesnt matter about the storage as the model is supported.

Mark.
[Nexus 7 Android Development] Krunk_Kracker:
I've used AVG free for 10 years with no issues, best AV on the market.

I'm a Network Admin with the same amount of professional experience as well.
[Nexus 7 Android Development] PCWright86:
Is there anyway i can get a mirror of this. I am on a work pc and it wont download from mediafire. thank you
[Nexus 7 Android Development] sstanton86:
hey guys..

Decided to root my nexus 7 yesterday, it all worked ok. Anyway, kept getting errors etc, after flashing custom rom. So I decided to flash stock image, and remove root... Everything seemed to be going ok, but now I can't boot up, it says ''Booting failed''. I've tried step '9', flashing stock image, it downloads the file, I then click continue, and it says failed throughout all the processes. IT JUST WONT WORK!

I've tried going back into Recovery, wont work either, says the same thing ''booting failed''. I'm a bit stumped.. I would have thought flashing the stock image using the toolkit would be fairly fool proof - it probably is - but I'm stumped as to what or how I went wrong?!

Any help would be much appreciated1:crying::crying:
[Nexus 7 Android Development] Jolest:
November? :)
[Nexus 7 Android Development] dondagun:
Hi, I have a newly purchased Nexus 7 on 4.1.1 (JRO03S) OTA updates are failing. Cleared the google services frame work still failed, tried adb side load update for JRO03S to 4.1.2 that also failed. What is my best option with toolkit for getting this resolved?
[Nexus 7 Android Development] dondagun:
it is stock. Can I just flash the 4.1.2 stock recovery over 4.1.1?
[Nexus 7 Android Development] HFX9:
When i root my nexus7 wifi 16GB with android 4.2.1, then i look on error message "too many links" and all faild

Help me anybody?

Here is screen:
[Nexus 7 Android Development] dondagun:
ok so I flashed 4.1.2 with toolkit and now it rebooted to "type password to decrypt storage". Can someone assist?

---------- Post added at 10:23 PM ---------- Previous post was at 10:03 PM ----------

Ok so I put it into fastboot selected recovery then wiped the Nexus and everything is A OK! Off to relock bootloader.
[Nexus 7 Android Development] dyepnoodle:
i just got my nexus 7 and its already 4.2.1. can use this tool to unlock and root it?
[Nexus 7 Android Development] kendallc123:
yes
[Nexus 7 Android Development] rkuijpers:
Yes you can, it's the easiest way to do it! :)
[Nexus 7 Android Development] bostonbassman78:
Did u install the drivers first then make sure u could see your devices serial # in the top left of the toolkit?

Sent from my Paranoid N7
[Nexus 7 Android Development] ThurstonX:
Trying to restore a NANDROID backup

I have TWRP installed. When I use the toolkit option to restore a NANDROID backup, it gets pushed to the N7, and I'm taken to TWRP, but I can't figure out how to restore from there. If I go to RESTORE, there's nothing listed. Do I need to somehow use CWM to restore it? What's the value of using TWRP in conjunction with the toolkit, or is there any value?

Made the mistake of going through the steps again, thinking the toolkit would see that it had already pushed the backup folder to the N7. Nope. Pushing it all again. *sigh*

Any advice on how to restore a NANDROID backup when I've got TWRP installed?

Thanks.

---- EDIT ----

Tried booting into CWM Recovery without flashing it. When I tried to Restore it returned "No files found"
[Nexus 7 Android Development] mskip:
Shushh I meant December lol :p

Either that or im a time traveller and im a bit lost ;)

Mark.
[Nexus 7 Android Development] mskip:
That message is a very strange one as it has happened to all different devices for no good reason. It even happened to me once.

No threads started for help have ended with a definitive fix and noone knows why its caused.

I think I fixed it by either changing usb ports or rebooting the tablet and rebooting the pc im not sure which. I dont think its driver related and its definitely not toolkit related so my only advice is to try the above fixes or just keep trying and it should fix itself.

Mark.
[Nexus 7 Android Development] mskip:
Just download the 4.2.1 image and flash it using option 9 in the main menu.

Mark.
[Nexus 7 Android Development] mskip:
I will upload it to dev-host and post the mirror in the OP. Should be there in 30 minutes.

Mark.
[Nexus 7 Android Development] mskip:
GOOGLE NEXUS 7 TOOLKIT V4.1.0 AUTO UPDATE [7TH DEC 2012] AVAILABLE!!

Changelog:

+Added adb sideload (install) any zip file via recovery feature to main menu

+Added set permissions to 644 for 720p camera mod

+Minor bug fixes

Enjoy.

Mark.
[Nexus 7 Android Development] ThurstonX:
So no one has any clues as to why a NANDROID backup made with the toolkit is unavailable for restoration?

--- EDIT ---

This may be the cause of CWM not seeing the backup:

In CWM Touch, if I try to mount /sdcard, it does not. If I mount /system (the only other thing that's not already mounted), it mounts it. Since the clockworkmod/backup/ dirs are under /sdcard, it stands to reason that is why I get the messages:

Couldn't open directory.

No files found.

Make sense? And, more importantly, any solution??
[Nexus 7 Android Development] Gster09:
Thanks for your work on this Toolkit Mark, it's truly appreciated.

My wife has the WiFi 16GB N7. She's on 4.1.2 with stock bootloader (re-locked), and CWM 6.0.1.0 recovery. She has a good amount of data and customization on it, where she would rather not have to resort to restoring backups if she can avoid it. So my question is this.. If she takes the update (which I guess will bring her to 4.2.1), can she retain or re-flash root and custom recovery without unlocking the bootloader again?

My first step for her was going be installing SuperSU from the Play store so that it can play nice with 4.2 and then take the update, but if there is another way I should approach it, I would rather err on the side of caution with her tablet. Mine, I don't care! I can always start from scratch and redo it all, but she's not one to enjoy the process, she just wants the results. :)

I apologize if this has been answered in the forum, I looked and couldn't tell for sure. Thank you.
[Nexus 7 Android Development] ThurstonX:
bug report

Well, I solved the mystery of why CWM Touch couldn't restore my NANDROID backup. It wants the folder in /data/media/clockworkmod/backup/

After making a backup from within CWM Touch, /data/media/clockworkmod/backup/ was created, owned by root:root and set to 777, including all files within the specific backup directory. I then used the toolkit to push my backup folder to /data/media/clockworkmod/backup/ BUT the set permissions action the toolkit tries to do does not happen (I tried 777). All my pushed files remained as 600.

I opened an adb shell, su'd, and set the permissions manually. Not sure if that's needed to do a restore, but to keep all CWM backup files consistent, I did it.

NB: turns out it's not required to change the permissions. I tried the second restore without manually chmod'ing them to 777. 600 seems sufficient, probably because the restore runs as root, and root:root is the owner/group.

Finally, I booted into recovery, was able to see both backups, and was able to restore my original backup.

So the two bugs are:

1. the Restore a NANDROID backup option should push the backup folder to /data/media/clockworkmod/backup/

2. the file permissions are not set correctly [though not needed for the restore to work]

HTH.

One question, for future reference. You mention that the 1-Click option will ask if the device is already unlocked. I didn't see it near the beginning of that process, so I backed off and did each install manually. Where in the 1-Click process is that question asked? I did see it when I was just rooting.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I should also note that restoring a 4.1.2 backup over a 4.2.x running install resulted in the /sdcard/0 dir still being there, fully loaded, and some things being broken. In the end I flashed the 4.1.2 Factory Stock ROM, re-rooted, re-flashed CWM, etc., and then restored the NANDROID... again. Lesson learned.

Sure wish CIFS would work under 4.2.x, but until there's a rock solid method, or apps adapt, I'm sticking with 4.1.2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EDIT

-------

Hmmm, not sure why, but after going back to the stock ROM and running the CWM backup, this path exists:

/sdcard/clockworkmod/backup/

and the backup folder I pushed to /data/media/clockworkmod/backup/ is also listed under /sdcard/clockworkmod/backup/

Maybe it's a symlink, not sure. But I know for sure that when the toolkit restore NANDROID option pushed that folder to /sdcard/clockworkmod/backup/ CWM Touch recovery could NOT see it. All seems like a big CF, frankly. Thankfully there are manual workarounds.
[Nexus 7 Android Development] mskip:
If you already have root then try installing root keeper from the play store which should retain root after an update and not require you to unlock the bootloader.

Mark.
[Nexus 7 Android Development] djsiva:
Did the mirror ever make it to dev-host? I'm at work too and cannot download from mediafire.
[Nexus 7 Android Development] mskip:
A mirror to Dev-Host for V4.0.0 has been added to the first post.

http://d-h.st/j7s

Mark.
[Nexus 7 Android Development] rnclock:
Mark,

Updated and my mods version went from 2.3 to 2.4, even though you did not update that. When I recheck it shows current mod at 2.4, and available mod at 2.3. Just want to make sure I don't miss an update when it finally goes up a version. Thanks for all the hard work you put into.
[Nexus 7 Android Development] peja_:
hey, i was wondering one thing - if my device was already rooted, and then i updated it (to 4.2.1) - is it ok to just rerun the root tool? (cause i lost root)

is that the right thing to do it? just rerun it?
[Nexus 7 Android Development] doncaruana:
Not that I mind donating because there's obviously a lot of work here, but is the only way to get 4.1.0 to use auto updater from the donate version? All the links are to 4.0.0.
[Nexus 7 Android Development] rnclock:
Yes, for the quickest way to get it. Or you can wait till the main post is updated with the newest version available. This could take some time though.
[Nexus 7 Android Development] mskip:
The permissions setting for the 720p mode pushed the modssection version to 2.4.0 but I forgot to update the version number in the update checker so everything is fine and I updated everything accordingly. Thanks for the catch.

Mark.
[Nexus 7 Android Development] mskip:
Yes it is. Theres not enough updates and they arent important enough to warrant a full update and I have 3 other toolkits im updating right now.

Mark.
[Nexus 7 Android Development] mskip:
Yes its fine.

Mark.
[Nexus 7 Android Development] yanksrock1000:
I was stuck on 4.1.2 and it would not update. I was not sure what to do, and have never really done any modifications to the tablet. I used your tool, and it was easy! I am now living happily with 4.2.1! :D thanks alot

One question! Now that I have everything all set and done, should I relock my bootloader? Will anything bad happen if I keep it unlocked?
[Nexus 7 Android Development] ThurstonX:
Personally, I keep it unlocked. Doesn't affect OTA updates, and makes it easier to re-root if you lose it, or to root for the first time, if you never have but want to. Voodoo OTA Rootkeeper might save your root, too, but no reason I know of to re-lock the BL. I'm also pretty sure somewhere in this thread Mark mentions that he agrees with me ;)

Here's an excellent post that explains a few basics:

http://xdaforums.com/showpost.php?p=28387895&postcount=9
[Nexus 7 Android Development] mskip:
Yes I do agree with you (or did I say it first and you agree with me?).. :)

The most important reason to keep your bootloader unlocked is that if your boot image ever becomes corrupted and your phone goes into a bootloop then the only way to fix it is to reflash a stock boot image back to your device. This is very easy if you have an unlocked bootloader and won't affect your system or Internal Storage at all. If however you have a locked (or relocked) bootloader and the same thing happens then the only fix is to unlock the bootloader first which means your system will be wiped and everything in your Internal Storage will be lost. This happened to someone who had pictures/videos of his newly born child on his phone but he had relocked his bootloader after rooting. He lost everything.

Enough said I think :)

Mark.
[Nexus 7 Android Development] ThurstonX:
LOL. Of course I was just parroting what I read in your post somewhere in here :)

Great point about the bootloop. Hope I never have to recover from that, but good to know it's relatively painless. Thanks for the lesson.
[Nexus 7 Android Development] yanksrock1000:
Thanks a lot! I will keep it unlocked :D
[Nexus 7 Android Development] mskip:
Wise decision my friend ;)

Mark.
[Nexus 7 Android Development] Fr3d_:
Thanks!

Just bough my Nexus 7, your tool (and this post) was really helpful. Just thanks! :D
[Nexus 7 Android Development] tucstwo:
Um, Help? I go for the update and it hangs on this page? Any ideas?
[Nexus 7 Android Development] superleeds27:
Ive found myself in aloop! well a device thatwont boot into CM.

Im currently downloading a Stock image using the program. If I flash will I lose all my items on internal storage? (Bootloader is unlocked)

---------- Post added at 10:54 AM ---------- Previous post was at 10:35 AM ----------

Also, how long does it take normally to 'send' recovery.

Seems to have been sat on that for a while :/

sending 'recovery' 6530kb
[Nexus 7 Android Development] mskip:
It only takes a few seconds to flash recovery so if its taking a while just reboot back to fastboot (keep holding vol up vold down and power until it reboots to fastboot) and try again.

If you are using v4.0.0 onwards then I have added the option to not format userdata before flashing the userdata partition so nothing will be wiped if you choose that.

Mark.
[Nexus 7 Android Development] mskip:
Close the toolkit and try again.

Mark.
[Nexus 7 Android Development] girkev:
Interchanged Factory Images Wifi vs GSM

Unfortunnately I flashed my Nexus7 WIFI with the wrong GSM factory image!!

No boot any more.No recovery mode. No ADB mode.

Is this the end? Or ist it possible to fixi it somehow?

I´m grateful for any tips and hints.
[Nexus 7 Android Development] Datron:
I shower you with xda thanks clicks and real donations, my friend. You are the wizard. Seriously.

Unclefest v2 alive and kicking - support SeanZ!
[Nexus 7 Android Development] Milamber33:
No, it's not the end. Put your device in Fastboot mode (Vol Down + Power to switch it on, from memory), and you should then be able to use the toolkit to flash the correct factory image. This will fix everything up.
[Nexus 7 Android Development] girkev:
:good:worked fine.

You made my day!
[Nexus 7 Android Development] DarkSorcerer:
Hi,

It worked perfectly on my Nexus 7 3G. Thank you, mskip!

Regards,
[Nexus 7 Android Development] Etilas:
Sorry for my bad english but i don't find the answer i need:

If I use this kit on my 4.2.1 N7, can I root it? Must I unlock the bootloader? So will i lost all my data?

May I find a n7 axtly like before (but rooted...) if I Backup and restore after?

Thanks
[Nexus 7 Android Development] ThurstonX:
Rooting requires unlocking the bootloader, and unlocking the bootloader will wipe your N7. The toolkit should allow you to back up some things before unlocking the bootloader. Sorry, I'm not sure what, exactly, but read the first page of this thread. I think it's explained there.

Hope that helps.
[Nexus 7 Android Development] Datron:
+1

Back up all your apps and stuff using the toolkit. Then root. Then restore.

Unclefest v2 alive and kicking - support SeanZ!
[Nexus 7 Android Development] dudumomo:
Bricked?

Hi there,

It looks like I've bricked my Nexus7....

I've used this script to install adb then to root it (in fact, I choose the option 8 to do all.

But finally, it looks like I did not install adb correctly i guess as the tablet didn't wanted to go into fastboot mode. So I stopped it myself to reboot it and try (Which was stupid I guess as know I cannot access to anything. Doesn't want to boot and cannot access to fastboot)

What sould I do ?

Thank you !

EDIT: Wow....It was not bricked in fact...I had to press several times the power button to make it boot...weird !

And it is working well now.

Pheww !

Very nice toolkit ! Thanks !