Android flash issue

Hi everyone, please can you help.

I have successfully erased the emmc, installed fast boot nexus tools. used rz boot helper to flash the bootloader.img. With the Zero now in fast boot mode I run the flash-all.bat and I get fast boot error: cannot find bootloader.img no such file or directory.

I originally found that the power shell script to install fastboot installed in to C:\users\me\nexus tools when I ran flash-all.bat from the radxa zero android 9 extracted download it couldn’t find nexus tools. I then edited the flash-all.bat and changed the file path from system32 to the nexus tools directory. That worked but now it says cannot load bootloader.img

Can anyone help please

1 Like

I should also add that everything was run as administrator.

i have made some progress by defining the path to the img files within the flash-all.bat Most wrote ok but I had a few that errored including the system img write. This is the output:
error: no devices/emulators found
OKAY [ 0.039s]
Finished. Total time: 0.041s
OKAY [ 0.038s]
Finished. Total time: 0.040s
Sending ‘bootloader’ (1181 KB) OKAY [ 0.064s]
Writing ‘bootloader’ OKAY [ 0.067s]
Finished. Total time: 0.253s
Sending ‘bootloader-boot0’ (1181 KB) OKAY [ 0.064s]
Writing ‘bootloader-boot0’ OKAY [ 0.087s]
Finished. Total time: 0.275s
Sending ‘bootloader-boot1’ (1181 KB) OKAY [ 0.062s]
Writing ‘bootloader-boot1’ OKAY [ 0.094s]
Finished. Total time: 0.287s
Erasing ‘env’ OKAY [ 0.031s]
Finished. Total time: 0.109s
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.006s
< waiting for any device >
FAILED (Device sent unknown status code: (:heart:U)
fastboot: error: Command failed
OKAY [ 0.040s]
Finished. Total time: 0.041s
Sending ‘dts’ (74 KB) OKAY [ 0.013s]
Writing ‘dts’ OKAY [ 0.146s]
Finished. Total time: 0.284s
Sending ‘dtbo’ (0 KB) OKAY [ 0.010s]
Writing ‘dtbo’ OKAY [ 0.023s]
Finished. Total time: 0.149s
Erasing ‘userdata’ OKAY [ 0.112s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 2956284 4k blocks and 739648 inodes
Filesystem UUID: c6509ca0-52ca-11ec-a743-43273520df5a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

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

Sending ‘userdata’ (124 KB) OKAY [ 0.016s]
Writing ‘userdata’ OKAY [ 0.035s]
Erasing ‘cache’ OKAY [ 0.040s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 286720 4k blocks and 71712 inodes
Filesystem UUID: c68a7718-52ca-11ec-9310-11936a313cbc
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]
Erase successful, but not automatically formatting.
Can’t determine partition type.
FAILED (Device sent unknown status code: :diamonds::heart: :diamonds:)
Finished. Total time: 0.883s
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘param’ OKAY [ 0.031s]
Finished. Total time: 0.112s
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘tee’ OKAY [ 0.030s]
Finished. Total time: 0.109s
Sending ‘vbmeta’ (4 KB) OKAY [ 0.011s]
Writing ‘vbmeta’ OKAY [ 0.023s]
Finished. Total time: 0.154s
Sending ‘odm’ (524 KB) OKAY [ 0.033s]
Writing ‘odm’ OKAY [ 0.041s]
Finished. Total time: 0.195s
Sending ‘logo’ (1386 KB) OKAY [ 0.072s]
Writing ‘logo’ OKAY [ 0.067s]
Finished. Total time: 0.267s
Sending ‘boot’ (9390 KB) OKAY [ 0.425s]
Writing ‘boot’ FAILED (Device sent unknown status code: :diamonds::heart: :diamonds:)
fastboot: error: Command failed
Sending sparse ‘system’ 1/6 (131068 KB) OKAY [ 5.832s]
Writing ‘system’ FAILED (Device sent unknown status code: :diamonds::heart: :diamonds:)
fastboot: error: Command failed
Sending sparse ‘vendor’ 1/2 (120948 KB) OKAY [ 5.381s]
Writing ‘vendor’ FAILED (Device sent unknown status code: :diamonds::heart: :diamonds:)
fastboot: error: Command failed
Sending ‘recovery’ (15920 KB) FAILED (Device sent unknown status code: ►♥a)
fastboot: error: Command failed
Sending ‘product’ (3680 KB) OKAY [ 0.174s]
Writing ‘product’ OKAY [ 0.149s]
Finished. Total time: 0.449s
OKAY [ 0.039s]
Finished. Total time: 0.041s
OKAY [ 0.039s]
Finished. Total time: 0.040s
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.005s
Press any key to exit…

1 Like

I feel this is the culprit! Should I mount it, partition, and format it? It appears it can’t find the System, recovery and other partitions as well. How do I go about creating a partition table for the zero?

Many thanks

Neil

1 Like

Hi, @neilfitzgerald

Install android doesn’t require erase the emmc. You can check the video tutorial here:

thanks, I just get “error [0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup” and then i hear the usb disconnect noise. Please advise

Olá!
Estou tentando seguir o tutorial sugerido mas não consigo fazer meu PC reconhecer o Radxa Zero como porta COM.
O que posso fazer para corrigir isso?

Can you take a screenshot?

Como pode ver eu instalei o driver recomendado mas ele não aparece como porta com na lista de dispositivos. Então o hterm não consegue reconhecer o dispositivo.

Após isso eu instalei ele como USB Serial (CDC) e a porta apareceu porém quando clico em conectar no hterm ele trava e fecha repentinamente.

Inclusive aproveitando a oportunidade só as imagens Ubuntu Focal e Debian Buster funcionaram pois as outras não dão tela e eu queria realmente era uma imagem Android mas nem o Android 9 dá tela.

Tentei também instalar todas as imagens com Balena e com UBS_Burning_tool mas nada feito.

Mais uma vez friso que só funcionam os Ubutu Focal e Debian Buster.

O que há de errado?

I am currently dealing with the same issue. I had these "FAILED (Device sent unknown status code: ♦♥ ♦)" errors occuring at seemingly random points when executing the flash-all.bat. I have tried to execute each command manually and just repeat it if i got an error. This worked up to the point when i had to flash system. At this stage i keep getting this:

c:\platform-tools>fastboot flash system C:\Users\neoya\Downloads\radxa_zero_android_9_20220311-fastboot.img\system.img

Sending sparse 'system' 1/6 (131068 KB)            OKAY [  5.854s]

Writing 'system'                                   OKAY [  5.435s]
Sending sparse 'system' 2/6 (131068 KB)            FAILED (Device sent unknown status code: ♦♥  ♦)
fastboot: error: Command failed

I have tried different ports and usb cables, but the same error still persists. Could it be a hardware problem with the radxa zero?

1 Like

Hi guys! Same issue here :sob:
Please, does anyone know how to overcome this?

Hi @jack ,Would you mind lending us a hand? I’m experiencing a similar issue to what @neoyarus mentioned.

it is some kind of problem with windows drivers. I had the same issue and with linux it is easy as hell.

1 Like

Thank you @ustix!! I have only seen your message now. I still have to try it on Linux but I would like to thank you in advance!!!

Yeeeesss! I tried with Linux and it worked :raised_hands: So, thank you guys!!!