Related
which one is better? ext2, ext3, ext4 or FAT32? and using what tools I should partition the sdcard?
I am using cm9.2.2
before that, I partition sdcard with Amonra Recovery with ext2 and use link2sd and have a problem, some times sdcard removed unexpected, when I reboot sdcard is not read, I pull out the sdcard and insert, and sdcard read normally. I reboot and sdcard not read again, I do this many time and finally can read sdcard. but it happens over and over again. I try to format the phone and install app, move app like unrooted phone, the sdcard work fine..when I try use ext2 with link2sd some times its happend again.,
help me..sorry for my bad english, I am Indonesian.
thank you before..
If you want to know what other people use to do this here I come:
How I make the ext partition:
Minitool partition wizard (windows)
Gparted (Linux)
Clockwork 6.0 (only for CM10+)
I didn't have any trouble with that programs, but be careful with the Clockwork because formats ALL the SD card, the ext and the fat partition, so make sure you do a backup of the SD.
Format of the second partition:
Always ext4
Link App
Link2sd is the best, other caused troubles over the time (reboots, not reading the sd, not reading the ext partition, etc)
chalo99 said:
If you want to know what other people use to do this here I come:
How I make the ext partition:
Minitool partition wizard (windows)
Gparted (Linux)
Clockwork 6.0 (only for CM10+)
I didn't have any trouble with that programs, but be careful with the Clockwork because formats ALL the SD card, the ext and the fat partition, so make sure you do a backup of the SD.
Format of the second partition:
Always ext4
Link App
Link2sd is the best, other caused troubles over the time (reboots, not reading the sd, not reading the ext partition, etc)
Click to expand...
Click to collapse
before that, I've use ext4, but cm9 not support, I change the kernel and still not support ext4, when I use ext3 its work fine..,
mirul_up said:
before that, I've use ext4, but cm9 not support, I change the kernel and still not support ext4, when I use ext3 its work fine..,
Click to expand...
Click to collapse
I used ext4 in all CM from 7 to 11 and no trouble, but always formatting after every wipe with gparted or minitool, because Clockwork 5.0 seem to not format well the ext partition, so after every wipe you should reformat with those programs.
From my experience use ext3, it is good and compatible with everything, allmost
maharu567 said:
From my experience use ext3, it is good and compatible with everything, allmost
Click to expand...
Click to collapse
+1
EXT4 has a tendency to corrupt
(At least for me )
Sent from my GT-I9082 using Tapatalk
Ext4 works great.
(Partition it with AmonRa recovery for a 100% guarantee of success, buggs with clockwork)
Sent from my LG-P500 using xda premium
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.
Does Samsung Galaxy S8+ have F2FS and ext4 support?
I'm running the stock ROM and I've flashed TWRP and rooted the device.
I want to have F2FS filesystem on /data and /cache.
I also want to format the external sd card with F2FS or ext4.
Thanks in advance.
I've been trying to partition my SD card, but all steps I take to try and diagnose why I am unable to partition the card is getting me nowhere.
Initially, I used gparted on my laptop to partition the SD card with a v-fat partition and a f2fs partition, both primary partitiond. This was when I found out that no matter what I do the second partition on the SD card, it doesn't seem like the format actually takes. Whatever tool I use complete the partitioning and formatting steps successfully by all appearances but it doesn't seem like the partition is ever actually formatted. What I mean by that is that no matter what the second partition is it never mounts. I get an invalid argument error or bad super blocks and so forth. I can make the first partition anything I want: fat, v-fat, f2fs, ext4 and so forth and that will mount in my terminal without issue, but no matter what I do the 2nd partition always fails to mount. I've also noticed that blkid never has any fs info for the second partition. It gives me the partition UUID and that's all, while the first partition has both part UUID & fs UUID.
I've even gone so far as to just recently get a brand new SD card thinking that perhaps the first SD card was corrupted but I'm still getting the exact same behavior. Also of note is that in gparted when I try to create a secondary partition, I'm unable to mount the second partition so I don't think it has anything to do with my device. I've tried using fdisk, gdisk, parted in the terminal and I've tried using extended partitions and logical partitions and only primary partitions. I've done this before in the past so I know that it is possible.
It almost seems like the SD cards that I have are simply not capable of being partitioned in any way but it's strange that I now have two 512 GB SD cards and they're both giving the exact same behavior so I'm thinking that I'm missing something obvious. Any help anyone could provide as far as trying to figure this out or debug what's going on what I'm doing wrong would be greatly appreciated.
Thanks,
Ryan
only the first partition is mounted from vold. that is normal behaviour on every device. if you want have all partitions mounted automatically install LineageOS.
furthermore, although sdcardfs supports ext4, f2fs, for file transfer via USB MTP afaik fat32, exfat or ntfs is required.
what do you need f2fs partition for? maybe I can point you to workaround.
aIecxs said:
only the first partition is mounted from vold. that is normal behaviour on every device. if you want have all partitions mounted automatically install LineageOS.
furthermore, although sdcardfs supports ext4, f2fs, for file transfer via USB MTP afaik fat32, exfat or ntfs is required.
what do you need f2fs partition for? maybe I can point you to workaround.
Click to expand...
Click to collapse
I don't need anything to mount automatically. I'm saying I can't manually mount these partitions. I also don't need f2fs, that was just an example. I've tried multiple partitions that are just fat, ext4 and many other combinations. Under no partition scheme can I get anything other than the first partition to mount--using the mount command as root.
can you please try gdisk binary from here
https://forum.xda-developers.com/t/...-on-qmobile-z8-with-bricked-dead-emmc.3712171
please post the result of partitioning and formatting.
if you're interested in alternative solution, you can actually format the whole MicroSD card as exfat, and create ext4 partition image on top as regular file. I have done that for my mothers Huawei for Link2SD because it doesn't support adoptable storage.
aIecxs said:
can you please try gdisk binary from here
https://forum.xda-developers.com/t/...-on-qmobile-z8-with-bricked-dead-emmc.3712171
please post the result of partitioning and formatting.
if you're interested in alternative solution, you can actually format the whole MicroSD card as exfat, and create ext4 partition image on top as regular file. I have done that for my mothers Huawei for Link2SD because it doesn't support adoptable storage.
Click to expand...
Click to collapse
I have tried with gdisk but I can try with that specific version and report back. I understand we can create imaged file systems, but one of the main reasons I do this is that I find fat partitions are fickle and can easily be corrupted where the whole partition requires wiped. By having a non fat partition I use that as a better backup option where I find it's easier to recover data in case of corruption or other issues. For such use, being tied to the fat FS would still incur the possibility of data loss so that doesn't work for my purpose.
Thanks and I'll report back,
Ryan
oh I wouldn't rely on f2fs for backups it still has bugs and there are no recovery tools for f2fs
https://forum.xda-developers.com/t/4550931
https://android.stackexchange.com/q/250389
alecxs said:
oh I wouldn't rely on f2fs for backups it still has bugs and there are no recovery tools for f2fs
https://forum.xda-developers.com/t/4550931
https://android.stackexchange.com/q/250389
Click to expand...
Click to collapse
Thanks for the suggestion to use gdisk. I downloaded the version you linked, but I still get the same behavior. I believe it is related to the fact that only the first partition gets a filesystem UUID in blkid. I'm not sure what this means, but it seems clear that the second filesystem isn't being properly created no matter what I do.
that's strange, especially the fact you tried on PC too. on the phone, can you create partitions inside a blank disk image just for double check to rule out kernel issue?
I'll give that a try and report back
alecxs said:
that's strange, especially the fact you tried on PC too. on the phone, can you create partitions inside a blank disk image just for double check to rule out kernel issue?
Click to expand...
Click to collapse
Yeah I'm able to create an image, partition it into a vfat & ext4, then mount both of those partitions.
can you dd the file into mmcblk1 for testing purposes?
alecxs said:
can you dd the file into mmcblk1 for testing purposes?
Click to expand...
Click to collapse
Sorry this isn't clear to me. What am I using to dd into the partition, and do you mean mmcblk1p1/2? As mmcblk1 is the whole disk.
Thanks,
Ryan
yes, I meant the whole disk you created a test file that contains MBR or GPT and two partitions including UUIDs and file systems? If you dd it into the mmcblk1 it should create 1:1 copy of that disk image with two partitions including partition table.
Well I'll be:
Code:
/dev/block/mmcblk1p2 on /data/data/com.termux/files/home/i2 type ext4 (rw,relatime,seclabel) /dev/block/mmcblk1p1 on /data/data/com.termux/files/home/i2 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
Code:
/dev/block/mmcblk1p2 23M 46K 23M 1% /data/data/com.termux/files/home/i2 /dev/block/mmcblk1p1 4.9M 0 4.9M 0% /data/data/com.termux/files/home/i1
I can possibly use gparted to just resize those! Any thoughts on what was going on, why this method worked? Hrmm looks like resizing fat could be a challenge, but this certainly gets me closer!
there is also parted binary you can use on phone
I have it and I'm playing around with it, thanks for all your help