Hello All,
Root
If on stock, uprooted (ever), go to method 1. If not, keep reading.
Now, in the latest Molly CF-AutoRoot, it flashes a modified kernel to gain root that causes OTA updates (i.e. impending 5.0.1) to fail, this was due to the fact that until a couple days ago, the modified kernel was necessary. Chainfire found a way to fix it without modifying the kernel and implemented it in SuperSU 2.37. If you are rooted, used CF-Auto Root, and wish to retain root, but regain the stock kernel for OTA's, simply follow root method 2.
Method 1
To Root from stock LPX13D, Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices, and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected.
8. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery!
9. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
10. Select "Install Zip from sideload"
11. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
12. (On ADT-1) Select "**Go Back**"
13. Select "Reboot to system"
14. Select "No" when asked to restore Root, as this's feature does not work yet.
15. Profit!
Method 2
To Root from CF-auto rooted LPX13D and regain stock kernel (This will not restore Build.prop and other system changes!), Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
- stockbootlpx13d.img
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices", and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected
8. Run "fastboot flash boot stockbootlpx13d.img"
9. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery! Then you must run "fastboot reboot recovery"
10. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
11. Select "Install Zip from sideload"
12. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
13. (On ADT-1) Select "**Go Back**"
14. Select "Reboot to system"
15. Select "No" when asked to restore Root, as this's feature doe snot work yet.
16. Profit!
Unroot
Requirements:
- stockbootlpx13d.img
- recovery.img
1. Enter the SuperSU app, and go to Settings ==> Full Uproot, and verify your choice. (Stop here if you didn't use CF-auto root)
2. Plug your ADT-1 into your PC and run the command "cd desktop", then "adb reboot bootloader", then "fastboot flash boot stockbootlpx13d.img"
3. Run "fastboot flash recovery recovery.img"
4. Then "fastboot reboot"
5. Un-Profit!
To take an OTA Update
If you followed this guide correctly, just unroot from within SuperSU as shown in Step 1. Of the unroot section. It will leave you 100% stock. Then take the OTA.
Downloads
Stock Boot Image LPX13D (stockbootlpx13d.img): https://www.dropbox.com/s/vayt67s513v9z8u/stockbootlpx13d.img?dl=0
Stock Recovery Image LPX13D (recovery.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
CWM Recovery Img (cwm_molly_recovery_lpx13d.img): https://www.dropbox.com/s/8evaum04mv843dp/cwm_molly_recovery_lpx13d.img?dl=0
SuperSU 2.37.zip: http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Optional: Install Leanback Launcher from here to allow launching sideloaded apps: https://play.google.com/store/apps/details?id=eu.chainfire.tv.sideloadlauncher&hl=en
Happy Modding!
Credits:
Chainfire: The super amazing SuperSU, and the awesome CF-Auto Root, thank him!
GTAVHacker: Used CWM Recovery Image as a base, thank him!
Myself: Stock Images, and the guide.
npjohnson said:
CWM Recovery (cwr_molly_recovery_lpx13d.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
Click to expand...
Click to collapse
Thanks for this! Should the file on dropbox be named cwr_molly...? When I go to the download it simply says recovery.img.
good work
This is awesome, thanks for sharing, I'd really like to see TWRP ported as well, they allow OTA installs/mtp, adb sideloads & more, this is a great step in the direction of seeing custom roms
OP download links updated. My apologies.
Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.
Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.
CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.
CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP
I cant seem to get this to work. I tried using just the boot option and it just reboots into the bootloader. I tried the flash as well and recovery never boots. Any chance the problem is that this is for the ADT1 (molly) and not the Nexus Player (Fugu)?
The title of the post indicates ADT-1. You need to make sure any modification you do is appropriate for the device you have. The ADT-1 uses and Android processor/chip set while the Nexus Player uses an Intel processor/chip set.
Is there not a subforum for the adt1?
hmmmm CWM
jscat1 said:
Is there not a subforum for the adt1?
Click to expand...
Click to collapse
No there is not! I know, it sucks, but until that changes, looks like we are setting up shop on the fugu forums. XD
thanks so much for this. the ADT-1 needs more love on xda
twrp
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
Thanks man. TWRP is actually gonna be more than it is worth. CWM should work just fine, it actually has better support for keyboard.
I'll mess with it. Did you build the kernel with the ADT-1 and x86 architecture in mind?
defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
mkaymuzik said:
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
Click to expand...
Click to collapse
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
im working on a new tree. open to anyone to contribute and add things. created a github organization for this purpose
https://github.com/adt1-dev
PS: im new to this and learning on the way.
Edit: are your sources on github?
npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
If you're referring to the builds I released on GTVHacker forums for CWM recovery on the ADT-1, I didn't build the kernel or use any Android TV or ADT-1 source (it wasn't even available when I had started). I just used generic CM Android 4.4, reused the kernel and fstab from the stock ADT-1 recovery, and made a few changes to the default generic BoardConfig.mk.
Any plans on making recovery for nexus player? Just curious
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
illuminerdi said:
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
Click to expand...
Click to collapse
You can just download the factory image and extract it. Here is a little tutorial if you are unsure how to extract.
Related
The purpose of this guide is to walk you through the process of rooting your phone running 2.3.3 ONLY! I will do the best I can to make this as painless as possible and help you achieve your goals of S-Off.
***THIS THREAD IS ONLY FOR OBTAINING S-OFF, OBTAINING ROOT, AND INSTALLING CLOCKWORK MOD RECOVERY! ANY QUESTION REGARDING INSTALLING ROMS DO NOT BELONG HERE AND WILL NOT BE ANSWERED! ONLY ISSUES REGARDING ROOT WILL BE ANSWERED BY MYSELF OR OTHER MEMBERS.***
What you will need: (** = File is attached to OP)
Windows XP or higher (Thats all I have, someone else with MAC and/or Linux will need to assist and I can add it to the OP)
http://revolutionary.io/ .:UPDATE:. PRE4 now available
This site is where you will download the rooting tools and obtain a beta key. When you click on the download button for your OS, make sure you view the box that pops up requesting your OS version, phone model, HBoot version, and phone serial number. Without doing this you cannot root your phone so do it or you are screwed. There are two ways to get your phone serial number: 1) Remove the battery and look at the white sticker or 2) On your phone, go to Settings -> About Phone -> Phone Identity and under Device Serial Number you will see it. After you receive your code COPY AND PASTE it onto a word document or notepad because there are times when you will get confused with the font type from the Revolutionary site. Example, in my beta key, the lower case L looks exactly like the capital I and it threw me off. Also, the key IS case sensitive so keep that in mind.
If running windows, you will need these drivers:
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
If running Linux, reports show that you do not need any drivers.
If running Mac OS, I currently do not know so someone please let me know and I will update.
http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip **
This file is required to obtain ROOT AFTER you have S-Off.
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (WINDOWS) **
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (LINUX) **
http://dl.dropbox.com/u/33327355/cwm-4.0.1.4-vivow.img **
These two items are in case Revolutionary tool fails to install CWM on your phone OR if you want to do this offline at another location. Fastboot and abd tool is the software that will take the img file of CWM and flash it onto your phone after S-OFF is obtained.
Prepping your Phone:
Turn off FAST BOOT in the settings located: SETTINGS -> POWER
Turn on Unknown Sources: SETTINGS -> APPLICATIONS
Turn on USB Debugging: SETTINGS -> APPLICATIONTS -> DEVELOPMENT
Installing Root:
1 - First, install the HTC drivers on your computer. It is a very simple step and you should have no issues doing this at all. Also look at your installed programs list and confirm HTC Sync is not installed. This will stop your device from being detected by Revolutionary to other problems when rooting.
2 - Extract the Fastboot and ABD zip file onto the root of your local disk drive (ex. C:\android-win-tools )
3 - Copy/Cut and Paste the CWM img file into the Fastboot and ABD folder (ex. C:\android-win-tools\cwm-4.0.1.4-vivow.img) Doing this will prep your PC to flash CWM in the event the Revolutionary tool does not download and install it.
4 - Place phone in "Disk Drive" mode then Copy/Cut and Paste the root su zip file (do not extract it) onto the root of your SDCard on your phone (ex. x:\su-2.3.6.3-efgh-signed.zip )
5 - Place phone in "Charge Only" mode. A lot ot people run into issues and not realize this was not selected.
6 - Run the Revolutionary file now that everything is set to go.
7 - You will get a prompt to enter your beta code. This is the code you received when you downloaded the revolutionary file and entered the information to obtain the beta key.
8 - Sit back and WAIT while the application does what is needed. This process will take anywhere from 3 to 5minutes so be PATIENT.
9 - Upon completion, you will get a prompt to install CWM. Say yes here! Once done skip to step 10.
9a - If the revolutionary app crashes or fails to download/install, leave your phone in the state it is (HBoot mode and should say "Fastboot USB". Open a command prompt in windows (Start - Run - type CMD).
9b - If you did exactly as told, type "CD.." until you see "C:\"
9c - Type the following:
CD android-win-tools
fastboot flash recovery cwm-4.0.1.4-vivow.img
9d - This process takes about 30sec max. Almost done!!!
10 - On your phone, back track to the main menu of HBoot using the volume keys and Power button and select recovery (2nd Option). In a few seconds your will be in CWM.
11 - As long as you copied the signed zip file to the root of your sdcard, perform the following:
"Install Zip From SDCard" (5th Option)
"Choose Zip From SDCard" (2nd Option)
Select the root/su zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait.
Back track to main menu and reboot
12 - Give yourself a pat on the back for paying attention and have a cookie!
I am typing this on my tablet/phone/pc so if an error exists, please let me know right away and I will update the OP. Again, questions here are ONLY for rooting. Anything else...kick yourself in the head, do a real search, and post if needed.
Support:
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Common Q&A for their recovery tool
irc.freenode.net channel #revolutionary
IRC Support Channel
Special thanks to:
XDA-Developers - You guys rock!!!
AlphaRev and unrevoked (Revolutionary) - You have made many dreams come true!!! DONATE to them if you can peeps.
http://forum.xda-developers.com/showthread.php?t=1122694 - attn1 - his How to guide on manually installing CWM.
Nice guide bro.
Sent from my Incredible Sensation using XDA App
The Incredible 2 or VIVO is not an option in the Beta key?
kyrumo71 said:
The Incredible 2 or VIVO is not an option in the Beta key?
Click to expand...
Click to collapse
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
rivera82falcon said:
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
Click to expand...
Click to collapse
My bad, my work computer is crappy, the 2 does not show up on my browser lol
NICE, this thread should be sticky.
On a side note, make sure you have your phone connected to wifi or 3G if you want the revolutionary tool to download and install the CWM automatically. If not then you would have to flash the CWM manually per the instruction from OP.
kyrumo71 said:
My bad, my work computer is crappy, the 2 does not show up on my browser lol
Click to expand...
Click to collapse
I went to the site just now and HTC DROID Incredible 2 is the 6th option down in the device list. If it still doesn't show up, test another pc or try it on your phone. All you need is the key anyways.
Sent from my A500 using XDA Premium App
Thanks for this guide...
Sent from my DROID using XDA App
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Darkpsych0 said:
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Click to expand...
Click to collapse
I will say it is okay as this happens to my PC as well. The files still transfer and CWM flashes through fastboot as well.
Sent from my A500 using XDA Premium App
Mmk. I downloaded ROM Manager but everytime i start it up it says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su/" or "system/xbin/su"
I have the file on the root of the sdcard and im pretty sure i rooted it with revolutionary and installed CWM as well.
Ok... Dumb question... where do we find the fastboot and adb zips to install on the C drive??
I have gotten thru step 8 and failed whentrying to install CWM. I manually installed it with step 9 and it said finished. Step 10 says to select recovery but it is not listed. I rebooted to see if that would work but it didnt. Where did I go wrong?
EDIT: Actually it did work just was trying to hard. Thanks for the great instructions.
@ Darkpsycho0
try installing busybox from the market and give it a try again.
@PacerguyDon
The links are in the OP.
It's next to the one that has the img file as well. There is only one zip file and it contains both items in it.
@Flightmed
Power down, and get back into HBoot. You will see the following options:
Fastboot
Recovery
Factory Reset
Simlock
Hboot Usb
Image CRC
The second option (Recovery) is what you want.
EDIT: Glad you got it working!!!
Sent from my A500 using XDA Premium App
Got it... thanks, Found it a few minutes after posting
PacerguyDon said:
Got it... thanks, Found it a few minutes after posting
Click to expand...
Click to collapse
It happens...we get so excited that we tend to overlook the obvious. Kind of like my wife...I love her to death and I love to make love to her but I overlooked the obvious that she is also crazy. Oh well...
Sent from my A500 using XDA Premium App
Busybox said "Root not found! The su binary was not found on your phone." -_____-
Thinking about it and looking back...I didn't complete the instructions on applying root. I apologize to you and everyone else.
When you have CWM installed, open it up through recovery. Next, as long as you copied the signed zip file to the root of your sdcard, select "Install Zip From SDCard" (5th Option).
Select "Choose Zip from SDCard" (2nd Option)
Select the zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait. Once done, reboot and you should be good!
Again, I apologize. I will update main post asap!
Sent from my A500 using XDA Premium App
That worked.. no more error thanks. I was about to throw my phone across the room especially since while i was waiting for replies I was trying to just install new themes but can't get Astros to work with the apk files correctly. -_- (still can't)
I'm already rooted via 2.2 but this is a great guide for the truly n00b.
Should be seeing lots of new members posting in the development section soon ;!)
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.
Manual Rooting Instructions for Galaxy Nexus
UPDATES:
VIDEOS:
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.
thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............
dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.
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.
Anon9mouz said:
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.
Click to expand...
Click to collapse
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:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
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.
Mark.
Skip I just sent you a message regarding the radio pull CMD
mskip said:
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.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.
I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.
Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!
I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....
INTRODUCING THE SAMSUNG GALAXY NOTE2 TOOLKIT
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
NOTE: If you want a new build added to the Toolkit then download and install, Type 'A' in the Model Selection screen and follow the instructions.
HOW TO VIDEOS ARE ON POST#4 (THANKS TO WWJOSHDEW) MAKE SURE YOU HAVE A LOOK AT THEM AS A VIDEO IS WORTH A THOUSAND WORDS
FUNCTIONS OF SAMSUNG GALAXY NOTE2 TOOLKIT V4.1.0 [9TH APRIL 2013]
Install drivers automatically
Backup/Restore a single package or all apps, user data and Internal Storage
Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
Root any public build (different options)
Root with Superuser (ChainsDD) or SuperSU (Chainfire) via CWM (works on ANY build)
[*]Root+busybox+rename recovery restore files via Custom Recovery
[*]Unroot (delete root files and busybox)
[*]Many root/unroot options including adb, recovery and sideload via custom recovery
[*]Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC
[*]Pull /data and /system folders, compress to a .tar file and save to your PC
[*]Auto Update ToolKit to latest push version on startup (donator feature)
[*]Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
[*]Install BusyBox binary on phone
[*]Flash Stock Recovery
[*]Flash CWM Recovery (thanks to Clockworkmod Team) or TWRP Recovery (thanks to Team Win)
[*]Rename Recovery Restore files if present
[*]Flash Insecure Boot Image for adb mode
[*]Flash Stock Boot Image back to your phone
[*]Create tar file to flash via Odin (from upto 10 image files) with 1-click process
[*]Download, Extract and Flash Stock Rom (full DETAILED steps) ESSENTIAL FOR WARRANTY RETURNS
[*]Rip cache.img to zip file in CWM format for editing and flashing (thanks to Adam Lange)
[*]Install a single apk or multiple apk's to your phone (being worked on)
[*]Push Files from your PC to your phone
[*]Pull Files from your phone to your PC
[*]Set Files Permissions on your phone
[*]Dump selected LogCat buffers to your PC
[*]Dump BugReport to your PC (if installed)
[*]Help, Information Screen for various tasks
[*]Mods Section to Modify your phone (being worked on)
[*]Reboot Phone options in adb mode
[*]Change background, text colour in ToolKit
[*]Device Information screen which pulls info directly from device
[*]Activate Professional features from within the ToolKit
--------------------------------------------------------------
Mod edit: Download link removed
MD5 Sum for V4.1.0: 37360aabdf3869aad55d12dd2c2b0b07
NOTE: 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.
IMPORTANT: ONLY FLASH ROMS THAT ARE SPECIFICALLY MADE FOR YOUR PHONES MODEL NUMBER AS FLASHING AN INCORRECT ROM CAN SOFT BRICK YOUR DEVICE!
Credits: ChainsDD for Superuser, Chainfire for SuperSU, Chenglu for modded cwm.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN FREE (PUBLIC) AND DONATE (PROFESSIONAL) VERSIONS?
THE FREE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD POSSIBLY NEED TO MANIPULATE YOUR PHONE. NOTHING IS RESTRICTED. ACTIVATING THE DONATE VERSION WILL ADD THE ABILITY TO CHECK FOR UPDATES VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED TO MY SERVER WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. THIS ALSO MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE VARIANT OR CARRIER SO DONATOR VERSIONS WILL BE UPDATED SOONER. IF YOU ARE NOT ABLE TO, OR DO NOT WANT THE AUTO UPDATE FEATURE THEN ALL UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL DOWNLOAD VERSION AS SOON AS TIME ALLOWS AND THERE ARE ENOUGH UPDATES TO WARRANT IT. DONATORS WILL ALSO HAVE THE QUICK PICKS AND EXTRAS SECTIONS UNLOCKED AND THE 'NAG' SCREEN ON EXIT WILL BE DISABLED. NEW DONATOR FEATURES WILL ALSO BE ADDED TO THE TOOLKIT IN THE FUTURE.
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 [email protected]. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Changelog at the Bottom of Post#1)
--------------------------------------------------------------
PLEASE READ THE *FAQ* IN POST#2 BEFORE ASKING QUESTIONS
--------------------------------------------------------------
1. INSTALLING GALAXY NOTE2 DRIVERS
The first thing you need to do is to install the drivers. These are needed so that you can communicate with the phone via the PC and perform the tasks that the ToolKit offers.
NOTE: If you have Kies installed then it is advisable to uninstall it first to avoid conflicts.
a. Make sure your phone is booted into Android and the USB cable is unplugged.
b. Select Option 1 in the ToolKit to install the Samsung USB Driver pack. This should install all the neccessary drivers you need.
C. While the drivers are installing make sure that USB Debugging is enabled on your phone via the Settings, Developer options Screen.
d. After the drivers have been installed connect the USB cable and the PC should detect the phone and install the correct drivers. This will also happen when you enter Download Mode and Recovery Mode for the first time.
e. If you want to check the drivers then go to your Control Panel on your PC and open the Device Manager. With the USB cable connected you should see a device listed as 'Samsung Android Phone' or something similar and a driver attached to it.
NOTE: If you are having trouble with your device being detected or the drivers installing correctly then you could try rebooting your phone, using a different usb port and making sure no other drivers are installed on your pc.
--------------------------------------------------------------
2. USING MSKIPS' SAMSUNG GALAXY NOTE2 TOOLKIT
a. Download the Samsung Galaxy Note2 ToolKit package and run to install the ToolKit to your PC. The installation will also create a Shortcut on your desktop 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 '12' for INTERNATIONAL GSM MODEL [GT-N7100] 4.1.1 [Build ALJ1-ALJ3]. 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 protected] so support can be added.
e. The Toolkit will now locate and download the boot 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.
f. When you enter the Main Menu you will see 'Adb 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. 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.
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 (shut down the phone then hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds).
c. Select 'Install zip from sdcard' and select 'choose zip from sdcard' if the file is on Internal Memory.
d. Scroll to your zip file and select. Then select 'Yes' in the list to start flashing.
e. When flashing is finished press the BACK Button to go back until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
--------------------------------------------------------------
4. FLASHING A ROM, RADIO OR KERNEL VIA DOWNLOAD MODE USING ODIN
Odin can be used to flash image files or parts of your phone. You can flash something as simple as a boot image or a complete system. Everything is packed in a tar or tar.md5 file on your PC and flashed via Odin which is a Windows OS program.
a. Make sure you have your tar file stored on your PC.
b. Reboot your phone to Download Mode [shut down your phone, then hold down the Home + Volume DOWN Buttons and press the Power Button for about 2 seconds until a Warning screen appears. Press Volume UP to continue to Download Mode.
c. Connect your phone via usb and the first box at the top under ID:COM should turn blue and have some text in it. If you are using Download Mode on your phone for the first time then you will notice drivers being installed to use it.
d. The site or page you downloaded the file from will usually give you instructions to set Odin but if not you want to load boot/recovery/system files to the PDA location and have 'Auto Reboot' and 'F.Reset Time' ticked and nothing else.
e. Click on 'Start' to start the flash. You can see what is happening in the text box in the lower left.
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
ChangeLog
ToolKit v4.1.0 (9th April 2013)
+Updated complete Toolkit structure for easier support and faster updates
+Added GT-N7100T and GT-N7105T models to the support list
+Added 4.1.2 support for many models. See screenshot for full list
+Updated CWM and TWRP Recovery to the latest model specific version
+Added TWRP NAND backup/restore procedure to backups section
+Updated SuperSU Root procedure to V1.25
+Updated Samsung usb drivers to 1.5.18.0
+Added more error detection and updated many parts of the Toolkit procedures
+Added Activation option and support procedure for new builds to Model Screen
+Updated Stock firmware download section with new Samsung images
+Adb server is now shut down if you exit from Model Selection screen
+Added more error control Toolkit processes
+Updated mods section
ToolKit v3.0.0 (18th December 2012)
+Rewrote soo many parts its hard to list them all
+Changed the Model Selection screen
+Split up images for all supported models to make them easier to distinguish
+Added support for Verizon, GT-N7105 (lte), AT&T and Korean SK Telecom
+Added new options to Root/Unroot Screen
+Added root+busybox+rename recovery restore files via Custom Recovery
+Added Root/Unroot via Sideload feature in Recovery
+Updated CWM Recovery to 6.0.1.9
+Updated TWRP Recovery to 2.3.2.3 for all available Models
+Updated SuperSU to 0.99
+Added Device Information Screen
+Added instant reply donate link to Toolkit
+Soo many more behind the scene changes
ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
+Added FULL support for TMobile (SGH-T889)
+Added FULL support for US Cellular (SCH-R950)
+Updated SuperSU Root zip file to V0.96
+Updated CWM Recovery to V6.0.1.5
+Added TWRP Recovery V2.3.1.1
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added option in ALLINONE Root routine to flash cwm or twrp Recovery
+Improved Root procedure on all builds
+Made some edits for Toolkit stability
+More tweaks
ToolKit v1.0 (7th Oct 2012)
+First version of Samsung Galaxy Note2 ToolKit released
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
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. 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. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
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 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. 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 and AVG Free) 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. 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 flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.
**RESERVED FOR MANUAL INSTRUCTIONS**
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U
How To Manually Boot to Custom (or Stock) Recovery
http://www.youtube.com/watch?v=9m6Uugh8ps8&hd=1
Sent from my SPH-L710 using Tapatalk 2
Can i unroot with toolkit?.Many thank for awesome work..:good:
thank you! worked like a charm!!!
simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
Yes you can.
Mark.
So does this add to the flash counter?
Tiffany84 said:
So does this add to the flash counter?
Click to expand...
Click to collapse
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Mark.
simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
mskip said:
Yes you can.
Mark.
Click to expand...
Click to collapse
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
GREAT work and thank you for getting this into an easy toolkit form, as many people will be helped out by this!! I was already rooted, as some others were too, but you created a tool that needs a BIG :good:
teshxx said:
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
Click to expand...
Click to collapse
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Is TWRP supported on the TMo Note II?
mskip said:
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Click to expand...
Click to collapse
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Oh ok. I would, but I haven't rooted mine yet. Still deciding if I want to keep my grey one or exchange it for the white lolol. Hopefully, someone who is already rooted will be kind enough to do it for you.
Thanks for your effort and time.
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
PM sent w/ link for stock T889 kernel.img. build number is the file name. sorry i can't help with stock recovery.img since i already rooted and flashed CWM recovery.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
hey mark, if u wanna post or PM me instructions i'll get u the mount points.
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
So nice to see you here. Thanks for all u do!!
Sent from my SGH-T889 using Tapatalk 2
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
LvDisturbed1 said:
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
Click to expand...
Click to collapse
I can use my extSD with CWM so it's something on your end. I used the toolkit for the N7100 but same stuff...
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
I just sent you a pm with the stock recovery.img from my device(T-Mobile Galaxy Note 2). My build number is JRO03C.T889UVALJ1. Hopefully this gives you what you need. Thanks again.
---------- Post added at 03:53 AM ---------- Previous post was at 03:43 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Just sent you a pm with the mount points for the T-Mobile Galaxy Note 2. Thanks for this tool. It's incredible.
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
CrankyPants said:
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
Click to expand...
Click to collapse
Restore you stock ROM nandroid. Look for it in here COLLECTION of Stock backup's seeing as you really didn't bother to provide us with the relevant and more important information such as the CID and Main software version you were on before you decided to mess your phone up and I doubt you made a backup of your device before doing it.
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
I guess I will be the "bad guy" but why are you messing with your phone when you have no clue what you are doing?
Everyone starts somewhere. Im sure we all learned a lot of what we know now by making lots of stupid mistakes. This logic rings true for life... not just phones.
lucas.scott said:
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
Click to expand...
Click to collapse
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
CrankyPants said:
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
Click to expand...
Click to collapse
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Jyotirdeb said:
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Click to expand...
Click to collapse
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
CrankyPants said:
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
Click to expand...
Click to collapse
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
leongwengheng said:
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
Click to expand...
Click to collapse
Good choice on the videos, these days reading is a bit to tedious for most people. Heck, they don't even read "STOP" on the STOP signs anymore, just drive straight past
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
leongwengheng said:
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck at school then and later on in your job
Lucky boy having such a commited community here. You could've quite easily ended up with a £600 paper weight. Might want to show some appreciation to everyone holding your hand through a process that you should've read about before doing anything. Must admit, I did like the 'I just kept hitting next without knowing what I was doing', that's probably the best thing I've read lol lol.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BerndM14 said:
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
Click to expand...
Click to collapse
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
CrankyPants said:
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
Click to expand...
Click to collapse
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
BerndM14 said:
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
Click to expand...
Click to collapse
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
CrankyPants said:
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
Click to expand...
Click to collapse
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
BerndM14 said:
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
Click to expand...
Click to collapse
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Jyotirdeb said:
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Click to expand...
Click to collapse
To get getvar all you'll need fastboot commands, will fastboot commands even work if he MIGHT not have enabled USB Debugging or for that matter haven't accepted the RSA key?
That's why I asked about the recovery as well though. I saw that on hasoon's toolkit the flashing of a custom recovery was like the next step on the process which means that this guy should at least have a custom recovery already installed.
My goal for this thread is to gather as much info for the BLU Life One X 2016.
Specs
Screen: 5.2", 1080 x 1920 pixels, ~424 ppi, Gorilla Glass 3
Memory: 2 GB RAM, 16 GB storage, microSD slot (up to 64GB)
Camera: 13 MP rear, 5 MP front, LED flash front & rear, [email protected] video
Battery: Li-Ion 2900 mAh
Chipset: Mediatek MT6753
CPU: Octa-core 1.3 GHz Cortex-A53
GPU: Mali-T720
Model: L0070UU
Links & Other General Resources
BLU Products
Amazon: Black - White
GSMArena
BLU Products Development Team (Google+)
L0070UU User Manual
ClanGSM claim to have firmware files for our phone but it would cost $$$ to download: / mnt / data / ftp / Flashes / BLU / Life One X / L0070UU /
Similar Phones
Wiko Fever (GSMArena)
Micromax Canvas 5 (GSMArena)
XOLO Black 1X (GSMArena)
Elephone P8000 (CM12.1) and P6000 Pro
Quantum Go 4G (PhoneMore)
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Note: While I use a variety of operating systems on a regular basis everything here will be Windows 10 focused.
ADB & Fastboot
Before doing most things mentioned below you will need "adb" and "fastboot" installed. Two of your options are to install the Android SDK Tools or the Minimal ADB and Fastboot tool. If you are somewhat new to this I highly recommend the second one. Go here, download the latest version (1.3.1 as of this writing), and install it. When setup is complete you should have an icon for the Minimal ADB and Fastboot tool.
Note: I highly recommend you add "C:\Program Files (x86)\Minimal ADB and Fastboot" to your PATH variable in Windows. This way you can open a Command Prompt anywhere and use adb or fastboot.
Drivers
I recently setup a 5th gen Kindle Fire 7" tablet on my Windows 10 desktop. Because the BLU Life One X 2016 and the Kindle Fire are similar enough it just worked. To use the Amazon drivers you can find them on this page: https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing. The direct link is https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip. Extract the zip file and then run KindleDrivers.exe.
Unlock Bootloader, Install Custom Recovery, and Install Root
Note #1: All credit for this guide goes to manos78's post for rooting the Wiko Fever!!! You can check it out here.
Note #2: I use Windows 10 on every PC I own. I assume Windows 7 and 8 should work just fine but cannot test that.
Note #3: The following assumes you have setup ADB and the proper drivers before beginning. I will try to detail that at a future time.
Note #4: Your phone will be completely erased. If there is anything you want to save do so beforehand.
1) Unlock Bootloader
Power on the phone and skip through all of the setup options
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
Type fastboot oem unlock
Press Volume Up to say Yes and wait for this to finish
Type fastboot getvar all and look for (bootloader) unlocked: yes
Type fastboot reboot
You should see your phone reboot a couple times as it erases the phone
2) Install Custom Recovery
Note #1: We will flash a version of CWM or TWRP that was built for a Wiko Fever as they appear to be fully compatible with the BLU Life One X 2016. Go to this thread and download the latest CWM (http://www.sendspace.com/file/4g87bj) or TWRP (http://www.sendspace.com/file/y4jel8). Extract the img file. Again, many thanks to manos78 for CWM and hanuma for TWRP!!!
Power on the phone
You can configure your phone now or just skip through all of the setup options and do that later
Go to Settings -> About device
Tap Build number five times to enable Developer options
Go to Settings -> Developer options
Enable OEM unlocking
Enable USB debugging
Plug the phone in to your PC and authorize it
Open a Command Prompt to wherever you extracted the .img file
Type adb reboot-bootloader
The phone should reboot and in a very tiny font at the bottom you should see => FASTBOOT mode
Type fastboot devices to verify that your PC sees it correctly
For CWM type fastboot flash recovery recovery-custom-wiko-fever.img or for TWRP type fastboot flash recovery TWRP_WikoFever_2.8.7.0.img
Type fastboot reboot
Note: If your phone does not reboot then just hold the power button until it turns off. Hold the power button again until it turns back on.
3) Install Root
Note: While there are newer beta versions of the SuperSU app I am not sure if they will work properly on our stock rom. You can test one of those out and report back but I would recommend you do a full backup beforehand.
Download BETA-SuperSU-v2.52.zip and save it to the phone's internal memory or an inserted microSD card
Plug the phone in to your PC
Open a Command Prompt
Type adb reboot recovery
You should now be in CWM. Go to Install zip, find BETA-SuperSU-v2.52.zip, and install it
When it finishes go to Go Back -> Reboot Phone -> No
Once the phone boots up launch SuperSU and configure it as you like
Xposed
Download the latest version of Xposed for sdk22 and arm64 from here. As of this writing it is xposed-v79-sdk22-arm64.zip. Also download XposedInstaller_3.0_alpha4.apk and xposed-uninstaller-20150831-arm64.zip (just in case).
Reboot into CWM or TWRP and do a full backup
Install xposed-v79-sdk22-arm64.zip and then reboot
Cross your fingers and hopefully your phone will start properly. Mine rebooted like five times during the "Android is starting" step but finally finished.
Once your phone boots up install XposedInstaller_3.0_alpha4.apk
ViPER4Android
ViPER4Android adds audio effects to your Android device and is beloved by many. First we will install SELinuxModeChanger and then ViPER4Android. Special thanks to Tha Watcher for his original write-up here.
1) SELinuxModeChanger
Go to the SELinuxModeChanger page on F-Droid, download the latest version (3.2 as of this writing) or use this direct link, and save it to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\com.mrbimc.selinux_42.apk
On the phone you may see a prompt saying Installation Blocked. If so, click the little triangle and tap Install anyway (unsafe). If you see a failure just do it again and it should work.
Launch the SELinuxModeChanger app on your phone, grant it root permissions, and click Permissive
Note: If you have any issues with SELinuxModeChanger then head over to the XDA thread.
2) ViPER4Android
Download the latest version in zip format from here and extract ViPER4Android_FX_A4.x.apk to your Desktop
Launch Minimal ADB and Fastboot and type adb install %USERPROFILE%\Desktop\ViPER4Android_FX_A4.x.apk
Launch the ViPER4Android app on your phone, click Yes when prompted, click Super Audio Quality, and then click OK
Grant root access when prompted
Click OK
Reboot your phone
Note: Once your phone reboots you can start configuring ViPER4Android. I cannot really help much with that but feel free to look over the official XDA thread or their Settings Explained page on the official website.
Engineering Mode
Note: If I were you I would not change anything unless you absolutely know what you are doing!
I cannot seem to get the phone codes to work. You can install the MTK Engineering Mode app from the Google Play Store.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Frequently Asked Questions
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
MTK Droid Tool
MTK SP Flash Tool
Latest Version: 5.1548.00.000
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Q: How can I tell if my model is the BLU Life One X 2016?
A: Go here and see if it is the same model.
Q: When I try to use adb root I get the following error: adbd cannot run as root in production builds
A: You can purchase and install [root] adbd Insecure by Chainfire. Once installed, launch the app, grant it root access, and then check Enable insecure adbd and Enable at boot
Q: How do I (re)mount /system as read-write?
A: Install [root] adbd Insecure as mentioned above, open a Command Prompt, type adb root, and then adb remount rw
Q: How can I disable the audio that plays when starting up or shutting down my phone?
A: Using a file explorer with root access, or an adb shell, delete or rename (with .bak at the end) /system/media/bootaudio.mp3 and /system/media/shutaudio.mp3 and then reboot your phone.
WARNING: *I* cannot be held responsible for anything *you* do to *your* phone!
Reserved #4
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Has anyone been brave enough to try this yet?
---------- Post added at 02:16 AM ---------- Previous post was at 02:12 AM ----------
I'm receiving my phone tomorrow so i might be the guinea pig...lol
Did this last night on my phone. Most difficult part for myself was finding the correct drivers as this is my first mediatek device. Ended up being my fifth attempt that had the correct set.
After I had the drivers it was extremely similar to a nexus process.
Do you have a link to the drivers
Sent from my 6045X using Tapatalk
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
OK thanks
Sent from my 6045X using Tapatalk
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu? They both have a MT6753, so from what I understand from reading on XDA it might work. You might need to make changes suggested at http://forum.xda-developers.com/showthread.php?t=2701283.
Click to expand...
Click to collapse
Unfortunately the guy that was bringing up the elephone p8000 has sold it and subsequently not be supporting it any longer. I'm happy enough there is custom recovery options and root. An AOSP ROM would be nice, but naturally the custom gestures would be lost.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
hottcakes said:
I must inform you that I am still running good ol' Windows 7 so there's that.
All credit on my end comes from [Tutorial] Flash/Root/update elephone P8000 by vetkak and the first step with the link. Its not a real link, but a copy and past of the mega.co link had the proper drivers.
If you're on Windows 10 there is a separate thread out there somewhere with instructions for that.
Click to expand...
Click to collapse
I was trying to using the link to download the driver, but the mega site asked for "decryption key" before I can download. Is there a key available to share? Thanks,
Tha Watcher said:
I did but from the original Wiko Fever thread instructions. I did this a couple of weeks before he actually posted this thread and I made my own instructions that I think are clearer and more concise than the Wiko thread; however, rogersa2k's guide is pretty thorough and easy to understand besides the following correction....
The fastboot reboot after flashing the custom recovery doesn't yield the same results, because when I did that it did NOT work! I corrected it by help from a comment by member yrude (and as hottcakes mentions above) and made my own instructions with the addition of adding the installation for Viper4Android. But I hesitate to post it on XDA as I don't want to step on any toes. However, I did post it on Google+, Amazon and GSMarena. If people want this alternate guide and notify me to post it, then I will. Otherwise, I'll keep it off XDA.
Click to expand...
Click to collapse
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
clu1688 said:
Pls post yours here. I saw your Amazon comment and tried to follow it. Everything seemed to work till I run "fastboot oem unlock" then the PC just displays "Waiting for device response...." and my BLOX never showed any response on screen. I suspected that I did not have the driver for this particular type cellphone device. Thanks,
Click to expand...
Click to collapse
I appreciate that but the only way I'd post it in this thread is if the OP says it's fine. I do not like hijacking or taking over other people's threads.
It sounds like ADB is actually not loaded or working on your computer or otherwise you wouldn't get that message. I could be wrong, though. To test to see if it is indeed working and drivers are properly loaded, what does it respond when you type: adb devices
SCrid2000 said:
Have you tried porting the Elephone rom for the Blu?...
Click to expand...
Click to collapse
Not yet, but I do plan to try to start with that. It's nice that Elephone released the source code for the P8000 so that could help as well. If I ever get to this I will need lots of help.
jmcneil919 said:
Has anyone been brave enough to try this yet?
Click to expand...
Click to collapse
Everything that *I* post in the OP will be something that I tested on my own device first unless I specifically mention otherwise.
hottcakes said:
I feel like it needs mention that after flashing the recovery (I used the TWRP flavor) that after the fastboot command you need to immediately power off the phone, instead of rebooting, then do the volume up + power button press to get to the custom recovery.
Click to expand...
Click to collapse
I will add a note about that but some of us had issues so I chose the alternate method that has worked for me the first time every time.