TOOLKIT AND DEVICE 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 like removing system apps.
Q. I flashed Custom Recovery 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 ES File Manager or 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 (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn’t contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a
better AntiVirus program such as BitDefender.
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.
Titanium Backup is mainly 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 (which takes up space).
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
1. 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, then click the Gear icon).
2. Click More PC Settings.
3. Click General.
4. Scroll down, and click Restart now under Advanced startup.
5. Click Troubleshoot.
6. Click Advanced Options.
7. Click Windows Startup Settings.
8. 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 updated to Android 4.2 or later and cannot find Developer options
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:
1. Goto Settings, About and tap the Build number text 7 times.
2. When you have tapped 3 times you will be given a countdown of taps until you become a developer.
3. Once you are told you are now a developer you can go back to the Settings Screen and can see Developer options.
4. You can now go into Developer options and enable usb debugging.
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won’t work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera (P2P) mode. To do this open the notification area [top left] with the device connected via usb, click where it says ‘connected as’ and change from MTP to PTP.
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
Q. How to get into your Download Mode
1. Unplug your usb cable if you have one plugged in
2. Keep holding the Volume Down, Home and Power buttons until you see a warning screen [about 10 seconds]
3. Press the Volume Up button to boot the phone into Download Mode
Q. How to get into Recovery
1. Unplug your usb cable if you have one plugged in
2. Keep holding the Volume Up, Home and Power buttons together until you see a
green android man on the screen [about 10-15 seconds]
Q. I tried to enter the code for the pro version but it says the code is incorrect
1. Make sure the code entered is for the correct Toolkit being used.
2. You need to start the Toolkit with the toolkit.exe file when activating so the settings can be initialised or the code will not be accepted.
3. Make sure you enter the code correctly as the characters are case sensitive.
Q. I flashed the insecure boot image and the screen is blank
After flashing an insecure boot image via odin you may notice that the screen is blank after the device reboots. The device is still fine but on some newer builds with more security and older kernel is required for full adb root access. You will be able to see exactly what is going on from the Toolkit screen and after the procedure finishes the stock boot image is dumped back to your device to bring the screen back to life.
Q. The procedure didn’t complete and the screen is still blank.. HELP.
If for any reason a procedure fails to finish and the screen stays blank [the stock boot image is not dumped back] then all you have to do is flash the stock boot image from the Root menu [option 6] via Odin with your device in download mode to bring the screen back. You can also do this manually by entering download mode [hold power vold down and home buttons for 15 seconds then follow the on screen direction] then start odin from the Toolkit installation folder and load the stock boot image from the root\device folder as a PDA file.