Develop Bugs

[Q] Need help updating please

Hello, I've been using this website til this past december and I love it but stopped messing around with my phone because of graduate school. So the last thing I did was just update to stock dk28 modem without rooting it. Now I'm trying to catch up and need help to refresh lol.
Anyways, so yeah i'm on 2.2 (not rooted) currently and trying to update to the new syndicate rom. As the installation instruction says, I need to use odin to install the TAR and PIT and I know that is after rooting my epic. So is the rooting method the same as it was for 2.1?
Last question for now to get started, I really dont understand this part of the installation instructions in their thread properly "Then, use the CWM 3.0.0.6 One Click to install Clockwork and convert to EXT4.", so if anyone can please help me I will be more than grateful. to break down the questions, how do I install that new clockwork after updating to EB13? and how do I convert to EXT4? what is EXT4?
Sorry for all the questions andn using such a long thread just for help. Thanks.

y2bangali said:
Hello, I've been using this website til this past december and I love it but stopped messing around with my phone because of graduate school. So the last thing I did was just update to stock dk28 modem without rooting it. Now I'm trying to catch up and need help to refresh lol.
Anyways, so yeah i'm on 2.2 (not rooted) currently and trying to update to the new syndicate rom. As the installation instruction says, I need to use odin to install the TAR and PIT and I know that is after rooting my epic. So is the rooting method the same as it was for 2.1?
Last question for now to get started, I really dont understand this part of the installation instructions in their thread properly "Then, use the CWM 3.0.0.6 One Click to install Clockwork and convert to EXT4.", so if anyone can please help me I will be more than grateful. to break down the questions, how do I install that new clockwork after updating to EB13? and how do I convert to EXT4? what is EXT4?
Sorry for all the questions andn using such a long thread just for help. Thanks.
Click to expand...
Click to collapse
1) odin to full eb13
2) run the cwm3.0.0.6 one click
3) reboot into recovery using 3 finger monkey grip. It well auto convert to ext4
4) flash the rom. (wipe data, cache, dalvik 3xs)
5) boot the phone (start up animation may look word)
6) boot into recovery again
7) flash the rom again (wipe data, cache 3xs)
8) your good to go
Sent from my SPH-D700 using Tapatalk

CWM One Click is a multi-purpose package. It: a) roots your phone, b) installs a flashing/backup/recovery package and c) converts your filesystem to ext4.
Do a search on how to install CWM. It's a matter of hooking your phone to a PC in USB debugging mode and then running a "run.bat" script. Now your phone is rooted and reboots, but you won't notice much different at that point (other than the Superuser App). If all you want is root, you're done.
If you want to flash a ROM then you boot into the recovery software (using the 3-finger technique).
This is where the gotchas start: The first time you do this, your file system will be automatically converted to a new filesystem: ext4 (it takes about 5 to 10 minutes). At this point, you need to be prepared: once it's converted to ext4, make sure you have an ext4-compatible ROM on your SD card that you can flash right then and there. At that point, I don't know if you can even reboot back into your stock ROM (I've always flashed a new ROM immediately, so I don't know).
Learn about the backup and restore mechanism in CWM, it's your friend.

abonet said:
At that point, I don't know if you can even reboot back into your stock ROM (I've always flashed a new ROM immediately, so I don't know).
Click to expand...
Click to collapse
You can run on stock eb13 with ext4 but you must flash at the minimum a ext4 compatible kernel.
Sent from my ACS frozen Epic

THANKS ALOT for all the help guys.. even in it is a multipurpose package, i do have to root first before i can use odin correct?

y2bangali said:
THANKS ALOT for all the help guys.. even in it is a multipurpose package, i do have to root first before i can use odin correct?
Click to expand...
Click to collapse
No
Sent from my SPH-D700 using Tapatalk

[Q] Ways of flashing custom rom. How to install cyanongenMod.

I'm using a GSM HTC Desire I bought a year ago. Its currently running froyo 2.2. I've used unrevoked to root my phone and did the s-off produce using alpharev a while ago. I'm now trying to flash a custom rom onto it. I read through a couple of tutorials and found out 2 ways to do it. One is to install ROM manager but I have to do a "flash ClockworkMod Recovery" in the software which I don't know if I should do. Another is to download the custom rom and install it through recovery mode by holding on power and volume down.... Is there a difference?
Also reading CyanongenMod installation procedures "3. Update your radio! New radio from HTC 2.2+ roms is required (Desire Radio Thread)." came up and I don't if I need to do this.
Thanks in advance.

macmac2008 said:
I'm using a GSM HTC Desire I bought a year ago. Its currently running froyo 2.2. I've used unrevoked to root my phone and did the s-off produce using alpharev a while ago. I'm now trying to flash a custom rom onto it. I read through a couple of tutorials and found out 2 ways to do it. One is to install ROM manager but I have to do a "flash ClockworkMod Recovery" in the software which I don't know if I should do. Another is to download the custom rom and install it through recovery mode by holding on power and volume down.... Is there a difference?
Also reading CyanongenMod installation procedures "3. Update your radio! New radio from HTC 2.2+ roms is required (Desire Radio Thread)." came up and I don't if I need to do this.
Thanks in advance.
Click to expand...
Click to collapse
Personally IMO i would never use ROM manager. I would upgrade your recovery to '4EXT recovery touch' first, search the forum for the guide, its simple enough.
You should also partition your memory card so it has an EXT partition on it. I would recommend using Gparted to partition the sd.
IMO i would leave the radio update for now.
Search for a suitable ROM to flash, download it, put it on your SD card, go into recovery and flash.
There are loads of guides in the forum just look and follow step by step, if you do everything completely to the guides you will not have a problem.

25092992 said:
Personally IMO i would never use ROM manager. I would upgrade your recovery to '4EXT recovery touch' first, search the forum for the guide, its simple enough.
You should also partition your memory card so it has an EXT partition on it. I would recommend using Gparted to partition the sd.
IMO i would leave the radio update for now.
Search for a suitable ROM to flash, download it, put it on your SD card, go into recovery and flash.
There are loads of guides in the forum just look and follow step by step, if you do everything completely to the guides you will not have a problem.
Click to expand...
Click to collapse
Why would he need to waste his time, effort and sd-space by partitioning for a ROM that does not natively support a2sd

bortak said:
Why would he need to waste his time, effort and sd-space by partitioning for a ROM that does not natively support a2sd
Click to expand...
Click to collapse
He's prolly gonna need it eventually when he decides to try one of those unstable roms out there.
via xda app

stankyou said:
eventually
Click to expand...
Click to collapse
Eventually. OP only wanted CM for now

Hi! The easiest way to install a new ROM it's by ROM manager. You can use the recovery mode also, but it's more complicated.
You can flash your recovery whitout any problem.
ALWAYS remember to make a nandroid backup before installing a ROM in case anything goes wrong.
You should also wipe data, cache and dalvik.
After installing a new ROM, use ROM managers or recovery to make à sd-ext partitions (more space for apps)

