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

Search This thread

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
Sorry if this has been asked and answered. I tried using search but it isn't working right now.

I'm using version 1.7.0 of the Toolkit. I want to use option #20 to make an Odin .tar file. Every time I try, it goes to a screen asking to install drivers. I already have drivers installed and working. Is this a bug or am I doing something wrong?
This was a bug, thanks for pointing it out I have just fixed it and pushed an Auto Update to V1.7.1 to fix it. Should work fine now.

Mark.
 
  • Like
Reactions: Atmazzz

fenrhir

Senior Member
Dec 8, 2010
56
10
Once again, just bought a Nexus 10, and use your tool to root it. Really great job, big thanks ! Nexus 4 and 10 rooted thanks to your job ! Happy to have paid you some beer-eq ;)
 

bootscreen

Member
Feb 28, 2011
25
1
Göttingen
www.bootscreen.net
hy mskip,

thx for your nice toolkit.

on point 13 you wrote [ADB Mode, Must be in Android]. what did you mean with must be in android? do you mean that android must be startet? than its not right. it also works when you are in the recovery.

when you enter point 13 is it possible to:
- get an option which opens the put_files_to_push_here folder
- list the name with a countet number so we only need to type te number and not the whole name?

greetings
bootscreen
 

Eckless

Member
Jun 23, 2010
46
9
Updating from 1.7.0 to 1.7.1

Very minor thing...I'm currently on version 1.7.0. When starting up it asks if I want to check for updates. When I say yes, it finds 1.7.1. It then puts a bunch of text on the screen but then closes before I have a chance to type anything.

Any ideas? (Not a huge issue...1.7.0 is fine for me now)

Thanks!
Eckless
 

Barguast

Senior Member
Sep 30, 2008
266
12
Super n00b question;

I rooted with the paid version of this toolkit, and installed the custom recovery, etc. Will this prevent me from getting the latest OTA? If so, how do I go about installing the update manually, and what do I need to be aware of (will it unroot, wipe, etc.)?

I just don't want to brick my device, and I'm sure others are wondering the same. :eek:
 

shimp208

Inactive Recognized Contributor
Jan 25, 2011
2,613
3,089
Boston
Re: [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE

Super n00b question;

I rooted with the paid version of this toolkit, and installed the custom recovery, etc. Will this prevent me from getting the latest OTA? If so, how do I go about installing the update manually, and what do I need to be aware of (will it unroot, wipe, etc.)?

I just don't want to brick my device, and I'm sure others are wondering the same. :eek:

While you can still get OTA updates when you are rooted and have a custom recover, generally it's assumed OTA updates will break root. You can manually install them by downloading the latest Nexus 10 OTA from this thread http://xdaforums.com/showthread.php?t=1971165. Then transfer the OTA update .zip file to your SD card then boot into the custom recovery. Once in recovery wipe the dalvik cache, next navigate to where you put the update on your SD card and install it. After the update finishes installing reboot the device and once it boots it up the tablet should be fully updated.

Sent from my Nexus 10 using xda premium
 
  • Like
Reactions: Barguast

Barguast

Senior Member
Sep 30, 2008
266
12
While you can still get OTA updates when you are rooted and have a custom recover, generally it's assumed OTA updates will break root. You can manually install them by downloading the latest Nexus 10 OTA from this thread http://xdaforums.com/showthread.php?t=1971165. Then transfer the OTA update .zip file to your SD card then boot into the custom recovery. Once in recovery wipe the dalvik cache, next navigate to where you put the update on your SD card and install it. After the update finishes installing reboot the device and once it boots it up the tablet should be fully updated.

Sent from my Nexus 10 using xda premium

Thanks though I'm not having any luck with this. When I try to install the ZIP, I get the following error:

Code:
assert failed: apply_patch_check("/system/bin/gzip", [HASH], [HASH])
E:Error in /sdcard/[...]
(Status 7)
I've tried downloading the update again, still the same. I'll wait to see how everyone else gets on before trying again. Thanks all the same.
 

dberthia

Senior Member
Apr 6, 2011
183
34
Samsung Galaxy S21 Ultra
Question about the adb sideload. I'm trying to use it to update to 4.2.2. I've got TWRP waiting in sideload mode, but when I enter "yes" to begin (in toolkit) I get a "device not found" error. I've got the zip file in the right place, and the N10 is connected in USB debugging mode. What am I missing here?
 

shimp208

Inactive Recognized Contributor
Jan 25, 2011
2,613
3,089
Boston
Thanks though I'm not having any luck with this. When I try to install the ZIP, I get the following error:

Code:
assert failed: apply_patch_check("/system/bin/gzip", [HASH], [HASH])
E:Error in /sdcard/[...]
(Status 7)
I've tried downloading the update again, still the same. I'll wait to see how everyone else gets on before trying again. Thanks all the same.

Are you on stock JOP40D? You have to be on that build version in order to apply the OTA update, also I would suggest checking out this guide on how to manually apply the latest 4.2.2 update for the Nexus 10.

---------- Post added at 04:12 AM ---------- Previous post was at 04:04 AM ----------

Question about the adb sideload. I'm trying to use it to update to 4.2.2. I've got TWRP waiting in sideload mode, but when I enter "yes" to begin (in toolkit) I get a "device not found" error. I've got the zip file in the right place, and the N10 is connected in USB debugging mode. What am I missing here?

Try doing it manually using ADB, you can download ADB from the Android SDK here. Once you have the SDK installed you can easily sideload the update by putting TWRP in sideload mode and typing the command:

Code:
adb sideload path/to/update.zip

An even easier method would be to just download the OTA update and flash it in TWRP using this method here.
 
  • Like
Reactions: alexandruvlad

Barguast

Senior Member
Sep 30, 2008
266
12
Re: [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE

Are you on stock JOP40D?
Yes, but I've messed with the system folders, including installing Busybox. I understand this causes issues with version checking, but can be overridden. I'll try it later.

EDIT: I successfully applied the update by removing all of the checks from the installer script (all the ones to /system/bin anyway). Applied the update with CWM via this toolkit, and it seems to have worked perfectly. :)

Sent from my Nexus 4 using Tapatalk 2
 
Last edited:

alexandruvlad

Senior Member
Mar 10, 2010
532
22
Bucharest
Google Pixel 7 Pro
Sorry for asking but where can i find the 1.7.1 to download - tried everywhere with no chance of success :(
I'm already a donator on the Note 2 toolkit.....do i have to donate again to receive a "Donate" version for the Nexus 10 toolkit?
Thanks a lot
 

dberthia

Senior Member
Apr 6, 2011
183
34
Samsung Galaxy S21 Ultra
Asking for a little help. I used the toolkit to re-flash the stock 4.2.0 image to my N10 with an unlocked bootloader. Worked like a charm. However, each time I try to apply the 4.2.1 update, I get a message saying "Error" toward the end of the update process, and when I reboot all I see is "No command" message. I've gone through this cycle a few times now. Anyone have any insight?
 

mrdunlop

Senior Member
Jan 24, 2011
320
52
Asking for a little help. I used the toolkit to re-flash the stock 4.2.0 image to my N10 with an unlocked bootloader. Worked like a charm. However, each time I try to apply the 4.2.1 update, I get a message saying "Error" toward the end of the update process, and when I reboot all I see is "No command" message. I've gone through this cycle a few times now. Anyone have any insight?

I had an issue likt that yesterday trying to update to the 4.2.2 I had to reflash the stock kernel on top of the original image to get it to work. Not sure why as it should of replaced it with the stock flash.

My device was also unlocked and rooted. I was able to sideload using adb and twrp and kept getting error till i flashed stock image and stock kernal. once 4.2.2 was flashed i had to re root and re load twrp, using the toolkit

May help may not. are you using the toolkit to apply 4.2.1?
 

dberthia

Senior Member
Apr 6, 2011
183
34
Samsung Galaxy S21 Ultra
Thanks for the response. When you say reflash the stock kernel, are you referring to recovery or something else? I've already restored the stock recovery. Is this something I can do through the toolkit? I'm not seeing any reference to flashing a kernel in the toolkit.

I had an issue likt that yesterday trying to update to the 4.2.2 I had to reflash the stock kernel on top of the original image to get it to work. Not sure why as it should of replaced it with the stock flash.

My device was also unlocked and rooted. I was able to sideload using adb and twrp and kept getting error till i flashed stock image and stock kernal. once 4.2.2 was flashed i had to re root and re load twrp, using the toolkit

May help may not. are you using the toolkit to apply 4.2.1?
 

shimp208

Inactive Recognized Contributor
Jan 25, 2011
2,613
3,089
Boston
Re: [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE

did it work for 4.2.2 Stock root ? not able to find out that options there..

Try selecting the 4.2 or 4.2.1 root options those should still work for 4.2 2. If not there are other simple root procedures you can try as well.

Sent from my SCH-I535 using xda premium
 
Dec 23, 2010
28
5
AW: [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE

Very minor thing...I'm currently on version 1.7.0. When starting up it asks if I want to check for updates. When I say yes, it finds 1.7.1. It then puts a bunch of text on the screen but then closes before I have a chance to type anything.

Any ideas? (Not a huge issue...1.7.0 is fine for me now)

Thanks!
Eckless

Hi Mark,
the same Problem by me.

Getippt mit nem Nexus 10
 

rugolt

Senior Member
Dec 11, 2011
71
23
Hi Mark,

the update from 1.3.0 to 1.7.1 worked perfectly after entering my donation code.
Will there be an update for Android Build JDQ39 (v4.2.2) ? Pleeease... :cyclops:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 118
    NEXUS 10 - SUPPORTS ALL 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
    * 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, 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).

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

    ChangeLog:
    ToolKit v1.4.1 (05th Oct 2015)
    +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)

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

    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.
    19
    Google Nexus 10 Frequently Asked Questions

    UPDATES:
    12
    UPDATE:

    Ok well apparently something is up with 4.2 and the oem unlock will mostly lead to a bootloop. Im rewriting the root procedure to do everything in the right order so that this shouldnt happen and as soon as its been tested I will re-release the Toolkit. Its 2:13am now so I will work for another hour and then finish off tomorrow. Watch out tomorrow evening for a new version and I will post back as soon as I have more info.

    ANYONE WHO EXPERIENCES THE BOOTLOOP PROBLEM. REBOOT BACK INTO FASTBOOT MODE, SELECT RECOVERY, HOLD POWER BUTTON DOWN AND THEN PRESS THE VOL BUTTON WITHIN A SECOND TO BRING UP THE RECOVERY OPTIONS, SELECT WIPE/FACTORY RESET AND WHEN THE DEVICE REBOOTS IT SHOULD BOOT UP FINE.

    Mark.
    11
    GOOGLE NEXUS 10 TOOLKIT V1.2.0 [22ND NOVEMBER 2012] UNLEASHED!!

    EVERYTHING WORKS AND WORKS WELL. THERE ARE FIXES FOR THE BOOTLOADER UNLOCK BOOTSCREEN FREEZE AND LOTS MORE HELP ADDED.

    Changelog:
    ToolKit v1.2.0 (22nd November 2012)
    Rewrote loads of routines to add extra safety
    +Added adb Sideload as a routing flash option
    +Added text to Bootloader Unlock to fix errors
    +Rewrote all the root routines
    +Added more text to the FAQ in the Info Section
    +Lots of other improvements

    My Nexus 10 turned up this morning so everything has been thoroughly tested by myself and SimonTuffGuy so im confident there will be no more problems (as long as people read before doing) but if anyone finds any bugs or textual errors please let me know so I can fix them.

    Download links in first post.

    Enjoy :)

    Mark.
    9
    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.