With TWRP, on almost every operation I get > Failed to mount '/preload' (Invalid argument) My device currently can not boot, and this may have something to do with it, /preload is currently in /etc/fstab, I can see the entry here with /dev/block/mmcblk0p16 /preload ext4 rw 0 0 When I try to mount it, I get mount preload/ mount: mounting /dev/block/mmcblk0p16 on /preload failed: Invalid argument Is there anyway to fix this problem? From my recovery.log, I have /preload | /dev/block/mmcblk0p16 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB Flags: Can_Be_Mounted Can_Be_Wiped IsPresent Primary_Block_Device: /dev/block/mmcblk0p16 Display_Name: preload Storage_Name: preload Backup_Path: /preload Backup_Name: preload Backup_Display_Name: preload Storage_Path: /preload Current_File_System: ext4 Fstab_File_System: ext4 Backup_Method: files I'm trying to flash LineageOS, but I'm really just curious about resolving this error message.

I have a Asus Zenfone 2 and a few days ago it ran out of battery and turned off. Then after I charged it up and restarted it, it wouldn't turn on. It gets to the logo and the loading circle and just gets stuck there forever. I can get into recovery, but can't do anything in recovery, because everything gives this error: > E:failed to mount /cache (invalid argument) Trying to wipe cache, factory reset the phone, mount /system, flash a ROM from SD card, ADB sideload, everything gives the error multiple times. Factory reset formats /data fine, but when it gets to /cache, gives the error and aborts. Same thing with fastboot. I tried to flash TWRP (I have stock recovery) and I tried to erase and format cache through fastboot, but both give this error: > FAILED (remote: 'Can not mount the necessary partition') > >fastboot: error: Command failed Is there anything I can do to format the phone or somehow rebuild the partitions without being able to flash anything via recovery or fastboot? I don't know if tools like AFT or xfstk can do anything for me. Edit: I don't think the EMMC chip is dead, because the recovery partition is still fine, I can still boot into recovery and when I did a factory reset, it formatted /data without any errors, only had an error when it started formatting /cache. When I was looking for a solution to this problem, I read somewhere that sometimes when the device gets interrupted, like when it shuts down suddenly, to prevent data loss android would change permissions on the /cache partition to read only or something like that. This would certainly explain what happened to my phone. Just need to think of a way to access ADB shell on it to try to change permissions. Shell doesn't work in ADB sideload mode, that's the only ADB thing the stock recovery has. Is that a similar thing in fastboot by any chance?

Using Apps2SD Pro app on Samsung Galaxy Note 3 N9005, Resurrection Remix Nougat v5.8.5 with Magisk v17.1. I lose the linked apps again & again after reboot. This happened several times already. I tried all mounting script types, including the advanced one, but after several reboots, the linked apps are disappearing (errors attached). See the Storage screenshot, where you can see the sdext2 (labelled as EXT4) mounted by system, instead by Apps2SD. The problem is that the sdext2 partition is mounted earlier than the Apps2SD is started and initialized, so Apps2SD can not mount the sdext2 partition, thus the system loses the installed linked apps. How can I make Apps2SD started before sdext2 partition is mounted by the Resurrection Remix system? " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> (Tap to enlarge)

I installed android-x86-4.2-20130228 as a live USB, but it doesn't read my partition of my hard disk. I tried with **Paragon UFSD Root Mounter**, but it doesn't work well in 4.2.2, and **ES Explorer** doesn't read any partition. How can I mount all partitions of the hard disk in Android-x86?

I have **Android-x86** alongside **Ubuntu 16.04**. I have installed Android in a 16GB partition on my hard drive. I was wondering if it is possible to access other partitions from Android, as it just shows nothing in the files app. It would be pointless because all my pictures, videos, and other files are in those other partitions. I am not an expert, so please let me know if additional information is needed.

