Related
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.
Hey guys I have a quick question. My buddy has the Samsung Epic 4g and was running from store stock DK18 build. He recently updated to DK28 using the leaked update.zip method. So far his phone is working fine with the exception of the gps not working. I dont own a samsung and after reading through all this info im super glad cause I see nothing but problems from what I am reading. Things are so much easier with my OG moto droid haahhahahah. He wants to root his phone and install a custom rom.
But most of the roms I look at say you need the dk28 modem installed first. Was the DK28 modem installed with the DK28 2.2 update zip? Or it wasnt included with that? How can I tell on his phone if he has the DK28 modem? Is the only way to get the DK28 modem on his phone by flashing it using odin? I find it hard to believe that there is no update.zip for it by now. If anyone can help me out with this or point me in the right direction I would appreciate it. Would much rather just find the update zip for the dk28 modem so I dont have to mess around with odin since I dont own a samsung.
There are way to many threads on here regarding this issue so its kinda hard to sort through them all. Any help would be appreciated. Thank you.
Go to Settings=>About Phone. This will tell you you're baseband version. If it says DK28 at the end you're set...otherwise read on.
I just flashed Bonsai 2.0 and the modem was not included. I used the signed modem update afterwards from this thread:
http://forum.xda-developers.com/showthread.php?t=861341
Without the DK28 modem you won't be able to get a signal through the cell radio. Wifi worked but the device was switching airplane mode on and off every half second. Flashed the modem AFTER the rom...I don't recommend this... and all is well.
I was also coming from DI18 and stock rom with a modified kernel.
zetterwing said:
Go to Settings=>About Phone. This will tell you you're baseband version. If it says DK28 at the end you're set...otherwise read on.
I just flashed Bonsai 2.0 and the modem was not included. I used the signed modem update afterwards from this thread:
http://forum.xda-developers.com/showthread.php?t=861341
Without the DK28 modem you won't be able to get a signal through the cell radio. Wifi worked but the device was switching airplane mode on and off every half second. Flashed the modem AFTER the rom...I don't recommend this... and all is well.
I was also coming from DI18 and stock rom with a modified kernel.
Click to expand...
Click to collapse
Ok ok awesome I was thinking that about the baseband version but wasnt sure so figured I would ask. So he does have the dk28 at the end. Thats good. One less step he has to take. How do you like Bonsai? I was actually looking at that one for him. That will probably be the first one he will try.
One more question. How did you root the phone? Did you use the z4root app and then download rom manager and flash clockwork that way? Or did you use one of these one click root programs that I see in this forum? What do you think the easiest way is for him to get root and clockwork recovery on his phone?
Thanks for all your help Zetter I appreciate it.
The best way to root is to use the one-click. It will give you root, recovery, and the recovery redirect.
Rom Manager will not flash clockwork without a custom kernel and z4 doesn't install recovery or the redirect.
DiGi760 said:
The best way to root is to use the one-click. It will give you root, recovery, and the recovery redirect.
Rom Manager will not flash clockwork without a custom kernel and z4 doesn't install recovery or the redirect.
Click to expand...
Click to collapse
Ok awesome thanks for the info Digi. What is the redirect I am seeing that alot but dont really see a quick explanation of what it is/does?
skylordusa1 said:
Ok awesome thanks for the info Digi. What is the redirect I am seeing that alot but dont really see a quick explanation of what it is/does?
Click to expand...
Click to collapse
For one, it allowed the use of multiple recoveries. For example, for a short period, many of us were running cwm 2.5.1.0 AND 2.5.1.2 since one only supports rfs and the other only supports ext4. Booting into recovery via the death-grip brought you to 2.5.1.0 and the redirect allowed you to reboot into 2.5.1.2.
I believe the redirect is also what allows programs like quickboot to reboot to recovery mode without using the death-grip.
DiGi760 said:
For one, it allowed the use of multiple recoveries. For example, for a short period, many of us were running cwm 2.5.1.0 AND 2.5.1.2 since one only supports rfs and the other only supports ext4. Booting into recovery via the death-grip brought you to 2.5.1.0 and the redirect allowed you to reboot into 2.5.1.2.
I believe the redirect is also what allows programs like quickboot to reboot to recovery mode without using the death-grip.
Click to expand...
Click to collapse
Awesome thank you for the info Digi. We used the one click root method and now we have root and when holding the volume , camera and power button we go into clockwork recovery 2.5.1.0. Is there a special button or combo you need to hit for the redirector to work? Or it reboots you into the correct clockworkmod automatically depending on what filesystem RFS/EXT4 you are currently using? Sorry to be such a pain. This stuff is kinda new to me since I dont own a samsung. I really appreciate your help though.
Ok I after reading the bonsai rom thread I found the new oneclickroot with clockwork3. So I tried that one now and was able to reboot into clockwork 3.x.x.x
and install the bonzai rom. Had a problem after the install completed. The phone wouldnt boot up just got hung on the black samsung screen. I know in the Bonzai thread it said not to wipe but after the phone hung I booted into recovery and and did a wipe then installed the bonzai zip again and the phone booted up. GPS still doesnt work so that kinda sucks. But I guess its all trial an error. I will keep reading. Thanks for the help.
Is there a way to check on his phone if he has the ext4 filesystem or the rfs. I am guessing since he has cw3 and was able to boot into the new ext4 bonzai rom he converted to the ext4 FS but would like to know if there is a way to check.
skylordusa1 said:
Is there a way to check on his phone if he has the ext4 filesystem or the rfs. I am guessing since he has cw3 and was able to boot into the new ext4 bonzai rom he converted to the ext4 FS but would like to know if there is a way to check.
Click to expand...
Click to collapse
Like you said, by installing CWM3 you have automatically converted to EXT4...BUT if you really want to check: from adb you can type 'adb shell mount' without the quotes. Or you can type 'su' (enter) then 'mount' from terminal emulator. You should see EXT4 as the fs type for /system, /data, and /cache.
leatherneck6017 said:
Like you said, by installing CWM3 you have automatically converted to EXT4...BUT if you really want to check: from adb you can type 'adb shell mount' without the quotes. Or you can type 'su' (enter) then 'mount' from terminal emulator. You should see EXT4 as the fs type for /system, /data, and /cache.
Click to expand...
Click to collapse
Thanks alot leatherneck. I figured he had it but its always good to double check to make sure everything worked. I see the EXT4 in Term Em. Thanks again for the help. I appreciate it.
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
Sorry if this is a n00b question that has been answered before but I have been reading a lot about rooting/flashing this phone and I am feeling very intimidated. There is a lot of info out there and almost all of it is different in the details.
I will be purchasing a 5660m tomorrow and want to install arpeggiomod and then unlock.
1. Do I have to root the phone before flashing with arpeggiomod? If so can I root with superoneclick?
2. Do I just follow the V0.9 instructions posted here http://forum.xda-developers.com/showthread.php?t=1263025 to install arpeggiomod? I flash the zip file using odin right? Do I need to restore factory defaults before flashing?
3. I need to unlock the phone since I want to use it with Rogers. Do I just use the bml5 unlock method?
Thanks a lot.
1. No. Arpeggiomod Rom comes with Root
2. You flash using a Recovery. Backup your Data. You do need to wipe factory defaults before flashing.
3. Yes you can use BML5 Method. Guide Here
Either click on:
EDIT 7 nov 2011: BML5 method guide
or
EDIT 31 aug 2011: Now Supersafe (BML5) method
Both guide works fine.
If this helped please click Thanks!
Peteragent5 said:
1. No. Arpeggiomod Rom comes with Root
2. You flash using a Recovery. Backup your Data. You do need to wipe factory defaults before flashing.
3. Yes you can use BML5 Method. Guide Here
Either click on:
EDIT 7 nov 2011: BML5 method guide
or
EDIT 31 aug 2011: Now Supersafe (BML5) method
Both guide works fine.
If this helped please click Thanks!
Click to expand...
Click to collapse
Should I flash arpeggiomod first and then unlock? If not what order of operations do you propose?
Flash first then unlock. But if your phone does not say it's locked
then don't try to unlock it!
Peteragent5 said:
2. You flash using a Recovery. Backup your Data. You do need to wipe factory defaults before flashing.
Click to expand...
Click to collapse
Still a bit confused about this step.
So is the following process correct:
1. Format sd card from RFS to ext4 using the ext4 converter on this page http://forum.xda-developers.com/showthread.php?t=1263025
2. No need to run the v0.9 Backup and Restore User Data Scripts since I will have no data on the phone.
3. Install px-CWM-v2.zip http://forum.xda-developers.com/showthread.php?t=1493932 on this page in recovery mode. Should I use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz) instead since arpeggiomod uses phiexz kernel?
4. Wipe factory defaults
5. Use the 0.9 ROM on this page http://forum.xda-developers.com/showthread.php?t=1263025 and flash using the cwm recovery tool.
6. Do i need to wipe factory defaults again after arpeggiomod rom is flashed?
1.correct
2.correct
3.Use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
4.Correct
5.Yes
6.Yes
Peteragent5 said:
1.correct
2.correct
3.Use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz)
4.Correct
5.Yes
6.Yes
Click to expand...
Click to collapse
Thank you very much.
Can I also say that you are doing a great job and that you should keep up the good work. I know that this compliment may not carry much weight since I am new around here but I come across your helpful posts a lot in other threads and you are doing a bang up job.
Thanks man!
FusiveR said:
Still a bit confused about this step.
So is the following process correct:
1. Format sd card from RFS to ext4 using the ext4 converter on this page http://forum.xda-developers.com/showthread.php?t=1263025
2. No need to run the v0.9 Backup and Restore User Data Scripts since I will have no data on the phone.
3. Install px-CWM-v2.zip http://forum.xda-developers.com/showthread.php?t=1493932 on this page in recovery mode. Should I use ClockWorkMod 5.0.2.7 ext+rfs (Phiexz) instead since arpeggiomod uses phiexz kernel?
4. Wipe factory defaults
5. Use the 0.9 ROM on this page http://forum.xda-developers.com/showthread.php?t=1263025 and flash using the cwm recovery tool.
6. Do i need to wipe factory defaults again after arpeggiomod rom is flashed?
Click to expand...
Click to collapse
Welcome on the board, you'll start getting the hang of things in due time. You're researching a good deal, which is an excellent way to do things.
Let me correct some things from Peteragent5's reply though:
1. Flash the CWM linked from the ArpegGioMod first post with Odin. The one modified by Peteragent5.
The ext4 converter does not touch your MicroSD card at all. It formats the internal /data, /system and /cache partitions to ext4.
If you want an additional ext4 partition on your SD card (often referred to as /sd-ext) to use scripts such as Darktremor Apps2SD or S2E, the Phiexz kernel included with ArpegGioMod 0.9 supports those.
SIM-unlocking requires root to read the BML5 partition. Since ArpegGioMod is already rooted, you might as well do it after you've installed the ROM, this will save you from having to root only to wipe that ROM immediately afterwards. (Or do it from CWM, which is also rooted.)
2. Correct
You only need to wipe once in CWM, either before or after flashing the ROM. In the specific case of a new ArpegGioMod 0.9, CM7 or CM9 installation, the formatting of the user data partitions to ext4 wipes them at the same time. To be honest I don't really know where this whole "wipe twice" thing comes from nor what its based on.
Darkshado said:
Welcome on the board, you'll start getting the hang of things in due time. You're researching a good deal, which is an excellent way to do things.
Let me correct some things from Peteragent5's reply though:
1. Flash the CWM linked from the ArpegGioMod first post with Odin. The one modified by Peteragent5.
The ext4 converter does not touch your MicroSD card at all. It formats the internal /data, /system and /cache partitions to ext4.
If you want an additional ext4 partition on your SD card (often referred to as /sd-ext) to use scripts such as Darktremor Apps2SD or S2E, the Phiexz kernel included with ArpegGioMod 0.9 supports those.
SIM-unlocking requires root to read the BML5 partition. Since ArpegGioMod is already rooted, you might as well do it after you've installed the ROM, this will save you from having to root only to wipe that ROM immediately afterwards. (Or do it from CWM, which is also rooted.)
2. Correct
You only need to wipe once in CWM, either before or after flashing the ROM. In the specific case of a new ArpegGioMod 0.9, CM7 or CM9 installation, the formatting of the user data partitions to ext4 wipes them at the same time. To be honest I don't really know where this whole "wipe twice" thing comes from nor what its based on.
Click to expand...
Click to collapse
Thanks a lot for the details.
I see that you have posted detailed instructions for the n00bs in your master arpeggiomod post. Should I follow these? It seems like it because what you wrote above complies with your instructions.
Either. I answered your questions more directly here and figured the first thread post could use some clearer instructions, which I did afterwards.
Complete noobie here. This thread saved my life LOL thanks Shado and Furious. I DID brick my phone, trying to Odin flash a ZIP file (smart one...), but got unbricked just as quickly... it wasnt like this in the PSP Homebrew and CFW days LOL
Just another question for the Droid Gurus: How do I get a2sd up and working on ArpegGio? It seems like a very useful and simple app but I'm having trouble finding specifics... I read somewhere you can only use upto 1gb for apps, not to mention I have Windows 7 so I don't know if I am able to format in ext4... Thanks in advance for anyone who points me in the right direction!!
db416 said:
Complete noobie here. This thread saved my life LOL thanks Shado and Furious. I DID brick my phone, trying to Odin flash a ZIP file (smart one...), but got unbricked just as quickly... it wasnt like this in the PSP Homebrew and CFW days LOL
Just another question for the Droid Gurus: How do I get a2sd up and working on ArpegGio? It seems like a very useful and simple app but I'm having trouble finding specifics... I read somewhere you can only use upto 1gb for apps, not to mention I have Windows 7 so I don't know if I am able to format in ext4... Thanks in advance for anyone who points me in the right direction!!
Click to expand...
Click to collapse
Oh. It seems like you can just install DT's A2SD right away cause of the kernel right? So just download Dt's A2SD from his Facebook page or somewhere in XDA Forums if you find the latest... Then put in root of SDCard and install from Recovery
I just about asked "where's the thanks button" ... why did it take me so long to convert from Blackberry? I'll never miss BBM... XDA rules and can't wait to stay tuned for future progress
Darkshado said:
1. Flash the CWM linked from the ArpegGioMod first post with Odin. The one modified by Peteragent5.
Click to expand...
Click to collapse
Hello all.
I've been lurking on the forums for over a week now, reading tons of stuff, and learning all I can about my new Android phone. I'm a "Windows guru" but new to the 'droid scene. I think I'm ready to flash my phone and really start delving into the custom goodness available to us.
I've read almost every post by Darkshado and Peteragent5 about the Gio S5660M, and would like to try out ArpeggioMod until a version of CM is out of development.
My big question is which CWM Recovery do I flash and how. Instructions say to use Peteragent5's modded CWM, but there are 4 versions in this thread. I have a rooted stock phone on the Solo network. Do I use the Odin version, or one of the other ones via Download/Recovery mode? I'm a little paranoid about bricking my phone.
Thank you in advance for any info provided. A huge thank you to Darkshadow and Peteragent5 for their ongoing work for the Canadian Gio!
Usually you're gonna have to start with the Odin version.
A more "unorthodox" method that should also work would involve flashing the recovery.img file directly to bml9 with the dd command on a rooted phone.
I did not include an assert line to check the model of phone reported in my updater scripts, so it shouldn't matter which version you flash. As long as that recovery supports etx4 properly. (Not all do, such as the older builds by Hyriand, which were configured for RFS only.)
In the case of Peteragent's ROMs, his scripts check for the presence of a 5660M and not just a 5660 from the build.prop included in the recovery ramdisk. Hence the need for the modified build prop compared to Phiexz's original builds which report as 5660.
Maelmord said:
My big question is which CWM Recovery do I flash and how. Instructions say to use Peteragent5's modded CWM, but there are 4 versions in this thread. I have a rooted stock phone on the Solo network. Do I use the Odin version, or one of the other ones via Download/Recovery mode? I'm a little paranoid about bricking my phone.
Click to expand...
Click to collapse
Use the "My ROMS" ODIN version. It should be the same as this link http://www.mediafire.com/?uxzesrnfswxxwes but don't use this link forever because if the file gets updated you will be using a deprecated version.
FusiveR said:
Use the "My ROMS" ODIN version. It should be the same as this link (cut due to posting restrictions...) but don't use this link forever because if the file gets updated you will be using a deprecated version.
Click to expand...
Click to collapse
Thank you. I have spent most of this day playing with flashing and formatting.
This is the file I used to get CWM installed. From there I used Darkshado's directions from Arpeggiomod. I found that if I run the re-odex script, several apps force close on boot (like the CPU clocker and samsung.singin(?) ) so as long as I don't run that, everything works great.
I then installed darktremor's a2sd after partitioning and formatting my sdcard. When I load dt's A2SDGUI it shows 24MB sd-ext (even though i formatted it to 1GB). When I load Titanium Backup it shows the 1GB /sd-ext but none of my apps got installed there. I'm not done playing with this part yet, lol.
I'm wandering how to remove ADW Launcher, since I prefer GO Launcher, but that's just a preference.
Maelmord said:
I'm wandering how to remove ADW Launcher, since I prefer GO Launcher, but that's just a preference.
Click to expand...
Click to collapse
1. Install Root Explorer.
2. Go to /system/app
3. Mount filesystem as r/w (in the upper right corner)
4. Delete ADW Launcher (Make sure you still have TouchWizLauncher)
5. Reboot and test.
Maelmord said:
Thank you. I have spent most of this day playing with flashing and formatting.
This is the file I used to get CWM installed. From there I used Darkshado's directions from Arpeggiomod. I found that if I run the re-odex script, several apps force close on boot (like the CPU clocker and samsung.singin(?) ) so as long as I don't run that, everything works great.
I then installed darktremor's a2sd after partitioning and formatting my sdcard. When I load dt's A2SDGUI it shows 24MB sd-ext (even though i formatted it to 1GB). When I load Titanium Backup it shows the 1GB /sd-ext but none of my apps got installed there. I'm not done playing with this part yet, lol.
I'm wandering how to remove ADW Launcher, since I prefer GO Launcher, but that's just a preference.
Click to expand...
Click to collapse
Would you mind clearing Dalvik cache and then running the re-odexing script? See if that still causes force closes?
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.