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 ?
Related
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.
My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
realcode said:
My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
Click to expand...
Click to collapse
Dont restore the backup of one firmware over another firmware.
Flash xxkpe twice aand over it flash xxkpq with factory reset after flashing each time. Use this guideforum.xda-developers.com/showthread.php?t=1133787
Sent from my GT-I9003
I tried to format the data, but it didn't work. I can see the previous installed application broken even I flashed with new ROM(Re-partion).
It seems something was locked by system.
Follow this guide to flash XXKPQ Check if everything works well. Try to restore your CWM backup
I tried to flash XXKPE/XXKPQ, but I got a wrong message "E: failed to mount /data (Invalid argument)" when the phone startup".
And the phone repeated to restart, I can't the normal phone.
It seems there is something wrong with the partion of /data.
Is there other way to fix it?
the /data is ext4, I am not sure XXKPQ support ext4 or not.
When flashing XXKPE with pit and all the other stuff you should see Re-Partition checked. Then everything should be formatted with the standard RFS filesystem unless you convert it. The stock Kernel doesn't support ext4, but that doesn't mean that you can't try to flash a Kernel that supports ext4.
Did you let the phone boot up completly after every flash?
I didn't let XXKPE boot up completely after flash.
It seems that the /data partion was not reset in flashing with the "Re-partion" selected.
I got error message when I tried to check the disk status.
/sbin # fsck.ext4 /dev/block/mmcblk0p3
fsck.ext4 /dev/block/mmcblk0p3
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p3: recovering journal
fsck.ext4: unable to set superblock flags on /dev/block/mmcblk0p3
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.
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.
//////////// USE IT AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY FAILURE OR BRICKED DEVICES /////////////////
THIS IS NOT a PUBLICITY for Any ROM or KERNEL
They are Simply just what i use
I have successfully changed my data partition to F2FS and using arter kernel as well
Also I have managed to get the Data back in place so after the whole operation all my ROM data are intact
NOTE THAT YOUR ROM & KERNEL MUST SUPPORT F2FS TO BE ABLE TO BOOT
Note that changing any partition filesystem from a type to another will require formatting that partition
From what i understood converting /system and /cache to f2fs is useless hence I converted /data only as it the main partition that you write on
First of all your internal storage is in /data/media/0 path and hence it will be wiped
I used the official TWRP to be sure of no issues
Take care of the 12th step as if it was missed you will start from scratch >> CRITICAL
Note that Fstab file already contains DFE so if you are unecrypted like my case flashing Fstab keeps me unencrypted without flashing DFE
Now let's start the operation of converstion of/data from ext4 to f2fs in a step by step guide
1- BOOT TO RECOVERY
2- TAKE A FULL NANDROID BACKUP ( MOST IMPORTANT IS THE DATA PARTITION )
3- TAKE A FULL CLONE OF YOUR INTERNAL STORAGE while you are in TWRP( To PC either via MTP or adb command and i prefer the adb method as it ensure that all your files are copied including hidden files )
4- WIPE > Format Data > Yes ( it is a factory reset and all your internal storage will be wiped )
5- Reboot to recovery again
6- Wipe > Advanced Wipe > Check Dalvik , cache , system and Data > Wipe and DONOT reboot to recovery
7- Connect cable again and copy the FSTAB Tools ZIP file only
9- Flash the FSTAB TOOLS File
9- Wipe > Advanced Wipe > Check Data ONLY > Repair or Change file system > F2FS > Change File system
10-Copy via cable whatever you need from your internal storage or the whole of it as your wish
11-Ensure that the TWRP Backup you took in step 2 is copied to internal storage again
12-GO TO TWRP SETTINGS and Tick the 3rd option in the first TAB ( it is called use rm -rf instead of formatting )
13-The above step ensured that when you restore Data partition TWRP won't format it again to ext4 and leave it as f2fs
14-Restore > Choose your fresh Backup > RESTORE DATA PARTITION ONLY ( you will see a message that you are restoring a backup taken of ext4 filesystem , donot worry it worked in my case )
15-Flash the following in order : Vendor > ROM > Fstab File ( NOT the tools one ) > Gapps > Arter97 kernel > Reboot
16-You should boot to the OS with all your data ( settings ) like they were intacted and now the /data partition is f2fs
17-Restore your internal storage if you still didnot do it in step # 10
18-Reboot to recovery and Flash Magisk ( optional )
Notes :
- I though that 4th step was useless however it is mandatory as it erases Vendor or something similar
- I though that 6th step is duplicate to 4th step and was useless however without it TWRP didnot change filesystem to F2FS
- The FSTAB must be flashed after every vendor update ( it can be before or after ROM in the sequence , the most important that it is after every Vendor BEFORE YOU BOOT )
- I didnot flash magisk in step # 15 as crCroid recommends that you boot to system one time before you flash magisk
- crDroid default kernel doesnot support f2fs and if i didnot flash arter97 i wouldnot be able to boot
- By this setup i cannot go back to crDroid default kernel anymore unless f2fs is supported by it
- If ROM doesnot support f2fs the system wouldnot Boot as it would not be able to understand the /data partition filesystem
- Ofcourse any Kernel and ROM combo that supports F2FS should be valid to apply this guide
Finally thanks for all the Devs for thier hard work and dedication , You all made our POCO a lovely BEAST
I think this thread is belong to guides&news and discussion forum
thanhnvt194 said:
I think this thread is belong to guides&news and discussion forum
Click to expand...
Click to collapse
Yes i you are right but do not know how to move thread from a forum to the other
Thanks @shouk_1987, good guide. Any chance you can provide a link to the FStab files mentioned in your post?
Is this arter kernel specific? I used shadow kernel and the fstab changes are flashed with the kernel
dgrasley said:
Thanks @shouk_1987, good guide. Any chance you can provide a link to the FStab files mentioned in your post?
Click to expand...
Click to collapse
They are in arter kernel thread in the OP
Thread moved to the correct section.
LTT
So, does this work with crDroid? I ask because both rom and kernel must apparently support f2fs and @gwolfu has indicated crDroid does not.
piet8stevens said:
So, does this work with crDroid? I ask because both rom and kernel must apparently support f2fs and @gwolfu has indicated crDroid does not.
Click to expand...
Click to collapse
crDroid Kernel doesnot for now
While the ROM does
What about my apps and its data, can I restore it back?
Edikuun said:
What about my apps and its data, can I restore it back?
Click to expand...
Click to collapse
Read the guide carefully
You will br able to restore everything but the most part that needs patience is restoring internal storage
works on miui ?
RubenPCA said:
works on miui ?
Click to expand...
Click to collapse
Didnot try but saw other users says it works
Which kernels/ROMs are supported?
Shished said:
Which kernels/ROMs are supported?
Click to expand...
Click to collapse
Read in the OP of the ROM / Kernel you want
A lot aupport f2fs now
a great guide . Any way to do the same(restore data) if ee wanna go back from f2fs to ext4? just in case.
Debraj903 said:
a great guide . Any way to do the same(restore data) if ee wanna go back from f2fs to ext4? just in case.
Click to expand...
Click to collapse
Didnot try but I believe it is the same concept
My internal storage went from 30GB free to 15GB free
Edikuun said:
My internal storage went from 30GB free to 15GB free
Click to expand...
Click to collapse
I am the opposite I have 2 gb increase
Least version for Poco is 64 gb , which version do u have ?
shouk_1987 said:
I am the opposite I have 2 gb increase
Least version for Poco is 64 gb , which version do u have ?
Click to expand...
Click to collapse
It's okay now, I forgot to delete my twrp backup and titanium backup. Anyways, nice guide! Successfully converted to f2fs