Hi All,
I'm using imx6q Android 9 BSP and facing issue while mounting the file system.
Below are the logs :
init: init first stage started!
init: Using Android DT directory /proc/device-tree/firmware/android/
init: [libfs_mgr]dt_fstab: file = /proc/device-tree/firmware/android/fstab/vendor/dev_ value =
init: [libfs_mgr]dt_fstab: Failed to find device for partition vendor
init: [libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt
init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
init: Loading SELinux policy
Any Inputs Would be helpful.
Thanks & Regards,
Dileep
Hello,
Please try remounting the system partition as following:
Connect the serial download cable to the host computer (the Type C for the i.MX8M and i.MX8MM. The OTG for the i.M6 SabreSD boards).
Open the adb server.
.\adb.exe start-server
See your connected devices.
.\adb.exe devices
You should see your device and the serial number that is assigned to the device.
Then, enter into Bootloader mode.
.\adb.exe reboot bootloader
Once inside the Bootloader mode, using fastboot you can unlock your phone.
First, see if your computer recognizes your board once inside the Bootloader mode.
.\fastboot.exe devices
If you do not see any device, go to Appendix A of the document.
Finally, Unlock and reboot the board.
.\fastboot.exe oem-unlock
.\fastboot.exe reboot
Note: remember that you need to have activated the oem function in the developer option of your Android device.
After the board rebooted. Start again the adb server
.\adb.exe start-server
.\adb.exe devices
Then root the board
.\adb.exe root
After rooting the board, disable the dm-verity option
.\adb.exe disable-verity
After disabling the verity option, it will request you to reboot your board. Just reboot your board.
.\adb.exe reboot
Finally, when you have access again to the adb command prompt. Remount the system (as root mode).
.\adb.exe root
.\adb.exe remount
Whit that, you should be able to have access to the system partition.
Hope this information can be useful to you.
Best regards,
Diego.
Hi Diego,
Thanks for your response.
I am unable to access adb shell because kernel gets rebooted at the first stage of init.
Please find the below boot logs:
NXP DBG :Blanking/Unblanking FB0
imx-ipuv3 2400000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
NXP DBG :Blanking/Unblanking FB2
imx-ipuv3 2400000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00080000
init: init first stage started!
imx-ipuv3 2800000.ipu: IPU Warning - IPU_INT_STAT_10 = 0x00100000
init: Using Android DT directory /proc/device-tree/firmware/android/
imx-ipuv3 2800000.ipu: IPU Warning - IPU_INT_STAT_5 = 0x00800000
init: [libfs_mgr]dt_fstab: boot_type = emmc
init: [libfs_mgr]dt_fstab: filename = /proc/device-tree/firmware/android/fstab/vendor/dev_emmc and dt_value= /dev/block/platform/soc0/soc/2100000.aips-bus/2198000.usdhc/by-name/vendor
init: Wait for partitions returned after 10010ms
init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found after polling timeout: boot, system, vbmeta, vendor
init: Failed to mount required partitions early ...
init: Reboot start, reason: reboot, rebootTarget: bootloader
init: Reboot ending, jumping to kernel
imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware
atmel_mxt_ts 0-004b: Touchscreen size X4095Y4095
atmel_mxt_ts 0-004b: Touchscreen name Primary
input: Primary as /devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-004b/input/input0
reboot: Restarting system with command 'bootloader'
Any Inputs will be helpful.
Regards,
Dileep
Hello
How did you download the Android image into the board? Did you use UUU?
Best regards,
Diego
Hi Diego,
I'm using MFG Tool to flash the image into the board.
Best regards,
Dileep
Hello,
Unfortunately. Android 9 does not support MFGtool anymore. The only tool that is supported for that Android version is UUU. I suggest you download the Android image with that tool. In the Android Quickstart guide you will find step by step how to use the tool to download the image for every supported board for the BSP.
Best regards,
Diego.
Hi Diego ,
Thank you so much for your reply
Regards,
Dileep