Develop Bugs

[(KERNEL)] A dumb question about EXT4

[(KERNEL)] A dumb question about EXT4
a)Flashed CWM Kernel + EXT4 tools app. Converted system to EXT4.
b)Flashed Speedmod Kernel K15H. Convert RFS to EXT4 via recovery
c)Flashed Talon Dev 0.2.2. Automatic Convert system partition to EXT4.
1)Are there various type of EXT4?
2)Do I need to convert system into EXT4 each time I flashed a kernel?
3)Why each kernel could not recognize the system already EXT4 converted?
How do I verify the system is in EXT4? CWM EXT4 tool could not recognize ETX4 if you flashed with others kernel.
Can someone explain? many thanks

1) Ext4 or Ext4nj (nj stands for non-journalized), using Ext4nj is only for non critical data.
2) No, the new Kernel must try to know if you're already in Ext4, if it doesn't, it's stupid.
3) use the "mount" command in a terminal or via adb, if you see Ext4 in line with /system, /data, etc. etc., you're under Ext4 Lagfix.

No, there is no different kind of ext4. If you flashed stock rom with odin between each kernel transition, know that this reformat the file system to RFS. Ususally, i use chainfire ext4 tool to know if my FS is in ext4. Also, you should not haveto worry about changing FS to ext4 again after changing as you only change the kernel and not the FS. Next time can you post your question in question & answer sub-forum plz.

.Slane. said:
1) Ext4 or Ext4nj (nj stands for non-journalized), using Ext4nj is only for non critical data.
2) No, the new Kernel must try to know if you're already in Ext4, if it doesn't, it's stupid.
3) use the "mount" command in a terminal or via adb, if you see Ext4 in line with /system, /data, etc. etc., you're under Ext4 Lagfix.
Click to expand...
Click to collapse
true that there is journalised and non-journalised, but both can be mount the same way and are seen the same way by the system.

.Slane. said:
1) Ext4 or Ext4nj (nj stands for non-journalized), using Ext4nj is only for non critical data.
2) No, the new Kernel must try to know if you're already in Ext4, if it doesn't, it's stupid.
3) use the "mount" command in a terminal or via adb, if you see Ext4 in line with /system, /data, etc. etc., you're under Ext4 Lagfix.
Click to expand...
Click to collapse
Thanks man. I would strongly agree that each kernel should try to reconize the EXT4. Somehow, this not the case.

chadouming said:
No, there is no different kind of ext4. If you flashed stock rom with odin between each kernel transition, know that this reformat the file system to RFS. Ususally, i use chainfire ext4 tool to know if my FS is in ext4. Also, you should not haveto worry about changing FS to ext4 again after changing as you only change the kernel and not the FS.
Click to expand...
Click to collapse
Hi. As i said. Once you flashed another kernel, chainfire ext4 would not able to identify wheather your system is in Ext4. I'm using custom rom not stock.

Just to add on, frequent converting from/to Ext4 would cause some app to be force close. You have to reinstall the apps. What the hack!

[Q] CWM 3.1.0.1 Help

Hey everyone. This is my first post. However, that's not why I'm here.
I'm trying to flash MIUI rom to my phone, but when I wipe data/factory reset, my phone displays:
E:format_volume: make_extf4fs failed on /dev/block/mmcb1k0p2
Formatting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
I don't know how to convert my phone to ext4..When I try to install zip from sdcard and press choose zip from sdcard, it says:
E:Can't mount /sdcard
Please help soon, I cant find how to convert my phone to ext4. Thanks in advance.
Edit:
--Now using Odin to go to stock.
Then going to re-root.
Afterwards going to make sure that the ext4rfs.zip is in my sd card, then go into first boot of cwm.
2nd edit:
Still DOESNT work

You can Odin in this EB13 prerooted with CWM 3.0.0.6 which upon first boot converts to EXT4 then you can flash your EXT4 compatible ROM afterwoods and also Odin in CWM 3.1.0.1 later. The 2nd link is the EXT4 one.
http://forum.xda-developers.com/showthread.php?t=853209

kennyglass123 said:
You can Odin in this EB13 prerooted with CWM 3.0.0.6 which upon first boot converts to EXT4 then you can flash your EXT4 compatible ROM afterwoods and also Odin in CWM 3.1.0.1 later. The 2nd link is the EXT4 one.
http://forum.xda-developers.com/showthread.php?t=853209
Click to expand...
Click to collapse
Thanks but when I do that, it says can't mount /sdcard in cwm 3.0.0.6...
:/

Note: Tried 3 different SD cards and still doesn't work.. I just want this MIUI ROM to work!!
(Only reason I wanted to root)
2nd Note: I can use cwm 3.0.0.6 but I cant fully wipe data because I get an error(forgot it)
However, I did install MIUI Rom but got errors since its 3.0.0.6 and not the latest version or ACS recovery.. Helpppp :/

[Q] ext4 on rooted stock 2.3.3 and unity kernel?

Hi!
I have now this setup:
1. 4EXT 2.2.7 RC5
2. Rooted sock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1169004 (exactly this link was used: http://www.multiupload.com/RZSJELJ5MR)
3. Unity V8 kernel with ext4 support (great kernel, by the way! )
I want to go to ext4 partitions for my system, data and cache.
I tryed this:
1. Boot to 4EXT.
2. Backup all my partitions (tar, ext3).
3. Convert my backup to ext4 with "EXT3 - 4EXT - EXT4" menu item.
4. WIPE all my partitions to ext4.
5. Restore backup.
6. Verify that all my partitions are still ext4 type -- OK.
7. Reboot.
After that system stops booting with white screen & HTC logo.
Then I can reboot to 4EXT, convert backup back to ext3 and restore it. After this system will boot.
I think, by some reason system can't mount /system partition. I've check in /proc/config.gz that kernel have ext4 support (no module, compiled into kernel).
And I think that the reason may be wrong kernel boot parameters line or wrong init script (for ext4 case, i mean). I can't find any /etc/fstab... and I don't know how does it mount filesystems (where to check parameters)?
So, the question is: what else should I change in my system to boot from ext4 partitions? I don't want to switch to custom ROMs.

I'm not sure why you need to wipe anything at all... I converted my partitions from ext 3 to 4 and all my data was preserved. Also my understanding was that if you've converted to ext 4 and then you restore a backup made with ext 3 your partitions would revert back... unless something has changed and I'm not aware of it...
Sent from my HTC Vision using XDA App

Ditamae said:
Also my understanding was that if you've converted to ext 4 and then you restore a backup made with ext 3 your partitions would revert back... unless something has changed and I'm not aware of it...
Click to expand...
Click to collapse
This is true for ClockWorkMod. But I'm using 4EXT Recovery. It's "killing feature" is that it serve backups and partition types in the right way.

.bva said:
This is true for ClockWorkMod. But I'm using 4EXT Recovery. It's "killing feature" is that it serve backups and partition types in the right way.
Click to expand...
Click to collapse
You do know its based of cwm right?
Sent from my HTC Vision using XDA Premium App

I was also talking about 4EXT Recovery... not CWM. Why don't you ask Madmaxx82 in his thread?
Sent from my HTC Vision using XDA App

I am a new user and as i have less then 10 messages, i can not post to developer's forums. That is why...

.bva said:
Hi!
I have now this setup:
1. 4EXT 2.2.7 RC5
2. Rooted sock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1169004 (exactly this link was used: http://www.multiupload.com/RZSJELJ5MR)
3. Unity V8 kernel with ext4 support (great kernel, by the way! )
I want to go to ext4 partitions for my system, data and cache.
I tryed this:
1. Boot to 4EXT.
2. Backup all my partitions (tar, ext3).
3. Convert my backup to ext4 with "EXT3 - 4EXT - EXT4" menu item.
4. WIPE all my partitions to ext4.
5. Restore backup.
6. Verify that all my partitions are still ext4 type -- OK.
7. Reboot.
After that system stops booting with white screen & HTC logo.
Then I can reboot to 4EXT, convert backup back to ext3 and restore it. After this system will boot.
I think, by some reason system can't mount /system partition. I've check in /proc/config.gz that kernel have ext4 support (no module, compiled into kernel).
And I think that the reason may be wrong kernel boot parameters line or wrong init script (for ext4 case, i mean). I can't find any /etc/fstab... and I don't know how does it mount filesystems (where to check parameters)?
So, the question is: what else should I change in my system to boot from ext4 partitions? I don't want to switch to custom ROMs.
Click to expand...
Click to collapse
Not all ROMs support ext4 partitions; I'd assume, since the stock ROM came as ext3 and wasn't "supposed" to be rooted that it only supports ext3.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
Not all ROMs support ext4 partitions; I'd assume, since the stock ROM came as ext3 and wasn't "supposed" to be rooted that it only supports ext3.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I didn't think of that... I bet you're 100% right.

Ditamae said:
I didn't think of that... I bet you're 100% right.
Click to expand...
Click to collapse
For mounting any partition with some spacific FS type, we need only kernel module (or support build into kernel) and right mount parameters passed to init.
So, any ROM can be modified for this, i think...

[Q] how to WORK/enable/use ext4 in MERRUK kernel

anyone help is appreciated,, thnx in advance,,

kawe42 said:
Preparation
(1) Backup all apps with Titanium Backup
(2) Backup sdcard to the pc
(3) Fullwipe
(4) Flash stock rom to get rid of all possible points of failure
(5) copy Madteam cwm to sdcard
(6) start stock recovery -> start cwm via update.zip
(7) partition sdcard with cwm -> ends up with sdcard fat32 partition and 1024MB ext3 partition (as I chose)
(8) copy sdcard backup from pc to fat32 partition, including merruks 2.0 kernel
(9) flash merruk 2.0 via cwm
Setup
(10) boot up phone, initial setup, install link2d
(11) choose link2sd mount script ext3
(12) after reboot there is a link2sd script in /etc/init.d
(13) modify script: add 2 lines at the end of the script:
rm -r /sd-ext
ln -s /data/sdext2 /sd-ext
this links link2sd standart path /data/sdext2 to /sd-ext
(14) Install and restore all apps with Titanium Backup
(15) use link2sd to move apps to second partition -> "Create Link"
(16) check /sd-ext with root file explorer to see if apps get moved correctly
Click to expand...
Click to collapse
as for mine i stop at step 11 because it worked already without modifying scripts..

my point is ext4, i just read in merruk you need to flash ext4 using CWM,, because ext4 is a zip file,,
is ext4 is same as ext3 ext2,,
i have already ext3 running using a2sd,

kimerika said:
my point is ext4, i just read in merruk you need to flash ext4 using CWM,, because ext4 is a zip file,,
is ext4 is same as ext3 ext2,,
i have already ext3 running using a2sd,
Click to expand...
Click to collapse
Its not for the sd card.. Your mentioning ext2/3 for the 2nd partition of sd card.. Flashing ext4.zip wipes data and cache and converts it to ext4 from rfs.. It increases performance but a noticeable little battery drain..
Sent from my GT-S5360 using xda premium

hitme987 said:
Its not for the sd card.. Your mentioning ext2/3 for the 2nd partition of sd card.. Flashing ext4.zip wipes data and cache and converts it to ext4 from rfs.. It increases performance but a noticeable little battery drain..
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
thats what i need can u give link or TUT how to work it,

kimerika said:
thats what i need can u give link or TUT how to work it,
Click to expand...
Click to collapse
Its simple. After having your desired custom ROM flashed you can apply merruk kernel with ext4.
1) Flash the merruk kernel using kernel updater or using odin(refer merruk topic)
2) Flash ext4 . It wipes the data and cache.
3) You need to flash your custom rom/stock ROM now as youll get boot loops
4) If you still encounter bootloops after flashing stock/custom ROM, flash the merruk kernel again.
5) Reboot and check the kernel version in settings->About phone and make sure its merruk 2.0
6) Thats it. Profit

[SOLVED] Cannot flash CM 9 RC1 Build 2 on my Tmobile G2

After flashing CM 7.0.3 a long time ago, I haven't really updated anything or touched anything when it comes to the recovery, SU, etc since.
Seeing ICS, I tried to flash CM 9 RC1 Build 2 the way I've flashed other ROMs before: Loading the ROM and gapps zip to the root of my SD card, rebooting into recovery, wiping phone, wiping cache, then applying a zip. When I try to flash CM9s zip, I get the error:
E:can't open sdcard/name_of_zip.zip (bad)
I've tried various CM9 mirrors with the same result. I have a feeling it might be because I have a much outdated recovery, and SU binary?
My ROM Manager: 5.0.0.8
My ClockworkMod Recovery: 3.0.0.5 (latest 5.0.2.7?)
My SU binary: 2.3.1-ef (latest 3.1.1?)
When trying to update my SU binary it fails when copying su to /system..
Can anyone give me a starting direction on what I need to do to get CM9 flashed and working?
Thank you!

Use the superwipe + 4ext 1st. or change ur recovery.
File sytem needs to be ext4 fore ICS onwards as far as i know.

wileykat said:
Use the superwipe + 4ext 1st. or change ur recovery.
File sytem needs to be ext4 fore ICS onwards as far as i know.
Click to expand...
Click to collapse
You can run EliteMod and CM9 for example on an ext3 filesystem (the zip provided will format whichever filesystem to ext4 when done in the actual recovery).
Though I have not tried CM9 since beta13 I don't see this being a problem. Though I would advise doing a FULL WIPE (factory reset + cache + dalvik) before flashing on any brand new roms especially when going from GB to ICS.
(last time I checked clockworkmod doesn't let you format a specific filesystem or convert backups from ext3 to ext4 , for that I use the 4EXT recovery).
@ OP you should not have to copy the SU binary anywhere, it should come with CM9 anyways (just like busybox and superuser.apk). The only additional thing you may need to flash on top of it is google apps, just like CM7 would have been.

kbeezie said:
You can run EliteMod and CM9 for example on an ext3 filesystem (the zip provided will format whichever filesystem to ext4 when done in the actual recovery).
Though I have not tried CM9 since beta13 I don't see this being a problem. Though I would advise doing a FULL WIPE (factory reset + cache + dalvik) before flashing on any brand new roms especially when going from GB to ICS.
(last time I checked clockworkmod doesn't let you format a specific filesystem or convert backups from ext3 to ext4 , for that I use the 4EXT recovery).
@ OP you should not have to copy the SU binary anywhere, it should come with CM9 anyways (just like busybox and superuser.apk). The only additional thing you may need to flash on top of it is google apps, just like CM7 would have been.
Click to expand...
Click to collapse
Worked like a charm! I installed 4EXT recovery, wipe/factory reset, wipe cache, wipe dalvik cache, and CM9 installed just fine.
Thank you so much!