This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM4/5) recovery
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
Donate
There have now been nearly 8.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Yellow triangle and flash counter
On Ice Cream Sandwich builds (only), get rid of the yellow triangle and flash counter after flashing using my Triangle Away app!
Features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Busybox v1.16.2androidminimal (from CWM)
- Integrated CWM 4.0.0.2
CF-Root v4.1 and older
- Superuser 2.3.6.1
- "Secure" mode
CF-Root v4.2 and newer
- Superuser 3.0
- "Insecure" mode
CF-Root v5.0 and newer
- "Insecure" mode
- Superuser v3
- Busybox v1.19.2
- Integrated CWM v5
- CWM Manager v3
CF-Root v5.4 and newer
- SuperSU (replaces Superuser)
- "Fake-secure" (ro.secure=1, but ADB is patched to run as ro.secure=0)
- Fixed ICS SD card issue
CF-Root v5.5 and newer
- CWM updated to v5.5
Instructions - ODIN (short)
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
Instructions - ODIN (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Instructions - If you already have CF-Root
- Copy the zip file to your SD card
- Stop sharing SD card with computer over USB, unplug the cable, etc
- Applications -> CWM -> Flash kernel. Select the ZIP file on your SD card.
- Done
Other kernels
Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager app may remain, but probably won't do anything useful.
ClockworkMod
CF-Root includes a custom version of CWM4. I always make custom versions, as the originals often do not take some Samsung specific things into account.
CF-Root/CWM4 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- Booting into recovery will immediately give you CWM. The standard recovery will only be started if a Samsung package is detected.
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
NOTICE: On CF-Root before 4.0, the kernel was not backed up or restored, on 4.0 it is. This can also cause issues restoring pre-4.0 nandroid backups. In that case, use "advanced restore" inside CWM4 and restore a backup's portions one by one.
CWM Manager
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011). You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups (CF-Root v5.0: including partition selection)
- Delete backups
- Install APKs
- Flash CWM3/4/5 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) - without changing warning triangle status or increasing flash counter
--- without changing warning triangle status or increasing flash counter
- CF-Root v5.0: Flash complete firmwares (seperate files as well as .tar and .tar.md5 archives, dump files in /sdcard/external_sd/firmware folder)
--- without changing warning triangle status or increasing flash counter
--- can pre-root new firmwares during flash
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility !
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Custom boot animations and binaries
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
And custom boot binaries:
- /data/local/bootanimation.bin
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Help! Which file do I use ?
Listen closely, for I will say zis only once!
Go to Settings -> About phone -> Kernel Version. Note the string present there:
2.6.35.7-I9100XXKG1-CL349526
What matters most (KG1) in this case, is in bold. Try to find the matching file under downloads:
CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip
The XX and OXA identifiers are not that important. Usually a "KG1" kernel is a "KG1" kernel, and that is that. Sometimes (pretty rare) it happens there will be multiple different kernels with the same name in different firmwares, that are actually different. If this happens, they are usually only very minor changes and you should expect them to still be fully compatible. I include the "XX" and "OXA" identifiers so the very advanced users can deduce from which full firmware I have taken the kernel file.
Don't worry too much, just find the matching download and use it. What if there is no matching download ? You can ask me to make one, but I can tell you right now, I very very rarely make CF-Root's for kernels on request, unless it is the very latest kernel that has been released by Samsung. In the latter case, be sure to let me know. If there's no match and I'm not making one, try finding the closest match. You should treat "KG1" as a number, but instead of 1-9, we have 1-9, A-Z (where A would be 10, and Z would be 35). "KG2" is really close to "KG1", "KF1" is not close to "KG1" at all. I hope that makes sense.
Download
These are general-purpose downloads. See the posts following this one for the kernels.
Getting rid of that pesky warning triangle during boot, and upgrading your firmware
Getting rid of that pesky warning triangle during boot
On ICS, there is now a much easer way: Triangle Away
It is definitely possible to remove that pesky warning triangle during boot when running a custom kernel, though you should be well aware that this method does NOT reset the custom kernel flash counter. The steps are not complicated, but they aren't easy either, so read well.
(1) Make sure you have CF-Root flashed (see the first post). You must have the "CWM Manager" app available.
(2) Make sure you have the same version of CF-Root extracted until you have the zImage file. (ZIP --> extract --> TAR --> extract --> zImage).
(3) Push the zImage file to /sdcard . It must still be called zImage !
(4) Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)
(5) Reboot into download mode (adb reboot download, or boot the device with home and volume-down pressed)
(6) Fire up ODIN, and flash the Samsung kernel
(7) Boot the device with the stock kernel. CWM Manager will still be available.
(8) Start CWM Manager, select Flash Kernel, and select the zImage from CF-Root you previously put on your SD-card. The kernel will flash and the device will reboot.
(9) You will now notice you no longer have the warning triangle during boot, but you are actually running CF-Root with all it's goodies!
(10) In the future, if you only use the Flash Kernel option inside CWM Manager instead of ODIN, the triangle will not return, neither will your flash counter increase. But keep in mind, that CWM Manager can only handle a direct "zImage" if you are NOT running a kernel with full busybox support (this is currently needed for flashing kernels out of .TAR and .ZIP files)
CF-Root v5.0: Upgrading your firmware
Important: This works ONLY on a CF-Root kernel !
CWM Manager has the ability to flash firmware parts either from separate files (zImage, factoryfs.img, etc) or from .tar / .tar.md5 files that they usually come packaged in.
- Download the firmware you want to flash
- If you have a ZIP or RAR file, extract it until you have seperate files, or .tar / .tar.md5 files
- Create a folder named 'firmware' on your external SD card
- Copy the files you want to flash to this folder ( /sdcard/external_sd/firmware ). factoryfs ("system") is mandatory part at the moment.
- TIP: If you are flashing a new firmware that already has a CF-Root kernel available, put it in the 'firmware' folder as well in zImage or .tar form (NOT .zip). Select it when asked which kernel to use, then use the "Flash normally" option later on.
- Open the CWM Manager app
- Select "Flash stock firmware"
- At this point, CWM Manager will tell you about the firmware parts it has found, and which ones it will flash. It will also give you warnings about bootloaders and PIT files if those were found. If some firmware parts are present multiple times, it will ask you which file to use as source.
- If what you are flashing includes both kernel and system parts, CWM Manager will warn you about this as you are about to lose root. It will provide you with three options:
1: Keep CF-Root kernel
Keeps the current CF-Root kernel, only flash the other parts. You will not lose root or CWM Recovery. You can flash a newer CF-Root kernel later (or maybe you have already done so), see 3.1 above.
2: Pre-root system
Flashes both kernel and system parts, but roots system during the flash. You will lose CWM Recovery, but you will keep root (if all goes well). The CWM Manager application will also remain, and allow you to flash the correct CF-Root kernel at a different time (if you have not done so before), see 3.1 above.
3: Flash normally
Doesn't do anything specific. If the kernel you are flashing is not a CF-Root (or similar) kernel, you will lose root, and CWM Recovery.
- CWM Manager will reboot into CWM Recovery, and will flash the firmware, rebooting afterwards.
The goods
It is important you guys let me know of new stock kernels and ROMs, else no new CF-Root's will be made
Note that I generally do not "back-port", in other words, I rarely make CF-Root's for old kernels/firmwares, and new features and fixes generally only appear for the very latest kernel/firmware.
NOTE: Removed < 4.0 version of CF-Root
v4.0 release notes: http://forum.xda-developers.com/showpost.php?p=14733439&postcount=534
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip
CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip
CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.zip
CF-Root-SGS2_XW_OJV_KF1-v4.0-CWM4.zip
Yet more downloads!
Notice: XX_OXA_KG1 is 2.3.4, while XW_MOT_KG1 is 2.3.3 ! Make sure to check which version you need.
XX_MOT_KG1: Untested
ZS_OZS_KG2: Untested
JP_XSG_KG2: Untested
XX_OXA_KG2: Untested
CF-Root-SGS2_XX_OXA_KF2-v4.0-CWM4.zip
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4.zip
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4.zip
CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip
CF-Root-SGS2_XW_MOT_KG1-v4.1-CWM4.zip
CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip
CF-Root-SGS2_JP_XSG_KG2-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KG2-v4.1-CWM4.zip
Yet more downloads!
XX_OXA_KG3: Untested (by me)
XX_OXA_KG6: Tested
XX_OXA_KG5: Untested (by me)
JP_XSG_KG5: Untested (by me)
XX_MUL_KG7: Untested (by me)
XX_OXA_KH1: Tested
XX_OXA_KH3: Untested (by me) (thx to robbielicious for the stock kernel)
XX_XEU_KH4: Tested
CF-Root-SGS2_XX_OXA_KG3-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KG5-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KG6-v4.1-CWM4.zip
CF-Root-SGS2_JP_XSG_KG5-v4.1-CWM4.zip
CF-Root-SGS2_UH_MUL_KG7-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KH1-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KH3-v4.1-CWM4.zip
CF-Root-SGS2_XW_XEU_KH4-v4.1-CWM4.zip
Even more downloads!
XW_NEE_KI4: 2.3.4
XX_OXA_KI3: 2.3.5
CE_XEN_KI2: 2.3.4, CF-Root v4.2, SU 3.0, "insecure"
XX_OXA_KI3-42: 2.3.5, CF-Root v4.2, SU 3.0, "insecure"
XW_NEE_KI4-42: 2.3.4, CF-Root v4.2, SU 3.0, "insecure"
XW_NEE_KI8: 2.3.5, CF-Root v4.3, SU 3.0.2, "insecure"
XX_XEO_KI4: 2.3.5, CF-Root v4.4, SU 3.0.5, "insecure"
(Sorry for the filename weirdness, my automated buildscript made a booboo )
CF-Root-SGS2_XW_NEE_KI4-v4.1-CWM4.zip
CF-Root-SGS2_XX_OXA_KI3-v4.1-CWM4.zip
CF-Root-SGS2_CE_XEN_KI2-v4.2-CWM4.zip
CF-Root-SGS2_XX_OXA_KI3-42-v4.2-CWM4.zip
CF-Root-SGS2_XW_NEE_KI4-42-v4.2-CWM4.zip
CF-Root-SGS2_XW_NEE_KI8-v4.3-CWM4.zip
CF-Root-SGS2_XX_XEO_KI4-v4.4-CWM4.zip
Even more downloads!
CF-Root-SGS2_XW_LUX_KJ1-v4.4-CWM4.zip
CF-Root-SGS2_XW_XEF_KJ2-v4.4-CWM4.zip
CF-Root-SGS2_XW_XEU_KH4-v5.0-CWM5.zip
CF-Root-SGS2_XW_LUX_KJ1-v5.0-CWM5.zip
CF-Root-SGS2_XW_XEF_KJ2-v5.0-CWM5.zip
CF-Root-SGS2_XW_XEN_KJ3-v5.0-CWM5.zip
CF-Root-SGS2_XW_XEN_KK2-v5.0-CWM5.zip
CF-Root-SGS2_XW_OXA_KK5-v5.0-CWM5.zip
Even more downloads!
KL1 (GB): Untested
KL3 (GB): Untested
LA2 (GB): Untested
KP1 (ICS): Untested
KP2 (ICS): Tested, but since this is a new Android version, I'd still expect some issues
KP4 (ICS): Untested
KP8 (ICS): Tested, seems fine to me
GB:
CF-Root-SGS2_XW_INU_KL1-v5.0-CWM5.zip
CF-Root-SGS2_DX_THL_KL3-v5.0-CWM5.zip
CF-Root-SGS2_XI_ITV_LA2-v5.0-CWM5.zip
CF-Root-SGS2_XW_OXA_LA4-v5.0-CWM5.zip
ICS:
CF-Root-SGS2_XX_OXA_KP1-v5.1-CWM5.zip
CF-Root-SGS2_XX_OXA_KP2-v5.1-CWM5.zip
CF-Root-SGS2_XX_OXA_KP4-v5.2-CWM5.zip
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5.zip
CF-Root-SGS2_XX_OXA_KPA-v5.2-CWM5.zip
CF-Root-SGS2_XX_OXA_LP1-v5.2-CWM5.zip
CF-Root-SGS2_XX_OXA_LP2-v5.2-CWM5.zip
CF-Root-SGS2_XX_OXX_LP6-v5.2-CWM5.zip
CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5.zip ***
CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5-PROPER.zip ***
CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.zip ***
CF-Root-SGS2_XX_OXA_LPJ-v5.3-CWM5.zip ***
CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.zip ***
CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.zip (use also for LPE)
CF-Root-SGS2_DX_XTC_LP7-v5.4-CWM5.zip
CF-Root-SGS2_XW_O2U_LP3-v5.4-CWM5.zip
CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5.zip
CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip
CF-Root-SGS2_BU_VOD_LPC-v5.4-CWM5.zip
CF-Root-SGS2_XW_XSA_LP8-v5.4-CWM5.zip
CF-Root-SGS2_XW_KPN_LP9-v5.4-CWM5.zip
CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip
CF-Root-SGS2_XX_NEE_LPD-v5.4-CWM5.zip *old*
ICS - CF-Root v5.5/6:
CF-Root-SGS2_XX_NEE_LPD-v5.5-CWM5.zip
CF-Root-SGS2_XW_OXX_LPE-v5.5-CWM5.zip
CF-Root-SGS2_XW_OXI_LPF-v5.5-CWM5.zip
CF-Root-SGS2_XX_OXA_LPW-v5.5-CWM5.zip
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5.zip
CF-Root-SGS2_UH_UVC_LPK-v5.5-CWM5.zip
CF-Root-SGS2_XW_DBT_LPI-v5.5-CWM5.zip
CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip (UPDATED)
CF-Root-SGS2_XW_NEE_LPO-v5.6-CWM5.zip
CF-Root-SGS2_XW_NEE_LPT-v5.6-CWM5.zip
CF-Root-SGS2_XW_XEZ_LPU-v5.6-CWM5.zip
CF-Root-SGS2_XX_XEO_LQB-v5.6-CWM5.zip
CF-Root-SGS2_XW_NEE_LPX-v5.6-CWM5.zip
CF-Root-SGS2_XW_NEE_LPY-v5.6-CWM5.zip
*** = problems mounting secure storage
Will probably hammer the f5 button anyway
CF-Root placeholder... good to hear that.. got 1 hour of wait, will do happily
Alright, here we go! Thread opened!
Keep in mind, I've only had the device in-hand for about 8 hours now, so not everything is as fully tested as might be wished for. You are all guinea pigs
Good deal, he didn't even have his GS2 for a day yet.
Sent from my GT-I9100 using XDA Premium App
10S156733U233402E
Thanks Chainfire..
You deserve this.. Put it towards a SGS3.
Installing now..
sweet finally got cwm3!!! flashing now!
Have a beer on me
Transaction ID: 7B567959WC141844X
Thanks for your hard work
Will be keeping a close eye on this thread
Chainfire, thank you for your awesome work once again.
You mention above about the "custom kernel flash counter", is this Samsungs way of keeping track of what we're upto? Voiding warranty etc?
If so, is there an easy way to reset it?
Thanks man.
madpete said:
Chainfire, thank you for your awesome work once again.
You mention above about the "custom kernel flash counter", is this Samsungs way of keeping track of what we're upto? Voiding warranty etc?
If so is there a way to reset it?
Thanks man.
Click to expand...
Click to collapse
Pretty much to keep track of us, yes. It can be reset with an USB JIG (there's a thread about it in this forum), but according to some, this does reset the custom kernel flash to 0, but it turn increments a counter-reset counter...
So err....
I've spent some time trying to find where this counter is stored and how to reset it, but so far no dice. I know a lot of places it ISN'T at now, though
Good news, the CWM! When It goes to final version I'll flash the phone. Thanks for your work!
paolol8768 said:
Good news, the CWM! When It goes to final version I'll flash the phone. Thanks for your work!
Click to expand...
Click to collapse
You are assuming there IS such a thing as final
Just ordered by SGS2, really pleased we have CWM3 already.
Related
so i rootes my bell sgs2 but never really thought about custom roms. now i want to get a custom rom going but when i try to get to recovery mod it just goes into the stock recovery program so installing the roms fail. when i rooted i flashed the rooted cf-root kernal then flashed the stock to get rid of the yellow triangle but still have root. did i mess up CWM some how?
if i need to reinstall can you give me steps on how to do so?
Thanks
Sounds like you got rid of clockwork flashing the stock kernel, reflash CF and you will have what you need to install roms. To get rid of the triangle you either need to follow these instructions or do it the easy way and buy a jig from ebay for a couple of quid.
http://www.forum.xda-developers.com/showthread.php?t=1103399
(1) Make sure you have CF-Root flashed (see the first post). You must have the "CWM Manager" app available.
(2) Make sure you have the same version of CF-Root extracted until you have the zImage file. (ZIP --> extract --> TAR --> extract --> zImage).
(3) Push the zImage file to /sdcard . It must still be called zImage !
(4) Find an original Samsung signed stock kernel (preferably from the same stock firmware you have, but it's not terribly important)
(5) Reboot into download mode (adb reboot download, or boot the device with home and volume-down pressed)
(6) Fire up ODIN, and flash the Samsung kernel
(7) Boot the device with the stock kernel. CWM Manager will still be available.
(8) Start CWM Manager, select Flash Kernel, and select the zImage from CF-Root you previously put on your SD-card. The kernel will flash and the device will reboot.
(9) You will now notice you no longer have the warning triangle during boot, but you are actually running CF-Root with all it's goodies!
(10) In the future, if you only use the Flash Kernel option inside CWM Manager instead of ODIN, the triangle will not return, neither will your flash counter increase. But keep in mind, that CWM Manager can only handle a direct "zImage" if you are NOT running a kernel with full busybox support (this is currently needed for flashing kernels out of .TAR and .ZIP files)
I am no longer supporting this version of CF-Root. I have personally moved away from permanent custom recoveries. I will still be providing roots by way of CF-Auto-Root (click). The downloads in this thread will remain available, I just won't be updating them.
.
.
.
.
.
Check your device model ! Settings -> About device -> Model number. This stuff is made for the GT-I9300 and GT-I9300T, if your model number has a suffix, it may not work, or if it is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many device (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus) and has clocked over 4 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
Coming from a different device ?
If you are using to CF-Root on other devices, please do still read this entire post, because this CF-Root is different than CF-Root for other devices!
What's installed
- Root: SuperSU
- Recovery: ClockWorkMod
- Util: CWM Manager
(See the next post for installation instructions)
Kernel
Unlike CF-Root for some other devices, this iteration of CF-Root does not include a custom kernel. Your kernel remains the stock kernel, and thus goodies like insecure adbd (ro.secure=0), custom boot scripts, and custom boot animations are not supported by CF-Root. You can of course flash a custom kernel that supports these.
At the same time, this also means that there will not be a different CF-Root for every firmware revision. You can just use the latest CF-Root on any firmware version!
Root - SuperSU
The root permission management app installed by CF-Root is SuperSU. This will allow your apps to gain root (superuser) access.
Recovery - ClockWorkMod (CWM)
A custom CWM 5.5 build is included in CF-Root, taken from this thread. This provides for the ability to install custom ROMs, and do nandroid (full device) backups and restores. Now also support OTA updates, but an OTA update itself will probably remove CWM, so you need re-flash CF-Root after OTA.
Not compatible with ROM Manager ! Use the CWM Manager provided instead (installed by CF-Root automatically)
Util - CWM Manager
My management application for CWM is also installed, see the recovery thread linked above for further details. It allows you to command CWM (install a ROM, make/restore backups, etc) from normally booted Android.
Not included (yet) - Busybox
Busybox is currently not automatically installed. I will probably be adding busybox installation in the near future, but I want to test / adjust it some more before going there. (No idea what this about ? Don't worry about it !)
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
Installation
(note that the actual downloads are in the next posts)
How to install using: (desktop) ODIN
Short: unpack the ZIP download, you will end up with a TAR, flash this in ODIN as PDA, and optionally install and run Triangle Away afterwards to reset the flash counter. Beware that this should boot your device into recovery mode (for a few seconds to install SuperSU and CWM Manager) after flashing. Sometimes it doesn't, just flash it again in that case.
Long:
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Root-SGS3-vX.X.zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Root-SGS3-vX.X.tar
- Put your phone in download mode (turn off phone, then hold volume-down + home + power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.
How to install using: Mobile ODIN
(You already need to be rooted for this)
- Download and unzip the CF-Root-SGS3-vX.X.zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar file - don't extract that one
- Put CF-Root-SGS3-vX.X.tar on your internal SD card
- In Mobile ODIN, use the Open file... option and select the CF-Root-SGS3-vX.X.tar file
- If you are running the Pro version, make sure EverRoot is not enabled
- Flash!
Note that if you are flashing this together with a stock Samsung firmware, you must open the CF-Root tar file last, and this will prevent the firmware's CSC to install (which doesn't bother me, but some people care about this). Alternatively, flash the entire firmware first (with EverRoot enabled), then flash only the CF-Root tar after it has booted up.
How to install using: Heimdall (Linux)
This is hearsay, I have not tried it myself. But extract the ZIP, then extract the TAR, so you end up with recovery.img and cache.img files. If you have heimdall setup right, this should do it:
sudo heimdall flash --recovery recovery.img --cache cache.img
How to upgrade with: custom ROM
If you are flashing a custom ROM, chances are it will include root and/or recovery, and there's no manual action to take.
How to upgrade with: Samsung ROM
If you are flashing a stock Samsung ROM, you will probably lose SuperSU (root), CWM (recovery) and the CWM Manager app. Just follow the entire installation procedure again - I recommend the Mobile ODIN option here.
How to uninstall
This is by no means an extensive guide for unrooting, but if you want to sell or warranty your device, I advise the following procedure:
- Use Triangle Away to reset the flash counters, and pull the battery immediately after rebooting starts
- Boot into recovery and perform a wipe, and pull the battery immediately after rebooting starts
- Go to SamMobile and get the stock firmware for your region
- Flash that stock firmware on your device
- Let Android boot, go through device setup (without doing any logins) until Android is fully usable again
- Reboot
- Wait at least 10 minutes
- Check Settings->About device->Status and make sure Device status is not "Modified"
- Perform another factory reset
- Boot into download mode and make sure the flash counter and system status are all set to official
Some of these steps may require further info, if you can't figure it out, do some more searching, or ask people who aren't me
OTA updates
CF-Root v6.3 supports OTA updates to be flashed by the system, but when you flash an OTA, that OTA will probably replace recovery (and keep trying to do so at every boot). You need to re-flash CF-Root after applying an OTA. Just re-flashing CWM will not work and stock recovery will keep coming back.
Download
CF-Root for SGS3 v6.4:
Root: SuperSU v0.93
Recovery: CWM v5.5 :: CF-v1.5
Util: CWM Manager v3.60
CF-Root-SGS3-v6.4.zip
(Changes: important SuperSU update, better chance of install-on-flash working)
-------- OLDER VERSIONS --------
CF-Root for SGS3 v6.3:
Root: SuperSU v0.91
Recovery: CWM v5.5 :: CF-v1.5
Util: CWM Manager v3.60
CF-Root-SGS3-v6.3.zip
(Changes: massive SuperSU update, CWM can now flash OTA's, CF-Root script will try to fix stock recovery coming back after flashing CWM)
CF-Root for SGS3 v6.2:
Root: SuperSU v0.90
Recovery: CWM v5.5 :: CF-v1.4
Util: CWM Manager v3.60
CF-Root-SGS3-v6.2.zip
(Changes: recommended SuperSU update, CWM has larger text, CWM Manager should now work with GT-I9300T)
CF-Root for SGS3 v6.1:
Root: SuperSU v0.89
Recovery: CWM v5.5 :: CF-v1.3
Util: CWM Manager v3.55
CF-Root-SGS3-v6.1.zip
(Changes: external storage fixes in CWM, minor bugfix in CWM Manager)
CF-Root for SGS3 v6.0:
Root: SuperSU v0.89
Recovery: CWM v5.5 :: CF-v1.2
Util: CWM Manager v3.50
CF-Root-SGS3-v6.0.zip
--- last one ---
Thx a lot!
Now this is what I'm talking about! This is pure Epicness!
Chainfire said:
--- this post is being typed, please return later ---
Click to expand...
Click to collapse
Quite a reputation you have, 13 thanks for a post that's being written But great work CF!! Receiving mine today and good to know CF-root is immediately available!
Charismatic Chainfire
The Most Impressive and Constructive as always.
Such an incredible asset to the android community, thanks a bunch man...
Hell Yeah! My reserve comment.... eh!
Epic. We love you Chainfire!
As i understand correctly cause of the separate recovery partition we only need one CF-Root now? Not like the SGS2 were every new firmware needed a new CF-Root.
Thx
flash3d said:
As i understand correctly cause of the separate recovery partition we only need one CF-Root now? Not like the SGS2 were every new firmware needed a new CF-Root.
Click to expand...
Click to collapse
As long as CF-Root does not include a custom kernel: correct!
That doesn't mean there will not be updates
Great work as always Mr Chainfire, will be putting this to good use
What should I now install?
This here oder http://forum.xda-developers.com/showthread.php?t=1684535 ?
Reynt said:
What should I now install?
This here oder http://forum.xda-developers.com/showthread.php?t=1684535 ?
Click to expand...
Click to collapse
See the first line of the first post of the thread you just linked ...
Reynt said:
What should I now install?
This here oder http://forum.xda-developers.com/showthread.php?t=1684535 ?
Click to expand...
Click to collapse
I believe there are no difference in versions.
The earlier [RECOVERY] thread you linked gets you to install CWM recovery, then install root, and optionally install CWM Manager util.
This thread repackages all of the above into a single file flashable via ODIN (or Mobile ODIN if you have root already)
love u chain seriously sometimes i am wondering where do u find ur calmness
awesome work like always!!!
USB Jig
is the USB Jig usable here on the Galaxy S3? it works on the S2 to get Triangle away, but just asking if it works as well on the S3?
Just sent a little donation your way CF, thanks again.
Root with CF-Root in stock recovery + Back up your existing kernel
Full Un-CF-Root and Restore your previous kernel
No need to a PC, no Odin, no Yellow Triangle or counter
Only one file flashed in stock recovery
Credits to Chainfire: http://www.chainfire.eu/
If there is one popular root method, it is for sure the CF-Root kernel one.
So, do not miss the original CF-Root thread here: http://forum.xda-developers.com/showthread.php?t=1103399
Advantages of CF-Root kernel are:
Keep a stock based kernel
Add Root with Chainfire SuperSU
Get insecure kernel for developers (Root acces for ADB in recovery)
Get permanent CWM5 and Chainfire CWMManager application
Get customboot.sh support
Click to expand...
Click to collapse
Original releases need to be flashed in odin, so you need a PC.
After flashing in odin, you get a Yellow Triangle and increase your custom flash counter. You need a special application called Yellow Triangle to reset these.
If you end up with a bootloop after flash (this can happen if you flash the wrong kernel) or you want to change your mind, you have to look for your previous kernel to flash it back
Unrooting needs you to flash a full ROM in odin, simply flashing previous kernel will not remove root.
In this thread, I got rid of these issues, putting the CF-Root kernel in a zip that can be flashed directly as an update in stock recovery.
The CF-Root files included here will backup your existing kernel to external sdcard (Kernel_Backup.img)
Later, you can restore your Kernel_Backup.img and fully unroot using the attached CF-Unroot file
CF-Root + Backup existing kernel files:
- Download the CF-Root zip file corresponding to your Kernel.
- Put the CF-Root zip file on your External SD (needed for stock recovery).
- Boot into stock recovery (volume up+home+power), and select "apply update from external storage".
- Select the CF-Root zip file from external SD
- It will backup your current kernel to Kernel_Backup.img file on the external SD and apply CF-Root for your kernel
Download:
CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5-PROPER
CF-Root-SGS2_XX_OXA_LPS-v5.4-CWM5
CF-Root-SGS2_XW_XEN_LP7-v5.4-CWM5.zip
CF-Root-SGS2_XX_NEE_LPD-v5.5-CWM5.zip
CF-Root-SGS2_XW_OXI_LPF-v5.5-CWM5.zip
CF-Root-SGS2_XX_OXA_LPW-v5.5-CWM5.zip
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5.zip
CF-Root-SGS2_XW_DBT_LPI-v5.5-CWM5.zip
CF-Root-SGS2_XX_OXA_LQ5-v5.6-CWM5.zip
CF-Root-SGS2_XW_NEE_LPT-v5.6-CWM5.zip
CF-Root-SGS2_XW_XEZ_LPU-v5.6-CWM5
CF-Root-SGS2_XW_NEE_LPX-v5.6-CWM5
CF-Unroot + Restores your Backup Kernel from SD Card
To completely remove CF-Root without having to flash a full ROM in odin, use the attached CF-Unroot.zip file
It will restore your Kernel_Backup.img file from external SD and remove all root files and CWM Manager application
It is unsigned as you are supposed to only use it on CF-Root Kernel when you have a Kernel_Backup.img made with previous method
FAQ / Fix for common issues
After flashing CF-Root kernel, you end up with no root access:
This is not caused by my script, but can happen even under odin when you flash many kernels
If it happens to you, just run the attached CF-Root-Fix.zip attached here. It will put superuser and cwmmanager application in /system
You used my CF-Unroot.zip file without the Kernel_Backup.img file in ext-sd
You should have read the instructions!
But do not worry, the script should now abort and nothing is done
You can use the CF-Unroot script to flash any kernel over CF-Root kernel
Just extract the zImage or boot.img file from the kernel you want to flash and rename it to Kernel_Backup.img
It can be useful to quickly try some kernels. Keep in mind that mobile odin can also directly flash zImage files.
A last one reserved for FAQ / uploads
Done
Feel free to comment
So this is the bigger part you were talking before.. nice one. I see the successful signing gave you lot of new ideas Anyway keep up the good work Phil!
Stileth said:
So this is the bigger part you were talking before.. nice one. I see the successful signing gave you lot of new ideas Anyway keep up the good work Phil!
Click to expand...
Click to collapse
No, this part is easy. Can be helpful for many people not having PC, or when you're on the road, flash a ROM and want a root...
I am looking to make CWM permanent... but this moves me to custom kernels, while all my guides were about keeping stock kernel
Also, it will need a kernel build for each kernel version, no other way till now. So people will need to rely on me to build each kernel. Not sure I have the time for such a support.
Looking to release only a few kernels maybe.
Phil3759 said:
No, this part is easy. Can be helpful for many people not having PC, or when you're on the road, flash a ROM and want a root...
I am looking to make CWM permanent... but this moves me to custom kernels, while all my guides were about keeping stock kernel
Also, it will need a kernel build for each kernel version, no other way till now. So people will need to rely on me to build each kernel. Not sure I have the time for such a support.
Looking to release only a few kernels maybe.
Click to expand...
Click to collapse
Sounds like Chainfire's CF-Root kernel job ... big foot prints
It_ler said:
Sounds like Chainfire's CF-Root kernel job ... big foot prints
Click to expand...
Click to collapse
After all it is by far the most popular root method
This way it becomes extremely noob friendly, just flash a file in stock recovery
Yes, i will resize my foot prints when back to home
Sent from my GT-I9100 using Tapatalk 2
Yeah CF-Root is most popular because it was for long the only reliable method, but since Rachmat3 came with the injection and you polished it to current state of art perfection makes it little bit obsolete Why to bother with insecure kernel (and till now with counter increase and yellow triangle [not anymore as sorted by you again ]) when you can do it in such easy and noob proof way?
Stileth said:
Yeah CF-Root is most popular because it was for long the only reliable method, but since Rachmat3 came with the injection and you polished it to current state of art perfection makes it little bit obsolete Why to bother with insecure kernel (and till now with counter increase and yellow triangle [not anymore as sorted by you again ]) when you can do it in such easy and noob proof way?
Click to expand...
Click to collapse
Insecure kernel is useful for dev purposes and also to recover phone in some circumstances
CF-Root also comes with fixed cwm and a cwm manager, useful for dev and crazy flashers.
Also, i forget to mention customboot.sh and init.d support
So, depends on each one and its needs
Sent from my GT-I9100 using Tapatalk 2
With these zip, rooting an S2 can be done at the age of 5.
Also, for the cf-unroot, you can put any zImage file, rename it to Kernel_Backup.img and it will flash your new kernel
Sent from my GT-I9100 using Tapatalk 2
ksilver89 said:
With these zip, rooting an S2 can be done at the age of 5.
Click to expand...
Click to collapse
I think 5 is really a big number
Sent from my GT-I9100
I removed the links because I am updating the scripts
I will use edify Mount command rather than temporary busybox as this method is only for our i9100, so I find it a better approach
Uploading tomorrow new files
OP updated with following changes
CF-Root files:
Temporary busybox is now extracted to /tmp instead of /sbin. This could cause later scripts with /sbin/busybox to fail
Click to expand...
Click to collapse
CF-Unroot
Added delete /system/cfroot
Previously, if you used CF-Unroot without a Kernel_Backup.img file on external sdcard, root files were deleted and you were instructed to flash the CF-Root fix file. Now, if you forget to put the Kernel_Backup.img file, script will abort and no changes are done
Click to expand...
Click to collapse
CF-Root-Fix
Now ensures that CWMManager.apk has correct permissions
Click to expand...
Click to collapse
Added to the OP the new two files from Chainfire thread here
Just update in stock recovery (see instructions in OP)
CF-Root-SGS2_XW_NEE_LPT-v5.6-CWM5.zip
CF-Root-SGS2_XW_XEZ_LPU-v5.6-CWM5.zip
Big thanks to chainfire for these updates
sorry but it's still unclear..
with your script no traingle & flash counter increase?
tuvi123 said:
sorry but it's still unclear..
with your script no traingle & flash counter increase?
Click to expand...
Click to collapse
Yes, exactly
Sent from my GT-I9100 using Tapatalk 2
My kernel version is 3.0.15-SPH-D710.FF18-CL663858 - I'm having a hard time figuring out which kernel to DL. Can anyone help?
ctroamer1 said:
My kernel version is 3.0.15-SPH-D710.FF18-CL663858 - I'm having a hard time figuring out which kernel to DL. Can anyone help?
Click to expand...
Click to collapse
Look in the Epic Touch 4G forum. Here is i9100 one
Sent from my GT-I9100 using Tapatalk 2
This is a Heimdall/Odin flashable pre-rooted stock UCLL6. This is the exact version that was released over Kies, and contains the bone stock kernel, plus rooted system, modem, cache.img and hidden.img. There are no bootloaders in this package. With this package, you can root stock ICS without incrementing the flash counter.
If flashing this from another base, you should perform a wipe data/factory reset before flashing this, or the phone may hang on the Rethink Possible screen during boot.
This Rooted package does not include busybox. If you need busybox, you can install it from the Google Play Store.
Kernel + Modem + Cache + Rooted UCLL6 System Odin One-click Downloader (Windows only): Hotfile | Dev-Host 288.1 MB (288.10 MB - 302093604 bytes)
(md5: f58fd040a7f38746c8e72a1bdf929bb5)
Download and extract the exe package using 7-Zip, which can be downloaded from http://www.7-zip.org/download.html. Open I777UCLL6 OCD Root No BL.exe on your desktop. Connect your phone to your computer in download mode. When the downloader recognizes the phone, press start.
Click to expand...
Click to collapse
Kernel + Modem + Cache + Rooted UCLL6 System Tar Package: Hotfile | Dev-Host 287.7 MB (287.68 MB - 301654790 bytes)
(md5: db4f040a1cb531df203088d5796e33cd)
Download and extract the tar package using 7-Zip. Put UCLL6_Stock_Rooted.tar in the PDA slot in Odin.
Download the Odin3 v1.85 package from MediaFire or xda-developers, or another source of your choice. Odin3 v1.82 will also work.
Click to expand...
Click to collapse
To flash with Heimdall command line, extract the individual files from the tar and flash the components with heimdall from the commandline as follows:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img --modem modem.bin --cache cache.img --hidden hidden.img
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.2 at this writing.)
It is unknown whether the kernel in this firmware distribution contains the eMMC cap erase bug. We can only speculate. There were many reports of damage from the leaks that led up to the first ICS release, UCLE5, but the UCLE5 kernel itself did not produce very many reports of damage. I only saw two reports that could have been memory damage due to the cap erase bug, and only one of those seemed to be even half way conclusive. So it is possible it was even fixed in that release. UCLL6 appearantly fixes some of the other kernel problems that were present in UCLC3 such as the sleep of death, so it may very well be a clean kernel with regard to the cap erase bug, but this can not be verified by the developers on xda without original source, which is not available.
If you are at all worried about this, it certainly would be the safest route to use a custom safe kernel. And as a bonus, the custom kernels are likely to perform much better than stock.
Three different ways to install a customized kernel containing ClockworkMod Recovery onto your Rooted phone without incrementing the flash counter.
You must use an ICS kernel if you want the system to boot up, and it must work with Samsung firmware, and be the no-mic-swap version. If you install a Gingerbread kernel the phone will not boot.
The main Kernel options are: Siyah v4.3.3 by Ktoonsez | Siyah v5.1.1 by AJ Newkirk (use the one without mic swap)
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Mobile Odin Lite or Mobile Odin Pro
This is the preferred method to install a customized kernel onto your phone. In addition, Mobile Odin is a very useful tool that will allow you to install custom software directly on your phone without using a computer.
Mobile Odin Lite (free) can be downloaded and installed directly on your phone, or it can be downloaded to your computer and installed with adb. Alternatively, you can purchase Mobile Odin Pro for under $5.00 and install it directly from the Google Play Store. It's easier, and you'll support the developer!
To use Mobile Odin Lite, download the file attached to the OP of this thread. You may need to be a registerd member of xda forums to download this file. Download directly on your phone, or to your computer and move or copy it to your phones sdcard. Using any file manager such as MyFiles or Root Explorer, select the file and install it. You can also install it from your computer using the following adb command:
Code:
adb install MobileODINLite-v2.45.apk
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Transfer the zImage to the root of your phone's internal or external sdcard, using a usb cable or another method such as dropbox.
On your phone, open the Mobile Odin program. If you installed Mobile Odin Lite, when it prompts you to install the add-in, click cancel. If you installed Mobile Odin Pro, you will have already downloaded and installed the add-in to activate all the features in the program. With Mobile Odin Lite, you will still be able to install the kernel.
In Mobile Odin, click on Kernel or Install Kernel, find and select the zImage on your internal or external SD card, and then click on Flash Firmware.
Mobile Odin will flash the kernel and then reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
If you installed Mobile Odin Lite, and you don't want to keep it, you can uninstall it now. If you want to keep it and activate all its features, download the add-on MobileODIN_FlashKernel_I777-v1.0.apk from here and install it on your phone with adb using the instructions above.
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from a pc, using Android Debug Bridge (Windows, Linux and Mac OS)
Download and install the Android Software Developer Kit (SDK) from here. You may need to run SDK Manager with administrator privledges.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
You will need busybox. If not already installed, download and install busybox from the Google Play Store.
Download the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Move or copy the zImage into the platform-tools directory (on older installations it is the tools directory) where adb.exe resides. This will be something like (on Windows) c:\android-sdk-windows\platform-tools.
On your phone, first enable USB Debugging (Menu\Settings\Applications\Development\USB Debugging) and then plug in your USB cable, connecting your phone to your computer.
Open a command prompt. Change directory to the tools directory, then enter the following at the command line:
Code:
adb push zImage /sdcard/zImage
adb shell
$ su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
# exit
$ exit
The dd command requires superuser permission on the phone represented by a # prompt. After you type su and hit enter, look for a superuser window on your phone and give the permission. If the permission request doesn't pop up, open superuser on your phone to force the phone to prompt for superuser permission. After approval, the adb session will be listed as Unknown in superuser.
After you've finished, the code in the Command prompt window will look something like this (your command prompt and some numbers will be different):
Code:
C:\android-sdk-windows\platform-tools>adb push zImage /sdcard/zImage
4279 KB/s <4776784 bytes in 1.090s>
C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
10153+1 records in
10153+1 records out
5198492 bytes transferred in 2.558 secs <2032248 bytes/sec>
# exit
exit
$ exit
exit
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
How to Install a customized kernel containing ClockworkMod Recovery onto your Rooted phone from your phone, using Android Terminal Emulator
Download and Install Android Terminal Emulator onto your phone from the Google Play Store.
You will need busybox. If not already installed, download and install busybox from the Google Play Store.
Download (onto your PC) the file containing the kernel you want to flash, and extract from it the zImage, which contains the actual kernel.
Transfer the zImage to the root of your phone's sdcard, using a usb cable or another method such as dropbox.
On the phone, open a terminal session with Android Terminal Emulator.
A few points to be aware of:
Android is a version of linux so you are using linux commands. Linux commands are case sensitive, so you must for instance type "zImage" and not "zimage", if that is the way the file is spelled on the sd card.
Since this will be the first time you have used superuser.apk with the terminal, you may need to approve it on you phone. After that, superuser permission will be remembered.
When you first open a terminal session, you will be at the root of the phone, or essentially "/". The $ prompt means shell access, the # prompt means root file access.
You need a # prompt to complete this Step.
If your keyboard goes away, use the menu button options to get it back.
In the terminal session, type su and then enter. You will get a superuser request. Once you approve it, you will get the # prompt.
Then type the following:
Code:
dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
Press enter, wait till the zImage is copied over to the named block. (takes about 2 or 3 seconds)
To close the root session, type "exit" and enter. Use the back button to close Android Terminal Emulator.
Reboot the phone. You have now installed a custom kernel containing clockworkMod Recovery without changing the flash counter.
If you want to confirm installation of the new kernel, reboot into recovery to verify that you now have ClockworkMod Recovery. (The stock kernel has 3e recovery.) Or install CPU Spy from the Google Play Store (before you root) and compare the Kernel Info it displays with the same info from the stock kernel.
To reboot into recovery on the SGH-I777: With the phone powered off, hold down the vol up + vol down + power buttons continuously until the initial boot screen appears a second time.
^
BIG THX for ur continued contributions to the i777 community !!
Much appreciated !! :thumbup: :beer:
Sent from my SAMSUNG-SGH-I747 using xda premium
4-2ndtwin said:
^
BIG THX for ur continued contributions to the i777 community !!
Much appreciated !! :thumbup: :beer:
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
+1. Hats off to creepyncrawly :good:
But, quick question, Isn't Kernel link pointing to here for ICS
I have a question.
My unlocked i777 did not like UCLK3 (sammobile) ROM, after flashing I was being asked for sim unlock codes. Which is weird, because I had my phone for over a year flashing from rom to rom (custom roms) before I decided to try a stock rom again and found out that it can lock my phone.
So my question is, would this stock rom lock my phone? Is there a way to prevent this? I don't want to rely on unlock apps because last time it took a great deal of time to get it unlocked.
As to why would I want to go back to stock? I'm thinking of selling this phone and would like to give it away with a stock (but rooted) rom.
Thanks!
mikeflash said:
I have a question.
My unlocked i777 did not like UCLK3 (sammobile) ROM, after flashing I was being asked for sim unlock codes. Which is weird, because I had my phone for over a year flashing from rom to rom (custom roms) before I decided to try a stock rom again and found out that it can lock my phone.
So my question is, would this stock rom lock my phone? Is there a way to prevent this? I don't want to rely on unlock apps because last time it took a great deal of time to get it unlocked.
As to why would I want to go back to stock? I'm thinking of selling this phone and would like to give it away with a stock (but rooted) rom.
Thanks!
Click to expand...
Click to collapse
It could be that sim unlock is in newer samsung ROM's code, It happened to me flashing a custom ROM's new version (SuperNexus build 4) updated with the lates samsung code. Unlocking the phone is fast and easy with the free app in this thread:
http://forum.xda-developers.com/showthread.php?t=1846451
Give it a try and if the phone gets relocked use the app in the thread, it's quick and easy
I wanted to say thanks for this it saved my phone..... thanks a lot.
Sent from my SGH-I777 using xda premium
creepyncrawly said:
If flashing this from another base, you should perform a wipe data/factory reset before flashing this, or the phone may hang on the Rethink Possible screen during boot.
Click to expand...
Click to collapse
Thanks so much creepyncrawly. I flashed with Odin yesterday and it worked great. So far I haven't gotten any SOD issues. :fingers-crossed:
For anyone else like me who was already running 4.0.4 rooted with exynos but on the old base, there's a workaround so you don't have to wipe your device just to get root back. First use Samsung Kies to update your firmware to the latest UCLL6 base. (Unlike the OTA update, the Kies update doesn't fail just because you have root.) Kies does remove root during the update, but it also inspects and updates all your apps automatically. No need to back them up and reinstall them. To regain root, you can flash this without having to wipe anything since its now the same base. Worked great!
Does AJK 1.25 work with this ROM?
First off, Thank you so much for providing this creepyncrawly!
I had my phone repaired by Samsung and they updated me to the latest ROM and this was the best option to obtain root for me.
I had a snag while trying to install a custom Kernel however.
I followed the link provided for AJK. I downloaded AJK v1.25-SS Samsung. I assumed that the JB kernels also worked with the UCLL6 build, because I didn't see any kernels labeled ICS. Did I miss them or was my assumption correct? I followed the instructions in this thread (Not AJK's) to the T. When I booted the phone the Samsung Logo displayed, then The AJK logo. Then....nothing. It didn't boot properly, I waited 15mins or so. When I touched the home key or others they lit up, but nothing showed on screen.
I rebooted, same thing. I then went into AJK's thread and read the install instructions. I was able to get into CWM and I followed the instructions on his thread to the T... Same result
I then Downloaded the Siyah kernel to my SD card and installed it with CWM, by following the instructions on that thread carefully. That has been working great so far.
So my question is, Did I do something wrong or does the AJK kernel not work with this stock build? Has anyone else had similar issues?
doggyollie said:
First off, Thank you so much for providing this creepyncrawly!
I had my phone repaired by Samsung and they updated me to the latest ROM and this was the best option to obtain root for me.
I had a snag while trying to install a custom Kernel however.
I followed the link provided for AJK. I downloaded AJK v1.25-SS Samsung. I assumed that the JB kernels also worked with the UCLL6 build, because I didn't see any kernels labeled ICS. Did I miss them or was my assumption correct? I followed the instructions in this thread (Not AJK's) to the T. When I booted the phone the Samsung Logo displayed, then The AJK logo. Then....nothing. It didn't boot properly, I waited 15mins or so. When I touched the home key or others they lit up, but nothing showed on screen.
I rebooted, same thing. I then went into AJK's thread and read the install instructions. I was able to get into CWM and I followed the instructions on his thread to the T... Same result
I then Downloaded the Siyah kernel to my SD card and installed it with CWM, by following the instructions on that thread carefully. That has been working great so far.
So my question is, Did I do something wrong or does the AJK kernel not work with this stock build? Has anyone else had similar issues?
Click to expand...
Click to collapse
Try my ICS kernel (be sure to grab the no-swap version) instead of AJK. It should work fine, and is highly tuned for ICS.
That makes more sense.
i think I was confused because your JB thread was linked in this thread and the title of your thread also says ICS.
Thanks for the clarification.
Is this something suggested? I sold an s2 to a guy at work and might try to hook him up with this
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
moparfreak426 said:
Is this something suggested? I sold an s2 to a guy at work and might try to hook him up with this
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
This is the latest (ICS) stock release, with root. If he wants something really fine in a Samsung based Jelly Bean rom, you could suggest he load SHOstock3.
creepyncrawly said:
This is a Heimdall/Odin flashable pre-rooted stock UCLL6. This is the exact version that was released over Kies, and contains the bone stock kernel, plus rooted system, modem, cache.img and hidden.img. There are no bootloaders in this package. With this package, you can root stock ICS without incrementing the flash counter.
[/LIST]
Click to expand...
Click to collapse
@creepy
Any chance of reupping the files from OP. Both Hotfile links appear to be dead and I have tried Chrome, Firefox, Opera and IE.
fham said:
@creepy
Any chance of reupping the files from OP. Both Hotfile links appear to be dead and I have tried Chrome, Firefox, Opera and IE.
Click to expand...
Click to collapse
I'll create Dev-Host links for them as soon as I can get my Dev-Host account reactivated. It will probably be sometime tomorrow at the earliest.
By the way, I tried the second link, and it started downloading right away. I use IE10. I didn't let the download go to completion though. Was your problem not being able to start the download, or the download crapping out?
creepyncrawly said:
I'll create Dev-Host links for them as soon as I can get my Dev-Host account reactivated. It will probably be sometime tomorrow at the earliest.
By the way, I tried the second link, and it started downloading right away. I use IE10. I didn't let the download go to completion though. Was your problem not being able to start the download, or the download crapping out?
Click to expand...
Click to collapse
That is very gracious of you to re-up them. Do them whenever you can as there is no hurry. I used your UCLE5 Stock ICS 4.0.3 ODIN package from Dev-Host to root. I was on UCLK3 4.0.4.
I cannot get any browser to connect to hotfile. Checked if hotfile was down and it was not. Used a proxy to try the download from three different IP addresses. Still no go.
Thank you again.
In getting ready to sell this phone, I did this after performing a factory reset.
However coming from ShoStock 3 it was getting stuck on the ATT logo screen.
To fix this after running the one-click process, I had to go into recovery and do another factory reset. Then if booted up just fine.
Thanks!
Just got a text from AT&T that Jellybean was released for this phone.
Any chance of an ODIN with Root injected being uploaded for the new Jelly bean build?
I am not trying to be a troll just trying to see if it is just me and if I can find out how to fix it. After I bricked my phone and I fixed it following the steps provided I can flash any Rom but a Samsung based Rom. After I flash one the internal memory gets locked. I can't erase any files and the gallery can not show any pictures. It will say memory full. Erase some pictures or videos. But my memory has internal memory is at least 5 gigs. Has anyone had this happen or know what to do. I am open to suggestions.
Sent from my SGH-I777 using xda premium
att galaxy s 2
creepyncrawly said:
I'll create Dev-Host links for them as soon as I can get my Dev-Host account reactivated. It will probably be sometime tomorrow at the earliest.
By the way, I tried the second link, and it started downloading right away. I use IE10. I didn't let the download go to completion though. Was your problem not being able to start the download, or the download crapping out?
Click to expand...
Click to collapse
hi. sorry for my question but i was wondering if u can help. i did flash/ download this on my phone but stupid enough i forgot to do factory reset. now the phone just blinks with a battery symbol and will not go in recovery mode. can go in download mode but flashing again doesnt help. how can i recover the phone and make it to boot? thanks.
grigoriisi said:
hi. sorry for my question but i was wondering if u can help. i did flash/ download this on my phone but stupid enough i forgot to do factory reset. now the phone just blinks with a battery symbol and will not go in recovery mode. can go in download mode but flashing again doesnt help. how can i recover the phone and make it to boot? thanks.
Click to expand...
Click to collapse
You have SGH-I777? If yes...
I can't think of any reason you would get that result. Perhaps you should say exactly what you had on the phone, the reason for flashing, and the exact procedure/sequence you followed. Give as much information as you can think of, even if you don't think it is relevant.
Rooting Guide
Samsung Galaxy SII GT-I9100*
Latest SuperSU (v2.01) by Chainfire
Latest Busybox (v1.22.1) by Stephen Stericson
This is SuperSU port meant to be used as a root. I converted it from sh script to edify script for flashing it from Stock Recovery No increase in binary counter. I signed this by the powerful tool by Ryuinferno (Sign-em) so you can flash without E: signature verification failed
From old SuperSU versions to new easy
No increase in binary counter
No yellow traingle
How To Use:
Download attached zip and move it into your external microsd card
Reboot into recovery
choice "apply update from sdcard"
Select the zip and click install
For Unrooting Flash UnRoot.zip which is attachment
Thanks For Reading :good:
PS : You can use it for I9100/G/T/P/i777 and all other s2 variants
Credits :
Ryuinferno
Me :victory: :victory:
Updated SuperSU to v2.01
s2 still gets development, THANK YOU!
LeJolly said:
s2 still gets development, THANK YOU!
Click to expand...
Click to collapse
no problem
Added UnRooting Flashable ZIP
Devils advocate here
Arent you still going to have to flash a custom kernel, without the emmc bug, which will (usually) come with su anyways?
I guess what im saying is, while this can give you root without increasing the binary counter, it will still leave you with a buggy stock kernel....
For me, from stock, i do the following:
1) Flash Philz kernel and recovery from stock recovery. (wont increase binary counter, and includes CWM recovery)
2) Reboot
3) Back up efs (important)
Then either stay on stock, reboot into recovery and flash Dorimanx 8.43 branch (with su included)
Or
reboot into recovery and flash custom ROM (usually with root)
And then update su (superuser or SuperSU (better))
Thats not exactly hard to do.
stylemessiah said:
Devils advocate here
Arent you still going to have to flash a custom kernel, without the emmc bug, which will (usually) come with su anyways?
I guess what im saying is, while this can give you root without increasing the binary counter, it will still leave you with a buggy stock kernel....
For me, from stock, i do the following:
1) Flash Philz kernel and recovery from stock recovery. (wont increase binary counter, and includes CWM recovery)
2) Reboot
3) Back up efs (important)
Then either stay on stock, reboot into recovery and flash Dorimanx 8.43 branch (with su included)
Or
reboot into recovery and flash custom ROM (usually with root)
And then update su (superuser or SuperSU (better))
Thats not exactly hard to do.
Click to expand...
Click to collapse
Thanks to reply
I created this thread for who wants only root (without flashing kernel, using odin and flashing custom rom)
I think it will not leave any bug (It's only copy files) and will not do anything to kernel
and your way is good but it's still replacing kernel ( duh )
3lo0sh said:
Thanks to reply
I created this thread for who wants only root (without flashing kernel, using odin and flashing custom rom)
I think it will not leave any bug (It's only copy files) and will not do anything to kernel
and your way is good but it's still replacing kernel ( duh )
Click to expand...
Click to collapse
Exactly, my way replaces the buggy stock kernel.....thats the entire point
will this root method work on latest stock version PDA: I9100XXMS7 CSC: I9100OXAMS7 MODEM: I9100XXMS2 ??
fcornejo said:
will this root method work on latest stock version PDA: I9100XXMS7 CSC: I9100OXAMS7 MODEM: I9100XXMS2 ??
Click to expand...
Click to collapse
Yes
Thank you! works great on I9100T 4.1.2 last update. :good:
Can anyone please give us links to the last CWM & TWRP & PhilZ that works on 4.1.2 stock untill CM with 4.4.4/5+ ?
There are too many links that I don't know which are works with stock and CM11/12 ....
For i9100/T..
not work for me
invalid zip file
Awesome
but hey, does it work on other devices from other manufacturers, or only on the s2?
joaopossamai said:
Awesome
but hey, does it work on other devices from other manufacturers, or only on the s2?
Click to expand...
Click to collapse
This is only for S2
It worked. Many Thanks
Hello!I have mtk 6753 device and I want to root it but I am failed.can I root my device through this procedure.
su is nice and all but can u mabe do something with magisk? love it by the way cuz my phone doesnt wanna flash anything via odin ive tried everything already so ur a real life saver