[Root] Samsung Epic 4G Official Froyo EC05 w/Optional EXT4

[ragnarokx]

Standard Disclaimer: as with any Android modification, proceed at your own risk.

There are two procedures listed below: Procedure 1 will root your phone and install ClockworkMod Recovery v2.5.1.0, leaving your filesystem in its stock RFS state; alternatively, Procedure 2 will install ClockworkMod Recovery v3.0.0.6 and convert your RFS filesystem to EXT4, allowing you to flash the latest ROMs and kernels.

It is recommended that you backup anything on your phone that you need before proceeding.

What is a filesystem?
A filesystem is a method of storing and organizing files and their data. Basically, a filesystem organizes your files into a database for the storage, organization, manipulation, and retrieval by the Android operating system.

What's the difference between RFS and EXT4?
RFS is Samsung's proprietary filesystem, which has a pretty poorly written driver and is overall not very efficient. EXT4 is the filesystem used by Linux, and is more efficient than RFS. EXT4's efficiency over RFS gives a noticeable boost in operating system responsiveness/performance (the nimble Nexus S uses EXT4).

What are the pros and cons of converting to EXT4?
Pros: increased OS speed/responsiveness, ability to install newer ROMs that require EXT4. Cons: once you convert to EXT4, if you want to flash a ROM that does not support EXT4 you must use Odin or flash a special zip in Clockwork to return to RFS (see last question before the procedure for more info).

What does this procedure do to my phone exactly?
It will permanently root your phone (if not already rooted; also safe for rooted phones), as well as install Clockwork v3.0.0.6, which will format "/cache", "/data" and "/system" from RFS to EXT4. Having an EXT4 filesystem will enable you to install ROMs with EXT4 support, and having Clockwork v3.0.0.5 will enable you to flash ROMs, kernels, themes, etc. that use Edify scripts.

What's an Edify script?
There are currently two ways to create flashable zip scripts. The first one is "update-script", also known as Amend. Amend was the first version of the scripting language created by Google, and was used in Android 1.0 and Cupcake (1.5). However, Amend has two serious design flaws: function arguments can not span more than 1 word, and the scripting language is compiled into the recovery causing image bloat and inflexibility. Because of this reason Google removed Amend support in Donut and beyond, and instead switched to update-binary and updater-script, which is also known as Edify.

However, Amend support was left in Clockwork, to help ease the transition off its usage in ROM creation. Clockwork needed to transition to using the newer Edify scripts to be compatible with Gingerbread. So we now have a recovery that is Gingerbread ready and uses the better Edify scripts instead of Amend scripts.

