# stuck in instructions about dm verity corrupted

#### lumyx012

##### Member
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

##### Member
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.

Staff member

#### lumyx012

##### Member
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

#### Attachments

• xxx.PNG
72.5 KB · Views: 15

#### lumyx012

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

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)?

#### Attachments

• Capture.PNG
376.1 KB · Views: 10
• Capture.PNG
72.2 KB · Views: 10
• xzx.PNG
58.1 KB · Views: 10

#### jwoegerbauer

##### Senior Member
Re-flash Stock ROM using MTK Flash Tool.

#### alecxs

##### Forum Moderator
Staff member
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

##### Member
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.

Last edited:

Staff member

#### Attachments

• Capture.PNG
13.4 KB · Views: 10

#### lumyx012

##### Member
Re-flash Stock ROM using MTK Flash Tool.

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

##### Forum Moderator
Staff member
i followed the instructions and when i run the code python setup.py install, at the end it gives me this message.
"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

Last edited:

#### lumyx012

##### Member
"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
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

#### Attachments

• Capture.PNG
23.6 KB · Views: 5
alecxs

#### alecxs

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

#### lumyx012

##### Member
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).

Last edited:

#### alecxs

##### Forum Moderator
Staff member
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

##### Member
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

##### Forum Moderator
Staff member
I assume that is command line tool, you should type from cmd.exe like for all command line tools
Code:
cd "C:\path\to\dir"
UsbDkController.exe -n

#### SnoopyFTW

##### Member
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:

Code:
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:

Code:
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:

Code:
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!

jwoegerbauer

### Top Liked Posts

• There are no posts matching your filters.
• 1
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:

Code:
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:

Code:
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:

Code:
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!
• 1
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:

Code:
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:

Code:
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:

Code:
fastboot flash --disable-verity --disable-verification vbmeta_vendor_a vbmeta_vendor.img
fastboot flash --disable-verity --disable-verification vbmeta_vendor_b vbmeta_vendor.img
1
"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
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
1
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:

Code:
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:

Code:
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:

Code:
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!