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?
Related
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
that's weird since the app working. what ekstension do you have on sd card fat? fat32?
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Your sd-ext files are actually in data/sdext2, not in /sd-ext.
Also Try using Amonra 3.0.6, overall it has better sd-ext support, I find it mounts and wipes things like dalvick cache inside the sd-ext partition as well , which is handy, unlike CWM.
Thanks for all your replies!
Sdcard file system is fat32. For the partition I have no idea as cwm didn't ask for any specific (e.g. ext2/3/4) and I haven't seen any way to get this Info...
Anyway, following this thread, I did find that all the app/data is in /data/sdext2- not sure what it means in terms of nandroid backup& recovery but it looks more reassuring..
As to RA recovery, I'm not in particular in love with cwm- it is just what I'm used to from other android devices I've been using. Actually on my htc mt4g I was using ext4 touch recovery and that one I really liked, but it is not supported in lots of devices. That phone was stolen, unfortunately. I'll give it a try, though.
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
DavisNT said:
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Click to expand...
Click to collapse
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
jaibar said:
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
/data/sdext2 is the mountpoint for the ext4 partition thats on your sd card, physically its obviously on your sd card, but If you use linux, data/ is where the all partitions other then home partition get "attached"/mounted to, the 11link2sd script made by link2sd in yout init.d folder actually mounts it sdext2, the name means nothing, just something link2sd names it as.
---------- Post added at 08:40 PM ---------- Previous post was at 08:30 PM ----------
So Basically nandroid will not back it up under /data/sdext2 as the script runs after recovery, the best way to backup apps that are on the ext partion is back them up using Titanium Backup, as that saves the real apks, and when you restore all your apps, select link2sd to automatically move them to sd-ext partition.
Hi at all,
at first sorry for my bad english.
I had a similar case. If I made a backup with cwm 5.0.2.7, cwm cant mount/read the sd-ext.
In a other thread a user wrote, that cwm 5.0.2.8 had problems with the sd-ext.
And he does downgrade to cwm 5.0.2.0, and than cwm will work.
So, I did this:
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Now, Rommanger made the installation with cwm 5.0.2.0. to my phone.
After this i go in to the recovery and made my nand-backup. It works perfekt!
No problems with the sd-ext, after I did this.
May be this will help.
Fietz said:
Hi at all,
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Click to expand...
Click to collapse
Thanks for the tip..
I have tried in the past to flash cwm 5.0.2.0 via Rom Manager, but I kept getting an error message, so I gave up.
Now I thought to give it a second chance, but as it fails to flash with Rom Manager (in the menu when I choose LG optimus one I don't get any choice between old BB or new or anything- it just reflashes 5.0.2.7) and from the "all recoveries menu I can only choose 5.0.2.0 but it gives an error message), so I downloaded the zip files from this thread http://forum.xda-developers.com/showthread.php?t=1523050 (including also Amon Ra 3.06) and tried to manually flash from recovery.
It flashed and showed recovery as "5.0.2.0" but nothing worked- every submenu that I tried to enter was black screen (with the CWM logo on background) and it gave me the creeps- I don't like being stuck without a functional recovery so I rebooted and flashed 5.0.2.7 again from Rom Manager.
I'll try to flash Amon Ra and see how it works.
[EDIT] flashed AmonRa 3.06 and it seems to work fine- able to mount/unmount all partitions including sd-ext, and it also has an option to check each of them in separate during nandroid backups.
A noobish question: it has also an option to include the ".android_secure" . Isn't this one a redundancy with sd-ext (e.g. contains all the apps/data that has been moved/linked2sd)?
jaibar said:
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
Click to expand...
Click to collapse
Hi, Jaibar
I have LG Optimus One with JB 4.2.2, CM 10.1.
Here what I have done in order to gain extra space on my internal memory. All the steps that you have followed are the same as I did. BUT! There are two important things that I have followed that had greatly helped to succeed:
1) For every 100Mb internal memory - NO MORE than 512Mb of SD card memory(for my LG I have separated 965Mb on the SD card)
2) INT2EXT+ works with EXT2/3/4 partitions BUT INT2EXT4+ works with ONLY EXT4 partition. After I have watched this short video, and this blog post I have been able to restart my phone with extended internal memory.
Believe me, for three days I have been flashing my phone, trying to find the correct way. At the end I have noticed that the problem was that I couldn't mount /sd-ext I thought that maybe following this two rules will help - and it did!
I hope that it will help! Good luck
There has been a lot of questions throughout various threads about converting your Note 3 file system to f2fs. This is a simple way to convert your current file system to f2fs on N9005 and N900T. I have not tried it on other Note 3 variants because I do not have access to them but I would think that the change would be similar.
First off, you need to have a f2fs compatible ROM installed with compatible f2fs kernel. I used Shinto [Shuriken] Kernel from @CekMTL to do this on N9005 and N900T. The kernel can be found HERE .
If your ROM and kernel meet the above requirements:
1. Backup everything you want to keep from your internal SD card, this process will wipe internal SD.
2. Update TWRP to the latest and greatest 2.8.1.0, go HERE
3. Drop to TWRP
4. IF YOU MISSED IT BY NOT READING #1, YOU WILL LOSE ALL PERSONAL DATA ON YOUR INTERNAL STORAGE BY DOING THIS!
5. Run a FULL NANDROID BACKUP to your External SD Card.
6. Go to SETTINGS and unselect (un tick) “use rm -rf instead of formatting” (We want TWRP to actually format with f2fs)
7. Go to Wipe and Choose Advanced Wipe
8. Select System and choose change or repair file system
9. Choose f2fs and go through the steps where it tells you that all data will be lost and apply it.
10. Follow steps 7-9 for Data and Cache one at a time.
11. Go to SETTINGS and select (tick) “use rm -rf instead of formatting” (We don’t want to restore back to EXT4)
12. Do a restore, but ONLY CHECK SYSTEM & DATA for restoral, NOTHING ELSE IS NEEDED.
13. It will tell you that your backup was made with ext4 and may not boot, don't worry it will boot.
14. After restore, reboot your device. First boot will take a few because it's a new file system and your apps will have to reconfigure themselves, etc
FROM @CekMTL : As for the external SD card and f2fs, it is mounted differently and your Kernel WILL NOT SUPPORT IT [f2fs on external SD card], so DO NOT format your external SD card to f2fs! (hopefully I said that enough times)
***DISCLAIMER***
You do thisl at your own risk! It has been tested completely and works perfectly on N900T as well as N9005. If you wreck your phone, soft brick, hard brick, your battery explodes, your screen jumps up and cuts you, your credit score tanks, your wife leaves you, your dog leaves you, your cat kills you, the sky falls, or anything else... it is not anyones fault but your own. Thank you
Updater process ended with error
Ok guys, just as the title states; I am having no luck in converting my /data filesystem to F2FS using TWRP versions 2.7.0.0 - 2.8.7.0 and its f***ing killing me as every other aspect of the tablet works flawlessly. I have modified many tablets/phones and I most definitely know what I am doing so hit me with whatever you've got and I will understand perfectly.
I am on the latest version of the bootloader and its unlocked
TWRP .2.8.7.0 recovery
flashed omni 5.1 and changed /data from ext3 to ext4
All diagnostic access points (Fastboot etc) work perfect and I've also enabled NVFLASH and have brickproofed myself using flatline.
Anytime I go to Repair/Change and choose F2FS for /data it simply fails and says the following
"Unable to wipe /data"
"Unknown MTP message Type 1"
"Error changing filesystem"
This has been for "EVERY" version of TWRP from 2.7 to Current 2.8.7.0 every time I try and I am about to break this thing over my leg.
I do not ever post unless I have done due diligence and combed/searched through the the forum using any string and phrase I can think of relating to the topic. All instructions which involve changing to F2FS within every post related to the topic have failed me. Absolutely ANY help on this would be GREATLY appreciated!!
i will share with you my experience with flashing the tf300t and formatting. everithing went smooth... just a lot of preparation...
firstly i flashed twrp 2.8.x.x from kang
http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479
than i copyed all needed files to my external SD card:
image file katkiss 5.1 #25
superSu
gapps image file
and K.A.T tool apk
device buttery must be full..
After being sure that i have everything on my sd card i entered twrp recovery and went to wipe everything exept of external sd card.
second i went to format /data to f2fs file system
third i flashed Katkiss image
fourth SuperSU for root access
fifth gapps
sixth wipe delvick/cache
Everyything went smooth as silk... hope that this helps you..
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.
//////////// USE IT AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY FAILURE OR BRICKED DEVICES /////////////////
THIS IS NOT a PUBLICITY for Any ROM or KERNEL
They are Simply just what i use
I have successfully changed my data partition to F2FS and using arter kernel as well
Also I have managed to get the Data back in place so after the whole operation all my ROM data are intact
NOTE THAT YOUR ROM & KERNEL MUST SUPPORT F2FS TO BE ABLE TO BOOT
Note that changing any partition filesystem from a type to another will require formatting that partition
From what i understood converting /system and /cache to f2fs is useless hence I converted /data only as it the main partition that you write on
First of all your internal storage is in /data/media/0 path and hence it will be wiped
I used the official TWRP to be sure of no issues
Take care of the 12th step as if it was missed you will start from scratch >> CRITICAL
Note that Fstab file already contains DFE so if you are unecrypted like my case flashing Fstab keeps me unencrypted without flashing DFE
Now let's start the operation of converstion of/data from ext4 to f2fs in a step by step guide
1- BOOT TO RECOVERY
2- TAKE A FULL NANDROID BACKUP ( MOST IMPORTANT IS THE DATA PARTITION )
3- TAKE A FULL CLONE OF YOUR INTERNAL STORAGE while you are in TWRP( To PC either via MTP or adb command and i prefer the adb method as it ensure that all your files are copied including hidden files )
4- WIPE > Format Data > Yes ( it is a factory reset and all your internal storage will be wiped )
5- Reboot to recovery again
6- Wipe > Advanced Wipe > Check Dalvik , cache , system and Data > Wipe and DONOT reboot to recovery
7- Connect cable again and copy the FSTAB Tools ZIP file only
9- Flash the FSTAB TOOLS File
9- Wipe > Advanced Wipe > Check Data ONLY > Repair or Change file system > F2FS > Change File system
10-Copy via cable whatever you need from your internal storage or the whole of it as your wish
11-Ensure that the TWRP Backup you took in step 2 is copied to internal storage again
12-GO TO TWRP SETTINGS and Tick the 3rd option in the first TAB ( it is called use rm -rf instead of formatting )
13-The above step ensured that when you restore Data partition TWRP won't format it again to ext4 and leave it as f2fs
14-Restore > Choose your fresh Backup > RESTORE DATA PARTITION ONLY ( you will see a message that you are restoring a backup taken of ext4 filesystem , donot worry it worked in my case )
15-Flash the following in order : Vendor > ROM > Fstab File ( NOT the tools one ) > Gapps > Arter97 kernel > Reboot
16-You should boot to the OS with all your data ( settings ) like they were intacted and now the /data partition is f2fs
17-Restore your internal storage if you still didnot do it in step # 10
18-Reboot to recovery and Flash Magisk ( optional )
Notes :
- I though that 4th step was useless however it is mandatory as it erases Vendor or something similar
- I though that 6th step is duplicate to 4th step and was useless however without it TWRP didnot change filesystem to F2FS
- The FSTAB must be flashed after every vendor update ( it can be before or after ROM in the sequence , the most important that it is after every Vendor BEFORE YOU BOOT )
- I didnot flash magisk in step # 15 as crCroid recommends that you boot to system one time before you flash magisk
- crDroid default kernel doesnot support f2fs and if i didnot flash arter97 i wouldnot be able to boot
- By this setup i cannot go back to crDroid default kernel anymore unless f2fs is supported by it
- If ROM doesnot support f2fs the system wouldnot Boot as it would not be able to understand the /data partition filesystem
- Ofcourse any Kernel and ROM combo that supports F2FS should be valid to apply this guide
Finally thanks for all the Devs for thier hard work and dedication , You all made our POCO a lovely BEAST
I think this thread is belong to guides&news and discussion forum
thanhnvt194 said:
I think this thread is belong to guides&news and discussion forum
Click to expand...
Click to collapse
Yes i you are right but do not know how to move thread from a forum to the other
Thanks @shouk_1987, good guide. Any chance you can provide a link to the FStab files mentioned in your post?
Is this arter kernel specific? I used shadow kernel and the fstab changes are flashed with the kernel
dgrasley said:
Thanks @shouk_1987, good guide. Any chance you can provide a link to the FStab files mentioned in your post?
Click to expand...
Click to collapse
They are in arter kernel thread in the OP
Thread moved to the correct section.
LTT
So, does this work with crDroid? I ask because both rom and kernel must apparently support f2fs and @gwolfu has indicated crDroid does not.
piet8stevens said:
So, does this work with crDroid? I ask because both rom and kernel must apparently support f2fs and @gwolfu has indicated crDroid does not.
Click to expand...
Click to collapse
crDroid Kernel doesnot for now
While the ROM does
What about my apps and its data, can I restore it back?
Edikuun said:
What about my apps and its data, can I restore it back?
Click to expand...
Click to collapse
Read the guide carefully
You will br able to restore everything but the most part that needs patience is restoring internal storage
works on miui ?
RubenPCA said:
works on miui ?
Click to expand...
Click to collapse
Didnot try but saw other users says it works
Which kernels/ROMs are supported?
Shished said:
Which kernels/ROMs are supported?
Click to expand...
Click to collapse
Read in the OP of the ROM / Kernel you want
A lot aupport f2fs now
a great guide . Any way to do the same(restore data) if ee wanna go back from f2fs to ext4? just in case.
Debraj903 said:
a great guide . Any way to do the same(restore data) if ee wanna go back from f2fs to ext4? just in case.
Click to expand...
Click to collapse
Didnot try but I believe it is the same concept
My internal storage went from 30GB free to 15GB free
Edikuun said:
My internal storage went from 30GB free to 15GB free
Click to expand...
Click to collapse
I am the opposite I have 2 gb increase
Least version for Poco is 64 gb , which version do u have ?
shouk_1987 said:
I am the opposite I have 2 gb increase
Least version for Poco is 64 gb , which version do u have ?
Click to expand...
Click to collapse
It's okay now, I forgot to delete my twrp backup and titanium backup. Anyways, nice guide! Successfully converted to f2fs