What do I need to get started?
A Windows computer (this is also possible on OSX and Linux, however there will be procedural differences not covered here), a USB cable, and an Epic 4G with official Froyo EB13 installed (does not matter if you're already rooted or have a custom ROM).

Is there any way to go back to my original setup after I do this?
Yes, you can use Odin to return to a completely stock state - see this thread.

 

[ragnarokx]

Procedure 1 - gives root access and leaves filesystem untouched (stock RFS)

If you want EXT4, skip this procedure and go to Procedure 2

Note: This may take several tries before being successful, so be patient.

0. You must have Froyo EC05 (official Android 2.2) before continuing to the next step. If you need to update from Eclair or an older version of Froyo, go to this thread: How to Update to Froyo EC05. Once you're done, come back and head down to the next step.

1. Download and install the appropriate drivers for your Windows system:
32-bit drivers
64-bit drivers

Plug your Epic into your computer via USB and let Windows recognize your phone/configure the drivers. After Windows is done with the drivers, unplug your Epic.

2. Download the one click root exploit (credit: noobnl) and extract it to a folder on your Windows desktop.

3. On your phone, push MENU, then select Applications > Development, then enable USB debugging and connect your phone to your computer via USB.

The type of USB cord and the specific USB computer port can make or break your ability to successfully root. If you are getting errors in the command prompt during step 4, trying swapping USB cables and/or switching USB ports (even the USB cord that came with the phone can cause problems!).

4. Now double click "run.bat" in the folder from Step 2. If all goes well, your Windows command prompt should look something like this:

If the command prompt asks you to restart adb, you need to go into Windows Task Manager (ctrl-alt-del on your keyboard) and end adb in the process tab, then go into the folder from Step 2 and double-click on the "adb" file to restart adb.

If the command prompt says "device not connected", disconnect the phone and reboot it, turn debugging mode back on, reconnect the phone via USB, and rerun the "run.bat" file again. If you're still getting "device not connected", try repeating these steps one at a time or in a different order, for example just kill adb and rerun "run.bat" or only reboot the phone and then rerun "run.bat".

After Rooting
An easy way to confirm that the rooting process was successful is to download a free app called Titanium Backup from the Market - upon startup the app will tell you if you have root access. If a "Superuser" pop-up window appears when you start Titanium Backup, push "Allow".

What is Superuser? It is an app that was installed when you rooted. Anytime there is a request to modify a low-level file or folder on your phone, Superuser will let you know and give you the chance to confirm or deny it access. This is a safety measure. If you happen to download a malicious app, Superuser will stop it from modifying low-level data and notify you. If an app you trust is requesting root access, just check the "Always Allow" box and it won't ask you again.

 

[ragnarokx]

Procedure 2 - gives root access and converts your RFS filesystem to EXT4

0. Steps 1-8 are for users already on Froyo EC05. If this is you, proceed to Step 1 now.

If you are on Eclair or a leaked version of Froyo, go to this thread: How to Update to Froyo EC05. Once you've updated to EC05, you can complete Steps 1-8 to get EXT4.

If you are on the official Froyo EB13 and already have EXT4, simply flash the EC05 EXT4 ROM of your choice in ClockworkMod3 and then flash the EC05 modem using Odin. If you are on Froyo EB13 but do not already have EXT4, you can either obtain EXT4 on EB13 first and then flash an EC05 EXT4 ROM in ClockworkMod3, or you can update to EC05 and then follow Steps 1-8, the choice is yours.

1. Download and install the appropriate drivers for your Windows system:
32-bit drivers
64-bit drivers

Plug your Epic into your computer via USB and let Windows recognize your phone/configure the drivers. After Windows is done with the drivers, unplug your Epic.

2. Download an EC05 ROM that supports EXT4 (e.g. Bonzai 4.0, Syndicate 1.1, etc.) and place it on the root (not in a folder) of your SD card.

3. Go to this thread and download "OneClickRootCWM3-EB13.zip" (filename is correct, this zip works for EB13 and EC05) onto your computer, then extract it to a folder on your Windows desktop.

4. On your phone, push MENU, then select Applications > Development, then enable USB debugging and connect your phone to your computer via USB.

5. Now double click "run.bat" in the folder from Step 2.

The type of USB cord and the specific USB computer port can make or break the success of this installation. If you are getting errors in the command prompt during this step, trying swapping USB cables and/or switching USB ports (even the USB cord that came with the phone can cause problems!).

If the command prompt asks you to restart adb, you need to go into Windows Task Manager (ctrl-alt-del on your keyboard) and end adb in the process tab, then go into the folder from Step 2 and double-click on the "adb" file to restart adb.

If the command prompt says "device not connected", disconnect the phone and reboot it, turn debugging mode back on, reconnect the phone via USB, and rerun the "run.bat" file again. If you're still getting "device not connected", try repeating these steps one at a time or in a different order, for example just kill adb and rerun "run.bat" or only reboot the phone and then rerun "run.bat".

Antivirus programs can also cause problems. If you still can't get the run.bat file to work, try disabling your antivirus software.

If all goes well your command prompt should look something like this:

6. Turn off your phone, and then hold these buttons: volume down+camera+power, until you see the Clockwork screen that has orange text. Clockwork v3.0.0.6 will now automatically convert your filesystem from RFS to EXT4. This may take a while. Once Clockwork is finished DO NOT reboot until after completing Step 8. Now proceed to Step 7 below.

7. In the main screen of Clockwork, go to Wipe data/factory reset>Yes and repeat for a total of 3 times. Do the same for Wipe cache partition>Yes, as well as Advanced>Wipe Dalvik Cache>Yes.

8. Now before you reboot, you need to flash the ROM from Step 2. Go to: install zip from sdcard>choose zip from sdcard>(navigate to the ROM .zip file on your SD card)>(select it using the camera button)>yes. The ROM will now be flashed. Once the flashing is complete, you can now reboot and enjoy your new EXT4 filesystem Note: if you have problems booting up, you may need to repeat this step and flash your ROM a second time.

Optional: you can confirm you have successfully converted to EXT4 by using the command

adb shell mount

or

adb shell df

Your command prompt will return something like this:

Picture courtesy of BlackPearl890

Notice it mentions "ext4", not "rfs".

Important Notes
You must boot into Clockwork v3.0.0.6 by turning off your phone and holding volume down+camera+power buttons. If you boot into Clockwork using a program like ROM Manager or Quickboot, you will get errors.

A quick way to manually boot into Clockwork is to press volume up+camera+power buttons to reset your phone, then immediately hold volume down+camera+power buttons until you see the recovery screen with orange text. Note: if you're using a ROM that has "no journaling", "journaling off", "journaling disabled", etc. do not use the three button reset or your data may become corrupted. If you're on a ROM that has journaling on then knock yourself out with this trick.

Also, as long as you have EXT4 in place you can only flash ROMs and kernels with EXT4 support. To flash a ROM or kernel without EXT4 support, you must use Odin to return to stock.

Any flashable zips you want to install must by compatible with the new Clockwork v3.0.0.6. This will be explicitly indicated, or there will be a note saying the zip is using the new Edify script (as opposed to the old Amend script).

 

[Officerpolabear]

For some reason, my phone won't be recognized when it's only in debug mode.so everytime I try to use the one click root, it says phone not recognized.but it does get recognized when it isn't in debug mode.

Edit: yes I have the drivers installed

 

[ragnarokx]

Here are a few things that come to mind to try: different USB cable, different USB port, disable antivirus software, run .bat file as Administrator in Windows, reset phone and computer and try again, or disconnect and reconnect phone via USB.

 

[Officerpolabear]

Okay thanks I will try that

 

[Officerpolabear]

Okay well I got my epic being recognized but now the part I'm stuck on is after doing a factory reset, wiping cache, and wiping dalvik cache 3 times and i put on Bonsai 4.0.0, after the samsung screen goes by a black screen is shown and my phone vibrates and goes into a boot loop.

Sorry if I have needed help on this so much but this is probably the last time for this

 

[foogama]

Okay well I got my epic being recognized but now the part I'm stuck on is after doing a factory reset, wiping cache, and wiping dalvik cache 3 times and i put on Bonsai 4.0.0, after the samsung screen goes by a black screen is shown and my phone vibrates and goes into a boot loop.

Sorry if I have needed help on this so much but this is probably the last time for this

Same thing happened to me. It happened when I tried this from EB13 AND EC05.

My guess is it has something to do with Clockwork v3.0.0.6

I wish there was a way to just run stock Froyo rooted, with EXT4 support.

 

[traumahawk]

is there any reason i should bother switching to this EC05 build and not stay on EB13?

 

[dcraig]

Same thing happened to me. It happened when I tried this from EB13 AND EC05.

My guess is it has something to do with Clockwork v3.0.0.6

I wish there was a way to just run stock Froyo rooted, with EXT4 support.

Yes! This is exactly what I want! Then you can flash what you'd like. I thought you'd be able to one click root with EXT4 then convert via cwm and flash a new kernel and you'd be good to go?

I just like how stable stock froyo can be and being able to have EXT4 support with flashable options would be great. Is this possible? Also i'm sure it would be better to be on a deodexed EC05 though.

 

[ragnarokx]

Since only the kernel is really needed to get EXT4 working, I've created a flashable zip with Bonsai's kernel only and revised post #3.

Let me know if the new EXT4 procedure works for you guys.

 

[drekosh]

File system is converting now. I'll looking good so far.

*edit - Vibrating boot loop here too. No luck.

*edit 2 - I didn't pay that close to the messages when I restarted it and converted to EXT4. I have used Odin to get back to 2.1 and the upgraded to EC05 again. I'm going to watch it and see if there is anything funny going on this time. It is running the conversion now. Stay tuned.

 

[dtm_stretch]

Yup same vibrating loop also.

 

[dtm_stretch]

File system is converting now. I'll looking good so far.

*edit - Vibrating boot loop here too. No luck.

*edit 2 - I didn't pay that close to the messages when I restarted it and converted to EXT4. I have used Odin to get back to 2.1 and the upgraded to EC05 again. I'm going to watch it and see if there is anything funny going on this time. It is running the conversion now. Stay tuned.

I flashed the kernel before restarting and I still got the vibrating loop.

 

[drekosh]

Ok, i think I found the problem. It never says it is converting. Just backing up. Then checking the md5 sum, and then goes right into recovering.

Getting ready to recover with Odin again.

 

[dtm_stretch]

Yeah now that I think about it, mine did the same thing.

 

[drekosh]

Since it didn't say it converted to EXT4, I didn't install the kernel. Just restarted it and it got stuck on the Samsung startup screen. Not much better than the vibrating loop.

 

[ragnarokx]

We might need to get a stock deodexed EC05 before EXT4 works.

Sent by a little green robot

 

[drekosh]

Yeah, I reinstalled EC05, rooted it, and I'm going to leave it that way until we can get a stock deodexed version. It won't hurt to wait a little while for it.
EC05 seems to be without many, if any, bugs so it will more than be fine for now.

 

[Officerpolabear]

Yeah I just did the Odin method but it's still odexed