I've been playing around with the CM-mod/S7 and can sucessfully make it boot with all ext4 partitions.
Backround information:
Parititions and formatting
Partitions are the basic unit of storage on my devices with storage (think C: D: E: if you use windows)
The standard layout of android devices:
A /cache partition
A /data partition
A /system partition
Other hidden partitions (this part isnt relevent to us)
The common filesystem formats for recent android devices are EXT 3 and 4 (4 being the newer obviously)
The S7's default partitions:
stock 3xx: (ie froyo)
/cache: ext3(?)
/data: ext3(?)
/system: ext2
stock 5xx: (ie honeycomb)
/cache: ext3
/data: ext3
/system: ext4
my ext4 mod:
/cache: ext4
/data: ext4
/system: ext4
All other devices that launched with HC installed use all ext4 partitions.
But the S7 didnt launch with HC, it launched with froyo.
Dell couldnt upgrade /data to ext4 without wiping user data.
They could upgrade system, since they wipe it on install anyway.
Cache they didnt for the outside chance a user had actual important data in it.
My proposal
What I propose is a modified version of CM9-mod with /cache and /data formatted as ext4 partitions.
I've already got a working version, the main issue is that:
I dont know what the difference is. I've ran quadrant with ext4 and again with ext4, and there's very little difference.
Since quadrant has an I/O and database benchmark (and they run on /data), at least it shows that there's only 1% change in scores.
Would anyone actually be interested in using an ext4 mod?
There are some downsides (depending on how you view it):
ext3 and ext4 nandroids arnt compatable
You will need to do a fac reset on first install (as it reformats)
You will need seperate versions of CM9-mod and CWM
This space for rent
A simple modification of the boot.img to change init.streak7.rc mount points to ext4, easy as pie.
Yea that's what I did, along with a CWM recovery.fstab mod.
But like I said I havnt really noticed any changes in quad, and it's using /data for it's tests
As soon as I get wifi up and working on cm10, going to see if there is any benefit to switching
Sent from my Nexus 7 using Tapatalk 2
I can test it tomorrow.
Sent from my PG86100 using xda app-developers app
Related
As of last night I'm running CF Root 3 JVK on Gingerbread 2.3.3.
When I tried using the ext4 App to convert the file systems to ext4, it was successful for:
/dbdata
/data and
/cache
However for /system, it says:
Code:
Using: internal sdcard
Converting /system
- Backing up files ...
- Creating ext4 filesystem ...
- Restoring files ...
- Restore failed ! Not enough space ?
- Performing rollback ...
- Creating rfs filesystem ...
- Restoring files...
- Rollback success!
I cleared up some space on my phone and now I have 1.87GB available space on the sd card, and 13.26GB Available space on the USB storage.
and 1.75GB Available Space on System storage.
However I still can't convert /system to ext4.
Any ideas why this might be the case?
You need to free some space on /system to be able to successfully convert it to ext4. Apparently, ext4 needs some extra space for the conversion.
This is explained in the CF-Root main post, or in the CF-3.0 release information.
Okay thanks for that!
All the answers were in the original thread. I was just searching for the wrong terms.
I eventually downloaded Super Manager, activated its root mode and deleted the Aldiko eBook app from /system/app
That freed up enough space to convert /system to the ext4 filesystem!
mercifulhop said:
Okay thanks for that!
All the answers were in the original thread. I was just searching for the wrong terms.
I eventually downloaded Super Manager, activated its root mode and deleted the Aldiko eBook app from /system/app
That freed up enough space to convert /system to the ext4 filesystem!
Click to expand...
Click to collapse
you're right.
that works.
greetings
andcooper
mercifulhop said:
As of last night I'm running CF Root 3 JVK on Gingerbread 2.3.3.
When I tried using the ext4 App to convert the file systems to ext4, it was successful for:
/dbdata
/data and
/cache
However for /system, it says:
Code:
Using: internal sdcard
Converting /system
- Backing up files ...
- Creating ext4 filesystem ...
- Restoring files ...
- Restore failed ! Not enough space ?
- Performing rollback ...
- Creating rfs filesystem ...
- Restoring files...
- Rollback success!
I cleared up some space on my phone and now I have 1.87GB available space on the sd card, and 13.26GB Available space on the USB storage.
and 1.75GB Available Space on System storage.
However I still can't convert /system to ext4.
Any ideas why this might be the case?
Click to expand...
Click to collapse
Tell me pls where can i find the ext4 tool, for download.
kunacs said:
Tell me pls where can i find the ext4 tool, for download.
Click to expand...
Click to collapse
It is attached on the first page of the CF-Root thread.
I want to check if my data and system partitions are ext3 or ext4. Is there a way to do this ?
Easy, just use a terminal/ADB to run the command 'mount'
cheers for that. it seems that if you run the backtoext3 script and then do a nand restore it converts your data back/system to ext4 .
Correct, it's smart like that.
Thanks, was wondering the same thing. I can see that my data and system are ext4 but cache is ext3. Is that ok, shouldn't they all be the same partition?
Sent from my LG-P990 using XDA App
I think I did it correctly, got a lot of text, like 2 screens there was 4 that found ext3 in, /system, /cache, /data, /lgdrm. So I guess the cm7 rc1 im running is using ext3 then? Why isnt cm7 using ext4?
Sent from my Optimus 2X using XDA Premium App
Because once you go EXT4, the only way back to EXT3 involves your data going bye-bye. I believe it was almost done, but RC changed his mind.
was a way to extract files from a nand back so I could push them to my device
Mount the .img on a Linux machine.
Hi all... Here there're many dev so maybe i'm so lucky to find someone that can help me....
I'm going to convert my phone's partition to ext4 but i have problem with /data. This because the phone has 4 gb of internal memory that Samsung push under /dev/block/mmcblk0. This memory is partitioned in three part /dev/block/mmcblkop1 (internal SD) /dev/block/mmcblkop3 (/data) and /dev/block/mmcblk0p2 (empty).
How can i format /data into ext4? I tryed different way but the phone doesn't boot. What is the correct way to make it?
My Phone (GT-I9003)
UPDATE: recovery can mount it without issue.... init.rc not.... why???
I've got an i9000M from Bell with a dead internal SD. I managed to get CM7 to boot on the device even though Samsung and Samsung based roms will just simply loop. JPY, JL2, JVQ all loop at the GT-i9000 screen.
My phone can fully boot to ADW and even make phone calls. However, settings are not saved and text messages are rejected because there is no space on the device.
I edited vold.fstab and fstab so that the first partition of my SD mounts to /sdcard instead of /emmc. (One problem cleared)
The second partition of the card is formatted as ext4 and that's what I'm trying to mount to /data. My problem, I edited the fstab to mount mmcblk0p2 (the ext4 partition) to /data, but won't automatically during bootup. If I try to mount manually via ADB, the device loops at the CM7 animation
Here is my fstab:
Code:
/dev/block/mtdblock3 /cache yaffs2 rw
/dev/block/mmcblk0p2 /data ext4 rw
/dev/block/mtdblock6 /datadata yaffs2 rw
/dev/block/mtdblock2 /system yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
P.S. My card is a SanDisk 8GB class 6. 7GB for /sdcard; 1GB for /data.
I have the same problem with my old phone, i can boot using custom kernel like ultimate kernel (froyo) and stock rom.
Still no luck replacing damaged data partition
Sent from my GT-I9100 using XDA App
Finally found a way. I recompiled cm 7 and altered data & sdcard refs to external sdcard.
The phone works ok with class 10 card.
Sent from my Xperia Ray using XDA Premium 4 mobile app
Hello,
I'm quite new in android development, so sorry for dumb question.
I have new GT-S6102 (because of dualsim setup) and I'd be quite happy with the stock firmware (S6102XXMA2) if it wasn't of the 160M memory. What I'm trying to do is to modify init.rc in bootimage to mount /data on 4G second partition of my SDCard instead of 160M /dev/stl11.
I'm using a Ubuntu 12.04 machine for my experiments.
I've copied /dev/block/bml7 from my phone using ADB, extracted it using abootimg.
First (and I hope that main) trouble is that when I try to update the boot.img (abootimg -u boot.img -r initrd.img), even without modifying the ramdisk, the resulting image has few different bytes near the beginning of the file. Anyway when I flashed it back to phone, it booted normally.
Then I unpacked the ramdisk (using steps from here) and modified init.rc:
Code:
mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
# mount rfs /dev/stl11 /data nosuid nodev crypt check=no
I have a 32G uSD card with 28G FAT and 4G EXT4 primary partitions.
Then I've repacked it, made new boot.img, flashed with ODIN and it made a nice bootloop with Samsung bootanimation without usual sound.
What am I doing wrong?
Is this modification even possible?
Thanks for advice
P.S.
I've tried to extract the boot.img from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, but 7zip on Windows and TAR on linux complain that it isn't valid archive.
jelinek.01 said:
Hello,
I'm quite new in android development, so sorry for dumb question.
I have new GT-S6102 (because of dualsim setup) and I'd be quite happy with the stock firmware (S6102XXMA2) if it wasn't of the 160M memory. What I'm trying to do is to modify init.rc in bootimage to mount /data on 4G second partition of my SDCard instead of 160M /dev/stl11.
I'm using a Ubuntu 12.04 machine for my experiments.
I've copied /dev/block/bml7 from my phone using ADB, extracted it using abootimg.
First (and I hope that main) trouble is that when I try to update the boot.img (abootimg -u boot.img -r initrd.img), even without modifying the ramdisk, the resulting image has few different bytes near the beginning of the file. Anyway when I flashed it back to phone, it booted normally.
Then I unpacked the ramdisk (using steps from here) and modified init.rc:
Code:
mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev crypt check=no
# mount rfs /dev/stl11 /data nosuid nodev crypt check=no
I have a 32G uSD card with 28G FAT and 4G EXT4 primary partitions.
Then I've repacked it, made new boot.img, flashed with ODIN and it made a nice bootloop with Samsung bootanimation without usual sound.
What am I doing wrong?
Is this modification even possible?
Thanks for advice
P.S.
I've tried to extract the boot.img from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, but 7zip on Windows and TAR on linux complain that it isn't valid archive.
Click to expand...
Click to collapse
OK, so it seems that I´ve managed to work it out at last.
The unpacking and repacking of bootimage was all right, trouble was in updating only the init.rc and probably using ext4. What I have done:
I replaced all mentions of mounting /dev/stl11 on /data by mounting /dev/block/mmcblk0p2 (that was in files fota.rc, init.rc, init.charge.rc, res/recovery.fstab). In res/recovery.fstab I also changed formatting type from rfs16 to rfs32 so it supports my 4.5G partition.
Then I flashed the bootimg in my phone and formatted the data partition in recovery (that was the only way to make it rfs I've found).
Maybe it would all work with changing the format and mount type to ext4, but I hoped for as little modification as possible.
Now it reports 4.25GB free space after all my apps are installed, hurray .
I have just to remember to never boot it up without SDcard inserted. Maybe it would work as a possibility to borrow the phone to somebody with another card.
The boot.img came from S6102XXMA3_S6102DBTMA1_S6102XXMA2_HOME.tar.md5, if someone wants to try it, it is here . It probably wouldn't touch the original /data partition, so it might be possible to try it and undo it by flashing original boot.img. It just requires to have a second primary partition on SDcard and formatting it in recovery before first boot.
i didnt know to do that boot "compiling" like u did, quite good for you, im using cronmod int2ext , i have 850mb internal. i use 'pimp my rom' to get init.d support.