So I'm on froyo but trying to upgrade to gingerbread CleanGB Rom. I'm already rooted and I flashed clockwork mod from Rom manager. If i try to make a backup, or flash the rom, everything fails, soemthing about not mounting in clockwork mod. What's wrong? (Not experienced with Epic 4G). How can i get the recovery working normally?
Redo the one click and make your backup from a 3 finger salute into CWM. Sounds like ROM Manager is broken for you. Update from 3 finger into CWM and then you should be able to get ROM Manager working. There are things you have to do if you are going to MTD to get ROM Manager working. But first let's get you to Gingerbread.
You need cwm5. I would Odin to stock and retry.
Sent from my OG Epic running MIUI4 ICS powered by ShadowKernel
Related
My epic wont go back into the rom, i tried to install bonsai 4.1.3 and i kept getting assert failed: "something about tmp and script files" i dont know.... and now i cant get past clockwork 3.0.0.6....all i wanted to do was flash the newest bonsai rom and now i cant the phone....what do i do?
EDIT: ok, i got it to restore to my previous bonsai build...but now i want to know how to upgrade to 4.1.3...idk what to do...
do a full wipe of everything three times. install your rom. reboot to system.
do i need to upgrade to EC05 or anything?
Rocklee99 said:
do i need to upgrade to EC05 or anything?
Click to expand...
Click to collapse
If you want. Your not using ROM manager or quickboot to get into clockwork are you? Boot into clockwork with the 3 finger method from power off. Bonsai 4.1.3 does all the wipes for you. If you are still having problems try upgrading your cwm to 3.1.0.1.
I have EC05 right now. Yesterday I flashed to ACS MIUI and it seems to work fine. Today I try to upgrade to EI22 with CWM 5.0.2.7 using modem.EC05toEI22.zip, but I get an error every time:
Updating modem to EI22...
script aborted (no error message)E:Error in /sdcard/firmware/modem.EC05toEI22.zip
(Status 7)
Installation aborted.
I tried re-downloading the file multiple times from different sources and I keep getting this error. What am I doing wrong?
Just had someone had a similiar issue with a modem.... can you odin back to stock ec05 and it completely flash everything?
It could be a hardware problem if your unable to flash back to stock ec05 and it gets stuck at modem.bin
Otherwise I'm sure someone else knows why its not flashing right... oh and have you tried flashing an alternative recovery possibly acs recovery5 its better. One more thing are you flashing from rom managers boot to recovery or your 3 finger salute?
Sent from my OG Epic
I odined back to stock EC05 then ota'd to EI22. Except now after I rooted and installed clockwork mod I can't boot into clockwork mod, I can only get into android system recovery, which I can't install a custom rom from. I have tried installing ACS CWM and the latest official CWM via odin and I still can't boot into anything but regular android system recovery using the three finger boot.
What is wrong now?
jagothejago said:
I odined back to stock EC05 then ota'd to EI22. Except now after I rooted and installed clockwork mod I can't boot into clockwork mod, I can only get into android system recovery, which I can't install a custom rom from. I have tried installing ACS CWM and the latest official CWM via odin and I still can't boot into anything but regular android system recovery using the three finger boot.
What is wrong now?
Click to expand...
Click to collapse
Samsung put a code into the kernel that reboots the original recovery mode every reboot. Download a custom kernel (which will overwrite this setting.) I recommend nebernal for this as it will work on rfs and I don't know if the others will... there is a qbking vid to properly root on ei22 if this is confusing you... Odin the cwm .tar and DON'T have auto reboot checked. After flashing cwm pull battery and reboot into recovery via the 3 finger method... now flash that kernel I told you to download and boom you now have a cwm tha sticks after reboot!!! Now you can flash whatever rom you would like... btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Samsung put a code into the kernel that reboots the original recovery mode every reboot. Download a custom kernel (which will overwrite this setting.) I recommend nebernal for this as it will work on rfs and I don't know if the others will... there is a qbking vid to properly root on ei22 if this is confusing you... Odin the cwm .tar and DON'T have auto reboot checked. After flashing cwm pull battery and reboot into recovery via the 3 finger method... now flash that kernel I told you to download and boom you now have a cwm tha sticks after reboot!!! Now you can flash whatever rom you would like... btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks! I will give it a shot tonight. Can you please explain for a noob what you meant by "btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition..." ?
jagothejago said:
Thanks! I will give it a shot tonight. Can you please explain for a noob what you meant by "btw for future reference I'm pretty sure you have to mount/system in cwm when flashing anything from the new miui and cm roms because of the new mtd partition..." ?
Click to expand...
Click to collapse
Not sure if this entirely right but with the new partition or reserved memory space the system needs to mounted in order for anything affecting or changing the system to work properly. However to do so its in mounts and storage you'd need to go to mount /system in cwm and then try flashing the ec05toei22.zip then it should work.
Sent from my OG Epic
I converted my Legendary 2.2 backup to MTD, and it's been running pretty smoothely. But today... I tried to backup my ROM from rom manager and I got an error, when it was backing up the boot img. It backs up just fine if I back it up directly from recovery, but I noticed that inside the backup folder, all the files I had to rename from ext4 extensions to yaffs2 are just image files now. Sooo, I'm a bit unsure the backup will work if I try to restore them and I'm a bit sketched to try it out.
Can anyone help me out with what's going on here?
xLoveHateLegend said:
I converted my Legendary 2.2 backup to MTD, and it's been running pretty smoothely. But today... I tried to backup my ROM from rom manager and I got an error, when it was backing up the boot img. It backs up just fine if I back it up directly from recovery, but I noticed that inside the backup folder, all the files I had to rename from ext4 extensions to yaffs2 are just image files now. Sooo, I'm a bit unsure the backup will work if I try to restore them and I'm a bit sketched to try it out.
Can anyone help me out with what's going on here?
Click to expand...
Click to collapse
Did you change ROM Manager for MTD use? There was lots of posts about this. You need to hit menu in ROM Manager, pick Manual Flash Overide, Epic-MTD and clockwork 3.x.x.x. The CWM installed when you converted to MTD is special and needs to be the only one used. Do not flash another recovery while on MTD. If you do you will have to convert again to get it.
I have not changed ROM Manager for MTD use. Someone told me to convert it, but when I click Manual Flash Override, it asks me if I'm having trouble flashing the recovery with rom manager, but whether I click ok or cancel, it doesn't really do anything. I don't see anything about MTD in rom manager.
xLoveHateLegend said:
I have not changed ROM Manager for MTD use. Someone told me to convert it, but when I click Manual Flash Override, it asks me if I'm having trouble flashing the recovery with rom manager, but whether I click ok or cancel, it doesn't really do anything. I don't see anything about MTD in rom manager.
Click to expand...
Click to collapse
You are supposed to click OK and a screen will pop right up with 3 Epic choices. Pick Epic-MTD and the clockwork 3.x.x.x then it will use the correct MTD clockwork installed. If this don't work your ROM Manager is bad. Uninstall and reinstall. If you still can't get it working you will have to not use it and 3 finger to CWM.
Sent from my SPH-D700 using XDA App
You Save my Rom Manager =)
kennyglass123 said:
You are supposed to click OK and a screen will pop right up with 3 Epic choices. Pick Epic-MTD and the clockwork 3.x.x.x then it will use the correct MTD clockwork installed. If this don't work your ROM Manager is bad. Uninstall and reinstall. If you still can't get it working you will have to not use it and 3 finger to CWM.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thank You very much Sir KennyGlass123.
I had this same dreaded error backing up the boot img when I upgrade to CM9 Beta 3 and used Rom Mananger 5.0.0.7 BackUp Rom option in app then it would reboot to CMW 5.0.2.7 and fail to do a backup.
The only way I was avoiding this error was to do a reboot to recovery in power options or do the 3 finger CMW then back Up would work ok. But I was annoyed about this error and how before in early FC09 & EL30 roms I had not experienced this.
I recently was with CleanGB 1.1.2 BML Rom but decided to go for MTD format. I flashed the CleanGB 1.1.2 MTD rom then tried out a bunch of other great epic 4g MTD roms while backing each before installing another and finally landed to CM9. After updating kernel and updating to CM9 pre4 I started to backup my CM9 b3 and found out I was herbed.
Not until I read your posts and followed your recommendations that it totally fixed this error in Rom Mananger. Now I have both ways to back up my current rom either using Rom Manager Back Up Rom option that kicks me to CMW or 3 finger salute, lol...
XDA is the gift that keeps on giving...
Thank You for xmas everyday with new roms and themes and great info.
Lanboy =)
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Most don't recommend Rom manager, I would just stick with Rogue.. I had no problems with it..
Bobby O'S Epic Touch....
indigo0086 said:
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Click to expand...
Click to collapse
Get rid of ROM manager it doesn't flash recovery right on this phone..and koush doesn't care to fix it...don't ever use the touch one either... Get a kernel with cwm in it at use mobile Odin to install....if using a GB ROM use the el26 if using a ics ROM don't use any recovery unless u hate your phone and want to brick it
Sent from my SPH-D710 using Tapatalk 2 Beta-5
indigo0086 said:
I installed the goodness as my first rom and following the guides it installed a modified CWM 5, the rogue version. I used Rom manager and installed the standard. WHen I reboot into recovery from the rom or using the pwr+up it boots into rogue, but when I reboot into recovery from rom manager it reboots into the standard cwm. I want to only use standard cwm, How do I get rid of and install it so when I boot into recovery manually it's the regular cwm.
Click to expand...
Click to collapse
Just stick with Rogue's. ROM Manager has been the source of a TON if bricks lately (mostly to do with CWM Touch). If you absolutely can't use Rogue you can use the stock CWM from EL26.
http://db.tt/rBZNsGaj
But really I'd stick with Rogue...
And ROM manager doesn't actually install recovery on the phone. When you flash a recovery in it it creates a temporary recovery for you to boot into. But ya, don't even bother messing with ROM manager for all the reasons everyone else has stated.
Epix4G said:
Get rid of ROM manager it doesn't flash recovery right on this phone..and koush doesn't care to fix it...don't ever use the touch one either... Get a kernel with cwm in it at use mobile Odin to install....if using a GB ROM use the el26 if using a ics ROM don't use any recovery unless u hate your phone and want to brick it
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I totally agree here with the ROM Manager danger... When I had trouble in the past on a GB ROM, Koush didn't respond to any of my help requests.
I haven't had any issues lately, but in all fairness I do like the fact that ROM Manager will automatically reboot the phone into recovery, create a backup, and then boot back into Android. Also, I can delete or rename existing backups from right within Android with RM. I have restored the backed-up images with no issues too...
I've been on ICS since Calk's 1.0 FC06 ROM, and I have been fortunate enough to know to stay away from the touch recovery
You can delete or rename backups in android from any file manager app, most custom roms have the reboot mod to get to recovery and its a few clicks to backup and reboot to phone from recovery Rom Manager doesn't do anything special you can't do with your fingers and your trusting an app to do something for you instead of doing it yourself and making sure its done right
Sent from my SPH-D710 using xda premium
thanks for the feedback, I won't bother with rommanager anymore than lol. Also Can I use Rogue to flash Cyanogenmod and other roms, Some people are saying to use certain clockworkmod versions and saying rogue has caused bricks.
So I took the dive on donate version of ROM Manager, but I can't do anything with it because it doesn't recognize that I've already got CWM 5.0.2.7 installed. I don't want to use it to push another phone's 5.0.2.7 CWM image, right? Trying to go from Osimood to Inc3ption ROM, really want to do a good solid ROM backup before going through all that pain...
Thanks in advance
L4T
>_> ROM Manager isn't compatible with our phones iirc. It's not even compatible with Cappy Gingerbread update..
just use the back up in CWM... hasnt failed me yet and have been doin it just testing everything out