Develop Bugs

[Q] ext4 uninstall?

So I've never been able to get an official response so I figured id just post it...
What are the methods to get back to rfs/original cwm if I want to? For both methods? By this I mean:
1. The cwm 2.x.x.2 -- the only thing I heard was that if I get myself into the original cwm (I think 3 finger salute gets you there by default), I can flash any ROM (say, the di18 rom and modem) and it'll automatically reformat to rfs. Is this true? And does it get rid of the other cwm?
2. The cwm 3.x.x.x -- seeing as how this seems like the easiest way to get ext4, I would definitely want to use this method. But what I'm getting is this cwm only does ext4..so aside from odin'ing myself back to stock or whatever, how would I go back to old cwm/rfs?
My point here is that I would love to avoid having to use odin for anything (except getting to dk28 of course). My laptop usbs are sketchy sometimes.
Please please please some clarification. And don't tell me to read posts or don't do it if I'm scared or anything like that...if you can't answer my question then don't reply. I've followed dameon from the beginning of this and it still isn't clear.
Sent from my baked and emotionless SPH-D700

Currently, the only way to go back to RFS is with Odin. Clockwork 3 should support various file systems, but I don't know if anyone has a utility to reformat a partition into RFS. I haven't seen one, but that doesn't mean much. If there is one, then it would be possible. If not, then we're stuck with odin.

DiGi760 said:
Currently, the only way to go back to RFS is with Odin. Clockwork 3 should support various file systems, but I don't know if anyone has a utility to reformat a partition into RFS. I haven't seen one, but that doesn't mean much. If there is one, then it would be possible. If not, then we're stuck with odin.
Click to expand...
Click to collapse
Ok. So say I want to odin back to "stock" dk28. Does this also erase any modified cwms? (Tho I have a feeling it gets rid of any cwm redirector and goes back to stock recovery) I'm sorry if that's a dumb question.
Sent from my baked and emotionless SPH-D700

remember to run a BACKUP with CM and Titanium before you convert and/or revert to any file system. best practices...

squshy 7 said:
Ok. So say I want to odin back to "stock" dk28. Does this also erase any modified cwms? (Tho I have a feeling it gets rid of any cwm redirector and goes back to stock recovery) I'm sorry if that's a dumb question.
Sent from my baked and emotionless SPH-D700
Click to expand...
Click to collapse
If you odin back to stock DK28, you will lose Clockwork Recovery. Unless you use a tar file that has Clockwork baked in.

[Q] Need help with CWM Recovery and other issues!

