[GNEX TOOLKIT V11.1] Drivers, Backup, Unlock, Root, Recovery, Flash + MORE [VERIZON]

Search This thread

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
What would rooting do to my 10 dollars on Google wallet prepaid card on my sprint gnex. And how about the 40 dollars Google will put in there in three weeks. Will rooting erase my balance and prevent Google from putting in the free money in three weeks?

Sent from my Galaxy Nexus using xda premium
Unlocking the bootloader and Rooting the phone wont affect google wallet in any way.

Mark.
 
  • Like
Reactions: godefoy

wwjoshdew

Inactive Recognized Contributor
Dec 30, 2008
1,389
1,400
Seattle
tinyurl.com
What would rooting do to my 10 dollars on Google wallet prepaid card on my sprint gnex. And how about the 40 dollars Google will put in there in three weeks. Will rooting erase my balance and prevent Google from putting in the free money in three weeks?

Sent from my Galaxy Nexus using xda premium

mskip is right, and if you watch my video, you'll see that mine is rooted and I used Google Wallet just fine! :D

http://www.youtube.com/watch?v=mOr_3qLw28I&hd=1&list=PL2A3C66EF2F16BA1E
 
  • Like
Reactions: godefoy

godefoy

Senior Member
Jun 3, 2011
106
9
just rooted and google wallet wont initialize my balance on my prepaid card is gone
help please
 

thenamesian

Senior Member
Aug 24, 2009
58
4
can someone show me a link on how to exactly install adb on a windows 7 64-bit machine for LTE galaxy nexus? thanks!
 

godefoy

Senior Member
Jun 3, 2011
106
9
locked the bootloader and now google wallet works. Im running stock rooted with locked bootloader and waiting for stable CM9
 

bunklung

Senior Member
Mar 20, 2011
532
110
Love this toolkit! Thanks mskip.

I would like to roll with an encrypted phone. Thankfully, someone came out with a work around for flashing custom roms using the phone's ram as a temp file system. http://xdaforums.com/showpost.php?p=25340449&postcount=39

The last hurdle is nandroid backup and restores. I am able to manually use the dd command in adb to backup the phone's firmware partitions. I have in the past restored my kernel (boot.img) with fastboot (via this toolkit).

Would there be any plans to automate this process so one could easily backup the firmware and then restore the firmware for encrypted phone. There is no easy way similar to nandroid that works for encrypted phones.

Thanks again.
 

2Ceedz

Senior Member
Jul 18, 2010
59
5
locked the bootloader and now google wallet works. Im running stock rooted with locked bootloader and waiting for stable CM9

Weird, was running stock, wiped wallet data from inside app (to keep NFC SE)..unlocked, restored data, updated to 4.04 OTA installed wallet but didnt initialize, backed up again, flashed Liquid, restored, installed wallet, all is great-my $1.00 is there, LOL. Although I do get the "unsupported device" now because of root, but all is fine here! :)

Does unlocking and rooting require a data wipe?
Unlocking does....use this GREAT tool to backup and restore data before and after unlocking... Thanks mskip!

can someone show me a link on how to exactly install adb on a windows 7 64-bit machine for LTE galaxy nexus? thanks!
Cyanogen Howto:_Install_the_Android_SDK

You may have to create an environment variable for JAVA_HOME in your win7 x64 box (i did - not hard) - Has Linux and Mac, just scroll below those once you get the required files. :)
 
Last edited:

Jerryatric

Senior Member
Oct 4, 2010
86
18
Rochester, MN
wifi problems

I have used previous versions of this awesome toolkit to root my phone and everything worked perfectly.

I returned my nexus to stock and relocked it. Everything worked fine, but I decided I wanted root back. I used this toolkit to unlock and root, and the process completed without a hitch. But after rooting, regardless of whether I stay on the stock rooted 4.02 rom or flash something else, my wifi constantly drops every 30 seconds or so. This happens regardless of what network I use, and every other device that uses the same wifi does not have this problem- so I have excluded the network. I make sure that wifi is set to always stay on.

I re-return to locked stock using this toolkit and the wifi goes back to normal working order. I re-root and I have the same wifi dropping issue.

Anyone have any good ideas why this would occur?
 

eyekyu

Senior Member
Nov 23, 2010
270
32
Sin City
stuck in unlocking the bootloader, I'm not sure what I'm do wrong but heres what I'm doing.

