We're hiring! Apply Now

Hovatek Forum DEVELOPMENT Android Unisoc mobile root problem

Unisoc mobile root problem

Unisoc mobile root problem

ridoy27253
ridoy27253
ridoy27253
Newbie
4
07-07-2024, 03:22 PM
#1



How to root unisoc processor,
I already unlock bootloader.
Model: Walton Primo R6 max
justshez
justshez
justshez
Intern
2,428
08-07-2024, 05:42 PM
#2
(07-07-2024, 03:22 PM)ridoy27253 How to root unisoc processor,
I already unlock bootloader.
Model: Walton Primo R6 max

Refer to https://www.hovatek.com/forum/thread-32678.html

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
ridoy27253
ridoy27253
ridoy27253
Newbie
4
26-07-2024, 08:27 PM
#3
(08-07-2024, 05:42 PM)justshez
(07-07-2024, 03:22 PM)ridoy27253 How to root unisoc processor,
I already unlock bootloader.
Model: Walton Primo R6 max

On last step on flash recover_patched.img with custom encode it shows writting recovery.... Then i wait 20minute but nothing happen. I used hovatek modified fastboot. On magisk i use V27 and on recovery then patched. I am using kali linux 2023.04. 
What should i do now, please help and thanks for previous response.
This post was last modified: 27-07-2024, 11:11 AM by hovatek.
ridoy27253
ridoy27253
ridoy27253
Newbie
4
27-07-2024, 04:52 AM
#4
used command: 

└─$ python avbtool.py info_image --image recovery_stock.img

Footer version:          1.0
Image size:              41943040 bytes
Original image size:      25290752 bytes
VBMeta offset:            25292800
VBMeta size:              2112 bytes
--
Minimum libavb version:  1.0
Header Block:            256 bytes
Authentication Block:    576 bytes
Auxiliary Block:          1280 bytes
Public key (sha1):        d9093b9a181bdb5731b44d60a9f850dc724e2874
Algorithm:                SHA256_RSA4096
Rollback Index:          0
Flags:                    0
Rollback Index Location:  0
Release String:          'avbtool 1.1.0'
Descriptors:
    Hash descriptor:
      Image Size:            25290752 bytes
      Hash Algorithm:        sha256
      Partition Name:        recovery
      Salt:                  3e09e8f2c9782d35b7b088a050c144892883fab971ec3dde3a0251bc9d257146
      Digest:                a3198d7f0092bbe2e5fcbeafb558c8c0ef9ece111e49f5ee85762ff50c0fdfad
      Flags:                0

└─$ python avbtool.py add_hash_footer --image recovery_magisk.img --partition_name recovery --partition_size 41943040 --key rsa4096_vbmeta.pem --algorithm SHA256_RSA4096

Using Platform Tools Fastboot└─# ./fastboot flash recovery recovery_magisk.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 41943040).
Sending 'recovery' (40960 KB)                      OKAY [  3.912s]
Writing 'recovery'  


Using Modified Fastboot by hovatek  └─# ./fastboot --slot all  flash recovery magisk_patched_recovery_signed.img
target didn't report max-download-size
sending 'recovery' (40960 KB)...
OKAY [  3.100s]
writing 'recovery'... 


On magisk patch i tried with recovery op[tion and without recovery option. But result was same.
I also try using SPD Research Tool R27.24.1301. But after 126Sec it shows wait time out, I tried most viewd videos on Youtube. Now tricks Working.
           


(08-07-2024, 05:42 PM)justshez
(07-07-2024, 03:22 PM)ridoy27253 How to root unisoc processor,
I already unlock bootloader.
Model: Walton Primo R6 max

Refer to https://www.hovatek.com/forum/thread-32678.html
This post was last modified: 27-07-2024, 04:55 AM by ridoy27253.
maxpayne
maxpayne
maxpayne
Intern
4,101
27-07-2024, 11:19 AM
#5



(27-07-2024, 04:52 AM)ridoy27253 ..

If you're trying to root, you should be focusing on the boot partition not recovery partition.
Anyway...
It points at signing incorrectly.
The mistake you made is that you assumed that they originally singed the recovery partition using rsa4096_vbmeta.pem which is clearly not the case.
You first need to create a custom vbmeta where you would've swapped the recovery partition with your own public key. In the end, you would be flashing the custom vbmeta and recovery.

Refer to https://www.hovatek.com/forum/thread-32664.html

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
ridoy27253
ridoy27253
ridoy27253
Newbie
4
27-07-2024, 04:05 PM
#6
(27-07-2024, 11:19 AM)maxpayne
(27-07-2024, 04:52 AM)ridoy27253 ..

If you're trying to root, you should be focusing on the boot partition not recovery partition.
Anyway...
It points at signing incorrectly.
The mistake you made is that you assumed that they originally singed the recovery partition using rsa4096_vbmeta.pem which is clearly not the case.
You first need to create a custom vbmeta where you would've swapped the recovery partition with your own public key. In the end, you would be flashing the custom vbmeta and recovery.

Refer to https://www.hovatek.com/forum/thread-32664.html





Thanks a lot
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
Join us
WhTlYt