[MOD][One Click Root]ClockworkMod 3.1.0.1[RFS & EXT4]

Status
Not open for further replies.
Search This thread

DRockstar

Retired Recognized Developer
Sep 30, 2010
309
561
Pasadena, CA
I installed per your instructions. Then once I rebooted, I installed RomManager. But I reboot into recovery from within RomManager, it takes you to cwm-3.0.0.6. Isn't it supposed to take you to cwm-3.0.2.5? Also, is the cwm3.0.2.5 in DRockstar's thread the updated version of cwm3.0.2.5? If not, can we get a flashable .zip of the updated cwm3.0.2.5 please?

just so you know, the cwm versions from both this one click, and the cwm3.0.2.5.zip are the same.

also, you can try out my kernel for reboot recovery and ROM Manager functions, if you haven't already:

Clean Kernel EC05

I know Rodderik is updating his kernel, and I have shared my sources, so other kernel devs can easily see how to do, and I have a commit for the entire initramfs changes that are needed for the kernel.

Hope that helps!
 

sniperkill

Senior Member
Sep 27, 2010
1,648
320
Maryland
just so you know, the cwm versions from both this one click, and the cwm3.0.2.5.zip are the same.

also, you can try out my kernel for reboot recovery and ROM Manager functions, if you haven't already:

Clean Kernel EC05

I know Rodderik is updating his kernel, and I have shared my sources, so other kernel devs can easily see how to do, and I have a commit for the entire initramfs changes that are needed for the kernel.

Hope that helps!

Oh, I see. The only things Rodderick changes is his kernel, not the cwm-3.0.2.5... thanks, that does help!

Sent from my SPH-D700 using XDA App
 

shiftr182

Senior Member
Oct 5, 2010
1,996
1,228
Boise
Google Pixel 8 Pro
I used the one click method to do this, and verified it worked because when I booted to recovery, it read 3.0.2.5.

My question is how do I tell it to format ext4 or rfs, or do I? If I dont, how do I know how the fs is formated?
 
Last edited:

DRockstar

Retired Recognized Developer
Sep 30, 2010
309
561
Pasadena, CA
I used the one click method to do this, and verified it worked because when I booted to recovery, it read 3.0.2.5.

My question is how do I tell it to format ext4 or rfs, or do I? If I dont, how do I know how the fs is formated?

Also, I restored a nand that I had done on ext4, and when it booted, there was none of my data or apps. I reflashed the old cwm, then restored the same nand, and everything was there.

firstly, the mount command, from either connectbot, or adb, will show all mounts, and what fs they use.

if a restore of your backup wasn't successful, then it most likely failed after the boot restore.

in cases like this, in cwm, choose:

backup and restore > advanced restore > {choose backup} > {choose partition to restore}

in your case, just restoring backup, and perhaps system, will give you your desired results.

Hope this helps!
 
Last edited:

Shoulon

Senior Member
Apr 12, 2008
1,999
239
So does this mean no more bashing on "epic has a Poor port of cwm"...?

Anyway, thank-you!! Also I love the new button maps. =)

Sent from my Epic 4G using XDA
 

sniperkill

Senior Member
Sep 27, 2010
1,648
320
Maryland
I used the one click method to do this, and verified it worked because when I booted to recovery, it read 3.0.2.5.

My question is how do I tell it to format ext4 or rfs, or do I? If I dont, how do I know how the fs is formated?

Firstly, I don't think cwm-3.0.2.5 formats ext4 or rfs. I THINK it just restores ext4 and rfs, also in back-ups. Cwm-3.0.0.6 formats ext4, and also Dameon87 has a .zip file in the OP that formats ext4. In case you don't wanna keep going back n forth between 3.0.0.6 and 3.0.2.5.

Sent from my SPH-D700 using XDA App
 
Last edited:

Shoulon

Senior Member
Apr 12, 2008
1,999
239
Firstly, I don't think cwm-3.0.2.5 formats ext4 or rfs. I THINK it just restores ext4 and rfs, also in back-ups. Cwm-3.0.0.6 formats ext4, and also DRockstar (I think) has a .zip file that formats ext4. In case you don't wanna keep going back n forth between 3.0.0.6 and 3.0.2.5.

Sent from my SPH-D700 using XDA App

If the rom is designed to be ext4 it won't switch between the two.(ext4 and rfs) Same with kernel.

Example, if u flash Syndicatefrozen 1.1 you will be ext4 automtically. Same with bonsai. If u do a backup of a ext4 rom, it'll stay ext4. Because sydicate is a ext4 rom

Other roms idk yet. Please docorrect me if I'm mistaken. ><

Sent from my Epic 4G using XDA
 
Last edited:

sniperkill

Senior Member
Sep 27, 2010
1,648
320
Maryland
ok so i figured out we should just wait until you favorite kernels update to the new CWM as to keep the issues to a minimum. you can try to run the one click again but it all depends on how your favorite kernel handles recovery. the safest bet will be to wait until they have a chance to update them.

Thanks for looking into it for me. I'll use DRockstars clean kernel for now. I got it all working now. You guys keep up the great work!!



Sent from my SPH-D700 using XDA App
 

musclehead84

Senior Member
Nov 3, 2010
4,582
967
39
Falling Waters, WV
I used the one click method to do this, and verified it worked because when I booted to recovery, it read 3.0.2.5.

My question is how do I tell it to format ext4 or rfs, or do I? If I dont, how do I know how the fs is formated?

If you want to convert to ext4 u can either use the instructions in the op to convert to ext4 or flash a rom that auto converts for u like acs or bonsai. Just like they said use terminal and type in mounts and it will tell u what each partition filesystem is

Sent From My Evo Killer!
 

nubecoder

Inactive Recognized Developer
Dec 5, 2010
569
556
Could someone please confirm this for me as I wont have time until later today...

In the more recent versions of CWM there is not a "Go Back" menu entry...
If you use the VolDown key and "scroll" past the bottom entry (which brings you back to the top) it will enable the "Go Back" menu entry.
You need to "scroll" past the bottom entry twice for it to work (if I'm not mistaken).

There's a chance this "feature" isn't in this version of CWM, but I thought I'd mention it in case it is.
I'm also not sure if the change persists through a reboot or not...

Please post back here if you can confirm this as working or not...
Thanks.

=]
 
  • Like
Reactions: vocaltreat

Rodderik

Inactive Recognized Developer
Sep 8, 2010
1,300
1,295
devphone.org
Could someone please confirm this for me as I wont have time until later today...

In the more recent versions of CWM there is not a "Go Back" menu entry...
If you use the VolDown key and "scroll" past the bottom entry (which brings you back to the top) it will enable the "Go Back" menu entry.
You need to "scroll" past the bottom entry twice for it to work (if I'm not mistaken).

There's a chance this "feature" isn't in this version of CWM, but I thought I'd mention it in case it is.
I'm also not sure if the change persists through a reboot or not...

Please post back here if you can confirm this as working or not...
Thanks.

=]

Booted CWM and scrolled down twice on the main menu and it spit out a message "Back menu button enabled." Then when you enter a new menu the "*****Go Back****" shows up in the menus. It is a good alternative if the capacitive buttons don't work for some reason on your device.
 

Rodderik

Inactive Recognized Developer
Sep 8, 2010
1,300
1,295
devphone.org
I got this PM but cannot reply so I'm posting it in the thread here so every one will know.

jwebe03 said:
Hey Bro - My Antivirus keeps attacking this download, Its windows and would normally ignore it - But I have never had it go off on any other XDA file I have downloaded. Prob Nothing, just wanted to give you a heads up.
Great work btw!

JW

Since rageagainstthecage is a malicious program (specifically it is an exploit of adb to get root) it is detected by a lot of anti virus programs...I've noticed lately more and more programs picking up on it but it is a false positive and is perfectly safe :)
 

GRK4G63

Senior Member
Just installed this on my Epic without a single problem!

ROM: Syndicate FROzen (EXT4)
Theme: BionixBlack

Thanks for the post! I was wondering when a newer version of CWM would be available. I kept trying to flash 3.0.2.4 but when I'd reboot, it would seem to "forget" the installation and go back to 3.0.0.6. Oh well, I'm all set now. Keep up the great work! :)
 

pongoface

