Hi, I performed the steps as you suggested with no luck. Kernel do not boot up.
Couple of points I see:
After last R button I pressed enter button to setup using Serial debugger:
setenv force_avb 1
saveenv
I am doing anything wrong?
fastboot erase bootenv && fastboot oem format && fastboot reboot bootloader
You need to press the R key after executing this
@xiong.zhang I tried the whole setup and found missing partition outputs looking to serial console. Is any previous step I need to perform to get proper partition table?
Logs from last step (flashing img files):
Flashing sparse image at offset 304128
Flashing Sparse Image
… wrote 782131200 bytes to ‘super’
Starting download of 29675668 bytes
…
…
…
…
downloading of 29675668 bytes finished
Flashing sparse image at offset 304128
Flashing Sparse Image
… wrote 30224384 bytes to ‘super’
** Bad device specification mmc userdata_a **
** Bad device specification mmc userdata_a **
Couldn’t find partition mmc userdata_a
Starting download of 2314516 bytes
…
downloading of 2314516 bytes finished
Flashing sparse image at offset 6628352
Flashing Sparse Image
… wrote 19013632 bytes to ‘userdata’
** Bad device specification mmc dtbo_a_a **
** Bad device specification mmc dtbo_a_a **
Couldn’t find partition mmc dtbo_a_a
Starting download of 4600 bytes
downloading of 4600 bytes finished
Flashing Raw Image
… wrote 4608 bytes to ‘dtbo_a’
** Bad device specification mmc dtbo_b_a **
** Bad device specification mmc dtbo_b_a **
Couldn’t find partition mmc dtbo_b_a
Starting download of 4600 bytes
downloading of 4600 bytes finished
Flashing Raw Image
… wrote 4608 bytes to ‘dtbo_b’
** Bad device specification mmc misc_a **
** Bad device specification mmc misc_a **
Couldn’t find partition mmc misc_a
Erasing blocks 5120 to 6144 due to alignment
… erased 524288 bytes from ‘misc’
** Bad device specification mmc frp_a **
** Bad device specification mmc frp_a **
Couldn’t find partition mmc frp_a
Erasing blocks 6144 to 7168 due to alignment
… erased 524288 bytes from ‘frp’
** Bad device specification mmc metadata_a **
** Bad device specification mmc metadata_a **
Couldn’t find partition mmc metadata_a
Starting download of 45132 bytes
downloading of 45132 bytes finished
Flashing sparse image at offset 6595584
Flashing Sparse Image
… wrote 45056 bytes to ‘metadata’
** Bad device specification mmc vbmeta_a_a **
** Bad device specification mmc vbmeta_a_a **
Couldn’t find partition mmc vbmeta_a_a
Starting download of 4096 bytes
downloading of 4096 bytes finished
Flashing Raw Image
… wrote 4096 bytes to ‘vbmeta_a’
** Bad device specification mmc vbmeta_b_a **
** Bad device specification mmc vbmeta_b_a **
Couldn’t find partition mmc vbmeta_b_a
Starting download of 4096 bytes
downloading of 4096 bytes finished
Flashing Raw Image
… wrote 4096 bytes to ‘vbmeta_b’
Hi, I’ve just uploaded the binaries to the board with some modifications to add a new system service, and a new app to test the system service. What’s happening is that when I open the ADB and try to execute almost any default common command, I’ve got the following error:
I’ve just followed all the processes described in the post, is there anything I need to add to the compilation?
Hey guys, just realize that @xiong.zhang instructions were based on Ubuntu and I am working with Windows.
Could be needed any change to use generated mke2fs?
Hello, the above instructions need to be executed on Ubuntu. The burn package we provide contains mke2fs, which can be used directly