Ive uninstalled all previous samsung drivers and what not.
followed the 1st step as per your app even got the weird error message, went back to the main menu and got the phone serial number as it describes. i proceed to option 7 and put my phone into fastboot mode and then it just hangs there, its like the phone isnot recognized.
any help, did i forget a step?

thanks

edit// did adb command
 
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
I have used previous versions of this awesome toolkit to root my phone and everything worked perfectly.

I returned my nexus to stock and relocked it. Everything worked fine, but I decided I wanted root back. I used this toolkit to unlock and root, and the process completed without a hitch. But after rooting, regardless of whether I stay on the stock rooted 4.02 rom or flash something else, my wifi constantly drops every 30 seconds or so. This happens regardless of what network I use, and every other device that uses the same wifi does not have this problem- so I have excluded the network. I make sure that wifi is set to always stay on.

I re-return to locked stock using this toolkit and the wifi goes back to normal working order. I re-root and I have the same wifi dropping issue.

Anyone have any good ideas why this would occur?
No idea at all why rooting would cause you wifi problems, sorry.

Maybe ask in the Q&A forums to see if anyone else has a similar problem.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
stuck in unlocking the bootloader, I'm not sure what I'm do wrong but heres what I'm doing.

Ive uninstalled all previous samsung drivers and what not.
followed the 1st step as per your app even got the weird error message, went back to the main menu and got the phone serial number as it describes. i proceed to option 7 and put my phone into fastboot mode and then it just hangs there, its like the phone isnot recognized.
any help, did i forget a step?

thanks

edit// did adb command
So when you enter fastboot mode and run the ToolKit you see the serial number in the Main Menu at the top? Can you also check in the Device Manager that the drivers have been installed properly.

Mark.
 

eyekyu

Senior Member
Nov 23, 2010
270
32
Sin City
So when you enter fastboot mode and run the ToolKit you see the serial number in the Main Menu at the top? Can you also check in the Device Manager that the drivers have been installed properly.

Mark.

as far as i know everything is properly installed. what would i look for? I noticed when i installed, 3 different drivers were successful all from your toolkit. just for some weird reason i had to use adb cmd on the boot loader then everything went like butter
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
as far as i know everything is properly installed. what would i look for? I noticed when i installed, 3 different drivers were successful all from your toolkit. just for some weird reason i had to use adb cmd on the boot loader then everything went like butter
In adb mode (android) run the ToolKit and in the main menu you should see a serial number at the top under the adb section. If thats ok use the reboot options in the ToolKit to reboot to fastboot and check if the serial number is now under the fastboot section at the top. If either are missing then goto your control panel on your pc and run device manager. With the phone connected in both modes you should see a device listed for the phone (may be called something like Android 1.0).

Mark.
 

eyekyu

Senior Member
Nov 23, 2010
270
32
Sin City
im guessing this is what you are talking about.
but none the less adb & fastboot mode both show devices now. maybe user error :confused: lol
 

Attachments

  • Untitled-2.jpg
    Untitled-2.jpg
    166.8 KB · Views: 178

2Ceedz

Senior Member
Jul 18, 2010
59
5
im guessing this is what you are talking about.
but none the less adb & fastboot mode both show devices now. maybe user error :confused: lol

No, he means in the toolkit.... pic 1 is when phone is booted (ADB MODE) & pic 2 is when in fastboot. ;)
 

Attachments

  • adbmode.jpg
    adbmode.jpg
    134.8 KB · Views: 182
  • fbmode.jpg
    fbmode.jpg
    139.5 KB · Views: 179
Last edited:

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
LARGE UPDATE TO TOOLKIT!

Changelog:
ToolKit v6.1 (2nd May 2012)
+Added Takju to Model Selection Screen
+Added rooting support for takju Stock Roms
+Added option to download Google Stock Image files directly via the ToolKit
+Added extra option to date format and added text for less errors backing up
+Added TWRP Touch Recovery to boot/flash options
+Added Sprint Stock Recovery image to the ToolKit
+Added Help info for App Backup option
+Added extraction check and auto rename of Google Image for incorrectly named files when flashing
+Added support for flashing Radio-cdma image files to correct partition on lte devices
+Added Sprint driver info to Manual Information
+Added proper insecure boot image from toroplus model IMM76D
+Changed CWM in 1-Click method to Touch version
ModsSection v1.7 (1st May 2012)
+Bought up to date with latest ToolKit

