yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] mskip:
Updated Device module v7.1.8 available for ALL users (Pro and Public)

Changelog:

+Added SuperSU systemless root method for root without modifying system partition

+Added check for latest stock image md5 checksum file after device selection

+Made some changes and improvements to the config module code and main code

Pro users can just start the Toolkit as normal. After you have selected your device you will be notified there is an update available and can auto update. SIMPLE.

Non Pro users have a few extra steps.

IF YOU DON’T HAVE THE 1.4.4 VERSION INSTALLED FROM 15TH DEC 2015 – FIRSTLY DOWNLOAD THE LATEST TOOLKIT FROM http://www.skipsoft.net/?p=1660 TO ENABLE THE SUPERSU SYSTEMLESS ROOT METHOD TO WORK PROPERLY AND AUTO UPDATE THE GOOGLE FIRMWARE CHECK FILE. IF THIS IS NOT DONE YOU WILL BE PROMPTED AFTER SELECTING A DEVICE.

1. Exit the Toolkit if it is open.

2. Run ToolkitClean.exe from the intallation folder (or the Start Menu)

3. Select the device from the list

4. Type ‘y’ or ‘yes’ (without the quotes) to delete the existing module files and settings for the device

5. Restart the Toolkit, select the device and new module files will be downloaded/installed

Note: Steps 1-5 are not needed if you have not selected the device before and not downloaded module files

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) so you get the right code fast.

Enjoy, Mark.
[Nexus 7 Android Development] FallDownTheSystem:
I'm having a problem rooting my device. I flashed it to the latest stock android image available to the 2012 WIFI-only model (Android 5.1.1), which works perfectly fine. I was able to enable to USB debugging and the ToolKit detects the device in adb mode. But when I attempt to root, I always get this message (I've attempted with all 3 root methods).

I can abort and reboot normally. I tried to search anything regarding to "Recovery mode not detected" but couldn't find anyone with the same issue. Any help would be much appriciated.

Edit: Fixed the issue by updating the adb drivers through device manager.
[Nexus 7 Android Development] mskip:
AUTOUPDATE AVAILABLE FOR NEXUS 7 2012 DEVICE MODULE [V7.2.0] 22ND APR 2016 [PRO ONLY]

These are available for PRO users. I will try to update the Public (free) modules next week if I can as I now have to work on adding the Galaxy S7/S7 Edge and Note 5 to the Toolkit. I can then continue updating the Samsung device modules for the latest support.

Changelog:

+Added option to keep existing recovery when flashing stock image to device

+Updated TWRP custom recovery to 3.0.2.0 for booting to/flashing to device

+Various minor adjustments/improvements to procedures

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast.

Mark.
[Nexus 7 Android Development] guri694:
So i fudged up a little bit , need some help.

I have a nexus 7 2012 v5..1.1 build LMY47V (WIFI only version) ,

what happened was that in the device selection i chose no. 45 which was nexus 7 v5.1.1 build LMY47V (GSM version) and done bootloader unlock, root and custom recovery installation.

So now how do i go about it , what will be the problems, consequences and how should i SOLVE this. Do flash CWM and root again under the correct WIFI version selection , is that even doable.

I am sorry for noobing up, but i will kindly appreciate all available help and advice, Thank You.
[Nexus 7 Android Development] mskip:
Update Available for Nexus 7_v1 device module [PRO Users]

Changelog:

+Updated latest STOCK firmware to googles new zip format to download/flash

+Updated everything in Toolkit to work with new firmware zip files from google

+Added much improved Drivers section in Startup [DR] and Toolkit Main Menu

+Improved Root file checker/downloader at device module startup

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy, Mark.
[Nexus 7 Android Development] mskip:
AutoUpdate Available for Nexus7 v1 device module [PRO Users]

Changelog:

+Added option in bootloader menu to check bootloader status and change state

+Fixed device not rebooting back to Android after flashing recovery image

+Updated Basic Toolkit to add latest basic functions for all Android devices

+Added more error control and updated some functions in Main Toolkit

If you want to donate to a device project please do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy, Mark.
[Nexus 7 Android Development] mskip:
AutoUpdate Available for Nexus 7 device module [PRO Users Only]

I had to buy a new laptop and whole new set of programs to make/compile the updates as I lost everything when my hard drive crashed and took out my pc. All this cost me £600 which I had to scrape together and why it took a few more days to get everything done. Updates should come thick and fast now but I have no money left. Im not begging for handouts but if you have ever found the Toolkit useful and want to give back you can send me anything at https://www.paypal.me/mskip. I wouldn’t be saying this unless it was critical and my family and me (and the Toolkit) will be very grateful for anything.

Changelog:

+Updated Toolkit base to 1.6.0. Updated app versions and improved functions

+Toolkit will automatically disable all server pings if they cause any trouble with downloads

+Added direct link to google download site in factory image downloads section

+Improved some Main Menu functions

If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link at http://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy, Mark.
[Nexus 7 Android Development] ride_bmx_mhell:
i got this error,can this be fixed?.?
[Nexus 7 Android Development] mskip:
Impossible to tell whats wrong from an unknown error code..

Did you get a prompt on your device after issueing the fastboot oem unlock?
[Nexus 7 Android Development] mskip:
AutoUpdate Available for Nexus 7 device module [Ultimate/PRO Users Only]

Changelog:

+Updated Toolkit base to 1.6.2 for NEW Ultimate feature. After device selection the Toolkit will update the devices main module to the latest version even if an AutoUpdate is not ready yet. This is extremely useful if an AutoUpdate hasn’t been released in a while or if an AutoUpdate isn't needed but the main module needs updating for up to minute bug fixes/new features. Minimum base version 1.6.2 needed for this to work+Added selection after rooting to help with bootloops if the device doesn’t boot

+Updated some root functions and removed SuperUser by CWM from root relection

+Updated app/file versions to latest

+Fixed some bugs in the main code

If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link *HERE* so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy.
[Nexus 7 Android Development] mskip:
AutoUpdate Available for Nexus 7 device module [Ultimate/PRO Users Only]

Changelog:

+Added completely new safer detection routine for adb/fastboot/recovery modes and integrated it in Toolkit procedures so automatic detection/rebooting works better

+Fixed Autorecoveryscript not working when selecting busybox option [bad zip file]

If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link *HERE* so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode now and unlock ALL device modules for the lifetime of the Toolkit. Follow me on twitter at https://twitter.com/mskipxda for posts/updates.

Enjoy.
[Nexus 7 Android Development] kendallc123:
Yes.

Kendall
[Nexus 7 Android Development] kptnk:
Ok; i reply to myself, but i managed to reboot in fastboot using adb, and fashed twrp...but i still don't know what happened with cwm..?
[Nexus 7 Android Development] nm8:
I am really excited to use this toolkit which looks like it makes life very easy.

I am waiting for new N7 stock to come, apparently this week at my local pcworls/currys/comet.

Will the toolkit still work with the new units?

How do I check my device if the toolkit will work without any problems?

Many thanks and more power to you mskip !!!

edit:

the intended purpose of this device is for my 3 year old (if I'm not using it) who likes to watch youtube and play children's games on it so she wont bugger my Desire HD (she has managed to delete some pics and uninstall some progs on my DHD).

Is there a way to make the unit childproof? Like will not be able to delete and modify files ?

cheers
[Nexus 7 Android Development] BurnRubber90:
I have the same question. Does this works with new firmware and devices?

EDIT: It does work and does it's job pretty darn good. Thanks for the tool :D
[Nexus 7 Android Development] ferris2375:
No you don't.
[Nexus 7 Android Development] Milamber33:
Oh? You know of a privilege escalation exploit to enable an ordinary user to write to /system do you?

Without already having root permissions, you need to flash the files for root through either a custom recovery or Fastboot. A custom recovery requires either root permissions (which you don't have yet) or Fastboot. Fastboot requires an unlocked bootloader. So unless an exploit has been found somewhere, you DO need an unlocked bootloader to get root. You don't necessarily need to keep it unlocked, but you DO need to unlock it.
[Nexus 7 Android Development] PashaK:
For Windows 8 x64 Users

For those of you with Windows 8 x64. To get the drivers working, you need to disable driver signature enforcement.

Go to PC settings, General, advanced settings, restart PC.

Follow prompts to reboot for advanced startup.

then Drivers will work.
[Nexus 7 Android Development] ferris2375:
Why yes I do! Actually no I don't. lol I don't know why I had a brain fart but I could have sworn you didn't need to unlock the bootloader to root. My bad. Didn't think I did on my GS3
[Nexus 7 Android Development] mskip:
Yes I know I did correct myself and hoped noone would pick up on it lol ;)

Mark.
[Nexus 7 Android Development] mskip:
Could you elaborate on this in as much detail as possible so I can add it into the text on the first post.

Or anyone else with Windows 8 that can write down the exact process.

Thanks.

Mark.
[Nexus 7 Android Development] mskip:
On the SGS3 the bootloader is already unlocked before they are shipped so no need to unlock it. On the Nexus devices they come prelocked but are very easy to unlock.

Mark.
[Nexus 7 Android Development] kptnk:
I've done it not later than yesterday and it works perfecty.

You'll find here the instructions i followed :

http://laslow.net/2012/03/14/disable-driver-signature-enforcement-in-windows-8/

Here with screens, (in french) :

http://keeplogeek.over-blog.com/art...u-driver-android-adb-interface-107029647.html

Important for those who wants to install the SDK on windows 8 64 :before installing Android SDK you have to install Java's JDK : install first JDK for x86 AND after x64, unless the SDK installer won't install, considering you haven't it. With both that works.
[Nexus 7 Android Development] nm8:
Hi everybody, I can confirm that the toolkit works well for unlocking boot loader and rooting even on an upgraded stock rom 4.1.1

I seem to have a problem though when installing busybox from the toolkit. There is an error in the end and basically busybox cannot be installed. Another problem is I cannot install CWM from the toolkit, maybe this explains why I cannot do a nandroid backup from the toolkit as well.

I have downloaded and installed ROM manager from the market, but it wont allow me to do a backup nor boot to recovery. All I see is the green robot with a red triangle.

Is there anything I am doing wrong ?

Can anyone please help.

cheers
[Nexus 7 Android Development] dlstaq:
Toolkit 2

Thank you for your work ;)

Option 5 do not work. (Adb checked superuser and present)

After installing CWM Touch the option recovry mode does not work.

If I run the reboot recovry Rom manager it works.

I'm rename files recovry with EFS and it work now

Cdlt
[Nexus 7 Android Development] boost91:
Wow!!! What a great tool you have shared with us!! Thanks so much!! Im so grateful we have such wonderful devs, like yourself, that are willing to share your amazing work with us, and you dont really ask for anything in return. This toolkit was very easy to use, did exactly as described, and could not have been an easier to use. Id like to make a small contribution to you, would you prefer I donate via this site or through the toolkit itself. Thanks again for such an amazing toolkit and for taking the time to make the instructions so thorough and easy to follow.
[Nexus 7 Android Development] flomitdreio:
Hey guys,

i own a mbp 15" and the mac toolkit seems to work not that good. So I thought, this could work for me via a virtual machine with Windows 7.

Has anyone of you a idea if it works, or how it could work???? Otherwise i would have to borrow a laptop - but I would like to do that on my mac..

Thanks:D
[Nexus 7 Android Development] Janzomaster:
Hi,

not sure if it's metioned somewhere, couldn't find it in the first post: on Win7x64, I had to change the connection-protocol from MTP to PTP for ADB to work.
[Nexus 7 Android Development] nm8:
hiya, maybe that is why some options on the toolkit don't work. How do I do that please.
[Nexus 7 Android Development] Janzomaster:
When you connect your device via USB, choose camera mode in the connection mode - that's PTP. Standard is media device = MTP
[Nexus 7 Android Development] mskip:
AUTO UPDATE AVAILABLE TO V2.1.0 (28TH AUGUST 2012)

Changelog:

+Added latest TRWP Recovery 2.2.2.0

+Added root/unroot section with new options

+Added cwm unroot file for quick unroot without flashing Stock Rom

+Added cwm root option to flash Superuser or SuperSU

