Originally Posted by k0nane

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!

EDIT: And, lots of credit to tanimn for tireless hard work on this project.

Quoted your post in the OP and added tanimn to credits. Thanks K0nane for pointing this out.

@Rodderick, or DRockstar, quick question please.

---

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?

Originally Posted by sniperkill

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?

if you install rom manager and click flash clockworkmod recovery and select epic4g it says that the epic doesn't have an officially supported cwm yet but allows you to manually say yes and this should allow rom manager to work...this is all we can do until koush gets back in town to make the change to rom manager for us but he did compile this cwm recovery binary for us so it is official. it just required some tweaking by DRockstar and tanimn and a few of the other devs to get it all working correctly.

Originally Posted by Rodderik

if you install rom manager and click flash clockworkmod recovery and select epic4g it says that the epic doesn't have an officially supported cwm yet but allows you to manually say yes and this should allow rom manager to work...this is all we can do until koush gets back in town to make the change to rom manager for us but he did compile this cwm recovery binary for us so it is official. it just required some tweaking by DRockstar and tanimn and a few of the other devs to get it all working correctly.

Thanks for the quick reply. But yes, I did do all that with RomManager, but it still takes me to cwm-3.0.0.6. But, if I shut it down, then 3 fingure boot, that takes me to cwm-3.0.2.5... Also, I greatly appreciate all the hard work you guy's do, so dont take me wrong, i'm deffinatly not complaining.. I love all the work you guys do!!!

Originally Posted by sniperkill

Thanks for the quick reply. But yes, I did do all that with RomManager, but it still takes me to cwm-3.0.0.6. But, if I shut it down, then 3 fingure boot, that takes me to cwm-3.0.2.5...

what kernel are you using? if the kernel hasn't been updated and you flashed after the one click process then rom manager will boot whatever recovery comes with your kernel. 3.0.2.5 should still be one bml8 for 3 finger boots unless the rom reflashes that as well. run the one click again now after you are all setup and rom manager should boot into 3.0.2.5

Originally Posted by Rodderik

what kernel are you using? if the kernel hasn't been updated and you flashed after the one click process then rom manager will boot whatever recovery comes with your kernel. 3.0.2.5 should still be one bml8 for 3 finger boots unless the rom reflashes that as well. run the one click again now after you are all setup and rom manager should boot into 3.0.2.5

Nice catch, I didnt even think about that. And yes, I did flash midnight-5.3.. So, imma have to figure another route.

On another note, does this OneClickRoot cwm-3.0.2.5 work with the official EC05?

Also, if you run the OneClickRoot cwm3.0.2.5 more than once, does it just overwrite the previously written files from running it the first time?

Originally Posted by sniperkill

Nice catch, I didnt even think about that. And yes, I did flash midnight-5.3.. So, imma have to figure another route.

On another note, does this OneClickRoot cwm-3.0.2.5 work with the official EC05?

Also, if you run the OneClickRoot cwm3.0.2.5 more than once, does it just overwrite the previously written files from running it the first time?

i think i just got a bad flash testing this for you...i loaded eb13 and will ota to EC05 but it was tested to work.

Originally Posted by Rodderik

i think i just got a bad flash testing this for you...i loaded eb13 and will ota to EC05 but it was tested to work.

Im sorry man, you dont gotta do that for me, as I'm sure I'll figure it all out. I'm pretty good at most of this kinda stuff. Fix your phone and keep up the great work buddy!!

Originally Posted by sniperkill

Im sorry man, you dont gotta do that for me, as I'm sure I'll figure it all out. I'm pretty good at most of this kinda stuff. Fix your phone and keep up the great work buddy!!

it's all good...i did the OTA to EC05 again and verified the one click root does work. being as how the OTA is odexed I know my kernel refuses to boot it as ext4 (its the only scenario it wont boot) i'm going to restore my nandroid and rerun the one click but we might have to wait until kernels are updated

i'll let you know shortly

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.