repack system.img erfos format can not boot successfully on phone

[soncao0212-commits]

sir, i really need your help.
My phone uses erofs file system and i have got the system.img file from the phone. I want to fix it to remove some default junk software on the phone and i used your software. It works perfectly and conveniently. But after repacking the system.img file in erfos format, i flashed it back to the phone, and unfortunately, it didn't work, the phone bootlooped. I did a quick check and found that the uuid of the original file and the repack file were different, is this the cause, i would like to ask you for advice, any help from you is extremely important and valuable to me at this time

[ravindu644]

Yes, it should bootloop, even it did in my device

It happens because of Android verified boot.

So, we have to disable it.

you can disable the AVB related lines from your vendor_boot partition's fstab(s) if your phone is GKI or,

from your boot's fstab if your phone is non-GKI.

Just nuke everything with the keyword avb from your fstab:

ravindu644/Simple-Android-Guides@70a9021

[soncao0212-commits]

I see on the internet there are many system.img versions based on the original version of my device and they have removed some applications but they are not to my liking. That version can be flashed successfully to any device without having to edit the avb file, right? Is the avb you mentioned that needs to be edited in the system.img or is it a separate partition? Moreover, I see that their uuid is the same as the original uuid. Is this a bootloop problem? It's really confusing, please help me. I want my system.img after flashing to be able to flash to any other device of the same model without having to do anything else like others are doing.

[ravindu644]

I see on the internet there are many system.img versions based on the original version of my device and they have removed some applications but they are not to my liking. That version can be flashed successfully to any device without having to edit the avb file, right? Is the avb you mentioned that needs to be edited in the system.img or is it a separate partition? Moreover, I see that their uuid is the same as the original uuid. Is this a bootloop problem? It's really confusing, please help me. I want my system.img after flashing to be able to flash to any other device of the same model without having to do anything else like others are doing.

Maybe the system.img you are referring is signed with googles/samsung's test keys by whoever it made it.

UUID only matters if your OEM uses UUIDs to mount the system image.

Also,

you can't use erofs filesystem if your kernel does not have erofs support.

If your kernel is below version 5.4, erofs support maybe limited.

Try go with ext4 first.

edit: I saw your input image is EROFS as well. That means there's something to do with AVB

[soncao0212-commits]

i solved it successfully, we need more config files. can start on all similar devices without disabling vbmeta, thank you very much for taking care of my problem

[ravindu644]

i solved it successfully, we need more config files. can start on all similar devices without disabling vbmeta, thank you very much for taking care of my problem

How did you solve it 👀

[aliakbar6821]

I am getting same issues
I am using moto g54 5g
Android 15
Kernel GKI 5.10-12

Wen i disable vbmeta using fastboot cmd it doesn't turn on so i have to use original vbmeta

How do i disable avb

Also boot.img there is nothing about fstab because its gki also vendor_boot.img its orangefox recovery

My device can boot magisk rooted image and ofox recovery without disabling avb but i want to disable so that i can boot custom image like gsi or debloted system

What should I do

[tedchirvasiu]

I am getting same issues I am using moto g54 5g Android 15 Kernel GKI 5.10-12

Wen i disable vbmeta using fastboot cmd it doesn't turn on so i have to use original vbmeta

How do i disable avb

Also boot.img there is nothing about fstab because its gki also vendor_boot.img its orangefox recovery

My device can boot magisk rooted image and ofox recovery without disabling avb but i want to disable so that i can boot custom image like gsi or debloted system

What should I do

Are you trying to boot the original OS but just disable AVB and it fails to boot after you flashed vbmeta with AVB disabled?

Can you show the command you run to disable AVB? Are you running both --disable-verity --disable-verification flags when you flash vbmeta?

Does your system have multiple vbmeta partitions? Such as vbmeta_vendor, vbmeta_system. If so, you would need to flash them with --disable-verity --disable-verification as well.

Does your system have A/B partitions? If so, you might have to try flashing on both a and b slots, like

fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_b vbmeta.img

And then the same for other vbmeta partitions (vbmeta_vendor, vbmeta_system etc.)

Take a look how this recovery script does it for CMF Phone 1 (they only flash vbmeta on _a partitions though):
https://github.com/spike0en/nothing_flasher/blob/e5469529a6789c68a3a051f082aeb29dc038ca8c/Windows/flash_all.bat#L156-L188

[ravindu644]

I am getting same issues I am using moto g54 5g Android 15 Kernel GKI 5.10-12

Wen i disable vbmeta using fastboot cmd it doesn't turn on so i have to use original vbmeta

How do i disable avb

Also boot.img there is nothing about fstab because its gki also vendor_boot.img its orangefox recovery

My device can boot magisk rooted image and ofox recovery without disabling avb but i want to disable so that i can boot custom image like gsi or debloted system

What should I do

The only thing you need to do is disable the AVB checks in the fstab file that your kernel reads first. For non-GKI devices, this file is inside the boot.img ramdisk, and for GKI devices, it’s inside the vendor_boot ramdisk.

There are absolutely no issues with modifying the vendor_boot image, even if your device does not use a separate recovery partition.

Just find all the fstab files and remove the AVB checking flags for your modified partition.

Using this method, you don’t even need to flash a patched vbmeta. I’m using a fully “cooked” super image with the stock vbmeta and disabled AVB through the vendor_boot editing method 🙂

https://ravindu644.medium.com/how-i-edited-the-android-vendor-boot-img-to-remove-avb-and-add-ext4-support-ae16ef98ef46