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"
}
Related
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"
I want to be able to copy files >4Gb to my Touchpad. This is so I can watch HD movies on the device.
I already tried adding resizing the media partition and adding an ext3fs partition using "Tailor" (a webOS app). Although this is easy and it worked, I couldn't find any way to have this partition mount at boot time and be seen by my Android apps.
There are a couple of posts out there on the web from people claiming that they "reformated" the shared partition (/media/internal) to ext3fs successfully.
Has anyone here done that, and if so (a) how? and (b) were you able to have it mount and be visible from android apps?
Otherwise does anyone have any suggestions please?
cheers
Paul
+1
Sent from my HTC Desire HD using XDA App
Getting somewhere...
I tried again having found out that the ext3 partition I created in webOS is found at /dev/mapper/store-ext3fs
Under Android - everything below is done in Android
I am able to mount this partition to my fake sd card (I just created a folder there called "ext").
Code:
su
mount /dev/mapper/store-ext3fs /sdcard/ext
I found that copying files by USB doesn't work while my ext3 partition is mounted, which is a pain - would be good to get that fixed. Anyone have any ideas?
I am now testing copying over a >4Gb file to my ext3 partition using ftp client. Will take some time on my crappy wifi, hence the comment about fixing USB.
I found that in order to make the ftp process work, I had to give full permissions to this folder.
Code:
chmod /sdcard/ext
I am a noob, so if anyone can help me with a less insecure set of permissions I would be grateful.
I'll post an update later on.
Nah, didn't work. After a few hours of copying I went to bed, this morning the folder is empty. I'm not sure if there was an error or anything.
My suspicion is that it crapped out when it got to 4Gb because even though the partition is ext3, it is mounted at a mount point on a FAT32 partition.
I realised I can test this more easily and eliminate possible network errors or ftp client instability, I'm running
Code:
dd if=/dev/zero of=output.dat bs=1024 count=51200000
within my /sdcard/ext folder (my mount point), this should create a 5Gb file.
I'm expecting this to fail, again because even though the partition is ext3, it is mounted at a mount point on a FAT32 partition. If anyone can help me to mount the partition some other way so its not mounted in a FAT32 partition, or point to another method to overcome the file size limit, I would be grateful.
thanks
Paul
That worked!
dd-ing a large file worked. I think I got my calculations wrong so when it got to >7Gb I just stopped it.
Now it would be great to get this working such that I can use USB instead of ftp to get my movies across.... Anyone?
{
"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"
}
USB transfers not working
Anyone help me identify partition number for my ext3 partition please?
My ext3 partition is all working except when mounted I cannot use USB transfer.
Believe this is because my vold.fstab mounts the first available partition as SD card.
So would like to know correct partition number for SD card and ext3 partition.
I gave up on this in the end. Assured by clearly very clever jcsullins over on the cm touchpad IRC that the partition doesn't get a number and I would not be able to get my USB file transfer working. I also found the available media players (or maybe CM itself at the moment?) unable to cope with my 720P movies.
All is not lost though. I'm having more luck over on webOS using touchplayer and an overclocked kernel.
Thanks to those who tried to help with this!
{
"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"
}
every time i post it at reddit it gets removed, so was getting difficult sharing it
What works
audio
video
wifi
keyboard
trackpoint
touch
android apps
linux
What doesn't work yet
acpi (needs linux people help to make a kernel to chrome os)
bluetooth (easy fix)
battery level
What do you need
one 16gb pendrive
one 8gb pendrive or higher
one gpd pocket (duh)
a lots of patience and free time
First step
Go to CrOS page and download pyro
Download EmydeOS
Download SWTPM.tar and chromefy script
Second step
use a linux or mac pc and dd EmedyOS image to a 16gb pendrive
List all disks:
Code:
in linux: lsblk
in mac : diskutil list
sudo dd if=/path to emedy os/ of=/dev/sdx (where x is your pendrive disk nummber)
Third Step
Boot the flashed pendrive in dev mode
enter in shell pressing press ctrl + alt+fn + f2
type in chronos
in shell follow this:
Code:
sudo su
lsblk (find your drive , usually its mmcblk0)
sudo /usr/sbin/chromeos-install --dst YOURDRIVE (Ex: /dev/mmcblk0)
wait and check if boots
fourth step
download mate ubuntu
flash it into 8gb usb using the mentioned dd command
boot in live usb
open gparted
delete mmcblk0p5
extend mmcblk0p3 to 4gb
fifth step
format ubuntu mate pendrive to extfat
extract pyro image and copy the bin file to pendrive
copy chromefy sh and swtpm to pendrive
boot emedyos pendrive
press ctrl fn alt f2
enter chronos
Code:
sudo su
sudo mkdir /home/chronos/tempfolder
lsblk ( find the 8gb with pyro files, mine was sdb)
sudo mount /dev/YOURDRIVEHERE /home/chronos/tempfolder
cd /home/chronos/tempfolder
sudo bash /home/chronos/temfolder/chromefy.sh /dev/mmcblk0p3 /home/chronos/tempfolderNAMEOFpyro.bin /home/chronos/tempfolderswtpm.tar
sudo mkfs.ext4 /dev/mmcblk0p1
Sixth step
boot into chrome os and boot into shell again
Code:
sudo su
cd /usr/share/vboot/bin/ ./make_dev_ssd.sh --remove_rootfs_verification --f --partitions 2 reboot
Upon reboot go back into shell
Code:
sudo su -
mount -o remount,rw /
mount -o remount,exec /mnt/stateful_partition
download [URL="https://fedorapeople.org/~jwrdegoede/brcmfmac4356-pcie.txt"]this[/URL] file and copy to 8gb pendrive
mount the pendrive
sudo su
sudo mkdir /home/chronos/tempfolder
lsblk ( find the 8gb with file, mine was sda)
sudo mount /dev/YOURDRIVEHERE /home/chronos/tempfolder
cd /home/chronos/tempfolder
cp /home/chronos/tempfolder/brcmfmac4356-pcie.txt /lib/firmware/brcm
reboot into dev mode and complete steup
seventh step
to get sound working
press ctrl alt t into chrome
Code:
type shell
sudo su
mkdir /usr/share/alsa/ucm/chtrt5645 directory and copy the 2 .conf files from here into that dir.
What needs to be done
with the help of linux fans we need to patch the kernel
Kernel patches needed:
MAX17047 Fuel Gauge
BATTERY_MAX17042
BQ24190 Charger
CHARGER_BQ24190
GPIO for Fan Control
GPD_POCKET_FAN
Intel Graphics
CONFIG_DRM_I915
UEFI Framebuffer
CONFIG_FB_EFI
ALSA Sound Card Support
CONFIG_SND_SST_ATOM_HIFI2_PLATFORM_ACPI
eMMC Block Device (ACPI SDIO)
CONFIG_MMC_SDHCI
CONFIG_MMC_SDHCI_ACPI
Wireless
CONFIG_B43
CONFIG_BRCMFMAC
CONFIG_BRCMFMAC_SDIO
CONFIG_BRCMFMAC_PCIE[/INDENT]
References
https://hansdegoede.livejournal.com/17445.html
https://forum.xda-developers.com/ha...talling-official-chrome-os-pc-t3865697/page92
https://github.com/imperador/chromefy
https://wiki.gentoo.org/wiki/GPD_Pocket
thank you so much for taking the time to write a tutorial!
I'm going to try it on my gpd pocket as soon as possible that at the moment is running this build https://kmyers.me/blog/computers/public-preview-chromiumos-for-the-gpd-pocket-1/ .
By chance, in the meanwhile, are there any news about a new kernel with working acpi/bluetooth/battery meter?
Thanks again for the great work you did!
Hello,
I've finaly find a way to mount "hos_data" FAT32 partition into Android, usable with all android apps (after 1 week )
You need Root (Magisk), enable "Global Namespace" in Magisk Manager.
After that i use Tasker to mount at startup :
All you need, is to create "Profile" into Tasker, and theses tasks :
{
"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"
}
You can now share your Roms/Thumbails between Horizon / Android
I hope it can help some peoples ... If people have better solution, without Tasker, please share
Bye
This doesnt help
This has 0 instructions, and isnt self explanitory because because its not even in english like the poat itself is.
Skilarmbabcock said:
This has 0 instructions, and isnt self explanitory because because its not even in english like the poat itself is.
Click to expand...
Click to collapse
You're an idiot. 0 instructions? Really? Instructions are clearly there. Isn't self explanatory, really? 100% self explanatory. Not in English? Can you not read? Everything needed to make this work is written in English. Because because poat blah blah, go learn some English.
thx , and n1 job. and i have found a way to switch the sdcard without turning off.
its tricky , and you must be fast. because when you reboot to hekate when the firat time blackscreens apear, ,, screen turns off ,, in that moment you have to put out the sd card and put in the other one. , but the touchlayout is missing , then you can load any payload with out any dongle or something else.
I followed everything checked it 4 times and it still doesn't show up the only diffrence is I couldn't find device start so I put it as device boot
Have you activate "Global Namespace" in Magisk, your Android is rooted ?
Try to install "Termux" or other terminal emulator, and try to enter same commands manually first.
Go to Magisk, look if Tasker root is actived.
For me these command work fine. It can depend of your SDCard, for me it's mmcblk0 and p1 for partition 1 = mmcblk0p1
I don’t understand can anyone help me getting this to work
Unfortunately, Tasker is a paid app, is there any free alternative ?
Probably just look for a root compatible shell application and run the commands every time manually.
Works great. Thx!!
Hello i finally found tasker and begin this tutotrial but i have an issue at the task 2 "mkdir /mnt/switch-sd" when i launch the task tester in tasker.
I confirmed Root & Global Namespace are activated.
Any idea ?
For those that don't want to pay for/use Tasker, you can run a script in Terminal instead.
Creating a script file in Android OS:
In X-plore (or use what ever file manger you want), go to Internal shared storage "/sdcard". Make sure you are on the root of the sdcard.
In the middle option pane touch "New text file" and a file namer will pop up. Save name as "switchsd.sh" (without the quotations).
Enter the following:
#!/system/bin/sh
mkdir /mnt/switch_sd
chmod 777 /mnt/switch_sd
mount -o bind /dev/block/mmcblk0p1 /mnt/switch_sd
mount -o remount,rw /dev/block/mmcblk0p1 /mnt/switch_sd
echo "Fat32 mounted"
Hit save in the upper right and exit app. (This will be the script file)
Go to the built in LineageOS Terminal emulator and type the following commands.
su
mount -o rw,remount /system
cp sdcard/switchsd.sh /system/bin/switchsd
chmod 555 /system/bin/switchsd
This moves the file to your system/bins folder so you can easily run the script without entering a path.
Now in Terminal emulator run the script by typing, "su" to change user. Then type "switchsd" to run the script, wait a sec and it should now say "Fat32 mounted".
Walla! Enjoy. Do this every time you boot into Android.
Credit:
https://www.pctips4u.com/2016/03/writing-shell-scripts-in-android.html
Karcus said:
Go to the built in LineageOS Terminal emulator and type the following commands.
su
mount -o rw,remount /system
cp sdcard/switchsd.sh /system/bin/switchsd
chmod 555 /system/bin/switchsd
Click to expand...
Click to collapse
It sounds great but i didn't find any LineageOS Terminal emulator in SwitchRoot
keriam said:
It sounds great but i didn't find any LineageOS Terminal emulator in SwitchRoot
Click to expand...
Click to collapse
LineageOS by default does not enable the Terminal app.
If you haven't already, enable developer options.
Then, if you go into the Settings app and search for 'terminal', there will be a "Local terminal" option which says "Enable terminal app that offers local shell access".
However, by many accounts the built-in terminal app is awful, so you may prefer to use another terminal app from the Play Store. (I use this one, but Termux looks like a more popular option lately.)
Hello and thank you for the helpful information.
I found a solution to automatically mount the partition on startup. I use the App App2SdPro. Whit this app you can start a Script as su on boot. Works great for me and the App is free.
Personally I just let XPosedEdge run this script on each keyguard unlock.
init.d might also work.
Great job on this finding!
Forgive me if I'm wrong, but if you're rooted, isn't the SD already accessible from /mnt/vendor/factory ?
urherenow said:
Forgive me if I'm wrong, but if you're rooted, isn't the SD already accessible from /mnt/vendor/factory ?
Click to expand...
Click to collapse
This path may be just added from Android 10 build? This old topic should talking about the past year build?
Has anyone tried doing this on the official new release to mount the partition at a user-accessible location?
urherenow said:
Forgive me if I'm wrong, but if you're rooted, isn't the SD already accessible from /mnt/vendor/factory ?
Click to expand...
Click to collapse
Might not be relevant to this thread but thank you for posting anyway. I didn't know this path existed for Android 10, it makes this process much easier!
Hello,
I need help for TWRP on my Samsung Galaxy A20e. My device is rooted for a while and TWRP is newly installed. But the problem is when I try to backup something, I got an error while creating the folder TWRP with the mension of operation not permited. I also have a problem when I touch the Install button, I see a list of folders with random generated names like in the photo. Can anybody help me to solve this problem? I can give more informations if needed.
Thanks for helping !
{
"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"
}
your device is encrypted. you must disable encryption and factory reset device in order to become TWRP functional, as TWRP cannot handle samsung encryption. or use other backup method such as Migrate.
Ok I tried what you wrote but it works only while I don't boot my device after factory reset it. If it happens, the encryption enables automatically and I can't backup anymore. Do you have a solution for this ?
you must disable encryption in /vendor/etc/fstab.samsungexynos7884
(can maybe done with zip)
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
How am I supposed to do that ? I tried everything with this file. There is a mount option for /data "filencryption=ice". I tried to delete this with a file editor in the stock system but when I reboot my phone it reappears. When I this this in TWRP the system can't boot.
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
Click to expand...
Click to collapse
This link cannot help me because it is just a tutorial and when I do exactly like in i get the same results. I don't unerstand why my phone has this problem and not others. If you have other ideas i would be good
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
aIecxs said:
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
Click to expand...
Click to collapse
I tried installing this zip file from the SD card but it didn't boot (locked on samsung logo) so I did a factory reset with TWRP and after configuring, I got the same results than before.
- in TWRP double check your vendor partition is separate partition (or directory inside system partition)
- in TWRP terminal make sure partition is mounted rw
Code:
mount /system w
mount /vendor w
mount
- install Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
- in TWRP terminal double check fstab.samsungexynos7884 file fileencryption= flag is gone
Code:
cat /vendor/etc/fstab.*
- in TWRP - wipe - format data - type yes
Thanks for the instructions. It works perfectly ! I am just an idiot because I didn't wipe /data in TWRP but I just swiped to factory reset. Thank you a lot !
maybe I was misleading you with factory reset. might be that TWRP factory reset just behaves like simple wipe, where only files are deleted excluding /data/media
formatting whole partition is required for removing encryption.
edit: Please note if you're interested in undo the patch, you must restore vendor partition. you can of course add the fileencryption= flag back with text editor yourself. However that requires linux line endings (LF) so you can't use Windows text editor (CRLF) that's why you should use Notepad++ and enable view for invisible chars with (π) button. Do not simply copy file back into /vendor you will lose file permissions. Do not use sed you still would lose secontext. only copy content of file into old existing file like this.
Code:
cat /tmp/fstab.new > /vendor/etc/fstab.samsungexynos7884
Btw if you're running custom ROM (such as LineageOS) it's possible to break samsung encryption and use AOSP encryption as fallback by deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw. This way you can use TWRP on encrypted device.