As the title states, my SD currently runs an EXT4 partition, however after reading around on these forums not all roms support EXT4 yet and most want EXT3 in order to work properly.. Upgrading EXT is easy im using RA Recovery Image, however how do you go from an EXT4 back to an EXT3?
I would think you'd have to repartition the card, well thats how I went about it.
It's tricky. usually, once you upgrade to ext4 you can't go back to ext3 without repartitioning.. but there's a work around...
you can turn off the ext4 "features" from a ext4 partition and mount it as ext3....
"mount -t ext4 /dev/yourpartition /mnt"
that would be the basic command. Needs to be rewritten for your particular situation.
You're better off just repartitioning lol.
Hi All!
I just made my first custom ROM:
It based on stock 2.2 JPF: only modification is rooting and converting to ext2 data system and cache partitions.
Flash it after flashing full stock JPF (My ROM don't contain bootloader, modem etc, so you must first flash stock JPF)
DON'T wipe after reboot, it will format you data and cache partitions back to RFS. I don't changed recovery binary, so please don't wipe if you want ext
ROM works OK for both rfs and ext2, so it will work, but no point to use my ROM with rfs
Any feedback is appreciated.
Update:
My JPM ROM converted to ext4
Stock firmware, only changes are rooted, busybox, fugutweak, (removed Layar and thinkfree for space, ext4 left less space for users ;( )
quadrant score is 470
Used apollo5801 kernel with modified initramfs to allow ext4 ext2 and rfs FS on all partitions, it use possibility to have data2sd
As for me, use ext4 for /system is has no much sense. Better use ext2 for /system and /cache, wile using ext4 for /data
/system normally is R/O, /cache has no vital information, so it better to use it with ext2 for performance
URL for ROMs:
My JPF ext2 ROM: http://www.multiupload.com/KQBT92RM0U
My JPM ext4 ROM: sorry, link removed, it has issue with WIFi
Interested in it. Give a detailed list of steps, please.
mumbozver said:
Hi All!
I just made my first custom ROM: sorry, I have no posts yet, and can't attach
It based on stock 2.2 JPF: only modification is rooting and converting to ext2 data system and cache partitions.
Flash it after flashing full stock JPF (My ROM don't contain bootloader, modem etc, so you must first flash stock JPF)
DON'T wipe after reboot, it will format you data and cache partitions back to RFS. I don't changed recovery binary, so please don't wipe if you want ext
ROM works OK for both rfs and ext2, so it will work, but no point to use my ROM with rfs
Any feedback is appreciated.
Click to expand...
Click to collapse
Hello,
I am interested in your ext2 ROM.
It's not quite clear for me how to flash it. I mean this: "DON'T wipe after reboot". Do you mean I should not do a factory reset? What about factory reset right after flashing stock JPF?
Would you write a detailed list of steps?
Thank you.
szabof1 said:
Would you write a detailed list of steps?
Click to expand...
Click to collapse
My ROM is kind of POC, it's not customized or so, main goal is try ext2 instead of rfs
1 - Flash stock JPF firmware.
2. - After flashing stock JPF you may do "wipe data/factory reset", or don't do factory reset.
3. - Flash my ROM.
4. - After reboot don't do "wipe data/factory reset" or "wipe cache partition", just choose "reboot system now"
If you do all right, you will get system data and cache partitions in ext2, only efs partition will stay in rfs.
mumbozver said:
Hi All!
I just made my first custom ROM: sorry, I have no posts yet, and can't attach
It based on stock 2.2 JPF: only modification is rooting and converting to ext2 data system and cache partitions.
Flash it after flashing full stock JPF (My ROM don't contain bootloader, modem etc, so you must first flash stock JPF)
DON'T wipe after reboot, it will format you data and cache partitions back to RFS. I don't changed recovery binary, so please don't wipe if you want ext
ROM works OK for both rfs and ext2, so it will work, but no point to use my ROM with rfs
Any feedback is appreciated.
Click to expand...
Click to collapse
hello. you converted the partitions /system /data and /cache to .ext2.
With a factory reset, the partitions will be converted back to .rfs?
kyrillos13 said:
hello. you converted the partitions /system /data and /cache to .ext2.
With a factory reset, the partitions will be converted back to .rfs?
Click to expand...
Click to collapse
Hello
system partition in any case will stay in ext2
"wipe data/factory reset' will reformat data and cache partition to rfs
"wipe cache partition" will reformat cache partition to rfs
Because of this don't do factory reset if you want test ext2 for data or cache partitions
P.S. looks like we need tweaked/custom recovery, if you know any - send me a link, pls
does it is working
I flashed your ROM
Hello,
I flashed your ext2 ROM just now.
Everything seems to be OK.
mount shows:
"/dev/block/stl6 /system ext2 rw,relatime,errors=continue 0 0
/dev/block/stl7 /data ext2 rw,nosuid,nodev,relatime,errors=continue 0 0
/dev/block/stl8 /cache ext2 rw,nosuid,nodev,relatime,errors=continue 0 0"
It is rooted and has busybox installed by default! Thanks.
Stock JPF upgraded by your ext2 ROM still workes well.
I also use Link2SD with 2nd (ext2) SD card partition for selected programs.
Is ext3 file system supported on SG3?
If yes, is it possible to convert /system, /data and /cache partitions to ext3 instead of ext2?
szabof1 said:
Is ext3 file system supported on SG3?
If yes, is it possible to convert /system, /data and /cache partitions to ext3 instead of ext2?
Click to expand...
Click to collapse
it isnt possible. When sammy release froyo kernel sources we will convert the partitions to ext4...
I do not know ext4. Why is ext4 better than rfs? What is the performance difference between ext2, ext4 and rfs?
szabof1 said:
I do not know ext4. Why is ext4 better than rfs? What is the performance difference between ext2, ext4 and rfs?
Click to expand...
Click to collapse
From my ext2 ROM: overall performance index by Quadrant increased from 325 to 520 after converting from rfs to ext2
ext4 is must be faster than ext2, but it uses more CPU, so need to get real user experience.
hi mumbozver,
what do you think about deodexing? does it make sence make ROM deodexed if this ROM is converted to ext2? i have heard some thoughts deodexed rom is not faster than non-deodexed... the higher performance is reached by ext2, not deodexing. is it true?
anly11 said:
hi mumbozver,
what do you think about deodexing? does it make sence make ROM deodexed if this ROM is converted to ext2? i have heard some thoughts deodexed rom is not faster than non-deodexed... the higher performance is reached by ext2, not deodexing. is it true?
Click to expand...
Click to collapse
Deodexing is increase first boot time after flashing and decrease available space in /data partition, but increase space in /system (you will get half of space, that you are wasting in /data. In deodexed ROM you need to store odexed "classes.dex" in /data/dalvik-cache and zipped deodexed "classes.dex: inside *.apk or *.jar files on /system).
So you will get lesser overall free space in you phone and slower first boot. Thats all about deodexing performance.
Main reason to get deodexed ROM is ability to change themes, and possibly put in /system some program of user choice, so programs will survive factory reset. But in my ROM factory reset will convert /data and /cache partitions back to rfs, so deodexing in my point is not needed.
i have flashed your rom, everything seems to be ok. quadrant score: over 500
mumbozver said:
Deodexing is increase first boot time after flashing and decrease available space in /data partition, but increase space in /system (you will get half of space, that you are wasting in /data. In deodexed ROM you need to store odexed "classes.dex" in /data/dalvik-cache and zipped deodexed "classes.dex: inside *.apk or *.jar files on /system).
So you will get lesser overall free space in you phone and slower first boot. Thats all about deodexing performance.
Main reason to get deodexed ROM is ability to change themes, and possibly put in /system some program of user choice, so programs will survive factory reset. But in my ROM factory reset will convert /data and /cache partitions back to rfs, so deodexing in my point is not needed.
Click to expand...
Click to collapse
Thanks for the ROM.... Just a question of how long the battery lasts...? Is it over a day...
Vishnu N S said:
Thanks for the ROM.... Just a question of how long the battery lasts...? Is it over a day...
Click to expand...
Click to collapse
It depend of usage pattern.
I use it lightly, just few minutes of call per day, but always on Wi-Fi or 3G connection, skype chats and email checks.
After Gallery3d removal it run something about 2 days.
mumbozver
I don't understand.
Yesterday was your explanation about deodexing.
Now i can't see this one
Why?
Is this a "postmoderating"?
Add.
Sorry.
It's very strange. I see it again!
kyrillos13 said:
it isnt possible. When sammy release froyo kernel sources we will convert the partitions to ext4...
Click to expand...
Click to collapse
Now we have sources
I did quick test for ext4 enabled kernel from here: http://forum.xda-developers.com/showthread.php?t=978823
Just flashed zImage to my ROM. everything looks OK for now, so I will make ext4 ROM in few days, probably based on JPL.
I use a Galaxy 3 I5801, with DDJP2 stock and rooted.
I tried to apply kyrillos' new Honeycomb theme by flashing the zip file provided in the v5.0_Extra_package by renaming the file Honeycomb_theme-signed.zip to update.zip, and putting it in the sd card root folder.
But, in recovery mode, if i select SDCARD:update.zip option, it says :
E: can't mount /dev/block/mmcblk0
E: Can't mount SDCARD:update.zip
Any solution to this?
Note: I was using kyrillos rom v4.1 oc before this, and I had used Madteam app2sd to partition my 16GB sd card, with 1GB app2sd space.
Would that be causing this problem?
krishna_bhargav said:
I use a Galaxy 3 I5801, with DDJP2 stock and rooted.
I tried to apply kyrillos' new Honeycomb theme by flashing the zip file provided in the v5.0_Extra_package by renaming the file Honeycomb_theme-signed.zip to update.zip, and putting it in the sd card root folder.
But, in recovery mode, if i select SDCARD:update.zip option, it says :
E: can't mount /dev/block/mmcblk0
E: Can't mount SDCARD:update.zip
Any solution to this?
Note: I was using kyrillos rom v4.1 oc before this, and I had used Madteam app2sd to partition my 16GB sd card, with 1GB app2sd space.
Would that be causing this problem?
Click to expand...
Click to collapse
You need CWM recovery to flash update.zip files .. DDJP2 has stock samsung recovery .. Flash any of the custom roms with cwm and you will be able to flash update.zip .. If you don't wasn't to flash a custom rim ask mumbozver for his cwm installer and run it for your phone...
thanks for the reply!
oh and one more thing, how do i get back the 1GB partition I made using Madteam app2sd while using kyrillos rom? or can it still be made usable in the stock rom?
krishna_bhargav said:
thanks for the reply!
oh and one more thing, how do i get back the 1GB partition I made using Madteam app2sd while using kyrillos rom? or can it still be made usable in the stock rom?
Click to expand...
Click to collapse
It can be made usable...flash any fugumod 2.4 kernel...then use lestatious Data2Sd...that shuld do the trick...
i just flashed fugumod 2.4 beta3!
ran mount in terminal emulator (after su ofcourse), i see that all partitions (data,cache,system,efs...) are rfs file system..
what partitions do i need to convert to ext2 or ext4?
and how do i see and use my 1GB partition mentioned above?
thanks in advance!
krishna_bhargav said:
i just flashed fugumod 2.4 beta3!
ran mount in terminal emulator (after su ofcourse), i see that all partitions (data,cache,system,efs...) are rfs file system..
what partitions do i need to convert to ext2 or ext4?
and how do i see and use my 1GB partition mentioned above?
thanks in advance!
Click to expand...
Click to collapse
Convert system and cache to ext2...and data to ext4...then use data2sd enabler of lestatious..and reenable data2sd
I converted the partitions data ext4 and system and cache to ext2!
But when i use EASS partition manager, i cannot see the swap and data2sd partitions at all.. It just shows a single FAT32 partition of 13.04 gigs!
And when i used data2sd enabler, and tried to reenable data2sd, it says path not found!
Hi,
I recently made the jump to CM7.1 KANG Oct24th, with ClockworkMod 5.0.2.0. All seems to be working very well.
But then I tried to do a ClockworkMod backup, just like I've always done. It worked through all the partitions, until sd-ext. I then get the following error:
"Could not mount sd-ext. sd-ext backup may not be supported on this device. Skipping backup of sd-ext" followed by the usual "Generating md5 sum..."
On another forum there was a mention that this error is normal. Does everyone get this error?
I think I created the SDCard partitions using ClockworkMod, so I have a 1024MB Ext4. It is my understanding that Ext4 is supported. It must be, as (I think) I used Clockwork to create the partition. I'm not certain about that, as I was also experimenting with GParted to create partitions. But had the same problem.
I am using Link2SD to move some apps to sd-card, so without sd-ext partition, the backup is incomplete!
Anyone seen this? Any ideas what might be wrong? Or how to fix it?
Thanks.
clockworkmod doesn't support ext4 on the blade. ext3 works.
Hate to resurrect an old thread but is this still the case I'm having the same problem?
Looks like I'm going back to 4EXT. After installing the latest touch version of Clockwork mod I got this message also during backup. This is fine if you have no problems on your next ROM but what if you have problem with the next ROM you chose. Doing a full wipe will include reformating EXT4 partition. That means since Clockwork mod didn't backup your EXT4 you have no way of getting all the files you want from your previous ROM. I also thought of changing my partition from EXT4 to EXT3 but besides the fact that I will have to move all my files to my PC then transfer again I read somewhere that EXT3 is not as efficient as EXT4.
xrookie24 said:
Looks like I'm going back to 4EXT. After installing the latest touch version of Clockwork mod I got this message also during backup. This is fine if you have no problems on your next ROM but what if you have problem with the next ROM you chose. Doing a full wipe will include reformating EXT4 partition. That means since Clockwork mod didn't backup your EXT4 you have no way of getting all the files you want from your previous ROM. I also thought of changing my partition from EXT4 to EXT3 but besides the fact that I will have to move all my files to my PC then transfer again I read somewhere that EXT3 is not as efficient as EXT4.
Click to expand...
Click to collapse
My version of CWM touch (the only one touch version there is afaik) does support ext4, both 6.0.1.1 stable and 6.0.1.2 experimental.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1835279
You might have been using my older testing version which had a problem with some ext4 partitions (notably ext4 partitions with special attributes).
Jinxxed said:
My version of CWM touch (the only one touch version there is afaik) does support ext4, both 6.0.1.1 stable and 6.0.1.2 experimental.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1835279
You might have been using my older testing version which had a problem with some ext4 partitions (notably ext4 partitions with special attributes).
Click to expand...
Click to collapse
Sorry I didn't notice the device name. I'm using HTC Desire. My latest version of HTC Desire doesn't support EXT4 anyways. It's Off-Topic here. NVM. Thanks.