stuck in instructions about dm verity corrupted

[lumyx012]

hi can any one help me with this one i use infinix hot 11s and it prompted a software update yesterday so i just schedule it for it at 2am i woke up, and the phone is dead, i turned it on and it has a message "dm verity corrupted" it just always says that and its just stuck there, i can boot the recovery mode, i tried factory resetting the phone, but once it restarted its still stuck there i tried doing fix on the youtube, i installed mediatek usb drivers, and sp flash. i installed mediatek auth bypass, i connected my device and for some reason, it always results to "force preloader to boot rom" and it gets stuck on "waiting for mtk brom usb device" even though it is connected. so i just leave it like that. i opened sp flash and put the scatter file, clicked download, plugged my device again, and theres an error which i also doesn't understand. i tried downloading infinix flash tool, it doesn't also worked. almost all videos that i watched and fixed that i saw always didn't work.. so im kinda resorting to adb sideload, but i need a firmware.zip for it and im not sure if the firmware.zip used for sp flash (the one with scatter file) is also the file for abd sideload flashing. can someone tell me if it will work or if not can someone give me a link to a stock firmware for it?, if it doesn't work that way, please help me on sp flashing, i really dont understand what im doing wrong. this is the first time i encountered this problem so im kinda new to it. thanks

 

[lumyx012]

also im trying to find the update.zip for infinix hot 11s nfc so i can just apply update from sd card, but sadly, infinix doesn't provide that, and most stock firmwares i see online is for sp flashing.

 

[lumyx012]

it will stay off if preloader connected with SP Flash Tool. maybe you didn't installed VCOM preloader drivers.

it would stay off if i press download on sp flash tool, but it always results to an error. and after a while, it would turn on again.

 

[alecxs]

wrong order, first start download, then connect phone

 

[lumyx012]

wrong order, first start download, then connect phone

i did both ways, and they always give the same error. tbh i lost hope on flashing it using sp flash. i just hope i can find an update.zip so i can just do it on recovery mode, but til now i cant see anything related to it

 

[lumyx012]

i saw a guide on how to flash using fastboot, which i can access, but it is quite confusing to me.

How To Flash Stock ROM Using Fastboot Mode (Best Guide)

Check out this tutorial guide and learn how to flash Stock ROM using Fastboot mode or Fastboot commands on Android device with ease.

www.androiddata-recovery.com

in the 2nd way, it doesn't need usb debugging so i can probably do it. the confusing part to me is it showed an image of xml file opened, but its not like the xml file i have on the firmware, but if i understand it correctly
in this case i need to put the code "fastboot flash preloader preloader_x6812_h6912.bin"
and do it on every single file just like how an sp flash does it, but im doing it manually, i am correct on this one, or am i completely wrong (cuz im stupid)?

 

[jwoegerbauer]

Re-flash Stock ROM using MTK Flash Tool.

Latest version:

MTK Flash Tool v5.1624

Download MTK Flash Tool v5.1624 for Windows which helps you to Flash or Install the Stock Firmware on your Mediatek Feature Phone.

mtktool.com

 

[alecxs]

are you sure you have VCOM preloader drivers installed? can you see it in windows device manager in the moment you plug in usb?

 

[lumyx012]

are you sure you have VCOM preloader drivers installed? can you see it in windows device manager in the moment you plug in usb?

Yes it says, Mediatek Preloader Usb vcom port. But it will disappear if sp flash isn't open.

 

[alecxs]

you can use mtkclient no need to hassle with scatter or xml file. first, read all partitions into directory (backup)

python3 mtk rl out

https://github.com/bkerler/mtkclient#read-flash

 

[lumyx012]

you can use mtkclient no need to hassle with scatter or xml file. first, read all partitions into directory (backup)

python3 mtk rl out

https://github.com/bkerler/mtkclient#read-flash

i followed the instructions and when i run the code python setup.py install, at the end it gives me this message.

 

[lumyx012]

Re-flash Stock ROM using MTK Flash Tool.

Latest version:

MTK Flash Tool v5.1624

Download MTK Flash Tool v5.1624 for Windows which helps you to Flash or Install the Stock Firmware on your Mediatek Feature Phone.

