The flash-all.bat disconnects the device and I had to reconnect and switch to fastbootmode again. Then the script goes further. When the script is done the OS should be flashed. But in my case it only shows the first splash screen again and again. I tried it so many times and with so many things but always the same result.
Now im at a point where im not be able to turn the Radxa Zero in Fastboot mode. The bootloader.bin and the factory-loader.bin are not working anymore for it.
What am I doing wrong?
Is there a IMG file for Android to just flash with BalenaEtcher?
i have the exactly same problem. i tried so many different things from the wiki guide, and no result.
I feel like my problem is connected to Uboot. It seems like it doesnt boot at all. Screen is just black.
/tmp/TemporaryFile-lvYJfl: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
******** Did you mean to fastboot format this ext4 partition?
Im stopping, i dont want to burn out the emmc. I switched to Coreelec. I erased with radxa-erase-emmc.bin. Plugged into Ubuntu and flashed with etcher. K*di works perfectly on the Zero
Install ADB/Fastboot tools (just google it) and add them Both to PATH in Windows 10 (It has to be added to path to work) (add both adb.exe and fastboot.exe to PATH)
Step 1: Hold USB Boot button and Use RZ Boot Helper to flash radxa-zero-erase-emmc.bin (this will erase the emmc so back up first if necessary)
Step 2: Open RZ Boot Helper and also Open Flash-All.bat, then Replug in while holding USB Button and flash bootloader.img from the Android image folder, the moment it stops flashing it it’ll reboot into Fastboot mode and the Flash-All.bat script will start.
Step 3: The Flash-All.bat script will STOP early and your device will disconnect, just unplug it and plug it back in. The script will finish. And board will boot into Android 9…
I already had my monitor plugged in. The MBOX logo takes a few, be patient
No I don’t get it. The first half of the “flash-all.bat” runs fine. But when I replug the device I have to press the USB Boot button and run the “bootloader.bin” from the android folder again. Then the script goes further. But the writing for near everything fails. How exactly do you reconnect the device? Just replug the USB cable or what you have done?
error: no devices/emulators found
< waiting for any device >
OKAY [ 0.040s]
Finished. Total time: 0.040s
OKAY [ 0.040s]
Finished. Total time: 0.040s
Sending ‘bootloader’ (1181 KB) OKAY [ 0.059s]
Writing ‘bootloader’ OKAY [ 0.060s]
Finished. Total time: 0.250s
Sending ‘bootloader-boot0’ (1181 KB) OKAY [ 0.080s]
Writing ‘bootloader-boot0’ OKAY [ 0.085s]
Finished. Total time: 0.320s
Sending ‘bootloader-boot1’ (1181 KB) OKAY [ 0.060s]
Writing ‘bootloader-boot1’ OKAY [ 0.092s]
Finished. Total time: 0.267s
Erasing ‘env’ OKAY [ 0.038s]
Finished. Total time: 0.123s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
< waiting for any device >
At this point it disconnects and I have to reconnect it.
OKAY [ 0.035s]
Finished. Total time: 0.045s
OKAY [ 0.040s]
Finished. Total time: 0.040s
Sending ‘dts’ (74 KB) OKAY [ 0.015s]
Writing ‘dts’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
Sending ‘dtbo’ (0 KB) OKAY [ 0.010s]
Writing ‘dtbo’ OKAY [ 0.025s]
Finished. Total time: 0.230s
Erasing ‘userdata’ OKAY [ 0.387s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 14238204 4k blocks and 3563520 inodes
Filesystem UUID: 3cc0c9ee-85ef-11ec-a363-63e393b01378
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.016s]
Writing ‘userdata’ OKAY [ 0.047s]
Erasing ‘cache’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘param’ OKAY [ 0.031s]
Finished. Total time: 0.108s
******** Did you mean to fastboot format this ext4 partition?
Erasing ‘tee’ OKAY [ 0.031s]
Finished. Total time: 0.115s
Sending ‘vbmeta’ (4 KB) OKAY [ 0.016s]
Writing ‘vbmeta’ OKAY [ 0.016s]
Finished. Total time: 0.163s
Sending ‘odm’ (524 KB) OKAY [ 0.031s]
Writing ‘odm’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
Sending ‘logo’ (1386 KB) OKAY [ 0.069s]
Writing ‘logo’ OKAY [ 0.069s]
Finished. Total time: 0.277s
Sending ‘boot’ (9390 KB) OKAY [ 0.443s]
Writing ‘boot’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
Sending sparse ‘system’ 1/6 (131068 KB) OKAY [ 6.003s]
Writing ‘system’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
Sending sparse ‘vendor’ 1/2 (120948 KB) OKAY [ 5.611s]
Writing ‘vendor’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
Sending ‘recovery’ (15920 KB) OKAY [ 0.733s]
Writing ‘recovery’ FAILED (Device sent unknown status code: )
fastboot: error: Command failed
Sending ‘product’ (3680 KB) OKAY [ 0.178s]
Writing ‘product’ OKAY [ 0.142s]
Finished. Total time: 0.457s
OKAY [ 0.031s]
Finished. Total time: 0.031s
OKAY [ 0.038s]
Finished. Total time: 0.038s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
All I did was run the flashall.bat when it disconnected I just unplugged and plugged back in. I didn’t hold down the USB button at the point where it disconnects
When I unplug and replug it, it wants to boot the half flashed OS and it shows the first splashscreen again and again. To come in fastboot mode again I have to replug it with the USB button and execute the bootloader again.
Can you try modify the flash-all.bat and delete fastboot reboot-bootloader line that’s above ping command? I flashed Android with flash-all.sh in Linux before without problem so this is the difference between those 2 files.
All I did was run the flashall.bat when it disconnected I just unplugged and plugged back in. I didn’t hold down the USB button at the point where it disconnects
