hi all,
i know how to format IN YOUR ROM to ext4 but i am building a ROM and i used the Stock Rom that is in Rfs FS , how do i format to ext4 ? i use PX-Kernel 3
thank you
EDIT: btw is it normal that when i exract the boot.img i dont get a Ramdisk ?
And again , no answer...
I suggest you tar the contents of the RFS /system partition, reboot into recovery, format /system to ext4 and extract the contents of your tarball.
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!
what kind of rom can i install for CWm 3.2.0.5??
everything
Though if you format data and such it will format to ext4 in which case you need a ext4 compatible kernel.
SOOOOO
you can install a RFS rom
you can install an ext4 rom + kernel
you can install an ext4 kernel and then restore a rom backup
you can install an rfs rom and then run rfs2ext4 with an ext4 kernel
you can install and format and do whatever with ext4 then do ext42rfs and not need an ext4 kernel
and so on
Popeye3c said:
what kind of rom can i install for CWm 3.2.0.5??
Click to expand...
Click to collapse
If you mean 3.0.2.5, you can install everything, but I HIGHLY recommend updating your clockwork to 3.1.0.1 to eliminate problems. Follow this video: http://www.youtube.com/watch?v=dsRA7q4JWPQ
like the title says, I want an EXT4 partition from my system, wich is needed to install mods.
im currently running cyanogenmod 7.2 rc1 rooted, clockworkmod installed.
to install the script, I need an EXT4 system partition. I know how to do this on my SD card, but how to do this on your system?
thanks
You find the tutorial in this thread:
http://forum.xda-developers.com/showthread.php?t=1397120
But you need a card reader, you can't format to ext4 with usb cable.
LegoGabi: he's talking about the internal memory.
IIRC the CM7 install script did the formatting for you.
Starting from RFS partitions, either:
-Install a ROM with CWM that includes the reformatting utilities in its zip along with the required commands in the script.
-Use an appropriate ext4 CWM recovery and use the format functions in there.
-You could also make your own script, there's a few out there for other devices that could be adapted...
Oh, i thought he wants to make app2sd work.
I think cyanogen are already EXT4, so you don't need to convert it anymore
Cyanogenmods for Gio are in EXT4.
It formats internal partitions during installation.
Sent from my GT-S5660
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
Hello. I can see that Android use Kernel on SD but write NAND Partitions (Data/Cache/System). It is Possible to make fota BOOTING from zImage ,,pushed" into any of this tree partitions, without SD? Not LOOP or Emulated NAND. Three Partitions, NO BADA, No SD. Possible?
ghoslslender124 said:
Hello. I can see that Android use Kernel on SD but write NAND Partitions (Data/Cache/System). It is Possible to make fota BOOTING from zImage ,,pushed" into any of this tree partitions, without SD? Not LOOP or Emulated NAND. Three Partitions, NO BADA, No SD. Possible?
Click to expand...
Click to collapse
FOTA can't read zImage from ext4 partitions as far as i know
We still have no any way to flash zImage(boot.img) as RAW to Onenand via Multiloader, and then need changes to FOTA
@adfree maybe you know how to flash zImage this way by multiloader? Something like you did with LK_boot for wave3, but we need app_compressed.bin for our FOTA
@volk204
From ext4 NO
but FAT32 like SD YES
Maybe make 4'th partition (FAT32 where we copy zImage) next to data( Now /data /cache and /system ) like /boot or something? 10mb is all what we need, we can cut it from Data (about 1550mb)
ghoslslender124 said:
@volk204
From ext4 NO
but FAT32 like SD YES
Maybe make 4'th partition (FAT32 where we copy zImage) next to data( Now /data /cache and /system ) like /boot or something? 10mb is all what we need, we can cut it from Data (about 1550mb)
Click to expand...
Click to collapse
Yeah, or keep one bada fat16 partition and put /cache on img file on it. Or put /cache and /data in the same ext4 partition.
Problem : path for kernel change depending on partition layout.
ex :
Code:
kernelImage = L"/e/boot_2.img"
for 1st fat partition of SDcard
Code:
kernelImage = L"/g/boot_2.img"
for 2nd fat partition of internal memory
But what is path for 1st fat partition of internal memory ?
Maybe someone want to try all alphabet letters... not me
Maybe someone know how these partition are mounted and labelled...