Hello All,
I have been working with my friends EPIG 4g phone for a while now. The first thing I did was use "superoneclick 1.7" to root his phone. Then he got interested in trying different roms+kernels, so he came to me for more help. Almost all the custom roms I was researching are EC05 based roms, so I looked further into it. For reasons unknown, he is still on DI18 Eclair (must not have got the OTA). I dug on forums and found the zip file that would allow him to jump from DI18 to EC05 (froyo), but I need a custom recovery to install the zip. No matter what I try, I cannot get the phone to boot into CWM recovery. (Tried both from rom manager, and using camera button+vol. down+power combination) I have tried just about everything that I can think of, to no avail.
I have also tried:
Unroot & Re-root using process found here:
http://forum.xda-developers.com/showthread.php?t=770388
Wiping all data via factory reset (really wish I wouldn't have, waste of a try)
Tried using methods found here:
http://forum.androidcentral.com/epic-4g-rooting-roms-hacks/34603-clockworkmod-recovery-rom-manager-guide.html
When trying to do anything in the stock recovery, I always get the:
e:signature verification failed errors.
Please bombard me with any and all ideas you guys have. I am currently about to try to manually install the CWM recovery by placing the update.zip file on the SD root directory. IF I can get that part done, I'm confident I will be able to get everything going. Another option I have read from other people's threads that I have not yet used is the Odin revert to stock and then flash some special .tar files. I took a look at Odin and don't remember seeing options for "stock" or anything, so if anyone can point me to a good Odin walk-through, that would be awesome.
PS: Ask me if I have failed to clarify on any aspects of the problem. Forgive me for not including more info on the problem, Ive been through like 8 hours of random stuff while trying to fix this, so Ive seen too much to remember everything I've seen.
Thanks in advance!
-Clarity

Too many words
I kinda fell a sleep in the middle so yeah
If you want to return too stock use odin
If you want to go to froyo from eclair use odin
If you want cw use I've of the one click rooters
Going to cw is just pressing every button that is not on the keyboard
(power + volume up + volume down + camera)
Sent from my SPH-D700 using XDA Premium App

Stock recovery will get you nowhere on this phone, and with all you have tried so far, I believe Odin is the best course of action. Here is a link to the Odin package-
http://www.mediafire.com/file/fn9s5cqkkwyu68d/Odin3+v1.61andepic.pit.zip
Unzip it to a folder on your desktop.
The necessary drivers and instructions for using it are here in the wiki
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700#Odin_Stock_Flashing
Follow the instructions carefully and be sure the drivers are installed before starting. Obviously, wherever it mentions the DI18 tar, you will use the current one in it's place. You can use this one, it's pre-rooted and de-odexed.-
http://forum.xda-developers.com/showthread.php?t=1021305
That tar file is still RFS file system so you will need to install CWM 3.0.0.6 and boot into it with the 3 finger solute so it can convert the file system to ext4. Package and instructions here-
http://forum.xda-developers.com/showthread.php?t=897612
If you made it this far you should be able to install one of the current ROMs you've been shopping for.

Thanks for the responses guys, I will try that out when I get a chance. Might be a while though because I don't see my friend that often.

So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Basically, I would like to know what I am doing wrong here. Is the CWM included from that .tar file compatible & ready to flash any custom ROM that I want? Or do I need to use that CWM 3.0.0.6+root that Mattalica suggested? The EC05 was prerooted, so I'm wondering what happens if I use the 3.0.0.6 exploit on top of this root... Let me know guys.

onlyclarity said:
So I was able to use Odin and successfully flash the EC05 .tar. However, I was unable to flash the Syndicate Frozen ROM that my friend wanted. It seems to fail on the flashing kernel step, some blue text that is large and out of place shows up for a second, and it goes back into the recovery menu. When I try to reboot the phone, it is clear that it did not work (assuming the kernel install is failing). I am going to Re-flash the EC05 for now, but do you guys have any recommendations for ROM+Kernel combinations good for battery/performance? Link me up if you know of any good combo's, but I've researched it a bit myself as well.
Click to expand...
Click to collapse
What happend when you rebooted that indicated it was not successful? If you had strange vibrations and a bootloop, that is common when trying to flash these new generation ROMs like ACS and Bonsai. A simple reflash usually fixes it.
Sent from my SPH-D700 using Tapatalk

The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.

onlyclarity said:
The Syndicate one failed as the kernel step was happening, resulting in a complete ROM failure (syndicate frozen tries to install their kernel midway thru the ROM flash). I tried it more than once, with no success. It just kept failing at kernel and only letting me into the CWM recovery (probably had already erased the base ROM?)
I was able to flash Baked Snack 1.6 without trouble and he is going to try that out for now. Interestingly enough, I did try to flash the baked snack "step 2" kernel, which is supposed to be a bit better on the battery life, and guess what happened mid install: the same weird black screen with huge blue text that goes off the screen (I think it says it fails, not sure though).
Here's the kicker on that, the "about phone" section does say that the base-band is something like "baked snack 1.6 step 2", which is odd, but the kernel version section seems to boast the same kernel version number that it had before. This leads me to think that it may have worked, but again, I cannot be 100% sure. If you have any more comments/suggestions, feel free to keep posting. Thanks again for all your help with the Odin TAR stuff, I really didn't feel confident until you confirmed the method.
Click to expand...
Click to collapse
BakedSnack 1.6 is a RFS ROM and is DI18 based. If you installed CWM 3.0.0.6, it would have converted your filesystem to EXT4. BakedSnack 1.6 does not have kernel support for EXT4. However if you installed an older version of CWM it would explain how ACS failed to install and how BackedSnack 1.6 was able to install and boot.

Question re Clockword Mod Update for Samsung Epic

I tried to post this on the actual thread about this Update, but I was not allowed because I had not posted 10 times previously.
Anyway, I am new to rooting Android phones….new to android phones for that matter. I have had the Samsung Epic 4G for about a month. I have been looking into rooting the phone, finally decided to go for it. I downloaded the filre for Clockwork Mod version 3.0.0.5/6 - UPDATED FOR EB13 from this site. After doing one run of that bat file and getting stuck on the startup screen, I realized I needed to find a compatible ROM and Kernel and install them before rebooting.
I reset the phone to default settings, using the info on http://forum.xda-developers.com/showthread.php?t=909384 and then I used the kernel
from the original update thread, Default Stock Dual FS kernel For EB13, and the Bonzai ROM from their website. This time, the install worked properly, and when my phone rebooted, the firmware is listed as Bonsai/Kernel_v4.01. So I wanted to backup and uninstall some Samsung Bloatware from the phone,and as I understand it, the Titanium Backup is the best way to do it. Well, I installed it, and it has consistently said the program could not acquire root status. I clicked on the “problems” icon, got busybox and upgraded superuse, and that did not effect anything. I even reflashed the Bonzai Rom, but the end result is the same, I am still getting that same message. Since I have replaced my Rom and have installed Superuser, I have to assume I have rooted the phone, so what could be the problem here? The app SetCPU also says I do not have Root Access. So I am not sure what to do at this point.

Sounds like a failed root:
Root again with the oneclick 3.0.0.6, power off, 3 finger boot and ext4 will be put on automatically. After ext4 installs install bonsai before rebooting.
Sent from Bonsai 7.0.3

Is there a difference between onclick 3.0.0.6 and the one in the thread http://forum.xda-developers.com/showthread.php?t=897612,which is labelled 3.0.0.5/6? Because, if not, that is pretty much what I have done already.

Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. Http://www.bonsaigeeks.com
Sent from Bonsai 7.0.3

Top Nurse said:
Same one.
I would odin to eb13, odin ec05 modem, root, boot to recovery and allow ext4, flash bonsai 4.0.1. Can't remember if 4.0.1 adds ec05 modem during flash, but if it does you can skip the ec05 odin (sorrry, but my mind has been on 4.1.0 for the last week).
The odin process will get rid of the kernel you currently have. Flashing the rom doesn't do anything to the kernel. The odin process will give you a nice clean slate to workv with. If your phone wants to do an ec05 OTA update during this process please tell it later and don't do it.
Suggest you peruse the Bonsai Forum as you will find a lot of treats that will be able to help you. www.bonsaigeek.com
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse

This exact thing happened to me after trying everything from the EC05 OTA. Just run the bat file again on the phone...nothing else and it will work fine.

[Q] Still on Froyo EC05. How should I move to GB?

I'm planning a major upgrade of my phone later this month and want to have as much information spelled out in advance as possible.
I think I will first upgrade my CWM to 5. Am I correct in understanding that CWM5 is out of beta and stable? I vaguely remember reading that its keys do not work perfectly with Froyo kernels, so I haven't moved until I do everything at once.
I'm leaning toward SleeperROM. It seems updated often and actively. On the other hand, reports that there may be wifi issues give me pause.
Whatever Rom I go to, I'll go back to RFS, because while I'm on Ext4 now, avoiding force closes is more important to me than operating speed.
My question is: Can I upgrade entirely with CWM, or will I need Odin? Has a way been developed yet to get my modem to EI22 that does not need Odin, or is it still recommended that I first Odin to a full stock EI22 Gingerbread, re-root and install CWM and my new rom from there?
If you had to do the upgrade process now, what steps would you take?

There is no modem.bin for the EI22 modem so no Odin. You have to flash the modem delta from CWM with EC05 modem on your phone. Then just flash a GB ROM and enjoy. Backup with nandroid and Titanium Backup. Not all data is compatible so some things may have to be set up again. I had to redo my email accounts in stock email client.
Sent from my SPH-D700 using XDA App

Now I'm not NEARLY as experienced as Kenny, but what I did seemed to have worked out alright. I didn't use Odin (have a Mac) and used CWM (purple at the time) for it all.
I came from Froyo and did a CWM update to GB. That put me on EI22 with EC05 modem.
Updated to CWM 5. I did this as I was researching and getting ready to goto a custom ROM.
I then CWM'd to Legendary ROM (so choose your ROM here, I guess).
Then through a lot of trial and error with all the different modems, used the CWM flash able ECO5 to EI22 modem updater. This put me on Legendary Rom with EI22 modem. EI22 actually works fantastically for me.
I haven't had any problems since (minus bugs and whatnots from the Samurai Kernel and Legendary updates).
It sounds like you are pretty savvy. I don't think you will have any problems getting what you need done without Odin.

garyf said:
I'm planning a major upgrade of my phone later this month and want to have as much information spelled out in advance as possible.
I think I will first upgrade my CWM to 5. Am I correct in understanding that CWM5 is out of beta and stable? I vaguely remember reading that its keys do not work perfectly with Froyo kernels, so I haven't moved until I do everything at once.
I'm leaning toward SleeperROM. It seems updated often and actively. On the other hand, reports that there may be wifi issues give me pause.
Whatever Rom I go to, I'll go back to RFS, because while I'm on Ext4 now, avoiding force closes is more important to me than operating speed.
My question is: Can I upgrade entirely with CWM, or will I need Odin? Has a way been developed yet to get my modem to EI22 that does not need Odin, or is it still recommended that I first Odin to a full stock EI22 Gingerbread, re-root and install CWM and my new rom from there?
If you had to do the upgrade process now, what steps would you take?
Click to expand...
Click to collapse
Check out QBKings How to video to Install EI22 Modem.. Then search his videos of numerous custom Roms for the one you like..
http://www.youtube.com/watch?v=qnk6lfBh5rI

It's also all personal preference. I Odined back to dg27 and got the ota package, Odined ACS Recovery, then flashed nubernel and then stock deodex EI22. Took an hour or so to reinstall apps and restore what data I wanted to keep. I like a super clean install, if it even matters much.

how come roms dont like me?

i got a new epic from assurion so it had nothing on it so i odined el30 flashed su odined acclaim and that was it then i put A rom on top of it ( the peoples rom ) and as usual it lags and doesn't open up things for up to a minute . i have always had problems with roms. what can i be doing wrong? are these the correct steps? are they incompatibility issues? or is el30 not stable yet. any help woiuld be appreciated. i really like using your masterpieces but i seem to have issues wit all of them, so clearly its me. thanks

If you don't like aosp but want stock rooted, Odin el30 ( victory pit in pit section, el30 .tar in PDA section, only have auto reboot checked), then OTA to fc09 then Odin cwm 5.x ( pit in pit section, cwm .tar in PDA section, leave everything unchecked), pull battery when Odin finishes, boot cwm, flash su.zip, boot fc09, use es file explorer(free in play store) launch es, navigate to settings> check use root explorer, grant su, check mount /system, delete /system/etc/ recovery-install.sh (or something like that to disable the script from reinstalling the stock recovery.) , Odin cwm again and your good.
Edit: or an easier way would be to Odin cwm once and flash this lol http://forum.xda-developers.com/showthread.php?p=24419155
Sent from my cm_tenderloin using Tapatalk 2 Beta-5

Also download Spare Parts and set Window and Transition Animations to FAST. You would be surprised at the difference that makes. You will lose CRT off but with that speed, who cares...LOL.

ok this was a bit much for me. i dont need stock rom i dont care about anything. i just thought i had to odin to start fresh . all id like is whatever it takes to get peoples rom (for instance) to work on my phone. btw, i can not even get the screen to turn back on now without pulling the battery. i can follow the directions but i was hoping for something alittle more simple. if thats not possible i will try to figure out those directions

Unfortunately Samsung's Gingerbread update killed the one click root option so Odin is needed to at least put on a custom recovery and then install a prerooted ROM.
Sent from my SPH-D700 using xda premium

ok i apologize i was half alseep when i read the first reply, so i opted for the second option and odined \cwm-5.0.2.7-epic4g.tar.md5
i also have a cwm 3.1.0.1
should i have used that? i usually do the acclaim in odin but i just odined the cwm but when i went into recovery of course the deoxed fc09 didnt work because it wasnt rooted but the su.zip doesn't show up on my sd card in recovery. it always does when i odin acclaim. what am i doing wrong?

When you odin cwm 5, uncheck reboot. Odin will complete but your phone will still have the triangle showing. Disconnect the cable, pop battery out and in, 3 finger salute into cwm5 and flash The People's Rom. That will put you on MTD. Then if you don't like that you can flash the deodexed FC09 from there.
Sent from my PantechP4100 using xda premium

Listen, I think most of the devs in this community work really hard to put out some great ROMS. The insight they have given me is much appreciated. But now that I've said that, here is my answer to your original question.
I have yet to use a ROM that is as reliable as stock ROMs. If you read the threads about each ROM you will see lots of comments like:
"Wow, this ROM is awesome. It's absolutely perfect.....also, sometimes my speaker doesn't work, and the system panel FCs all the time, but THIS ROM is PERFECT! Thanks".
See my point? People get religiously attached to their favorite ROMs and easily ignore the problems to avoid admitting that they aren't using the hot sh*t.
I've tried lots of ROMs, but I always end up going back to a lightly modified stock ROM because for me reliability is the number one item with me. I have yet to find one dev's ROM that doesn't have a fatal flaw, IMHO.

gorelow said:
ok i apologize i was half alseep when i read the first reply, so i opted for the second option and odined \cwm-5.0.2.7-epic4g.tar.md5
i also have a cwm 3.1.0.1
should i have used that? i usually do the acclaim in odin but i just odined the cwm but when i went into recovery of course the deoxed fc09 didnt work because it wasnt rooted but the su.zip doesn't show up on my sd card in recovery. it always does when i odin acclaim. what am i doing wrong?
Click to expand...
Click to collapse
this might help some ...look below