NOTE2: As the ToolKit.exe and ModsSection.exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
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 'EXTRAS' SECTION WILL CONTAIN BROWSER TIPS, GENERAL TIPS, KEYBOARD TIPS, MARKET TIPS, SCREEN TIPS, SECURITY TIPS AND SETTINGS TIPS AS WELL AS A FEW TRICKS YOU CAN DO WITH YOUR DEVICE. THE 'QUICK PICKS' SECTION 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.
AUTO REPLY LINKS FOR PAYPAL AND GOOGLE CHECKOUT TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
AUTO UPDATES ARE BY FAR THE EASIEST WAY TO KEEP THE TOOLKITS UP TO DATE AS I HAVE LOTS OF OTHER TOOLKITS TO LOOK AFTER. IF ANYONE HAS ANY VIEWS ON THIS PLEASE PM ME OR CONTACT ME AT TOOLKIT.SUPPORT@SKIPSOFT.NET. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
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 phone and flash CWM (ClockworkMod) Recovery.
THE DRIVERS CAN NOW BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
IF YOU HAVE ANY TROUBLE WITH THE TOOLKIT INSTALLING THE DRIVERS PLEASE POST IN THIS THREAD WITH YOUR OPERATING SYSTEM VERSION AND ERROR MESSAGE.
a. If you dont want to use the ToolKit to install the drivers then the best best drivers to try are PdaNet for Android, download and run the 32-bit Windows 7/Vista/XP or 64-bit Windows 7/Vista and follow the instructions to install (selecting Samsung as your device manufacturer if asked).
You can remove pdanet for Android from your phone and pc at a later time without removing the drivers.
b. After the drivers have been installed disconnect the usb cable and shut down your phone. Keep holding the 'Volume Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode.
c. Goto your Control Panel on your PC and open the Device Manager. You want this open so you can see the FastBoot driver is installed or so you can install it manually.
d. Connect the usb cable. In the Device Manager a new item called 'Android 1.0' should pop up and then the driver should install automatically. Once it is installed you will have a new section in the Device Manager called Android Phone without an "!" meaning its installed correctly.
MAKE SURE YOU ENABLE USB DEBUGGING IN SETTINGS, DEVELOPER OPTIONS BEFORE CONNECTING THE USB CABLE IN ADB MODE SO THAT THE PC CAN DETECT THE PHONE PROPERLY.
Note 1: If the driver doesnt install automatically then double click on the Android 1.0 item, then click on the driver tab and select 'update driver'. Select 'browse my computer' and then 'Let me pick from a list'. If no items appear in the list then untick 'Show compatible hardware' and find the Android adb driver or Samsung adb driver.
Note 2: If you are still having problems setting up the fastboot drivers then have a read of *THIS* guide which may help you.
Note 3: Samsung Verizon Drivers can be downloaded *HERE*. These drivers will most probably only work on LTE devices.
Note 4: Sprint users may have better luck downloading drivers from *HERE* (click on 'See All Downloads' then select 'Software' at the bottom) if you cant get the automatic drivers to work from the ToolKit.
a. Download the Galaxy Nexus ToolKit package and install the ToolKit to your PC. The installation will create a Shortcut on your desktop called 'Galaxy Nexus ToolKit' for easy access. You have the option to include or exclude the drivers files at installation so if you already have your drivers set up and are just updating the ToolKit then you can untick the drivers if you wish.
b. Once the ToolKit is installed make sure your phone is booted and plugged in via USB cable and double click on the shortcut on your desktop to run it.
c. You will be asked if you want to check for an Update. If you type 'yes' this will download and check the latest version numbers against the versions in the ToolKit. If there is an update available then you will have the option to download and install it (professional feature).
d. You will now be presented with a Model Selection Screen to choose the Model/Build that you are currently on. Type the number that corresponds to your desired selection. For example type '17' for GSM MODEL [YAKJU] 4.2.2 [Build JDQ39]. If you cannot find the build your device is using then type 'h' to select the HELP option to get more info.
NOTE: If you have a new build that isnt covered by the Toolkit you can also type 'a' in the Model Selection screen to see instructions on how to pull your stock image and send it to email@example.com so support can be added.
e. The Toolkit will now locate and download the image pack for your chosen Model. This is a new feature so the Toolkit is not limited to how many Models can be added and it cuts down ALOT on the download size. After the zip file has finished downloading it will be extracted to the correct folders and the files checked to make sure everything is ok. If you cannot download the pack via the Toolkit then you can download it manually from http://goo.im/devs/mskip/toolkit/gal...us/model_files and extract the files to your installation folder.
f. When you enter the Main Menu you will see 'Adb Mode' and 'Fastboot Mode' at the top. If you have installed your drivers correctly then you will see your devices serial number under the text with 'device' next to it for the mode you are in. If you see this then your device is connected and you can carry on.
NOTE: If you haven't installed the drivers and don't see a serial number at the top then this is the FIRST thing you want to do so the Toolkit can operate properly. You may need to do this in adb and fastboot mode.
g. Each option in the ToolKit has full information on what it is and how to use it.
3. FLASHING A ROM, RADIO OR KERNEL VIA CWM RECOVERY
a. Download your chosen Rom, Radio or Kernel from the Development Forum, then make sure your phone is booted up as normal and connect your usb cable so it goes into MTP Mode. Copy the .zip file (DO NOT UNZIP IT FIRST) to the 'Internal Storage' part on your phone. Do not copy it to a Sub Directory as it will be harder to find when flashing it.
b. Enter CWM Recovery by first entering the Fastboot mode Screen (Disconnect the usb cable (if you have one plugged in), then shut down your phone. Keep holding the 'Volume Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode), then select 'Recovery mode' by pressing the 'Volume Down' button and then press the 'Power' button to enter CMW Recovery.
You can also enter Recovery by downloading Rom Manager (free from the Market) which gives you the option to reboot to Recovery.
c. Scroll down to 'Install zip from sdcard' and select. Then select 'choose zip from sdcard'.
d. Scroll to your Roms' zip file and select. Then scroll down to 'Yes' in the list and select to start flashing the Rom.
e. When flashing is finished select 'Go Back' until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
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 Up' and 'Volume Down' buttons and press the 'Power' button to boot the phone into FastBoot Mode
How to get into ClockworkMod 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. The blue recovery menu screen should pop up.
ToolKit v11.1.0 (7th May 2013)
+Added missing superuser apk (chainfires root)
+Few minor bug fixes
ToolKit v11.0.0 (19th April 2013)
+Completely restructured Toolkit code
+FULL Support upto JellyBean 4.2.2 (all models)
+Added model zip file download after model selection to reduce download size
+Check md5 of stock image to make sure downloaded file isn't corrupted before flashing
+Downloaded stock image file is copied to the 'backups' folder before flashing for future use
+Added adb sideload for auto flashing zip files
+All stock images now downloaded from goo.im so the link won't be broken if google delete the file
+Latest CWM and TWRP Recovery images included
+Lots more minor improvements and changes
ToolKit v10.1.0 (29th Nov 2012)
+Added support for JellyBean 4.2.1 (yakju/takju)
+Edited some code for stability with different builds
+Checked and verified root functions with new builds
+Changed version checker method to work with V10+
+Added new donation link to get an immediate code
ToolKit v10.0.0 (27th Nov 2012)
+Added full support for yakju/takju Jelly Bean 4.2
+Blocked rooting 4.2 with Superuser until it's working
+Added Insecure boot image for 4.2 (build JOP40C)
+Added full support for Sprint 4.1.1 FH05 Stock Build
+Added takju 4.2 JOP40C to download section
+Added yakju 4.2 JOP40C to download section
+Added Sprint 4.1.1 FH05 to download section
+Added SuperSU 0.98 by Chainfire for Rooting 4.2
+Added Custom Recovery choice in 1-CLICK option
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added Device Information Screen to Main Menu
+Added Boot Insecure Boot Image to root section
+Updated cwm recovery (gsm) to v22.214.171.124 (includes new 'install zip via sideload' feature
+Updated TWRP for all models to 126.96.36.199
+Added choice to format/leave userdata partition when flashing google stock image
+Added boot/flash stock recovery image
+Added sideload root/unroot zip files via cwm
+Various bug fixes and textual additions
ToolKit v9.1.0 (21st Oct 2012)
+Fixed CWM and TWRP Recovery flashing error on certain builds.
ToolKit v9.0.0 (20th Oct 2012) [HUGE UPDATE]
+Added FULL Root and Toolkit support for Verizon upto 4.1.1 JRO03O
+Added FULL Root and Toolkit support for GSM upto 4.1.2 JZO54K
+Added Stock Recovery Images for GSM and LTE
+Added 4.1.1 and 4.1.2 Google Stock Images to Downloads Section
+Fixed Google Stock Image links in Downloads Section
+Added option to enable/ask/disable Update Check at Toolkit Startup
+Added NEW 'Quick Picks' Donators Feature (10 programmable slots, 6 Tasks to choose from)
+Added CWM Recovery 188.8.131.52 [all versions]
+Added TRWP Recovery 184.108.40.206 [yes I know 220.127.116.11 is available but that has bugs and is not stable]
+Added Unroot, Uninstall Busybox, Uninstall CWM Manager Zip file for quick unroot via Custom Recovery without flashing Stock Rom
+Improved Flash/Boot .img stability
+Re-wrote lots of procedures to incorporate the Quick Picks Feature
+Added NEW Root/UnRoot Section in Main Menu
+Added Custom Recovery root option for Superuser or SuperSU
+Added 'Help Me' option on Model Selection Screen
+Added 'Auto Update' check option in Toolkit Settings Section
+Added uninstall.bat batch file for Clean removal of Toolkit files
+Updated NAND Backup script in ModsSection
ToolKit v7.8 (6th Aug 2012)
+Fixed Radio Dump not running the radio trimmer
+Added pause after all 'adb root' commands to fix some users adb restarting and missing commands
+Added option to reboot into Fastboot Mode from adb in all fastboot tasks. No more having to reboot to fastboot manually before performing a task
+Added 'WHAT'S NEW' viewer to see what's in the Auto Update when an update is available
+Fixed several scripts which crashed on non UK languages
+Fixed efs backup (folder backup) routine
+Checked entire program and added minor tweaks
+Wrote New Date/Time Stamp script to work across all Regions (different formats)
+Integrated script into all required features in ToolKit
Note: This should fix all errors caused by incorrect stamp in ALL Backup Tasks, Odin tar Creator and several other tasks
ToolKit v7.7 (31st July 2012)
+Fixed Auto Updates not installing from V7.6
+Enabled 'Quick Pick' option in Main Menu and added some info
+Enabled non English OS support to open Internet Explorer for people who want to donate
+Updater will now only update from the last released version to cut download size (this may mean you get a few incremental updates if you have a very old version
+Installer will automatically clean folders before installing (will not delete folders that may contain user data) so no need to uninstall between builds
ToolKit v7.6 (29th July 2012)
+Added Stock Recovery image for Jelly Bean builds
+Added option to check for Updates at startup
+Updated uninversal drivers to 0.7
+Updated driver commands for Windows XP 32bit
+Added google stock image links to 4.1.1 for yakju and takju models in the Downloads Screen
+Added option to flash google image after it has been downloaded via the ToolKit
+Minor edits and fixes
ToolKit v7.5 (20th July 2012)
+Added Auto ToolKit Update feature on startup
+Updated CWM Touch to 18.104.22.168 on all models
+Updated TWRP Recovery to 2.2.0 on all models
+Added Create tar with 1-Click for flashing via Odin
+Added Activation of Donator features via ToolKit
+Rewrote push routine to find filename from wildcard
+Removed a date setting from backup routines
+Rewrote extras file to work with new activation
ModsSection v3.0 (20th July 2012)
+Minor rewrites and ammendments
ToolKit v7.4 (11th July 2012)
+Added ToolKit support for JellyBean 4.1.1 (yakju and takju but other models can use either of these to root)
+Added option to boot from insecure kernel for Internal Storage backup to fix problems on JellyBean builds
+Reorganised folders in ToolKit
+Made some changes to scripts suggested by users
+Clarified some points in the Model Selection Screen
ModsSection v2.1 (10th July 2012)
+Added JellyBean check for certain mods that do not work on 4.1+ (disables those mods if on JellyBean)
ToolKit v7.3 (10th July 2012)
+Added full auto download Google Stock Image to
ToolKit folder ready for extracting/flashing (no need
to move the file manually anymore)
+Fixed Stock Recovery flash flashing TWRP Recovery
+Removed 'Restore NAND files to extSDCard' since
there is no external SD Card (oops)
+Adb server is restarted before the Main Menu to
+Minor re-writes to improve some scripts
ToolKit v7.2 (9th July 2012) ANOTHER BIG UPDATE!
+Added Root support for Jelly Bean (4.1) on all models (maguro, toro, toroplus)
+Added Busybox install into 1-CLICK process
+Added download link for Stock Toro IMM76K image
+Added option to keep/delete NAND backup files after NAND backup completes
+Added option to push NAND backup folder to Internal or External Storage for CWM restore
+Added Superuser 3.1.3 zip file to root folder for flashing via Custom Recovery if required
+Added insecure boot image for LTE IMM76K builds
+Added Cache Ripper by Adam Lange in Dev Tools
+Grouped Recovery flash options
+Grouped Bootloader Unlock/ReLock options
+Added Colour Settings (background and text)
+Added Reboot to Download Mode in Reboot Options
+Reorganised alot of the Menu Screens
+ToolKit kills adb server when exiting via 'x' in the Main Menu
ModsSection v2.0 (9th July 2012)
+Added check step for Jelly Bean compatability
+Added step to ask if a NAND backup wants to be made before attempting any mods
+Ammended text on Menu Screens
ToolKit v7.0 (31st May 2012) BIG UPDATE!
+Added ability to perform a FULL NANDROID Backup of your system (Boot img, Cache tar, Data tar, Recovery img and System tar) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery
* Added /data and /system folders backup, compress to a .tar file and save to your PC
* Added Backup/Restore of your /efs partition
* Added Dump of selected Phone Partitions, compress to a .zip file with md5 and save to your PC
* Added Install BusyBox binary on your phone
* Moved backup/restore options to a single screen
* Tidied up alot of text on screens
ToolKit v6.2 (16th May 2012)
+Added Verizon IMM76K to Model Selection Screen
+Added Verizon IMM76K root support
+Added info about Google Play devices not wiping after Bootloader Unlock
+Added useful info on Model Selection Screen
+Added extra info on several options to help users
+Various minor bug fixes and optimised code more
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
Q. Adb is not working with the newer 4.2.2 JellyBean update (device offline)
As many people have found out the older versions of my Toolkits (or adb) won't work with the 4.2.2 update. The device shows as offline as will not connect for any adb operations. The older adb server doesnt include the new authentification method needed to connect. Fortunately the fix is as easy as updating 4 files which I have zipped up and uploaded to my server to make everything easy.
NOTE: The latest Auto Updates for the Toolkits include the new google files so this shouldnt be a problem for anyone who has Auto Updated their Toolkit recently.
1. Download http://www.skipsoft.net/download/too..._for_4.2.2.zip
2. Make sure your Toolkit has been closed correctly with the "x" option in the Main Menu or the adb server will still be running
3. Extract the contents of the zip file above to your Toolkit folder (overwriting the original files)
4. Run the Toolkit and when you get to the Main Menu a popup will appear on your device asking to allow USB debugging for your pc
5. Tick 'allways allow from this computer' and click ok to add your pc to the whitelist
6. Select the 'Refresh Main Menu' option in the Toolkit and your device will now show as 'device' and not 'offline'
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).
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. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android 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 the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
Q. How do I Update to the latest Google Stock Rom (manually)?
THE FOLLOWING PROCESS WILL ERASE YOUR INTERNAL STORAGE BACKUP ANYTHING YOU NEED.
You can use the GN ToolKit which will do everything automatically or execute the following steps.
Or you can follow the following instructions and do it manually:
These steps assume that you have set up your adb/fastboot drivers correctly.
1. Download it from *HERE*.
2. Unzip it to a folder on your pc.
3. Copy the file fastboot-windows.exe to this folder (you can find the fastboot file in many places including my ToolKit download on post#1).
4. Browse to this folder on your pc, hold the 'shift' key down while right clicking on a blank area of the window and select 'Open command window here' to open a command prompt in that folder.
5. Boot the phone into Fastboot Mode (KEEP holding the 'Volume up' and 'Volume down' buttons while pressing the 'Power' button).
6. Connect your device via the usb cable
7. In the command prompt type:
which should return your phones serial number and prove you are connected.
8. To flash the google images type the following:
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download and run the GN Toolkit.
2. Follow instructions on the first screen to install fastboot drivers (if you havent already done so)
3. Option5 to flash a stock rom.
4. Let the phone reboot, then shut the phone down and reenter fastboot mode again (hold vol up and vol down buttons together while pressing power button).
5. Option7 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped.
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 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 phone in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your phone into fastboot mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your phone 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. If the driver isnt installed then it should say 'Android 1.0' (or something similar) in the list. 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 (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 then it should work fine.
Q. I get the message - exec '/system/bin/sh' failed: No such file or directory (2) when attempting any adb root commands
There is something wrong in your /system folder and the shell won't work. On testing I got this message on certain methods to update to Jelly Bean (may have been my fault when flashing) but most methods are fine. Users who got the phone with this pre-installed should not get this message but if you updated from ICS by flashing a Stock Update then you need to get it via a different method.
Q. I have a GSM Nexus build 4.0.4 IMM76K and I dont know which number to type in the Model Selection Screen
Builds that are very close usually share a boot image if they are compatible so if you dont see your build in the list you can choose the next build up (as long as it is the same version i.e. dont choose a 4.1 build when you have 4.0.4 on your phone). If you have a GSM 4.0.4 IMM76K build on your phone that isnt in the list then you can select the 4.0.4 IMM76I build which will work perfectly.
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’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
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 updated to Android 4.2 JOP40C and 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. The Toolkit does not work from behind a proxy, is there any way I can get round this?
The Toolkit uses wget to retrieve files from internet. According to wget manual, you can setup wgetrc file for environment setting of wget that also includes proxy settings.
The following is done with Windows XP but other operating systems should be similar (thanks to coalee for the info):
1. Open Control panel → System → Advance tab → Environment Variables
2. Add new User variable named WGETRC with value c:\wgetrc.txt
3. Create a text file named wgetrc.txt in c:\
4. Edit file wgetrc.txt
Here is the wgetrc.txt contents it contains 2 lines:
These instructions are for people who want to know EXACTLY what they are doing when they
root their device and dont want to use quicker methods such as superboot or any ToolKits.
Download the GNex Manual Root file *HERE* and unzip to your PC.
NOTE: If you have already installed adb/fastboot drivers and Unlocked your Bootloader
then you can skip straight to Step 9.
1. First thing is to make sure you have installed the fastboot/adb drivers. You can download the drivers from *HERE* (click on 'See All Downloads' then select 'Software' at the bottom).
2. Browse to the 'GNex Manual Root' folder on your PC in Windows Explorer, then hold the
shift button and right click in a blank area of the folder. Select 'Open command window
here'. With the phone booted in Android and the usb cable attached go into your settings,
Developer options and tick 'USB debugging'. The USB debugging icon should appear at the
3. Check your Android build version (this is needed for later) by going to settings,
About phone and writing down your Android version.
4. In the Command Window type: adb devices [return] and you should see a serial number.
5. Type: adb reboot fastboot [return] to reboot into fastboot mode.
6. Once in fastboot mode type: fastboot devices [return] to check for a serial number.
If you dont see a serial number in either adb or fastboot when typing the commands then
read through the drivers installation section to make sure they are installed correctly.
7. IF you havent done so already then type: fastboot oem unlock [return] to unlock the
bootloader and enable images to be booted/flashed. THIS WILL ERASE ALL INFORMATION ON
YOUR PHONE INCLUDING YOUR VIRTUAL SD CARD SO MAKE ANY BACKUPS BEFORE DOING THIS!!
8. If you only just Unlocked your Bootloader then reboot your phone into Android by
typing: fastboot reboot [return]. The phone will reboot half way through and then
continue to the setup wizard. Go through this and then reenable your USB debugging from
settings, Developer options.
STEP 8 IS NOT NEEDED IF YOU HAVE ALREADY UNLOCKED YOUR BOOTLOADER PRIOR TO STARTING THIS!
9. Reboot into fastboot mode by typing: adb reboot fastboot [return].
NOTE: When in fastboot mode you need to reboot back into Android using an Insecure boot
image which is included. Once booted the insecure boot image will grant you temporary
root access via adb to allow you to push the superboot.apk and su binary files and change
their files permissions. This only lasts until you reboot your phone.
10. Find the right Insecure Boot Image (in the folder) for your build version and model
(GSM OR LTE). For Sprint 4.0.4 IMM76D you will want to use the boot_gsm_IMM76D_insecure.img file. Type: fastboot boot YourInsecureBootImage.img [return].
11. When booted into Android (you dont have to unlock from the lockscreen) you can now
Mount the device, Push the files and set their permissions to complete the procedure.
Type: adb root [return] to gain root access.
Type: adb remount [return] to mount the device.
Type: adb push su /system/bin [return] to push the su binary to /system/bin.
Type: adb push superuser.apk /system/app [return] to push superuser.apk to /system/app.
Type: adb shell chmod 06755 /system/bin/su [return] to set file permissions.
Type: adb shell chmod 06755 /system/app/Superuser.apk [return] to set file permissions.
Job done. You have now completed the root procedure. Reboot the phone and install any
root app such as AdAway, SetCPU, Root Checker or Root Explorer to check it.
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
After reading about Dan Rosenberg’s bootloader exploit for the Samsung Galaxy S 4,I … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?