**System**: rooted Samsung Galaxy S10 with Android 10 I have replaced my old external sdcard (128GB) with a new and bigger one (512GB). The old card was automatically mounted to /storage/6639-3031. The new card is mounted to: /storage/9C33-6BBD. Since I have a lot of configured appz that use custom paths pointed to /storage/6639-3031/somesubfolder I would like to change the new id: 9C33-6BBD back to the old one 6639-3031 system wide. Since there is no fstab in Android responsible for this and I cannot find **where this id's are stored in Android**, maybe some experts here can help me? It seems like a simple problem but I did not find the solution yet. Some clues I already found: 1. Android equivalent of /etc/fstab? 2. Remount FUSE partition Once I have found where this external sdcard id is stored, **can I just change the id** (I have **root**)? **Will it be stay changed after reboot**?

The phone is a Xiaomi Redmi 9 running Android 10 and MIUI 12.0.1. After a reboot, my phone refuses to mount my SD card. From what I have searched, this seems to be a common problem with MIUI, but no one seems to have tried to do anything except reformatting, which probably makes the phone just not scan. - I have checked, the SD card is alright. It never had any problems until the reboot and Android weirdness, and still does not have any problems on any other device. - I have tried putting another SD card from the same brand, and it passed the check, however, that card has way fewer files, which I think might be part of the reason. - I ran adb logcat vold, and I have noticed that every time it tries to mount the card, it runs fsck.exfat, After 50 seconds, the check times out. After a while, the check finishes with no errors, but since it times out, it does not mount. This seems like a pretty bad design choice. - adb shell sm list-volumes returns the card as unmountable. There is a slight chance some corruption occurred after the restart, as it was not present earlier. And yes, I am absolutely sure there are no problems with the card. Now the question is, is there any way to change the check timeout? Or just do anything else to fix this instead of having to move files or format the card? Maybe a way to force the mount? I have tried pretty much everything, nothing works except for the command to mount the card

There is a vendor image in my device I want to change (unpack/mount, doing changes, pack/umount). My purpose is to update boot.img with my new kernel (in a rooted device). Unfortunately, it does not work due to incompatible versions between a newly compiled kernel (my compilation) to the previous kernel modules stored in vendor.img. As I figure it, I need to update the old ko executables stored in vendor.img in my product. The first step is to do dd from my device and adb pull it out to my build environment. While I tried to do a mount on vendor.img, I discovered it not working due share_blocks attribute blocking it to mount as RW (dmesg wrote: "...unsupported optional features (4000)"), To solve it, running the following command e2fsck -y -E unshare_blocks vendor.img will disable the share_blocks feature that prevented me to do mount as RW. Of course, doing mount RW works correctly. In the last phase, I tried to replace files in the vendor filesystem and then I discovered another challenge into my way, Unfortunately, there was a problem with limited space in the file system, For example: In case I want to replace the kernel module called abc.ko, deleting the file doesn't show any new free space in the file system. At this point, I can't update the old kernel modules with the new ones (compatible with the newly compiled kernel). Of course, running df -h . returned no free space and 100% used. Does anyone have any idea what I need to do?

Sometimes I really wish they hadn't messed around with Linux so much! I know there's an /etc/fstab in there somewhere, but where? I'd like to mount some partitions with alternative filesystems (because I don't like FAT32).

I'm trying to mount the directory of an app to a folder in storage. I've put a script called custom.sh inside "/data/adb/service.d". The contents of the script are:

#!/system/bin/sh

sleep 30

mount -o bind /data/data/is.xyz.mpv /storage/emulated/0/Test

It just doesn't work. Can anyone point me in the right direction please?

How can I mount the /system directory rewritable or read-only on my Android phone?

I have a device, rooted through the KernelSU. I granted root access to the Termux app using the KernelSU app. Now I have access to the su command, and theoretically should be able to use the mount command within the su shell. But when I try to use it for my root partition /, it says: mount: '/dev/block/dm-2'->'/': Operation not permitted What I want is to mount the root as read-write, but any mount operation I've tried failed. The commands I've tried: mount -o rw,remount / mount -o ro,remount / Or maybe there's another way to make the root writable?