mtktool.com

it says i put a wrong scatter file, the scatter file i put is the same scatter file i put on sp flash, and sp flash accepts it, idk why the MTK flash tool doesn't

 

[alecxs]

i followed the instructions and when i run the code python setup.py install, at the end it gives me this message.

I don't know about windows but I read in instructions
"If you install python from microsoft store, "python setup.py install" will fail, but that step isn't required."

nevertheless I guess you need python 3.9
https://www.python.org/ftp/python/3.9.13/python-3.9.13-amd64.exe
and git
https://github.com/git-for-windows/git/releases/download/v2.39.1.windows.1/Git-2.39.1-64-bit.exe

 

[lumyx012]

I don't know about windows but I read in instructions
"If you install python from microsoft store, "python setup.py install" will fail, but that step isn't required."

nevertheless I guess you need python 3.9
https://www.python.org/ftp/python/3.9.13/python-3.9.13-amd64.exe
and git
https://github.com/git-for-windows/git/releases/download/v2.39.1.windows.1/Git-2.39.1-64-bit.exe

i did go through the instructions and i started the mtk_gui, it required me to connect the phone, but because i dont have the sp flash opened, it turned on, and it says on the cmd, that handshake failed. im pretty sure i downloaded the Mediatek Vcom drivers, it just keeps turning on if i dont press download on sp flash and plugged it

 

[alecxs]

no need for SP Flash Tool for handshake. try again with both volume keys pressed, connect when mtkclient ask

 

[lumyx012]

no need for SP Flash Tool for handshake. try again with both volume keys pressed, connect when mtkclient ask

tried just plugging it in, it will turn on with charging logo, i tried holding it with volume up / volume down / both keys/ and all keys. i also tried single pressing each one of them, it didn't work. did i do something wrong? does my mediatek driver is outdated? (idk i just found a auto installer for it).

 

[alecxs]

double check with "UsbDkController.exe -n" if you see a device with 0x0E8D 0x0003 when connecting.

alternative you can use rufus.ie for installing re_livedvdV4.iso to pendrive, boot from BIOS key F11 or F12

 

[lumyx012]

double check with "UsbDkController.exe -n" if you see a device with 0x0E8D 0x0003 when connecting.

alternative you can use rufus.ie for installing re_livedvdV4.iso to pendrive, boot from BIOS key F11 or F12

how can i double check?, i installed that usbdkcontroller but idk, it just installed and nothing happens

 

[alecxs]

I assume that is command line tool, you should type from cmd.exe like for all command line tools

cd "C:\path\to\dir"
UsbDkController.exe -n

 

[SnoopyFTW]

To get rid of the dm-verify issue flash empty vbmeta via fastboot disabling dm-verity at that occasion:

1. First, use the command below to flash the vbmeta file into both slots:

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

2. If your device already has a vbmeta system file, use the following commands to flash it in both slots:

fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img

3. Similarly, if your firmware includes the vbmeta vendor file, use the following commands to flash it across both slots:

fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img

Oh my god you are a lifesaver!!!!!! FOR REAL DUDE!!!!

I just had the BRILLIANT idea of updating my 9 pro to the latest F75. I have root and magisk and all, also unlocked bootloader ofc.

Well, OnePlus sistem is like retarded. I downloaded OTA package from Oxygen Updater, and it fails when unpacking, happened to me last 3 times, can't tell the reason, just works installing full package.

So I decided to go for the full package, what could go wrong? Let me tell you what went wrong:

Well, I hit the local install option, it says "checking" and "unpacking", seems like it does not work like it used to, you have to install magisk right before restarting but now it never says actually "installing". Well, when it did finish I reinstalled magisk to inactive slot... And when reboot I got the Qualcomm crashdump splash!

Tried flashing original boot.img and so, but no luck, and then I found your post.

Just flashed as you said and BAM, system just started right where I left it, in the previous version, not in the "updated".

Thanks a lot man, makes me so happy to solve this things thanks to google and people like you sharing your knowledge!

I am making a full backup now if anything goes wrong, lesson learnt!

 

[SnoopyFTW]

@jwoegerbauer Is there a chance to reenable dm-verity and update normally or do I have to use MSM?