[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 7 - Drivers, Root, Recovery + MORE

Search This thread

3XTR3M1ST

Senior Member
Mar 17, 2011
101
7
I'm using Unified_Android_Toolkit_v1.3.3 and trying to flash the nakasi-lrx22g-factory-2291c36b.tgz (L 5.0.2?) on my nakasi device, somehow this error happens despite multiple tries. almost half a year ago i think i've used Google_Nexus_7_ToolKit_v5.0.0 or Unified_Android_Toolkit_v1.2.0 to flash 4.4.2 on the same device and it was successful.

Is the new toolkit of factory image the problem?

WgxhGmI.jpg
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
I'm using Unified_Android_Toolkit_v1.3.3 and trying to flash the nakasi-lrx22g-factory-2291c36b.tgz (L 5.0.2?) on my nakasi device, somehow this error happens despite multiple tries. almost half a year ago i think i've used Google_Nexus_7_ToolKit_v5.0.0 or Unified_Android_Toolkit_v1.2.0 to flash 4.4.2 on the same device and it was successful.

Is the new toolkit of factory image the problem?

WgxhGmI.jpg
The google image on the google download site is faulty, flashing the bootloader causes your problem. I have repacked the 5.0.2 image with a fixed bootloader which works perfectly.

The latest device module for the Nexus 7 2012 model has full 5.0.2 support and can download/flash/root without any problems. Pro users can autoupdate to the latest version but if you want the fixed google image for 5.0.2 you can download it from http://www.skipsoft.net/?wpdmpro=nexus-7-wifi-2012-nakasi-android-5-0-2-lrx22g-fixed and flash it as normal via the Toolkit. IF you do not have the latest device module version you will get an unknown md5 check error but you can carry on and flash.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
AutoUpdate available to add FULL 5.0.2 support with fixed google stock image (Pro Users)

+Added FULL support [including root] for Android 5.0.2 LRX22G
+Download and Flash stock 5.0.2 LRX22G stock image directly from Toolkit
+Fixed Apps Backup procedure not starting in Backups section

Mark.
 

ks2

Member
Aug 6, 2009
10
0
hi,

I get "Access denied. " when trying to download from the skipsoft page. whats wrong?

KS

edit: 11 pm, now the site is working
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
TOOLKIT UPDATE
-New functions added to the root section [new rooting options for root and unroot],
-More text added to various sections,
-Text added to the Factory Image Download/Flash section to help recovery from a bootloop/device not booting properly,
-Fixed apps backup routine not starting when selected,
-Fixed push/pull and sdcard backup routines for Lollipop as Android 5 has problems communicating with the sdcard without root,
-Fixed the unroot zip file and added stock recovery to the routine to make the device fully compatible with OTA updates,
-OTA Updates can be sideloaded via stock recovery using the Toolkit (unroot first though),
-Toolkit always updates to latest SuperSU version from Chainfire.

I will push AutoUpdates for all Nexus devices within the next few days to make it easier to update but for users without the Pro Version (I urge you to donate if you use it/like my work as I won't be able to keep it going much longer without your support) you can do the following:
In the Tools folder delete the tkmainNexus7.exe file (this will trigger new device files to be downloaded at startup)
Download the updated unroot zip file from http://skipsoft.net/download/fileupdates/Unroot-UninstallBusybox-CwmManager.zip and move it to the root folder (overwriting the original)
Start the Toolkit, select your device and enjoy.

I am currently working on adding a OnePlus One Toolkit device module. Once that is finished I will build a new Toolkit and you will be notified on startup that a new version is ready to download directly via the Toolkit (if using UAT base 1.3.3 or later).

If anything doesn't work properly please let me know in the thread or at [email protected] so it can be fixed. I do test as much as I can on most devices but i'm not perfect

Mark.
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
AutoUpdate available for Nexus 7 2012 device module

+Added FULL support [including root,recovery] for GSM model [nakasig] Android 5.0.2 LRX22G
+Download and Flash stock 5.0.2 LRX22G stock image for GSM model [nakasig] directly from Toolkit

I will update the public device module with the next Toolkit update (when the OnePlus One is added).

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
UPDATE TO DEVICE MODULE FILES

I have updated the device module to add new support and updates to the main toolkit, If you have installed the Toolkit in the last few days then you will already have these new files but if not you can easily update these new files:

Just go in to the tools folder and delete the config*.exe file (where * is your device name, eg nexus5, nexus6, nexus7, nexus10). Run the Toolkit and select the device from the list and new device module files will be downloaded.

You can go to http://www.skipsoft.net/?page_id=1203 to check what support is available for your device.

I am now working on adding 5.1 support (with automation for downloading/flashing the stock image to your device) and this should be available in the next 2 days.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
AutoUpdate available for Nexus 7 [2012 edition] Toolkit module

+Added FULL support [including root] up to Android 5.1.0 LMY47D
+Added Android 5.1.0 LMY47D stock image to Download/Flash section
+Download, Flash and root up to 5.1.0 LMY47D directly from the Toolkit
+Fixed unroot zip file and added stock recovery to unroot routine for OTA updates
+Updated TWRP recovery to latest version [for booting/flashing to device]
+Separate [older] TWRP with working adb for sideload/openrecoveryscript use in Toolkit
+Updated Tar Creator procedure to Auto Detect image types and convert all at once
+Updated burrows apps Root Checker app [installed via Toolkit] to v3.73
+Updated mdroidapps Easy Backup/Restore app [installed via Toolkit] to v4.10
+Updated wanam efs backup/restore app [installed via Toolkit] to v1.40
+Updated Busybox free installer by Stephen Erickson to v27

The main change with this update is that I have separated TWRP that the Toolkit uses in to 2 versions. The version that can be booted to [temp] or flashed to [perm] the device will always be the latest version available. Another version of TWRP is used for any adb operations within the Toolkit. The Android Unified Toolkit needs working adb function in Recovery for the Auto Root scripts as well as adb sideloading and some newer versions of TWRP have problems with adb so an older version needed to be used. Splitting the 2 types means I can bring back regular updates of TWRP (when released by TeamWin) while knowing that all Recovery functions will still work.

You can download the Unified Android Toolkit from http://www.skipsoft.net/?p=1660

I will update the public modules as soon as possible (probably when the next full version is built).

Mark.
 

sdwyz74

Senior Member
Jun 23, 2009
610
33
46
Seattle
Will this help with possible Brick ? As my tablet would not come on so I start pushing buttons and it went to some kind of screen and I pushed something now it won't come on but when I plug it to my PC or sort of recognizes it and says I don't have the drivers ??? Please help as I love this thing it's the Nexus 7 ME370T the WiFi Model thanks in advance and Please Advise
 

jerryp7

Senior Member
Feb 20, 2011
400
55
Hells Kitchen, NYC
My toolkit has given years of good service on my Nexus 10 but in trying to update to LMY47V, when I tell it my bootloader is unlocked it says "< was unexpected at this time" and takes me back to the device page. What am I doing wrong?
Opps. Wrong thread. Sorry.
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
UAT 1.4.1 RELEASED AND AUTOUPDATE and PUBLIC VERSIONS UPDATED

Changelog for device module:
+Added FULL support [including root] up to Android 5.1.1 LMY47V GSM MODEL
+Added SkipRoot image [5.1.0, 5.1.1] to auto root GSM without needing recovery
+Added 5.1.1 LMY47V GSM stock image to download/flash directly from Toolkit
+Added FULL support [including root] up to Android 5.1.1 LMY47V WIFI MODEL
+Added SkipRoot image [5.1.0, 5.1.1] to auto root WIFI without needing recovery
+Added 5.1.1 LMY47V WIFI stock image to download/flash directly from Toolkit
+Updated TWRP Custom Recovery to 2.8.7.0 with fixes for 2.8.6.0 [both models]

Changelog for UAT 1.4.1:
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)

The AutoUpdate for pro users has all the above included (update via the toolkit).
You can also download the Unified Android Toolkit 1.4.1 from http://www.skipsoft.net/?p=1660. You can select Fresh Install to delete all device modules and related files (recovery, root) so when you select your device at startup it will download the latest module with all the above included. If you have several device modules downloaded (e.g. for samsung and nexus) then you can select 'upgrade' when installing the toolkit, then run ToolKitClean.exe to delete just the modules you want to update.

Enjoy, Mark.
 
  • Like
Reactions: Harpratap

yrp888

Senior Member
Nov 12, 2011
120
14
Android M Apps&Data Restore Error

Been a while since visiting this thread. Testifies to how well the Toolkit works.

So true, this tool gets used regularly here and get better each revision.

Today I decided to backup my Nexus 7 Grouper which many different flavours of 5.x ruined so that I can install Marshmallow. Same procedure followed each previous occasion when installing a new ROM - create backup of apps & data, wipe according to Dev's instructions, restore, but this time when I went to restore my backup I received the following error

adb: unable to connect for restore: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

No confirmation dialogue appeared on the device and I wasn't able to issue the adb kill-server command successfully.

I'm managing to work around it by manually installing each app, but that's rather tedious! :eek:

I know this error is my own making by attempting something the tool is not (yet) ready for but I hope this info can assist Mark in refining his awesome toolkit for those of us who still see value in this great little device.
 

ClintE1956

Senior Member
Sep 29, 2012
142
35
So true, this tool gets used regularly here and get better each revision.

Today I decided to backup my Nexus 7 Grouper which many different flavours of 5.x ruined so that I can install Marshmallow. Same procedure followed each previous occasion when installing a new ROM - create backup of apps & data, wipe according to Dev's instructions, restore, but this time when I went to restore my backup I received the following error

adb: unable to connect for restore: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.

No confirmation dialogue appeared on the device and I wasn't able to issue the adb kill-server command successfully.

I'm managing to work around it by manually installing each app, but that's rather tedious! :eek:

I know this error is my own making by attempting something the tool is not (yet) ready for but I hope this info can assist Mark in refining his awesome toolkit for those of us who still see value in this great little device.

You might try another USB cable or port on your PC; I've had many strange connection problems (files transfer fine, but certain commands won't work at all) and when I changed cable or port, everything worked again.

