Can you try to manually flash the contents one-by-one?
Reboot it, then enter fastboot. Then
fastboot flash partition <path-to-partition.txt>
fastboot flash firstboot <path-to-firstboot.img>
fastboot flash recovery <path-to-recovery.img>
fastboot flash system <path-to-system.img>
fastboot flash secondboot <path-to-secondboot.img>
Then we can see which part actually fails. If all of them succeeded, run flash_all.bat again.
Yes. You entered the incorrect command.
<path-to-xxx.txt> refers to the windows path to that “xxx” file, not a direct copy-and-paste.
So for example, if the partition.txt is at C:\AAU01210415\images\partition.txt, you should type
fastboot flash partition C:\AAU01210415\images\partition.txt
or
fastboot flash partition images\partition.txt
if your console is already in C:\AAU01210415 directory.
Looks like you have no installed the ADB tools, therefore the console does not recognize the “fastboot” command.
Try to follow the step 1 from guide below
https://docs.cubepilot.org/user-guides/herelink/herelink-user-guides/generate-a-bug-report#1-install-adb-and-google-drivers
The installation was performed several times using the video without success. adb can still be started, but it fails with fastboot. How to fix the problem?
because it requires more arguments to understand what you want to do
eg: fastboot flash partition .\images\partition.txt
You may check this by entering fastboot --help
