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

Search This thread

loveubuntu

Senior Member
Nov 25, 2010
508
179
Nope sorry everything that was on the virtual sd card is very much wiped now. I learned that lesson the hard way too the first time I unlocked.

Mark.

Thanks man. I thought so. The messed up thing is that it wasn't my first time unlocking. I just blanked out and forgot. Oh well. I really am not impressed with this no external sd card devices. It gave me a sense of security to know that I had an sd card I could take out if something went wrong (drop the phone in water lately?).

I will n ot buy another virtual sd card device. That's for sure.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
Thanks man. I thought so. The messed up thing is that it wasn't my first time unlocking. I just blanked out and forgot. Oh well. I really am not impressed with this no external sd card devices. It gave me a sense of security to know that I had an sd card I could take out if something went wrong (drop the phone in water lately?).

I will n ot buy another virtual sd card device. That's for sure.
I know what you mean this is the first phone I have had with no external expansion and yes it doesnt give you much confidence if you should have an accident. I have my dropbox on my phone set to automatically upload all camera and camcorder files over wifi and dropbox linked on my pc means so at least I know I will never lose those files and they available on my pc without ever having to plug my phone in. Everything else on my virtual sd card is expendable.

Mark.
 

ddgarcia05

Senior Member
Mar 28, 2010
2,287
114
Edinburg / Mcallen, Texas
I tried to restore my lte nexus to stock. It extracted the stock image and said that my device would reboot into setup but it never rebooted....what now.

Nevermind. Looks like there was a second file in the google image folder.
 
Last edited:

jss2

Senior Member
Feb 12, 2012
137
37
Greater Boston Area
On the first post, it says (and the screen shot shows) that this works with the GSM version of 4.0.4 IMM76D, but for the CDMA/LTE version, it doesn't have 4.0.4 IMM76D, rather, it has 4.0.4 IMM30B.

Right now, on my CDMA/LTE phone, I'm running BAMF Paradigm v1.2, which is based on 4.0.4 IMM76D.

Does v5.6 of this toolkit work with CDMA/LTE 4.0.4 IMM76D builds? If so, which choice should I select at the first screen?

Thanks.
 

Flawd

Member
Jun 10, 2010
41
1
Delaware
Not sure if it's something with an app I have installed or if it's with the toolkit as I haven't had time to test, but I just wanted to get this written down before I forget.

I disabled shutter sounds for the camera and video recorder.

I installed the max quality settings.

I rebooted.

I took a couple pictures. Everything seemed fine (actually it seemed unchanged at all, file sizes were the same if not smaller, but that's not why I'm here).

I took a test video. When copying it to the computer to view the quality, I noticed there were two videos. Both were named correctly (VID_20120412_TIME) but one had a (1) at the end. The "original" without the 1 is 60MB, and the "copy" with the (1) is 88MB.

More file info: both files have the exact same detailed info according to Win7 properties:

VIDEO
Length: 00:24
Frame width: 1280
Frame height: 720
Data rate: 30651kbps
Total bitrate: 30782kbps
Frame rate: 29

AUDIO
Bit rate: 131kbps
Channels: 2(stereo)
Audio sample rate: 48 kHz

The date and time created is also the same for both.

Edit: Just curious, why stereo audio recording? Is it utilizing the noise cancellation mic or something? Or is it just required to have the higher quality?
 
Last edited:

skater95

Senior Member
Sep 11, 2010
843
30
Wichita, Kansas
Help please? So I'm 99% sure I have the drivers installed, I downloaded them from samsung, and when I try to install them with the toolkit it gives me the MUI error, so they're installed, but my phone isn't showing up on the adb or fastboot. I'm wanting to unlock and root my phone and put AOKP and Franco kernel so I have a better battery life.

Edit: PDAnet got me to get the toolkit to recongize my phone.
 
Last edited:

MarcMaiden

Senior Member
Sep 17, 2010
186
33
Fremont, CA
Hi guys,

I am having a weird issue

(first off awesome program man, props to you)


for some reason when I try to root my phone, it just hangs at waiting for device. By hang i mean ive waited over 10 minutes for it to do something. The weird thing is, I tried it on two different computers, my laptop have V5.5 and my desktop has 5.6 and both have the same issue. It worked on the laptop before so I'm not sure what is different. USB debugging is on.

EDIT: more info
the device is showing as connected through adb
I am selecting the right build number
I am fully charged etc

any help would be awesome!
Thanks,
MArc






