Develop Bugs

[30.03.2012][CF-Root 4.4] J-P/S/Q-*,JV-1KBHIOPQRSTAUV,JVU,JW4 - su+bb+2e/CWM-rfs+ext4

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 (unprotected recovery and CWM compatibility) OR (CWM3)
If you are looking for highly optimized kernels or kernels that perform specific functions, look elsewhere. All CF-Root's are based on original Samsung kernels, they are NOT recompiled, and thus ensure maximum compatibility.
THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device. 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 over 200.000 downloads of CF-Root for various devices, 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!)
Features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Superuser 2.3.6.1
FROYO ( CF-Root < 2.4 versions )
---- Busybox 1.15.3 or 1.17.1 (if not mentioned in the filename it is 1.15.3)
---- "2e" recovery (can flash unsigned update.zip's)
---- Integrated fix for ClockworkMod's nandroid (2.5.0.4+)
GINGERBREAD ( CF-Root >= 2.4 versions, JVK and newer )
---- Busybox v1.16.2androidminimal (from CWM)
---- Integrated CWM 3.0.0.5 / RFS
CF-Root v4.3 (JVT and newer)
--- Superuser updated to v3
--- Kernel is now in "insecure" mode (rooted ADB shell)
CF-Root v4.4 (JW4 and newer)
--- SuperSU
--- ro.secure=1, patched adbd to act as if ro.secure=0
Instructions (short)
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
Instructions (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 (alternative if you are already running CF-Root 2.5 or newer)
- 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 (speedmod, voodoo, etc) 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 2e recovery will be lost (unless the other kernel also includes it), but there should not be issues.
CF-Root is made to be applied on a stock kernel. Going from a lagfixed kernel to CF-Root usually does not work. Unlagfix first.
Voodoo If you are running the latest Voodoo, you probably do not need CF-Root at all. Voodoo has the basic root features in place, but not the applications. Voodoo does not come with 2e recovery, but it does come with CWM, so there is no need for 2e on Voodoo. To get Superuser and Busybox on Voodoo, simply open Market and search, download, and install them ! Voila !
ClockworkMod on FROYO ( CF-Root versions < 2.4 )
CF-Root is ClockworkMod compatible, it does not include CWM itself. It uses 2e recovery, which means it can flash unsigned update.zip's, like CWM.
To use CWM, either place the update.zip in the correct location ( /sdcard ), or install it through the ROM Manager application.
When you boot into recovery, you will get the 2e recovery, even if CWM is installed. It does not boot directly into CWM (though it may do so when you boot into recovery from the ROM Manager application). Select "flash update.zip" in recovery to start CWM.
Important note: The very first time you do this on a ROM, it will usually not work. The phone will reboot normally after you flashed the update.zip. You need to reboot into recovery a second time and flash update.zip again. Then you will be launched into CWM. After this, it will work the first time you select it.
ClockworkMod on GINGERBREAD ( CF-Root versions >= 2.4, excluding JV1 on which CWM is broken )
CF-Root includes a special version of CWM3, modified to work with RFS. CWM3 by default does not support RFS, koush' versions are all based on ext4. The RFS compatibility is done with heavy scripting, the same method used on CF-Root for Galaxy Tab. For SGS CWM3 is also recompiled from source with some slight modifications to handle key input correctly.
CF-Root/CWM3 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly.
- Booting into recovery will immediately give you CWM. The standard recovery is completely gone.
- A "CWM" icon is added to your applications, which will reboot your device into recovery mode (CWM).
- 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.
- Version jumped from 1.3 to 2.4 to keep the cross-device CF-Root versioning in-sync (CF-Root is also available for Galaxy Tab).
- If you wonder where your bootup/shutdown sounds have gone, CF-Root probably removed them to make sure it has enough space available.
- ( CF-Root versions < 2.6 ) Make sure to boot up your device fully at least once before flashing CF-Root. This is because the device may have some code it needs to run at first boot. CWM disables this code.
CWM Manager on GINGERBREAD ( CF-Root versions >= 2.5 )
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011) and beta. 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
- Delete backups
- Install APKs ( CF-Root versions >= 2.8 )
- Flash CWM3 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility ! At this version of CWM Manager this does not produce errors, it just doesn't do what you expect it to
Tweak Manager on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root includes a number of tweaks that are applied on startup. From CF-Root versions 2.8 and up a "Tweaks" application is included you can use to select which tweaks to apply.
Ext4 Manager on GINGERBREAD ( CF-Root versions >= 2.8 )
CF-Root supports ext4 mounts for the main mount points. Converting between rfs and ext4 however requires a secondary external package (which you can find in the download area a great many posts below this one), because it is all too large to fit inside the kernel. Download the APK from below, put it on your sd card, start CWM Manager, select "Install APK", find the APK and tap to install. Now you can use the "ext4" app to convert between filesystems, manually check the filesystem, etc.
Obviously you should revert back to rfs before flashing a new stock ROM. A lot of custom ROMs support ext4 as well, but it is still advised to revert to rfs before installing them.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Features:
- Show current filesystem status
- Convert between rfs <=> ext4 and back
- Manual fsck
- Selects either internal or external sdcard for temporary storage, depending on which has the most space
- Automatically reverts on conversion failure
- If it tells you to PANIC !, please do so
Custom boot / init scripts on GINGERBREAD ( CF-Root versions >= 2.8 )
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.
Custom boot animations and binaries on GINGERBREAD ( CF-Root versions >= 2.9, broken in 2.8 ! )
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
CF-Root v3.0 and up also support:
- /data/local/bootanimation.bin
Installing busybox over the included version on GINGERBREAD ( CF-Root versions >= 3.0 )
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.
Notes
- (FROYO) ADB in recovery is flaky. Sometimes it works, sometimes it doesn't. If you go into ClockworkMod it usually works, though.
- (FROYO) An older version of BusyBox is used (in some versions) because the newer versions drive me absolutely crazy with throwing color codes into the shell while it isn't supported.
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! I don't know which file to pick! The filenames confuse me!
First thing: don't panic! It's all rather easy, and you won't easily do something bad! I am personally attentive to use the exact same version as the ROM I am running, but it's not that important.
First, go to Settings -> About phone -> Build number. It should say something like FROYO.xxJPy. It's primarily the JPy that we are interested in. Try to match that with a download link available in this (and the next few) posts. Some of the downloads dont just have JPy file name format, but are called xx_xxx_JPy.
Let me explain that. Samsung isn't always very precise in naming/marking their different (leaked) firmwares. CF-Root's are modified kernels, the filenames explain in more detail which exact firmware ROM the base kernel was taken from, for those experts who understand.
If you are not one of those people, go back to the JPy thing. The "y" in JPy is 0-9, A-Z. If they run out of numbers, they use letters. So A would be 10 (9 + 1), while Z would be 35 (9 + 26). Find the one that is closest to yours, if yours is not present, and flash that one.
The truth is, these kernels, they don't differ all that much. It's quite likely that the very latest version (at time of writing: JPY) will work perfectly fine on your ROM. There are some small differences, but using a different version is unlikely to cause serious issues. The closer the versions are, the less likely there are to be issues, BUT it is still quite possible that the latest version will work better for you than the matching version (or not!).
If you are just installing CF-Root to flash a custom ROM like Darky, make sure you have ROM Manager already installed, ClockworkMod flashed, then simply install the latest CF-Root, reboot once normally, then reboot in recovery and run the Darky update.zip. In this case it does NOT need to be a near match at all!
Download
LOOK WELL AT THE FILENAMES, MAKE SURE YOU ARE GETTING THE RIGHT VERSION !
DOWNLOADS CONTINUED IN NEXT POSTS !
CF-Root-JPH-v1.0.zip
CF-Root-JPH-v1.1.zip
CF-Root-JPK-v1.1.zip
CF-Root-JPM-v1.2-Busybox-1.15.3.zip
CF-Root-JPM-v1.2-Busybox-1.17.1.zip
CF-Root-JP6-v1.2-Busybox-1.15.3.zip
CF-Root-JP6-v1.2-Busybox-1.17.1.zip

--- more downloads ---
CF-Root-JPJPA-v1.2-Busybox-1.15.3.zip
CF-Root-JPJPA-v1.2-Busybox-1.17.1.zip
CF-Root-XX_XEU_JPO-v1.2-Busybox-1.15.3.zip
CF-Root-XX_XEU_JPO-v1.2-Busybox-1.17.1.zip
CF-Root-XW_XEE_JPA-v1.2-Busybox-1.15.3.zip
CF-Root-XW_XEE_JPA-v1.2-Busybox-1.17.1.zip
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_OXA_JPU-v1.3-BusyBox-1.17.1.zip

--- more downloads ---
ROOTING JVK: See this post instead. It contains a CF-Root version specifically for JVK, you do not need to flash back the original kernel again. I also strongly advise you to read the first post of this thread.
ROOTING JV1: The JV1 version is not compatible with ANY version of ClockWorkMod (CWM).
CF-Root-XX_XEU_JPX-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_XEU_JPX-v1.3-BusyBox-1.17.1.zip
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_XEU_JPY-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.15.3_NO-CWM.zip
CF-Root-XW_OXX_JV1-v1.3-BusyBox-1.17.1_NO-CWM.zip

--- more downloads ---
CF-Root-XW_OXF_JS2-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_OXF_JS2-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEN_JS3-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEN_JS3-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_XEE_JS7-v1.3-BusyBox-1.17.1.zip

--- more downloads ---
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version!
Release notes for v2.5: http://forum.xda-developers.com/showpost.php?p=12507221&postcount=1188
Release notes for v2.6: http://forum.xda-developers.com/showpost.php?p=12526079&postcount=1211
Release notes for v2.7: http://forum.xda-developers.com/showpost.php?p=12563930&postcount=1256
Fix for iptables / Droidwall for JVK: http://forum.xda-developers.com/showpost.php?p=12527335&postcount=1212
Note that v2.8 is available in the next post
CF-Root-XX_DBT_JQ3-v1.3-BusyBox-1.15.3.zip
CF-Root-XX_DBT_JQ3-v1.3-BusyBox-1.17.1.zip
CF-Root-XW_NEE_JS8-v1.3-BusyBox-1.15.3.zip
CF-Root-XW_NEE_JS8-v1.3-BusyBox-1.17.1.zip
CF-Root-XX_OXA_JVK-v2.4-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.5-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.6-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.7-CWM3RFS.zip

--- more downloads ---
Note: it is NO PROBLEM to flash new JVK version over old JV1 or JVK version!
Release notes for v2.8: http://forum.xda-developers.com/showpost.php?p=12652182&postcount=1332
Release notes for v2.9: http://forum.xda-developers.com/showpost.php?p=12672516&postcount=1400
Release notes for v3.0: http://forum.xda-developers.com/showpost.php?p=12736616&postcount=1536
Release notes for v3.1: http://forum.xda-developers.com/showpost.php?p=12823970&postcount=1663
Release notes for v3.1 JVB: http://forum.xda-developers.com/showpost.php?p=12950723&postcount=1774
Release notes for v3.2 JVH: http://forum.xda-developers.com/showpost.php?p=13619653&postcount=2012
Release notes for v3.7 JVP: http://forum.xda-developers.com/showpost.php?p=14582942&postcount=2227
Apparently this CIFS patch works for JVB/JVK CF-Root: http://forum.xda-developers.com/showpost.php?p=12997697&postcount=123
More downloads after the ext4 and license posts!
CF-Root-XX_OXA_JVK-v2.8-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v2.9-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v3.0-CWM3RFS.zip
CF-Root-XX_OXA_JVK-v3.1-CWM3RFS.zip
CF-Root-XW_XEE_JVB-v3.1-CWM3RFS.zip
CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.zip
CF-Root-XX_OXA_JVO-v3.2-CWM3RFS.zip
CF-Root-XX_OXA_JVP-v3.7-CWM3RFS.zip

ext4 tools
Note: don't link to this post directly, as it will move down in the thread when more CF-Root downloads become available!
The ext4 tools addon for CF-Root requires CF-Root version 2.8 or later
Release notes for v1.0: http://forum.xda-developers.com/showpost.php?p=12652182&postcount=1332
Release notes for v1.1: http://forum.xda-developers.com/showpost.php?p=12672516&postcount=1400 (non-essential update)
Release notes for v1.2: http://forum.xda-developers.com/showpost.php?p=12736616&postcount=1536 (non-essential update)
Release notes for v1.3: http://forum.xda-developers.com/showpost.php?p=13619653&postcount=2012

LICENSE for CF-Root v3.0+, ext4 tools v1.2+
As it seems a number of kernels are being based on CF-Root, and CF-Root is being included in custom ROMs, I'm going to set up a number of rules. The rules are meant to be fair to both you and me, and futher cooperation, not limit it. If you are an end-user, do not distribute kernels based on CF-Root, and do not distribute ROMs using it, you can skip this post, it is not for you. If you make kernels based on CF-Root, or your ROMs include CF-Root, read this post and follow the rules.
I don't mind you using the CF-Root hacked kernels, in fact I think it's great All parts of CF-Root are free to use/include in your own stuff, if these rules are followed.
If something doesn't work for you, feel free to PM/ask for a change. None of these rules are set in stone, maybe you have a good reason to want something different.
Usage of "CWM Manager", "Tweak Manager", and "ext4 tools" apps
- You may not modify these APKs in any way, if you include or redistribute them. The only exception to this rule is modifying the icons to match your ROM's theme.
- You may not re-post these files anywhere else (separately from CF-Root), but you may of course link to the post (not the download directly!) in the CF-Root thread containing these files. In other words, either you include them or you don't, but you can't offer them as a separate download.
- You must use the appropriate versions, released at the same time as the kernel, or any newer version released by me. For example, if you are using CF-Root v3.0, if you use/include these apps, you must use CWM Manager 1.50+, Tweak Manager 1.20+ and ext4 Manager 1.20+.
- You must test that their functionality remains 100% intact regardless of your (kernel/ROM) modifications. If the functionality is not as expected with your (kernel/ROM) modifications but you still include the apps, you must clearly state what you know is broken.
If you are just using CF-Root in your custom ROM, but do not modify the CF-Root kernel in any way (except icons)
- You must include a notice that the ROM uses CF-Root, and the version of CF-Root used.
- You should (not required but strongly encouraged) also include a link to this thread ( http://forum.xda-developers.com/showthread.php?t=788108 )
- You should (not required) include a link to donate to me, Chainfire ( http://www.jongma.org/dx.php )
- You should (not required) inform me that you are using it either by posting in the CF-Root thread or sending me a PM. (Thanks!)
- As you are not modifying CF-Root in any way (except icons), you can skip the rest of this post
Modifications to CF-Root (aside from the icons)
- Due to a lot of bickering and argueing, I'm simply no longer allowing this at all
- You can still kang a script or two left and right, I don't mind, as long as you are not basing an entire kernel on mine, or re-branding it, etc. Use common sense, you know exactly what I mean.

--- more downloads ---
JVI: Untested by me
JVQ: Untested by me
JVT: v4.3, Superuser updated to v3.0.2, and "insecure" mode
JVA: Untested by me
JVU: Untested by me
JVZ: Untested by me
CF-Root-XW_DBT_JVI-v3.7-CWM3RFS.zip
CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS.zip
CF-Root-XX_OXA_JVR-v4.1-CWM3RFS.zip
CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
CF-Root-XX_OXA_JVT-v4.3-CWM3RFS.zip
CF-Root-XF_TSR_JVA-v4.3-CWM3RFS.zip
CF-Root-XW_TMN_JVU-v4.3-CWM3RFS.zip (OLD !! Not the 2012 version !!)
CF-Root-XX_OXA_JVZ-v4.3-CWM3RFS.zip
This is the December 29, 2011 / Android 2.3.6 / JVU / Value Pack ? build:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
March 2012 / Android 2.3.6 / JW4 / Value Pack build:
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.zip

In Odin, repartition unchecked?

Awesome news saves me a lot of battery in battery out hassle - here's the kicker - I'm going back to JPC because of MODEM file issues and touchwiz lag - anychance of a JPC version ?

This is good stuff. I will test it tomorrow.

ed10000 said:
In Odin, repartition unchecked?
Click to expand...
Click to collapse
Don't touch anything except the PDA and START buttons, as per the instructions.
DangerMUK said:
Awesome news saves me a lot of battery in battery out hassle - here's the kicker - I'm going back to JPC because of MODEM file issues and touchwiz lag - anychance of a JPC version ?
Click to expand...
Click to collapse
Making a JPC version requires testing and some trial and error... not something I'm looking forward to be doing, as JPH is newer.

Thank you so much.
Can I flashed this if I have lagfix ?

poowe893 said:
Thank you so much.
Can I flashed this if I have lagfix ?
Click to expand...
Click to collapse
It should not be a problem. I flashed it myself over an active installation of CF-LagFix. Cannot guarantee it will be without issues, but I do not expect it to be a problem.

Flashed like a charm for me. But on restart, I got totally wierd settings, frequent FCs etc, those were very anxious 10 minutes, the I pulled the battery, reinserted, restarted the phone, & everything is normal. Thanks.

Hi there. Thanks for this release. I already have a JPH ROM flashed. How do I reflash this one, meaning, do I need to erase/wipe cache or format my SD card? Or just simple over writing will work?
Thanks so much.

ragin said:
Flashed like a charm for me. But on restart, I got totally wierd settings, frequent FCs etc, those were very anxious 10 minutes, the I pulled the battery, reinserted, restarted the phone, & everything is normal. Thanks.
Click to expand...
Click to collapse
I had this myself in one of my tests. Not completely sure what causes it but I suspect it is because in the background SU is being installed/upgraded. Waiting a few minutes and rebooting solved the issue for me as well. As it only occurred once for me I did not mention it, but I have now updated the first post with this info.
rajuki said:
Hi there. Thanks for this release. I already have a JPH ROM flashed. How do I reflash this one, meaning, do I need to erase/wipe cache or format my SD card? Or just simple over writing will work?
Thanks so much.
Click to expand...
Click to collapse
Yes, you already need the JPH firmware installed. You do NOT need to wipe cache, data, SD card, etc. Just follow the instructions - this patch only overwrites a small partion of the ROM.

Works for me..great it's fast and easy. Good Job

Great job, I'll test it asap.
Just one question for you: did you symlink available busybox commands or just put in the BB executable?

[03 JAN][ROM-ZIP] Raidroid Sense v1.0 - Desire Base

This ROM is based on Cotulla's original NAND release with a few changes, the main one being that this is the first ROM that can be flashed using ClockworkMod Recovery.
How to flash;
1: Boot into Clockwork Recovery
2: Select flash zip from sdcard
3: Select ROM file and then confirm
4: Wait for All Done! message
5: A wipe is recommended but not always required, if you experience force closes or things not working, try wiping before posting problems.
Changelog;
-v1.0- Initial Release
-gauner1986 Kernel from Desire HD rom release
-RMNet by default, create ppp folder in system to enable PPP data
-SU Fully working
-Flashable ONLY with clockworkmod recovery found HERE
-DOWNLOAD-
*CACHE FIX IS REQUIRED TO INSTALL APPS*
-Cache Fix-
THIS ROM IS ONLY FLASHABLE USING CLOCKWORKMOD RECOVERY FOR HD2 FOUND HERE
Credits to;
Cotulla + DFT - For the base ROM and all the great work thats gone into NAND on the HD2
Gauner1986 - For the kernel used in this ROM
CyanogenMod Team - For the great recovery that allows flashing custom roms
Anyone else who has contributed to android on the HD2

RaiderX303 said:
This ROM is based on Cotulla's original NAND release with a few changes, the main one being that this is the first ROM that can be flashed using ClockworkMod Recovery.
How to flash;
1: Boot into Clockwork Recovery
2: Select flash zip from sdcard
3: Select ROM file and then confirm
4: Wait for All Done! message
5: A wipe is recommended but not always required, if you experience force closes or things not working, try wiping before posting problems.
Changelog;
-v1.0- Initial Release
-gauner1986 Kernel from Desire HD rom release
-RMNet by default, create ppp folder in system to enable PPP data
-SU Fully working
-Flashable ONLY with clockworkmod recovery found HERE
-DOWNLOAD-
-
*CACHE FIX IS REQUIRED TO INSTALL APPS*
Cache Fix-
THIS ROM IS ONLY FLASHABLE USING CLOCKWORKMOD RECOVERY FOR HD2 FOUND HERE
Credits to;
Cotulla + DFT - For the base ROM and all the great work thats gone into NAND on the HD2
Gauner1986 - For the kernel used in this ROM
CyanogenMod Team - For the great recovery that allows flashing custom roms
Anyone else who has contributed to android on the HD2
Click to expand...
Click to collapse
Very nice, thanks for the update.zip.

Thank you
SOOOOOOOOOOOOOOOO much!

As
for the cache fix. Do I flash directly after the ROM?

jhr5474 said:
for the cache fix. Do I flash directly after the ROM?
Click to expand...
Click to collapse
yes, just flash the rom then the cache fix

work very well

RaiderX303 said:
This ROM is based on Cotulla's original NAND release with a few changes, the main one being that this is the first ROM that can be flashed using ClockworkMod Recovery.
How to flash;
1: Boot into Clockwork Recovery
2: Select flash zip from sdcard
3: Select ROM file and then confirm
4: Wait for All Done! message
5: A wipe is recommended but not always required, if you experience force closes or things not working, try wiping before posting problems.
Changelog;
-v1.0- Initial Release
-gauner1986 Kernel from Desire HD rom release
-RMNet by default, create ppp folder in system to enable PPP data
-SU Fully working
-Flashable ONLY with clockworkmod recovery found HERE
-DOWNLOAD-
*CACHE FIX IS REQUIRED TO INSTALL APPS*
-Cache Fix-
THIS ROM IS ONLY FLASHABLE USING CLOCKWORKMOD RECOVERY FOR HD2 FOUND HERE
Credits to;
Cotulla + DFT - For the base ROM and all the great work thats gone into NAND on the HD2
Gauner1986 - For the kernel used in this ROM
CyanogenMod Team - For the great recovery that allows flashing custom roms
Anyone else who has contributed to android on the HD2
Click to expand...
Click to collapse
Too F'ing fast RAIDER! Thanx.

how do I convert it to ppp?
I used the search optiion, believe me. All I found was ppp to rmnet because of the early on data disconnects. Could you guys help? Thanks in advance.

elcanela said:
I used the search optiion, believe me. All I found was ppp to rmnet because of the early on data disconnects. Could you guys help? Thanks in advance.
Click to expand...
Click to collapse
the first damn post said:
-RMNet by default, create ppp folder in system to enable PPP data
Click to expand...
Click to collapse
In a terminal emulator or adb shell.
Code:
su
mkdir /system/ppp

elcanela said:
I used the search optiion, believe me. All I found was ppp to rmnet because of the early on data disconnects. Could you guys help? Thanks in advance.
Click to expand...
Click to collapse
youll need to use adb and
adb remount
adb shell mkdir /system/ppp
Click to expand...
Click to collapse
or in terminal emulator
su
mount -o rw,remount /system /system
mkdir /system/ppp
Click to expand...
Click to collapse

the initrd and the zimage on the sd card is needed for CW or its a zimage files for your zip rom?
its question becouse you write its gauner kernel from HDrom, and he have in gauner hd rom 0.3 kernel with OC to 1113mh... can i replace the zimage from the sd card with this one and its allready replace in system?

ilijan said:
the initrd and the zimage on the sd card is needed for CW or its a zimage files for your zip rom?
its question becouse you write its gauner kernel from HDrom, and he have in gauner hd rom 0.3 kernel with OC to 1113mh... can i replace the zimage from the sd card with this one and its allready replace in system?
Click to expand...
Click to collapse
the zImage on the SD is for CWM recovery, not the ROM, the zImage for the rom is in the boot partition on the NAND

shadiku said:
In a terminal emulator or adb shell.
Code:
su
mkdir /system/ppp
Click to expand...
Click to collapse
Damn, I feel like an A$$! Didnt think it was that literal, I thought you had to drop certain files in there, but I will just make one with SUFBS. Thanks.

ok so if i want to replace zimage i need to go with install.bat wia adb? or its possible with cw?

Well even though I hate Sense.. I have to flash something with Clockwork. Here we go.

ilijan said:
ok so if i want to replace zimage i need to go with install.bat wia adb? or its possible with cw?
Click to expand...
Click to collapse
I think we can change in zip file : boot --->zImage and /system/lib/modules ----> ..
wait for RaiderX303 confirm this method again.

ilijan said:
ok so if i want to replace zimage i need to go with install.bat wia adb? or its possible with cw?
Click to expand...
Click to collapse
boot into CWM, then using adb run these commands
adb shell mount /dev/block/mtdblock2 /boot
adb push zImage /boot/zImage
adb reboot
Click to expand...
Click to collapse
or just change the zImage in the cache fix zip file and reflash

canot install mdj 9.2 oc rom becouse its canot mount boot block mtdblock0

thanks so much! its work just edited install_ kernel.bat and its allready replace the zimage

@raiderx
hmmm is it possible to use your .zip and swap the system folder with a cm6 system folder+nand kernels and flash from there?
in theory its possible but asking first before my phone becomes a ticking timebomb
does it need to be signed?

[17.12.2011][CF-Root v5.1] ICL53F - su+bb

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 firmware, and just adds root and busybox.
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 THE ENTIRE FIRST FEW POSTS!
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...
Main features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Superuser v3
- Busybox v1.19
- Custom boot / init scripts
- Insecure
Installation instructions
Please see the next post !
Recovery
Unlike CF-Root for various other devices, CF-Root for the Galaxy Nexus does not include any recovery, due to kernel and recovery being separate partitions on the device. This means you don't need to flash a recovery with your kernel.
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/sh")
- /system/bin/customboot.sh
- /system/xbin/customboot.sh
- /data/local/customboot.sh
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Busybox
Busybox by default creates symlinks in /sbin. You can turn this off by executing the following:
adb shell setprop persist.busybox.nosymlink 1
And reboot your device.
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root. 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. It is now used to make CF-Root for many devices!
Help! Which file do I use ?
Check Settings -> About phone -> Build number and find the matching download. YAKJU downloads are for GSM, MYSID downloads are for LTE.
Download
These are general-purpose downloads. See the posts following this one for the kernels.

Instructions
IMPORTANT: If your device is not yet OEM unlocked, both methods WILL WIPE your data ! If you are already OEM unlocked, this does not happen.
Flashing with ODIN
ODIN: Short
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
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 (turn off phone, then hold volume-down + power to boot)
- (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!)
Flashing with FASTBOOT
Fastboot: Short
- Flash boot.img (inside the tar inside the attached zip) as boot. Done.
Fastboot: Long
- Unzip the attached CF-Root-xxx-vX.X.zip
- Untar the CF-Root-xxx-vX.X.tar (found inside the zip)
- Find the boot.img file that you extracted
- (USB) Disconnect your phone from your computer
- Put your phone in fastboot mode (turn off phone, then hold volume-up + volume-down + power to boot)
- (USB) Connect the phone to your computer
- If your device is not yet OEM unlocked - NOTE: This wipes your data!
fastboot oem unlock
- (1) Flash the kernel (permanent):
fastboot flash boot boot.img
- Press the power button to boot
- or (2) Flash the kernel (temporary, applies root only):
fastboot boot boot.img

Downloads
Remember: I only have the GSM version, so the LTE versions are not tested by me !
CF-Root-GGN_YAKJU_ICL53F-v5.1.zip
CF-Root-GGN_MYSID_ICL53F-v5.1.zip

-- reserving yet another post --

I have the LTE SGN and my build number is ICL53F, not MYSID

theboo7 said:
I have the LTE SGN and my build number is ICL53F, not MYSID
Click to expand...
Click to collapse
And thus you should use:
CF-Root-GGN_MYSID_ICL53F-v5.1
and specifically not:
CF-Root-GGN_YAKJU_ICL53F-v5.1

omanomanom, tastes like bacon.
*installs*

finally the greatness has arrived on the galaxy nexus

So this changes/modifies the kernal to add root? What about OTA updates?
Sent from my Galaxy Nexus using XDA App

@chainfire
if my device is ITL41F and what can i do?
can i flash your other thread ICL53F rom via odin
and then flash cf-root kernel via odin again?

kangxi said:
So this changes/modifies the kernal to add root? What about OTA updates?
Click to expand...
Click to collapse
It should not interfere with OTA updates ...
leamoor said:
@chainfire
if my device is ITL41F and what can i do?
Click to expand...
Click to collapse
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...

Chainfire said:
It should not interfere with OTA updates ...
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...
Click to expand...
Click to collapse
Thanks for the quick response. Gonna try it when I get home.
Sent from my Galaxy Nexus using XDA App

Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？

leamoor said:
Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？
Click to expand...
Click to collapse
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data

Chainfire i knew you would come with a cr-root kernel...thanks!!!
Sent from my Galaxy Nexus using xda premium

Okay i did this, but my phone is now stuck on the Google Screen with a lock on the bottom that is unlocked.
When i go back to the bootloader and select Recovery Mode.
I get an Android with a "!"
Reboots back to the Google and nothing happens =(
The only way to start my Device is in CMD and using Superboot =S
Help!

Glad to see Odin works. I like having that safety net for when ROMs attack.

chainfire, je bent een baas! grtz uit haarlem.
pitje

cdesai said:
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data
Click to expand...
Click to collapse
get out noob this thread is sacred

Will this work with buildnumber ITL41F?
If not what should I do to make use of this kernel?
Many THanks in advance

Resolved - How do I install Liblights for BLN ?

I've just returned my phone to stock UCLJ3 + LiteKernel-4.0-20130121
BLN warns me that "this iblights does not support BLN. - I tried copying across liblights.n1.so from the LiteROM_0.9.zip to no avail.
would some kind sole please provide a CWMR zip to flash, to update it.
or
provide me with a step by step guide on how to use https://nodeload.github.com/Adam77Root/liblights_bln/zip/master to build my own.
[GUIDE] How to make a cwm recovery flashable zip
or
Guidance on how to extract the necessary file from my CWMR backup of my previously working Lite ROM 0.9 installation.
Thanks in advance.

requiem_mortis said:
I've just returned my phone to stock UCLJ3 + LiteKernel-4.0-20130121
BLN warns me that "this iblights does not support BLN. - I tried copying across liblights.n1.so from the LiteROM_0.9.zip to no avail.
would some kind sole please provide a CWMR zip to flash, to update it.
or
provide me with a step by step guide on how to use https://nodeload.github.com/Adam77Root/liblights_bln/zip/master to build my own.
[GUIDE] How to make a cwm recovery flashable zip
or
Guidance on how to extract the necessary file from my CWMR backup of my previously working Lite ROM 0.9 installation.
Thanks in advance.
Click to expand...
Click to collapse
I just went back to stock ICS tonight as well and have me found in the same situation, to fix it all you need is to dowload the lights.n1.so - BLN.zip from here ---> http://forum.xda-developers.com/showthread.php?t=2067954
unzip it cause its not a flashable zip for some reason, transfer the lights.n1.so file you got from the zip to your sdcard, use any root enabled file explorer (i use rootbrowser lite myself) and copy the file to this directory --> system/lib/hw and paste it there, it should ask you to overwrite (back up the original file just in case) select yes and reboot. After that check the BLN app and you sould be able to activate it now :good: activate it and deactivated a couple time just in case lol it worked for me. Hope it helps.

Thanks
Thank you worked like a charm.

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers

[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible

Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image

I dont get it
Sent from my Nexus 4 using xda app-developers app

gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch

Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl

hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake

Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?

hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?

Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?

hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.

Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?

hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery

Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!

hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?

Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.

Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails

Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..

subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation

Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files

Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk