[Tutorial] How to disable dm-verity or Android Verified Boot (AVB)
[Tutorial] How to disable dm-verity or Android Verified Boot (AVB)
16-04-2021, 09:34 AM
(15-04-2021, 01:12 PM)Vallyboyx Hello I'm getting
Fastboot: error: cannot load 'vbmeta. Img' : No such file or directory
And I have placed the vbmeta in adb folder. What should I do?
create a new thread for your device issue by clicking "ask question" at the top
in the new thread, attach a screenshot showing the command you sent and the error, also attach a screenshot showing where (what folder) vbmeta is placed
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
17-04-2021, 10:55 AM
(16-04-2021, 03:31 PM)chin2s I have oneplus 8 android 11. I flash empty_vbmeta.img but after reboot bootloop? any solution for disable dm-verity
create a new thread for your device issue by clicking "ask question" at the top
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
13-05-2021, 06:42 AM
(12-05-2021, 12:51 PM)hd_scania But my stock boot.img doesn’t have the hex string ‘‘2C 76 65 72 69 66 79’’ or the keyword ‘‘verify’’ at all
My device is Samsung SM-A125F, which is still being boot looped for flashing my own TWRP
It is very naive of you to hope that you'll find ‘‘76 65 72 69 66 79’’. Probably, 5-6 years ago it was a working method. Nowadays, as I understand, verity mechanism is implemented on a much more deeper level in the code of boot/recovery.
This post was last modified: 13-05-2021, 06:43 AM by vpolinov.
13-05-2021, 08:39 AM
With the kernel image no longer having dm-verity keywords, what are the final steps to solve the boot loops for entering my TWRP which has been built and working when boot loops have been solved?
(13-05-2021, 06:42 AM)vpolinov(12-05-2021, 12:51 PM)hd_scania But my stock boot.img doesn’t have the hex string ‘‘2C 76 65 72 69 66 79’’ or the keyword ‘‘verify’’ at allIt is very naive of you to hope that you'll find ‘‘76 65 72 69 66 79’’. Probably, 5-6 years ago it was a working method. Nowadays, as I understand, verity mechanism is implemented on a much more deeper level in the code of boot/recovery.
My device is Samsung SM-A125F, which is still being boot looped for flashing my own TWRP
14-05-2021, 02:01 PM
(12-05-2021, 12:51 PM)hd_scania But my stock boot.img doesn’t have the hex string ‘‘2C 76 65 72 69 66 79’’ or the keyword ‘‘verify’’ at all
My device is Samsung SM-A125F, which is still being boot looped for flashing my own TWRP
already replied to @ https://www.hovatek.com/forum/thread-39047.html
This post was last modified: 14-05-2021, 02:02 PM by X3non.
Learn MediaTek, Unisoc / Spreadtrum (SPD) and Qualcomm Software Repairs @ https://www.hovatek.com/training
Note!
We have a reply schedule for Forum Support. Please try Private Support if you can't wait.
Users browsing this thread:
1 Guest(s)
1 Guest(s)
Users browsing this thread:
1 Guest(s)
1 Guest(s)