+Added 'Auto Update' check in Settings Screen

+Added uninstall batch file for clean uninstall

+Checked entire code and made edits to parts where needed

Full version will be built and released at the end of the week.

Enjoy :)

Mark.
[Nexus 7 Android Development] tucstwo:
never mind. found it on last page
[Nexus 7 Android Development] nm8:
thanks, just done and installed Rom manager, but I always had to flash CWM recovery before booting the N7 to CWM recovery mode, otherwise the N7 will noly boot to stock recovery with the robot with a red triangle. But there was an option in CWM to remove the stock recovery which solved the problem.

====================================

EDIT:

I just found out that the above scenario is what OPTION 5 in the utility is for.....

========================================

Just done a NANDROID backup using the utility, I thought my sytem hang as it took ages to pull the backup to the PC, but hey! patience is a virtue. It might be worth mentioning this in the utility @mskip.

===================================
[Nexus 7 Android Development] rkanwar:
OK I'm a total noob at the nexus 7... I read through the thread but the answer wasn't clear to me. I can root without unlocking my boot loader? And by using this toolkit? From what I've so far understood from the answer a few pages back is that I can root without unlocking the boot loader but not with this toolkit?

And what exactly voids the warranty? Rooting or unlocking the boot loader or both?

Thanks guys
[Nexus 7 Android Development] Milamber33:
No, you CANNOT root without unlocking the bootloader. Unless some kind of privilege escalation exploit is discovered, this will not change, no matter which method you use.
[Nexus 7 Android Development] rkanwar:
OK thanks. So either way warranty is void?
[Nexus 7 Android Development] kendallc123:
Yes, your warranty is void after unlocking the boot loader and rooting

Kendall
[Nexus 7 Android Development] yeoldeusrename:
Can you mention this in the OP please??? Took me forever to find this info (although if I'd just checked the second to last of this thread I would've seen it :)).

Thanks Janzomaster and nm8. And mskip of course. :)
[Nexus 7 Android Development] 3vo kid:
Can I unlock and root even tho my build # is JRN84D?

Sent from my Black "Destroy Mode" N7
[Nexus 7 Android Development] mskip:
Yes your warranty will be void if you unlock the bootloader or mess with your nexus 7 but its quite easy to flash a stock rom back and relock the bootloader which will put your tablet back to a FULL warranty state again.

Mark.
[Nexus 7 Android Development] mskip:
JRN84D is still a 4.1.1 build which means you can still use the ToolKit to do anything you want to do.

Mark.
[Nexus 7 Android Development] 3vo kid:
Thank you :D

Sent from my Black "Destroy Mode" N7
[Nexus 7 Android Development] demandarin:
I need to manually put google stock image into appropriate directory. My desktop is a dinosaur and has no wifi..lol I already downloaded stock image to my phone. So I will just transfer it to my pc. what folder or Directory do I put it in so your toolkit will properly flash it? Then once thats done, ill use your kit to relock boitloader.

I do have another toolkit that comes with stock image included but IM more familiar with your setup. so id rather use your toolkit since it got me out of jams before.
[Nexus 7 Android Development] jastonas:
Tried to flash Google Stock Image and now it's stuck on "sending userdata (137526 kb)"...

Tablet is on fastboot and vol up/down aren't working.

How safe would it be to try to power off and on by holding power button?
[Nexus 7 Android Development] demandarin:
Another quick question, if IM already running stock ROM w/ motley kernel, is it neccessary for me to gave to flash complete stock img(check my previews post). Couldn't I just flash stock kernel back, then use tool kit to unroot, then toolkit to relockbootloader instead? or is stock img. Needed to get stock recovery back?

Just trying to see which would be better/faster option to get back complete stock to send device in.
[Nexus 7 Android Development] kendallc123:
Don't quote me on this but I think you might be able to flash the stock kernel again, then use the toolkit to flash the stock recovery, unroot and lock the boot loader. I'm not sure that would work, just something I thought of that you could try

Kendall
[Nexus 7 Android Development] bowser001:
same thing happened to me. just hold volume up, volume down, and power till it begins to power up.
[Nexus 7 Android Development] mkdr:
So Ive rooted my Nexus 7 with the latest toolkit, and I wanted to replace SuperUser with SuperSu. How do I do it without any issues? Can I just install SuperSu via the play store and uninstall SuperUser, or first have to uninstall it and then install SuperSu via the market, or is there another way I have to do it? What's with the apps SuperUser already granted access, could this lead to problems now switching to SuperSu?

---

I just installed SuperSu over the market, opened it, and deleted superuser.apk from /system/apps. Was there anything wrong with that? Should I move the supersu apk to system apps too like superuser was a system app?
[Nexus 7 Android Development] mvmacd:
As long as you opened SuperSU first before deleting superuser.apk, and it said "/bin/su binary needs updating.." and then a confirmation that it updated the su binary [with supersu's binary, instead of superuser's binary], then you are fine.

However, if you uninstall supersu now, I do believe you will lose your root. It's not a huge deal, you just download the superuser CWM zip and flash it in cwm/twrp, and presto, you are back to superuser root, and you can again install supersu and then get rid of superuser.

If you ever want to remove supersu, first download the other root program [i.e. superuser, except I doubt you'll be going back :laugh:], and launch it, and let it update the binary first. After that you're free to remove supersu.

And about making supersu a system app.. I am not 100% sure, but I believe that's fine. But if you do it and it fails, don't blame me if you gotta flash superuser.zip in cwm/twrp to regain root! :P
[Nexus 7 Android Development] Datron:
I'm still only halfway through this thread, but wanted to bump this solution since it plagued me and a friend for a few days. It's very simple but can be frustrating.

Thanks Skip for the support.
[Nexus 7 Android Development] marcox92:
LittleHelp

Have installed Toolkit and drivers.

For future ROM update, have I ti S-OFF the device, and How ?

Just tell me if Toolkit can do that or if I have to look on an other Forum ti achieve it.

Thanks
[Nexus 7 Android Development] tommykwan222:
hey, if I use this toolkit to unlock my nexus 7, is it possible to get back the warranty ?

thanks
[Nexus 7 Android Development] flomitdreio:
Yes, you can allways relock your Device, like nothing ever happend....;)

Relock bootloader, unroot, stock rom and stock kernel - no problem and no difference if you use the tool or not.
[Nexus 7 Android Development] mkdr:
I wanted to get into CWM yesterday so I shut down my Nexus and triggered PoweOn+Volume up+down until it went on with the menu, I selected recovery and pressed start. And then my Nexus got stuck in the Google boot image, it doesn't do anything from there anymore. I got really worried because pressing poweron/off didnt do anything, connecting usb cable didnt do anything too. I googled for it and found another forum post somewhere that this seems to be a known bug since months (that it's just safe to get into CWM when you trigger it from Android itself via ADB), and I got lucky, because pressing poweron/off+volume down/up for like 10 seconds did reboot my device...

Maybe you could write this somewhere on the intro page or, isn't there a fix somewhere for this? I mean, it's really bad if it get's stuck there and you can't do anything/don't know what to do. You can't even pull out the battery that easily I guess, isn't it pasted over with a paper?
[Nexus 7 Android Development] joelhon:
I can't run this Toolkit.exe on my computer. I have read the first post, and nothing pops up saying it is not allowed, nor does it remove any files afterwords. It just pops up and quickly disappears.

P.S. 8HC49927R60127213
[Nexus 7 Android Development] mvmacd:
You did not get 'lucky,' holding the power button for 10 seconds is how you stop an unresponsive Nexus 7, and most people should know that's how to turn it off if you get stuck.

Also, yes, CWM has a bug, it only seems to work when you have it plugged into a computer when you select "Recovery," from the bootloader.

What I recommend is getting TWRP, it seems to work much better for me.

And yes, you need to get ROM Toolbox, and use the "Rebooter -> Reboot Recovery," unless your custom ROM has "Recovery" in the reboot menu.
[Nexus 7 Android Development] mkdr:
So TWRP doesn't has this bug, you can start it without a cable connected, or is this issue with the bootloader itself? Can I just install TWRP over CWM, like for xample using this guide here or do I have first to deinstall CWM or do something else?