gab_hamelin said:
Hi! The easiest way to install a new ROM it's by ROM manager. You can use the recovery mode also, but it's more complicated
Click to expand...
Click to collapse
Take your advice and go somewhere else. ROM Manager both sucks and blows and just causes problems. The only "good" use it does have is the ability to download ROM's straight to your phone. Otherwise steer clear.
gab_hamelin said:
You can flash your recovery whitout any problem.
Click to expand...
Click to collapse
In most cases
gab_hamelin said:
ALWAYS remember to make a nandroid backup before installing a ROM in case anything goes wrong.
You should also wipe data, cache and dalvik.
Click to expand...
Click to collapse
Should do a full wipe, including boot, system etc.
gab_hamelin said:
After installing a new ROM, use ROM managers or recovery to make à sd-ext partitions (more space for apps)
Click to expand...
Click to collapse
Do not use ROM manager to make backups. Can just cause problems as already stated. Don't be lazy and do it yourself via recovery, now with 4EXT touch it's easier and simpler than ever.

Yes. Go and flash manually. Rom manager is just a middle man that screws up the process. Dont ever use it at least for Desire coz it really doesnt play well with it. Even after you successfully flashed cyanogenmod.
via xda app

Use this fine guide?
I used this very fine guide when I wanted to go further than HTC would let me. http://forum.xda-developers.com/showthread.php?t=1016084
And it is maintained on XDA, which is nice.

[SOLVED] Looking to update from CM7.2 to an ICS ROM

Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
___________________
SOLVED AFTER A STEP BY STEP INSTALLATION WITH KB!! MANY THANKS
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
Ive always been running CM roms since I got the phone nearly two years ago, but recently have been reading too many good things about ICS roms. My phone has been laggy as of late, and honestly after nearly 2 years, I wanna see and try something new. I've been reading some stuff about updating 4EXT or something like that. Can someone link me or explain in great details how i do this? What is it? And if I do that, will i still be able to run my old CM rom if i decide the ICS roms arent for me? I dont want to be unable to roll back.
Whats the best ICS roms out there right now?
Many thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
Depends on your definition of best, personally I like EliteMod ICS (in my signature) but you may want to try out Andromadus Mimicry 1.3.0, it's pretty nice out of the box and has a graphical installer (aroma).
Just be aware that due to the fact that the Desire-Z/G2 does not have an official ICS release, that some things such as hardware drivers have their limits.
1) Camera drivers are not fully available, so the camera won't function as well as it would have on a GB rom.
2) No Wireless-N, also due to drivers, but Wifi-B/G are available.
and a number of other smaller issues which are mentioned varying on the roms, but the two above are the most common complaints, something to keep in mind before you start updating the thread about lack of it.
4EXT Recovery is just another recovery, like ClockworkMod is another recovery.
I personally prefer 4EXT Touch Recovery ( http://www.4ext.net/ has the app to install it ), but both ClockworkMod (what you may have now) and 4EXT can create backups, and restore your backups to the phone (just make sure you do a factory-reset/wipe cache, when you're flashing a brand new rom on, and when you wish to restore a backup.)

So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
So i can flash ics roms with clock work mod and not use 4ext?
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
You can, they're both recoveries and will both apply a rom zip. I just find 4EXT to have quite a bit more features that pertain to ICS (i.e.: the ability to convert some of your partitions from the older ext3 filesystem to the ext4 filesystem which is better, but not all roms support it, most ICS roms do though), as well as the ability to do tar-based backups (compresses, smaller backup size), and the paid version of the app lets you configure a number of settings in 4EXT (much like the paid version of Rom Manager).
Just don't flash roms via the app, always do that from the actual recovery, or you risk causing problems.
Generally speaking: Reboot into recovery (you can do this from the power menu in CM7.2)
1) Perform a backup of your currently installed Rom to the SD card
2) (toggle USB storage and copy over the rom zip if you haven't already done so)
3) Perform a Factory Reset/Wipe and wipe cache
4) Goto Apply zip from SD Card and select the new ROM
5) Flash any additional zips you want on top, google apps, wifi calling, etc (note the thread for any specifics, for example Mimicry doesn't come with Google Apps so need to flash the ICS google apps if you want them, where as EliteMod includes a custom set of google apps already)
6) reboot and enjoy.
If you decide you don't like it, just repeat the above steps, just do a restore at #4 and reboot.
Both of the ones I mentioned (mimicry, elitemod) by no means require a swap partition or sd-ext partition, but you can partition the card via either clockworkmod or 4EXT, just skip the sd-ext2 option (since elitemod doesn't support a secondary one [and not much point either). And don't set a sd-ext size less than 1.5GB (no sense in making it smaller than your /data partition).
For both though, skipping an SD swap is advised, I only have SD swap on mine cuz no other rom I know of supports dataswap and I'd rather have my SD Card partitioned already to test out other roms than to re-do the SD Card each time (since you gota make sure to back up the content of the SD Card to the PC). 4EXT though will let you repartition the SD card without erasing the FAT32 partition, where as clockworkmod will always wipe the whole card before repartitioning (it's just easier to partition from scratch though).

Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
Yeah the whole partition and swapping was the confusing part. But good to hear I don't have to do any of that. I did see the gapps zip included in the mimicry thread, but where can I find a wifi calling apk to install? Also +1 thanks to u for the detailed reply! Thanks!
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
In Mimicry the Aroma installer will actually let you pick that option during the graphical install. It's one of those roms that presents you with a nice installation menu after you select the zip to be applied. Just bear in mind though you need the 26.13.04.19 radio in order to use the T-Mobile Wifi calling app (and course be on T-Mobile). EDIT If you're one of those people who end up getting no WIFI at all after flashing the Wifi calling app from the aroma installer and have the 26.13.04.19 radio, in the first post of the mimicry thread there's a mention of a Wifi-Fix app you can install that might be able to fix that.
For EliteMod ICS, you would apply it by downloading the zip in my signature (for the wifi calling) and flashing that after flashing the rom. But again, needs the 26.13.04.19 radio, as the app won't work with an old radio (26.03.*)
The thread on applying the radio is also linked from my signature , if you're on a T-Mobile G2, you can just grab the first 26.13.04.19 zip file, rename it PC10IMG.zip just like the instructions say there, put it on the SD Card, reboot into the boot loader and apply the radio. Also if you're planning on flashing either mimicry or Elitemod immediately after flashing the new radio, both roms already Clean your EFS partition for you when you install them in recovery, so you don't have to run the EFS wipe zip (something you normally need to flash in recovery after changing a radio).

KB suggested EliteMOD to me a few days ago,...... Gota say it is running vnice at the moment, highly recommend it. w/ SD EXT, no swap.

I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?

