Unable to start Android system using self compiled images

#1

Using the guidance of this article:
Rock5/guide/android12 - Radxa Wiki
compile Android:
radxa:rock-android12 $ source build/envsetup.sh
radxa:rock-android12 $ lunch RadxaRock5B-userdebug
radxa:rock-android12 $ ./build.sh -UACKup

And use balenaEtcher to flash gpt.img into the SD card
gpt.img: rock5a/RADXAROCK5A_USERDEBUG_RK3588S-ROCK-5A_ENG…20230724.223006_20230724.2230/IMAGES/gpt.img

but android cannot boot up. It enters recovery every time.

20230725100853
20230725100853.jpg2312×1736 1.33 MB

Does anyone know what’s going on?

#2

Does the image contain all the partitions? They are listed as not able to be mounted.

#3

I noticed this,
E: Trying mount fs/dev/block/mmc/blk0p1 to vfat
E: Trying mount/dev/block/mmcblk0p1 to ntfs
E: Trying mount/dev/block/mmcblk0 ntfs
E: Failed to mount/mnt/external_sd error: no such device

E: [libfs_mgr] Failed to open ‘/dev/block/by name/cache’: No such file or directory
E: [libfs_mgr] Failed to mount/cache: No such file or directory

E: Failed to mount/cache/recovery/last_ Locate
E: Failed to clear BCB message: failed to open/dev/block/by name/msic: No such file or directory

I am using the official compilation script，how to solve this issus?

#4

Yes, this is what I was referring to. Can you check if the SD card (or whatever you’re using) contains all of the partitions required? You can view them using lsblk -t or gnome disks or gparted.

#5

This is lsblk -t result

image
image.png1041×478 199 KB

this is sudo fdisk -l

image
image.png797×531 237 KB

#6

All the partitions seem to be present, I don’t know what’s wrong then. Maybe 5A has trouble with this particular SD card? On 5B some that work with Linux don’t work on Android.

#7

Is it possible that this issus is related to spi nor flash?

#8

@punan2010 were you able to get it working?

#9

@punan2010 Any update on this issue?

#10

@yanw Please check the above issue. Seems to only affect microSD installation:

I can successfully create an update image for eMMC, and it works fine. However, the gpt.img for the SD card is causing mounting issues, even though I am using the same manifestation as provided in Radxa’s documentation for Android AOSP 14.

@vegg_v Please make sure you have erased the eMMC before booting from microSD.

#11

I have erased the emmc . The issue I have figured out is The Android image provided by radxa is working fine it has mounted block devices

console:/ $ ls /dev/block/by-name/                                             
backup          dtbo            mmcblk1         security        userdata
baseparameter   metadata        mmcblk1boot0    super           vbmeta
boot            misc            mmcblk1boot1    trust
cache           mmcblk0         recovery        uboot

In my emmc image I’m getting these devices installed properly but in gpt.img there is only mmcblk devices:

# ls /dev/block/by-name/mmcblk1                                                
mmcblk1         mmcblk1boot0    mmcblk1boot1

also I’m not getting fstab in /vendor/etc/fstab.rk30board.

1 Like