Froyo EB13 Pre-Rooted, Deodexed, with Clockwork - RFS & EXT4

I got the tense part out of the way, and I now have ext4 and CWM 3.0, however I can't seem to load the ACE Rom from the sd card "file not found". I must not be getting it to the sd card correctly. The Rom is a bundle of books, what do I do at this point to get it to the sd card correctly so I may load ACE.

Thanks!!!!
 
- Connect your device via cable and select mass storage and drop it on your sdcard

- Pull your sdcard and use a sdcard reader/adapter to load it from your computer to the sdcard

If your still having troubles you may need to backup all your sdcard contents to your computer and format your sdcard and then move your backed up data to your sdcard once again.
 
It reads as update.zip, not ace.zip when I try to flash it. Arghhh... I've
Uploaded all files to the pc already, but not my backed-up apps. How do I format the sd.?
 
It reads as update.zip, not ace.zip when I try to flash it. Arghhh... I've
Uploaded all files to the pc already, but not my backed-up apps. How do I format the sd.?

When you boot into CWM to flash, are you using the option that says

Install zip from sdcard


If you are trying to use the "Apply update from sdcard" then that is your problem. This option is looking for a set file name of "update.zip".

Install zip from sdcard>choose zip from sdcard>(find ACE ROM 1.7 on your sdcard)>Yes - Install ACE ROM 1.7.zip

BTW, don't forget to wipe before you flash :)
 
Okay.. It appeared to go well this time.. I gues I was cheating by trying to boot into CWM with ROM Manager. Until I saw a post about writing, blue or green. Mine was blue, and didn't give me the option to load anything but update. So I formatted SD card with no avail. Finally pwr>down>camera did the trick. Ran script for about 10min and then came the orange writing and I was able to take it from there. However, I did not wipe. Phone is charging now, what are issues of not wiping? I will wipe if I need to, but I'm just so stocked to be a this point.

Thank you!
 
Since you just did the conversion your system is for the most part "wiped" so it should follow threw with no problems. If it doesn't then you will just have to reboot into CWM, wipe and flash again..

Just keep a mental note in the future any time you flash a ROM, wipe... Themes, addons, kernels.. No wipe unless stated.
 
So I'm new to epic rooting, but fairly experienced with evo's so I'm guessing relatively speaking the concepts are the same. Anyway, my main question is what would be the easiest (quickest) way to accomplish this on the epic. The reason i'm looking for a fairly quick way is because its not my phone (I have an EVO, its actually my sons phone), and i really don't want to have to keep the owner (my son) from his phone for to long. I see root access as a necessity for these devices because of the extremely slow update process of the manufacturers, and i'm sure that my son would really appreciate the different roms and themes that he can use after obtaining root, not to mentions Titanium Backup, and apps2sd (I'm currently a CM7 nightly addict so, i'm sure he'll follow somewhat the same route as it applies to the EPIC).

Anyway, thanks for any advice, i do really appreciate it.
 
So I'm new to epic rooting, but fairly experienced with evo's so I'm guessing relatively speaking the concepts are the same. Anyway, my main question is what would be the easiest (quickest) way to accomplish this on the epic. The reason i'm looking for a fairly quick way is because its not my phone (I have an EVO, its actually my sons phone), and i really don't want to have to keep the owner (my son) from his phone for to long. I see root access as a necessity for these devices because of the extremely slow update process of the manufacturers, and i'm sure that my son would really appreciate the different roms and themes that he can use after obtaining root, not to mentions Titanium Backup, and apps2sd (I'm currently a CM7 nightly addict so, i'm sure he'll follow somewhat the same route as it applies to the EPIC).

Anyway, thanks for any advice, i do really appreciate it.


Currently the best choice would be to get him on Froyo EB13 rooted with CWM 3.0.0.6/EXT4 filesystem. There are many ROMs to choose from. The newest official Froyo EC05 is still in the OTA process of updating and only has 2 custom ROMs to choose from.

Using the method in the link below will take his phone no matter whatever state its in to the upgrade below. I recommend choosing the option for "Stock EB13 Deodexed EXT4 + CW 3.0.0.6". From there he can run any Froyo EB13 custom ROMs and even the 2 new Froyo EC05 ROMs that are available. Its a one stop shop, rooted and CWM installed all in one flash/package.


Froyo EB13 Pre-Rooted, Deodexed, with Clockwork - RFS & EXT4
 
  • Like
Reactions: fiddy619
Thanks for this thread. I went and got "Stock EB13 Deodexed EXT4 + CW 3.0.0.6," and I did the scary conversion to EXT4.

Now To decide between Bonsai or midNIGHT for my EC05. Could someone tell me the pros and cons between the two?

Edit: I tried Bonsai, but it has my program manager widget and clock notification missing. I went back to Stock EB13 Deodexed EXT4 + CW 3.0.0.6," and I'll wait patiently for a Stock EC05 EXT4, and I don't really care if it's odexed or deodexed. I really want EXT4 for the performance gains more than anything else.
 
Last edited:
I tried all of these steps with no result...

- Only tick the Auto Reboot option in Odin.

- You could try Odin without your sdcard in the phone

- You can also try removing your battery and plugging in and run the whole procedure without your battery. This has helped on some more stubborn phones.

^^^ These options create an error message of boot.bin complete(write) operation fail

1. Disable/Turn off any and all antivirus/spyware/malware programs.

2. Use the ports off the back of the computer these are usually directly off the motherboard for best power/connection. Also if your only option is using a laptop then make sure its plugged in to provide the best power available.

3. Try a different cable if available.

4. You can pull your battery out and leave it out of the phone, then plug in via cable to your computer and boot into Download mode and run the procedure.

5. Removing the sdcard in the past has helped too...

^^ With these options i ticked only repartition. This one only sits on SET PARTION. It does not move from there. I am not using the stock crappy cable. I'm using an HTC EVO cable, same cable that flashed a Samsung Moment & Intercept

I have tried two different PC's. A laptop with Windows 7 and a desktop with Windows Vista. I have tried the both stock tar (2.1/2.2) with nothing included as well before trying this tar. The only difference with the stock tar it fails at param.lfs instead of boot.bin. Any other steps to try??
 
I tried all of these steps with no result...

- Only tick the Auto Reboot option in Odin.

- You could try Odin without your sdcard in the phone

- You can also try removing your battery and plugging in and run the whole procedure without your battery. This has helped on some more stubborn phones.

^^^ These options create an error message of boot.bin complete(write) operation fail

1. Disable/Turn off any and all antivirus/spyware/malware programs.

2. Use the ports off the back of the computer these are usually directly off the motherboard for best power/connection. Also if your only option is using a laptop then make sure its plugged in to provide the best power available.

3. Try a different cable if available.

4. You can pull your battery out and leave it out of the phone, then plug in via cable to your computer and boot into Download mode and run the procedure.

5. Removing the sdcard in the past has helped too...

^^ With these options i ticked only repartition. This one only sits on SET PARTION. It does not move from there. I am not using the stock crappy cable. I'm using an HTC EVO cable, same cable that flashed a Samsung Moment & Intercept

I have tried two different PC's. A laptop with Windows 7 and a desktop with Windows Vista. I have tried the both stock tar (2.1/2.2) with nothing included as well before trying this tar. The only difference with the stock tar it fails at param.lfs instead of boot.bin. Any other steps to try??

Umm you have about run out of options. Other than trying that stock cable (believe it or not I still use mine and it works 99% of the time). If your able to get into download mode over and over, its not anything related to your phone. Your having a setup/software issue then. Keep trying different combinations until you have success..
 
AWESOME! Unfortunately my stock cable is not recognized at all. No matter how many times i uninstall/reinstall those drivers. Either Windows Vista/7