I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
No it converted to rfs
Sent from my GT-I9003 using XDA App
Ok... What about I wipe date from cwm? Does that revert the partitions back to rfs as well?
I don't think by wiping your data cache u can revert back to rfs. you have to reflash for rfs.
e398rokr said:
I have a question about ext4 convert here.. Let's say I've flashed to a custom rom that converts my phone's partitions to ext4, once I flash a stock firmware on top of it, do the partitions stay in ext4 or back to rfs?
Click to expand...
Click to collapse
Wiping doesnot changes the partition format. When you flash a new firmware the partitions will be converted to rfs.
send from gt-i9003 using android keyboard
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Lucasred said:
I have a big Q!
Once i flashed KPH and i tried to convert to ext4 via CWM, but i had a problem, after doing a backup i flashed the ext4 zip, when i tried to restore the nandroid i stuck on bootloop!
Any idea of what could have caused this?
Click to expand...
Click to collapse
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
sirilpta said:
I think it is not compatible with xxkph. Try wiping cache and dalvik cach
send from gt-i9003 using android keyboard
Click to expand...
Click to collapse
Could be the reason, but many guys at another forum did it and it worked perfect for them, i think the error could be in the flash of kph, so the whole process went bad
Lucasred, i had the same problem twice. But i had tried it with XXKPQ.
can i converted file system too ext4 on KPU
google translate
user_i9003 said:
can i converted file system too ext4 on KPU
google translate
Click to expand...
Click to collapse
Yes, I'm using it.
For the others: the restore of the nandroid backup after the conversion failed whenever I tried to convert the phone before deodexing it. Try to deodex first, and then convert.
What I found weird was that the error was "not enough space", but when I tried to restore the backup on rfs it worked, doing the same after the ext4 conversion gave the error. I don't know how you could convert the partitions in ext4 with an odexed rom, I didn't look for any solution, maybe if you don't want to deodex your rom you could try to remove some system apps or something like that before the nandroid backup, in order to get more space.
Related
So it has come to my attention that when you restore a firmware via nandroid backup It does not restore the default ext4 partition that you convert. I found this out today when I had hoped my constant flashing would lead to XXKPN not booting unless I used CFRoot when flashing from Cranium [XXKPH]. Only to find out the firmware booted . Now this got me in surprise only because default partition is rfs and not supposed to be able to boot if set partition format was ext4. All default Samsung firmwares come with rfs partition.
Code:
Note: Next time you flash to a new firmware and back, you are required to flash the ext4 script then restore your nandroid backup for that respective firmware.
Misledz said:
So it has come to my attention that when you restore a firmware via nandroid backup It does not restore the default ext4 partition that you convert. I found this out today when I had hoped my constant flashing would lead to XXKPN not booting unless I used CFRoot when flashing from Cranium [XXKPH]. Only to find out the firmware booted . Now this got me in surprise only because default partition is rfs and not supposed to be able to boot if set partition format was ext4. All default Samsung firmwares come with rfs partition.
Code:
Note: Next time you flash to a new firmware and back, you are required to flash the ext4 script then restore your nandroid backup for that respective firmware.
Click to expand...
Click to collapse
I thought everyone knows this Because
1. before converting to ext4 you make backup. And if it will restore filesystem you will never get ext4 (it will always put rfs from backup)
2. when you make backup you can see that it backups files, not partition.
Mods please Sticky this thread and lock it by Misledz's permission before the thread is noob killed
Tapashocked via my gt-I9003 with a random keyboard of my choice !
I think mod should murge this info in already available sticky thread. Making lot of thread sticky will not be a good idea.
vishal24387 said:
I think mod should murge this info in already available sticky thread. Making lot of thread sticky will not be a good idea.
Click to expand...
Click to collapse
I have to agree, although this is helpful information, having too many stickied threads could become a problem.
falex007 said:
I thought everyone knows this Because
1. before converting to ext4 you make backup. And if it will restore filesystem you will never get ext4 (it will always put rfs from backup)
2. when you make backup you can see that it backups files, not partition.
Click to expand...
Click to collapse
I too already know this by reading skin's original post on ext4.
Instructions were to make nandroid backup -> convert to ext4 -> restore backup -> reboot.
After that u will have ext4 partitions.
So after you anything restore from backup, u will still have ext4.
Yeah but this came as a surprise, I didn't expect that the file system gets overwritten. Some cases flashing to another firmware kicks you into a bootloop due to ext4 previously there, but there are times when the firmware boots which got me in wtf is happening kind of scenario.
When I used cranium or any custom ROM usually does Ext4 by default, but upon flashing XXKPN on top of it, it worked? Which isn't supposed to, So what I'm confused is, What is responsible for the rfs file format, the pit? or the firmware? , and does clearing cache partition reset to rfs?
Because flashing XXKPH->XXKPN->XXKPH without use of pit works and this is without CFRoot
Yes for what this pit file for ? Means for what partition.is it convert file system to rfs ?
Does anyone know how to change the file system formatting from Ext4 back to Rfs somewhat like the ext4 formatter? This would be helpful when flashing from ext4 nandroid backups to stock Rfs nandroid backups. So far this has been unsuccessful for me.
Sent from my SCH-I510 using XDA App
The voodoo control app will turn it off. Then you need to reboot to make the changes.
emtee_skull said:
The voodoo control app will turn it off. Then you need to reboot to make the changes.
Click to expand...
Click to collapse
That will only work if you are using a Voodoo kernel. I can find the needed commands to format everything to rfs for you then and create a CWM zip that will do it for you (or modify one if I can find it) so you can go back to RFS. However, CWM should format partitions before restoring.
I have always used the charge.pit file with repartition checked and ee4 to convert back to rfs via odin. I have also been told this charge.pit works with gb as well...
Try this. It's similar to the ext4 formatting package but should convert everything back to RFS for you. However, it is untested, so it may not work. I think I have it all setup properly, but I'm not completely sure.
Sweet bro., Thanks, I will try this; not sure why but when I try to go from Humble 5.2 or say your newest Infinity Rom back to the either leaked EP4D or the stock ota rooted EP4D, it gives me an error in CWM saying that the file system isn't RFS. All of the other ROMS are ext4. Something else that was interesting was I tried to format the OTA with the ext4 all formatter and it bricked my phone. Nothing worked except the charge pit and EE4 odin. I will give this a shot and tell you the results. thanks for the speedy answers. (BTW- I donwloaded some of the software to compare and contrast ROM's in Kdiff and it always gives me a Runtime error and force closes.I am trying this on xDark 4.3 tweaked so this might the issue, but any thoughts on this is appreciated.)
EDIT: I tried the rfs-all-formatter and it said it worked, but when I tried to restore the nandroid for EP4D stock rooted, it gives me this error:
format_rfs_device failed on /dev/block/st110
system won't mount either.
I then used the ext4 formatter and can restore Infinity or Humble no problem.
Is there any way i can change the file system to EXT-4 so that i can get the clockwork mod or can i do something else?
Now mine is RFS file system....
Tried installing some custom roms still my fs is RFS only
Can't able to install CYANOGEN MOD It stuck on the boot screen for approx 1 and half hour which is a black screen written "android" on it. bcoz of RFS file system i think
I JUST WANT THE CYANOGEN MOD.
PLEASE HELP ME OUT Is thr any other method for converting RFS to EXT 4 file system
1st save any cm roms on the root of your sd card...
Flash cwm by tj_style
wipe data, wipe cache
flash the cm rom of your choice
wipe data, wipe cache..reboot...
Try switching on without sim card...
- Via xda premium
format system and flash cwm by wiping dalvik too.....
and dont go deep into rfs fs you cant change it ext4 on stock rom....and rfs in noway is involved in installing other roms and bootloops...
Welcome everyone to my second thread (i'm not expert in threads ),
As usually, you may do it, but please consider you do it "at your own risk",
even if it doesn't brick your phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This thread is about repairing a broken RFS /system and /data partition.
As seen there i'm sure someone here had this problem on a Galaxy Young,
http://forum.xda-developers.com/showthread.php?p=11868531
I found a solution when i tought i have an empty userdata.img image (i formatted /data and made a cat /dev/stl11)
I tested if i may repair my broken RFS partition, which was broken by a Online Nandroid Backup (My CWM backups never broke /system)
I renamed userdata.img to system.img, i opened cygwin and made a .tar.md5 package, flashed it, YEAH!,
problem fixed without downloading 100MB of stock ROM package.
After that history, i finally created the "Unbricker" package, which rewrites /system and /data
(not cache, cache cannot be integrated in an Odin package)
I flashed it and re-formatted corectly using CWM /data and /cache, wiped and reinstalled my ROM.
Hope it will help you, the download link for : http://d-h.st/tnu :good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thanks i got this but i didnt know how to repair i only knew that i can unbrick by odin.
sent from my GT-P1000 using XDA Premium
hamada3381 said:
Thanks i got this but i didnt know how to repair i only knew that i can unbrick by odin.
sent from my GT-P1000 using XDA Premium
Click to expand...
Click to collapse
Hi, i just discovered after your reply it sharps /system partition, i updated link for /data, you may if you used it flash stock ROM,
then restore your nandroid backup using a different version of ClockWorkMod than one by BroadcomCM (this CWM print error formatting /system etc.. hope it will get fixed :good
I'm making an aroma package, will be called 'sharped repair'
Hello all. As per the title, I find that my i9003 cannot be converted to Ext4.
I am on DDLF2, and I used the Ext4 converter script once, then it soft-bricked my device. After flashing DDLF2 again and restoring from my backup, I tried it again - this time using the CF-Root's bundled Ext4 Manager, and its automated RFS to Ext4 conversion. I did it, but I opened it again and the internal flash is still RFS.
Can anyone help?
Requiem- said:
Hello all. As per the title, I find that my i9003 cannot be converted to Ext4.
I am on DDLF2, and I used the Ext4 converter script once, then it soft-bricked my device. After flashing DDLF2 again and restoring from my backup, I tried it again - this time using the CF-Root's bundled Ext4 Manager, and its automated RFS to Ext4 conversion. I did it, but I opened it again and the internal flash is still RFS.
Can anyone help?
Click to expand...
Click to collapse
If you're on FULL DDLF2 Custom Rom there is na application that will do this job for you.
Its simple. Just select the option you need, restart and you're good to go.