[Development] Unisoc / Spreadtrum (SPD) auto TWRP recovery porter by Team Hovatek
[Development] Unisoc / Spreadtrum (SPD) auto TWRP recovery porter by Team Hovatek
(07-06-2021, 03:11 PM)X3non(07-06-2021, 05:56 AM)Pupstime _ Hi, so I try to port twrp for android 8.1.0 go edition. My phone has spreadtrum chipset. I use this tutorial here https://www.hovatek.com/forum/thread-32678.html to unlock bootloader and flash custom signed vbmeta. The problem is, after i port the twrp, I need to sign the twrp.img using the .pem isn't it? And to sign it, I need to use this command "python avbtool info_image --image twrp.img" to find out the partition size and algorithm before I use this command "python avbtool add_hash_footer --image twrp.img --partition_name recovery --partition_size ? --key hovatek.pem --algorithm ?". When I use this command "python avbtool info_image --image twrp.img" , it return this "avbtool: Given image does not look like a vbmeta image." I use hxd hex editor to find DHTB sign , it doesn't exist in the ported twrp.img. Is there any solution for that?
you're to use the info_image command on your stock recovery not on twrp, this will give you the needed info ; refer to https://www.hovatek.com/forum/thread-32674.html
(08-06-2021, 08:28 AM)Pupstime _ ... isn't the twrp file supposed to stay the same size?
(08-06-2021, 08:28 AM)Pupstime _ Any way, I flash the custom signed vbmeta and twrp file. Using the custom signed vbmeta image, my phone show this error no google key (red color) at left top of my phone screen. My phone also cannot detect sim card. It also cannot go to recovery mode. So I flash the stock vbmeta and my phone goes back to normal. However, when I go to recovery mode, it shows the stock recovery instead of twrp. I have flashed the twrp.img.
(08-06-2021, 10:25 AM)X3nonI don't understand what you mean. I just flash twrp.img using fastboot. I don't know how to delete or rename file from within /system parititon. Also for extra information, the stock recovery image has this no command error with android robot resting on its back. But if I push power + volume up. I can go to the stock recovery.(08-06-2021, 08:28 AM)Pupstime _ ... isn't the twrp file supposed to stay the same size?
No, it's not
(08-06-2021, 08:28 AM)Pupstime _ Any way, I flash the custom signed vbmeta and twrp file. Using the custom signed vbmeta image, my phone show this error no google key (red color) at left top of my phone screen. My phone also cannot detect sim card. It also cannot go to recovery mode. So I flash the stock vbmeta and my phone goes back to normal. However, when I go to recovery mode, it shows the stock recovery instead of twrp. I have flashed the twrp.img.
did you delete or rename the file recovery-from-boot.p from within /system partition?
(08-06-2021, 10:25 AM)X3non(08-06-2021, 08:28 AM)Pupstime _ ... isn't the twrp file supposed to stay the same size?
No, it's not
(08-06-2021, 08:28 AM)Pupstime _ Any way, I flash the custom signed vbmeta and twrp file. Using the custom signed vbmeta image, my phone show this error no google key (red color) at left top of my phone screen. My phone also cannot detect sim card. It also cannot go to recovery mode. So I flash the stock vbmeta and my phone goes back to normal. However, when I go to recovery mode, it shows the stock recovery instead of twrp. I have flashed the twrp.img.
did you delete or rename the file recovery-from-boot.p from within /system partition?
(08-06-2021, 10:25 AM)X3non(08-06-2021, 08:28 AM)Pupstime _ ... isn't the twrp file supposed to stay the same size?
No, it's not
(08-06-2021, 08:28 AM)Pupstime _ Any way, I flash the custom signed vbmeta and twrp file. Using the custom signed vbmeta image, my phone show this error no google key (red color) at left top of my phone screen. My phone also cannot detect sim card. It also cannot go to recovery mode. So I flash the stock vbmeta and my phone goes back to normal. However, when I go to recovery mode, it shows the stock recovery instead of twrp. I have flashed the twrp.img.
did you delete or rename the file recovery-from-boot.p from within /system partition?
(09-06-2021, 05:09 AM)Pupstime _ ...
Hi, I'm now able to boot to twrp.img but it is not working. Here is the image https://ibb.co/c6tN3KN , I'm quite sure the problem is with twrp.img , If I flash the stock recovery, It can boot into the stock recovery.
(09-06-2021, 10:43 AM)X3non(09-06-2021, 05:09 AM)Pupstime _ ...
Hi, I'm now able to boot to twrp.img but it is not working. Here is the image https://ibb.co/c6tN3KN , I'm quite sure the problem is with twrp.img , If I flash the stock recovery, It can boot into the stock recovery.
create a new thread for this issue by clicking "ask question" at the top
in the new thread be sure to explain better what you mean by "able to boot to twrp.img but it is not working"
(10-06-2021, 04:10 AM)Pupstime _ Hi, I wanted to clarify something. So to sign my twrp.img , I use this command "python avbtool.py add_hash_footer --image twrp.img --partition_name recovery --partition_size 36700160 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096"
While twrp.img size is 16900096 , the --parition_size 36700160 is my stock recovery partition size. To sign the twrp.img , which --partition_size should I use? --parition_size 36700160 or --parition_size 16900096 ?
(10-06-2021, 12:55 PM)X3non(10-06-2021, 04:10 AM)Pupstime _ Hi, I wanted to clarify something. So to sign my twrp.img , I use this command "python avbtool.py add_hash_footer --image twrp.img --partition_name recovery --partition_size 36700160 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096"
While twrp.img size is 16900096 , the --parition_size 36700160 is my stock recovery partition size. To sign the twrp.img , which --partition_size should I use? --parition_size 36700160 or --parition_size 16900096 ?
you're to use partition size 36700160