I think my grouper is bricked, but I can't seem to get a definitive answer about this. Running AICP 5.1.1 rom (you might want to give this a try, as I have not found any other rom that even comes close to features and performance for grouper and Sprint GS3) & TWRP, device went into bootloop, stopping and restarting at the point where the boot animation dims. Bootloader and TWRP run fine, but I can't seem to write to *any* partition, or erase or flash them either. Fastboot commands return successful, but nothing changes on the partitions no matter what I try. A couple of files won't stat in TWRP, so no nandroid backups since that started, but the tab worked fine for quite a while after that issue showed up.

I would sure love to see this N7 resurrected, as it's one of the best little tabs I've ever used. Anyone have any ideas?

Thanks in advance.
 

yrp888

Senior Member
Nov 12, 2011
120
14
You might try another USB cable or port on your PC; I've had many strange connection problems (files transfer fine, but certain commands won't work at all) and when I changed cable or port, everything worked again.

I think my grouper is bricked, but I can't seem to get a definitive answer about this. Running AICP 5.1.1 rom (you might want to give this a try, as I have not found any other rom that even comes close to features and performance for grouper and Sprint GS3) & TWRP, device went into bootloop, stopping and restarting at the point where the boot animation dims. Bootloader and TWRP run fine, but I can't seem to write to *any* partition, or erase or flash them either. Fastboot commands return successful, but nothing changes on the partitions no matter what I try. A couple of files won't stat in TWRP, so no nandroid backups since that started, but the tab worked fine for quite a while after that issue showed up.

