This is a cache of https://discuss.96boards.org/t/after-uefi-the-board-doesnt-go-to-fastboot-mode/2796. It is a snapshot of the page at 2024-09-19T06:46:45.366+0000.
A<strong>f</strong>ter UE<strong>f</strong>I the board doesnt go to <strong>f</strong>astboot mode - HiKey 960 - 96Boards <strong>f</strong>orum

After UEfI the board doesnt go to fastboot mode

Products Support HiKey 960
#1

I did the UEfi steps, and now I want to flash linux , but the board doesnt answer to f in the boot process.
This is my log about writing fastboot :

…[Bds]Booting Boot from SD
[Bds]Booting Grub
[Bds]Booting Android Boot
add-symbol-file /home/buildslave/workspace/96boards-reference-uefi-staging/21/edk2/Build/HiKey960/DEBUG_GCC49/AARCH64/EmbeddedPkg/Application/AndroidBoot/AndroidBootApp/DEBUG/AndroidBootApp.dll 0xBA176000
Loading driver at 0x000BA175000 EntryPoint=0x000BA176000 AndroidBootApp.efi
failed to get Abootimg Size: Invalid Parameter
Error: Image at 000BA175000 start failed: Invalid Parameter
remove-symbol-file /home/buildslave/workspace/96boards-reference-uefi-staging/21/edk2/Build/HiKey960/DEBUG_GCC49/AARCH64/EmbeddedPkg/Application/AndroidBoot/AndroidBootApp/DEBUG/AndroidBootApp.dll 0xBA176000
Image Return Status = Invalid Parameter
[Bds]Booting Android fastboot
add-symbol-file /home/buildslave/workspace/96boards-reference-uefi-staging/21/edk2/Build/HiKey960/DEBUG_GCC49/AARCH64/EmbeddedPkg/Application/Androidfastboot/AndroidfastbootApp/DEBUG/AndroidfastbootApp.dll 0xBA173000
Loading driver at 0x000BA172000 EntryPoint=0x000BA173000 AndroidfastbootApp.efi
Android fastboot mode - version 0.6.
Press RETURN or SPACE key to quit.
fastboot platform: check for partition-type:ptable
Downloading 24576 bytes
24576 / 24576 bytes downloaded (100%)
flashing partition ptable
Done.
fastboot platform: check for partition-type:xloader
Downloading 154752 bytes
154752 / 154752 bytes downloaded (100%)
flashing partition xloader
Done.
fastboot platform: check for partition-type:fastboot
Downloading 1081344 bytes
1081344 / 1081344 bytes downloaded (100%)
flashing partition fastboot
Done.
fastboot platform: check for partition-type:fip
Downloading 1470504 bytes
1470504 / 1470504 bytes downloaded (100%)
flashing partition fip
Done.

#2

Seems to me the booting sequence has entered “fastboot” mode, so don’t need input ‘f’ anymore; and you can flash kernel with command: fastboot flash boot boot.img

#3

No, the device are unable to flash anything in this state.
fastboot device shows nothing

#4

I encounter the same issue, anyone know how to fix it?

After I have done
sudo ./hikey_idt -c config -p /dev/ttyUSB1
and then press the f key, let it stop at:
Press ESCAPE for boot options UfsExecScsiCmds() fails with Target failure
UfsExecScsiCmds() fails with Target failure
UfsExecScsiCmds() fails with Target failure
UfsExecScsiCmds() fails with Target failure
.[Bds]Booting Android fastboot
add-symbol-file /home/buildslave/workspace/96boards-reference-uefi-staging/25/edk2/Build/HiKey960/DEBUG_GCC49/AARCH64/EmbeddedPkg/Application/Androidfastboot/AndroidfastbootApp/DEBUG/AndroidfastbootApp.dll 0xBA172000
Loading driver at 0x000BA171000 EntryPoint=0x000BA172000 AndroidfastbootApp.efi
Android fastboot mode - version 0.6.
Press RETURN or SPACE key to quit.

I found the fastboot can not found any devices.