[Cereal_Mkos]

I have a Moto G20 it comes with Unisoc T700 and it already has an unlocked bootloader using fastboot flashing unlock command but I have a problem with root and with TWRP that I compiled ... they give the same problem the device turns on at most 1 or 2 seconds in the bootlogo and it is in a loop and flashing boot.img stock everything goes back to normal
Moto G20 (Java)
Android 11
ARM64
A/B
dynamic partitions

[X3non]

I have a Moto G20 it comes with Unisoc T700 and it already has an unlocked bootloader using fastboot flashing unlock command but I have a problem with root and with TWRP that I compiled ... they give the same problem the device turns on at most 1 or 2 seconds in the bootlogo and it is in a loop and flashing boot.img stock everything goes back to normal
Moto G20 (Java)
Android 11
ARM64
A/B
dynamic partitions

did you disable dm_verity? flashing empty or custom vbmeta as the case maybe? see https://www.hovatek.com/forum/thread-32719.html

[Cereal_Mkos]

empty vbmeta it doesn't flash it's writing and it crashes... I saw about custom vbmeta here but I found it only for Android 8 9 and 10 not for Android 11... and I didn't even find an effective way to use dm_verity..

[Cereal_Mkos]

I have a Moto G20 it comes with Unisoc T700 and it already has an unlocked bootloader using fastboot flashing unlock command but I have a problem with root and with TWRP that I compiled ... they give the same problem the device turns on at most 1 or 2 seconds in the bootlogo and it is in a loop and flashing boot.img stock everything goes back to normal
Moto G20 (Java)
Android 11
ARM64
A/B
dynamic partitions

did you disable dm_verity? flashing empty or custom vbmeta as the case maybe? see https://www.hovatek.com/forum/thread-32719.html

empty vbmeta it doesn't flash it's writing and it crashes... I saw about custom vbmeta here but I found it only for Android 8 9 and 10 not for Android 11... and I didn't even find an effective way to use dm_verity..

[X3non]

empty vbmeta it doesn't flash it's writing and it crashes... I saw about custom vbmeta here but I found it only for Android 8 9 and 10 not for Android 11... and I didn't even find an effective way to use dm_verity..

should be the same process with difference in vbmeta_pad, read_info from your vbmeta
in general go through the custom vbmeta guide and find out what differs in android 11 vbmeta

[Cereal_Mkos]

empty vbmeta it doesn't flash it's writing and it crashes... I saw about custom vbmeta here but I found it only for Android 8 9 and 10 not for Android 11... and I didn't even find an effective way to use dm_verity..

should be the same process with difference in vbmeta_pad, read_info from your vbmeta
in general go through the custom vbmeta guide and find out what differs in android 11 vbmeta

I used vbmeta_pad_10 .. I corrected the differences in the partitions and I managed to do my problem is that it doesn't flash the vbmeta-sign.img stock flash in seconds and the vbmeta-sign-customized it writing and it never ends, it gets stuck... and also uses the same RSA4096 ... and also uses the same Release String: 'avbtool 1.1.0' .... and even with the drivers the SPD TOOL doesn't recognize my phone... and as a consequence I can't install there too

[hovatek]

I used vbmeta_pad_10 .. I corrected the differences in the partitions and I managed to do my problem is that it doesn't flash the vbmeta-sign.img stock flash in seconds and the vbmeta-sign-customized it writing and it never ends, it gets stuck... and also uses the same RSA4096 ... and also uses the same Release String: 'avbtool 1.1.0' .... and even with the drivers the SPD TOOL doesn't recognize my phone... and as a consequence I can't install there too

My guess is that Motorola would not use the default keys to sign their partitions

[Cereal_Mkos]

I used vbmeta_pad_10 .. I corrected the differences in the partitions and I managed to do my problem is that it doesn't flash the vbmeta-sign.img stock flash in seconds and the vbmeta-sign-customized it writing and it never ends, it gets stuck... and also uses the same RSA4096 ... and also uses the same Release String: 'avbtool 1.1.0' .... and even with the drivers the SPD TOOL doesn't recognize my phone... and as a consequence I can't install there too

My guess is that Motorola would not use the default keys to sign their partitions

and how could I get around it? do you have any idea

[Cereal_Mkos]

I used vbmeta_pad_10 .. I corrected the differences in the partitions and I managed to do my problem is that it doesn't flash the vbmeta-sign.img stock flash in seconds and the vbmeta-sign-customized it writing and it never ends, it gets stuck... and also uses the same RSA4096 ... and also uses the same Release String: 'avbtool 1.1.0' .... and even with the drivers the SPD TOOL doesn't recognize my phone... and as a consequence I can't install there too

My guess is that Motorola would not use the default keys to sign their partitions

I did a test just unzipped and compressed the boot.img it already entered in loop as root and twrp this information helps in anything?

[X3non]

and how could I get around it? do you have any idea

the only workaround is to get the same private key used by the OEM and replace the rsa4096 key we used in our guide
downside is that the key can only be retrieved from the OEM