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?

I have an issue with my LG K10 (K430, MT6753). I was experimenting with it to learn the adb function. I accidentally erased the whole boot partition using rm, and then my phone is not booting anymore. It is showing the LG boot logo, but not starting up, keeps rebooting. I tried to: 1. Repair it through LG Bridge, to flash the stock ROM through LG UP and LG Flash Tool. But the phone is not staying in Flash mode or Download mode, and can't boot into Fastboot. The only thing that apparently works is the Factory Reset mode, but it only shows the interface. It only reboots the phone and nothing else. 2. Flash the boot image through SP Flash Tool, but have no luck. The phone is detected by Windows, but only for 3 seconds, then it disconnects. No matter what I do, when I connect the phone to my PC, it quickly disconnects, even with Driver Enforcement deactivated. I tried LG drivers and some other drivers for Mediatek, but still have no luck. Is there any other way to recover the boot partition's data or to unbrick my phone?

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.

I have installed Android 4.4.2 x86 on my PC that has 2 hard disks with 2-2 partitions each. I have installed Android 4.4.2 X86 on one of them, and I have data on the other 3. The problem is that I am not able to access any of my other three partitions. How can I access my other partitions?

Is it possible to edit the fstab to mount /data, /cache, etc. from a different partition on the 1. internal memory? 2. external SD card? Details: The default partition for /data and /cache is too small for my needs and I can manage to format the (internal) /sdcard in ext4. My question may superficially seem to be like other questions asking for a way to increase the size of /data, but it's not. Here's why: 1. I need to do it *specifically* by editing fstab, which is the usual way of doing the same thing on a GNU/Linux desktop. 2. The other questions don't ask about /cache and other partitions.

I've recently got this new device which shipped with an Android >=4.0 Jelly Bean, and I was wondering how to increase zram on it because with the current parameters, it happens that even the foreground application goes out of memory and gets killed by the system. So you know, weird. You know, because I have other devices with the same 2 gigabytes of RAM which shipped with Android Jelly Bean and still run this same very recent Android version this new device runs on which I have never experienced this issue unless than when like I enable all types of tethering and run >10 applications in the background at the same time. I've heard it like supports something new called "Treble". I've also read now that there are Android Java applications whose entire purpose is just editing the zram parameters, which seems totally wild and inappropriate to me, so I was wondering if it was possible to do it properly without having to deal with such weird stuff.

I'm about to flash my kernel for the purposes of overclocking, and I want to start by backing up my LG G7 ThinQ partition by partition in QFIL so I can restore them later with LGUP's partition DL option. This is the safest recovery option for me, since post-root I can no longer access fastboot and it takes me 8 seconds to enter EDL mode. TWRP does not work on my model. If my firmware was corrupted to the point that the phone crashes in seconds then I might find I can't access EDL mode anymore, but I can easily reach the firmware update screen as long as my bootloader is intact, and from there I can connect to LGUP. There is just one problem with my plan: LGUP demands IMG partition files but the files generated with QFIL are BIN, and I suspect simply renaming the extension might result in a full brick. What to do? I might need to ask the creator of Magisk if nobody here can help, he would have to know how.

I'm trying to get list of partitions and their mount points in terminal, but I'm not so succesfull. "ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/” (found this path by using "cat /proc/mounts" but it return me a 'permission denied, I guess I need root, but I don't have one. So how to get partitions names and mount points without root? Also there is one weird thing: when I go with Total commander in /dev folder there isn't /block folder inside just file named 'block' with size 0 and not readable (becase lack of root). How is that possible?

I am trying to install a GSI that is 1.8GB, and I need to re-partition the system partition to allow the img to be installed. I tried using fdisk /dev/block/mmcblk0, then I tried using the command d, but all it says is "Selected partition 1" and it doesn't allow me to choose the partition number, which is partition 26 in my case (userdata). How to delete a partition using fdisk?

Nowadays, phones don't have SD cards anymore, but some have a ton of storage. So, I was thinking of creating a fake external SD card using an extra partition to be able to store all of your zip flashable files, pictures, and music and have it stay when you inevitably format user data when flashing a ROM or whatever. My question is: **How to properly mount a partition as an SD card so that Android thinks you have an external SD?** (you see it in a file manager, can store pictures on it directly, etc.) What I've done already : - I have created an extra partition on my OnePlus 6 with parted, it's sda17 - I have successfully mounted this partition to be able to use it normally (mount -t ext4 -o rw /dev/block/sda17 /external_sd) This command allows you to navigate to /external_sd and see your files, but Android doesn't think that you have an external SD card. I'm thinking of using a Magisk module to mount everything properly at every boot (if this is even possible)

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?