EDIT


I am a retard - wasn't in fastboot mode......those mimosas I had for breakfast sure didnt help...
 
Last edited:

spectrumfox

Senior Member
Oct 5, 2009
577
142
I don't think I've commented yet on how awesome this utility is. Thanks so much for putting it all together and keeping it updated. It has come in handy many many many many times and I will continue to praise its usefulness.

:D :eek: :D :eek: :D :eek:
 

turntable

Member
Jun 26, 2010
15
1
i'm in fastboot mode and it still just sits there waiting for device....


any tips?

---------- Post added at 10:46 PM ---------- Previous post was at 10:30 PM ----------

the driver install within the toolkit gives the error that you are instructed to disregard, so i am under the impression the drivers are fine. i know i've never installed the pdanet drivers referenced in one of the first posts so i tried and get this:

toolkit%20probs.png


also in the above image is what device manager lists for the phone...looks normal...

---------- Post added at 11:21 PM ---------- Previous post was at 10:46 PM ----------

for those that run into the same thing i did, try following the instructions on installing the android adb driver manually. that seems to have worked for me.

---------- Post added at 11:33 PM ---------- Previous post was at 11:21 PM ----------

almost forgot.....thanks skip!



:)
 

tu3218

Senior Member
Apr 14, 2009
3,413
368
So I achieved root via this toolkit months ago. I just flashed a mod from a fellow member and now it broke root. I'm running a 4.0.4 rom, do I just go back and get root again? Or is there something else I can do?
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
So I achieved root via this toolkit months ago. I just flashed a mod from a fellow member and now it broke root. I'm running a 4.0.4 rom, do I just go back and get root again? Or is there something else I can do?
If you lost root then you can just use the ToolKit to reroot the phone. Make sure to select 4.0.4 from the Model Selection Screen so the ToolKit uses the correct insecure boot image.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
UPDATE TO GALAXY NEXUS TOOLKIT V5.7

ChangeLog:
ToolKit v5.7 (16th April 2012)
+Added extra error control when flashing Google Stock Rom to detect incorrectly named files
+Added more info after installing drivers
+Fixed Camera quality profiles for fast sound playback in HQ Profile (Phone Mods Section)
+Minor bug fixes and streamlined code

The compiled package file is not digitally signed (as it costs money to buy a Microsoft authenticode certificate). This may be thrown up on your PC as a potential virus or you may just be asked if you want to trust the file. THERE ARE ABSOLUTELY NO VIRUSES IN THIS TOOLKIT.

Mark.
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
Will this utility work with the Sprint version that's coming, or is it too soon to know until someone has one in their hands? Thanks.
It all depends which build is shipped with the Galaxy Nexus but it will be an LTE model on Sprint so im sure it will be covereable by the ToolKit the same as Verizon's LTE version is now.

Mark.
 
  • Like
Reactions: Examiner19

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,072
Norfolk
Mark,

thanks for your continued support of this toolkit. Now that v5.7 is out, can you answer my question from several days ago:
http://xdaforums.com/showpost.php?p=24730114&postcount=587


Does v5.7 support LTE/CDMA 4.0.4 IMM76D builds in addition to IMM30B builds? It's clear that 4.0.4 IMM76D builds are supported for the GSM version, but it's not clear for the CDMA/LTE version.

Thanks again.
IMM76D is a GSM build and the Rom you are using is an LTE Rom with parts of IMM76D included (I assume). The Model Selection screen is only really needed for stock users so the correct boot image can be used to perform certain functions (rooting, pushing files and performing phone mods). As you Rom is a custom Rom it is most probably using an insecure boot image so whenever you are asked that question in the ToolKit you can reply 'yes'.

You can select the 4.0.4 LTE build from the Model Selection screen but as long as your Rom uses an insecure boot image then it doesnt really matter what you choose.

Mark.
 

jss2

Senior Member
Feb 12, 2012
137
37
Greater Boston Area
Mark,

thanks for answering my question about 4.0.4 IMM76D, and of course, thanks for creating and maintaining this great tool. It's very much appreciated.

- Jason
 

max_rio

Senior Member
Nov 5, 2011
105
12
Venice
Backups

When i sync my contacts with google, big G returns them to me, after I reinstall an update (after wipe factory) only with the contact photo. No ring tone associated. I must then associate the ringtone prefered, again, contact after contact. I'm feel sick..

Mark, your toolkit can help me?

Thanks for your explanation.

Max_rio
 

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.