How to Flash Android 9 on IMX8 with 128G eMMC

[weikeng-jimmy]

Hi Sir,

My customer want to expand EMMC size from 32GB to 128GB. We modify and new a 128GB bpt file as below.

1.

{
"settings": {
"disk_size": "128 GiB",
"disk_alignment": 2097152,
"first_partition_offset": 8388608
},

2. Modify ~/ANDROID_CODEBASE/device/fsl/imx8m/rom5720_a1/BoardConfig.mk

# Support gpt
BOARD_BPT_INPUT_FILES += device/fsl/common/partition/device-partitions-13GB-ab.bpt
ADDITION_BPT_PARTITION = partition-table-7GB:device/fsl/common/partition/device-partitions-7GB-ab.bpt \
partition-table-128GB:device/fsl/common/partition/device-partitions-128GB-ab.bpt \
partition-table-28GB:device/fsl/common/partition/device-partitions-28GB-ab.bpt

We try to use uuu tool and get a fail when use download command.

./uuu_imx_android_flash.sh -f imx8mq -a -e -c 128

Please help to modify a "128GB dual-bootloader" .bpt file for 128G eMMC.

Thansk~

[cklim]

I suspect 119 is too big to accommodate the OS files. Please try 112 instead.

This is what i did for MX8QXP_MEK, and i was able to extend the userdata size to 112GB.

1. Copy partitions-28GB-ab.bpt, paste and rename it to partitions-112GB-ab.bpt. Change 28 to 112 as follow

{
"settings": {
"disk_size": "112 GiB",
"disk_alignment": 2097152,
"first_partition_offset": 8388608
},

2. Modify ~/ANDROID_CODEBASE/device/fsl/imx8m/rom5720_a1/BoardConfig.mk

# Support gpt
BOARD_BPT_INPUT_FILES += device/fsl/common/partition/device-partitions-13GB-ab.bpt
ADDITION_BPT_PARTITION = partition-table-7GB:device/fsl/common/partition/device-partitions-7GB-ab.bpt \
partition-table-112GB:device/fsl/common/partition/device-partitions-112GB-ab.bpt \
partition-table-28GB:device/fsl/common/partition/device-partitions-28GB-ab.bpt

3. Edit uuu_imx_android_flash.sh or uuu_imx_android_flash.bat script to accept 112, then use following command.

./uuu_imx_android_flash.sh -f imx8mq -a -e -c 112

Boot up the system and perform factory reset after flashing the image. Good luck.

[Rita_Wang]

Could you share us your 128G emmc part num or picture to us? Many thanks.

Have a nice day

[Rita_Wang]

The fail maybe caused by the 119 size, here recommend you to try the smaller size, such as 40, 60,80, 100, 116 and so on. If lower size works OK, add step by steps.

By the way, only modify the file device-partitions-128GB-ab.bpt the

"disk_size": "** GiB"

[Rita_Wang]

Could you share us the fail information?

[weikeng-jimmy]

Hi Sir,

My customer first change to 40GB emmc size , it's can boot up system . We will try 60,80 100 116size step by step , and share the fail log to you.

[weikeng-jimmy]

Hi Sir,

We change Emmc size to 80GB and get below error log.

........ wrote 12722176 bytes to 'vendor_a'
request 00000000ba29cbc0 was not queued to ep1in-bulk
request 00000000ba29cbc0 was not queued to ep1in-bulk
request 00000000ba29cbc0 was not queued to ep1in-bulk
Starting download of 4096 bytes
request 00000000ba29cbc0 was not queued to ep1in-bulk
request 00000000ba29cbc0 was not queued to ep1in-bulk

downloading of 4096 bytes finished
writing to partition 'vbmeta_a'
Initializing 'vbmeta_a'
switch to partitions #0, OK
mmc0(part 0) is current device
Writing 'vbmeta_a'

MMC write: dev # 0, block # 167759872, count 8 ... 8 blocks written: OK
Writing 'vbmeta_a' DONE!
request 00000000ba29cbc0 was not queued to ep1in-bulk
erase target is MMC:0
Erasing blocks 7569408 to 7577600 due to alignment
........ erased 4194304 bytes from 'misc'
request 00000000ba29cbc0 was not queued to ep1in-bulk
erase target is MMC:0
Erasing blocks 7581696 to 7583744 due to alignment
........ erased 1048576 bytes from 'presistdata'
request 00000000ba29cbc0 was not queued to ep1in-bulk
erase target is MMC:0
Erasing blocks 167755776 to 167757824 due to alignment
........ erased 1048576 bytes from 'fbmisc'
request 00000000ba29cbc0 was not queued to ep1in-bulk
avb_ab_flow.c:30: ERROR: Magic is incorrect.
avb_ab_flow.c:112: ERROR: Error validating A/B metadata from disk. Resetting and writing new A/B metadata to disk.
request 00000000ba29cbc0 was not queued to ep1in-bulk
erase target is MMC:0
Erasing blocks 8634368 to 167755776 due to alignment

[Rita_Wang]

As you are you using 128GB, you can try the 112 as the above friend recommend.

[weikeng-jimmy]

Hi Sir,

112GB size still failure , and 60GB size use uuu download normal .

[Rita_Wang]

How about the value above 60?

[weikeng-jimmy]

80GB still fail .

[Rita_Wang]

The fail information is still same as above you sent?

[weikeng-jimmy]

Yes , it's 80GB failure log.

[Rita_Wang]

Hi,

The configuration method is the same. It seems that your emmc is 64GB. Could you confirm again about customer's emmc? If it is 128GB or 64GB?

Have a nice day

Best Regards

Rita

[weikeng-jimmy]

Hi Sir,

It's 128GB.

[Rita_Wang]

I have saw you picture and discuss with our team members, maybe you can try another one emmc, not this one, If you have on your side.

[weikeng-jimmy]

Hi Sir,

Do you have any update~ Thanks!

[weikeng-jimmy]

We want to change Emmc size to 128GB not 28GB .So We use 128GB .bpt file to generate 128GB .img file You means can use partition-table.img to burn 128GB Emmc ?

[Rita_Wang]

Yes, the 32G or above you can use it.

[weikeng-jimmy]

The test result is still show 32GB not 128GB as below post . Please help to check it. Thanks~

[Rita_Wang]

Here you do not need to modify the bpt file, you can ask customer to rename partition-table.img to partitiontable-
28GB.img in the corresponding UUU script.