Hovatek Forum DEVELOPMENT Android [Development] Unisoc / Spreadtrum (SPD) auto TWRP recovery porter by Team Hovatek
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


[Development] Unisoc / Spreadtrum (SPD) auto TWRP recovery porter by Team Hovatek

[Development] Unisoc / Spreadtrum (SPD) auto TWRP recovery porter by Team Hovatek

Pages (23): Previous 118 19 20 21 22 23 Next
Pupstime _
Pupstime _
Pupstime _
Enthusiastic Member
14
08-06-2021, 08:28 AM



(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

After I port the twrp file from the stock recovery, the twrp file is 16.1 mb while the stock recovery is 35 mb, after I sign the twrp file, it become 35 mb , isn't the twrp file supposed to stay the same size? 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.
X3non
X3non
X3non
Recognized Contributor
22,062
08-06-2021, 10:25 AM
(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?
Pupstime _
Pupstime _
Pupstime _
Enthusiastic Member
14
08-06-2021, 11:04 AM
(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?
I 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.
This post was last modified: 08-06-2021, 11:07 AM by Pupstime _.
Pupstime _
Pupstime _
Pupstime _
Enthusiastic Member
14
08-06-2021, 11:50 AM
(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?

I have deleted the file recovery-from-boot.p using root explorer. I boot to recovery using "adb reboot recovery" It still goes to stock recovery instead of twrp. And if I use the custom signed vbmeta, using "adb reboot recovery", I cannot access even the stock recovery. It is stucked at boot. I also notice that when in normal booting. My phone will show two line of sentence. The first line sentence is "INFO: LOCK FLAG IS : UNLOCK !!" and the second line sentence is "WARNING : LOCK FLAG IS : UNLOCK! SKIP VERIFY !!!". Using the custom signed vbmeta, when I try to reboot to recovery using adb, only the first sentence appear.
This post was last modified: 08-06-2021, 12:11 PM by Pupstime _.
Pupstime _
Pupstime _
Pupstime _
Enthusiastic Member
14
09-06-2021, 05:09 AM



(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?

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.
X3non
X3non
X3non
Recognized Contributor
22,062
09-06-2021, 10:43 AM
(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"
Pupstime _
Pupstime _
Pupstime _
Enthusiastic Member
14
10-06-2021, 04:10 AM
(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"

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 ?
X3non
X3non
X3non
Recognized Contributor
22,062
10-06-2021, 12:55 PM
(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
Pupstime _
Pupstime _
Pupstime _
Enthusiastic Member
14
10-06-2021, 01:16 PM
(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

Okay, that means I use the correct partition size. Anw, I've done what you told on this thread https://www.hovatek.com/forum/thread-392...14871.html , please check it out
pindonga123
pindonga123
pindonga123
Enthusiastic Member
12
17-06-2021, 12:03 AM



Hello everyone, hopefully someone help me. I have a rear view mirror with Android Oreo and an SPD 9832E. I unlocked the bootloader thanks to a tutorial that I saw here that used a script and the token, but from then on I can't do anything. When I want to flash a recovery twrp the command is sent but it hangs there, nothing happens, it does not write the new recovery. I also tried to do what this tutorial says but when I flash with research download it does not finish the process. It does not throw any error, it only stays there for minutes and after a while it says busy port or something like that. Do these unisoc have any verification system of the images which does not allow me to record them in the O.S?
Pages (23): Previous 118 19 20 21 22 23 Next
Users browsing this thread:
 5 Guest(s)
Users browsing this thread:
 5 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram