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...
Related
[(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!
I have a question that some may think is stupid especially since i have been modding for almost half a decade. Anyway i still do not understand the whole ext2,3,4 thing. I know there are kernals that use different ext # but when they say that a kernal has ext4 support, does that mean that you still have to partition our sd card to have ext4 or does it mean that the kernal creates and uses an ext4 partition for aps2d?
Another question that I have is with Boot Manager, when you are about to install a zip in one of your slots and it asks if your rom is ext 2 or 4, what does that mean, does it mean that you have to have an ext paritition to use bootmanager?
Any feedback would be appreciated
When a kernel has support for a certain version for the ext file system that means the kernel can read and boot partitions that a formatted to that version of the file system. Now sd-ext still needs to be creates in clockworkmod or some other way for app2sd.
Now as for boot manager. It doesn't create a partition. what it does is create img files which the app mounts and format it either as ext2 or ext4 whichever you chose and then copies the contents of the zip to the mounted img files according to the updater-script in the zip.
Sent from my Incredible 2 using XDA App
Which one should I be using for my sd-ext partition? I just put on a new ROM on the other day (see sig for details), and did an ext2. If 3 or 4 is better, is there an easy way to convert it (using linux is fine in a card reader). Could I just copy it off, format and copy back or do I need to be more careful. Also will the ROM just pick up the partition type, or would the ROM need a complete re-install?
4 is better. It is newer and more robust with journalling (like 3) but better performance.
But if you use an Old CWM recovery, it will convert it back to ext 3 when you backup / restore.
Edit, you do use an old CWM. The Alpharev one is dodgy anyway. I recommend 4EXT recovery (Touch)
rootSU said:
4 is better. It is newer and more robust with journalling (like 3) but better performance.
But if you use an Old CWM recovery, it will convert it back to ext 3 when you backup / restore.
Edit, you do use an old CWM. The Alpharev one is dodgy anyway. I recommend 4EXT recovery (Touch)
Click to expand...
Click to collapse
Thanks that's great information. So how do I go about converting it from 2 to 4? Happy to do this in linux, etc? As it's just the sd-ext partition, can I just copy the contents (wuth cp, etc), and re-format, or is there a better way, and will my ROM just work?
(I should be able to dig around for the newer recovery u recommended without help!)
gunja99 said:
(I should be able to dig around for the newer recovery u recommended without help!)
Click to expand...
Click to collapse
On my sig. LOL
rootSU said:
4 is better. It is newer and more robust with journalling (like 3) but better performance.
But if you use an Old CWM recovery, it will convert it back to ext 3 when you backup / restore.
Edit, you do use an old CWM. The Alpharev one is dodgy anyway. I recommend 4EXT recovery (Touch)
Click to expand...
Click to collapse
Does all v.5.x.. of CWMs recoveries partition to ext4 or is that for the touch version only? Thanks.
Sent from my HTC Desire using XDA App
laserlion said:
Does all v.5.x.. of CWMs recoveries partition to ext4 or is that for the touch version only? Thanks.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I believe so but CWM uses sd parted which doesnt align the partition which will mean that performance is degraded. I always recommend gparted.
I havent actually tried partitioning in 4ext. It doesnt use sdparted and uses scripts to align but as much as I am a fan of this recovery, I would still always recommend gparted.
rootSU said:
I believe so but CWM uses sd parted which doesnt align the partition which will mean that performance is degraded. I always recommend gparted.
I havent actually tried partitioning in 4ext. It doesnt use sdparted and uses scripts to align but as much as I am a fan of this recovery, I would still always recommend gparted.
Click to expand...
Click to collapse
I see. I'll give gparted a go. Thanks for answering!
Sent from my HTC Desire using XDA App
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
Hi.
Ever since ive rooted my desire ive been using clockworkmod recovery and I'm kind of getting bored of it. Don't get me wrong, its stable and Its never given me any problems, but i change want some change lol.
Does anyone have any recommendations for recoveries? I'm thinking of switching to either cwm touch, 4ext, or twrp.
Also when I switch, do I need to somehow delete my current recovery, or is it OK to just flash it through fastboot without deleting the old one?
Thanks
Sent from my HTC Desire using xda app-developers app
4ext recovery is highly regarded around here, it's good for partitioning sd card properly among other things. see my sig, you can install it through the 4ext app.
to change recoveries you need s-off. when you change, it automatically overwrite the previous one. i think it's only possible to have only one recovery at a time (you only need one working one!)
4ext all the way. Best for Desire.
Sent from my HTC Desire using xda premium
4Ext
I've recently switched from Clockworkmod to 4Ext and have found it quite good.
4Ext has tons of options and can be themed, the only problem I've had with it is the occasional issue where when you boot into recovery it comes up as read-only on /system.
This issue is easily resolved by deleting the 4Ext folder off your SD-Card and rebooting into recovery.
Apart from that - it's rock solid and much nicer to use than Clockworkmod....
thanks guys,
i just flashed it and its pretty cool.
I noticed that when i went to info it showed my ext partition as ext2, when i am sure that i partitioned it as ext4(using gparted)
Anyone else have this problem?
chromium96 said:
thanks guys,
i just flashed it and its pretty cool.
I noticed that when i went to info it showed my ext partition as ext2, when i am sure that i partitioned it as ext4(using gparted)
Anyone else have this problem?
Click to expand...
Click to collapse
that's strange, not seen that before. you can backup your sd card to PC, then repartition from scratch as ext4. i've converted ext3 to ext4 before using 4EXT, don't think it can do ext2 to ext4?
you can't restore a backup to a different file type afaik. in other words, if you have apps on ext2 at the moment, don't think they'll be happy if they're restored to ext4.
if you're flashing a brand new rom, not really a problem, you'll need to full wipe anyway, so you'll have a fresh new ext4 partition to fill.
eddiehk6 said:
that's strange, not seen that before. you can backup your sd card to PC, then repartition from scratch as ext4. i've converted ext3 to ext4 before using 4EXT, don't think it can do ext2 to ext4?
you can't restore a backup to a different file type afaik. in other words, if you have apps on ext2 at the moment, don't think they'll be happy if they're restored to ext4.
if you're flashing a brand new rom, not really a problem, you'll need to full wipe anyway, so you'll have a fresh new ext4 partition to fill.
Click to expand...
Click to collapse
yeah its weird. I think i'll just leave it for now as it doesnt seem to be causing any issues.
Also i got this message on the second boot into recovery saying that i changed by hboot (even though i didnt) and that i should wipe my system partition. I decided not to, and my rom booted properly, so is that message normal?
One more thing, when i boot into recovery it takes about 15 seconds to prepare the boot. Is this normal too?
15 seconds isn't normal....
That sounds like the read-only /system partition message that I've got a few times..
Resolved by deleting the 4EXT folder from SD-CARD and it was fine on the next boot into recovery. (only 2 or 3 seconds)
Thanks that fixed it.
Sent from my HTC Desire using xda app-developers app