bv5500 plus root
bv5500 plus root
(11-09-2020, 04:58 PM)Denny83 ...
I'm managing with your tutorials to create my own vbmeta to flash a boot image...some questions:
1 if I unlock bootloader like you show in this post https://www.hovatek.com/forum/thread-32287.html - then i can sign vbmeta with the .pem key used to unlock bootloader?
2 I have a vbmeta image as in attached file vbmeta_info.txt; is it correct to make my vbmeta to run this command: python avbtool.py make_vbmeta_image --key denny2048.pem --algorithm SHA256_RSA2048 --flag 2 --chain_partition recovery:1:keys/recovery.bin --chain_partition vbmeta_sysstem:2:keys/vbmeta_system.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor.bin --chain_partition boot:3:keys/boot.bin --padding_size 12288 --output vbmeta-sign-custom.img
3 my vbmeta is Image Size: 46976 bytes ---how can i obtain vbmeta image with this size?
...
(12-09-2020, 03:42 PM)X3non(11-09-2020, 04:58 PM)Denny83 ...
I'm managing with your tutorials to create my own vbmeta to flash a boot image...some questions:
1 if I unlock bootloader like you show in this post https://www.hovatek.com/forum/thread-32287.html - then i can sign vbmeta with the .pem key used to unlock bootloader?
2 I have a vbmeta image as in attached file vbmeta_info.txt; is it correct to make my vbmeta to run this command: python avbtool.py make_vbmeta_image --key denny2048.pem --algorithm SHA256_RSA2048 --flag 2 --chain_partition recovery:1:keys/recovery.bin --chain_partition vbmeta_sysstem:2:keys/vbmeta_system.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor.bin --chain_partition boot:3:keys/boot.bin --padding_size 12288 --output vbmeta-sign-custom.img
3 my vbmeta is Image Size: 46976 bytes ---how can i obtain vbmeta image with this size?
...
i take it that any attempt to disable dm_verity on this model get the device bricked? did you try unlocking critical partitions too?
1. You already unlocked bootloader of your device, so you don't need that guide. BTW that guide is meant for unisoc devices requiring identifier token to unlock their bootloaders
2. Your make_vbmeta command will be similar to that posted @ https://www.hovatek.com/forum/thread-35862.html ; check the Extra section
you'll need to create a folder named "phone" in the same location as the keys folder and copy your stock dtbo.img into this phone folder before running the make_vbmeta command
3. padding size (argument) will be the size of the original vbmeta in bytes. are you certain yours is really 46976? ensure to right click and check the properties of the file and copy the byte size value
(13-09-2020, 06:10 AM)Tigryss Hi guys, I would like to create twrp recovery and lineageOS 17.1 for this device are the steps similar to this rooting steps? I have 2 devices and the first one is already stucks in black screen downloading mode(waiting for dry out).
(11-09-2020, 04:58 PM)Denny83 I open this post as suggested me in this thread: https://www.hovatek.com/forum/thread-32664.html
my question - as i failed in create my own vbmeta.img was:
I'm managing with your tutorials to create my own vbmeta to flash a boot image...some questions:
1 if I unlock bootloader like you show in this post https://www.hovatek.com/forum/thread-32287.html - then i can sign vbmeta with the .pem key used to unlock bootloader?
2 I have a vbmeta image as in attached file vbmeta_info.txt; is it correct to make my vbmeta to run this command: python avbtool.py make_vbmeta_image --key denny2048.pem --algorithm SHA256_RSA2048 --flag 2 --chain_partition recovery:1:keys/recovery.bin --chain_partition vbmeta_sysstem:2:keys/vbmeta_system.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor.bin --chain_partition boot:3:keys/boot.bin --padding_size 12288 --output vbmeta-sign-custom.img
3 my vbmeta is Image Size: 46976 bytes ---how can i obtain vbmeta image with this size?
thanks for reply
...
(13-04-2021, 10:21 AM)gratefultraveller(11-09-2020, 04:58 PM)Denny83 I open this post as suggested me in this thread: https://www.hovatek.com/forum/thread-32664.html
my question - as i failed in create my own vbmeta.img was:
I'm managing with your tutorials to create my own vbmeta to flash a boot image...some questions:
1 if I unlock bootloader like you show in this post https://www.hovatek.com/forum/thread-32287.html - then i can sign vbmeta with the .pem key used to unlock bootloader?
2 I have a vbmeta image as in attached file vbmeta_info.txt; is it correct to make my vbmeta to run this command: python avbtool.py make_vbmeta_image --key denny2048.pem --algorithm SHA256_RSA2048 --flag 2 --chain_partition recovery:1:keys/recovery.bin --chain_partition vbmeta_sysstem:2:keys/vbmeta_system.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor.bin --chain_partition boot:3:keys/boot.bin --padding_size 12288 --output vbmeta-sign-custom.img
3 my vbmeta is Image Size: 46976 bytes ---how can i obtain vbmeta image with this size?
thanks for reply
...
Hi Denny,
may I ask you where you found the Bv5500 plus stock (recovery) ROM and which version it is? I have been dl'ing a lot of different rar-compressed files, but they were all corrupt or empty I have the BV5500 Plus as well, Build number BV5500Plus_EEA_E353_V1.0_20201021V13, which I would like to root. I am working to get the scatter file at the moment, sofar without success.
I would really appreciate your reply.
Regards, gratefultraveller
(13-04-2021, 10:21 AM)gratefultraveller ... I have the BV5500 Plus as well, Build number BV5500Plus_EEA_E353_V1.0_20201021V13, which I would like to root. I am working to get the scatter file at the moment, sofar without success.