[CF-Root 3.7][Universal] CF-Root Adaptation for Galaxy GIO {Working For GB & CM Roms}
THIS IS NOT A ROM - it is only a kernel (S5660: boot image). You need to have a firmware already on your device (S5660: tested on Stock/Custom Gingerbread DXKP6, and DXKT4 using ext4 fs). You do NOT need to wipe anything for this patch. You DO need to read the instructions.
MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really)
Donate
*Features
Some binary files added:
-- pre-Rooted, su binary added
-- Superuser added
-- Busybox installed
- Integrated Tweaks Manager & CWM Manager
- Running All Scripts in /system/etc/init.d
- Custom Bootanimation Working on All Roms
- Overclock support
- BLN support (lights.msm7k.so modified)
- wifi module (ar6000.ko) included, so this version of CF-Root-S5660 will work on all versions of Gingerbread or CM GB
- ext4 support
- added more governors scaling & iosched
- etc
Instructions - CWM/RZR
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Flash CWM or RZRecovery.
- Download the File To Your Sd-Card
- Flash via CWM or RZRecovery
- No Need to Data Wipe
- Initial/First Boot May Take Long Time,Very Long Maybe .
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
- 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.
CWM Manager
Same as Chainfire's CF-Root
Features:
- Boot to CWM
- Backup firmware
- Restore backups (S5660: Do not use CWM Manager to restore any backup for now, use CWM Advance Backup directly!)
- Delete backups
- Install APKs
- Flash CWM update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) (S5660: you have to rename boot.img to zImage)
Tweak Manager
Same as Chainfire's CF-Root, except:
- Kernel: Scheduler option always disabled on boot. Kernel scheduler tweak not working on S5660.
- Now have "DT: Auto start" option to turn on/off Darktremor a2sd script on boot. Don't worry, Darktremor apps2sd setting is persistent, event you turn off the auto start script. It's safer to turn a2sd auto start off!
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
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. The Kernel is Custom Supporting Ext4 FS, OC, and other Features*
THIS IS NOT A ROM - it is only a kernel (S5660: boot image). You need to have a firmware already on your device (S5660: tested on Stock/Custom Gingerbread DXKP6, and DXKT4 using ext4 fs). You do NOT need to wipe anything for this patch. You DO need to read the instructions.
MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really)
Donate
There have now been nearly 1.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...
*Features
Some binary files added:
-- pre-Rooted, su binary added
-- Superuser added
-- Busybox installed
- Integrated Tweaks Manager & CWM Manager
- Running All Scripts in /system/etc/init.d
- Custom Bootanimation Working on All Roms
- Overclock support
- BLN support (lights.msm7k.so modified)
- wifi module (ar6000.ko) included, so this version of CF-Root-S5660 will work on all versions of Gingerbread or CM GB
- ext4 support
- added more governors scaling & iosched
- etc
Instructions - CWM/RZR
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Flash CWM or RZRecovery.
- Download the File To Your Sd-Card
- Flash via CWM or RZRecovery
- No Need to Data Wipe
- Initial/First Boot May Take Long Time,Very Long Maybe .
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
- 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.
CWM Manager
Same as Chainfire's CF-Root
Features:
- Boot to CWM
- Backup firmware
- Restore backups (S5660: Do not use CWM Manager to restore any backup for now, use CWM Advance Backup directly!)
- Delete backups
- Install APKs
- Flash CWM update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP) (S5660: you have to rename boot.img to zImage)
Tweak Manager
Same as Chainfire's CF-Root, except:
- Kernel: Scheduler option always disabled on boot. Kernel scheduler tweak not working on S5660.
- Now have "DT: Auto start" option to turn on/off Darktremor a2sd script on boot. Don't worry, Darktremor apps2sd setting is persistent, event you turn off the auto start script. It's safer to turn a2sd auto start off!
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
Last edited: