Hi!
First post, but I've got a few things nailed down right through searching the forums and various guides and wiki's.
I've managed to install Google ION with firmware v1.5
I've SIM-unlocked the phone, using another carrier works splendid.
The Kernel version i'm using is 2.6.25.00894-g83efb08-dirty
[email protected]
My build number is CRB43
What I'm trying to accomplish here is getting root on the filesystem. I've tried various methods, guides and forum conversation tips but I can't make /system anything else than ro (Read-only).
I have installed Better Terminal from Market.
su and telnetd works perfect, I can connect to the phone using telnet. I'm using telnet to connect to the device, by forwarding ports through ADB.
I have tried using ADB shell to get root as well as telnet.
What I am trying to do is replace my current keymapping from an English one to an edited, åäö-capable one, because it's damn tricky trying to type these characters on the hardware keyboard. I haven't even found a way of typing åäö without replacing the keymap because of very little information about how the keyboard _is_ mapped using Android on the Kaiser.
Please advice wither on how to be able to type åäö characters without having to modify the keymap or give me a heads-up on how I'm supposed to get root on this filesystem, using commands such as;
# mount -o rw,remount /dev/block/mtdblock3 /system
does not give me an error but nothing else is returned either so I can't verify that the command actually executed or did anything to the system. I can however verify that the /system is still ro and still as a cramfs type no matter how I attack this.
Here's my situation on my mounts;
Code:
rootfs on / type rootfs (rw)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,codepage=cp437,iocharset=iso8859-
1,flush)
/dev/block/loop2 on / type ext2 (ro,sync,noatime,nodiratime,errors=continue)
tmpfs on /dev type tmpfs (rw,size=100k)
proc on /proc type proc (rw)
sys on /sys type sysfs (rw)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,codepage=cp437,iocharset=iso8859-
1,flush)
/dev/block/mmcblk0p1 on /cache type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,codepage=cp437,iocharset=iso8859-1
,flush)
/dev/block/loop0 on /data type ext2 (rw,sync,noatime,nodiratime,errors=continue)
/dev/block/loop1 on /system type cramfs (ro)
/dev/block/loop0 on /etc type ext2 (rw,sync,noatime,nodiratime,errors=continue)
/dev/block/loop0 on /shared_prefs type ext2 (rw,sync,noatime,nodiratime,errors=continue)
/dev/block/mmcblk0p1 on /tmp type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,codepage=cp437,iocharset=iso8859-1,f
lush)
/dev/block/loop0 on /system/lib/modules type ext2 (rw,sync,noatime,nodiratime,errors=continue)
/dev/block/mmcblk0p1 on /system/build.prop (deleted) type vfat (rw,noatime,nodiratime,fmask=0000,dmask=0000,codepage=cp4
37,iocharset=iso8859-1,flush)
/dev/block/loop2 on /system/bin/su type ext2 (ro,sync,noatime,nodiratime,errors=continue)
/dev/block/loop2 on /system/xbin/su type ext2 (ro,sync,noatime,nodiratime,errors=continue)
/dev/block/loop0 on /smodem type ext2 (rw,sync,noatime,nodiratime,errors=continue)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
These are my blocks;
Code:
loop0 loop2 loop4 loop6 mmcblk0 mtdblock0 vold
loop1 loop3 loop5 loop7 mmcblk0p1 ramzswap0
Hi ppl!
Explaining the situation:
- Stock ROM (Orange ES)
- Apply OCLF V2+
- Tired of 2.1, I move to froyo (without remove the lagfix) with this steps:
* Flash with ODIN I9000XWJM8 with re-partition
* Flash with ODIN I9000XWJPA without re-partition
After that, I decided to install Voodoo.
Well, after 2 days of heavy use... the phone is very lagged... and transactions are slow
I have just disabled voodoo (creating "disable_lagfix" in voodoo folder), and I was considering to try I9000XXJPO. But I just remember that I have not disabled OCLF when I installed Froyo, and everything I read about doing this is very bad... Maybe that is causing problems? I have reinstalled the app, and it says OCLFV2 is not installed. But maybe the froyo installation overwrite files and the apk cannot detect anything...
Could anyone clarify me about this?
This is the "mount" output:
Code:
# mount
rootfs on / type rootfs (ro,relatime)
proc on /proc type proc (rw,relatime)
sys on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p2 on /data type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
/dev/block/stl6 on /mnt/.lfs type j4fs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/stl9 on /system type rfs (rw,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl10 on /dbdata type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl11 on /cache type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/stl3 on /efs type rfs (rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.google.android.stardroid-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.rovio.angrybirds-1 type vfat (ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
Thank you!!
How is this development?.. But yes.. When u flashed jm8, oclf got wiped... So no.. Oclf is not installed.
Sent from my GT-I9000
Hi, I have an unlocked, rooted Milestone running 2.1-update1.
I am having some issues getting App2SD up and running.
Everything seems to be working fine except for one piece:
I can't mount the ext2 partition of my SDCard.
I have a 16gb sdcard, formatted with two primary partitions, 14.5gb for FAT32 and 1.5gb for ext2.
busybox was installed ok, all the shell scripts seem to have installed fine as well, however, in order for it to work, the "mount_sd.sh" script has to be able to mount the second partition in order to link /data/app to it - but the damn thing won't mount.
I have tried re-partitioning the SD card multiple times, using multiple different partitioners (gparted in Ubuntu, Minitool in XP, even fdisk in the Android shell itself...) but nothing seems to work - I always get the same error:
Code:
# mount -t ext2 /dev/block//vold/179:2 /system/sd
mount -t ext2 /dev/block//vold/179:2 /system/sd
mount: No such device
The device however, most certainly DOES exist:
Code:
# ls /dev/block//vold
ls /dev/block//vold
179:2
179:1
179:0
I have seen that some people use the /dev/block/mmcblk0 instead of /dev/block//vold/179 - I am unsure as to why (anyone know which one I should be using on the Milestone???) but I tried that as well:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Again, it tells me the device doesn't exist, when it clearly DOES:
Code:
# ls /dev/block/mmc*
ls /dev/block/mmc*
/dev/block/mmcblk0
/dev/block/mmcblk0p1
/dev/block/mmcblk0p2
When I try to verify the partitions are there in the ADB shell, it looks like /dev/block//vold/179 doesn't exist or is some kind of special device (incidentally, does anyone know wtf the double slashes "//" are for?):
Code:
# fdisk /dev/block//vold/179
fdisk /dev/block//vold/179
fdisk: can't open '/dev/block//vold/179'
However, I CAN fdisk /dev/block/mmcblk0, and it gives me the following partition table:
Code:
# fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
...snip...
Disk /dev/block/mmcblk0: 16.0 GB, 16039018496 bytes
255 heads, 63 sectors/track, 1949 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1762 14153233+ b Win95 FAT32
/dev/block/mmcblk0p2 1763 1949 1502077+ 83 Linux
So, it looks like /dev/mmcblk0 is the correct block device, however, mount tells me this:
Code:
# mount
mount
...snip...
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=101
020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
So, mount is telling me that the first partition is mounted onto /sdcard from /dev/block//vold/179:1
I am confused. The only thing left I need to do in order to get App2SD working on my Milestone, is to mount the bloody second partition of my SD card and link it to the file system, yet the damn thing refuses to mount.
Does anyone know where I am going wrong here?
Which is the correct block device I should even be trying to mount /dev/block/mmcblk0 or /dev/block//vold/179:2?
I don't want to flash to an unofficial 2.2 and I have everything else working just the way I want it, so I'd rather not reset either.
There MUST be a solution somewhere, but I am getting frustrated.
Thanks for any help you can give me!
Hello!
I'm having exactly the same problem... I've been trying to find a solution for this problem for the last 3 hours, but I can't figure out a way...
Can anyody give us a light??
Thanks!
Same question here. Partitioned more than a month ago, but then I reached a dead end. I don't know a reliable way to mount the ext2 partition. I'm familiar with Linux, and I have tried all kinds of crazy shell scripts, but the Android filesystem is still a bit alien to me.
By the way, what is this App2SD that you speak of? It's something different from the Apps2SD app on Froyo, right?
JoeDuncan said:
Code:
# mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount -t ext2 /dev/block/mmcblk0p2 /system/sd
mount: No such device
Click to expand...
Click to collapse
A shot in the dark would be ext2.ko is not insmodded ... ?
got this problem to on stock US froyo kernel for Samsung Galaxy 5. I also suspected ext2 was missing but it seems compiled into kernel.
Code:
# cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev rpc_pipefs
nodev inotifyfs
nodev devpts
ext2
nodev ramfs
vfat
nodev nfs
rfs
For the MS, you have to insert a ext2 Kernel module, look around here on the forums..
Depending on which module-version you're using try "-t auto" instead of "-t ext2"
Also you should use "/dev/block/mmcblk0p2" if this is your ext2 partition
Besides, there should be some packages available which contain the necessary scripts and files to install this automatically and at boot, applicable as OR-updates
It was my understanding that Apps2SD could not be used on 2.1, you needed 2.2 to use that app. Although I have the same issue with Links2SD which is suppose to work with 2.1. I can't get anything to see an ext2 or 3 or Fat partition.
My amator tries
Hy,
I've got the same problem on Cyanogen and Goapk roms:
mount -t auto /dev/block/mmcblk0p2 /sd-ext
doesn't work
I verified sd-ext was present
mkdir /sd-ext
Nothing changed.
My mount description is somethime using vold instead of mmcblk0p... I don't really understand.
However I succeeded to mount sdext by using busybox (on goapk rom)
busybox mount -r -w -t auto /dev/block/mmcblk0p2 /sd-ext
result mount:
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,g
id=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1
000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso
8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0
/dev/block/mmcblk0p2 /sd-ext ext2 rw,errors=continue 0 0
Just in case, If somebody can help me:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
*perl script are unable to decompresse boot.img, how to change init.rc in this case?
thanks
symlinks
lamidesbetes said:
*I have a symlink /data/drm =>/data/local :how to unsymlink it? (unbind isn't present and replacement doesn't work:" Invalid cross-device link")
Click to expand...
Click to collapse
Symlinks can be removed with the rm command.
The "cross device link" error happens when one uses the ln command without the "-s" option (so attempting a hard link instead of symlink).
Hey guys, since there is nothing for this phone yet, I decided to try to make a device tree, in order to build a recovery. The result is here .
As it's written in the repository, I started from scratch using this tutorial, and taking what I could from this stock ROM .
Unfortunately, after that I unexpectedly lock the bootloader using the MiFlash tool, the official MiUnlock asks me to wait 160 hours before unlocking the bootloader again(I don't know why, but this thing happened three times!), so at the moment, if I tried to build a TWRP recovery, I wouldn't be able to flash it and try it on the phone. I'll simply wait for this.
In the meanwhile, I thought about sharing it to let you suggest me any recommendation or similar, since I have a lot of doubts about what I've done. Here's why:
- In the 5th step, the tutorial says to move "factory_init.*.rc files, meta_init.*.rc files, ueventd.mt****.rc, init.recovery.mt****.rc" files into the root folder. Unfortunately, inside the unpacked recovery.img that I used I couldn't find these files. Therefore, I put the files that are still there, hoping that they're the correct ones.
- Still in the 5th step, I completely skipped the writing of the permissive.sh file, because I didn't know what to write. The file is there, but it's empty.
- From the 6th step, the tutorial starts to mention the values BRAND and MANUFACTURER. They should respectively be Redmi and Xiaomi. Hopefully, I didn't get any of these wrong.
- In the 8th step, the tutorial shows how to write the BoardConfig.mk file. I have got several doubts about that file, you can search for these comments inside the file itself: "I have no idea about this" and "I believe the zImage file is wrong". In particular, my doubt about the zImage stems from the fact that, in the 5th step, the tutorial says to put the "recovery.img-kernel" file inside the prebuilt folder. Unfortunately, I was not able to find this file inside the recovery.img, but I found the "recovery.img-kernel_offset" file, and I put that one, hoping that it's the correct one. Nonetheless, I've read here on the forum that the kernel has not been released yet by Xiaomi.
- In the 9th step, the tutorial shows how to write the omni_merlin.mk(in this case) file. I got some doubt about the last values, you can search for this comment inside the file itself: "I'm not totally sure about these last values".
These are all my doubts about this device tree, hopefully you'll be able to help me! Please let me know, and thank you!
P.S. It's my first time doing something like this, and, more important, using Git. I hope I didn't do anything wrong!
Ok, now I'm completely stuck. I managed to extract from the boot.img what I think is the kernel image, it's now in prebuilt/zImage. But I got a problem with the recovery.fstab I should write. The problem is that I cannot find /system mounted. Could it be that the problem is that Magisk is installed and it messes up something? Please help me. Could it be that the mount address is /dev/block/dm-1/system?
Code:
[email protected]:~$ adb shell
merlinnfc:/ $ su
merlinnfc:/ # mount -o ro,remount /
merlinnfc:/ # mount -o ro,remount /system
mount: '/system' not in /proc/mounts
1|merlinnfc:/ # mount -o ro,mount /system
mount: bad /etc/fstab: No such file or directory
1|merlinnfc:/ # mount
/dev/block/dm-1 on / type ext4 (ro,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1921708k,nr_inodes=480427,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600,ptmxmode=000)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /mnt type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1921708k,nr_inodes=480427,mode=755,gid=1000)
tmpfs on /apex type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1921708k,nr_inodes=480427,mode=755)
/dev/block/mmcblk0p9 on /metadata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,data=ordered)
/dev/block/dm-2 on /vendor type ext4 (ro,seclabel,relatime)
/dev/block/dm-0 on /product type ext4 (ro,seclabel,relatime)
tmpfs on /sbin type tmpfs (rw,seclabel,relatime,size=1921708k,nr_inodes=480427,mode=755)
/sbin/.magisk/block/persist on /sbin/.magisk/mirror/persist type ext4 (rw,seclabel,relatime,data=ordered)
/sbin/.magisk/block/system_root on /sbin/.magisk/mirror/system_root type ext4 (ro,seclabel,relatime)
/sbin/.magisk/block/system_root on /sbin/setlockstate type ext4 (ro,seclabel,relatime)
none on /dev/cg2_bpf type cgroup2 (rw,nosuid,nodev,noexec,relatime)
none on /dev/cpuctl type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
none on /acct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
none on /dev/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
none on /dev/memcg type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
none on /dev/stune type cgroup (rw,nosuid,nodev,noexec,relatime,schedtune)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,relatime)
none on /config type configfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime)
pstore on /sys/fs/pstore type pstore (rw,seclabel,nosuid,nodev,noexec,relatime)
none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,size=1921708k,nr_inodes=480427,mode=750,gid=1000)
none on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
none on /sys/fs/cgroup/freezer type cgroup (rw,relatime,freezer)
/dev/block/mmcblk0p46 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=10010,resgid=1065,errors=panic,data=ordered)
/dev/block/mmcblk0p45 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p15 on /mnt/vendor/protect_f type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/mmcblk0p16 on /mnt/vendor/protect_s type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/mmcblk0p12 on /mnt/vendor/nvdata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered)
/dev/block/mmcblk0p11 on /mnt/vendor/nvcfg type ext4 (rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered)
/dev/block/mmcblk0p13 on /mnt/vendor/persist type ext4 (rw,seclabel,nosuid,nodev,noatime,data=ordered)
/dev/block/mmcblk0p41 on /cust type ext4 (ro,seclabel,nosuid,nodev,noatime,data=ordered)
tmpfs on /storage type tmpfs (rw,seclabel,nosuid,nodev,noexec,relatime,size=1921708k,nr_inodes=480427,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/loop2 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop2 on /apex/com.android.tzdata type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop3 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop3 on /apex/com.android.media type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop4 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop4 on /apex/com.android.resolv type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop5 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop5 on /apex/com.android.conscrypt type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop6 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop6 on /apex/com.android.runtime type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop7 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop7 on /apex/com.android.apex.cts.shim type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop8 on /apex/[email protected] type ext4 (ro,dirsync,seclabel,nodev,noatime)
/dev/block/loop8 on /apex/com.android.media.swcodec type ext4 (ro,dirsync,seclabel,nodev,noatime)
/sbin/.magisk/block/vendor on /sbin/.magisk/mirror/vendor type ext4 (ro,seclabel,relatime)
/sbin/.magisk/block/product on /sbin/.magisk/mirror/product type ext4 (ro,seclabel,relatime)
/sbin/.magisk/block/data on /sbin/.magisk/mirror/data type ext4 (rw,seclabel,relatime,noauto_da_alloc,resuid=10010,resgid=1065,errors=panic,data=ordered)
/sbin/.magisk/block/data on /sbin/.magisk/modules type ext4 (rw,seclabel,relatime,noauto_da_alloc,resuid=10010,resgid=1065,errors=panic,data=ordered)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
/data/media on /mnt/runtime/full/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal)
/dev/block/vold/public:179,129 on /mnt/media_rw/A246-600F type exfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,iocharset=utf8,namecase=0,errors=remount-ro)
/mnt/media_rw/A246-600F on /mnt/runtime/default/A246-600F type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/A246-600F on /storage/A246-600F type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,mask=6)
/mnt/media_rw/A246-600F on /mnt/runtime/read/A246-600F type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/A246-600F on /mnt/runtime/write/A246-600F type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=18)
/mnt/media_rw/A246-600F on /mnt/runtime/full/A246-600F type sdcardfs (rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,mask=7)