itop4412的recovery无法启动的问题

来源：互联网发布：廖雪峰python百度云编辑：程序博客网时间：2024/06/05 20:26

1.问题现象itop开发板烧录recovery后竟然无法启动recovery，然后尝试用fastboot直接启动recovery也不成功：fastboot boot recovery.img 。在终端打印了错误信息：

Starting download of 4960256 bytes....downloading of 4960256 bytes finishedReceived 4 bytes: bootKernel size: 003e00f4Ramdisk size: 000d983cBooting raw image..Boot with zImageWrong Ramdisk Image Format[err] boot_get_ramdisk

2.问题分析
recovery分区表如下：
分区表路径在安卓源码下：out/target/product/smdk4x12/recovery/root/etc/recovery.fstab

# Android fstab file.#<src>                  <mnt_point>         <type>    <mnt_flags and options>                               <fs_mgr_flags># 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#itop4412 2015-06-08# dg add  "check"  options to /data,/cache for safty data storage. on 16G eMMC, sometimes mount errors happen,so need check and repair  before mount. #/dev/block/mmcblk0p3    /data               ext4      noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc,errors=panic    wait#/dev/block/mmcblk0p4    /cache              ext4      noatime,nosuid,nodev,nomblk_io_submit    wait#/dev/block/mmcblk0p1    /boot               ext4      defaults   defaults/dev/block/mmcblk0p2    /system             ext4      rw                                                       wait/dev/block/mmcblk0p3    /data               ext4      noatime,nosuid,nodev,nomblk_io_submit,noauto_da_alloc    wait,check/dev/block/mmcblk0p4    /cache              ext4      noatime,nosuid,nodev,nomblk_io_submit                    wait,check#/dev/block/mmcblk0p1    /recovery               ext4      defaults   defaultsboot                    /boot               mtd     defaults   defaultsRecovery        /recovery           mtd         defaults   defaultskernel          /kernel             mtd         defaults   defaultsramdisk         /ramdisk            mtd         defaults   defaults

1 0