mapheG2 said:
I downloaded the zip file from the Andromadus thread, and proceeded to flash the ROM. It says the flash was successful, however upon rebooting, I would see the HTC screen but it would never make it to the boot animation. I would just get a black screen. I tried flashing through ClockWorldMod v5. I cleared all data and caches, and then flashed the ROM.. still not working?
Click to expand...
Click to collapse
What's the exact details of your phone, i.e.: hboot information and radio version.

I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?

mapheG2 said:
I flashed the radio from your signature. Hboot information: 0.82.0000
blkjack said I needed to do a superwipe. If that is the case, how would I perform one?
Click to expand...
Click to collapse
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.

kbeezie said:
hboot in my signature is a 0.84.2000 which is a desire-z engineering hboot.
0.82.000 would be an S-ON hboot which you wouldn't be able to change much at all. (which would be odd if you managed to get the 26.13.04.19 radio flashed, while S-On since it wouldn't normally allow you to).
May want to reboot into the boot loader mode and verify all your hboot information.
Click to expand...
Click to collapse
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?

mapheG2 said:
I flashed a radio in the past. And it clearly says I have S-OFF on the top. I had the (26.03.02.26) radio before. And it did successfully flash the radio linked from your signature. HBoot says 0.82.0000. Where to go now?
EDIT: I found this link (http://forum.xda-developers.com/showthread.php?t=1044992) but dunno if this is outdated or not. If not, which of the three files do I want?
Click to expand...
Click to collapse
I think, the -=SuperWipeG2+=-.zip should be the right one, but as I'm not sure, I did a quick Google search for you and found this:
EdKeys said:
I recently flashed the new 4EXT Mod of ClockworkMod Recovery. The 4EXT Recovery is based off of Koush's CWM Recovery but offers additional power options, one of which is the ability to show the file system format your partitions are formatted in. To my surprise my system was formatted in the Ext 4 format and my data and cache partitions were formatted in Ext 3. The new 4EXT Recovery offers the option to convert the format without deleting any of the data. Your ROM will stay intact after the conversion. I selected that option and changed my data and cache partitions to ext 4 to match my system, rebooted, and notice quite an improvement in speed and smoothness in my current CM7 Nightly. After looking into it further I found out that the SuperwipeG2 that many of us have been flashing is formatting our partitions in the Ext 3 format. The reason only my system was formatted in ext 4 is because I used ClockworkMod Recovery the last time I did a full wipe to first flash the Superwipe, and then I immediately formatted system again with ClockworkMod Recovery. If you've used SuperwipeG2 to do a wipe, more than likely your system, data, and cache partitions are now Ext 3. You might want to check with your ROM developer to see if your ROM will run on the Ext 4 format. If its a CM7 based ROM, it will.
You can find more information about the Ext 4 format here.
Tsubus has since modified SuperwipeG2 so that it now formats the partitions into ext 4 when you flash it. I've used it and it also includes the EFS wipe. You can find it here. As I said, if there is no reason to wipe right now the new 4EXT Recovery can convert your partitions if you choose if they are in currently Ext 3. At the very least you can see what format they're currently in with 4EXT. I highly recommend it. You can always flash back to CWM Recovery if and when you choose. The partitions will remain Ext 4 once you choose to convert.
UPDATE: Several users have reported that checking partition information with Terminal Emulator is not reliable.
Click to expand...
Click to collapse
This one should definitely be the right one.
Besides that, the problem might also be a bad download, as your symptom fits a known issue in blk_jack's thread:
blk_jack said:
...
Q) After flashing I'm stuck at the HTC logo screen!
A) This is likely the result of a bad download. Check your downloaded md5sum hash against the one listed next to the download link above.​...
Click to expand...
Click to collapse

I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.

mapheG2 said:
I thought it was a bad download too, so I downloaded from one of the mirrors. Still the same problem.
Click to expand...
Click to collapse
So you did not check the MD5 hash?

Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app

mapheG2 said:
Im a bit of a noob and all of this wasnt around when I was flashing CM roms ages ago. How do I do that? Would that fix my issue??
Sent from my T-Mobile G2 using xda app-developers app
Click to expand...
Click to collapse
An MD5 hash is something like a fingerprint of a file and it was definitely there when you first flashed CyanogenMod ROMs. The MD5 hash/sum is used to compare two files because it is possible that a downloaded file is slightly different from the original file due to mistakes that could have happened during transfer. So "checking the MD5 hash" means using a program to calculate that "fingerprint" of your downloaded file and comparing it with the "fingerprint" mentioned in blk_jack's thread. If the file you have downloaded is slightly different, its MD5 hash will be different from the MD5 hash that it should have and thus will be unusable and lead to a phone being stuck at HTC boot logo.
By the way, downloading a file from two different mirrors doesn't exclude the risk of getting a corrupt file.

I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?

mapheG2 said:
Ok, so if it is a bad download, how do you remedy it? Because there are only so many options to download the ROM right. And what program are you referring to
Click to expand...
Click to collapse
There are actually lots of programs to calculate an MD5 hash. If you are on Linux it usally is as easy as typing md5sum <path to file> in a shell and reading the output. If you are on Windows, I'd recommend a Google search for "md5 generator" or something like this. Maybe even your recovery is able to calculate a file's MD5 hash - I'm using 4EXT and it definitely is, though I don't know if ClockwordMod is.
You can't remedy a bad download except trying to download it again, hoping that the file will be transferred right.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
mapheG2 said:
I ran "md5 update.zip" from my Mac's desktop where the file is located. I was returned MD5 (update.zip) = 2a314e5f1361825c83a354aea38c6c4b .. which matches the md5sum of what was given. What next?
And I noticed you have the same H-Boot information that KB was talking about earlier, so I guess that can't be the problem either. Should I just try to Superwipe?
Click to expand...
Click to collapse
Oh, sorry - didn't update the thread's page before submitting my reply.
Just try it, there should be nothing wrong with it.

Okay, I read that I should manually clear all the data and cache first and THEN run the superwipe, followed by installing the ROM right? And I will be downloaded from the thread I listed because I still have ext3 I guess and don't want to deal with a ext4 change right now.

Backup and Restore of Stock Gio S5660M Rom After Installing EXT4 Based Custom ROMs

