[Q] backup EFS partition on Droid! - Motorola Droid and Milestone General

Hello all!
So I need to backup my EFS partition (with phone info, number, nv_data.bin, etc), but I can't find the partition! Furthermore there is no /efs folder on the phone, and the rootfs is mounted read-only.
I have searched for it on a vanilla ROM, a rooted ROM, and now a Cyanogen7 ROM, but I can't find it.
I have scoured the web for info, but all answers don't apply to this phone. There are many guides talking about reading and writing from /dev/stlX, but my droid seems to use /dev/block/mtdblockX, and none of the mtdblock's have EFS or Baseband information. Does Anyone know Anything about reading from or discovering the EFS partition on the Droid, or communicating with the baseband?
My goal: I ultimately need a way to read and write the nv_data.bin file on a Motorola Droid, or otherwise modify and restore important phone information (ESN, IMEI, MEID, whatever).
Also please no off-topic posts / "just letting me know you think this is wrong/illegal/impossible" / "whatever you think", as I've asked Verizon/lawyers and I have legal authority in my scenario. This seems to be a common response, so those of you who intend to say something like this, I'm asking you to please refrain from posting. Furthermore I know this procedure is possible, because I've seen it done on other Verizon devices.
For the record, when I run "mount" as root, this is what is printed:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock4 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock6 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock5 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock0 on /config type yaffs2 (ro,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
It seems most of my phone's data is contained within mtdblock's. However running "cat /proc/mtd" prints this:
Code:
dev: size erasesize name
mtd0: 00180000 00020000 "pds"
mtd1: 00060000 00020000 "misc"
mtd2: 00380000 00020000 "boot"
mtd3: 00480000 00020000 "recovery"
mtd4: 08c60000 00020000 "system"
mtd5: 05ca0000 00020000 "cache"
mtd6: 105c0000 00020000 "userdata"
mtd7: 00200000 00020000 "kpanic"
Elsewhere on the web, I have seen partitions named "efs" and "radio" pop up. Clearly mine lacks these.. where is this info? It must exist somewhere, as it's visible in Settings->About->Phone Status.

Related

[Q] Change ROM without disable lagfix

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

how to dump your zio

I wrote this up in another forum and it also got lost in the 1.6 thread. Thought I'd pull it out.
---------
Instructions on how to dump your image manually:
Note: Everything in green is a command to type.
Pre)You installed the Kyocera USB drivers that came with the phone.
Kyocera ZIO - Downloads
Direct: http://www.ziobykyocera.com/downloads/files/M6000_USB_Driver.zip
Also, on the phone: Menu->Settings->Applications->Development->USB Debugging [selected]
Steps:
Root your phone:
[APP] [ROOT] 1-click root for N1 (Latest ver: 1.6.2 beta 5) - xda-developers
Direct: xda-developers
Install Android SDK for windows:
Android SDK | Android Developers
Direct: http://dl.google.com/android/android-sdk_r07-windows.zip
Extract that somewhere convinient, for ex: c:\
You'll need dump_image to get the img, find it here:
My Brain Hurts: Porting Clockwork Recovery to New Devices
Direct: http://koush.tandtgaming.com/test/dump_image
Copy that to the root of your sdcard, we'll use it later.
Lets connet to your phone.
Plug it in to the usb, make sure it is not mounted for reading the sdcard. On the phone, in the notification window tap the 'usb connected' notice and select "don't mount".
Now in windows, click Start->Run and type cmd.
cd \android-sdk-windows\tools\
adb.exe devices
It should list your device if all has gone well.
adb.exe shell
It should have connected to the phone and you have a "$" prompt.
su root
Now look at the phone, the Super User program (was installed after 1-click-root) should have popped up and asked if you want to allow root access, allow it.
Now you are at a "#" prompt.
Installing dump_image:
dump_image should be on the root of your sdcard from step 3.
Copy it to your bin directory:
cat /sdcard/dump_image > /system/bin/dump_image
Give it executable permission:
chmod 6755 /system/bin/dump_image
What to dump:
cat /proc/mtd
You're going to want to copy the output of that to the forum.
There should be a number of lines begining with mtd#
and the last name column has the name we'll need in quotes.
The dump:
mkdir /sdcard/dumped
dump_image boot /sdcard/dumped/boot.img
That just pulled the boot image. We need to do that for all the other images now:
dump_image name_here /sdcard/dumped/name_here.img
There could be 6-8 of them. Total will take a couple hundred megs.
Final:
Now we have it all, so zip up the files in /sdcard/dumped and put it on megaupload.com or something like that and post a link and the output from "cat /proc/mtd"
And that's it
Simple, yeah?
Some of those partitions that were listed in /proc/mtd are probably not needed, but I'm not certain as to which ones those are. I'm guessing "cache" and "userdata" probably aren't needed.
There was some issues with using the dump_image on yaffs2 partitions. For those the yaffs2 utility is useful. Here's some more info that was in the 1.6 thread:
Get it here:
http://jiggawatt.org/badc0de/android/mkfs.yaffs2.arm.tar.gz
(I attached it as well since that's the only place I could find an actual working version)
There's also a utility to extract the yaffs2 image (source)
You can also google for "mkyaffs2image" which is for something I can't recall.
Kind of shows how to use it in the middle of this section:
http://jiggawatt.org/badc0de/android/index.html#dynamic
adb push mkfs.yaffs2 /data/misc/mkfs.yaffs2
adb shell
# cd /data/misc
# ./mkfs.yaffs2 /system /system.img
# exit
adb pull /system.img ./system.img
Click to expand...
Click to collapse
Other useful info:
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 01080000 00020000 "fota_amss"
mtd1: 00400000 00020000 "boot"
mtd2: 06780000 00020000 "system"
mtd3: 011e0000 00020000 "flex"
mtd4: 00500000 00020000 "recovery"
mtd5: 0ba60000 00020000 "userdata"
mtd6: 00600000 00020000 "fota_boot"
mtd7: 06780000 00020000 "cache"
mtd8: 000c0000 00020000 "misc"
Code:
#mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock2 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /data/FLEX yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=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,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
So
Code:
boot not yaffs2
system yaffs2
recovery ...most likely yaffs2
userdata yaffs2
cache yaffs2
misc ...no clue
I've also tossed a bug in clockworkmods ears -- maybe if enough people request, we can get a fully supported recovery through rom manager.
dump_image data /sdcard/data.img
can't find data partition
is this a yaffs2 partition?
edit: mkfs.yaffs2 allows me to dump the partition, dump_image will not.
Could you clarify, ftr, what filesystem each of the partitions are?
I added more info the the second post about the yaffs2 and partitions.

NBC Sports Live Extra app creates /storage on /sdcard

I noticed that I have multiple storage/emulated/0 directories in sdcard. I reboot'ed in recovery mode to make sure no symblinks or bind mounts were involved, ran find and it seems like the NBC app created all those directories to save its data. Has anyone else experienced this?
Code:
adb devices
List of devices attached
HT3XXXXXX recovery
...
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /data type ext4 (rw,seclabel,relatime)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,seclabel,relatime)
find /sdcard/storage/|grep 960835569-1967877118
/sdcard/storage/emulated/0/storage/emulated/0/Android/data/com.phunware.nbc.sochi/cache/960835569-1967877118
/sdcard/storage/emulated/0/storage/emulated/0/storage/emulated/0/storage/emulated/0/Android/data/com.phunware.nbc.sochi/cache/960835569-1967877118
/sdcard/storage/emulated/0/storage/emulated/0/storage/emulated/0/storage/emulated/0/storage/emulated/0/Android/data/com.phunware.nbc.sochi/cache/960835569-1967877118
Thela7 said:
I noticed that I have multiple storage/emulated/0 directories in sdcard. I reboot'ed in recovery mode to make sure no symblinks or bind mounts were involved, ran find and it seems like the NBC app created all those directories to save its data. Has anyone else experienced this?
Click to expand...
Click to collapse
Yes, slightly annoying to say the least. Had this happen on my last device as well and made the mistake of deleting it. Of course it was symlinked and erased my entire internal storage. I'm on a Nexus 6 btw, not that it matters.

