fastboot 刷机进fastboot “fastboot flash -w”

 1、检查开机log:
     [    6.482185] EXT4-fs (mmcblk0p57): VFS: Can't find ext4 filesystem
 
2、adb shell mount
    /dev/block/mmcblk0p57 on /metadata type ext4 (rw,seclabel,nosuid,nodev,noatime,discard)
 
3、dump metadata: QFIL
     C:\Users\AppData\Roaming\Qualcomm\QFIL\COMPORT_213\ReadData_emmc_Lun0_0x538010_Len32768_DT_19_01_2021_10_22_52.bin

4、使用e2fsck检查metadata数据是否正常
CC:/ # e2fsck -v data/ReadData_emmc_Lun0_0x538010_Len32768_DT_19_01_2021_10_22_52.bin
e2fsck 1.44.4 (18-Aug-2018)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open data/ReadData_emmc_Lun0_0x538010_Len32768_DT_19_01_2021_10_22_52.bin

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>
！！！以上，是从进fastboot的设备里dump出来的metadata，很明显看到数据异常。

CC:/ # e2fsck -f data/ReadData_emmc_Lun0_0x538010_Len32768_DT_19_01_2021_10_43_22-OK.bin
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
data/ReadData_emmc_Lun0_0x538010_Len32768_DT_19_01_2021_10_43_22-OK.bin: 17/4096 files (0.0% non-contiguous), 1174/4096 blocks
！！！以上，是从进OK的设备里dump出来的metadata，很明显看到数据正常。

 

参考：元数据加密  |  Android 开源项目  |  Android Open Source Project