I m just rebuilding my stock rom with some mods. Used a random updater script provided in forum (As I don't have my own). Rebuild it in dsixda's kitchen. It says this:
Code:
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system"); mount("ext4", "EMMC", "/dev/block/mmcblk0p18", "/data");
but I've gathered info via adb of my device that looks like this:
Code:
[email protected]:/ $ cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0013af20 000d6800 "cache"
emmc_p3: 00211f20 0018f800 "usrdata"
emmc_p4: 003a1f20 003910e0 "fat"
emmc_p5: 00009f00 00002800 "sec_ro"
emmc_p6: 0000ef20 0012b800 "android"
Code:
[email protected]:/ $ cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000025800000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000001ae00000 0x00000000275e4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000032000000 0x00000000423e4000 2 /dev/block/mmcblk0p3
fat 0x000000007221c000 0x00000000743e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
What to do?
Rep.
Abirwebster said:
I m just rebuilding my stock rom with some mods. Used a random updater script provided in forum (As I don't have my own). Rebuild it in dsixda's kitchen. It says this:
Code:
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system"); mount("ext4", "EMMC", "/dev/block/mmcblk0p18", "/data");
but I've gathered info via adb of my device that looks like this:
Code:
[email protected]:/ $ cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0013af20 000d6800 "cache"
emmc_p3: 00211f20 0018f800 "usrdata"
emmc_p4: 003a1f20 003910e0 "fat"
emmc_p5: 00009f00 00002800 "sec_ro"
emmc_p6: 0000ef20 0012b800 "android"
Code:
[email protected]:/ $ cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000025800000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000001ae00000 0x00000000275e4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000032000000 0x00000000423e4000 2 /dev/block/mmcblk0p3
fat 0x000000007221c000 0x00000000743e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
What to do?
Click to expand...
Click to collapse
Should I mount it as mount("ext4", "EMMC", "/dev/block/mmcblk0", "/system") ?? Any kinda help is appreciated.
Try running
adb shell
mount
If this doesn't give you system partition check your recovery log or use busybox
run_program("/sbin/busybox", "mount", "/system");
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Try running
adb shell
mount
If this doesn't give you system partition check your recovery log or use busybox
run_program("/sbin/busybox", "mount", "/system");
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't see any of /system/, /bootimg/ partitions! Here's the code:
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[email protected] /system ext4 ro,relatime,noauto_da_alloc,commit=1,data=ordered 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_ro /system/secro ext4 ro,relatime,data=ordered 0 0
/dev/block/vold/179:97 /storage/sdcard0 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:97 /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 /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:4 /storage/sdcard1 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/dm-0 /mnt/asec/orangebd.holy.quran-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.desaxedstudios.bassboosterpro-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.adobe.reader-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/com.icloudzone.DeathMoto-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-4 /mnt/asec/com.antutu.pro.batterysaverplus-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-5 /mnt/asec/com.sonyericsson.trackid-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-6 /mnt/asec/com.mcc.zapp-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-7 /mnt/asec/com.ratana.jazzcat.steampunkdroid-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-8 /mnt/asec/com.batteryacid.highwayrider-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-9 /mnt/asec/os.tools.scriptmanager-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-10 /mnt/asec/com.opera.mini.android-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-11 /mnt/asec/org.videolan.vlc.betav7neon-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-12 /mnt/asec/com.imangi.templerun-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-13 /mnt/asec/com.joeykrim.rootcheck-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-14 /mnt/asec/com.jb.gokeyboard.plugin.pad-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-15 /mnt/asec/com.bigeyes0x0.trickstermod-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-16 /mnt/asec/stericson.busybox-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-17 /mnt/asec/com.freemind.fishing-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-18 /mnt/asec/bbc.mobile.news.ww-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-19 /mnt/asec/com.gami.agecalculator-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-20 /mnt/asec/com.instaforex.android.forex.mt4droidtrader-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-21 /mnt/asec/com.speedsoftware.rootexplorer-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-22 /mnt/asec/com.cpuid.cpu_z-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-23 /mnt/asec/net.hasnath.android.keyboard-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-24 /mnt/asec/com.bdodesk.bdnewpapersall-2 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-25 /mnt/asec/com.agilesoftresource-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-26 /mnt/asec/com.vpnoneclick.android-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-27 /mnt/asec/com.mobjoy.roadwarrior-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-28 /mnt/asec/com.touchtype.swiftkey-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-29 /mnt/asec/com.fingersoft.hillclimb-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-30 /mnt/asec/com.imangi.templerun2-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-31 /mnt/asec/com.acr.tubevideodownloader-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-32 /mnt/asec/com.twitter.android-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-33 /mnt/asec/com.androidwasabi.livewallpaper.jellybean-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-34 /mnt/asec/org.zwanoo.android.speedtest-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-35 /mnt/asec/com.tencent.ibibo.mtt-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-36 /mnt/asec/com.androidwasabi.livewallpaper.xperiaz-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
never seen it listed as [email protected] , this is normally where partition info is, maybe try
adb shell
ls dev/block
ls -l dev/block
cat /proc/partitions
df
busybox df -hm
hopefully something should work, otherwise like i said should be in recovery log assuming you have a custom recovery
demkantor said:
never seen it listed as [email protected] , this is normally where partition info is, maybe try
adb shell
ls dev/block
ls -l dev/block
cat /proc/partitions
df
busybox df -hm
hopefully something should work, otherwise like i said should be in recovery log assuming you have a custom recovery
Click to expand...
Click to collapse
My goodness!! Thanks a lot!!
Code:
Partition Logs:
/boot | /dev/bootimg | Size: 6MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/bootimg
Display_Name: Boot
Storage_Name: boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/cache | /dev/block/mmcblk0p2 | Size: 421MB Used: 12MB Free: 409MB Backup Size: 12MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/data | /dev/block/mmcblk0p3 | Size: 796MB Used: 460MB Free: 336MB Backup Size: 460MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p3
Display_Name: Data
Storage_Name: Data
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/misc | /dev/misc | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/misc
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/recovery | Size: 6MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/recovery
Display_Name: Recovery
Storage_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/emmc | /dev/block/mmcblk0p4 | Size: 1822MB Used: 29MB Free: 1792MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent Has_Android_Secure Is_Storage Is_Settings_Storage
Symlink_Path: /emmc/.android_secure
Symlink_Mount_Point: /and-sec
Primary_Block_Device: /dev/block/mmcblk0p4
Display_Name: emmc
Storage_Name: emmc
Backup_Path: /and-sec
Backup_Name: and-sec
Backup_Display_Name: Android Secure
Storage_Path: /emmc
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
/system | /dev/block/mmcblk0p6 | Size: 597MB Used: 572MB Free: 24MB Backup Size: 572MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p6
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/sdcard | /dev/block/mmcblk1p1 | Size: 1886MB Used: 1475MB Free: 410MB Backup Size: 1475MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable IsPresent Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: sdcard
Storage_Name: sdcard
Backup_Path: /sdcard
Backup_Name: sdcard
Backup_Display_Name: sdcard
Storage_Path: /sdcard
Current_File_System: vfat
Fstab_File_System: vfat
Backup_Method: files
/nvram | /dev/nvram | Size: 3MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/nvram
Display_Name: Nvram
Storage_Name: Nvram
Backup_Path: /nvram
Backup_Name: nvram
Backup_Display_Name: Nvram
Storage_Path: /nvram
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/uboot | /dev/uboot | Size: 0MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/uboot
Display_Name: Uboot
Storage_Name: Uboot
Backup_Path: /uboot
Backup_Name: uboot
Backup_Display_Name: Uboot
Storage_Path: /uboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sd-ext | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI Removable
Primary_Block_Device: /dev/block/mmcblk1p2
Display_Name: SD-Ext
Storage_Name: SD-Ext
Backup_Path: /sd-ext
Backup_Name: sd-ext
Backup_Display_Name: SD-Ext
Storage_Path: /sd-ext
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
Hi everybody. I've an hard brick with my Asus ME302KL.
I did a full backup using TWRP v3.2.0, comprehensive of boot and all the possible things I could select. Then I restored it and my device became completely dead.
No ASUS logo
Screen completely black. Even no screen backlight when trying to power on
No fastboot
Obviously no recovery
The device is now recognized as "Qualcomm HS-USB QDLoader 9008" and I think something screwed up with the bootloader.
I've tryed following two paths:
I downloaded QSFP (v2.7.474) in order to use QFIL, but it requires the .mbn files to be flashed and I can't find them anywhere.
I downloaded BoardDiag but it requires a partition.txt file that describes the partition table of the device. I can't find this file anywhere too.
Some probably useful links I've found:
BoardDiag usage (I have some troubles following the thread being in russian): http://4pda.ru/forum/lofiversion/index.php?t643084-4420.html
Partition.txt structure (image from previous link): http://cs5-3.4pda.to/8750059/partiton.jpg?0d987766ec8b46bd23debca950955b1a
http://rom95g.blogspot.com/2017/10/how-to-create-msimagembn-file-flashable.html
https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
Some updates
I came across the Qfil and BoardDiag utils. Anyway, the first requires a .tot file which I can't find anywhere. I actually have a very old backup made with TWRP, but I can't understand if it can be useful.
I also tried with BoardDiag but it requires the partitions table which I don't have.
Main post also updated.
Regarding the .mbn files, it seems from these posts (#1, #2) that they are just the usual .img files. Can anyone please confirm this? In that case, the original firmware provided by ASUS would contain severals .img files (boot.img, bootloader.aboot.img, etc.). I also have an old backup made with TWRP with .win files, which i suppose to be .img binary files with just different extension (the same as .img and .mbn).
The partition.txt is still missing though.
UPDATE:
In the old backup mentioned before i found a recovery log that reports the following blocks. Can it be useful to recreate the partition.txt?
Code:
I:Unmounting main partitions...
Partition Logs:
/cra | /dev/block/mmcblk0p29 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p29
Display_Name: cra
Storage_Name: cra
Backup_Path: /cra
Backup_Name: cra
Backup_Display_Name: cra
Storage_Path: /cra
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/ssd | /dev/block/mmcblk0p27 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p27
Display_Name: ssd
Storage_Name: ssd
Backup_Path: /ssd
Backup_Name: ssd
Backup_Display_Name: ssd
Storage_Path: /ssd
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/ddr | /dev/block/mmcblk0p26 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p26
Display_Name: ddr
Storage_Name: ddr
Backup_Path: /ddr
Backup_Name: ddr
Backup_Display_Name: ddr
Storage_Path: /ddr
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/metadata | /dev/block/mmcblk0p31 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p31
Display_Name: metadata
Storage_Name: metadata
Backup_Path: /metadata
Backup_Name: metadata
Backup_Display_Name: metadata
Storage_Path: /metadata
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modemst1 | /dev/block/mmcblk0p2 | Size: 3MB
Flags: Can_Be_Backed_Up Has_SubPartition IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: ModemST
Storage_Name: ModemST
Backup_Path: /modemst1
Backup_Name: modemst1
Backup_Display_Name: ModemST
Storage_Path: /modemst1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/modemst2 | /dev/block/mmcblk0p3 | Size: 3MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /modemst1
Primary_Block_Device: /dev/block/mmcblk0p3
Display_Name: modemst2
Storage_Name: modemst2
Backup_Path: /modemst2
Backup_Name: modemst2
Backup_Display_Name: modemst2
Storage_Path: /modemst2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/demoapp | /dev/block/mmcblk0p30 | Size: 500MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p30
Display_Name: DemoApp
Storage_Name: DemoApp
Backup_Path: /demoapp
Backup_Name: demoapp
Backup_Display_Name: DemoApp
Storage_Path: /demoapp
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/fsg | /dev/block/mmcblk0p8 | Size: 3MB
Flags: Can_Be_Backed_Up Has_SubPartition IsPresent
Primary_Block_Device: /dev/block/mmcblk0p8
Display_Name: Efs
Storage_Name: Efs
Backup_Path: /fsg
Backup_Name: fsg
Backup_Display_Name: Efs
Storage_Path: /fsg
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/m9kefs1 | /dev/block/mmcblk0p5 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /fsg
Primary_Block_Device: /dev/block/mmcblk0p5
Display_Name: m9kefs1
Storage_Name: m9kefs1
Backup_Path: /m9kefs1
Backup_Name: m9kefs1
Backup_Display_Name: m9kefs1
Storage_Path: /m9kefs1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/m9kefs2 | /dev/block/mmcblk0p6 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /fsg
Primary_Block_Device: /dev/block/mmcblk0p6
Display_Name: m9kefs2
Storage_Name: m9kefs2
Backup_Path: /m9kefs2
Backup_Name: m9kefs2
Backup_Display_Name: m9kefs2
Storage_Path: /m9kefs2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/m9kefs3 | /dev/block/mmcblk0p7 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /fsg
Primary_Block_Device: /dev/block/mmcblk0p7
Display_Name: m9kefs3
Storage_Name: m9kefs3
Backup_Path: /m9kefs3
Backup_Name: m9kefs3
Backup_Display_Name: m9kefs3
Storage_Path: /m9kefs3
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/m9kefsc | /dev/block/mmcblk0p28 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /fsg
Primary_Block_Device: /dev/block/mmcblk0p28
Display_Name: m9kefsc
Storage_Name: m9kefsc
Backup_Path: /m9kefsc
Backup_Name: m9kefsc
Backup_Display_Name: m9kefsc
Storage_Path: /m9kefsc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/aboot | /dev/block/mmcblk0p12 | Size: 5MB
Flags: Can_Be_Backed_Up Has_SubPartition IsPresent
Primary_Block_Device: /dev/block/mmcblk0p12
Display_Name: Bootloader
Storage_Name: Bootloader
Backup_Path: /aboot
Backup_Name: aboot
Backup_Display_Name: Bootloader
Storage_Path: /aboot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl1 | /dev/block/mmcblk0p9 | Size: 1MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p9
Display_Name: sbl1
Storage_Name: sbl1
Backup_Path: /sbl1
Backup_Name: sbl1
Backup_Display_Name: sbl1
Storage_Path: /sbl1
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl2 | /dev/block/mmcblk0p10 | Size: 1MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p10
Display_Name: sbl2
Storage_Name: sbl2
Backup_Path: /sbl2
Backup_Name: sbl2
Backup_Display_Name: sbl2
Storage_Path: /sbl2
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl3 | /dev/block/mmcblk0p11 | Size: 2MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p11
Display_Name: sbl3
Storage_Name: sbl3
Backup_Path: /sbl3
Backup_Name: sbl3
Backup_Display_Name: sbl3
Storage_Path: /sbl3
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/tz | /dev/block/mmcblk0p15 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p15
Display_Name: tz
Storage_Name: tz
Backup_Path: /tz
Backup_Name: tz
Backup_Display_Name: tz
Storage_Path: /tz
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/rpm | /dev/block/mmcblk0p13 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p13
Display_Name: rpm
Storage_Name: rpm
Backup_Path: /rpm
Backup_Name: rpm
Backup_Display_Name: rpm
Storage_Path: /rpm
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/abootb | /dev/block/mmcblk0p18 | Size: 5MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p18
Display_Name: abootb
Storage_Name: abootb
Backup_Path: /abootb
Backup_Name: abootb
Backup_Display_Name: abootb
Storage_Path: /abootb
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl2b | /dev/block/mmcblk0p16 | Size: 1MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p16
Display_Name: sbl2b
Storage_Name: sbl2b
Backup_Path: /sbl2b
Backup_Name: sbl2b
Backup_Display_Name: sbl2b
Storage_Path: /sbl2b
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/sbl3b | /dev/block/mmcblk0p17 | Size: 2MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p17
Display_Name: sbl3b
Storage_Name: sbl3b
Backup_Path: /sbl3b
Backup_Name: sbl3b
Backup_Display_Name: sbl3b
Storage_Path: /sbl3b
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/tzb | /dev/block/mmcblk0p20 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p20
Display_Name: tzb
Storage_Name: tzb
Backup_Path: /tzb
Backup_Name: tzb
Backup_Display_Name: tzb
Storage_Path: /tzb
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/rpmb | /dev/block/mmcblk0p19 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p19
Display_Name: rpmb
Storage_Name: rpmb
Backup_Path: /rpmb
Backup_Name: rpmb
Backup_Display_Name: rpmb
Storage_Path: /rpmb
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/abootu | /dev/block/mmcblk0p21 | Size: 0MB
Flags: Can_Be_Backed_Up Is_SubPartition IsPresent
SubPartition_Of: /aboot
Primary_Block_Device: /dev/block/mmcblk0p21
Display_Name: abootu
Storage_Name: abootu
Backup_Path: /abootu
Backup_Name: abootu
Backup_Display_Name: abootu
Storage_Path: /abootu
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/boot | /dev/block/mmcblk0p14 | Size: 16MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p14
Display_Name: Boot
Storage_Name: Boot
Backup_Path: /boot
Backup_Name: boot
Backup_Display_Name: Boot
Storage_Path: /boot
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/recovery | /dev/block/mmcblk0p25 | Size: 10MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p25
Display_Name: Recovery
Storage_Name: Recovery
Backup_Path: /recovery
Backup_Name: recovery
Backup_Display_Name: Recovery
Storage_Path: /recovery
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/misc | /dev/block/mmcblk0p24 | Size: 1MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mmcblk0p24
Display_Name: misc
Storage_Name: misc
Backup_Path: /misc
Backup_Name: misc
Backup_Display_Name: misc
Storage_Path: /misc
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/system | /dev/block/mmcblk0p22 | Size: 887MB Used: 834MB Free: 52MB Backup Size: 834MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: System
Storage_Name: System
Backup_Path: /system
Backup_Name: system
Backup_Display_Name: System
Storage_Path: /system
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/system_image | /dev/block/mmcblk0p22 | Size: 1536MB
Flags: Can_Be_Backed_Up IsPresent Can_Flash_Img
Primary_Block_Device: /dev/block/mmcblk0p22
Display_Name: System Image
Storage_Name: system_image
Backup_Path: /system_image
Backup_Name: system_image
Backup_Display_Name: System Image
Storage_Path: /system_image
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/data | /dev/block/mmcblk0p32 | Size: 11363MB Used: 114MB Free: 11116MB Backup Size: 114MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media/0
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p32
Length: -16384
Display_Name: Data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media/0
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537
/cache | /dev/block/mmcblk0p23 | Size: 516MB Used: 9MB Free: 507MB Backup Size: 9MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mmcblk0p23
Display_Name: Cache
Storage_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Backup_Display_Name: Cache
Storage_Path: /cache
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/firmware | /dev/block/mmcblk0p1 | Size: 85MB
Flags: Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p1
Display_Name: Radio
Storage_Name: Radio
Backup_Path: /firmware
Backup_Name: firmware
Backup_Display_Name: Radio
Storage_Path: /firmware
Current_File_System: emmc
Fstab_File_System: emmc
Backup_Method: dd
/persist | /dev/block/mmcblk0p4 | Size: 14MB Used: 4MB Free: 10MB Backup Size: 4MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up IsPresent
Primary_Block_Device: /dev/block/mmcblk0p4
Display_Name: Persist
Storage_Name: Persist
Backup_Path: /persist
Backup_Name: persist
Backup_Display_Name: Persist
Storage_Path: /persist
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
/external_sd | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/mmcblk1p1
Alternate_Block_Device: /dev/block/mmcblk1
Display_Name: Micro SDCard
Storage_Name: Micro SDCard
Backup_Path: /external_sd
Backup_Name: external_sd
Backup_Display_Name: Micro SDCard
Storage_Path: /external_sd
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
MTP_Storage_ID: 65538
/usbotg | | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Wipe_Available_in_GUI Removable Is_Storage
Primary_Block_Device: /dev/block/sda1
Alternate_Block_Device: /dev/block/sda
Display_Name: Usb-Otg
Storage_Name: Usb-Otg
Backup_Path: /usbotg
Backup_Name: usbotg
Backup_Display_Name: Usb-Otg
Storage_Path: /usbotg
Current_File_System: auto
Fstab_File_System: auto
Backup_Method: files
MTP_Storage_ID: 65539
Finally solved
I finally found the missing files here.
As reported in the later posts of that thread, I used Miflash2012 to flash the bootloader and the related stuff of the first package.
Then the device apparently became completely unknown (i really hoped to not have to mess with JTAG), but after force reboot (kept power button pressed) I was able to access fastboot and run the debrick-flashall.cmd script. The tablet returned to stock conditions. I now have to unlock it again, but at least the worst part is gone.
Still having problems. I'm now trying to unlock the bootloader again but the unlocking app doesn't work. It just report "An unknown error occurs, which may be a network issue".
From logcat i see this
Code:
D/DMServerUnlock( 4954): Unlock ID: *** here there is an ID that I omit for privacy ***
D/DMServerUnlock( 4954): index of line: 3
D/DMServerUnlock( 4954): DM Server Response: 107
D/DMServerUnlock( 4954): numUnlock ============================================ 107
EDIT:
I found in the settings that the IMEI is set to 0, probably due to Miflash usage. The S/N is instead correct. Investigating...
Strange behaviours
The IMIEI problem is still not solved.
Anyway, I noticed some even stranger behaviours. I can not write anything on the internal memory, both through file manager apps and through USB connection. The partition seems to be read only.
The two versions of the unlock tools (the so called v7 and v8) create these logs:
Code:
W/System.err( 3128): java.io.FileNotFoundException: /sdcard/Unlock_Time.txt: open failed: ENOENT (No such file or directory)
W/System.err( 3128): at libcore.io.IoBridge.open(IoBridge.java:416)
W/System.err( 3128): at java.io.FileOutputStream.<init>(FileOutputStream.java:88)
W/System.err( 3128): at java.io.FileOutputStream.<init>(FileOutputStream.java:73)
W/System.err( 3128): at com.asus.unlock.UnLockActivity.l(Unknown Source)
W/System.err( 3128): at com.asus.unlock.UnLockActivity.a(Unknown Source)
W/System.err( 3128): at com.asus.unlock.o.onClick(Unknown Source)
W/System.err( 3128): at android.view.View.performClick(View.java:4233)
W/System.err( 3128): at android.view.View$PerformClick.run(View.java:17425)
W/System.err( 3128): at android.os.Handler.handleCallback(Handler.java:725)
W/System.err( 3128): at android.os.Handler.dispatchMessage(Handler.java:92)
W/System.err( 3128): at android.os.Looper.loop(Looper.java:137)
W/System.err( 3128): at android.app.ActivityThread.main(ActivityThread.java:5074)
W/System.err( 3128): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err( 3128): at java.lang.reflect.Method.invoke(Method.java:511)
W/System.err( 3128): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
W/System.err( 3128): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
W/System.err( 3128): at dalvik.system.NativeStart.main(Native Method)
W/System.err( 3128): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory)
W/System.err( 3128): at libcore.io.Posix.open(Native Method)
W/System.err( 3128): at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110)
W/System.err( 3128): at libcore.io.IoBridge.open(IoBridge.java:400)
W/System.err( 3128): ... 16 more
Code:
W/UnLockActivity( 2810): Error Log Unlock Time @1
D/DMServerUnlock( 2810): get DMServer Response retry count = 3
D/DMServerUnlock( 2810): Unlock ID: *** S/N omitted **
D/DMServerUnlock( 2810): index of line: 3
D/DMServerUnlock( 2810): DM Server Response: 107
D/DMServerUnlock( 2810): numUnlock ============================================ 107
The v7 clearly states that it can't create the /sdcard/Unlock_Time.txt file. In fact, /sdcard/ can't be even accessed through file xplorers such as MiXplorer (it reports "Not supported").
Apart from the 107 server error, I think also v8 app suffers of this access error ("Error Log Unlock Time @1").
Also all the other applications trying to access /sdcard or /storage/emulated/0 crash.
Permissions fixed
Internal memory fixed by following this post.
For who needs, ME302KL can be rooted by using Framaroot.
Root your device
Boot into android and enable USB debugging
Connect device to PC
Start up "adb shell", then type in "su"
A supersu prompt would pop up on the device, agree to give adb shell root permissions.
In adb shell execute "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist"
In adb shell type "exit" twice to quit.
Execute "adb reboot".
The 107 error code from ASUS persists. I think the only hope is to contact ASUS support (good luck to myself).
So, I decompiled the ASUS unlock app and found that the IMEI is needed, together with the CPU id (which is actually fine), in order to compose the right request to the server.
So i'm first moving into the direction of restoring it.
I found these two guides. Hope to get something out of them.
https://www.htcmania.com/showthread.php?t=969255
http://en.miui.com/thread-260943-1-1.html
Any help is appreciated, although it seems I'll keep talking to myself for entire problem duration. At least I hope all this will be useful to someone in the future
ME302KL bootloader unlock alternatives
Ciao Mantova
Did you get the bootloader unlocked?
How you did it?
Hello everyone!
I'd like to better understand my smartphone's Partitions Layout...
At the moment I'm inside TWRP and I managed to enter into Shell as root:
Code:
\platform-tools>adb.exe shell
~ #
So... I'm gathering these infos:
~ # fdisk /dev/block/mmcblk0
Code:
Found valid GPT with protective MBR; using GPT
Command (m for help): p
Disk /dev/block/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 52 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 131072 303103 84.0M 0700 modem
2 393216 393217 1024 0700 fsc
3 393218 393233 8192 0700 ssd
4 393234 394257 512K 0700 sbl1
5 394258 395281 512K 0700 sbl1bak
6 395282 396305 512K 0700 rpm
7 396306 397329 512K 0700 rpmbak
8 397330 401425 2048K 0700 tz
9 401426 405521 2048K 0700 tzbak
10 405522 406033 256K 0700 devcfg
11 406034 406545 256K 0700 devcfgbak
12 406546 439313 16.0M 0700 dsp
13 439314 442385 1536K 0700 modemst1
14 442386 445457 1536K 0700 modemst2
15 524288 524351 32768 0700 DDR
16 524352 527423 1536K 0700 fsg
17 527424 527455 16384 0700 sec
18 655360 677887 11.0M 0700 splash
19 786432 788479 1024K 0700 aboot
20 788480 790527 1024K 0700 abootbak
21 790528 921599 64.0M 0700 boot
22 921600 1052671 64.0M 0700 recovery
23 1052672 1054719 1024K 0700 devinfo
24 1054720 7346175 3072M 0700 system
25 7471104 7995391 256M 0700 cache
26 7995392 8060927 32.0M 0700 persist
27 8060928 8062975 1024K 0700 misc
28 8062976 8063999 512K 0700 keystore
29 8064000 8064063 32768 0700 config
30 8064064 8588351 256M 0700 oem
31 8650752 8650815 32768 0700 limits
32 8781824 8782847 512K 0700 mota
33 8782848 8784895 1024K 0700 dip
34 8784896 8850431 32.0M 0700 mdtp
35 8850432 8851455 512K 0700 syscfg
36 8851456 8859647 4096K 0700 mcfg
37 8912896 8913151 128K 0700 lksecapp
38 8913152 8913407 128K 0700 lksecappbak
39 8913408 8913919 256K 0700 cmnlib
40 8913920 8914431 256K 0700 cmnlibbak
41 8914432 8914943 256K 0700 cmnlib64
42 8914944 8915455 256K 0700 cmnlib64bak
43 8915456 8915967 256K 0700 keymaster
44 8915968 8916479 256K 0700 keymasterbak
45 9043968 9044479 256K 0700 apdp
46 9044480 9044991 256K 0700 msadp
47 9044992 9045007 8192 0700 dpo
48 9045008 9176079 64.0M 0700 logdump
49 9176080 30535646 10.1G 0700 userdata
~ # mount
Code:
rootfs on / type rootfs (rw,seclabel,size=853376k,nr_inodes=134849)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=936796k,nr_inodes=138672,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
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)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=936796k,nr_inodes=138672)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p25 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/block/mmcblk0p24 on /system type ext4 (rw,seclabel,relatime,data=ordered)
~ # ls -lh /dev/block/platform/soc/7824900.sdhci/ | sort -g
Code:
drwxr-xr-x 2 root root 1020 Feb 17 19:54 by-name
drwxr-xr-x 2 root root 1020 Feb 17 19:54 by-num
lrwxrwxrwx 1 root root 18 Feb 17 19:54 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Feb 17 19:54 mmcblk0p9 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p38 -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p39 -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p40 -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p41 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p42 -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p43 -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p44 -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p45 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p46 -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p47 -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p48 -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mmcblk0p49 -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 22 Feb 17 19:54 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
~ # ls -lh /dev/block/platform/soc/7824900.sdhci/by-name | sort -f -k6
Code:
lrwxrwxrwx 1 root root 21 Feb 17 19:54 aboot -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Feb 17 19:54 abootbak -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Feb 17 19:54 apdp -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 Feb 17 19:54 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib64 -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlib64bak -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 Feb 17 19:54 cmnlibbak -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 Feb 17 19:54 config -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Feb 17 19:54 DDR -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Feb 17 19:54 devinfo -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dip -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dpo -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 Feb 17 19:54 dsp -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Feb 17 19:54 fsc -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Feb 17 19:54 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keymaster -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keymasterbak -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 21 Feb 17 19:54 keystore -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Feb 17 19:54 limits -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 Feb 17 19:54 lksecapp -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 Feb 17 19:54 lksecappbak -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 Feb 17 19:54 logdump -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mcfg -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mdtp -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 Feb 17 19:54 misc -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Feb 17 19:54 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Feb 17 19:54 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Feb 17 19:54 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Feb 17 19:54 mota -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Feb 17 19:54 msadp -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 Feb 17 19:54 oem -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Feb 17 19:54 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Feb 17 19:54 recovery -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 20 Feb 17 19:54 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Feb 17 19:54 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Feb 17 19:54 sbl1 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Feb 17 19:54 sbl1bak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Feb 17 19:54 sec -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Feb 17 19:54 splash -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Feb 17 19:54 ssd -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Feb 17 19:54 syscfg -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Feb 17 19:54 system -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Feb 17 19:54 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Feb 17 19:54 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Feb 17 19:54 userdata -> /dev/block/mmcblk0p49
~ # find / -iname "*fstab*"
Code:
/cache/recovery/recovery.fstab
/cache/recovery/storage.fstab
/system/etc/vold.fstab
/system/vendor/etc/fstab.qcom
find: /sys/kernel/slab/L2TP/IPv6: No such file or directory
find: /sys/kernel/slab/L2TP/IP: No such file or directory
/etc/fstab
/etc/twrp.fstab
Contents of ~ # find / -iname "*fstab*"
Code:
/cache/recovery/recovery.fstab
### EMPTY FILE ###
\\\
/cache/recovery/storage.fstab
/data/media;Internal Storage;
/external_sd;External SD;
/usb-otg;USB OTG;
\\\
/system/etc/vold.fstab
# Copyright (c) 2013, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host
# MTP
#dev_mount sdcard2 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host
\\\
/system/vendor/etc/fstab.qcom
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait, verify
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,resize,forceencrypt=footer,quota
/devices/platform/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/soc/7864900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,noemulatedsd,encryptable=footer
/devices/platform/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/devices/soc/78db000.usb/msm_hsusb_host* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto
/dev/block/bootdevice/by-name/config /frp emmc defaults defaults
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/modem /firmware vfat ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0 wait
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,nosuid,nodev,barrier=1 wait
\\\
/etc/fstab
/dev/block/mmcblk0p25 /cache ext4 rw 0 0
/dev/block/mmcblk0p24 /system ext4 rw 0 0
/dev/block/dm-0 /data ext4 rw 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw 0 0
/usb-otg vfat rw 0 0
\\\
/etc/twrp.fstab
/cache ext4 /dev/block/bootdevice/by-name/cache
/system ext4 /dev/block/bootdevice/by-name/system
/system_image emmc /dev/block/bootdevice/by-name/system
/data ext4 /dev/block/bootdevice/by-name/userdata flags=encryptable=footer;length=-16384
/boot emmc /dev/block/bootdevice/by-name/boot
/recovery emmc /dev/block/bootdevice/by-name/recovery
/misc emmc /dev/block/bootdevice/by-name/misc
/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="External SD";storage;wipeingui;removable
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB OTG";storage;wipeingui;removable
And now... Questions time!
Which fstab should I trust? Why there are so many different ones?
Why my smartphone has the by-name/ directory inside this path: /dev/block/platform/soc/7824900.sdhci/ ?
In case I would use ddto backup or restore or reflash partitions, can i use dd within ADB Shell while I'm into Recovery (TWRP)?
Will dd be capable of reflashing .bin and .img and .mbn partitions even if I am OEM locked-out from Fastboot?
Why I cannot mount /datawhile inside TWRP?
Code:
~ # mount -o noatime,nosuid,nodev,barrier=1,noauto_da_alloc,discard,wait,resize,forceencrypt=footer,quota /dev/block/bootdevice/by-name/userdata /data \\\ mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Device or resource busy
Many thanks guys!!
1. vold fstab is for external storage managed by StorageManagerService in android mode.
vendor/etc fstab is fstab for emmc storage provided by vendor. other fstabs are generated by and only used by TWRP.
2. android partitions are always referenced by it's symlinks generated from kernel. for example on A/B devices the /dev/block/bootdevice/by-name/system is linked to either /dev/block/bootdevice/by-name/system_a or /dev/block/bootdevice/by-name/system_b depending on active slot. in android mode you will see /dev/block/dm-0 instead as the partition is protected by dm-verity.
3. we don't care about real block partition, you can just dd its symlink. (Note, it requires exFAT MicroSD Card, FAT32 has 4 GB file size limit.) it's even more comfortable to just adb pull partition btw.
4. /data is already mounted in TWRP (Device or resource busy) except for failed decrypts (check /tmp/recovery.log)
if /dev/block/bootdevice/by-name/userdata is decrypted successfully, a new (decrypted) block device /dev/block/dm-0 is created by dm-crypt and mounted to /data.
/proc/partitions is maintained in realtime by kernel.
aIecxs said:
4. /data is already mounted in TWRP (Device or resource busy) except for failed decrypts (check /tmp/recovery.log)
if /dev/block/bootdevice/by-name/userdata is decrypted successfully, a new (decrypted) block device /dev/block/dm-0 is created by dm-crypt and mounted to /data.
/proc/partitions is maintained in realtime by kernel.
Click to expand...
Click to collapse
Hey... I'm doing some testing... Here's the steps I've done so far:
wipe / reformat all partitions
entirely re-flash the whole Stock ROM
reboot
completed the Startup Wizard
set a PIN when requested (instead of a Password or a Pattern)
boot into Android
reboot
boot again into Android
reboot to Bootloader
Bash:
fastboot flash recovery twrp.img
reboot into Android
reboot into TWRP
[V] Never show this screen during boot again
Swipe to Allow Modifications
TWRP is NOT asking me the PIN to decrypt /data
/data is NOT mounted, but with different error now (see logs down below)
every time I boot into TWRP, it always keeps me asking Swipe to Allow Modifications!!!
recovery.log
Bash:
[...]
Data successfully decrypted, new block device: '/dev/block/dm-0'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Updating partition details...
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount storage
/data | /dev/block/dm-0 | Size: 0MB Used: 0MB Free: 0MB Backup Size: 0MB
Flags: Can_Be_Mounted Can_Be_Wiped Can_Be_Backed_Up Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent Can_Be_Encrypted Is_Encrypted Is_Decrypted Has_Data_Media Can_Encrypt_Backup Use_Userdata_Encryption Is_Storage Is_Settings_Storage
Symlink_Path: /data/media
Symlink_Mount_Point: /sdcard
Primary_Block_Device: /dev/block/mmcblk0p49
Decrypted_Block_Device: /dev/block/dm-0
Crypto_Key_Location: footer
Length: -16384
Display_Name: data
Storage_Name: Internal Storage
Backup_Path: /data
Backup_Name: data
Backup_Display_Name: Data
Storage_Path: /data/media
Current_File_System: ext4
Fstab_File_System: ext4
Backup_Method: files
MTP_Storage_ID: 65537
I:Unmounting main partitions...
Successfully decrypted with default password.
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Updating partition details...
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount storage
I:Unmounting main partitions...
[...]
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Failed to mount '/data' (No such process)
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount /data/media during GUI startup.
[...]
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
Unable to mount /data/media/TWRP/.twrps
I:Attempt to load settings from settings file...
I:InfoManager file '/data/media/TWRP/.twrps' not found.
I:Backup folder set to '/data/media/TWRP/BACKUPS/WF012646'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
I:Unable to mount '/data'
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:TWFunc::Set_Brightness: Setting brightness control to 128
I:PageManager::LoadFileToBuffer loading filename: '/twres/languages/en.xml' directly
parsing languageFile
parsing languageFile done
I:Translating partition display names
[...]
Failed to mount '/data' (No such process)
I:Actual block device: '/dev/block/dm-0', current file system: 'ext4'
I:TWFunc::Set_Brightness: Setting brightness control to 5
I:TWFunc::Set_Brightness: Setting brightness control to 0
~ # dmesg
Bash:
[...]
[ 5.628850] SELinux: initialized (dev mmcblk0p25, type ext4), uses xattr
[ 5.658433] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.658777] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.667880] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[ 5.668184] EXT4-fs (mmcblk0p49): VFS: Can't find ext4 filesystem
[...]
[ 8.417484] device-mapper: req-crypt: req_crypt_ctr: Mapping block_device /dev/block/mmcblk0p49 to dm-req-crypt ok!
[...]
[ 14.258270] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 14.259729] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 14.259840] EXT4-fs (dm-0): mount failed
[ 14.261825] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 14.263192] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 14.263286] EXT4-fs (dm-0): mount failed
[...]
[ 56.822575] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 56.824051] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 56.824153] EXT4-fs (dm-0): mount failed
[ 56.826017] EXT4-fs (dm-0): warning: maximal mount count reached, running e2fsck is recommended
[ 56.827383] EXT4-fs warning (device dm-0): ext4_enable_quotas:5282: Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
[ 56.827477] EXT4-fs (dm-0): mount failed
[...]
~ # e2fsck /dev/block/dm-0
Bash:
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/dm-0 has unsupported feature(s): quota
e2fsck: Get a newer version of e2fsck!
No such process is known issue with disk quota. try to mount dm-0 read-only with ro,noexec,noload,noatime flags.
(Unrelated) for changing default_password try this app (may be outdated)
Cryptfs Password - Apps on Google Play
Easily set a complex disk encryption password different from the lockscreen one
play.google.com
aIecxs said:
try to mount dm-0 read-only with ro,noexec,noload,noatime flags.
Click to expand...
Click to collapse
Code:
~ # mount -o ro,noexec,noload,noatime /dev/block/dm-0
~ # mount | grep dm-0
/dev/block/dm-0 on /data type ext4 (ro,seclabel,noexec,noatime,norecovery)
And what if I completely disable /data encryption? Is it a viable option?
Are there some infos on how to disable Android encrypting /data? Can Stock ROMs be patched to disable encryption?
disable avb/dm-verity to allow modification on /system.
in vendor/etc fstab replace forceencrypt= flag with encryptable= and format userdata partition.
there exist flashable zip for this
no-verity-opt-encrypt.zip
(recommended for FDE)
Disable_Dm-Verity_ForceEncrypt.zip
(can also remove disk quota, read instructions)