Q:Sdcard didn't mounted to read write

Hello all,this is my serious problem i think my sdcard have big problem i can only copies file and not allowed delete,format,download etc...
And then when i opened folder in root system not sdcard dev/block/vold/179:1 force close <<< i'm using root explorer then command on terminal and this is description i get:
$ export PATH=/data/local/bin:$PATH
$su
# dev/block/vold/179:1
dev/block/vold/179:1: permission denied
# dev/block/vold/179:1 rw
dev/block/vold/179:1: permission denied
# mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,mode=755,gid=1000)
/dev/block/mtdblock0 on /system type yaffs2 (rw)
/dev/block/mtdblock2 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock1 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock2 on /cache/download type yaffs2 (rw,nosuid,nodev)
>>> (Read only) /dev/block/vold/179:1 on /mnt/sdcard type vfat (ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
>>> (Read only) /dev/block/vold/179:1 on /mnt/secure/asec type vfat (ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000)
#
You can see it's always (permission denied) and you can see down there it's ro type not rw...
Okay master can you fix this sdcard? thank you.
I'm really confusing with this sdcard
....:banghead::banghead:
Sent from my E15i using Tapatalk 2
Please someone help this is confusing
Also why i inserting into tablet can confirm change write disk to read write and ok i changed but nothing works:banghead::banghead::banghead::banghead:
Sent from my E15i using Tapatalk 2
This is very strict read only sigh....
And i'm using another sdcard on my E15i
Sent from my E15i using Tapatalk 2

Here's a probably dummy device tree!

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)

Categories

Resources