Related
This is a simple .zip file you can flash on any amami, which uses a ramdisk like the combinedrootfs from Cyanogenmod 11. Your device needs to have a f2fs-compatible kernel, for example this one.
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your system, data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
Ok but... what is f2fs?
It is a new file system, which is especially designed for flash-based storages, like our phones. It will give you much better reading and writing speed.
Installation:
1. Be sure, that you have a f2fs-compatible kernel and your ramdisk's structure is similar to Cyanogenmod's one. If you are on any aosp-based rom, the ramdisk will be compatible anyway.
2. Flash the .zip file from a custom recovery
3. Reboot recovery
4. Now go to advanced wipe and you can change the file systems of system, data and cache to f2fs.
Some more information:
If you convert cache to f2fs:
->No data will be lost
If you convert data to f2fs:
->Your whole internal storage will be wiped. backup your data before you decide to do that!
If you convert system to f2fs
->You need to flash your rom again. You need to modify the updater script of your rom before that like this
OK. I formatted data with f2fs, but want to flash a new rom. What to do?
You need to flash a kernel with f2fs and this zip, no need for any wipes
Download:
http://www.androidfilehost.com/?fid=23578570567713678
For Developers:
You can include this in your rom like this: https://gist.github.com/CoolDevelopment/54ede52a1e075da48151
XDA:DevDB Information
F2FS for amami, Tool/Utility for the Sony Xperia Z1 Compact
Contributors
CoolDevelopment, NovaFusion
Version Information
Status: Testing
Current Beta Version: 2.0
Beta Release Date: 2014-07-16
Created 2014-07-16
Last Updated 2014-07-16
@CoolDevelopment
So, if I corectly understand this zip will erase all data including internal storage? Am I right? But about if I use nightlies? Will I neen to flash it every time after update?
da900 said:
this zip will erase all data including internal storage?
Click to expand...
Click to collapse
It won´t erase your internal storage , I flashed and everthing is there !
pvillasuso said:
It won´t erase your internal storage , I flashed and everthing is there !
Click to expand...
Click to collapse
OK. Thanx. But will erase all data, so I need to install all apps again?
da900 said:
OK. Thanx. But will erase all data, so I need to install all apps again?
Click to expand...
Click to collapse
Nope , it won´t erase any data, files, apps, etc from your internal o external storage
from the OP :
This zip is only modifying your current ramdisk. It will delete the normal fstab and add a binary, which detects if your data and cache partition are formatted with f2fs and create a new fstab every boot. It will also flash a twrp recovery, which is modified to work with f2fs.
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
CoolDevelopment said:
It does not erase anything. It makes your current ramdisk compatible with f2fs. If you just flash this notjing changes. But you can convert you cache and data partition to f2fs after flashing the zip with the recovery. If you do that, all your data is lost.
If you have converted your partitions to f2fs and flash a new rom, you need to flash a f2fs-compatible kernel and this again.
Click to expand...
Click to collapse
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
da900 said:
OK. Thanx. I will try. But if I will update the ROM (for example, when using CM nighlies), when there is no need to wipe all data, will I still need to perform all these steps to convert data partion to f2fs? I mean will I need every time restore all data again?
Click to expand...
Click to collapse
You need to flash a f2fs compatiblr kernel and this zip, no wipes
But if you don't do that your rom will bootloop
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
New version!
I uploaded a new version with /system support and a few fixes.
I also updated the op.
Have fun!
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
idimitro said:
I would guess that if you have f2fs you should flash the appropriate kernel only if switch ROMs or if the nightly build brings kernel changes.
If you install kernel with f2fs support and your partition is f2fs formatted, I think your data should be safe even between ROM changes.
Somebody please confirm my assumptions.
I hope oshmoun will have the time to build PAC ROM with oms kernel, built in [emoji12]
Click to expand...
Click to collapse
Every rom flashes a boot.img. This boot.img contains a zImage and a ramdisk(on sony devices it is a bit more complicated but that's enough for now).
Using f2fs needs:
1. A zImage(kernel) with f2fs support
2. A ramdisk with f2fs support
This zip modifies the ramdisk for compatibility with f2fs.
You need to flash a f2fs kernel manually.(for example my moshkernel)
And everytime you flash a new rom, you have to modify the contents of the boot.img again
And why don't I just let you flash a modified boot.img? It is only one file.
It would only be compatible with one rom. This is compatible with any rom and boot.img, which uses the ramdisk architecture like cyanogenmod(combinedrootfs).
I hope I could explain it well
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
najar360 said:
If i want to format my system to f2fs, i just need to do step 6 as in your link and then zip back the rom?
So when ever i decide to do full wipe everything, will my system, data, cache format still in f2fs format?
Sent from my Candy Amami using Tapatalk
Click to expand...
Click to collapse
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
CoolDevelopment said:
If you use TWRP yes
But if you want to revert back go to advanced wipe->change or repair filesystem/change filesystem-> ext4
Click to expand...
Click to collapse
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
najar360 said:
i try to change data to f2fs format then flash new rom, mosh kernel, and this patch and then reboot system. i got bootloop. i didnt do step 6 yet.
Click to expand...
Click to collapse
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
CoolDevelopment said:
Can you tell me which rom?
I tried it with slimkat and it worked well
And what kind of bootloop? Do you see the sony or rom bootlogo?
And please use MoshKernel 0.1.2
Click to expand...
Click to collapse
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
najar360 said:
i'm using candykat
my step, flash f2fs patcher, reboot recovery, change cache and data to f2fs format. reboot recovery again, wipe everything. checking cache and data still in f2fs. flash candykat, mosh kernel, f2fs patcher. reboot system. sony bootlogo appear, rom bootanimation appear. stuck for 10 minutes.
anything wrong with my step?
Click to expand...
Click to collapse
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
CoolDevelopment said:
Did you use the latest MoshKernel?(0.1.2)
The new f2fs-patcher zip is not compatible with the old MoshKernel
Click to expand...
Click to collapse
yeaps. i'm using 0.1.2 version.
najar360 said:
yeaps. i'm using 0.1.2 version.
Click to expand...
Click to collapse
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
CoolDevelopment said:
That's strange. I tried it with slimrom, which is the base for candycat as far as i know, and it worked perfectly.
Click to expand...
Click to collapse
is my step correct?
edit : try slimkat and it work.
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
andreas1996 said:
I made a F2FS conversion to Data Partition.When I made a restore the Data Partition cannot be Mount or do a Format.With any recovery(CWM,TWRP,Philz) the Data partition Cannot be mounted or formated.What Can I do?I read threads on the Transformer Forum but nothing of these working for me :crying:
Click to expand...
Click to collapse
Only one that can mount it will be twrp 2.7.1.1 (or the f2fs twrp released in dev)
If it has corrupted just format it back to ext4 and start again.
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Sent from my GT-I9505G using XDA Free mobile app
andreas1996 said:
This is the log when I press wipe or repair partition.in the mount menu i cant select any partition
Click to expand...
Click to collapse
That's not a log, it's a screenshot. The log is in /tmp/recovery.log, so you can use adb pull to get it and post it. Or you can probably use the "copy log to SD card" option in the advanced menu.
Here is the log.I compressed the file because the log format is not supported to attachments.
andreas1996 said:
Here is the log.I compressed the file because the log format is not supported to attachments.
Click to expand...
Click to collapse
According to the log, your recovery can't access any partitions on your eMMC. To find out more, reboot to your recovery again and run on the connected PC:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
and read/post the resulting files.
Here is the two files your commands gave me
andreas1996 said:
Here is the two files your commands gave me
Click to expand...
Click to collapse
Your tablet's eMMC seems to have no partitions at all:
Code:
<6>[ 4.770320] mmcblk0: unknown partition table
What exactly did you do for "a F2FS conversion to Data Partition"? Did you format mmcblk0 instead of mmcblk0p8?
The only thing I did after f2fs conjversion is in Philz recovery I select wipe to install a new ROM.And the problem began.
andreas1996 said:
The only thing I did after f2fs conjversion
Click to expand...
Click to collapse
If you expect help, you need to answer my question. I did not ask what you did *after* the f2fs conversion - what exactly did you do to convert /data to f2fs?
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
andreas1996 said:
enter recovery-wipe-advanced-repair or change filesystem-f2fs-reboot
Click to expand...
Click to collapse
Friend! You got the attention of one of the few people who may be able to help you get your tab back! Use it!
Post DETAILED steps of what you did or _that is going to ignore you!
Which recovery and version thereof did you use?
What did you do afterwards? You mention 3 recoveries. Did you flash all of them?
What did you do in which order in each of them?
Provide as many details as you can!
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
Define "full wipe".
Which CROMi-X version did you try to flash?
Details, details....
andreas1996 said:
First I used the modded twrp recovery from the f2fs thread.I did the f2fs and the chromi-kk work successfull.But because battery drain I wanted to install the last chromi-x version based to stock firmware.Next,I didn't convert f2fs back to ext4,but I made a full wipe with twrp 2.7.1.1.And my problems began.
Also I tried full wipe from the latest CWM and Philz recovery with the same results
Click to expand...
Click to collapse
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
sbdags said:
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
How would you format data without a data partition?
sbdags said:
OK So your issue is that you have left your data partition as f2fs and installed a kernel/rom that does not understand f2fs.....
So as I see it - install a recovery that will reformat as EXT4 - format data and start again?
Click to expand...
Click to collapse
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
andreas1996 said:
I tried that but the TWRP gave me a ERROR message(cannot mount Data).Tomorrow i will upload screenshots and full logs for that,because my transformer has empty battery because of the attempts
Click to expand...
Click to collapse
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
sbdags said:
So try formatting from adb?
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Click to expand...
Click to collapse
When I doing the command (make_ext4fs /dev/block/mmcblk0p8) I receive the message : Need size of file system.
Something seems to be wrong with your GPT. Unfortunately the busybox tools don't support big offsets to read it, so let's first see if the Tegra-specific partition table (which is not used by the kernel) is still there - that won't help you immediately but will show if the eMMC can be read at all and where the partitions are supposed to be. Post the output file of this command:
adb shell hexdump -s 0x300000 -n 2048 -C /dev/block/mmcblk0boot0 > pt.txt
Prerequisites:
You need to be on the 10.6.1.14.10 bootloader
You need to know how to flash a recovery
Some background reading on f2fs: http://en.wikipedia.org/wiki/F2FS
Step 1:
Backup all your data off the tablet because it will get wiped!!
Step 2:
Install a recovery that supports conversion to the f2fs file system
You can use the official TWRP 2.8.x from here:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Do not use TWRP 2.8.5 - it has a bug with the f2fs conversion - or 2.8.6 for that matter. It has another bug: won't reboot to anything from recovery...
For Transformer users I would highly recommend to install @lj50036 TWRP Kang version from here:
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
His Kang TWRP allows you to format/convert/backup external partitions or entire cards which will come in very handy for data2sd or rom2sd users.
It even supports the dock SD!
Step 3
Flash your chosen recovery in fastboot and reboot.
Optional but recommened
Since you are at it anyway I would recommend you format your /data partition before you convert to f2fs. The TWRP build-in "Format data" option does a "a secure erase" which trims and wipes every single block. A great way to start with a fresh and clean data partition. This process takes time - could be upwards of 60 minutes - do not interrupt it!!! You find the option under the Wipe menu
Step 4:
Enter TWRP, choose Wipe > Advanced Wipe
To Convert INTERNAL /data to f2fs
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "F2FS"
Swipe the button
DATA2SD/ROM2SD users only:
To Convert EXTERNAL /data to f2fs (with lj's Kang TWRP TF700T only - official TWRP does not support this)
Check the box for Ext/data
Proceed as above
Step 5
Go back to TWRP Home screen, and reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!! Like: your microSD
Notes:
With /data on f2fs you need to run your ROM with a kernel that supports that file system. Read the OP of your ROM thread
Convert ONLY /data to f2fs. Do NOT convert /system (or anything else for that matter)
If you forma /data back to ext4 for any reason it will take up to 90 minutes. Do not interrupt it!!!
DATA2SD/ROM2SD ONLY
If you have the official TWRP installed and do not want to flash lj's Kang TWRP, you can - as always - use the data2sd1.zip/rom2sd1zip to have TWRP act on your external partitions.
MINE ......
Cool!
berndblb said:
Convert EXTERNAL /data to f2fs (lj's Kang TWRP TF700T only)
Check the box for Ext/data
Proceed as above
5. Step
Go back to TWRP Home screen, and reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!!
Click to expand...
Click to collapse
Convert EXTERNAL /data to f2fs
-- > ??? Is this a folder or a partition as stated in " post #2 Using GParted to setup a micro SD for ROM2SD or DATA2SD support"
reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!!
--> ??? It must be on external, I presume?
Where could it be located? If on external i suppose it is on:
--> ??? 14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
eRPeeX said:
Convert EXTERNAL /data to f2fs
-- > ??? Is this a folder or a partition as stated in " post #2 Using GParted to setup a micro SD for ROM2SD or DATA2SD support"
Click to expand...
Click to collapse
It's the second partition if you are running data2sd/rom2sd
data2sd:
1. partition fat32 = your microSD storage
2. partition f2fs (or ext4) = /data
rom2sd
1. partition fat32 = microSD storage
2. partition f2fs or ext4 = /data
3. partition ext4 = /system
[*]reflash your ROM - which you have stored somewhere you did NOT wipe with the preceding steps!!
--> ??? It must be on external, I presume?
Click to expand...
Click to collapse
The fat32 partition on the microSD (or just plain microSD if you don't run data2sd/rom2sd) is probably the safest place, yes.
Where could it be located? If on external i suppose it is on:
--> ??? 14. FAT 32 : Size 16GB – this will be /dev/sdc1 in gparted and will be your sdcard for storage in Android
Click to expand...
Click to collapse
Yes
berndblb said:
It's the second partition if you are running data2sd/rom2sd
data2sd:
1. partition fat32 = your microSD storage
2. partition f2fs (or ext4) = /data
rom2sd
1. partition fat32 = microSD storage
2. partition f2fs or ext4 = /data
3. partition ext4 = /system
The fat32 partition on the microSD (or just plain microSD if you don't run data2sd/rom2sd) is probably the safest place, yes.
Yes
Click to expand...
Click to collapse
So for f2fs you always need a Gparted formatted SD.
f2fs only on internal /Data is not possible?
Sure it is. Read step 4
I just only converted Internal /data to f2fs.
Flashed beta 4.
Seems to be possible to have f2fs only on internal.
eRPeeX said:
f2fs only on internal /Data is not possible?
Click to expand...
Click to collapse
berndblb said:
Sure it is. Read step 4
Click to expand...
Click to collapse
eRPeeX said:
I just only converted Internal /data to f2fs.
Flashed beta 4.
Seems to be possible to have f2fs only on internal.
Click to expand...
Click to collapse
Where does it say you can't????????????????
Edit: Ahhh! I see where your thinking went off track. You thought you had to convert both internal and external data for f2fs to work, right?
Nope - external data only concerns data2sd/rom2sd users. Edited OP to make that clear - I hope.
berndblb said:
Where does it say you can't????????????????
Edit: Ahhh! I see where your thinking went off track. You thought you had to convert both internal and external data for f2fs to work, right?
Nope - external data only concerns data2sd/rom2sd users. Edited OP to make that clear - I hope.
Click to expand...
Click to collapse
Yes, you could read my mind.
Just thought I'd share my experience, in case someone else makes the same mistake I did ...
I put the card into my computer and ran gparted to create the partitions. I fiddled with it for a while, resizing partitions while trying to decide how much space to allocate to each and what format to use for /data. I ended up with what graphically looked like the right layout:
I---sdcard---II--------------data--------------II---system---I
The rom2sd install seemed to go fine (Crombi-kk at the time). However I couldn't get it to boot.
Turns out in my fiddling I managed to get the second two partition table entries switched - partition 1 was fine, partition 2 pointed to the rightmost block graphically, parition 3 pointed to the middle block. I don't really know whether it was the installer or TWRP that got confused, or if it installed ok but the boot got confused.
In any case, deleting the partitions and re-creating them in order worked.
I have Zombi-X on a TF700T. I picked the F2FS option during install but didn't realize I had to have the /data partition formatted to F2FS first. So I'd like to minimize my update time. Can you tell me if this is how to proceed?
I have TWRP 2.8.4.0 already installed,
When you say backup data do you mean do a TWRP backup of the system/data/boot or just the /data section?
Or do you mean copy files to an SD card or PC?
I would then do the "optional" format of the /data partition using the existing data format ext4.
Then choose Wipe > Advanced Wipe
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "F2FS"
Swipe the button
"Go back to TWRP Home screen, and reflash your ROM"
Do I have to do this? I don't want to change anything, the original install had F2FS enabled?
If I do have to do it, do you mean TWRP "restore" the ROM backup (system/boot/data) or actually TWRP
"install" the ROM zip file?
Then I would TWRP "restore" the /data backup and the tablet would work like it did before the reformat or would I have to reinstall apps, photos etc.?
Thanks for your help.
The easiest would be if you nandroid system/boot/data to your microSD. You gotta have it off internal storage. Nothing in internal /data will survive a format.
Then do the formatting and convert to f2fs
Restore your nandroid
You may get a warning from TWRP that the nandroid is off a different file system but you can safely ignore it.
Now, I do not quite remember where in Aroma the f2fs option was, but I think it's on that page about data journaling... So I'm not sure what selecting that option in Aroma actually does and if it gets implemented when the preinit script finds an ext4 partition instead.
But you can try it. Just restore the nandroid, pay attention during boot and read the script under the penguins.
If then your nandroid doesn't run as expected, reflash the rom with the same options, then restore only data from the nandroid you made earlier (during restore just uncheck boot and system). That also would give you an identical installation to what you have now.
berndblb said:
The easiest would be if you nandroid system/boot/data to your microSD. You gotta have it off internal storage. Nothing in internal /data will survive a format.
Then do the formatting and convert to f2fs
Restore your nandroid
You may get a warning from TWRP that the nandroid is off a different file system but you can safely ignore it.
Now, I do not quite remember where in Aroma the f2fs option was, but I think it's on that page about data journaling... So I'm not sure what selecting that option in Aroma actually does and if it gets implemented when the preinit script finds an ext4 partition instead.
But you can try it. Just restore the nandroid, pay attention during boot and read the script under the penguins.
If then your nandroid doesn't run as expected, reflash the rom with the same options, then restore only data from the nandroid you made earlier (during restore just uncheck boot and system). That also would give you an identical installation to what you have now.
Click to expand...
Click to collapse
Perfect, thanks. I will let you know my results. Might be a few days away.
IIRC the option is to turn on/off data journaling (one or two "l"s?) on ext2/3/4 partitions, with a final option of "f2fs user" where journalling is unnecessary. But it will not automatically format to f2fs in any case.
Hello. Yesterday I rebuilt my TF700 from the ground up. My intent was to get to Zombi-Rom with data2sd, to get a performant system. Here's what I did:
- started with twrp 2.8.6.x and Zombi-Rom beta 6, internal data, nice but laggy
- created two partitions on my samsung class 10 microSD card using gparted: 1. FAT32 at approx 4GB, 2. F2FS at approx 24GB
- flashed lj's kang twrp 2.8.6.1 recovery to replace 'standard' twrp 2.8.6.x
- formatted internal data using the kang twrp to f2fs (but it only took a second?) (I think this step was unnecessary, I meant to go to data2sd...)
- i *think* i formatted the new f2fs partition on the ext sdcard again using kang twrp, but don't recall. Rem: it was formatted f2fs by gparted already...I may have assumed I didn't need to do it again.
- flashed Zombi-Pop Android 5.1 beta 6, choosing the only kernel which has _that in the name
-- choosing f2fs
-- choosging data2sd (the ultimate goal of the exercise - get rid of TF700's awful lags/freezes)
-- choosing overclock (said it was required since _that kernel is selected)
-- choosing rest of default options
However I find performance is worse? I am sure I have done something wrong.
I have no data to protect or worry about tryig to restore. Before I do it all over again, do the steps above look correct, or am I making a mistake somewhere?
Thanks in advance.
Some people - me among them - have reported that data2sd doesn't work that well with ZOMBi-POP anymore. I do not get any performance improvement out of it with the same card that did well on other roms.
Could also be just your specific card - hard to tell.
I see no mistakes in your procedure but did you at any point do the secure erase the "Format Data" option provides? Read the "Optional but recommended" section in the OP.
Try different kernels. I like the Omni kernel best so far.
So my advice is: format internal data, then convert it to f2fs again, flash the rom with the omni kernel and all tweaks.
My TF700 runs very well with those options but it's still slower than my TF701 or my HTC M8 (there's actually no comparison to the latter..) and it always will be.
This is a what - almost 3 year old device now. These roms improve it by 300% but nothing will turn the TF700 into a smooth-as-silk-under-any-circumstances device....
berndblb said:
Some people - me among them - have reported that data2sd doesn't work that well with ZOMBi-POP anymore. I do not get any performance improvement out of it with the same card that did well on other roms.
Could also be just your specific card - hard to tell.
I see no mistakes in your procedure but did you at any point do the secure erase the "Format Data" option provides? Read the "Optional but recommended" section in the OP.
Try different kernels. I like the Omni kernel best so far.
So my advice is: format internal data, then convert it to f2fs again, flash the rom with the omni kernel and all tweaks.
My TF700 runs very well with those options but it's still slower than my TF701 or my HTC M8 (there's actually no comparison to the latter..) and it always will be.
This is a what - almost 3 year old device now. These roms improve it by 300% but nothing will turn the TF700 into a smooth-as-silk-under-any-circumstances device....
Click to expand...
Click to collapse
Same here Bernd - I see no improvements with data2sd anymore on zombi-pop.
I think we got internal running as sweet as can be
Bernd and dags,
thanks for the input, and again for all the great work to get it running the way you and your teammates have. Wish I had your know-how. At any rate I re-built it as originally posted and it's now working well. Backed that up and am trying it on internal today.
One more, maybe trivial question - the version of Nova Launcher says 'mod'. I can't install any other wallpaper with it. (I use Nova all the time, never seen this before.) Do you know if there something in the mod that makes it the default zombi-rom wallpaper or nothing?
Hi guys,
I'll share some scripts (flashable) that I've made to help with xperia l internal memory shortage.
1. First one is the link2sd-enabler.zip: http://www24.zippyshare.com/v/UduJGjqJ/file.html.
For this to work you'll need a second partition on the external sdcard formated as ext4. So first partition is the vfat one, the second primary partition on the external sd card is the ext4 one. Currently I have a 8Gb ext4 second partition.
Installation procedure: prepare your external sdcard, flash the zip, install link2sd application.
2. Second is the 01link2sdmm: http://www86.zippyshare.com/v/9DSgorlH/file.html.
The link2sd application does not automatically link the oat directory of the application. This directory contains the compiled application in the form of an odex file. For big apps this file is pretty big. So this script will automatically link this directory to the sdcard second partition for the applications that are linked to the sdcard. This works in conjunction with the link2sd-enabler.zip script.
Installation procedure: put this script in the /etc/init.d directory with the proper permissions. This way it will run at boot. If you want to run this directly after you link an app you'll need to use automagic and make a rule to run this script after you exit the link2sd application.
Observations: This script is not needed if you switch the internal partitions because you'll have enough space to keep the odex file internally. It's your choice.
3. Third script is the mm-partition-swapper.zip: http://www10.zippyshare.com/v/eyRO7gLw/file.html.
This one will switch your sdcard and userdata partition on your current mm rom. This was tested on rr573 that I have installed, but it should work in other mm roms as well.
Installation procedure: Make sure you have enough space on the external sd card so the script will be able to save your current data partition files. Save the files that you need from your internal partition to your external sd card. Make a backup of your current rom from twrp in case something wrong happens. Format from TWRP the internal sd card as ext4. Flash the zip. If everything works ok then you'll have a rom with the internal partitions swapped and you'll have 4Gb of user data available (minus your space for the already installed apps).
!!!!!!!!!!!!!!!!!!Very important!!!!!!!!!!!!!!!!!!
Don't try formatting the internal sdcard as ext4 with twrp version 3.0.2! It seems that his twrp version does not support this. I'm using twrp 2.8.7.0 by Barbarosa.
Observations: Twrp does not support backing up/restoring internal sd. If you swap partitions you'll have to backup your ext4 internal sd manually from within twrp connected through adb (with a simple tar command)
4. I think 256 ZRAM for the rr573 rom is too big so this zip will change this to 128MB:
mm-128Mb-zram.zip:http://www103.zippyshare.com/v/XjVAnXEl/file.html.
Please make a backup before flashing the swap zip and report if this worked for you.
Hope this helps,
Thanks.
cojocar.andrei said:
Hi guys,
1. First one is the link2sd-enabler.zip:
For this to work you'll need a second partition on the external sdcard formated as ext4. So first partition is the vfat one, the second primary partition on the external sd card is the ext4 one. Currently I have a 8Gb ext4 second partition.
Installation procedure: prepare your external sdcard, flash the zip, install link2sd application.
Click to expand...
Click to collapse
I've been struggeling for quite some time to get the link2sd app working since I flashed MM.
I've done a clean install, flashed the zip, installed link2sd, but I still get a 'mount script error, Cannot create script, mount: no such file or directory.' Anyone got an idea what I do wrong?
thx!
mikelektro said:
I've been struggeling for quite some time to get the link2sd app working since I flashed MM.
I've done a clean install, flashed the zip, installed link2sd, but I still get a 'mount script error, Cannot create script, mount: no such file or directory.' Anyone got an idea what I do wrong?
thx!
Click to expand...
Click to collapse
Check if you have in the /etc/init.d directory the 00link2sd script. For this script to work you need a rom with a working init.d (otherwise this won't work obviously...). If you have the script there, then check if you see a directory /data/sdext2 (if this directory is missing, but you have the 00link2sd script in the /etc/init.d directory, then this means you don't have init.d support in the rom). If you partition your sdcard correctly then the second ext4 partition of you sdcard should me mounted in the /data/sdext2 directory ... All these you need to check before installing the link2sd app...
Awesome! Thank you. I'll try this
cojocar.andrei said:
Check if you have in the /etc/init.d directory the 00link2sd script. For this script to work you need a rom with a working init.d (otherwise this won't work obviously...). If you have the script there, then check if you see a directory /data/sdext2 (if this directory is missing, but you have the 00link2sd script in the /etc/init.d directory, then this means you don't have init.d support in the rom). If you partition your sdcard correctly then the second ext4 partition of you sdcard should me mounted in the /data/sdext2 directory ... All these you need to check before installing the link2sd app...
Click to expand...
Click to collapse
I have the init.d folder, but it seems the sdext2 folder was only created after I installed the link2sd app.
I tried doing it all over again, but it still doesnt work, same messages...
mikelektro said:
I have the init.d folder, but it seems the sdext2 folder was only created after I installed the link2sd app.
I tried doing it all over again, but it still doesnt work, same messages...
Click to expand...
Click to collapse
Then your rom doesn't have init.d support. You need a kernel/rom (more precisely a ramdisk) with init.d support to use this ... The rr573 supports init.d ... Try it with this one ...
cojocar.andrei said:
Then your rom doesn't have init.d support. You need a kernel/rom (more precisely a ramdisk) with init.d support to use this ... The rr573 supports init.d ... Try it with this one ...
Click to expand...
Click to collapse
Thx! Which do you recommend? I've tried several in the last two or three months. Now I'm running AOSP-OMS.
I ran slim, RR and CM 13 beta before without any problems, just the storage issue.
mikelektro said:
Thx! Which do you recommend? I've tried several in the last two or three months. Now I'm running AOSP-OMS.
I ran slim, RR and CM 13 beta before without any problems, just the storage issue.
Click to expand...
Click to collapse
I've just told you. RR573. For a completely working camera on this one just replace a camera library... Search the rr thread...
Sent from the center of the galaxy
3. Third script is the mm-partition-swapper.zip: http://www10.zippyshare.com/v/eyRO7gLw/file.html.
This one will switch your sdcard and userdata partition on your current mm rom. This was tested on rr573 that I have installed, but it should work in other mm roms as well.
Installation procedure: Make sure you have enough space on the external sd card so the script will be able to save your current data partition files. Save the files that you need from your internal partition to your external sd card. Make a backup of your current rom from twrp in case something wrong happens. Format from TWRP the internal sd card as ext4. Flash the zip. If everything works ok then you'll have a rom with the internal partitions swapped and you'll have 4Gb of user data available (minus your space for the already installed apps).
Click to expand...
Click to collapse
I use rom AOSP OMS . file zip working?
Brick and problem other ?
Thx you building script .
Thx advanced
I am on stryflex MM ROM and TWRP 3.0.2.
I formatted internal storage as ext4, then flashed mm-partition-swapper.zip.
Says that there is no ext4fs partition and I tried reboot recovery and my phone is dead now, can't turn it on...
I don't blame you, I blame myself for trying. But please help. Flashtool doesn't recognize flash mode.
Don't use this method. Not safe.
Option58 said:
I am on stryflex MM ROM and TWRP 3.0.2.
I formatted internal storage as ext4, then flashed mm-partition-swapper.zip.
Says that there is no ext4fs partition and I tried reboot recovery and my phone is dead now, can't turn it on...
I don't blame you, I blame myself for trying. But please help. Flashtool doesn't recognize flash mode.
Don't use this method. Not safe.
Click to expand...
Click to collapse
Sorry to hear this. If the script gave you this error then the script did nothing to your phone. It just aborted the procedure because it did not find the sdcard formated as ext4. It must be the twrp version. I'm using twrp 2.8.7.0 by barbarosa. I think twrp 3.0.2 does not support formatting the internal sdcard as ext4. Most pobably the twrp version 3.0.2 formated something else as ext4 or whatever instead of internal sd... I did not know this. Sorry again...
Try to search the brick threads. If you still have a blue light when in flashmode I think you still have a chance to resurect it...
Sent from the center of the galaxy
I've modified the post to warn people of this twrp version. So, people, use only twrp 2.8.x.x to format the internal sdcard. I'm using 2.8.7.0 twrp version by Barbarosa. I don't know if other twrp versions support ext4 on internal sdcard.
Sent from the center of the galaxy
Thanks for the solutions. So now if I only need to swap internal sd and /data, i just need to flash 3rd script? I'm quite confusing about partitioning and memory stuffs
newguyknowsnothing said:
Thanks for the solutions. So now if I only need to swap internal sd and /data, i just need to flash 3rd script? I'm quite confusing about partitioning and memory stuffs
Click to expand...
Click to collapse
You have to have twrp 2.8.7.0, then format internal sdcard as ext4 (wipe settings) and then flash the zip...
Sent from the center of the galaxy
Yes, formatting internalSD as ext4 is tricky. My recovery was broken. Probably formatted something else. It wasn't your script.
However I have no volume up button on my phone (fell out) - no fastboot. And just volume down button (flash mode) and a somewhat broken USB cable. Phone not recognized by flashtool at all...
cojocar.andrei said:
You have to have twrp 2.8.7.0, then format internal sdcard as ext4 (wipe settings) and then flash the zip...
Sent from the center of the galaxy
Click to expand...
Click to collapse
Ok thanks! One more question, If I somewhat want to undo this, I need to back up the current MM rom before flashing the script? Will the internal sd and /data automtically be swapped back when I restore the back up?
newguyknowsnothing said:
Ok thanks! One more question, If I somewhat want to undo this, I need to back up the current MM rom before flashing the script? Will the internal sd and /data automtically be swapped back when I restore the back up?
Click to expand...
Click to collapse
After swapping the partitions your old backups of the rom will not work anymore (or probably they would just revert the swapping. Anyway if you want to restore a backup that's been done prior to swap it's better to format back by hand the internal sdcard to vfat and data to ext4)
For backing up a rom with swapped partitions you'll have to select the sdcard instead of data partition in the backup options... I did not try it yet...
Sent from the center of the galaxy
Option58 said:
Yes, formatting internalSD as ext4 is tricky. My recovery was broken. Probably formatted something else. It wasn't your script.
However I have no volume up button on my phone (fell out) - no fastboot. And just volume down button (flash mode) and a somewhat broken USB cable. Phone not recognized by flashtool at all...
Click to expand...
Click to collapse
I don't know, sorry. You have to search the brick threads...
Sent from the center of the galaxy
I ran the the link2sd enabler script on my rr573, works like a charm now.
Thank you so much, I needed this!
Didn't swapped the storages yet.
The dream is real!
Congratulations.
Seeking a long time for a script like mm-partition-swapper.zip
Before seeing your post, I had already made the formatting of SD0 (ext4) to try to install Link2SD to work with SD0 without work.
I used the TWRP 3.0.2.
I could easy return the partition to FAT.
I intend to make a clean installation of ROM on my device to then install your mm-partition-swapper.zip script.
As both the "DATA" as SD0 are empty you still think need to format with TWRP 2.8.7?
No way to change this script without the data transfer?
Only formatting partitions and inverted mounts?
If not necessary then ok...but... please clear this my doubts.
Again without getting tired ... very thank you even for your script.
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Just to be clearer, you have to delete all inside /data, unless /media folder.
Salieri99 said:
Just to be clearer, you have to delete all inside /data, unless /media folder.
Click to expand...
Click to collapse
I think the problem with the term 'delete' is that people will think you mean 'wipe'. 'Wipe' and 'format' actually mean different things. The latter is what is actually required.
This method will not Work at 100%
It depends on the encryption Key from the Rom
Deleting /Data without deleting Media will simply Work to have a bootable State of the flashed Rom but your internal Data will be encrypted and your Rom cant decrypt /Data/media anymore also the Recovery after reboot.
it Happens because of a different Decryption Key in /Data
For Safety and Security reasons i would Not recommend doing this, unless you have a Backup.
Smilex93 said:
This method will not Work at 100%
It depends on the encryption Key from the Rom
Deleting /Data without deleting Media will simply Work to have a bootable State of the flashed Rom but your internal Data will be encrypted and your Rom cant decrypt /Data/media anymore also the Recovery after reboot.
it Happens because of a different Decryption Key in /Data
For Safety and Security reasons i would Not recommend doing this, unless you have a Backup.
Click to expand...
Click to collapse
1.the rom boots and can't decrypt data anymore ??? wtf is this ??? a new science ???
2.where do you think encryption keys are stored ??? in the cloud ???
3. a device with FOD requires encryption in data otherwise the FOD will not work !
4. how do you think i built the TWRP for this device ???? (check my first thread in the forum for this device)
You should never talk about things you don't know very well !!!
The world is upside down these days ... and i'm really bored with idiocracy !
Sorry If i have Not so much knowledge.
But i have done your steps above
Went from Evo X to Derpfest Rom
Everything was fine then i realised my Internal Storage was encrypted.
Maybe i forgot to mention ive used Official Twrp Not your twrp, also maybe its my own mistake
Thank you for your serious words.
Smilex93 said:
Sorry If i have Not so much knowledge.
But i have done your steps above
Went from Evo X to Derpfest Rom
Everything was fine then i realised my Internal Storage was encrypted.
Maybe i forgot to mention ive used Official Twrp Not your twrp, also maybe its my own mistake
Thank you for your serious words.
Click to expand...
Click to collapse
All devices with FOD (fingerprint on display) require encryption to work (These are the new standard policies by Qualcomm & Google). If you use a decryption script that you can find here and there ... your FOD will not work !!! It's not a normal fingerprint ... can you understand ???
My TWRP was made 3 months before the official one. It's built by stock official blobs from xiaomi !
The official TWRP uses a generic kernel not official kernel by xiaomi ! So there are and will be always
some stuffs missings !!! That's why there are many people struggling with backups and rom installations !
im almost got it.
But the only except is Dirty unicorns Rom, they need always an internal storage format.
They are not using Public keys
maybe i known why from alex cruz
gringo80 said:
All devices with FOD (fingerprint on display) require encryption to work (These are the new standard policies by Qualcomm & Google). If you use a decryption script that you can find here and there ... your FOD will not work !!! It's not a normal fingerprint ... can you understand ???
My TWRP was made 3 months before the official one. It's built by stock official blobs from xiaomi !
The official TWRP uses a generic kernel not official kernel by xiaomi ! So there are and will be always
some stuffs missings !!! That's why there are many people struggling with backups and rom installations !
Click to expand...
Click to collapse
if i am just going from Miui EU to New or older MIUI Eu roms ... will i have be encrypted also or not ?
gringo80 said:
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Click to expand...
Click to collapse
To avoid encryption problems between flashing different roms the easiest thing to do is just go to lockscreen settings and delete the PIN or Pattern, this will delete the FP stored as well and you can then flash any rom you want without issues. No more encryption problems and no need to flash any zips and kill the FOD.
Also, I always wipe data as well as "internal storage" if changing roms, there's nothing wrong with that... That way I have a perfectly clean start.
gringo80 said:
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Click to expand...
Click to collapse
U used some roms or only your lineage?
This is exactly what I was searching for!
Does this apply to other phones as well? The ones for which ROM developers always ask to format the internal storage on the phone (OnePlus 6T for me)?
Now that I've finally found this thread, I'd like to also know, is encryption the only culprit due to which it's recommended to format all the data? If yes, why wouldn't one simply remove their screen-lock (I assume that will decrypt any data on the phone), change ROM without formatting internal storage and then keep another screen-lock?
Actually, encryption issues jumping from ROM to ROM is more complicated than that if you don’t know what encryption type is used by the ROMs.
A. Sometimes you might need to format (not just wipe) the data partition. If you format the data partition before flashing the new ROM, then you must reboot OrangeFox immediately afterwards, and, most definitely, before doing anything else.
B. If you are moving from a ROM that uses a different encryption protocol (eg, from FDE ROM to FBE ROM or vice-versa), then you must format the data partition preferably after flashing the new ROM, and then boot to system.
C. If you are moving from a stock ROM to a custom ROM (or vice versa), then you must format the data partition.
D. If you boot the newly flashed ROM, and it gets stuck forever on the Google/Android logo, or just dumps you at fastboot or straight back to OrangeFox, this might be a sign that you need to format the data partition.
source : https://wiki.orangefox.tech/en/guides/flashing
You are right Just
gringo80 said:
Hi all,
A lot of people here and there are struggling to boot their new custom roms.
To be short :
=========
format /data (not wipe) is " NOT " mandatory for every new rom installed like many think because this will erase the whole " internal storage ".
To avoid that, just do a simple " wipe ". Then go (with the TWRP file manager) to /data and delete the residual "encryption" folders and files and keep only /media folder.
Doing " format " is only needed when you change your file system (for a kernel reason) : ext4 <=> f2fs !!!
Don't use any " Encryption disabler .zip ", otherwise your FOD will not work !!!
That's all.
Click to expand...
Click to collapse
Thats right just changed my Rom for Crdroid to Spark I didnt format data just WIPED it. The rom Boots up clean. I also deleted the ANDROID folder in case. there were nothing else in the DATA. You must have to Flash Force Decrypt file after flashing a rom