Related
Anyone having this issue with ANY of the voodoo kernels? It enabled and converted everything to EXT4, but errors out when trying to convert back to RFS. ANy suggestions? Tried the flashable disable voodoo and attempted to disable in CWM, all Try to convert back but fails (see below)
Thanks for your help!
EDIT: Discovered issue was due to a non-existent file, fat.format, in custom builds. Flash the attached zip file, and Voodoo should be able to convert back to RFS.
Hope it helps!
Code:
2010-12-09 06:34:23 filesystem detection on system:
2010-12-09 06:34:24 Ext4 on /dev/block/stl9
2010-12-09 06:34:24 filesystem detection on dbdata:
2010-12-09 06:34:24 Ext4 on /dev/block/stl10
2010-12-09 06:34:24 filesystem detection on cache:
2010-12-09 06:34:24 Ext4 on /dev/block/stl11
2010-12-09 06:34:24 filesystem detection on data:
2010-12-09 06:34:24 Ext4 on /dev/block/mmcblk0p2
2010-12-09 06:34:24 convert cache (/dev/block/stl11) from ext4 to rfs
2010-12-09 06:34:24 ERROR: unable to call fat.format: cancel conversion
2010-12-09 06:34:24 convert dbdata (/dev/block/stl10) from ext4 to rfs
2010-12-09 06:34:24 ERROR: unable to call fat.format: cancel conversion
2010-12-09 06:34:24 convert data (/dev/block/mmcblk0p2) from ext4 to rfs
2010-12-09 06:34:26 ERROR: unable to call fat.format: cancel conversion
2010-12-09 06:34:26 convert system (/dev/block/stl9) from ext4 to rfs
2010-12-09 06:34:29 ERROR: unable to call fat.format: cancel conversion
known issue. supercurio pointed towards a modified fat.format as causing this to happen when running a non-stock rom, as i believe he used the purely stock kernel, and most of us are running modified kernels and roms. not a biggie, just can't disable it, to go back to rfs or flash another rom, you have to odin using the froyo that does not brick method.
Br1cK'd said:
known issue. supercurio pointed towards a modified fat.format as causing this to happen when running a non-stock rom, as i believe he used the purely stock kernel, and most of us are running modified kernels and roms. not a biggie, just can't disable it, to go back to rfs or flash another rom, you have to odin using the froyo that does not brick method.
Click to expand...
Click to collapse
What you mean is to odin back to T959UVJFD with repartition? Will odin wihout disable voodoo birck the phone?
Br1cK'd said:
known issue. supercurio pointed towards a modified fat.format as causing this to happen when running a non-stock rom, as i believe he used the purely stock kernel, and most of us are running modified kernels and roms. not a biggie, just can't disable it, to go back to rfs or flash another rom, you have to odin using the froyo that does not brick method.
Click to expand...
Click to collapse
Mna, was hoping for an easier method. Anyone have the stock fat.format available that can be pushed to /system/bin? Wonder if it would work. Anyone else w/ a better solution? Thanks again for your help!
Odin without disable is fine
I had this same issue. I was able to Odin to eugene's froyo that doesn't brick and then move on to other roms from there. The process was easy.
smartmind said:
What you mean is to odin back to T959UVJFD with repartition? Will odin wihout disable voodoo birck the phone?
Click to expand...
Click to collapse
Odin without disabling voodoo will not brick the phone, if you search for, follow, and use the Froyo That Does Not brick method, that fixes bricks, and will bring you back to stock with rfs.
zimphishmonger said:
Mna, was hoping for an easier method. Anyone have the stock fat.format available that can be pushed to /system/bin? Wonder if it would work. Anyone else w/ a better solution? Thanks again for your help!
Click to expand...
Click to collapse
not sure if pushing the stock fat.format would do it, or cause issues with the rom you're on. thats above my pay grade here. i don't think there is any way to truly remove the voodoo'd partitions and convert them back to rfs, besides the disable method that doesn't work on custom roms, or using odin.
i do think if the voodoo kernel were written into the rom, it may work, but thats just a theory, and i'm no chef.
supercurio did put out the source he used for the voodoo kernel, and i believe also has posted an injection method to inject voodoo into other kernels, however again, above my pay grade (and current knowledge level to actually make it happen)
What is strange is Im using Morific's i9000-based Voodoo kernel, which is made for TW's Nero and I ran into this issue. Guess im stuck on Voodoo for a bit. If anyone would be nice enough to upload a stock fat.format from a JK6\JL1 build, that would be much appreciated (and Ill be able to attempt that idea of pushing a stock fat.format, and attempting to convert back to RFS).
Thanks!
Just odin jk2 with repartion checked. No need for froyo that doesn't brick
Sent from my SGH-T959 using XDA App
zimphishmonger said:
What is strange is Im using Morific's i9000-based Voodoo kernel, which is made for TW's Nero and I ran into this issue. Guess im stuck on Voodoo for a bit. If anyone would be nice enough to upload a stock fat.format from a JK6\JL1 build, that would be much appreciated (and Ill be able to attempt that idea of pushing a stock fat.format, and attempting to convert back to RFS).
Thanks!
Click to expand...
Click to collapse
morific's kernel, was that built from the voodoo 5 beta or the newly released voodoo stable?
again the thought of writing it into a rom was mere speculation on my part. very interesting, i am curious to hear your results of pushing a stock fat.format and attempting a disable, please post your results if you're able to get and push the file.
stephenj37826 said:
Just odin jk2 with repartion checked. No need for froyo that doesn't brick
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
thanks for the heads up, one step that doesn't have to be stepped, i guess old practices die hard.
Okay, fixed it, and I wanted to share w/ everyone else so you can benefit from my PITA.
Voodoo does not like the (or cannot find) fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file (only for the NON-flashable version, attached to this post)
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
I have searched the threads, but Eugene has dropped support for this forum, Could anyone kindly tell me where I can find the rom froyo that doesn't brick?
zimphishmonger said:
Okay, fixed it, and I wanted to share to everyone else can benefit from my PITA.
Voodoo does not like the fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
Click to expand...
Click to collapse
thanks for being the guinea pig, gonna push this over myself and test it out!
smartmind said:
I have searched the threads, but Eugene has dropped support for this forum, Could anyone kindly tell me where I can find the rom froyo that doesn't brick?
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
i would try pushing the fat.format that zimphishmonger posted a few posts back, will be a lot less effort that going with odin.
Hey Zimphishmonger, what version of Nero and which Voodoo kernel were you running when this happened?
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I can confirm pushing that fat.format zim posted to the /system/bin directory will let you disable voodoo.
Sent from my Black Froyo'd, Voodoo'd Vibrant with a gooey Macnut center
Mods, thanks for moving the thread.
I wanted to clarify, as there seems to be some confusion. I was using the Voodoo-modified CWM kernel from Morfic at 1.4Ghz (the one with the "voodoo" red Clockwork Recovery built-in).
I am using Nero b3, no other lagfixes or tweaks to the file system. The key was the error logs that pointed out that fat.format couldnt be executed, because "Linda" actually says "converting system, converting data, etc" but if you check in terminal or via adb, you will still see your partitions mounted as /ext4 (Voodoo Enabled).
Right after pushing the stock fat.format and attempting a conversion back to RFS, it completed the process, AND gave a time estimate (something it didnt do when it errored out). I hope this helps people.
I have attached a FLASHABLE version of fat.format to make things easier for everyone. It just puts the correct file in /system/bin/ so you dont have to work in terminal or adb
zimphishmonger said:
Okay, fixed it, and I wanted to share to everyone else can benefit from my PITA.
Voodoo does not like the fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
Click to expand...
Click to collapse
Thanks, Zimp! This type of solution research is of great value to the community!
BruceElliott said:
Thanks, Zimp! This type of solution research is of great value to the community!
Click to expand...
Click to collapse
NP, glad to share....
OP updated with flashable version (for laziness\ convenience)
zimphishmonger said:
Okay, fixed it, and I wanted to share w/ everyone else so you can benefit from my PITA.
Voodoo does not like the (or cannot find) fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file (only for the NON-flashable version, attached to this post)
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
Click to expand...
Click to collapse
How did you try to convert back to RFS and what does RFS mean? Sorry for the noob questions. I have just never ran into this problem but you seemed to have saved my phone. I hope lol
I was on a hunt to make this work without losing any data and I've figured out a way that works quite nice, and all it involves is a TWRP backup, ADB, and a bit of commandline.
Thanks to TrevE for his ever evolving tweaks to Android and for making them readily available to the community at the cost of one thanks per post, and maybe a beer or two (how many people really buy beer with donations?!)
Required:
TWRP backup
ADB
The EXT4 tweaks for /data
The EXT4 tweaks for /system
(If your ROM doesn't already have them, I will be providing the zips for them courtesy of Synergy.)
Step 1:
Connect your phone to your PC and like all things of this nature, BACKUP! Use TWRP to create a nandroid of your entire phone. We will need this backup to restore data and system via commandline. TWRP is the only tested method that works, since it creates backups that are actually TAR files (God, I love TWRP for this). Stay in recovery after completing backup.
Step 2:
While still in recovery, enable USB storage mode and download the two EXT4 files below (or applicable if your ROM already has one of the partitions optimized) onto the root of your microSD card. To make things easier, you can temporarily move your data.win and system.win files to the root of your microSD card. They are located in the TWRP folder on your microSD card. Afterward, disable USB storage mode.
Next, there are TWO ways to accomplish this. Choose which way you want to go before continuing.
Method 1: Reflash your ROM(NOT RIGHT NOW, later on in the guide--depending on ROM, this may format your /system and/or data partitions, rendering the tweaks useless.)
Method 2: Use commandline to restore your ROM from TWRP backup.
Step 3:
From recovery, wipe dalvik and cache and format data and and depending on method, your system partitions as well. NOTE: formatting the partitions can be done from TWRP in the advanced menu.
Step 4:
Flash the applicable EXT4 file.
Step 5:
Mount /data, /system, (if applicable), and /sdcard with TWRP and launch an ADB shell by typing "adb shell" then press enter while in your ADB folder from command prompt/terminal.
Step 6:
Type "cd /sdcard" and press enter. To make sure you're in your sdcard, type "ls" then press enter to verify that it's listing your microSD card contents.
Step 7:
Type "cd /data" and press enter. To make sure you're in /data, type "ls" then press enter to verify that it's empty. It will probably contain a lost+found folder, if so then that's fine.
Step 8:
If you moved your data.win and system.win backups to the root of your microSD card to make this easier, simply type "tar xvpf /sdcard/data.win" then press enter and it will begin extracting the backup file onto the /data partition. Otherwise, you will have to type "tar xvpf /sdcard/TWRP/nameofHTCfolder/nameofdatefolder/data.win" then press enter. This will take a few minutes to complete.
NOTE: MAKE SURE YOU ARE IN THE /DATA PARTITION BEFORE TYPING THAT COMMAND, OTHERWISE THINGS WILL GO WRONG.
Step 9:
Either reflash your current ROM (checking to make sure it doesn't format /system before installing) OR type "cd /system" then press enter. To make sure you're in /system type "ls" then press enter to verify that it's empty. It may contain another folder, if so that's fine. It should however be empty of ROM related files.
Step 10:
If you moved your data.win and system.win backups to the root of your microSD card to make this easier, simply type "tar xvpf /sdcard/system.win" then press enter and it will begin extracting the backup file onto the /system partition. Otherwise, you will have to type "tar xvpf /sdcard/TWRP/nameofHTCfolder/nameofdatefolder/system.win" then press enter. This will take a few minutes to complete.
NOTE: MAKE SURE YOU ARE IN THE /SYSTEM PARTITION BEFORE TYPING THAT COMMAND, OTHERWISE THINGS WILL GO WRONG.
Step 11:
Once this is all complete, exit ADB shell by typing "exit" then pressing enter. Next, unmount /system, /data, and /sdcard from TWRP and head on over to the fix_permissions option in TWRP and let it run. It will take a few minutes to complete.
Step 12:
Go ahead and wipe dalvik and cache again just to make sure, then reboot.
It will take a while to boot back into android, but if all goes well, you should have your data intact with fully optimized EXT4 partitions thanks to TrevE/Synergy.
NOTE: This worked for me, and if you follow the guide precisely, it should work for you too.
NOTE2: I did not try this method with /system, ONLY data, and it worked fine. I assume the same for /system as well.
Awesome! I as many others are appreciative of Team Xposed and how you explain mods to everyone. Most of the time we get a .zip with no explanation on how the .zip is doing what it does. We just know flash this and this happens, lol. With these breakdowns we all get a better understanding on how things work in our devices
Perhaps a sticky with all Team Xposed mods/tweaks, that would be
I believe this is what i used the last time i flashed synergy. If so, then it works great.
Wow the step by step was GREAT!! Man I did this in like 5 minutes....Granted it took me about 30 minutes to download all the tools I needed. Thanks for this one!!
Edit: So how do you know it truly worked?? How do I check if I am ext4 or not?
wow. I had EXT4 on my samsung phones and I LOVED it compared to this! I will definitely try this and make a video on my success or failure! lol
so what if i didnt care to lose data could i flash this with another rom.
Ok. So just trying to gain a better understanding here. So say if the rom were running already includes the /system tweaks but not the /data tweaks and the rom doesn't erase on flash can I just flash both of the files and flash the rom?? Also if I wanted to apply the tweaks to and existing nand can I just flash both the files and do a nand restore??? Or is restoring the data from the command line needed in order for the tweaks to work effectively???
Locked & Loaded
" Shooter on Deck "
Great write up, thanks for that!
Not to be a party pooper, but isn't there a tweaked version of the EXT4 optimized zip that backs up data to sd card, formats /data with ext4, then auto restores /data for you? I found it somewhere in the Synergy thread.
Correct me if im wrong if this does something more/different.
here is a link to it:
Synergy_Format_Data_EXT4_Optimized_apps_autorestored.zip
http://forum.xda-developers.com/attachment.php?attachmentid=708982&d=1315062399
I used it to go from Warm2.3 to Steel2.3 without any issues what so ever, except having to restore XDA app, wifi/bt networks and some widgets. It kept all my screens and settings just the way i like it. YMMV! i take no credit, and assume no responsibility if it rips your phone a new one.
Our phones are already ext4, the optimization just turns on some more features for ext4.
And the tool linked before me doesn't backup everything in /data... It should probably work, but if it misses anything this method will catch it
I just took the opportunity to wipe clean and reset some things.
Sent from my PG86100 using XDA App
youngpro83 said:
Wow the step by step was GREAT!! Man I did this in like 5 minutes....Granted it took me about 30 minutes to download all the tools I needed. Thanks for this one!!
Edit: So how do you know it truly worked?? How do I check if I am ext4 or not?
Click to expand...
Click to collapse
Good question. I suppose you could run a few Quadrant benches to ease your mind. You should get much better scores than you would normally. I suppose the only real way to know for sure is if someone created an EXT4 tweak checker of some sort lol. But the Quadrant benchmark should be enough, that is if you remember what kind of scores you were getting before hand.
digitalcrash said:
so what if i didnt care to lose data could i flash this with another rom.
Click to expand...
Click to collapse
Glad you asked! If you don't care about losing data, just go ahead and format your system and data partitions with TWRP or whatever recovery you use, then apply the tweaks zips and go ahead and flash the ROM of your choice. You should double check the updater-script of your ROM to make sure it doesn't reformat the /system partition or it will render the /system tweak useless.
laie1472 said:
Ok. So just trying to gain a better understanding here. So say if the rom were running already includes the /system tweaks but not the /data tweaks and the rom doesn't erase on flash can I just flash both of the files and flash the rom?? Also if I wanted to apply the tweaks to and existing nand can I just flash both the files and do a nand restore??? Or is restoring the data from the command line needed in order for the tweaks to work effectively???
Locked & Loaded
" Shooter on Deck "
Click to expand...
Click to collapse
Well, if the ROM you're running already contains the /system tweaks then you're half-way there. You still want a backup though, because each of these zips will format its respective partitions. You only want the zip that applies. In your case, you'd only need the data tweaks, but you'd still have to follow the guide that pertains to restoring your data partition after tweaking.
MFD00M said:
Great write up, thanks for that!
Not to be a party pooper, but isn't there a tweaked version of the EXT4 optimized zip that backs up data to sd card, formats /data with ext4, then auto restores /data for you? I found it somewhere in the Synergy thread.
Correct me if im wrong if this does something more/different.
here is a link to it:
Synergy_Format_Data_EXT4_Optimized_apps_autorestored.zip
http://forum.xda-developers.com/attachment.php?attachmentid=708982&d=1315062399
Click to expand...
Click to collapse
Glad you linked that. I actually looked over this yesterday, and while it does do something similar to this guide, It actually only restores part of your data partition, which is why it's said that you will need to repair your bluetooth devices and reenter your WiFi network settings. IIRC, it doesn't restore the entire data partition, just most of the important folders. If it were to do the entire partition, well, this guide would be much shorter.
freeza said:
Glad you linked that. I actually looked over this yesterday, and while it does do something similar to this guide, It actually only restores part of your data partition, which is why it's said that you will need to repair your bluetooth devices and reenter your WiFi network settings. IIRC, it doesn't restore the entire data partition, just most of the important folders. If it were to do the entire partition, well, this guide would be much shorter.
Click to expand...
Click to collapse
Thanks for clearing that up, i will try your method as well. I need more ADB exposure to help me learn.
so my next question is if the rom does format system on boot then i would install with adb as your guide says?
digitalcrash said:
so my next question is if the rom does format system on boot then i would install with adb as your guide says?
Click to expand...
Click to collapse
Yup...pretty much.
Thank you for this. I was able to apply this without any issues.
freeza said:
Yup...pretty much.
Click to expand...
Click to collapse
What would be the process if I didn't care about losing data? Would I just flash, and resign into my Google account and go through that process again?
LiquidSolstice said:
What would be the process if I didn't care about losing data? Would I just flash, and resign into my Google account and go through that process again?
Click to expand...
Click to collapse
If you don't care about losing data, you'd format/wipe the data and system partition from recovery, apply both ext4 zips... wipe dalvik+cache, reflash your ROM, and reboot
Keep in mind that this is pretty much the same process as factory reset, so you might as well just perform one of those lol
freeza said:
If you don't care about losing data, you'd format/wipe the data and system partition from recovery, apply both ext4 zips... wipe dalvik+cache, reflash your ROM, and reboot
Keep in mind that this is pretty much the same process as factory reset, so you might as well just perform one of those lol
Click to expand...
Click to collapse
So just to be clear, all that I need to do is before I flash a ROM, Superwipe/XRON wipe like I always do, flash the ROM, flash the EX4 zips, and then clear dalvik/cache and boot?
LiquidSolstice said:
So just to be clear, all that I need to do is before I flash a ROM, Superwipe/XRON wipe like I always do, flash the ROM, flash the EX4 zips, and then clear dalvik/cache and boot?
Click to expand...
Click to collapse
You wanna flash the zips before flashing ROM, as they format the partitions with the tweaks. You also want to double check the updater-script of your ROM to make sure it doesn't format the /system partition before installing, as it would remove the tweaks.
Soo..
Superwipe/XRON
EXT4 tweaks
ROM
No need to wipe anything as Superwipe/XRON already does this.
freeza said:
You wanna flash the zips before flashing ROM, as they format the partitions with the tweaks. You also want to double check the updater-script of your ROM to make sure it doesn't format the /system partition before installing, as it would remove the tweaks.
Soo..
Superwipe/XRON
EXT4 tweaks
ROM
No need to wipe anything as Superwipe/XRON already does this.
Click to expand...
Click to collapse
EXT4 before ROM?
Bear with me, I'm still a bit confused :X. Wouldn't flashing a ROM after the EXT4 data/system zips negate the zips' function?
LiquidSolstice said:
EXT4 before ROM?
Bear with me, I'm still a bit confused :X. Wouldn't flashing a ROM after the EXT4 data/system zips negate the zips' function?
Click to expand...
Click to collapse
lol no problem.......Well, what the tweaks does is format the system and data partitions a certain way as to improve io functions and other stuff. It's like formatting a drive in Windows with cluster switches etc. It's still empty once you flash the tweaks. The ROM simply puts all the information on the newly formatted filesystem. If you were to apply the tweaks after flashing the ROM, it would format the partitions and erase all data, which is why you do it first. The updater-script in ROMs also have the ability to format partitions, which is why in Synergy ROMs, simply flashing their ROM also applies the tweak and which is why you should check your updater-script beforehand to make sure it doesn't have a format command in it, as it would negate the tweaks.
Hi,
If i convert to EXT4 from CWM settings, will stock ROM have any issues or it's going to work just fine?
got anwer at #moto-atrix IRC chan.
I need custom kernel which supports EXT4 first.
purpler said:
got anwer at #moto-atrix IRC chan.
I need custom kernel which supports EXT4 first.
Click to expand...
Click to collapse
Once you get the appropriate kernel the CWM conversion works great. Keep in mind, whenever you wipe a partition through CWM/fasboot you will need to re-run the script, as they will get formatted back to ext3. They can still get mounted as ext4, but all of the optimizations will be gone.
What's the benefit of converting to ext4?
Milenko2121 said:
What's the benefit of converting to ext4?
Click to expand...
Click to collapse
Faster file transfers, processing, and the ability to read extremely large files. As far as I know at least, as I'm no expert
Sent from my MB860 using xda premium
Hi all.
I'm thinking to convert my file system from rfs to ext4. For that I downloaded the conversion app from the cf-root thread, but I'm not sure that this is safe enough to go.
I have ~20 MB free space on system, I have cwm 5 installed, and I'm on 2.3.6 XKT7. (I would like to have ext4 system, to flash turboboost and lagfree.) Could you tell me something? Is it 100% safe, doesen't it harm the phone? Naturally I made a backup with Titanium Backup, and with cwm, but it would be better just to have nothing changed, only the file system...
I did it about 2 month ago. Everything work great, I don't have any problems. Don't wait, just do it
since i didnt see you have written CF-root kernel is installed on your phone first i have to remind you that CF-root ext4 tool won't work without it!
and second (just a little correction); you do not need to have your file system as ext4 in order to use turboboost and lagfeee... they are scripts to make some changes in the way your phone decides what to do when it comes to manage things in its functioning system like ram management.. on the other hand, ext4 tool is an apk to easily change your memories' formats to ext4 from rfs..
but still i would recommend you to make an ext 4 convertion, it makes difference.. and also using ONE of those scripts..
_delice_doluca_ said:
since i didnt see you have written CF-root kernel is installed on your phone first i have to remind you that CF-root ext4 tool won't work without it!
and second (just a little correction); you do not need to have your file system as ext4 in order to use turboboost and lagfeee... they are scripts to make some changes in the way your phone decides what to do when it comes to manage things in its functioning system like ram management.. on the other hand, ext4 tool is an apk to easily change your memories' formats to ext4 from rfs..
but still i would recommend you to make an ext 4 convertion, it makes difference.. and also using ONE of those scripts..
Click to expand...
Click to collapse
So I just don't understand this. In the lagfree thread, it says, that the system has to be in ext4 format, to make the tool work.
And in the other hand, I read, that turboboost and lagfree together are the best way, to make the Ace a true ace.
So than... I'm as confused as I can be.
kmarci said:
So I just don't understand this. In the lagfree thread, it says, that the system has to be in ext4 format, to make the tool work.
And in the other hand, I read, that turboboost and lagfree together are the best way, to make the Ace a true ace.
So than... I'm as confused as I can be.
Click to expand...
Click to collapse
Nobody out there to help a bit...?
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Sent from my MT11i using XDA
mpiekp said:
Hi guys as you know our Xperia 2011 use yaffs2 for the mtd partitions, but it doesn't have too.
I bit the bullet, formated system, cache and data as ext4 from updater-script, knowing that alliance (nightelf) kernels had support for this.
It boots and runs lovely
Click to expand...
Click to collapse
Any noticeably difference? Run any benchmarks? I never understood why SE used yaffs2 for phones, same as why ext4 isn't supported by default, but that's other story
Anw, I guess now you can only install rom via .zip from CWM? Or maybe even flashtool wouldn't complain, but I guess PCC would complain for sure
p.s. respect for trying that
report pros and cons
Lol to revert just flash s zip that formats as yaffs, will try flashtool, although don't expect an issue as it basically raw writes the sin, which are complete img files including filesystem.
Benchmarks would be pointless, due to running experimental build anyway so nothing to compare to, but things like file manger appear more responsive.
All I can say is try it, make sure the updater-binary you use can accept 4 arguments for format and mount (hint the one in codename can), place that into any Rom zip and edit the updater-script.
So the format line is like this
format("ext4", "MTD", "system", "0");
Sent from my MT11i using XDA
Wonderful and brave find!! ext4 are supposed to be safer (journalism), but can have some overhead.
I have seen a script that even converts live yaffs2 to ext4 in some other forum, so that formatting is not required.
Otherwise, after format, you can restore the backups!
I am really interested to know if the partitions can be resized, so that we can have more space for /data (instead of 100 mb /cache and such a large /system)
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
mpiekp said:
Actually having checked how its mounted, it appears to have ignored the fs type
Still I'm going to persue this, what are the default part sizes? Esp part mtd1 where vendor gets mounted as on gb vendor is empty
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Maybe those links help you understand :
http://forum.xda-developers.com/showthread.php?t=1566846
http://forum.xda-developers.com/showthread.php?t=1449917
how can we check the type of our partitions?
I'm researching a bit, and people say that yaffs2 is better than ext4 for NAND memory.
I need to research a bit more on this matter.
I am here to learn.Thanks for sharing.
termagazis said:
how can we check the type of our partitions?
Click to expand...
Click to collapse
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
su
Click to expand...
Click to collapse
df
Click to expand...
Click to collapse
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
400 for system is excessive, should be safe to bring down to 300, forget vendor 6m is not worth worrying.
With /cache that could be another 200mb for data.
Also boot is a worry, formatting the blocks of mtd doesn't appear to work, could rewrite the array, but may kill boot, which would be a hard brick.....
Sent from my MT11i using XDA
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
leajian said:
FOUND IT! :D
Install Terminal emulator
AND TYPE THIS:
It gives you all the info you need. If you won't type su, it would not give you MTD partitions' info.
Searched this http://www.computerhope.com/unix/udf.htm according to the image shown here http://forum.xda-developers.com/showthread.php?t=1566846 did I realised that.
Click to expand...
Click to collapse
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
termagazis said:
in the image you gave it doesnt say in what format is every partition.(yaffs or ext3,ext4)
Click to expand...
Click to collapse
In that case, just time
mount
Click to expand...
Click to collapse
in Terminal Emulator and see that every partition is reported on what filesystem it is.
More info @ http://www.cyberciti.biz/faq/linux-how-to-determine-find-out-file-system-type/
Or run it as root
Sent from my MT11i using XDA
yacloo said:
Yaffs designed for nand flash based embedded systems
Ext4 is not for that
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Before you will notice any degradation of NAND, you will sell this phone and forget about it, so...
I made a mess
do I change file system? dont i change it? good or bad?
Actually, it is that easy.
However, all the kernels are set to mount as yaffs, so you also need to unpack and edit the config files in the kernel too.
Sent from my MT11i using XDA