Senior Member
Jan 13, 2008
982
803
Experienced Evo 4g rooter here, just bought my girl an epic and about to root it using this method. 2 questions, 1 How do you boot into recovery from phone off. On the evo it is power volume down. 2nd from experienced epic rooters, what is the most stablest rom on xda for the epic that my 3year old could run lol.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 58
    [MOD][One Click Root]ClockworkMod version 3.1.0.1[RFS & EXT4]

    One Click Root does NOT work on Gingerbread!Read on for why.


    Standard disclaimer: I think you guys know the deal by now. I am not responsible for anything you do, don't do, don't read, or brick.

    If you are already rooted and have ClockworkMod installed and you just need to upgrade CWM please visit DRockstar's thread: [RECOVERY][GPL] ClockworkMod 3.1.0.1 PURPLE UPGRADE RFS/EXT4/USB CUSTOM FOR EPIC4G

    This is an updated and refreshed One Click Root based off Dameon87's 3.0.0.6 version here (originally based off work from noobnl and firon). It has been updated and fixed by myself (Rodderik) and DRockstar.

    Huge credit goes to DRockstar. Without his persistence and hard work we would not have a new working recovery image. He spent many hours fixing and testing the image after bugging koush to compile a ROM Manager compatible, dual file system recovery. Credit also goes to the noobnl and firon for the original one click root scripts, koush for giving us a new better recovery, Dameon87 for his one click changes and EXT4 conversion script, tanimn and all the other developers that worked hard to contribute to the new recovery.

    UPDATED 6/24/2011
    updated to Clockwork Mod 3.1.0.1_purple by DRockstar
    updated busybox to latest (1.18.4)
    updated recovery.fstab
    tweaked script to hopefully improve success rate
    fixed redirector (again)
    plus some other misc fixes

    Includes:
    Dual file system support (RFS & EXT4)
    New ClockworkMod (v3.0.2.5)
    koush's latest hacked adbd
    Superuser.apk (v2.3.6.1)
    busybox (v1.18.0.git)
    su (v2.3.1-ef)
    Switched to bmlwrite for flashing
    Added scripts for mounting UMS (by DRockstar)
    FIXED REDIRECTOR!!!
    Rom Manager Compatible
    Works properly on Mac OSX

    Tested with EC05 (Froyo), EB13 (Froyo), and DI18 (Eclair)
    Works on: Windows, Linux, and Mac OSX
    For future reference the rageagainstthecage root exploit has been patched in Gingerbread. Refer to DRockstar's post on Gingerbreak for rooting Gingerbread (this also works on the Epic running Froyo)


    Instructions:

    Windows
    1. Extract zip to a folder
    2. Ensure phone is in usb debugging mode and connected to your computer
    3. Run the run.bat
    4. Follow on screen instructions

    Linux
    1. Extract zip to a folder
    2. Ensure phone is in usb debugging mode and connected to your computer
    3. Open a terminal and navigate to the unzipped folder
    4. Type: chmod 777 run.sh
    5. Type: ./run.sh
    6. Follow on screen instructions

    Mac OSX
    1. Extract zip to a folder
    2. Ensure phone is in usb debugging mode and connected to your computer
    3. Open a terminal and navigate to the unzipped folder
    4. Type: chmod 777 run.sh
    5. Type: ./run.sh
    6. Follow on screen instructions

    qbking77 has done a nice video tutorial on using Windows to root and install ClockworkMod using this method. You can see his video here: http://www.youtube.com/watch?v=ymN1H2e9YMk
    Thanks qbking77!

    dansan382 also made a video that you can find here.

    Notes:
    1. Button mappings are slightly different from older versions of CWM. Volume buttons = Up and Down, Power or Camera = Enter, Capacitive Back = Back. Capacitive Home also works as enter but not correctly from the main menu so if you hit it and the screen disappears hit Capacitive Home again or Capacitive Back to bring it back.
    NOTE: As of 3.1.0.1 the buttons have been sorted out.
    2. KNOWN ISSUE: When invoked, reboot recovery requires a re-plug of the usb cable for adb to work again. Simply unplug the usb cable and plug it back in.
    3. If the script does not reboot your phone at the end please run the script again. If it still doesn't work reboot the phone and run the script again.
    4. USB Mass Storage can be mounted from inside of recovery. 'adb shell' into the phone and type 'mountums' MAKE SURE YOU SAFELY REMOVE/EJECT BEFORE RUNNING 'umountums' to safely unmount sdcard.
    NOTE: As of 3.1.0.1 mounting from the menu works again!
    5. There is a Go Back menu option but it must be enabled. See the post here.
    6. VIRUS ALERT!!! rageagainstthecage may be detected by your antivirus program but it is NOT harmful to your computer. See this post for an explanation.
    7. A few users report issues with 3.1.0.1 not booting. If that happens then use 3.0.2.5.

    Download: http://devphone.org/files/epic4g/oneclickroot/OneClickRootCWM3.1.0.1-EC05.zip
    md5: 57d787dba5a478eb088f148e0dff2ef0

    Previous version(s): http://devphone.org/files/epic4g/oneclickroot/OneClickRootCWM3.0.2.5-EC05.zip

    EXT4/RFS Conversion:
    For converting RFS to EXT4 or EXT4 to RFS please see this post by chris41g: Rfs2Ext4 and Ext42Rfs CWM 3.0.25 flashable zips. These will work fine with ClockworkMod 3.1.0.1

    FYI, the EXT4 conversion script is not necessary if you are flashing a ROM that properly formats to EXT4, unless you plan to keep data (which isn't recommended coming from stock anyway, use MyBackup Root if you must). Currently, only SRF, Bonsai, and the journal-off version of midNIGHT (I have not checked 5.3) do this. Other ROMs only use delete_recursive() in their updater-script - so flashing them will work, but you'll get RFS!
    If you are flashing a new rom please make sure you check or ask if you need to take additional steps to convert your filesystem.
    10
    Here is sample output from a run in Linux. Windows and Mac OSX should be similar. You may or may not get "sudo: adb: command not found" but it is ok so long as the script runs correctly. Getting the error is dependent on how your environment is set up. If you get any other errors you will need to run the script again.

    rodderik@roddlaptop:~/Desktop/OneClickRootCWM3.0.2.5-EC05$ ./run.sh

    One Click Root & CWM 3.0.2.5 for the Epic 4G

    Updated and tweaked by Rodderik and DRockstar 5/10/2011

    Original one click by joeykrim and one click installer by noobnl and firon
    busybox by skeeterslint
    Huge credits go out to:
    koush - dual fs recovery binary
    DRockstar - recovery kernel build

    Press any key to continue...Starting adb server
    sudo: adb: command not found
    sudo: adb: command not found
    Copy and run the exploit (may take up to two minutes)
    98 KB/s (5392 bytes in 0.053s)
    0 KB/s (43 bytes in 0.044s)
    [*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C

    [*] checking NPROC limit ...
    [+] RLIMIT_NPROC={2662, 2662}
    [*] Searching for adb ...
    [+] Found adb as PID 2974
    [*] Spawning children. Dont type anything and wait for reset!
    [*]
    [*] If you like what we are doing you can send us PayPal money to
    [*] 7-4-3-C@web.de so we can compensate time, effort and HW costs.
    [*] If you are a company and feel like you profit from our work,
    [*] we also accept donations > 1000 USD!
    [*]
    [*] adb connection will be reset. restart adb server on desktop and re-login.
    Wait for phone to reconnect...
    Mount system as r/w, cleanup old files, do some basic configuration
    96 KB/s (4793 bytes in 0.048s)
    Copying files onto phone...
    499 KB/s (26264 bytes in 0.051s)
    2097 KB/s (196521 bytes in 0.091s)
    2048 KB/s (927544 bytes in 0.442s)
    6 KB/s (327 bytes in 0.052s)
    Setting permissions...
    Installing busybox...
    Installing clockworkmod redirector
    108 KB/s (6535 bytes in 0.059s)
    push: recoveryfiles/etc/recovery.fstab -> /system/bin/recoveryfiles/etc/recovery.fstab
    push: recoveryfiles/sdparted -> /system/bin/recoveryfiles/sdparted
    push: recoveryfiles/mountums -> /system/bin/recoveryfiles/mountums
    push: recoveryfiles/umountums -> /system/bin/recoveryfiles/umountums
    push: recoveryfiles/fix_permissions -> /system/bin/recoveryfiles/fix_permissions
    push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
    push: recoveryfiles/tune2fs -> /system/bin/recoveryfiles/tune2fs
    push: recoveryfiles/recovery_wrapper -> /system/bin/recoveryfiles/recovery_wrapper
    push: recoveryfiles/nandroid-md5.sh -> /system/bin/recoveryfiles/nandroid-md5.sh
    push: recoveryfiles/killrecovery.sh -> /system/bin/recoveryfiles/killrecovery.sh
    push: recoveryfiles/e2fsck -> /system/bin/recoveryfiles/e2fsck
    push: recoveryfiles/parted -> /system/bin/recoveryfiles/parted
    push: recoveryfiles/adbd -> /system/bin/recoveryfiles/adbd
    push: recoveryfiles/postrecoveryboot.sh -> /system/bin/recoveryfiles/postrecoveryboot.sh
    14 files pushed. 0 files skipped.
    1538 KB/s (2018303 bytes in 1.280s)
    push: recoveryfiles/etc/recovery.fstab -> /system/bin/recoveryfiles/etc/recovery.fstab
    1 file pushed. 0 files skipped.
    8 KB/s (515 bytes in 0.060s)
    push: recoveryres/images/progress_bar_empty_right_round.png -> /system/bin/recoveryres/images/progress_bar_empty_right_round.png
    push: recoveryres/images/icon_clockwork.png -> /system/bin/recoveryres/images/icon_clockwork.png
    push: recoveryres/images/icon_error.png -> /system/bin/recoveryres/images/icon_error.png
    push: recoveryres/images/indeterminate2.png -> /system/bin/recoveryres/images/indeterminate2.png
    push: recoveryres/images/progress_empty.png -> /system/bin/recoveryres/images/progress_empty.png
    push: recoveryres/images/progress_fill.png -> /system/bin/recoveryres/images/progress_fill.png
    push: recoveryres/images/progress_bar_fill.png -> /system/bin/recoveryres/images/progress_bar_fill.png
    push: recoveryres/images/icon_firmware_install.png -> /system/bin/recoveryres/images/icon_firmware_install.png
    push: recoveryres/images/progress_bar_empty_left_round.png -> /system/bin/recoveryres/images/progress_bar_empty_left_round.png
    push: recoveryres/images/icon_firmware_error.png -> /system/bin/recoveryres/images/icon_firmware_error.png
    push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/icon_installing.png
    push: recoveryres/images/progress_bar_left_round.png -> /system/bin/recoveryres/images/progress_bar_left_round.png
    push: recoveryres/images/indeterminate3.png -> /system/bin/recoveryres/images/indeterminate3.png
    push: recoveryres/images/progress_bar_right_round.png -> /system/bin/recoveryres/images/progress_bar_right_round.png
    push: recoveryres/images/progress_bar_empty.png -> /system/bin/recoveryres/images/progress_bar_empty.png
    push: recoveryres/images/indeterminate6.png -> /system/bin/recoveryres/images/indeterminate6.png
    push: recoveryres/images/indeterminate4.png -> /system/bin/recoveryres/images/indeterminate4.png
    push: recoveryres/images/indeterminate5.png -> /system/bin/recoveryres/images/indeterminate5.png
    push: recoveryres/images/indeterminate1.png -> /system/bin/recoveryres/images/indeterminate1.png
    push: recoveryres/keys -> /system/bin/recoveryres/keys
    20 files pushed. 0 files skipped.
    78 KB/s (81069 bytes in 1.010s)
    Installing clockworkmod recovery...
    794 KB/s (66884 bytes in 0.082s)
    3213 KB/s (5478824 bytes in 1.664s)
    Cleaning up files...
    sudo: adb: command not found
    All done!

    If your phone did not reboot or root does not
    work correctly. Please rerun the script.
    Press any key to exit the script.

    rodderik@roddlaptop:~/Desktop/OneClickRootCWM3.0.2.5-EC05$
    3
    Hehe, it's about time, this needs sticky at top of the dev board!

    Great work, Rodderik spent some time learning root and the cwm redirector, to make this happen.... I think we both have tweaked it out, so that anyone on any computer can use it, now

    I've been waiting for a single solution for a long time now, so I'm very glad to see it happen.
    2
    Hehe, it's about time, this needs sticky at top of the dev board!

    Great work, Rodderik spent some time learning root and the cwm redirector, to make this happen.... I think we both have tweaked it out, so that anyone on any computer can use it, now

    I've been waiting for a single solution for a long time now, so I'm very glad to see it happen.

    Yeah buddy! I couldn't have done it without your work and help. Thanks a bunch and I can't wait for the AIO. :D
    2
    This is outdated. Do not use any longer.

    Sent from my PantechP4100 using xda premium