I would sure love to see this N7 resurrected, as it's one of the best little tabs I've ever used. Anyone have any ideas?

Thanks in advance.

I learned yesterday that the ADB error is actually something to do with that particular ROM, so no need for Mark to investigate that further.

Not sure if this could help you but I ended up deleting the cache & data partitions and reformatting to EXT4 (previously F2FS). For some weird reason during attempting to install a ROM TWRP couldn't wipe the data partition because one folder was somehow "locked". Removing and repartitioning solved that for me. I discovered I could recopy the ROM install files while in Recovery using drag & drop as the tab remained connected as an MTP device, so that made it a simple decision to remove and reformat the partitions.

So far I've been less than happy with the few LP ROMs I've tried for their random sluggishness despite the various Dev Option tricks suggested. Installing KK has proved that the Nexus 7 still is a really good tablet!
 
Last edited:

ClintE1956

Senior Member
Sep 29, 2012
142
35
I learned yesterday that the ADB error is actually something to do with that particular ROM, so no need for Mark to investigate that further.

Not sure if this could help you but I ended up deleting the cache & data partitions and reformatting to EXT4 (previously F2FS). For some weird reason during attempting to install a ROM TWRP couldn't wipe the data partition because one folder was somehow "locked". Removing and repartitioning solved that for me. I discovered I could recopy the ROM install files while in Recovery using drag & drop as the tab remained connected as an MTP device, so that made it a simple decision to remove and reformat the partitions.