I have a Moto G9 Plus that is stuck in a bootloop. I’ve tried flashing the stock firmware multiple times without success, and I cannot boot into recovery or use a custom recovery ROM since none is installed. My phone's bootloader is currently locked. I’ve obtained the unlock code from Motorola's official website and am seeking a way to unlock it so I can flash a custom ROM like LineageOS. After researching potential solutions, I found that it might be possible to remove the memory storage from the motherboard and access the **persist partition** using an *UFI device* and an *eMMC toolkit*. Given this, I’m wondering if modifying the OEM_UNLOCK flag in the persist partition could bypass the "OEM Unlock" feature, allowing me to unlock my bootloader through fastboot. If possible, would this approach break any security measures defined in the **vbmeta partition**? Any advice or insights would be greatly appreciated!

I understand how partitions work on a hard disk, also how to use programs to create, change, and delete these partitions. I am also using Android for quite some time. In this question, I would like to focus on the Android partitions only. I found [CyanogenMod Wiki - Common Partitions and directories](https://web.archive.org/web/20161225045502/https://wiki.cyanogenmod.org/w/Doc:_more_concepts#Partitions_and_directories) (archived). But I would like to understand a little bit more: - Is the concept similar to hard disks? - Can these partitions also be changed? Or would it be necessary at all? - Are there tools to change the partitions? - Can I brick my device forever when working on the partitions?

I was looking through my Android device's partitions and noticed that the root directory / is mapped to /dev/block/dm-5. Cold starting and rebooting the device did not influence this partition number. However, updating the device or in general, flashing another image did cause it to change. Using the same image on two different devices did not give the same results, leading me to the question: How are these partition numbers determined, and what are the permissible values (e.g. / is typically mapped to .../dm-5 to .../dm-9)?

I want to flash a new ROM for my Android phone. I clean data by fastboot erase userdata but after that, I can not enter TWRP recovery because can not mount /data I tried fastboot format userdata then below errors occured: Couldn't parse erase-block-size '0x'. Couldn't parse logical-block-size '0x'. So how to make the TWRP work again? Or how to rebuild the data partition by fastboot?

I have googled from a month ago about on how to reach my goal, and I have found only https://android.stackexchange.com/questions/217741/how-to-bind-mount-a-folder-inside-sdcard-with-correct-permissions My goal is to link the WhatsApp directory in Samsung Galaxy S9 running Android 10 (so it is storage/emulated/0) in the second partition of my microSD card in ext4 (I have chosen that filesystem because I have got some issues when coping some data inside exFAT partition, related discussion if you are interested in [XDA Forums](https://xdaforums.com/t/copy-of-big-files-from-pc-to-microsd-return-error-trimming-file-message-error.4578733/#post-88848923)) Now, in the upper link, there are 2 modes but both doesn't satisfy me: 1. MOUNT SD CARD MANUALLY: but it's referred only to exFAT or FAT32 filesystem 2. ADOPTABLE STORAGE: it's related to the ext4 filesystem, but I'm forced to use adoptable storage that I haven't understood very well how it's different from mounting manually, and if all apps can be installed into microSD or only the apps where it's explicitly mount such this command mount -t sdcardfs -o nosuid,nodev,noexec,noatime,mask=7,gid=9997 /mnt/expand/[UUID]/media/0/WhatsApp /mnt/runtime/write/emulated/0/Whatsapp So, from what I have understood, I have executed the following commands referred to link explanation:

mkdir /data/media/0/sdext2
mount -t ext4 -o rw /dev/block/mmcblk0p2 /data/media/0/sdext2
mkdir /data/media/0/sdext2/prova
restorecon -rv /data/media/
mount -t sdcardfs -o nosuid,nodev,noexec,noatime,mask=7,gid=9997 /data/media/0/sdext2/prova /mnt/runtime/write/emulated/0/prova

And I have made a folder called "prova" to verify that from /storage/emulated/0/prova I can see the only file inside /data/media/0/sdext2/prova. But nothing is viewed while if from X-plore I navigate into mnt/runtime/write/emulated/0/prova the file is shown. Questions: 1. What are the commands to reach my goal? (I'm not an expert in Linux and Android) 2. When I use WhatsApp, the only important thing is that mnt/runtime/write/emulated/0/Whatsapp can read all files (and so no matter if from /storage/emulated/0/Whatsapp files aren't viewed?) Nothing can be made to read /storage/emulated/0/Whatsapp with files into MicroSD from X-plore as it's worked with local storage? 3. I don't remember how I created the second partition, but now the second partition is used by Link2SD and own and the group is system:system, and permission is drwxrwx--x. Is this ok? Link2SD automatically mounts partitions into /data/sdext2, but if this is a problem, I can remove the mount inside /system/bin/debuggerd script 4. Can the new commands be added to /system/bin/debuggerd script? I'm not sure, but seems that the Android 10 firmware of my Galaxy S9 doesn't support init.d.

When I connect my Android device via USB into a Linux machine (be it Debian, Ubuntu, Arch, etc.) I am unable to find any trace of the device or partitions using cmds fdisk -l, lsblk, etc. This is apparently due to the Android device not being treated like regular USB storage and being accessed through MTP. How can I view my Android partition tables etc? Ideally without downloading adb, using basic Linux pre-installed packages.

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?