Related
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.
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.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 3.0 Recovery
(Clockworkmod v6.0.1.5 based recovery)
Galaxy S2 - i9100 Version Only
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This is the temporary version of my custom clockworkmod recovery
For permanent one, look here
WARNING: flashing some update.zip files with format commands
can still brick your phone until you use a safe kernel, like PhilZ-cwm6.
New in v3.00
Completely revised new touch code
Much more user friendly touch experience
Lots of new features
Video Teaser:
Main menu at height setting 5 and 1
{
"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"
}
PhilZ Settings menu
Backup / Restore EFS and kernel
GUI Touch Settings
Aroma File Manager
Source code
coming soon...
Read in my kernel thread post 2 for instructions to use PhilZ Touch features like aroma and ors support[/SIZE][/B]
PhilZ Touch 3.0 recovery (clockworkmod v6.0.1.5 based):- touch interface: toggle 3 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation)
[*]new touch code completely revised compared to v2.x and older
[*]much more stable full touch mode: no more skips, jumps or wrongly validations while scrolling
[*]when you set full touch mode, it defaults to optimized settings for menu height and touch sensitivity (you still can alter them manually later)
[*]adjust scrolling touch sensitivity in 6 settings
[*]adjust menu height in 6 settings
[*]toggle vibrator on/off when using bottom virtual buttons
[*]toggle key repeat for volume up/down scrolling when maintained pressed: needs recovery restart to take effect
[*]backup/restore EFS and Kernel
[*]browse phone with root access using full GUI in Aroma File Manager: default location or browse for path
[*]support openrecovery script in 3 modes using a smart one touch menu: goomanager, default custom scripts location, browse for script
[*]mount internal and external sdcards on PC in recovery
[*]poweroff, reboot to recovery and reboot to download mode options
[*]Can be flashed in Stock Recovery
[*]Dual USB mount in recovery support (needs fixed kernel like PhilZ-cwm6)
[*]ADB root in recovery: just wait about a minute to activate
Click to expand...
Click to collapse
Why a temporary recovery?
Wipe safely on a stock kernel
Will work on any i9100 phone with ICS, even stock non rooted
No PC needed, only and android device and the zip files that you download to your sd card
Fully reversible after reboot
No Yellow Triangle and No custom counter increased
Incremental Backups to save a lot of space and time (CWM6)
Much better user interface, bigger menus, smoother scroll, safer touch, works with both touch and keys
Click to expand...
Click to collapse
Flashing instructions for stock recovery
Download philz-touch_x.xx_i9100-signed.zip, the last philz touch cwm v6.x for i9100 Galaxy S2. This version works with touch AND with keys to scroll in menus
Put the previously downloaded philz-touch_x.xx_i9100-signed.zip file on your external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the philz-touch_x.xx_i9100-signed.zip file you copied in previous step
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Click to expand...
Click to collapse
You are done
If it fails with black screen after successful flash:
read about it here: http://forum.xda-developers.com/showpost.php?p=32785650&postcount=33
It is because their recovery is not automatically restarted once killed
You can manually edit the file /sbin/killrecovery.sh in the temporary recovery zip package and modify it by adding the extra 2 lines before the #...
(make sure you edit it in something like notepad++ with EOL conversion set to unix)
so that it looks like below:
Code:
kill $(ps | grep /sbin/adbd)
kill $(ps | grep /sbin/recovery)
/sbin/recovery &
exit 1
Save the zip and try it again
Click to expand...
Click to collapse
Change log
15 nov 2012:Update to new custom touch 3.00 recovery included in PhilZ-cwm6 kernel
Read full change log in kernel thread
08 oct 2012:Update to new custom touch recovery included in PhilZ-cwm6 kernel
Wipe safely on a stock kernel, flash even update.zip files with format commands (patched update-binary)
now using CWM6 based custom touch recovery 6.0.1.4 (internal build 1.15) * Siyah source code *
DUAL USB MOUNT in recovery is now supported * Special thanks to [email protected] *
semi-touch interface with right slide to select disabled for safety: use slide up/down and left for back
include bottom virtual buttons for easier navigation
revised GUI with bigger fonts and larger menus for better readability
transparency effects in recovery menus
fixed backup format selection menu in original Koush cwm6 (was echoing previous menu)
added power off and reboot to download mode options in recovery menus
battery % level displayed in recovery
fixed some menus spelling and aspect in original recovery
Click to expand...
Click to collapse
20 Sep 2012: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **
Now, CWM6 is built from source to fix possible issues related to previous dynamically linked binary
Big big thanks to Tallustus from Team SkyFire for the support
Click to expand...
Click to collapse
19 Sep 2012: Update non touch version to 6.0.1.4
Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.4 or source changes for touch cwm6, let me know please
6.0.1.4 : version increment for ROM Manager compatibility
Click to expand...
Click to collapse
17 Sep 2012: Update non touch version to 6.0.1.3
Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.3 or source changes for touch cwm6, let me know please
6.0.1.3 many bug fixes and performance issues.
Click to expand...
Click to collapse
28 Aug 2012: Update to 6.0.1.2 - Touch (ICS only) and non touch versions
6.0.1.2 fixes some issues with /sdcard (/data/media).
Click to expand...
Click to collapse
Credits
Chenglu for his great unpack / repack tool: MAJOR CREDITS
kbc-developers for the base semi-touch code :good:
[email protected] for his touch source and great support over PM in fixing dual USB mount: MAJOR CREDITS
Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
sk8erwitskil for his recovery source (ors support, aroma file manager and efs backup/restore), a great place to start learning: MAJOR CREDITS
shoe63 for his testing and great help in porting to the N7000 Big thanks
dr.ketan for his precious help in porting to the N7000 (I don't own one), for support in the thread and for his faster mirrors: Big thanks
utkanos for his great and kind support over IRC
gweedo767 @ #Koush for sharing his new touch code source (not yet used)
myfluxi for his xxRecovery source in fixing dual usb mount
Koush for his great work on CWM6 and CM
Cyanogenmod for their scripts / initramfs
Chainfire for his support (stock recovery flash) and all his work for the Android community
superatmos and Dharam_Maniar for their great guides on unpacking/building custom kernels
Thx Phil, great job as usual!
Odoslané z GT-I9100 cez Tapatalk 2
Thank you
I hated the CWM4 navigation mode and the unfriendly CWM5 touch for our S2
The 6 is so great, GUI wise mainly. You get a much cleaner interface, scroll in touch is much better, and you can still use keys. Much less risks selecting a wrong menu now.
This one took me less than expected. Had to learn a bit in ADB, but could also do it in other ways.
The bigger part is with my next thread, soon...
Stay tuned
Great job thanks
Yep best way to get custom rom on phone
1. Get desired custom rom + this (place in external sdcard)
2. boot phone into stock recovery
3. flash this in stock recovery
4. do a backup of stock rom
5. wipe data and cache aka. factory reset
6. flash custom rom + custom kernel if you want
7. reboot phone
Now you should have perm recovery + custom rom of choice. If there is a need to go back to stock rom for warranty reasons just restore backup made in step 4. After restore you should have stock rom + stock recovery and after all this still no yellow triangle + need for PC
-Grift- said:
Yep best way to get custom rom on phone
1. Get desired custom rom + this (place in external sdcard)
2. boot phone into stock recovery
3. flash this in stock recovery
4. do a backup of stock rom
5. wipe data and cache aka. factory reset
6. flash custom rom + custom kernel if you want
7. reboot phone
Now you should have perm recovery + custom rom of choice. If there is a need to go back to stock rom for warranty reasons just restore backup made in step 4. After restore you should have stock rom + stock recovery and after all this still no yellow triangle + need for PC
Click to expand...
Click to collapse
Yes, the new feature to get permanent recovery is awesome
Sadly, you still need a zip. He cannot flash tar or raw images.
I dont get you
-Grift- said:
I dont get you
Click to expand...
Click to collapse
-Grift- said:
Yep best way to get custom rom on phone
.
.
6. flash custom rom + custom kernel if you want
7. reboot phone
Now you should have perm recovery + custom rom of choice...
Click to expand...
Click to collapse
I couldn't get it put the recovery as not temporary. I tried to flash a kernel zip file in CWM, but I loose CWM and I get the recovery that was bundled with the flashed kernel. Not sure how to make it permanent if the custom kernel keeps overwriting the recovery on boot. In the features, CWM6 last update should have that option, but I do not see it anywhere
Ah OK now I follow looks like I phrased it wrong
However, that's a feature supposed to be in CWM6, making it permanent
But maybe only for phone with a recovery partition, as CWM6 was not released as self zip for the i9100
So, could be still need manual editing of the kernel, which seems logical
too bad it's not permanent
kmetek said:
too bad it's not permanent
Click to expand...
Click to collapse
You need a custom kernel for that. My aim here was to keep stock kernel. For occasional flashers, not the daily ones, it is perfect
Sent from my GT-I9100 using Tapatalk 2
Phil3759 said:
You need a custom kernel for that. My aim here was to keep stock kernel. For occasional flashers, not the daily ones, it is perfect
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Great stuff Phil3759. Would it be ok to flash and use with latest 4.0.4 firmware bearing in mind issues with eMMC brick bug?
Regards
fs1023
fs1023 said:
Great stuff Phil3759. Would it be ok to flash and use with latest 4.0.4 firmware bearing in mind issues with eMMC brick bug?
Regards
fs1023
Click to expand...
Click to collapse
Koush said it will fix it. However, I do not have any feedback on this one. Till then, wipe in CWM + stock kernel 4.0.4 should be avoided, unless you want to test it :fingers-crossed:
Hope someone can confirm it is safe.
Phil3759 said:
Koush said it will fix it. However, I do not have any feedback on this one. Till then, wipe in CWM + stock kernel 4.0.4 should be avoided, unless you want to test it :fingers-crossed:
Hope someone can confirm it is safe.
Click to expand...
Click to collapse
I would test it but I have already had a brick due to eMMC bug and have noted that the PCB was changed in posts i made in forum, so don't want a potential another one.
BTW in your OP in http://forum.xda-developers.com/showthread.php?t=1746794 you state that CWM 4 will be safe with brick bug so i assume it will be safe to use this recovery version till CWM v6 has been tested.
Many thanks for your help
fs1023 said:
I would test it but I have already had a brick due to eMMC bug and have noted that the PCB was changed in posts i made in forum, so don't want a potential another one.
BTW in your OP in http://forum.xda-developers.com/showthread.php?t=1746794 you state that CWM 4 will be safe with brick bug so i assume it will be safe to use this recovery version till CWM v6 has been tested.
Many thanks for your help
Click to expand...
Click to collapse
entropy512 confirmed CWM4 is safe
Seems versions 5.x and above are affected, not sure the new ones, only time and feedback will say. I would brick mine without problem as it is under warranty, but need it for dev/learning these weeks
Would it be ok to flash kernal Siyah v.4.0.1 with Oobile Odin?
Sent from my GT-I9100 using xda premium
---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------
Sorry Mobile Odin
Sent from my GT-I9100 using xda premium
fs1023 said:
Would it be ok to flash kernal Siyah v.4.0.1 with Oobile Odin?
Sent from my GT-I9100 using xda premium
---------- Post added at 12:13 AM ---------- Previous post was at 12:12 AM ----------
Sorry Mobile Odin
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Mobile odin is a great tool for this
Thanks for this. I currently have 6.0.1.1 no-touch with CW9.
Can I make this permanent on my phone somehow? Maybe using download mode?
Cheers
No, Kernel overwrites the recovery files on boot. So, no way without flashing a custom kernel with touch built in
Here is the link for the CyanogenMod kernel for i9100 with recovery 6.0.1.1:
http://www.mediafire.com/file/y99yvcm7ztpfs5p/cm-cwm6-i9100.img
I extracted recovery from that kernel. Looking at the console output, they do use CM9 source code, so give it a try and see if it is the last kernel update for you
I got a bootloop on the first time I tried to flash a ROM (later fixed), so I apologise as I'm a bit scarred.
I'm on stock XWLPG ROM. Recently used CF Root v5.5. Battery is still troubling me, so I am hoping to give Siyah v4.0 Kernel a try.
I want to keep the stock ROM because I like Swype, Samsung Dive (I haven't tried cerberus just yet) and the stock chinese keyboard / input.
What I want to know is if I understand how this works correctly...
1. I use Odin and select the Siyah v4.0 by clicking PDA (like I did when I flashed CF Root v5.5)
2. the stock XWLPG ROM will continue to function as it should
3. battery life even on stock Siyah v4.0 settings should improve
Thanks in advance!
-SKYLINE- said:
I got a bootloop on the first time I tried to flash a ROM (later fixed), so I apologise as I'm a bit scarred.
I'm on stock XWLPG ROM. Recently used CF Root v5.5. Battery is still troubling me, so I am hoping to give Siyah v4.0 Kernel a try.
I want to keep the stock ROM because I like Swype, Samsung Dive (I haven't tried cerberus just yet) and the stock chinese keyboard / input.
What I want to know is if I understand how this works correctly...
1. I use Odin and select the Siyah v4.0 by clicking PDA (like I did when I flashed CF Root v5.5)
2. the stock XWLPG ROM will continue to function as it should
3. battery life even on stock Siyah v4.0 settings should improve
Thanks in advance!
Click to expand...
Click to collapse
Use CWM recovery instead of Odin.
-Download Siyah CWM zip version(I recommend 4.0.1 or 4.1rc1)
-Reboot into CWM recovery
How to do this?
Off your phone. Hold Volume up + home button + power button, release your hands once your phone lights up.
-flash Siyah kernel
-wipe cache partition
-wipe dalvik cache
-reboot your phone
-Download "extweaks" from market
-open extweaks
-change profile to battery
-apply changes.
You should have improved battery life now with good performance too.
Swyped from my Samsung Galaxy SII
Hi im using Samsung Galaxy S2 rooted stock ROM ICS 4.0.3 ,
GT i9100
baseband version : I9100DDLPA
Kernel version : 3.0.15-i9100XWLP7-CL340913
Build number : IML74K.XWLP7
I have a noob doubt ...Does installing Custom Kernel removes the user data +apps ??
And my whole settings ?? Or is it just like Rooting my phone ( Doesnt affected anything-even my BG image :laugh: )??
Please help me ....Im planning to Install Siyah Kernel since many of them using it and its awesome kernel itseems ....Googled
Is Siyah compatible for my version ??
Please Help me XDA
No, all your data is safe... until something goes wrong and you will be forced to wipe your data/factory reset. But this are rare incidents.
Just put few kernels in your internal sdcard card root folder, be sure that kernels are properly downloaded (verify md5 signature) and flash it with cwm or mobile odin. You can also use odin on your computer but binary counter will be increased.
i9.0.1.3k galaxy imperator
SirKunon said:
No, all your data is safe... until something goes wrong and you will be forced to wipe your data/factory reset. But this are rare incidents.
Just put few kernels in your internal sdcard card root folder, be sure that kernels are properly downloaded (verify md5 signature) and flash it with cwm or mobile odin. You can also use odin on your computer but binary counter will be increased.
i9.0.1.3k galaxy imperator
Click to expand...
Click to collapse
The thing is i dont have CWM so only installing custom Kernel .....I only have stock recovery .....Clockworkmod is not available in CWM website it says the download is not available now ...Im looking to install CWM6 ......
The imp reason for installing custom rom is to get CWM6 .....
Is there any way to flash custom kernel without CWM and Odin ?? With stock recovery ??
Or please suggest me anyway to install CWM without installing custom kernel for S2 i9100
Mobile odin (free version will be enough), if your phone is rooted.
Select kernel with cwm build in (Siyah...) and flash.
i9.0.1.3k galaxy imperator
kingsleyhopper said:
The thing is i dont have CWM so only installing custom Kernel .....I only have stock recovery .....Clockworkmod is not available in CWM website it says the download is not available now ...Im looking to install CWM6 ......
The imp reason for installing custom rom is to get CWM6 .....
Is there any way to flash custom kernel without CWM and Odin ?? With stock recovery ??
Or please suggest me anyway to install CWM without installing custom kernel for S2 i9100
Click to expand...
Click to collapse
custom ROM/KERNEL cannot be flashed thro Stock Recovery ma8. for that u need a wrk'ng CWM Recovery.
U can flash the .tar file of siyah v4.1.2 using ODIN from ur PC, u will get the latest 6.x.xx recovery installed along with it.
Use Odin on your pc and flash the .tar archive of the Siyah Kernel (4.1.2 or 4.0.1).
Unless something really rare happens, this shouldn't affect your user data. Remember to wipe cache and dalvik after flashing the kernel (you will have CWM just after flashing).
Sun90 said:
custom ROM/KERNEL cannot be flashed thro Stock Recovery ma8. for that u need a wrk'ng CWM Recovery.
U can flash the .tar file of siyah v4.1.2 using ODIN from ur PC, u will get the latest 6.x.xx recovery installed along with it.
Click to expand...
Click to collapse
Does it affect my wallpaper settings or folder arrangement or any other changes or just it installs the custom kernel just like rooting??
i have seen many ppl bricking phone using ODIN is there any good tutorial from XDA for using ODIN to flash custom kernel
I already searched and many comes up confused which tut to use ODIN
gb.yolo said:
Use Odin on your pc and flash the .tar archive of the Siyah Kernel (4.1.2 or 4.0.1).
Unless something really rare happens, this shouldn't affect your user data. Remember to wipe cache and dalvik after flashing the kernel (you will have CWM just after flashing).
Click to expand...
Click to collapse
yeah okay ......I will do as you say ......but why should i wipe cache and dalvik after installing custom kernel ??
SirKunon said:
Mobile odin (free version will be enough), if your phone is rooted.
Select kernel with cwm build in (Siyah...) and flash.
i9.0.1.3k galaxy imperator
Click to expand...
Click to collapse
Really Do u have link to any xda tut for this or any links if u consider to share here :highfive:
kingsleyhopper said:
Does it affect my wallpaper settings or folder arrangement or any other changes or just it installs the custom kernel just like rooting??
Click to expand...
Click to collapse
Installing a new kernel doesn't affect any of your settings.
You should wipe cache and dalvik cache to ensure integrity, stability and no program errors
gb.yolo said:
Installing a new kernel doesn't affect any of your settings.
You should wipe cache and dalvik cache to ensure integrity, stability and no program errors
Click to expand...
Click to collapse
okay sure thank u
kingsleyhopper said:
Really Do u have link to any xda tut for this or any links if u consider to share here :highfive:
Click to expand...
Click to collapse
Sure, here you go:
http://forum.xda-developers.com/showthread.php?p=19375406
Flashing with Odin is easy and preferred by most ppl, but I don't wont to have a yellow triangle and incrased binnary counter (never had it). I preffer tools or ways more complicated but still safe to root or flash. I'm using Odin only when I want to perfectly debrand phone or wipe him to factory state with stock firmware.
But S2 is so user friendly that it is a sin to rape him with Odin all the time. All you need is:
1. Fake recovery to root any ICS based stock firmware
2. Mobile Odin (or something like that) to flash custom 'preclockworkmoded' kernel
After that you can, and you should, flash averything from cwm recovery (all .zip based files) or tools like Hellcat's kTool or Chainfire's CWM tool or mentiobed before Mobile Odin (to flash anything you want - .zip .tar .bin wit md5 hash or without it)
Use Odin only when you don't have another choice. You will not be bored by drivers, data connections, is it see or not see by explorer or Odin, etc.
It is mobile gadget, use it's wireless power.
Even for data transfer there are great aps (AirDroid, ES File explorer, Solid explorer etc.).
(Post dedicated not only for OP)
i9.0.1.3k galaxy imperator
SirKunon said:
Sure, here you go:
http://forum.xda-developers.com/showthread.php?p=19375406
Flashing with Odin is easy and preferred by most ppl, but I don't wont to have a yellow triangle and incrased binnary counter (never had it). I preffer tools or ways more complicated but still safe to root or flash. I'm using Odin only when I want to perfectly debrand phone or wipe him to factory state with stock firmware.
But S2 is so user friendly that it is a sin to rape him with Odin all the time. All you need is:
1. Fake recovery to root any ICS based stock firmware
2. Mobile Odin (or something like that) to flash custom 'preclockworkmoded' kernel
After that you can, and you should, flash averything from cwm recovery (all .zip based files) or tools like Hellcat's kTool or Chainfire's CWM tool or mentiobed before Mobile Odin (to flash anything you want - .zip .tar .bin wit md5 hash or without it)
Use Odin only when you don't have another choice. You will not be bored by drivers, data connections, is it see or not see by explorer or Odin, etc.
It is mobile gadget, use it's wireless power.
Even for data transfer there are great aps (AirDroid, ES File explorer, Solid explorer etc.).
(Post dedicated not only for OP)
i9.0.1.3k galaxy imperator
Click to expand...
Click to collapse
:good: :highfive:
Thank you very much ....I used mobile odin and flashed new siyah kernel into my stock ICS ...thank u very much .......
Very simple and easy ..........
After a few weeks im planning to change my rom to custom rom like CM9 or recursion remix something like that
kingsleyhopper said:
:good: :highfive:
Thank you very much ....I used mobile odin and flashed new siyah kernel into my stock ICS ...thank u very much .......
Very simple and easy ..........
After a few weeks im planning to change my rom to custom rom like CM9 or recursion remix something like that
Click to expand...
Click to collapse
thats 4.1.1.
smallevil said:
thats 4.1.1.
Click to expand...
Click to collapse
which one is 4.1.1 ??
Is just like rootig your phone.all apps will be safe.siyah is a very good kernel for me especially when used together with exTweaks
JUST HIT THE BIG THANKS BUTTON...
Sent from my beautiful phone powered by the best OS ever
Thin_Bezel said:
Is just like rootig your phone.all apps will be safe.siyah is a very good kernel for me especially when used together with exTweaks
JUST HIT THE BIG THANKS BUTTON...
Sent from my beautiful phone powered by the best OS ever
Click to expand...
Click to collapse
yes siyah kernel is very good kernel :good: it gives me many options in extweaks .....Mainly my headphones now have high amplification - better now...
Using mobile odin to flash kernel is just simple and easy ...took me barely 3 minutes thats all
I've stuck by the Siyah kernel for the better part of this year and always held it in high regard.
If you're keen, I encourage you to dabble with ExTweaks for a solid day as the outcomes can be very useful. Namely, improved performance and better battery stats
Transpiror said:
I've stuck by the Siyah kernel for the better part of this year and always held it in high regard.
If you're keen, I encourage you to dabble with ExTweaks for a solid day as the outcomes can be very useful. Namely, improved performance and better battery stats
Click to expand...
Click to collapse
Could you please tell me the settings for ExTweaks for improving performance and better battery stats ?:highfive:
kingsleyhopper said:
Could you please tell me the settings for ExTweaks for improving performance and better battery stats ?:highfive:
Click to expand...
Click to collapse
check the link below for 'Magic tweaks' with Extweaks for siyah kernel by @geko95gek
Magic Tweaks
Sun90 said:
check the link below for 'Magic tweaks' with Extweaks for siyah kernel by @geko95gek
Magic Tweaks
Click to expand...
Click to collapse
thank you very much i will try and post the result here
kingsleyhopper said:
Could you please tell me the settings for ExTweaks for improving performance and better battery stats ?:highfive:
Click to expand...
Click to collapse
My current settings on RR 3.0.6 and Siyah 4.1.3
CPU Tab
Everything left "as is" except...
CFS Tweaks: Linux kernel defaults
CPU Step Count: 8
Default CPU Governor: smartassV2
GPU Tab
Mali Touch Boost Level: disabled
Freq Step1: 100mhz
Freq Step2: 160mhz
Freq Step3: 200mhz
Freq Step4: 267mhz
Voltage Level1: 800mV
Voltage Level2: 850mV
Voltage Level3: 900mV
Voltage Level4: 950mV
Have kept thresholds relatively stock but use common sense here to tweak according to taste and application. Like how often will you be gaming?
Misc Tab
Android Logger: disabled
Default I/O scheduler: sio
CPU voltage settings done via NS tools
1600mhz: 1400mV
1400mhz: 1300mV
1200mhz: 1200mV
1000mhz: 1100mV
800mhz: 1025mV
500mhz: 950mV
200mhz: 900mV
100mhz: 875mV
Italicised settings not for typical everyday usage but are stable nonetheless
The above settings from my experience are rock solid on my phone. Sure they might not be perfect but are certainly a good reference point. Your mileage may vary however...
Good luck!