To clarify: I know that basically any root access is unsafe. But I'm asking ***only*** about the remount command itself, not about what can happen after. I want to execute as root something like:

mount -o rw,remount /

Can this particular command or its equivalent theoretically break something (especially my data or even the whole OS) or I only need to be careful after the execution? P.S. I use *Termux* as terminal emulator and *KernelSU* as root solution, but I don't think these things matter

I have a rooted Samsung Galaxy S23 with Android 14 and Magisk 27 installed. I ran

root

successfully and then proceeded to go into

shell

in which I obviously had root rights (#). Then I ran

-o remount,rw /data/adb/service.d

which gave me the error message

: '/service.d' not in /proc/mounts

. This always occurs whenever I try to mount/remount any root directory. How can this be fixed?

I have a Xiaomi Mi A2 running Android Ice Cold Project (AICP) nightly build 15.0 (Android 10). I don't know what I did, but after installing a custom ROM, I noticed that my system partition cannot be mounted as read/write. I tried 1. mount -o rw,remount /system command on a terminal emulator, ADB shell, and TWRP terminal. The command shows no feedback showing failure (maybe I succeeded?) 2. Mount it using the built-in TWRP mount function. The system check box can be checked out (it doesn't retain its check mark on reboot) Some apps actually work according to sources and reviews. Some say (Failure to mount..), some say (System mounted as rw), and some don't have feedback. I don't know what to do. I noticed this when I installed a custom ROM. I tried using another custom ROM but same thing. Also, reformatting doesn't help. I don't know if this occurs on the stock ROM.

I accidentally wiped the **metadata** partition along with **Dalvik/ART Cache** and **Cache** using TWRP and now I can't boot into the OS. **Internal Storage** and **USB-OTG** were excluded. I know that the data is still on the phone, but that it's encrypted, so I've already tried the following: 1) Inside TWRP > Wipe > Advanced Wipe, I tried to **Repair or Change File System**, but no luck there. 2) I connected the phone to a PC and used these adb commands to try to backup the raw data: - *adb pull /dev/block/by-name/userdata* - *adb pull /dev/block/by-name/metadata* This backed up everything (128 GB of userdata - the whole phone memory, and the metadata partition which is 16 MB), so If I'm correct, this should be my data, but it's encrypted. Since the metadata partition was wiped, I now have no access to the keys that are used to decrypt this data. My question is, how can I decrypt this or mount it somewhere, either on the phone or Windows/Linux? What do I do next with the files that I backup up? 3) I have also tried to flash a newer version of the ROM using **fastboot**, so that the phone will hopefully boot, but that didn't help either. Probably because the **Internal Storage** says **0mb**, I got lots of errors while trying to flash it with fastboot. Is there any way to backup my data (files, photos...)? Either by somehow fixing what I did wrong and booting into the OS or just by connecting the phone to a PC and using adb or any other method? When I boot into TWRP, the **Internal Storage** says **0mb** and the TWRP built-in **File Manager** can see some folders and files but cannot access all of them. For example, it doesn't show anything inside the data folder, which is what I care about saving. But inside TWRP > Mount, there's an option that says **Decrypt Data**. When I click on it, it asks for a **password**. What is this password, and where is it stored? It’s not the PIN used to unlock the phone, so what is it? If there’s no way to find out the current password, how can I find it when the phone is fully working and decrypted, so I have it in case I need it later? The phone is Poco F3 with Android 13 Custom ROM from Xiaomi.eu, rooted with Magisk **v27** and alioth TWRP version **3.7.0-12-POCOF3-v7.9_A13**, if that helps. I know I can flash a new ROM and boot the phone. But right now, I don't care about fixing the phone, just about my data, and I just want to save it if possible in any way? It may even be encrypted, doesn't matter, as long as I can decrypt it later and access it.

