Hey, it's my first time in this forum.
I'm having a problem: I have a lg p500 with a custom rom (which uses app2sd with partitions in the sd card). I use a class 4 4gb sd card. Everything okay till here: I want to use a 8gb sd card in this phone, so I upgraded the custom recovery to version 1.2 (i had 1.0) so I could do a nandroid backup of the ext4 parts + ROM. So I copied evertyhing to new sd card, did a nandroid of the ROM + ext4 partition, copied the 'nandroid' folder to the new sd card, put the new sd card (the 8gb one) on the phone), turned on the phone in recovery mod, did the restore, and reboot. But the phone freezes at the LG Logo. But if I use the OLD sd card I can iniciate the phone correctly. Any ideas on this? :\
I assume you have created a new ext4 partition on your new card manually like you did on your old card right?
Use a Linux os (like ubuntu) to copy everything in the ext4 partition of the old sd card to the new sd card ext4 partition. Then repeat for the fat32.
It should work. It did for me.
Sent from my LG-P500 using XDA App
Yes I created. Well, how do I do that? I don't know how to work with linux or ubuntu :s
I am not sure about the nandroid backup. Have you done it with the same recovery (backup and restore)?
Anyway I would do it without the phone.
You can download and install EASEUS Partition Master --> Home Edition. It has some nice copy features that you can try (Copy partition with fast file-by-file copy to protect your data; Copy entire hard disk to another without Windows system reinstallation; etc.)
Just read and try it for yourself (there are multiple alternatives).
If you can backup and restore nandroid backups using your recovery, then you can use that method to restore your ext partition.
Create a nandroid backup while your old card is still in your phone.
Turn off your phone and remove the memory card.
Put in the new memory card.
Boot into your recovery and partition the new memory card.
While still in the recovery, format it to ext4 using adb shell:
Code:
su
umount /sd-ext
mke2fs -m0 -b4096 /dev/block/mmcblk0p2
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -yf /dev/block/mmcblk0p2
tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
tune2fs -O ^has_journal /dev/block/mmcblk0p2
Now turn on usb mass storage mode (still in recovery under mounts and storage) and transfer the nandroid backup from your old memory card to your new memory card using your computer.
Restore the nandroid backup. If you have the option of advanced restore, use that instead, and just restore the sd-ext partition.
Now boot up your phone (it should work).
Restore the rest of the contents of your memory card.
mmarz said:
If you can backup and restore nandroid backups using your recovery, then you can use that method to restore your ext partition.
Create a nandroid backup while your old card is still in your phone.
Turn off your phone and remove the memory card.
Put in the new memory card.
Boot into your recovery and partition the new memory card.
While still in the recovery, format it to ext4 using adb shell:
Code:
su
umount /sd-ext
mke2fs -m0 -b4096 /dev/block/mmcblk0p2
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
e2fsck -yf /dev/block/mmcblk0p2
tune2fs -o journal_data_writeback /dev/block/mmcblk0p2
tune2fs -O ^has_journal /dev/block/mmcblk0p2
Now turn on usb mass storage mode (still in recovery under mounts and storage) and transfer the nandroid backup from your old memory card to your new memory card using your computer.
Restore the nandroid backup. If you have the option of advanced restore, use that instead, and just restore the sd-ext partition.
Now boot up your phone (it should work).
Restore the rest of the contents of your memory card.
Click to expand...
Click to collapse
EDIT: Can't do the commands (i type adb shell in cmd, and then su and appears "/sbin/sh: su: not found"
EDIT2: There is only one option for nand restore (which I hope it restores the ext4 too). Anyway, did everything you said (except for that adb stuff) and stuck at LG logo again (yay).
marioemp2k7 said:
I am not sure about the nandroid backup. Have you done it with the same recovery (backup and restore)?
Anyway I would do it without the phone.
You can download and install EASEUS Partition Master --> Home Edition. It has some nice copy features that you can try (Copy partition with fast file-by-file copy to protect your data; Copy entire hard disk to another without Windows system reinstallation; etc.)
Just read and try it for yourself (there are multiple alternatives).
Click to expand...
Click to collapse
I'm trying your option, but I cannot make it so the Fat32 partition will have the same exact size, so that the rest is ext4 (btw, in the program my 512mb partition appears as 489,26 mb and ext3, altough it is ext4)
In the this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in 1 the size is bigger altough it is a 512mb partition, so how do I know what FAT32 partition to create, so that the exact partition left is ext3, since I cannot join 2 partitions?
migueel said:
EDIT: Can't do the commands (i type adb shell in cmd, and then su and appears "/sbin/sh: su: not found"
EDIT2: There is only one option for nand restore (which I hope it restores the ext4 too). Anyway, did everything you said (except for that adb stuff) and stuck at LG logo again (yay).
Click to expand...
Click to collapse
The su command is just to make sure you are root. If you have # and not $, you can continue with the commands. They format the partition to ext4.
The other commands don't work either, same error.
EDIT: Finally I made it, using "MiniTool partition wizard home edition"
Related
hello ppl.
i have a microsd 16gb , my rom is behero+ but not working app2sd.
on my microsd 2gb works perfectly.
Suggestions?
Thanks
did you create a ext2 partition for your 16gb card?
yes but see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
read the instructions @ htcpedia.com, he said you need to set-up the ext partition as first one (you have it as second one )
No you did not.
You only have a vfat partition; the 2 others are free space
Try:
mkfs.ext2 -m 0 -O dir_index,sparse_super /dev/block/mmcblk0p2
or replace mkfs.ext2 with mke2fs
adwinp;6495506 begin_of_the_skype_highlighting**************6495506******end_of_the_skype_highlighting said:
No you did not.
You only have a vfat partition; the 2 others are free space
Try:
mkfs.ext2 -m 0 -O dir_index,sparse_super /dev/block/mmcblk0p2
or replace mkfs.ext2 with mke2fs
Click to expand...
Click to collapse
i tested:
mkfs.ext2 -m 0 -O dir_index,sparse_super /dev/block/mmcblk0p2
but not works
I dont know what all "mkfs.ext2 -m 0 -O dir_index,sparse_super /dev/block/mmcblk0p2" is,...
Have you got the latest Amon-Ra recovery?
Just format your card and use the recovery to do your partitioning.
exactly, use amon ra and it will work. and "don't works" is NOT an error message.
hello
i use the latest amon ra and create particion correctly
see:
but app2sd not works
my rom is behero+
I don't know what that screenshot is of,...
But ADWINP said earlier,...
adwinp said:
No you did not.
You only have a vfat partition; the 2 others are free space
Click to expand...
Click to collapse
FORMAT YOUR SD CARD,... THEN,...
(Taken from BTDAG's guide linked in my signature)
btdag said:
.....
2. Restart your phone into recovery mode (Home + Power)
3. Select:
Partition sdcard
Partition SD
Press Home
Swap-size = 0 MB
Ext2-size = 512 MB (recommended)
FAT32-size = Remainder
Press Home
4. Once complete Reboot system now and wait!.....
Click to expand...
Click to collapse
ddotpatel;6505107 begin_of_the_skype_highlighting**************6505107******end_of_the_skype_highlighting said:
I don't know what that screenshot is of,...
But ADWINP said earlier,...
FORMAT YOUR SD CARD,... THEN,...
(Taken from BTDAG's guide linked in my signature)
Click to expand...
Click to collapse
ok done.
but app2sd don´t works again.
kendong2 said:
and "don't works" is NOT an error message.
Click to expand...
Click to collapse
Use BTDAG's guide. There is a section on testing Apps2SD. Use that.
... and again, if it doesn't work,... GIVE DETAILS!!!!!!!
ok i follow the tutorial :
Check A2SD
Please assume it is automatically working unless you can load applications without your SD card inserted. However, here is the process for those who are pedantic about these things (like me ). Many thanks to Villainrom Wiki for this process.
1. Download check.zip from the bottom of this guide.
2. Extract check.sh
3. Download GScript Lite from the market
4. Place check.sh on your SD card in a folder named gscript
5. Open GScript and press:
Menu
Add Script
Uncheck "needs su"
Load File
Select check.su
Save
6. Then click check from the main screen and you will get a readout of whether it is enabled or not.
when finished process the script says: APP2SD IS NOT WORKING..
what more details you want?
i use rom behero+ microsd 16 classe 6
Have you checked the partitions have done correctly? Through the DOSprompt thing or whatever it is.
yes i check the partioned is ok i think...exist another way the create particions?
another tutorial?
lineup said:
yes i check the partioned is ok i think...exist another way the create particions?
another tutorial?
Click to expand...
Click to collapse
Post another screenshot.
I dont know any other ways. Everyone I know has used the Amon Ra recovery to do the partitioning and all is ok.
Maybe your SD is dead?
dead i dont believe. but i think amon ra dont support 16gb.
On my microsd 2gb works fine.
lineup said:
dead i dont believe. but i think amon ra dont support 16gb.
On my microsd 2gb works fine.
Click to expand...
Click to collapse
Post something in the thread for the recovery, he tries to help all the time. It is worth asking.
ok friend .
thanks for all especially your attention and sorry my bad english.
best regards
No worries bruv. Sorry I couldn't help more.
I have been trying various A2SD scripts on Maclaw's new CM9 builds and nothing seems to work.Tried S2E from the android market first but it doesnt work,also tried to flash the dtapps .zip and neither did that work.
I using Titanium backup to check for the external partition and its not detected on both the scripts.
Any Ideas anyone?
The main reason I'm asking this is because thats the only thing holding me back from using CM9 as daily driver as I mostly use my phone for games!!..
Also awsome job Maclaw!!!
same prob here dude :s anyone can help? i used s2e
Sent from my GT-S5830 using XDA App
Link2SD is working.
actually i using a2sd on CM9 beta 1... but have to install the scripts manually with Root explorer!
kevo02 said:
actually i using a2sd on CM9 beta 1... but have to install the scripts manually with Root explorer!
Click to expand...
Click to collapse
how do u do that?
kevo02 said:
actually i using a2sd on CM9 beta 1... but have to install the scripts manually with Root explorer!
Click to expand...
Click to collapse
Please share with us.....
Sent from my GT-S5830 using xda premium
Titanium back has never understood the alternative install methods that A2SD, S2E or Link2SD use. Titanium understands only the old method that uses the FAT32 partition.
Don't use Titanium to manage where apps are installed, or make sure everything is set to internal: What A2SD (symlinks /data/app/ to /sd-ext/app/), S2E (mounts /data/app/ to /sde-ext/app) and Links2SD (symlinks individual APKs from /data/app/ to /sd-ext/) do is fool Titanium and the OS into thinking internal storage is internal when it is actually not.
With Titainium, you need to move all apps to internal storage after you have a working A2SD/S2E/Link2SD -- this will actually move them to the EXT3/4 partition.
What problems do people have with not getting A2SD/S2E/Link2SD working?
its a realy nice info but buddy im rly stucked.. i made 2gb partition s2e recognize the partition. i moved all to sdExt.,but my problem is when i want install or download any apk from market always says : no free space in internal memory. what im making wrong?:s
Sent from my GT-S5830 using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-S5830 using XDA App
Someone can help me? What i did wrong? This are my setup in S2E.
Thx in advance
Sent from my GT-S5830 using XDA App
I don't have an ICS build yet, but I know with CM7.2 - you cannot safely "Montar como ext4" -- it breaks the mounting and S2E fails -- try turning it off and rebooting. You may also need to reformat sd-ext and only try to install using Titanium after you can confirm S2E is really working.
The way I check if S2E is working is to use terminal command [mount | grep "mmcblk0p2"] to check the mounts:
Code:
# mount | grep "mmcblk0p2"
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /data/app type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /data/app-private type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /data/dalvik-cache type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
Here you can see S2E has successfully mounted the device mmcblk0p2 (which is your Ext formatted partition) as /data/app + data/app-private + data/dalvik-cache (/sd-ext is mounted using 05mountsd script in init.d in CM ROMs) -- if you dont see these mounts S2E has failed.
Thanks.for the info.buddy
Device : Samsung Galaxy Ace
Rom: CyanogenMod9 By Maclaw
Fast,smooth...that's my Ace!
I just flashed CM9 Beta2 -- there is no init.d script to mount sd-ext/ and therefore S2E at least will fail to install properly:
Code:
I/MountChecker( 129): NO SD-EXT DIRECTORY YET!!!!!
I/busybox ( 130): S2E: Initialization...
I/busybox ( 130): S2E: /sd-ext not mounted... Exit!
To fix that, I edited /etc/init.d/02gio and added the following:
Code:
busybox mount -t ext4 /dev/block/mmcblk0p2 /sd-ext
After the done; around line 19. Then reboot, enable S2E, reboot and S2E at least works on CM9beta2... Now to try and fix the other bugs...
Working a2sd on CM9 beta 7.
Hi guys,
I just found a way to make a2sd scripts work under CM9 beta 7 by maclaw et al.
The flashable package by darktremor needs at least 8 mb on /system, but as I could discover, maclaw's ROM eats the whole partition space, leaving no room for the scripts to install.
So the trick is to move stuff that is not crucial for the ROM to work. Using a root explorer, I moved youtube and mail apks from /system/app and the bootanim.zip file from /system/media (replaced this one with a stock (GB) bootanim file). This leaves /system with around 11 mb of free space.
After that, reboot your ACEs into recovery mode and flash Darktremor's package (found here - get beta 4). Just in case, I mounted /system and /data even though is not mentioned as a required step. Reboot your phones and open app2sdGUI to manage the script.
And that's all!
Hope this helps.
Best regards from Argentina.
Hi, I made an internal 64 GB SD Card. But again, the internal memory is going to set up programs. Why is that?
Is it normal to have such a system memory? If you do not need to show up 59 gigabytes' Is?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
volkantipi said:
Hi, I made an internal 64 GB SD Card. But again, the internal memory is going to set up programs. Why is that?
Is it normal to have such a system memory? If you do not need to show up 59 gigabytes' Is?
Click to expand...
Click to collapse
Please can you rephrase your question? I do not understand what you are asking.
Also you images are broken.
rootSU said:
Please can you rephrase your question? I do not understand what you are asking.
Also you images are broken.
Click to expand...
Click to collapse
I make my memory card as internal memory but my phone still use phone memory.
https://www.dropbox.com/s/9xsg4s50abs1d1m/Screenshot_2013-06-17-10-17-25.png
https://www.dropbox.com/s/7y3sb9s2wkvy5pa/Screenshot_2013-06-17-10-17-46.png
apps will still be installed to the internal memory, because it only swaps the /data/media, and apps are installed into /data/
Glebun said:
apps will still be installed to the internal memory, because it only swaps the /data/media, and apps are installed into /data/
Click to expand...
Click to collapse
Exactly this ^^
Internal /sdcard is 11.35 GB but it is shared with /data so both /data AND /sdcard use that 11.35 GB
All you have done is swap /sdcard with /extSdCard, but apps still go to /data so that 11.35 GB still gets used.
rootSU said:
Exactly this ^^
Internal /sdcard is 11.35 GB but it is shared with /data so both /data AND /sdcard use that 11.35 GB
All you have done is swap /sdcard with /extSdCard, but apps still go to /data so that 11.35 GB still gets used.
Click to expand...
Click to collapse
How do I use the most effective. I want to use, such as built-in Card.
volkantipi said:
How do I use the most effective. I want to use, such as built-in Card.
Click to expand...
Click to collapse
To break it down (simply), your internal memory consists of:
/system partition - Where the ROM goes
/data partition - Where your Apps and settings are stored
So all (user) apps install to /data/app and all the basic app data (settings) goes to /data/data (as do your rom settings such as Which ringtone, alarm times etc)
Usually /sdcard is an external Micro SD card. But here, Samsung have made the internal memory 16 GiB in size. So in the /data partition, they have put /data/media which is also your /sdcard.
Android looks for /sdcard and it is "redirected" to /data/media.
What you have done is swapped the mount point for /extSdCard (external sdcard) and /sdcard. So when android looks for /sdcard, it is "redirected" to you external sd card. When android looks for /extSdCard, it is "redirected" to /data/media
Hope this clarifies,
rootSU said:
To break it down (simply), your internal memory consists of:
/system partition - Where the ROM goes
/data partition - Where your Apps and settings are stored
So all (user) apps install to /data/app and all the basic app data (settings) goes to /data/data (as do your rom settings such as Which ringtone, alarm times etc)
Usually /sdcard is an external Micro SD card. But here, Samsung have made the internal memory 16 GiB in size. So in the /data partition, they have put /data/media which is also your /sdcard.
Android looks for /sdcard and it is "redirected" to /data/media.
What you have done is swapped the mount point for /extSdCard (external sdcard) and /sdcard. So when android looks for /sdcard, it is "redirected" to you external sd card. When android looks for /extSdCard, it is "redirected" to /data/media
Hope this clarifies,
Click to expand...
Click to collapse
I copied all the files. However, there was no change.
volkantipi said:
I copied all the files. However, there was no change.
Click to expand...
Click to collapse
All what files? What are you expecting to change?
Sent from my GT-I9300 using Tapatalk 2
I was trying to backup the stock rom to the external sd card but does not work. Its like the card has 0 space.i had to do it to the internal sd card.
android-incredible said:
I was trying to backup the stock rom to the external sd card but does not work. Its like the card has 0 space.i had to do it to the internal sd card.
Click to expand...
Click to collapse
I had the same issue. I tried otg and that was recognized fine....Not sure why.
I am assuming that your sd card is exFat. It needs to be formatted to Fat32 for twrp to recognize it.
BladeRunner said:
I am assuming that your sd card is exFat. It needs to be formatted to Fat32 for twrp to recognize it.
Click to expand...
Click to collapse
thanks, My desktop don't have that option fat32. has exfat and ntfs.
android-incredible said:
thanks, My desktop don't have that option fat32. has exfat and ntfs.
Click to expand...
Click to collapse
Right, Windows doesn't format to Fat32 natively. There's a free program you can download that will do it though but I don't remember the name of it atm.
I have a 64gb SD card. I used Aparted from the app store to format it to fat32. Rebooted into TWRP and it allowed me to backup to external SD. The app is free and was very quick on the format
https://play.google.com/store/apps/...arted&pcampaignid=APPU_72c5VMa-JMX2yQT_jYD4CQ
Format with TWRP and to ext3 or 4. But only prob is windows doesn't read those formats. I use *nix so I am fine but Fat32 via another option works just as well. Only now you will have file size limits. Ext doesn't.
edif30 said:
Format with TWRP and to ext3 or 4. But only prob is windows doesn't read those formats. I use *nix so I am fine but Fat32 via another option works just as well. Only now you will have file size limits. Ext doesn't.
Click to expand...
Click to collapse
I have a 64gb as card. Could you tell me which settings should I choose?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's partition. Dont use that. Wipe the SD card and select ext3 or ext4. I use 4. Just know you will not be able to read that SD card on a windows box.
edif30 said:
That's partition. Dont use that. Wipe the SD card and select ext3 or ext4. I use 4. Just know you will not be able to read that SD card on a windows box.
Click to expand...
Click to collapse
Thanks. Yea, someone pointed that out to me in a different topic. I mixed myself up I guess.
Can u backup to internal memory than manually transfer to sd with an explorer?
Quick Boot, from Sirius, on the Play Store is very handy. (A random mention, but I vastly prefer it to access TWRP compared to futzing with the power button)
You can use TWRP to reformat to fat, which is then usable by both TWRP and the system, though you will have a 4GB size limit on a single file.
Back up your external sd card.
Start TWRP
Wipe
Advanced wipe
Check the external_sd box
Repair or change file system
Change file system
Select fat
TWRP will reformat the external sd to fat. Reboot and restore whatever files you had copied off the external sd.
If you use FAT you will not be able to backup a stock image. There is a file size limit. Use Ext.
edif30 said:
If you use FAT you will not be able to backup a stock image. There is a file size limit. Use Ext.
Click to expand...
Click to collapse
I was able to create a backup on my Fat32 formatted SD card. The file size limit is 4gb and the size of my backup was 3.8.
BladeRunner said:
I was able to create a backup on my Fat32 formatted SD card. The file size limit is 4gb and the size of my backup was 3.8.
Click to expand...
Click to collapse
I will rephrase... Not all backups will be the same size. Case in point mine is 6g. So if the backups will be under 4... FAT is an option.
Have you confirmed that option works with both TWRP and when running the system (sd accessible for read/write)?
markfm said:
Have you confirmed that option works with both TWRP and when running the system (sd accessible for read/write)?
Click to expand...
Click to collapse
Which option are you talking about? I can create and restore tibu back ups from my SD card plus my music is stored on my external as well. Note that I have the KK SD card full access exposed module installed.
I'll try ext, too. In the original thread people had tried several options.
Ok I reformatted to fat 32 with a mac computer and now I can back up my stock rom to the external SD card..
edif30 said:
I will rephrase... Not all backups will be the same size. Case in point mine is 6g. So if the backups will be under 4... FAT is an option.
Click to expand...
Click to collapse
The TWRP backup functionality chops things into chunks that do work with a fat format. It looks like it divides at about 1.5GB boundaries.
When I did a TWRP backup, onto my TWRP-fat-formatted SD, I see two different system files in the backup folder, system.ext4.win000 (1.49GB) and system.ext4.win001 (618 MB). Similarly I have several data.ext4 files, the largest showing 1.51 GB.
As long as a single file isn't over 4 GB size, TWRP appears to be entirely happy with a fat external SD.
For kicks I might try shoveling a single > 4 GB file into my internal storage, to see if TWRP chops that single file up, though in my own use case that isn`t an issue.
It`s all good, having TWRP is a big relief to me
I have an f2fs volume I want to mount. The problem is, every time I look up "Android" and "f2fs", what comes up is internal storage. I'd rather stick to ext4 storage for the time being. What I want is to mount my f2fs volume just like my Linux laptop can without any issues. I know if I want things to work with windows I need exfat, but I have no interest in windows functionality. I just need my storage drive to work on Linux based systems. Windows doesn't interest me.
I'm on a rooted OnePlus 7 Pro and am willing to flash. Oxygen OS 10 OB5. (latest beta)
If mounting f2fs volumes is impossible on Android - a system based on the Linux kernel, I'd love to know why is that so. I was considering building a kernel from source, as I've written a game in C and believe I'm experienced enough to build a kernel at this point.
Thanks in advance!
Nó information. sadly
Check the below reply.
Instead of editing this message, i mistakenly replied again.
so, erased this message
@namhoang235
Its possible to mount f2fs/ext4 microSD / usb-otg on android.
i use f2fs since 2017 for microSD on Android.
u need to be rooted, and, a your need to have kernel f2fs-support.
if you can format /data as f2fs and mount it.
then, youtl already have f2fs support.
else you can use any custom kernel with f2fs support.
as (on 2018) for my asus x00td device, i requested @Sakhtlonda69 to add f2fs support in his custom kernel build.
(and, he did it!)
----
these are few values , which u need to know, to execute the below commands
# YOUR_DEVICE_NUMBER = the exact partition which is your memory card's 1st partition.
# If you have a device with UFS storage (not eMMC), then, microSD will be most likely at "mmcblk0p1"
# If you have a device with eMMC Storage (not UFS), then, microSD will be most likely at "mmcblk1p1"
# If you still can't understand what I'm saying,
# Make sure your memory card is inserted,
# then,
# just go to /dev/block from any rooted file manager
# search "mmcblk1" there.
# if it only shows these 2 files: mmcblk1 and mmcblk1p1
# then, "YOUR_DEVICE_NUMBER" is "mmcblk1p1"
but, if you can't find anything with "mmcblk1"
#then, search "mmcblk0" there.
# if it only shows these 2 files: mmcblk0 and mmcblk0p1
# then, "YOUR_DEVICE_NUMBER" is "mmcblk0p1"
so, "YOUR_DEVICE_NUMBER" is actually either "mmcblk0p1" or "mmcblk1p1"
WARNING: (If you format any wrong system's internal storages partition, your device will most likely be bricked!)
Understand?
---
#---Format your microSD part with f2fs---#
simply unmount the memory card from Settings > Storage.
then, launch Terminal Emulator/ Termux App
(make sure you have root)
enter below 2 commands one by one:
su
make_f2fs -f /dev/block/YOUR_DEVICE_NUMBER
#---Formated successfully---#
-----
Now reboot your device
After reboot your device show a notification that your Memory Card is corrupted!
(because most of the android system can't mount anything except fat/exFAT for Memory Card - it's normal)
---
to mount the microSD (Memory Card),
Launch Terminal/Termux: and, enter below lines one by one:
(YOU NEED TO ENTER THESE LINES EVERY TIME AFTER YOU REBOOT YOUR DEVICE)
su
mkdir -p /mnt/extsd
mkdir -p /sdcard/_MemoryCard_
# Mount f2fs-microSD at /mnt/extsd
mount -t f2fs -o rw,nosuid,nodev,noatime,noexec,discard,fsync_mode=nobarrier /dev/block/platform/soc/*.sdhci/mmcblk*p1 /mnt/extsd
# Bind using sdcardfs f2fs-microSD from /mnt/extsd to /sdcard/_MemoryCard_
mount -t sdcardfs -o rw,nosuid,nodev,noatime,noexec,fsuid=1023,fsgid=1023,gid=9997,mask=2 /mnt/microSD /mnt/runtime/default/emulated/0/_MemoryCard_
----
Now,
microSD is mounted under Internal Storage's _MemoryCard_ folder.
---------
(Extra things)
If you dont want to show Memory Card Corrupted (annoying) Notification on each boot,
simply edit your /vendor/etc/fstab* file.
(it will be under : /vendor/etc/fstab.qcom or /vendor/etc/fstab.default or /vendor/etc/fstab.emmc)
(if you have more that one fstab, edit all)
Edit fstab* :
Find the line contains
"/devices/platform/soc/ ......... /mmc_host*"
add a "#" at the starting of that line (without quotation marks)
and save that file.
Reboot your device.
Now, It won't show any corruption device notification.
afridi.shahriar said:
@namhoang235
...
Click to expand...
Click to collapse
thank for your suggest, but i use android 11 and sdcardfs and mnt/extsd seem like changed,
i try to replace by storage/sdcard1 but it doesnot work
also try to edit fstab from auto to f2fs but it not show my sdcard, my rom support f2fs already
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}