So far I've been less than happy with the few LP ROMs I've tried for their random sluggishness despite the various Dev Option tricks suggested. Installing KK has proved that the Nexus 7 still is a really good tablet!

How did you remove and repartition?

Yes, the N7 is a great little tab, I'm hoping this one isn't bricked. Works great for most games and excellent for reading, which has been the primary use for it. If I get some type of answer about this issue that proves it is, I can't see spending $50 to replace the motherboard; better to get something with at least 2GB RAM.
 

yrp888

Senior Member
Nov 12, 2011
120
14
How did you remove and repartition?

Yes, the N7 is a great little tab, I'm hoping this one isn't bricked. Works great for most games and excellent for reading, which has been the primary use for it. If I get some type of answer about this issue that proves it is, I can't see spending $50 to replace the motherboard; better to get something with at least 2GB RAM.
In TWRP under Wipe, went into Advanced Wipe, tick which partition you want to work with then hit Repair or Change FS. In there you get the option to Change FS.

Be warned though, when you wipe the Data partition you will need to recopy the installation ZIP files from your PC back to the newly erased partition. So before you do the wipe, while in TWRP please do a test copy of some files using Windows Explorer with your Nx7 connected as MTP (that's how I did it) to satisfy yourself you can do the copy successfully after the wipe. Probably the push files command in this Toolkit will do the same. I can't remember now but I think I skipped that method because I was getting the ADB errors.

This isn't a plug, but can I say that SlimKat 4.4.4 has returned this tab back into the great little tab I remember before Google "upgraded" it to JB. No lags, really snappy, <50% RAM usage with 13 services, and it appears to have great battery life despite being the original 3YO battery.

I think my ROM search is over but I'll know for sure after a few months of testing. The only peculiarities were I flashed SuperSU manually (my fault for not RTFM), and the DPI setting wasn't correct (??) but I was able to easily reset that with a free app from the Play Store. Once that was done, all good! I also disabled journaling in Ext4, read somewhere that helps too.

My usage for that tab is even more basic - I read Play Newsstand, check stockmarket apps, look at weather forecasts, and check my emails. That's all. You'd think that JB and M could handle that but no.
 

ClintE1956

Senior Member
Sep 29, 2012
142
35
In TWRP under Wipe, went into Advanced Wipe, tick which partition you want to work with then hit Repair or Change FS. In there you get the option to Change FS.

Be warned though, when you wipe the Data partition you will need to recopy the installation ZIP files from your PC back to the newly erased partition. So before you do the wipe, while in TWRP please do a test copy of some files using Windows Explorer with your Nx7 connected as MTP (that's how I did it) to satisfy yourself you can do the copy successfully after the wipe. Probably the push files command in this Toolkit will do the same. I can't remember now but I think I skipped that method because I was getting the ADB errors.

This isn't a plug, but can I say that SlimKat 4.4.4 has returned this tab back into the great little tab I remember before Google "upgraded" it to JB. No lags, really snappy, <50% RAM usage with 13 services, and it appears to have great battery life despite being the original 3YO battery.

I think my ROM search is over but I'll know for sure after a few months of testing. The only peculiarities were I flashed SuperSU manually (my fault for not RTFM), and the DPI setting wasn't correct (??) but I was able to easily reset that with a free app from the Play Store. Once that was done, all good! I also disabled journaling in Ext4, read somewhere that helps too.

My usage for that tab is even more basic - I read Play Newsstand, check stockmarket apps, look at weather forecasts, and check my emails. That's all. You'd think that JB and M could handle that but no.

I've tried everything I can find using TWRP and fastboot, including changing partition type and formatting /data. I just can't seem to get anyone to respond as to whether there is anything else that can be done for this device. None of the partitions can be wiped, formatted, or change filesystem. Also, files can be copied from the device using MTP and copying to it results in reported success but nothing is actually written. :(

Battery life is still great, buttons work, screen is flawless, always been in leather case, not a scratch on it, looks brand new. It's just not worth putting $50 or so into a new motherboard kit. Anyone need a 2012 wifi N7 for parts?
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,064
Norfolk
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.
 
  • Like
Reactions: Reiven89

Top Liked Posts

  • There are no posts matching your filters.
  • 770
    NEXUS 7 - SUPPORTS ALL AVAILABLE VERSIONS UP TO LATEST ANDROID BUILDS
    SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*

    The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.

    FUNCTIONS OF UNIFIED ANDROID TOOLKIT
    * Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
    * Backup/Restore a single package or all apps, user data and Internal Storage
    * Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
    * Unlock/Re-Lock your Bootloader [Nexus]
    * Root Stock builds
    * Various Root options using insecure boot image or custom recovery
    * ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
    * ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
    * [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
    * Install BusyBox on your device
    * Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
    * Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
    * Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
    * Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
    * Extras, Tips and Tricks section
    * Auto Update ToolKit to latest available version at startup (professional only feature)
    * Program up to 10 Quickpick slots and run them very quickly (professional only feature)
    * Mods section to automatically perform certain tasks on your device
    * Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
    * Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
    * Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
    * Flash Custom Recovery or Google Stock Image to Device
    * Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
    * Rename the Recovery Restore File present on some Stock Roms
    * Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
    * Flash Custom Recovery to Device
    * Boot [Nexus] or Flash .img Files directly from your PC
    * Install a single apk or multiple apk’s to your device
    * Push Files from your PC to your device
    * Pull Files from your device to your PC
    * Disable forced encryption on Nexus6 and Nexus9 devices
    * Install Root Checker app by Burrows Apps
    * Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
    * Install EFS/Partition Backup/Restore app by Wanam
    * Dump selected LogCat buffers to your PC
    * Dump BugReport to your PC
    * Set Files Permissions on your device
    * Open new Command Prompt for manual input
    * Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
    * Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
    * Display Important Information about your device

    --------------------------------------------------------------
    Toolkit_main_menu.png

    --------------------------------------------------------------

    SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*

    DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)

    NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.

    Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.

    --------------------------------------------------------------

    WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
    THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.

    ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
    THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
    THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
    PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).

    MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.

    AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv

    --------------------------------------------------------------

    PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.

    --------------------------------------------------------------

    1. INSTALLING ADB/FASTBOOT DRIVERS

    The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.

    THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.

    If drivers are not installed or there is an exclamation mark next to the device:
    Plug the device in to a usb cable directly connected to your motherboard.
    In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
    Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
    If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
    If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
    Click OK and select Google ADB Interface.

    Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.

    On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.

    --------------------------------------------------------------

    2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT

    When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.

    Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).

    --------------------------------------------------------------

    USEFUL INFORMATION

    How to get into your FastBoot Mode
    1. Turn your phone off
    2. Unplug your usb cable if you have one plugged in
    3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode

    How to get into Recovery
    1. First boot into FastBoot Mode as described above
    2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery

    Show the Menu in the Stock Recovery Screen
    1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.

    --------------------------------------------------------------
    *DISCLAIMER*
    I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
    189
    66
    65
    Frequently Asked Questions:

    Q. What is ADB Shell?

    Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).

    From Google:

    Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
    A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
    A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
    A daemon, which runs as a background process on each emulator or device instance.

    ----------------------------------------------------------------------------

    Q. What is FASTBOOT?

    Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.

    It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.

    ----------------------------------------------------------------------------

    Q. I flashed CWM but each time I reboot the Stock Recovery is back

    There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.

    Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.

    OR you can use the ToolKit to rename the files (root access needed).

    ----------------------------------------------------------------------------

    Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader

    1. Download, install and run the Google Nexus 4 Toolkit.
    2. Install adb/fastboot drivers (if you havent already done so)
    3. Option 9 to download a Google Factory Image.
    4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
    4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
    5. Option3, 2 to relock the bootloader.

    Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.

    ----------------------------------------------------------------------------

    Q. What is the difference between Nandroid and Titanium backup?

    A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.

    Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.

    The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).

    ----------------------------------------------------------------------------

    Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.

    The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.

    ----------------------------------------------------------------------------

    Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).

    Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.

    You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.

    ----------------------------------------------------------------------------

    Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?

    Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.

    This option will NOT require your bootloader to be unlocked first.

    You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.

    You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.

    The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.

    ----------------------------------------------------------------------------

    Q. I have Windows 8 and cannot install the drivers

    How to Disable Driver Signature Enforcement in Windows 8:

    From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
    Click ‘More PC Settings’.
    Click ‘General’.
    Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
    Wait a bit.
    Click ‘Troubleshoot’.
    Click ‘Advanced Options’
    Click ‘Windows Startup Settings’
    Click Restart.

    When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.

    ----------------------------------------------------------------------------

    Q. I cannot find Developer options to Enable USB Debugging

    With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:

    Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
    When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
    Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
    You can now go into Developer options and enable usb debugging.

    ----------------------------------------------------------------------------

    Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect

    Make sure the code entered is for the correct Toolkit being used.

    You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.

    Also make sure you enter the code correctly as the characters are case sensitive.
    23
    I really am sorry that some people feel I shouldnt have donate links in my Toolkits or ask for donations to receive the latest Updates before they are available for mass download in the Toolkit thread. I am not going to start digging into why I do things this way as I want to keep this thread about the Toolkit and not about money or people who want everything for fee and expect it immediately.

    I know there have been some bugs with 4.2 and most are releated to the way google have implemented multiuser support which has changed how everything has always been in the past. I have neglected some of my Toolkits as I have been working 16hours a day for the last week building toolkits for the Nexus 4 and 10 and damn does the Nexus 10 have alot of internal issues right now lol (toolkit sorts them out though).

    I just wanted to post a worklog update that I am currently updating the Galaxy Nexus Toolkit which will be finished and a full build posted in the OP tomorrow night (hopefully), then I will be updating the Nexus 7 Toolkit and posting a full build in the OP with 4.2 support for all models including the new 32GB 3G model Monday or Tuesday depending on how many issues I come accross.

    I work 7 days a week trying my hardest to keep the Toolkits up to date and I would like to thank all the people who show appreciation for that (in whatever way they see fit).

    Oh and for the people who do show their appreciation with donations (and for people who dont like to wait) the link in the menubar at the top of my website www.skipsoft.net will send an instant email with activation code as soon as paypal completes. If you do want to donate then use http://skipsoft.net/donate/?toolkit=GoogleNexus7 until it is added to the next version as you will get your code alot quicker.

    Now PLEASE lets have no more talk about donations in the thread. If you have any questions or issues then feel free to pm me.

    If anyone has a current bug list for 3.4.2 and would like to speed up the next release then please message me as it will make my life a bit easier.

    Thank you.

    Mark.