I accidentally wiped the **metadata** partition along with **Dalvik/ART** and **Cache** using TWRP and now I can't boot into the OS. **Internal Storage** and **USB-OTG** were excluded. Is there any way to backup my data (files, photos...)? Either by somehow fixing what I did wrong and booting into the OS or just by connecting the phone to a PC and using adb or any other method? When I boot into TWRP, the **Internal Storage** says **0mb** and the TWRP built-in **File Manager** can see some folders and files but cannot access all of them. For example, it doesn't show anything inside the data folder, which is what I care about saving. The phone is Poco F3 with Android 13 Custom ROM from Xiaomi.eu, rooted with Magisk **v27** and alioth TWRP version **3.7.0-12-POCOF3-v7.9_A13**, if that helps. I know I can flash a new ROM and boot the phone. But right now, I don't care about fixing the phone, just about my data, and I just want to save it if possible in any way? It may even be encrypted, doesn't matter, as long as I can decrypt it later and access it.

I have a rooted Android 13 device with dm-verity disabled. How can I remount the system partition for read and write permission without Magisk installed?

I am using Micromax A106 Unite 2. I used the app FolderMount to move files to the SD card for WhatsApp, UC Dowloads, Picsart, and other apps. After some days, my phone had many hang problems. I just uninstalled FolderMount and did a hard reset on my phone. But before uninstalling FolderMount, I forgot to unmount all folders. Now I am facing many problems with that. The FolderMount's partitions are still on my phone. If I create a folder "WhatsApp" on my SD card and internal storage, the folders mount automatically. And after 1 or 2 minutes, the phone will hang. I formatted the SD card but it is not a solution. I tried another SD card, but the result is the same. How do I remove these FolderMount's partitions?

I'm using Android Studio. I was trying to set up a dev environment and it requires modifying the hosts file. So, 1) I created new devices in ADM (Nexus 4, Android 10 x86_64 without Google API and without Google Play). 2) I launched the emulator 3) Then I tried following instructions from Stack Overflow . I'm using Linux Mint so:

$ ~/Android/Sdk/platform-tools/.adb root

output: 
restarting adbd as root

Okay, I got root:

$ ~/Android/Sdk/platform-tools/.adb shell whoami

output: 
root

Then I was supposed to remount and this is where I stuck:

~/Android/Sdk/platform-tools/.adb remount

output: 
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
avb_ops_user.cpp:217: ERROR: Error writing data.
avb_user_verity.c:205: ERROR: Error writing to partition 'vbmeta'
E Skipping /system
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
W DM_DEV_STATUS failed for scratch: No such device or address
E [liblp]No device named scratch
[liblp]Partition scratch will resize from 0 bytes to 814587904 bytes
E [liblp]bool android::fs_mgr::WritePrimaryMetadata(int, const android::fs_mgr::LpMetadata &, uint32_t, const std::string &, const std::function &) write 540 bytes failed: Operation not permitted
E [libfs_mgr]add partition scratch
Skip mounting partition: /product
Skip mounting partition: /product_services
Skip mounting partition: /product
Skip mounting partition: /product_services
W DM_DEV_STATUS failed for scratch: No such device or address
E Can not mount overlayfs for partitions: No such file or directory
Skip mounting partition: /product
Skip mounting partition: /product_services
E failed to remount partition dev:/dev/block/dm-1 mnt:/vendor: Read-only file system
E Consider providing all the dependencies to enable overlayfs
/system/bin/remount exited with status 10
remount failed

I don't know if remount is the critical issue, but I guess so. At the moment I don't have permission to modify /etc/. For example:

$ ~/Android/Sdk/platform-tools./adb shell "cp /etc/hosts /etc/hosts.bak"

output: 
cp: /etc/hosts.bak: Read-only file system