I want to put the built Android OS image into the actual machine (failed to load/verify boot images)

I would like to put the Android OS image I built into the actual machine (Pixel 3a).
The version is Android 9.0 and the tag (branch) is Android-9.0.0_r47.Pixel 3a is supported (Reference)
Follow the document and hit the fastboot flashall-w command in fastboot(fastbootd) mode.

 yamakentoc:/home/yamakentoc/:~$fastboot flashall-w
--------------------------------------------
Bootloader Version...: b4s4-0.2-5736883
Baseband Version...: g670-00030-191028-B-5972069
Serial Number........:94LAY0R0QK
--------------------------------------------
Checking 'product' OKAY [0.000s]
Setting current slot to 'b' OKAY [0.081s]
Sending 'boot_b' (65536 KB) OKAY [1.690s]
Writing 'boot_b' OKAY [0.434s]
Sending 'dtbo_b' (8192KB) OKAY [0.211s]
Writing 'dtbo_b' OKAY [0.113s]
Sending 'vbmeta_b' (4 KB) OKAY [0.001s]
Writing 'vbmeta_b' OKAY [0.002s]
Resizing 'product_b' OKAY [0.005s]
Resizing 'system_b' OKAY [0.004s]
Resizing 'vendor_b' OKAY [0.004s]
Resizing 'system_b' OKAY [0.005s]
Sending sparse 'system_b' 1/3 (524284KB) OKAY [13.756s]
Writing 'system_b' OKAY [3.394s]
Sending sparse'system_b'2/3 (524284KB) OKAY [13.701s]
Writing 'system_b' OKAY [3.619s]
Sending sparse 'system_b' 3/3 (133160 KB) OKAY [3.476s]
Writing 'system_b' OKAY [1.217s]
Sending 'system_a' (91744 KB) OKAY [2.375s]
Writing 'system_a' OKAY [0.615s]
Erasing 'userdata' OKAY [0.062s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [0.005s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting OKAY [0.000s]
Finished.Total time:44.881s
yamakentoc:/home/yamakentoc/:~$

There was no error like this, and I think it went in well (probably).This should boot...

Enter fastboot mode and the screen displays Enterreazon:failed to load/verify boot images.

What's wrong?
As you can see from the image, the boot loader is unlocked.
It also specifies ANDROID_PRODUCT_OUT=/home/yamakentoc/AOSP/out/target/product/sargo/.

I look forward to your kind cooperation.

android

2022-09-29 20:27

1 Answers

Self solved!
A binary hardware support file had to be downloaded from the ↓ site to the root directory!
https://developers.google.com/android/drivers

I summarized the details in Qiita.
https://qiita.com/yamakentoc/items/564108cd5ad207193f0e

2022-09-29 20:27

If you have any answers or tips

Popular Tags

python x 4647

android x 1593

java x 1494

javascript x 1427

c x 927

c++ x 878

ruby-on-rails x 696

php x 692

python3 x 685

html x 656