Radxa-zero cannot boot android

arzak · August 8, 2022, 2:18am

Hi, I’ve followed Android9 (eMMC) installation here on my ubuntu.
My step:

Load bootloader.img [success]
Execute flash-all.sh

./flash-all.sh
error: no devices/emulators found
OKAY [  0.040s]
Finished. Total time: 0.040s
OKAY [  0.039s]
Finished. Total time: 0.039s
Sending 'bootloader' (1181 KB)                     OKAY [  0.068s]
Writing 'bootloader'                               OKAY [  0.066s]
Finished. Total time: 0.248s
Sending 'bootloader-boot0' (1181 KB)               OKAY [  0.070s]
Writing 'bootloader-boot0'                         OKAY [  0.086s]
Finished. Total time: 0.271s
Sending 'bootloader-boot1' (1181 KB)               OKAY [  0.067s]
Writing 'bootloader-boot1'                         OKAY [  0.086s]
Finished. Total time: 0.267s
Erasing 'env'                                      OKAY [  0.031s]
Finished. Total time: 0.107s
OKAY [  0.040s]
Finished. Total time: 0.040s
OKAY [  0.038s]
Finished. Total time: 0.038s
Sending 'dts' (74 KB)                              OKAY [  0.014s]
Writing 'dts'                                      OKAY [  0.146s]
Finished. Total time: 0.279s
Sending 'dtbo' (0 KB)                              OKAY [  0.010s]
Writing 'dtbo'                                     OKAY [  0.023s]
Finished. Total time: 0.142s
Erasing 'userdata'                                 OKAY [  1.474s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 14238204 4k blocks and 3563520 inodes
Filesystem UUID: 7db9c398-867b-4990-b039-4140605ebf84
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done   

Sending 'userdata' (316 KB)                        OKAY [  0.028s]
Writing 'userdata'                                 OKAY [  0.041s]
Erasing 'cache'                                    OKAY [  0.060s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 286720 4k blocks and 71712 inodes
Filesystem UUID: 1ed670e1-9d76-409d-a7fb-0d04661faf6a
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'cache' (84 KB)                            OKAY [  0.014s]
Writing 'cache'                                    OKAY [  0.031s]
Erasing 'metadata'                                 OKAY [  0.033s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'metadata' (44 KB)                         OKAY [  0.012s]
Writing 'metadata'                                 OKAY [  0.029s]
Finished. Total time: 2.682s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'param'                                    OKAY [  0.037s]
Finished. Total time: 0.113s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'tee'                                      OKAY [  0.037s]
Finished. Total time: 0.112s
Sending 'vbmeta' (4 KB)                            OKAY [  0.010s]
Writing 'vbmeta'                                   OKAY [  0.024s]
Finished. Total time: 0.144s
Sending 'odm' (524 KB)                             OKAY [  0.036s]
Writing 'odm'                                      OKAY [  0.042s]
Finished. Total time: 0.188s
Sending 'logo' (1386 KB)                           OKAY [  0.078s]
Writing 'logo'                                     OKAY [  0.066s]
Finished. Total time: 0.262s
Sending 'boot' (9392 KB)                           OKAY [  0.452s]
Writing 'boot'                                     OKAY [  0.327s]
Finished. Total time: 0.955s
Sending sparse 'system' 1/6 (131068 KB)            OKAY [  6.433s]
Writing 'system'                                   OKAY [  4.236s]
Sending sparse 'system' 2/6 (131068 KB)            OKAY [  6.427s]
Writing 'system'                                   OKAY [  4.519s]
Sending sparse 'system' 3/6 (131068 KB)            OKAY [  6.342s]
Writing 'system'                                   OKAY [  4.523s]
Sending sparse 'system' 4/6 (131068 KB)            OKAY [  6.375s]
Writing 'system'                                   OKAY [  4.517s]
Sending sparse 'system' 5/6 (131068 KB)            OKAY [  6.373s]
Writing 'system'                                   OKAY [  4.525s]
Sending sparse 'system' 6/6 (34524 KB)             OKAY [  1.671s]
Writing 'system'                                   OKAY [  1.209s]
Finished. Total time: 57.270s
Sending sparse 'vendor' 1/2 (120948 KB)            OKAY [  5.868s]
Writing 'vendor'                                   OKAY [  3.898s]
Sending sparse 'vendor' 2/2 (107184 KB)            OKAY [  5.382s]
Writing 'vendor'                                   OKAY [  3.702s]
Finished. Total time: 18.966s
Sending 'recovery' (15922 KB)                      OKAY [  0.790s]
Writing 'recovery'                                 OKAY [  0.535s]
Finished. Total time: 1.445s
Sending 'product' (3680 KB)                        OKAY [  0.182s]
Writing 'product'                                  OKAY [  0.142s]
Finished. Total time: 0.435s
OKAY [  0.039s]
Finished. Total time: 0.039s
OKAY [  0.046s]
Finished. Total time: 0.046s
Rebooting                                          OKAY [  0.003s]
Finished. Total time: 0.305s

Unplug and replug usb

But the device cannot boot android after successfull installation, my lcd only show “amllogic logo S905Y2”.
What’s wrong?

arzak · August 8, 2022, 9:50am

Now I can fond android device using adb devices

List of devices attached
1234567890	device

and lsusb

Bus 003 Device 037: ID 18d1:4e40 Google Inc. Nexus 7 (fastboot)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 1bcf:2c1e Sunplus Innovation Technology Inc. HP Truevision HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

there is Google Inc. Nexus 7 (fastboot) that is android device.
and I can enter to adb shell.

But my lcd only show Amlogic.

arzak · August 9, 2022, 8:53am

Solved, the radxa-zero can boot android 9 after I use my old monitor. I think my new monitor is not compatible or needs setup.