Hovatek Forum MOBILE Android Problems with Research Download Tool
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Problems with Research Download Tool

Problems with Research Download Tool

Watuwant?
Watuwant?
Watuwant?
Enthusiastic Member
5
11-09-2022, 03:59 AM
#1



Hello users, I'm currently having some problems in doing an root for an unisoc (spreadtrum) device.

I already unlocked the bootloader (following this guide: https://www.hovatek.com/forum/thread-32287.html), already created the vbmeta-signed-custom.img (following this guide: https://www.hovatek.com/forum/thread-32664.html) with an custom recovery key, since I intended to flash recovery for root. Also created an recovery-signed.img and patched it in Magisk (version is 25.2). Already flashed the vbmeta-signed-custom.img and recovery-patched-magisk.img both in fastboot.

The problem occurs when I'm trying to "reboot" from fastboot to recovery with the Research Download Tool method to get access to root. My Research Download Tool stays blank, without showing the "waiting for device" - thought it was the drivers, reinstalled it and nothing. Also tested in another PC with same drivers, same Research Download Tool and nothing.

My questions are:
Does RDT or even the android got something preventing this from working?
Do I need to flash my stock vbmeta, then my stock recovery.img to revert those changes (in fastboot)?
Can I try to do the same process, just using the boot.img and get root from it?
Do I need to have TWRP (for rooting with the boot.img) or it's not necessary?


My firmware: https://mega.nz/file/XyJn1ZBQ#7_Rob9DtHD...E-hqgvqNfI
My recovery-signed-patched (by magisk): https://mega.nz/file/zyJGAIZQ#-hNdyPPKXQ...zSWzOmicIU
My vbmeta-signed.img is in the attachments

PHONE SPECS:
Model: Multilaser G
CPU: SC9832A
RAM: 1GB
ROM: 32GB
Android: 9.0 (Android Pie)
Attached Files
.img
vbmeta-sign-custom.img
Size: 1 MB / Downloads: 14
Gargoyle
Gargoyle
Gargoyle
Contributor
505
11-09-2022, 11:07 AM
#2
I think you went about it the wrong way.

Do not patch with magisk recovery.img but boot.img, then create vbmeta-sign-custom.img again.

You must sign the patched boot.img.

Also try Magisk v23.0 or v24.3 first, version 25 and above didn't work for me on Unisoc devices.


Edit:
Fixed files here
https://mega.nz/file/OR9FjJ4B#595VUjhIZN...epv7NLZzFA

if you flashed a patched recovery, replace the stock recovery.
flash the files via fastboot
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta-sign.img
This post was last modified: 11-09-2022, 11:43 AM by Gargoyle.
Watuwant?
Watuwant?
Watuwant?
Enthusiastic Member
5
12-09-2022, 12:52 AM
#3
(11-09-2022, 11:07 AM)Gargoyle I think you went about it the wrong way.

Do not patch with magisk recovery.img but boot.img, then create vbmeta-sign-custom.img again.

You must sign the patched boot.img.

Also try Magisk v23.0 or v24.3 first, version 25 and above didn't work for me on Unisoc devices.


Edit:
Fixed files here
https://mega.nz/file/OR9FjJ4B#595VUjhIZN...epv7NLZzFA

if you flashed a patched recovery, replace the stock recovery.
flash the files via fastboot
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta-sign.img

Thanks for the tips and the help! I did what you said, replaced my vbmeta-sign and recovery for the stock ones, got the vbmeta-sign.img and boot.img, flashed both in fastboot and rebooted the phone via fastboot, but now it's stuck in boot (not the boot animation, I think its stuck in the boot logo or something - image in the attachments) and it doesn't go further than that.

What can I do to possibly fix this issue?
Attached Files
.jpg
Stuck here in this part.jpg
Size: 649.54 KB / Downloads: 5
Gargoyle
Gargoyle
Gargoyle
Contributor
505
13-09-2022, 12:50 AM
#4
Does the stock firmware boot without problems?
This post was last modified: 13-09-2022, 12:54 AM by Gargoyle.
Watuwant?
Watuwant?
Watuwant?
Enthusiastic Member
5
13-09-2022, 03:46 AM
#5



(13-09-2022, 12:50 AM)Gargoyle Does the stock firmware boot without problems?

Yes it does, I flashed the stock vbmeta.img and boot.img to revert the changes.

Edit: I actually got it working now. I discovered that my device, for some reason didn't allow to flash more than 2 files in a row and use the fastboot reboot command after it, so I just flashed the vbmeta-sing-custom.img, did an fastboot reboot, flashed my boot-patched-signed.img and did an fastboot reboot again.

I also checked the root with Root Checker (that I gave permissions through Magisk Manager, which also changed quite a lot from the last time I used it).
Again, thank you so much for your time and help, and I also thank this forum for the help.
Attached Files
.png
Root Checker proof.png
Size: 45.94 KB / Downloads: 5
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl