Hovatek Forum MOBILE Android [Please help] Vortex HD65 Ultra - MT6739 - Global - DM Verity Corruption Fix Failure
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


[Please help] Vortex HD65 Ultra - MT6739 - Global - DM Verity Corruption Fix Failure

[Please help] Vortex HD65 Ultra - MT6739 - Global - DM Verity Corruption Fix Failure

Justadudeinspace
Justadudeinspace
Justadudeinspace
Enthusiastic Member
9
14-06-2024, 11:58 PM
#1



I recently acquired a Vortex HD65 Ultra - MT6739 - Global variant. It's nothing special, kinda laggy with only 3GB of Ram, but I was able to Root the device in 15 mins of taking it out of the box. However, I can't for the life of me seem to fix the DM Verity Corruption. I've tried all the normal methods.

I have tried to fix DM Verity Corruption by using the following methods.


First I followed the path:

Code:

adb reboot bootloader



Code:

fastboot devices



Code:

fastboot oem cmds


Failed!

So I tried the next step in flashing the vbmeta.img partition file with both the pulled copy from the dump file as well as a blank version following the path:


Code:

adb reboot bootloader



Code:

fastboot devices



Code:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification


Failed!

Next I tried to use the adb shell command through the computer by following the path:


Code:

adb reboot "dm-verity enforcing"


Failed!

I tried to use the same command through a Rooted Termux terminal:


Code:

su



Code:

reboot "dm-verity enforcing"


Failed!

So next, I tried to use these fastboot codes:


Code:

fastboot devices



Code:

fastboot oem disable_dm_verity
fastboot oem enable_dm_verity


Failed!


Each method has either completely failed, or bricked/bootlooped the device. None of the usual methods seem to work, and I find it surprising for such a cheap phone that I rooted within the first 15 mins of taking it out of the box.

I definitely need an assist on this problem. If anyone has any ideas, I'm completely open to listening. I'm not the only one trying to solve this problem with this device. For some reason this device has gathered a following on XDA forums, but no one has been able to solve the DM Verity Corruption.

Thanks in advance..
maxpayne
maxpayne
maxpayne
Intern
3,602
17-06-2024, 08:49 AM
#2
(14-06-2024, 11:58 PM)Justadudeinspace Thanks in advance..

If you have already rooted, then I assume verified boot isn't a problem. Unless I'm missing something.
Unless you're referring to the message that appears on boot which would be Yellow State.
https://www.hovatek.com/forum/thread-31664.html .
Another option is to try signing images using avbtool assuming this model uses the generic private key to sign partitions or vbmeta at least

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Justadudeinspace
Justadudeinspace
Justadudeinspace
Enthusiastic Member
9
30-06-2024, 05:53 PM
#3
[quote pid="243087" dateline="1718610557"]
Unless you're referring to the message that appears on boot which would be Yellow State.
https://www.hovatek.com/forum/thread-31664.html .
Another option is to try signing images using avbtool assuming this model uses the generic private key to sign partitions or vbmeta at least
[/quote]

So it's in Orange State and still requires pressing power upon boot to boot to system due to corruption. But yes, it was very simple and straightforward to root.

It's a cheap device as it has 3GB of Ram. However, it ironically is Android 13. Adding any Magisk Modules causes extreme lag, but I've yet to try and install a GSI.

Strangely, the boot.img is only 1kb.

It's a confusing device for certain.
Justadudeinspace
Justadudeinspace
Justadudeinspace
Enthusiastic Member
9
30-06-2024, 05:57 PM
#4
(17-06-2024, 08:49 AM)maxpayne
(14-06-2024, 11:58 PM)Justadudeinspace Thanks in advance..

If you have already rooted, then I assume verified boot isn't a problem. Unless I'm missing something.
Unless you're referring to the message that appears on boot which would be Yellow State.
https://www.hovatek.com/forum/thread-31664.html .
Another option is to try signing images using avbtool assuming this model uses the generic private key to sign partitions or vbmeta at least
I'll try the hex editor route.
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl