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

Search This thread
By:
Advanced…
S

shockdj

Member
Jul 15, 2010
17
6
upgraded to jph via kies, installed the custom rom, flashed your CF-Root JPH and my galaxy is flying, no force close errors.

Noticed a few apps dont work but i guess this is 2.2 incompatablities, also my market doesnt show my downloaded apps, just asks me to retry or cancel. Any ideas??

Good work on the fast update to get clockwork running tho. Well needed in these times of daily flashing lol :)
 
  • Like
Reactions: Figueiredo81
coradux

coradux

Senior Member
Mar 24, 2009
240
17
Chainfire said:
It took some hacking, but here it is, CF-Root for the JPH firmware. It's a much simpler root (to use) then the other methods available for JPH: a single PDA flash through ODIN is all there is to it.

THIS IS NOT A ROM - it is only a kernel. You need to have the JPH firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions.

Features
- Root
- Superuser 2.3.6.1
- Busybox 1.15.3
- "2e" recovery (can flash unsigned update.zip's)
- Integrated fix for ClockworkMod's nandroid (2.5.0.4)

Beta
This is a beta release. I've tested it in a few situations, doesn't mean it works for you. I have tested it on top of other installed rooting methods as well as from a clean flash, but there could still be issues, as most of you seem to have used a different root package than I have.

Instructions (short)
- Flash CF-Root-JPH-vX.X.tar (from the attached zip) as PDA in ODIN. 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-JPH-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-JPH-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)

Force closes ?
At first boot after the patch you may run into some force closes. DON'T PANIC. Wait a few minutes. Reboot, they should be gone now.

Notes
- ADB in recovery is flaky. Sometimes it works, sometimes it doesn't. If you go into ClockworkMod it usually works, though.
- An older version of BusyBox is used 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 :)

Download
Click to expand...
Click to collapse

Hi, I have JPH but I don't have 3 buttons combo. I there a way to install this with adb?
 
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
captive said:
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?
Click to expand...
Click to collapse

All busybox applets except "su" and "reboot" are symlinked in /system/xbin to /sbin/busybox

shockdj said:
upgraded to jph via kies, installed the custom rom, flashed your CF-Root JPH and my galaxy is flying, no force close errors.

Noticed a few apps dont work but i guess this is 2.2 incompatablities, also my market doesnt show my downloaded apps, just asks me to retry or cancel. Any ideas??

Good work on the fast update to get clockwork running tho. Well needed in these times of daily flashing lol :)
Click to expand...
Click to collapse

Probably has nothing to do with CF-Root, but of course it is possible I did something that breaks compatibility - I'm not an Android guru (yet). Regarding the Market, I noticed my downloaded apps weren't listed after flash (JPH, not CF-Root) either (only 2 or 3 of 100). Now a week later they are still not listed. Not sure what's up with that... I can still find them with a search, though.

coradux said:
Hi, I have JPH but I don't have 3 buttons combo. I there a way to install this with adb?
Click to expand...
Click to collapse

I'm not sure. ADB can reboot the phone into download mode, but I'm not sure whether you already need root for that or not.

The command would be: adb reboot download

Try it. If that command works, pull the battery and boot normally again. Then try the reboot download command again, but at the same time as the phone boots, pull the USB cable. The USB cable should be out of the phone before you see the download screen popup, so try timing it well.

This is because ODIN is really picky about the order and timing that USB cable is connected to the computer. If you don't do the order exactly right (no USB connected when download mode start, and don't reconnect it until ODIN is loaded) the flash often fails for who knows what reason. (At least for me it fails unless this is done perfectly)

Now with your phone in download mode, launch ODIN, select the .tar file with the PDA button, connect the phone again with the USB cable and press start. Done.

Let me know whether the adb reboot download command works without you having root :)
 
Last edited:
coradux

coradux

Senior Member
Mar 24, 2009
240
17
Chainfire said:
All busybox applets except "su" and "reboot" are symlinked in /system/xbin to /sbin/busybox



Probably has nothing to do with CF-Root, but of course it is possible I did something that breaks compatibility - I'm not an Android guru (yet). Regarding the Market, I noticed my downloaded apps weren't listed after flash (JPH, not CF-Root) either (only 2 or 3 of 100). Now a week later they are still not listed. Not sure what's up with that... I can still find them with a search, though.



I'm not sure. ADB can reboot the phone into download mode, but I'm not sure whether you already need root for that or not.

The command would be: adb reboot download

Try it. If that command works, pull the battery and boot normally again. Then try the reboot download command again, but at the same time as the phone boots, pull the USB cable. The USB cable should be out of the phone before you see the download screen popup, so try timing it well.

This is because ODIN is really picky about the order and timing that USB cable is connected to the computer. If you don't do the order exactly right (no USB connected when download mode start, and don't reconnect it until ODIN is loaded) the flash often fails for who knows what reason. (At least for me it fails unless this is done perfectly)

Now with your phone in download mode, launch ODIN, select the .tar file with the PDA button, connect the phone again with the USB cable and press start. Done.

Let me know whether the adb reboot download command works without you having root :)
Click to expand...
Click to collapse

The update failed and now the phone shows a picture of a phone and a pc conected with an exclamation mark.
 
thoriig

thoriig

Senior Member
Aug 9, 2010
87
10
works great on german t-mobile version.

first installed jpc followed by jph. installed your kernel. update.zip from rombie.

all fine without lagfix, but changed autokiller values to strict and changed scheduler to deadline. no "quadrant" e-penis, but feels very very smooth with launcher pro. access time on musicplayer (album pictures) is much faster then with apk-lagfix.

nandroid backup and restore tested without any problems.
 
R

RyanZA

Senior Member
Jan 21, 2006
2,023
784
JHB
Surely there must be an easier way to root Froyo than flashing a kernel? Do none of the froyo root exploits from other devices work?
 
Chainfire

Chainfire

Moderator Emeritus / Senior Recognized Developer
Oct 2, 2007
11,452
87,862
www.chainfire.eu
RyanZA said:
Surely there must be an easier way to root Froyo than flashing a kernel? Do none of the froyo root exploits from other devices work?
Click to expand...
Click to collapse

AFAIK it's the easiest way so far. Not exactly a difficult procedure. If you've flashed the ROM, flashing this after it should not be beyond anyone's skill level.

It's a hell of a lot easier than the old way, in any case :)
 
S

sccambuur

Member
Sep 19, 2010
12
0
If I use this way to root my Froyo 2.2, is it possible, after the root, to install Lagfix v2.0 from RyanZa? Or is this impossible?
 
TrOjAnUK

TrOjAnUK

Senior Member
Sep 28, 2009
2,396
1,013
Essex
Actually.. Odin shows PASS but the device shows as NOT rooted, I also have another issue.. If I set ADW launcher as default when I hit home it goes back to TW launcher.

Has ANYONE got ADW to work with froyo and this root??

TrOjAn
 
Last edited:
S

sccambuur

Member
Sep 19, 2010
12
0
Woohoo it works! I rooted my Froyo JPH 2.2, and have installed RyanZa OCLF, and got 2000 now! (before 986!).

Thanks!
 
You must log in or register to reply here.

Similar threads

Darkyy
  • Locked
[ROM] [22.07.2011] DarkyROM v10.2 ★ JVQ ★ What are you waiting for?
Replies
42K
Views
10M
Oswald Boelcke
Oswald Boelcke
D
  • Locked
[online KITCHEN] *ROM Kitchen* 10/5: Ginger JVH 2.3.3 up
Replies
40K
Views
7M
marcedli
marcedli
Lukiqq
[KERNEL] GALAXIAN [344MB][JVU][Voodoo Sound][EXT4][BLN][COLOR]
Replies
7K
Views
2M
Occasus
Occasus
stratosk
[KERNEL] Semaphore 2.7.4 (CF-Root + Voodoo Snd v10 + OC/UV + BLN)
Replies
8K
Views
2M
P
Patryk2003
H
[KERNEL] SpeedMod Gingerbread [K17-3 XWJW8 Value Pack CWM EXT4]
Replies
3K
Views
2M
saszseb
saszseb

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 244
    Chainfire
    Chainfire
    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
    View
    201
    Chainfire
    Chainfire
    CF-Root v3.2 for JPH, and ext4 tools v1.30 released

    CF-Root v3.2 for JVH has been released.

    No significant code changes compared to JVB version, just different base kernel, and a few minor script changes here and there.

    Please note I have not been able to test it very extensively. CWM appears to be fully functional, backup/restore works, ext4 works, root works, etc. Looks fine to me so far, but feel free to post about JVH specific issues.

    Also, making a backup on JVB using CWM, then flashing JVH, flashing CF-Root, going into CWM, doing advanced restore, and only restoring data seems to work without issue too. Nice trick to not lose any data/apps.

    Ext4 Tools has received a minor bugfix regarding /dbdata and /data FS type display (rfs or ext4) that were sometimes switched around.

    Enjoy, and don't forget to use the "Thanks" button and/or donate!
    View
    88
    Chainfire
    Chainfire
    --- 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
    View
    70
    Chainfire
    Chainfire
    --- 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
    View
    69
    Chainfire
    Chainfire
    --- 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
    View

New posts