Im hoping this version will get rid of any errors when flashing google stock roms as the ToolKit will automatically rename the file if its been downloaded incorrectly. For some reason Internet Explorer renames tgz files to tar when downloading. I also added the auto download option and filled in the missing stock images that google deleted with ones from goo.im.

Download link in 1st post as usual.

Enjoy :)

Mark.
 

palomosan

Senior Member
May 29, 2010
205
2
Jersey
My problem is the following...
I installed and uninstalled the drivers (all of them with USBDeview) installed them back using the tool kit but when I check for the fast boot drivers in Device Manager I don't see the Android 1.0.

I went to ADB and checked, my phone's serial number is listed but it says offline, any help will be appreciated, thanks.
 
Last edited:

krze

Senior Member
Sep 29, 2010
162
32
Los Angeles
Will 6.1 be able to unlock/root the new IMM76K (Verizon 4.0.4 build)? If not, what does the time frame look like if any?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 211
    90
    [TOOLKIT] SKIPSOFT ANDROID TOOLKIT -GNEX VER- Drivers, Root, Recovery + MORE

    GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
    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 V1.4.1 [05th Oct 2015]
    * 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

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

    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.
    57
    [GUIDE] Flashing Your First Galaxy Nexus Rom For Newbs [GSM and LTE]

    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.
    12
    GALAXY NEXUS TOOLKIT AUTO UPDATE V9.4.0 [15TH NOV 2012] AVAILABLE!!

    Changelog:
    +Added FULL support for Jelly Bean 4.2
    +Added SuperSU 0.98 by Chainfire for Rooting JellyBean 4.2
    +Blocked rooting 4.2 with Superuser until it is updated
    +Added comprehensive 'Information/Help Section' within Toolkit
    +Added many minor edits relating to JellyBean 4.2 stability
    +Added link for 4.2 JOP40C Google Image (takju) in Download/Flash section
    +Added Stock Recovery Image for 4.2 JOP40C build
    +Added Insecure boot image for 4.2 (build JOP40C) for proper support
    +Added more to the 'Device Information' Screen
    +Made Auto Updater fully Automatic. No user input required at all

    Ok here we go..

    The Android 4.2 build adds a cool new feature called MultiUser. Unfortunately for users this update brings a world of trouble in regards to rooting and a few other things. Superuser 3.1.3 will not root and SuperSU 0.97 will look like it worked but it didnt and busybox wont go on properly. Chainfire has updated SuperSU to 0.98 to bring a temporary fix until he sorts it out properly but with SuperSU only the primary user can have root access. The SDCard is also now in /data/media/0 so if looking for your sdcard on clockworkmod or twrp you will have to look in the "0" folder as a legacy folder and another folder have been created in /data/media. Im not sure how this affects Internal Storage backups as the the files go back to the correct location but you may have to set permissions and owner rights manually to see the files/folders.

    The good news is that I have updated all parts of the Toolkit relating to do EVERYTHING you need to. I have temporarily blocked Superuser being used to root 4.2 as it wont work so just use SuperSU and you will be fine.

    I have also added all the FAQ from post#2 along with all other Information Screens to an Information/Help Section in the Main Menu so you have everything you need in the Toolkit to answer any questions/problems you may have.

    ALSO Im not sure if this has been mentioned in the thread but in 4.2 the Developer options section in settings has been hidden (google are crafty gits). To show the Developer options you need to go to Settings, About phone and tap on the 'Build number' line 7 TIMES until you are told you are now a developer. You can then see the Developer options section and enable usb debugging.

    I must appologise to users who dont want or cannot get the Auto Update feature as this will be the only way to get V9.4.0 until I can build a full version. I have loads of people shouting at me for help and im only 1 person trying to do the best I can in the time I have so please be patient.

    Hope you all enjoy the update and your rooted 4.2 builds :)

    Mark.
    8
    Amazing thread! This thread would probably be really helpful for newbies :)
    Just a few suggestions:
    1.)You might want to include how to flash custom kernels
    and also that you can
    2.)Clockwork Recovery can be instealled through Rom Manager

    Nonetheless, great thread :)
    Thanks :)

    1. Added Step 7, how to flash kernels and Radios via CWM.

    2. Added a Note at the end of the CWM flashing step for the Rom Manager method.

    Mark.