I have been researching the forums for a few weeks now but I have not stumbled across enough threads that would assist me to fully understanding the proper process for restoring via CWM back to a stock ROM (without going back to ODIN to flash it).
Of course this all relates to my Samsung Gio GT-S5660M from Bell in Canada (Pay as you Go). I really only purchased the phone to play with it to learn more. My wife has had the same phone for over a year. Her phone was rooted in order to be none carrier specific so she could use it to replace a phone under contract that was stolen. Other than that, it is stock.
I tried not to post and continue reading but now I am at the point where I need to ask a some specific questions.
First, some background as to what I am trying to do and what I have done so far.
The goal, as I am sure is the case with others, is to test custom ROMs but also be able to restore back to a factory default Samsung based ROM CWM backup at any point in the most convenient fashion.
I would like to perform this process with known working tools on this forum.
To start, I am familiar with the installation of the CWM from phiexz's work http://forum.xda-developers.com/showthread.php?t=1421650. I have installed 5.0.2.7 via Flash from Recovery signed_cwm-5.0.2.7-flashablezip-ext4+rfs. After the installation of CWM I performed a backup of the stock rom.
Once that was complete, I began playing with some custom ROMs installing them via CWM off the SD card from zip files.
I learned after installing the custom ROMs that my phone was reformatted to EXT4 file system. This obviously makes it difficult to simply restore back to the stock ROMs original RFS file system easily. I received the obvious errors message (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) when trying to restore the original ROM files via nandroid restore within CWM.
I have reviewed the nandroid backups stored on the SD card in the \clockworkmod\backup\appropriate dated file and I can see that the file names include RFS before the .tar extension for the system, data and cache files. From everything I have read this is normal since stock Samsung ROMs (at least FROYO and Gingerbread based ones) are based on the RFS file system as opposed to most custom ROMs which are based on EXT4. I made backups of some of the ROMs I was playing with from within CWM nandroid backup. I did notice those files had ext4 before the .tar extension in the file names. So I believe I am clear in understanding that portion.
I read that the only way to really get back to the RFS file version is to use ODIN to flash back the stock firmware all in one package retrieved from www.sammobile.com for the GT-S5660M for Bell in Canada. That again worked perfectly fine. I again went back into restore mode and re-installed signed_cwm-5.0.2.7-flashablezip-ext4+rfs. Once CWM was installed I tried to restore the original stock ROM backup I had saved originally and it gave me the same error (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) even though I know the phone is now back at RFS file system again. Even when I try to perform a backup from CWM of the ODIN installed stock rom it complains stating (Backing up system.... Can't mount /system!.
I of course can reinstall Custom ROMs and restore them just fine after one initial installation and the file system being formatted back to EXT4.
So here are the questions.
1. What is the proper way to restore a stock ROM backup?
2. Is it possible to convert the RFS backup or existing system to EXT4 and have it still operate?
From what I can tell there is custom kernels that support EXT4 that can be injected via ODIN or CWM. Such as CF-ROOT however it is completely confusing to me on how to do that. I tried the ODIN method and that complained. I am not sure what version of CF-ROOT to use. Really I would like to stay with the EXT4 file system and convert the Stock backup to run with a custom ROM if need be. The goal is really just to be able to do it all within CWM and not require a computer other than for transferring files to the SD card as required.
I do not mind using ODIN but I would like to be able to restore with all the settings and changes I made in the stock OS to carry forward so I do not have to do that again.
3. Is there an easier or more reliable method to carry these steps out? Overall I would choose a method that consistently works over convenience.
Any assistance that could be provided would be appreciated.
Thank you in advance for your time in reading and/or hopefully replying to this thread.

Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk

AvrX said:
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply AvrX.
Is there any particular reason you are suggesting that I use an older version of cwm (5.0.2.6) over 5.0.2.7? Is it due to your experience with stability between the two versions or support of RFS over EXT4?
Also your procedure is a bit vague to me.
Why would backing up another version of the stock ROM again assist me? Converting the stock ROM to EXT4 and then reflashing stock ROM again with Odin does not really make sense. Does the phone have to be rooted again? I thought once rooted you did not have to root it again.
I believe I am even more confused now.
I am confident these are all noob questions that can be answered by someone out there with S5660 experience. Then maybe this thread can be locked for future reference for everyone.

http://forum.xda-developers.com/showthread.php?t=1449320
The thread above is not in the S5660 area but it seems like a step in the right direction. I just can not figure out what version of CF-Root to install via CWM from the following thread http://forum.xda-developers.com/showthread.php?t=788108 for the GT-S5560M. I realize the thread is for a different model phone though.
There is the thread for the GT-S5660 http://forum.xda-developers.com/showthread.php?t=1564629 but I do not see where you download the file for CF-ROOT 3.7. I have signed up for Gio Community forum but my account is not approved yet.
Hence I am still at a loss as to what to do next.
So as you can see I have done research which leads me to believe it is possible but I have no proof it can be done or I just do not fully understand and/or have access/knowledge of the tools to achieve it.

(I have the Canada Model of Galaxy Gio)
1. First use EXT4-only version of CWM
2. You could do a nandroid backup of your EXT4 ROM, the rename then files from .[highlight]EXT4[/highlight].IMG to .[highlight]RFS[/highlight].IMG
3. If you do this, make sure you also edit the [highlight]md5sum[/highlight]
4. Now use RFS+EXT4 version of CWM
5. Replace boot.img in the folder where you saved the backup, with a RFS kernel only! (Stock Kernel) To avoid bricking...
6. Then restore using CWM or nandroid
NOTE:​Do with your own risk. I plan to do it myself soon, but be careful...​

I've re-read your post a few times and I'm not 100% certain that I get what you're trying to do... Going back to a completely stock, out-of-the-box phone from CWM?
Different builds of CWM are available for the Gio. Some support RFS, others ext4. I'd rather avoid those with dual support as they're not very clear regarding what format they're using for which operation.
Let's clarify the types of ROMs out there, you've got:
-Stock, Samsung releases, RFS, Odin-flashable. Leaked images (such as those from samfirmware et al.) contain the CSC image, "put-together" ones (like my early 5660M stock backup) don't as the files are already integrated.
-Stock-based. Community-made ROMs with varying levels of modification; earlier ones were typically Odin-flashable (with a number of issues due to modem and kernel changes, especially for 5660M and V users), later releases usually CWM-flashable. File system support depends on the kernel used. The Samsung kernel only runs RFS, whereas others such as Phiexz's will run either ext4 or RFS.
-AOSP and derivatives. Community-made, CWM-flashable, ext4 ROMs, such as CM7, 9 and 10, or MIUI.
Recoveries:
-CWM, as previously discussed
-Stock: the Samsung recovery you've overwritten pretty early on if you're a typical XDA poster. It does provide for proper CSC installation when flashing a stock ROM through Odin. Can also do a factory reset and reformat /data and /cache RFS partitions.
In most situations you would want to go back to a stock ROM and kernel, but keep the CWM recovery, that's relatively easy to do with an RFS-compatible CWM and a nandroid backup. Even a non-RFS compatible CWM could be made to work with appropriate images and the (ADB shell) dd command.
But back to the question: going back to a completely stock, out-of-the-box phone from CWM, stock recovery, CSC and all?
I've thought about it for a few minutes, and it might just be possible to do. Neat? Kinda. Worth the trouble? Meh.
It would involve dd-ing RFS-format /system, /data and /cache partitions, boot.img and recovery.img, into place.
The part I'm not sure about is how to go about extracting CSC.rfs in the proper location and issuing a reboot recovery command at the end of the script, which should kick stock recovery into gear and apply CSC.
Maybe one manual reboot to finish the process.
Let us know if that helped,
Darkshado

Thank you for the replies Peteragent5 and Darkshado. Again I really do appreciate your time and your support of those out there interested in learning more about android based devices.
Going back to a completely stock, out-of-the-box phone from CWM?
Click to expand...
Click to collapse
Good question Darkshado....let me try to clarify things again. I apologize as I tend to ramble. I would rather give more information than not enough.
Yes that is the goal. Or at least I would like the ability to do that. I understand it is not entirely accurate though as with the installation of CWM it is not really stock.
Let's clarify the types of ROMs out there, you've got:
-Stock, Samsung releases, RFS, Odin-flashable. Leaked images (such as those from samfirmware et al.) contain the CSC image, "put-together" ones (like my early 5660M stock backup) don't as the files are already integrated.
-Stock-based. Community-made ROMs with varying levels of modification; earlier ones were typically Odin-flashable (with a number of issues due to modem and kernel changes, especially for 5660M and V users), later releases usually CWM-flashable. File system support depends on the kernel used. The Samsung kernel only runs RFS, whereas others such as Phiexz's will run either ext4 or RFS.
-AOSP and derivatives. Community-made, CWM-flashable, ext4 ROMs, such as CM7, 9 and 10, or MIUI.
Click to expand...
Click to collapse
Well of course I started with the Out-of-Box Stock Samsung/Bell Canada ROM on the phone based on Gingerbread 2.3.4. I rooted it of course. Then I installed CWM that supported both RFS and EXT4. I believe 5.2.0.7 by Phiexz as mentioned in my first post. To be honest, since I am a noob and I wanted to get started so quickly, I cannot honestly remember which version of CWM I used originally. It may have even been px-CWM-v2.zip. Regardless of the version it obviously supported Stock Samsung/Bell Canada RFS based file system and I used that to make the Nandroid based backup within CWM of the existing Stock ROM on the phone.
After that point I thought I would be safe to start playing with Community-made ROMs CWM-flashable installs based on the GT-S5660 although of course I had the GT-S5660M Canadian version. So I went forward and tried [ROM] Enhanced236 - stock 2.3.6 (06.08.2012 update) http://forum.xda-developers.com/showthread.php?t=1654317 as I wanted something close to original version of Gingerbread that came Out-of-Box with the phone but was upgraded to fix and issue I had with version 2.3.4 of Gingerbread.
The main drive for doing this was to assist my wife with an issue she has on her Bell GT-S5660M running on the SaskTel telco in SK. There is an issue with her SMS/texting. She always has to turn on/off Settings, Wireless and Network, Mobile Networks, Use Packet Data to get texting to send out. Receiving is fine. It seems to be a known issue when the phone is used with Telus or SaskTel networks in Canada. From what I understand the phone with 2.3.4 of Gingerbread is not affected on the Bell and Rogers network in Canada. It seems to be related to a bug in the phone at the particular Gingerbread version 2.3.4 from what I read. Since Kies did not have an update for the Bell based phone beyond version 2.3.4 I thought it is time to check out custom ROMs. After trying her SIM card with the Enhanced236 - stock 2.3.6 everything worked perfectly on my test phone for texting. So I took a Nandroid backup via CWM of that ROM. Then I tried [DEV] CyanogenMod 9.1 / CyanogenMod 10 by MacławStudios http://forum.xda-developers.com/showthread.php?t=1414173 to see what the Jelly Bean hype was about and again made a CWM backup of the ROM to maintain my settings.
I had a friend over and I was showing him what I had learned so far and I was showing all the capabilities of CWM. Then I told him I could even restore back to original factory ROM as well although I had not tried it yet thinking CWM was full proof. I tried it and it failed in front of him. So then I thought...wow...I do not understand as much as I think. That is when I stumbled on the difference between RFS in Stock Samsung ROMs and EXT4 in the Community-made ROMs. Sorry I know that is quite a bit of background information but it helps to show where I am coming from in terms of wanting to accomplish to here.
So I read a bunch and realized that the only way to go back was to flash back to Stock with ODIN. So that at that point I tried your Stock ROM GT-S5660M_MUGKG3_stock_rooted_ROM and the one from sammobile for the GT-5660M from Bell GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3. I thought then I could simply install CWM again (the version that obviously supports RFS and EXT4 5.2.0.7) and then restore the original Stock Nandroid backup I made of the original Out-of-Box ROM. As mentioned in the previous post I saw the rfs in the file names of the back before the .tar extension.
That is when the failures in restoring via CWM occurred noted in the first post (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!). I thought this would work for sure. That is when I started to think if I could get this all to work I would convert the stock ROM with a custom kernel to running exclusively on EXT4 so that if I ever wanted to go back to 2.3.4 I could do it easier with out having to use ODIN and going back to stock RFS file system. So I guess really I do not want to go back to Stock but the Stock Files in EXT4 formatted form...which I understand would require a custom kernel. Regardless I am not able to restore the original backup so obviously there is something I am missing. That is where I would like to start. I thought as long as I can not get the original backup to restore....then I do not understand enough to continue on the journey. Hence to post requesting assistance.
Can also do a factory reset and reformat /data and /cache RFS partitions.
Click to expand...
Click to collapse
I am not exactly sure what you mean here. Once I flashed the Stock RFS Samsung/Bell Canada ROM back via ODIN in some cases it would not boot. It was in a boot loop stuck on the Samsung logo. I went into normal recovery mode (Not CWM recovery mode since I did not reinstall it yet at that point) and I would perform the Wipe Data and Wipe Cache functions within recovery to get it out of the boot loop. I always made sure the OS fully loaded and functioned before moving to the next step of what I was trying to do. It was at that point I would install CWM again and then find out the original backup I took would not restore with the same error (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!).
In most situations you would want to go back to a stock ROM and kernel, but keep the CWM recovery, that's relatively easy to do with an RFS-compatible CWM and a nandroid backup. Even a non-RFS compatible CWM could be made to work with appropriate images and the (ADB shell) dd command.
Click to expand...
Click to collapse
I read a bit about this but I did not completely understand it. Is there a thread you can point me to in regard to this? Ultimately the goal is just to be able to restore to stock (or stock converted to EXT4 with a custom "close to original" kernel like CF-Root) if and when I want to in the easiest fashion.
But back to the question: going back to a completely stock, out-of-the-box phone from CWM, stock recovery, CSC and all?
I've thought about it for a few minutes, and it might just be possible to do. Neat? Kinda. Worth the trouble? Meh.
Click to expand...
Click to collapse
Yes I can understand that it is a bit of an odd request and not one that many would really be that interested in...but I am simply from the point of view of just seeing if it is possible. Once I get something in my head I want to prove or disprove it is possible. But I need knowledgeable people like you to offer suggestions and share past experience. I do not mind performing the work....I just need some help from time to time. I have been employed in the IT field for over 15 years but I am more of Windows guys.... but I am not afraid to play with anything and learn. Please do not bash me on the Windows/Microsoft thing....it pays the bills.
Again the goal is to keep everything within CWM so that you do not really need to go back to a computer. It might take some work and effort to get there though. I am not sure who else would be interested but it then could be shared with the masses on this forum. Again not sure of the value to everyone.
It would involve dd-ing RFS-format /system, /data and /cache partitions, boot.img and recovery.img, into place
Click to expand...
Click to collapse
GREAT!!!...I am game to try it. Again if you have a post of step by step on how to achieve this it would be appreciated. I believe I saw a post of yours when I was performing my research about this but it may not be exact for what we are trying to accomplish here. Perhaps it is though.
The part I'm not sure about is how to go about extracting CSC.rfs in the proper location and issuing a reboot recovery command at the end of the script, which should kick stock recovery into gear and apply CSC.
Click to expand...
Click to collapse
Well based on the posts I have read on your dissection of the partitions on the GT-S5660, you are one of the great resources to assist on this. I noticed that the CSC.rfs in not in your GT-S5660M_MUGKG3_stock_rooted_ROM but it was included in the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home from samsmobile. So I am not sure where that version came from if it was leaked or what. I would guess that my original Out-of-Box CSC.rfs has been overwritten by the S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3_home version if there happen to be any differences. My wife's phone is still available so I could still extract the original file from her phone. Maybe that would not help though....I am not really sure what is contained in the CSC.rfs if it is phone, ROM specific...etc.
Anyway regardless I appreciate the time anyone has put in reading or thinking about my post. Again thank you for your time and effort. This is really a great forum full of great information.
ps. How much do I dislike the ReCaptcha spam blocker when trying to post? Very much!!!....you have to hit refresh about 100 times before you can actually make out some words you can type.....FAIL. I see it on numerous sites....really annoying...I like the pattern based ones that you put together way better.

NOTE:​Do with your own risk. I plan to do it myself soon, but be careful...​
Click to expand...
Click to collapse
You first. You seem to have more experience. Ha!!!. Kinda joking but also kinda serious. I guess I am still a noob so I would be leery to try this. I always have the fear of the bricking.

LOL I admire you for your long list of explanations. As well as Darkshado's posts.
Let's backtrack shall we?
The reason it gave you "error while formatting /system" is because CWM doesn't support converting the filesystem back to RFS. At least that's what I know. But for ODIN, you can do this fine. The thing about ODIN, is that it includes the base RFS files and doesn't come with other RFS partitions because it assumes your phone is already RFS
Hmmm I don't know any reason to go back to Stock RFS if you have already converted your partitions into a far more superior filesystem --> EXT4. Darkshado has his own custom ROM that has these specifications
A CF-Root kernel is a kernel that includes root. So when you flash the kernel, it also gives you root and possibly busybox.
Busybox is a series of UNIX tools for Linux and derivatives (Android) to use in the Terminal.
Hehe. It's fine if you're getting paid at IT, or doing IT, dunno which one.. But if you wanna learn more about Android and whatever stuff about it, that's great! It's a nice place to start. Then make your way towards linux.
Linux Distros (Distributions):
Ubuntu = Newbies
Debian = Ubuntu based on this
Fedora = Productivity
Linux Mint 12/13 = Ease of Use
Arch Linux =Advanced
BackTrack = Hacking/Cracking
Tails = Security
Bohdi = Speed
SliTaz = Small & For old hardware + Nice UI
(Just giving you tips here, if you do wanna do this )
Be careful if you're dd'ing your data, cache, system, stl, bml, etc..
Because there is a chance of bricking your device. I know dd'ing stl5 has a high chance that you'll brick your device.
The CSC contains all the info about your carrier, and some other stuff... Lol
Yes I hate the 5 minute waiting period to post a reply or thread, and i hate the captcha..
Sent from my BlackBerry PlayBook

Let's backtrack shall we?
Click to expand...
Click to collapse
Fine by me.
The reason it gave you "error while formatting /system" is because CWM doesn't support converting the filesystem back to RFS. At least that's what I know. But for ODIN, you can do this fine. The thing about ODIN, is that it includes the base RFS files and doesn't come with other RFS partitions because it assumes your phone is already RFS
Click to expand...
Click to collapse
Okay I understand that. However when I made my first backup via CWM the system was stock with RFS. When I restored back to stock ROM after playing with custom ROMs with EXT4 filesystem, the system was back to RFS right? Therefore how come the original restore would not work when the filesystem of the stock rom was back to RFS. That is where I am struggling. Is there an easy way to confirm you are on RFS vs EXT4 from within CWM? Or does ODIN have the ability to restore the RFS Stock version back to a EXT4 formatted phone. I assumed it converts the system back to RFS during the flashing. Is that an incorrect assumption?
Hmmm I don't know any reason to go back to Stock RFS if you have already converted your partitions into a far more superior filesystem --> EXT4. Darkshado has his own custom ROM that has these specifications
Click to expand...
Click to collapse
I guess I have not spent the time to really check out every single Custom ROM. So are you saying Darkshado's ROM is Gingerbread based with EXT4? I agree I would like to stay with EXT4 over all as I understand it is superior and that even Samsung has finally moved to it for its Stock ROMs on newer phones. Really I just want the stock image converted to EXT4 and the ability to restore to that EXT4 based version of the stock ROM via CWM.
A CF-Root kernel is a kernel that includes root. So when you flash the kernel, it also gives you root and possibly busybox.
Click to expand...
Click to collapse
I also understand that CF-Root supports EXT4 and is supposed to be the closest to the original Samsung based kernel.
Hehe. It's fine if you're getting paid at IT, or doing IT, dunno which one.. But if you wanna learn more about Android and whatever stuff about it, that's great! It's a nice place to start. Then make your way towards linux.
Linux Distros (Distributions):
Ubuntu = Newbies
Debian = Ubuntu based on this
Fedora = Productivity
Linux Mint 12/13 = Ease of Use
Arch Linux =Advanced
BackTrack = Hacking/Cracking
Tails = Security
Bohdi = Speed
SliTaz = Small & For old hardware + Nice UI
(Just giving you tips here, if you do wanna do this )
Click to expand...
Click to collapse
To be more clear I am employed in the IT field/profession..however you want to describe it...for the past 15 years. More of a Windows Server Administrator position and previous to that various other positions starting in client support. I have played with Ubuntu before and I have used bootable versions of Knoppix and other linux based distros in the past. I just do not use them enough on a regular basis. It is more of a time issue than anything. Arch Linux looks interesting to me. Perhaps enough to try. I appreciate the tips. Regardless playing with the phone is fun for me for now. I have an iPhone as well but I love the flexibility and NON closed ecosystem that android offers. I guess ultimately both are based on Unix/Linux based OSs.
Be careful if you're dd'ing your data, cache, system, stl, bml, etc..
Because there is a chance of bricking your device. I know dd'ing stl5 has a high chance that you'll brick your device.
Click to expand...
Click to collapse
That is exactly why I am asking for step by step. It is really not worth it to me if the potential of bricking is high. I am interesting in playing and learning but not at the stake of losing the cash I put in to play with the phone.
The CSC contains all the info about your carrier, and some other stuff... Lol
Click to expand...
Click to collapse
I figured based on what I read in Darkshado partition mapping post that CSC has the carrier content. Really then that does not seem that important if the carrier is the main part of it to consider it for restoration. Again unless there is other items in there I should be concerned about.
Yes I hate the 5 minute waiting period to post a reply or thread, and i hate the captcha..
Click to expand...
Click to collapse
Well that is 2 votes. Moderators please consider another spam deterrent. Ha!!!

AvrX said:
Backup with cwm 5.0.2.6 and then when you have ext4 flash stock via odin. Root with stock cwm and then flash cwm 5.0.2.6 and restore.
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
Well it appears that CWM 5.0.2.7 may have been one of my issues in getting my original backup to restore.
I loaded CWM 5.0.2.6 from the following thread http://forum.xda-developers.com/showthread.php?t=1493932 and I was able to restore my original backup of the stock ROM with no issues. Thanks again Peteragent5 for putting that great post together.
Also a thank you AvrX for that for the suggestion of going back to 5.02.6. Also Darkshado's guidance of sticking with a CWM that supports one file system or the other.
I downloaded and installed the second version of 5.0.2.6 indicated in the 1st post of the thread named S5660M_cwm-5.0.2.6_feb_26_12.zip. Not sure if that is correct or not Peteragent5 as I not totally understanding the difference between Phiexz & Maclaw Roms and My ROMs in your post. I would assume you are speaking of the Custom ROMS created by Phiexz & Maclaw vs ones created by you? Regardless it would be nice to have a bit greater detail so I am confident in which tool to use in which situation.
So question 1 from my original post in this thread has been solved. Well sort of. Still not clear why 5.0.2.7 supports both RFS and EXT4 but it seems like all the functions for formatting are EXT4 based within it. Although the backup I made within it still shows the rfs prior to the *.tar extension.

Based on my last post I have a few new questions. After performing some more testing (trial by fire/trial and error) with CWM I am not sure that I really understand the support of CWM 5.0.2.7 RFS and EXT4 file system as mentioned in my last post.
Typically before I perform a backup of a ROM (in this case the stock ROM which is RFS filesystem based) I perform the following procedure in CWM regardless of the version of CWM
1. wipe data/factory reset
2. wipe cache partition
3. go to advanced menu
4. Wipe Dalvik Cache
5. Wipe Battery Stats
6. Main Menu -> backup and restore
7. Backup
Questions:
1. Is that the correct procedure? Could some steps be left out or added? What is the safest most reliable way? Should I even use those steps before I perform a backup or are they only really to be used when you are having problems? These are all really the same question presented in different ways.
2. If I am using CWM 5.0.2.7 (supports both RFS and EFS) and I perform the wipe data/factory reset, I see that it is Formatting /data /cache /sd-ext etc on the screen. Also with the wipe cache partition option I see Formatting /cache displayed on the screen. When using these functions in CWM 5.0.2.7 does this format the phone for those partitions from RFS to EXT4?
I am beginning to agree with Darkshado's comment
Different builds of CWM are available for the Gio. Some support RFS, others ext4. I'd rather avoid those with dual support as they're not very clear regarding what format they're using for which operation.
Click to expand...
Click to collapse
However if anyone else has done some extensive testing and know the answer to this....then I can move on and stop using tools. I believe that some of the tools are suppose to work and perform a certain operation but do the opposite or not what is claimed or do not explain the functions well enough for me to understand what operation does what. I want to understand....not just do.
The reason I am asking is that when I try to run a restore of an RFS (stock ROM) backup that was preformed in CWM 5.0.2.6 (only RFS supported) or a backup from CWM 5.0.2.7 (supports RFS and EXT4) after performing the above procedures within CWM 5.0.2.7, it always fails with the
dreaded (E:format_volume: format_rfs_device failed on /dev/block/stl12 Error while formatting /system!) error. This is of course after flashing via Odin back to the stock RFS based ROM GT-S5660M_BMC_S5660MUGKG3_S5660MUGKG3_S5660MBMCKG3 from sammobile.com and then entering stock recovery mode and installing CWM 5.0.2.7.
Does CWM 5.0.2.7 change the stock Kernel on my phone to one that supports RFS and EXT4? My assumption is yes but it would be nice to know for sure.
Based on my testing and findings so far I can tell right now that 5.0.2.7 is more EXT4 based then RFS. It will read RFS files and install on an RFS based filesystem (Stock ROM) and it will even make good backups of the RFS system. However it will not restore those RFS backups regardless if they were made in CWM 5.0.2.6 or CWM 5.0.2.7. Now if you flash back to stock ROM again via ODIN and install CWM 5.0.2.6 only RFS supported, you can restore backups of RFS based file systems backups( on a stock ROM system) made in either CWM 5.0.2.6 or CWM 5.0.2.7.
So the verdict is again (finding out the hard way)....DarkShado and AvrX are indeed correct. Use CWM 5.0.2.6 for backups and restores of Stock ROM.
For custom ROMs...which are predominantly EXT4 based now...I guess you need to use 5.0.2.7....but I will use the soley EXT4 based one from now on as the RFS & EXT4 based one I believe is limited. The only thing is if you install the 5.0.2.7 EXT4 only supported version, you will need to use the EXT4 Formatter (installed via CWM) before to make everything work properly before playing with EXT4 based Custom ROMs. Unless EXT4 formatting is built into the installer like it is with enhanced236_06.08.2012.
Morale of the story is again Darkshado is correct in what he was implying....what I am trying to accomplish is "Neat?" "Worth the Trouble"....My answer now...is a "NO".
None of the current versions of CWM "Fully" (read and write) support RFS and EXT4 at the same time and allow you to return to the stock based RFS backup plus play with EXT4 based new Custom ROMs. I know about the EXT4 Formatter....does anyone know of RFS Formatter tool that installable via CWM?
That tool might accomplish what I would like to achieve. Then it really is only a matter of the procedure to follow to make it all work within CWM. Just have to switch between CWM 5.0.2.6 and CWM 5.0.2.7.
Thanks for following the thread and reading my "trial and error" findings. I may perform a summary of my current findings in this post. It would be be a reply to my questions in the first post with the answer to my own questions. However I think I will wait to see if anyone is interested in providing any further comments.

modem issues after flashing anything other than stock
I am facing a similar issue to you TrippleRipple.
Sorry for the lengthy back story..but here it goes;
I am in Saskatchewan on Sasktel and I had originally given this phone to my son flashed with CM9 as a cheap android media and games device...but the screen on my SGS2 broke the other day and my son offered to "rent" his to me to use until my screen replacement comes in. When I put my SIM in the device (unlocked by retrieving code via ADB) it can connect to some providers in the area (Rogers)...but not to my home network of Sasktel. I read in a previous thread here on XDA that there is an issue with the baseband of custom firmware and that you should keep your stock modem for Bell/Telus handsets (Sasktel also falls in that category)....and so..I am trying to completely restore stock FW...to be able to connect to my home network.
Did you/do you have this modem issue as well?

kid___icarus said:
I am facing a similar issue to you TrippleRipple.
Sorry for the lengthy back story..but here it goes;
I am in Saskatchewan on Sasktel and I had originally given this phone to my son flashed with CM9 as a cheap android media and games device...but the screen on my SGS2 broke the other day and my son offered to "rent" his to me to use until my screen replacement comes in. When I put my SIM in the device (unlocked by retrieving code via ADB) it can connect to some providers in the area (Rogers)...but not to my home network of Sasktel. I read in a previous thread here on XDA that there is an issue with the baseband of custom firmware and that you should keep your stock modem for Bell/Telus handsets (Sasktel also falls in that category)....and so..I am trying to completely restore stock FW...to be able to connect to my home network.
Did you/do you have this modem issue as well?
Click to expand...
Click to collapse
To be honest, I have only really been playing with the custom ROMs but not really using them with an active SIM. So unfortunately I am not the best point of reference. I do know the stock firmware on sammobile does have the correct baseband in it as I copied down all of the details of the original out of box rom and it was the same once restored with the stock firmware from sammobile via odin. However with the out of box stock rom, there were issues with texting on SaskTel. You might want to try the enhanced236 ROM. That seemed to work fine on SaskTel with texting as well. However you should of course backup what you have now with CWM so that you can restore it back for your son when you get your other phone back.
I have not tried CM9 with the SIM chip...only with enhanced236. I did however play with CM9 and CM10. Sorry I could not have been of more assistance. Good luck.

[Q] HOW-TO? Clean ENTIRE phone, Manual or Superwipe?

IDK if this is ever an issue for new users but When I search I never find the exact thing I wish to know but much close to it.
In all My 16GB phone as of yesterday with no media or installed apps my phone had only 1 GB free and the filesystem was full of folders from old apps. I had installed and uninstalled many apps and flashed many roms, Which I believe left many leftover files. So I was told to format the System Partition and either restore or install a new rom. Since my latest nandroid was ICS based I decided to start fresh (also to clear up as much space I could.
My question now is, I still have many extra files from uninstalled apps. My phone now has 6.8GB of the available 11.8GB according to Windows 7.
So to completely START CLEAN what is the best method? (I will have a nandorid backup and a rom to install both on my pc and on my External SD Card)
Using CWMR,
Format System, Then Format SdCard? Then the Steps Required to install The Specific ROM you will now install.
Is the SdCard partition the usable space? If it is then the System Partition Contains all System Files and leftovers from flashing Roms and Kernels? If that is correct then Is the SdCard Partition basically the Users Space for apps and Media and what Shows up on the PC and The user Directory once Rooted?
Is this The Best way to do it? I have Seen Superwipe although have not found a page specifically about it. I have found versions of the script for many devices. Since their seems to be one available for the Samsung GS3 should i just flash that (I see it on the page for installation of the Xquizit Rom) and on an older post for another device said that it would "wipe /boot /data /system /cache and /devlog" then it says your phone is ready to install the rom (on the page i forget the rom or device it was for).
So to Clean my phone to the point that it is as close to possible as being new and this is the first rom to be installed and the first apps to be installed, when i install apps.
To accomplish this Should I? Use CWMR and manually format the system and the sd card partitions? or use the Superwipe script from the Xquizit Rom page?
Lastly but Most Importantly to use Superwipe do I simply just flash the zip? Also if i do it manually Have i described the correct way to do it?
Last of all Thank you and Sorry Its I just have never done this and as i still haven't even paid off my phone I don't want to Brick this phone at ALL.

Since this post has no reply's but some views that means i either asked a question that either A. has been asked and answered and i have not found it. or B. This is something that is so easy its never really been an issue.
If its A. Could someone be kind and just link to a post, or post the correct search term as I have been unable to find it.
If its B. Then to close this will I have a problem formatting the SD-card the same way I formatted the system partition
Also is their a Superwipe how to? and does it do what i think it does (basically format your hole phone in one easy step by running a script via your recovery mod?
I just don't want to brick this phone when it comes to formatting it just scares me for the first time.

Use the Odin software for a clean install. It wipes partitions, radio's everything. You can choose to intall a rooted Tmo update with Odin so that way you are ready to go. Just flash CWM with Rom manager after using Odin and you are ready to flash any rom you want.
See this thread.
http://forum.xda-developers.com/showthread.php?t=1949687

Go here http://samsung-updates.com/device/?id=SGH-T999
Download: Galaxy S 3 (T-Mobile) SGH-T999 TMB T999UVDLJA Android 4.1.1 20.10.2012 19.10.2012
Then just odin that file and this will reset your phone 100% like you bought it from the store.
Then after that you can re-root your phone, download Titanium Back up and clean up bloatware or simply flash a custom rom.

Crisisx1 said:
Go here http://samsung-updates.com/device/?id=SGH-T999
Download: Galaxy S 3 (T-Mobile) SGH-T999 TMB T999UVDLJA Android 4.1.1 20.10.2012 19.10.2012
Then just odin that file and this will reset your phone 100% like you bought it from the store.
Then after that you can re-root your phone, download Titanium Back up and clean up bloatware or simply flash a custom rom.
Click to expand...
Click to collapse
Will Odin even replace custom recovery and radio with the stock recovery and radio? Or must that be done manually?
-Sent from my Razr i on AT&T.-

Yes ODIN will replace everything. I suggest using the pre-rooted route66 file for ODIN in Doc's thread I referenced above. It saves a step.

phositadc said:
Will Odin even replace custom recovery and radio with the stock recovery and radio? Or must that be done manually?
-Sent from my Razr i on AT&T.-
Click to expand...
Click to collapse
Yes. Odin will replace everything. You would have a phone just as if you bought it brand new @ a store.
Sent from my SGH-T999 using xda app-developers app

jcbofkc said:
Yes ODIN will replace everything. I suggest using the pre-rooted route66 file for ODIN in Doc's thread I referenced above. It saves a step.
Click to expand...
Click to collapse
Wow good to know so returning to bone factory stock is as simple as running triangle away if necessary and then using Odin to flash stock firmware. Amazing!
-Sent from my GS3 running CM10.-