Database Develop

Link for a clean 10.0.3 Boot.img

Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,

aliensk said:
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
Click to expand...
Click to collapse
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12

lept_2014 said:
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
Click to expand...
Click to collapse
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.

Hey guys,
I managed to resolve the bootloop issue. If anyone has the same issue use the following untouched boot.img
https://xiaomifirmware.com/download/11657/
As I was suspecting, the ones I was using the from the links provided in the forum were too small and this one is 64 mb. After flashing it boots perfectly.
However, unfortunately again I get errors during the update. At least no bootloop

aliensk said:
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Click to expand...
Click to collapse
That Stock BOOT works fine for me. Remember flash it into the right slot for you.

I did flash to to slot B as the getvar current-slot was B but it was still bootlooping until i tried the last one from the link I provided. However, since I am still unable to update, is there a link to download the system.img for 10.0.3.0 just in case i have somehow modified my system? I dont remember to have done anything but just in case.
Thank you.

How will you solve it
Plz...tell me with boot file how fill solve your problem

Varshithpoudala said:
Plz...tell me with boot file how fill solve your problem
Click to expand...
Click to collapse
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful

aliensk said:
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
Click to expand...
Click to collapse
Did you find any way to fix it?

[recovery] twrp 3.2.1-0

TWRP for EMUI 9.1​
THIS TWRP IS FOR DEVICES WITH KIRIN 65x SOC (HI6250) RUNNING EMUI 9.1 AND NOT EMUI 8
What's different from TWRP for Android 8?
erecovery_ramdisk option to flash .img
system_root partition for 9.1
What works now?
You can now flash .zip like Gapps and they'll work (before it gave error 64)
What doesn't work?
At the moment, I don't know if ADB sideload works.
Otherwise, everything seems to be working.
How to flash this TWRP
To recovery_ramdisk
Code:
fastboot flash recovery_ramdisk [TWRP].img
I DIDN'T BUILD ANY OF THIS
I only modified a TWRP (which I don't know the author, sorry) to make it work good on hi6250 EMUI 9.1 devices.
I would like to have the hardware and knowledge to build and develop new stuff but at the moment I can't.
Download - https://drive.google.com/open?id=10VONtu_Bf6grW60N7K8gMrzQSG-rswni
Feel free to contact me on Telegram
https://t.me/GelberVogel (PM) - temporary

screenshots

This guy's doing gods work, saved me from throwing a perfectly good device into the trash. Working perfectly, tested on an ANE-LX1!

Anyone know ROMs that will work with emui 9?
I Know openkirin a long time but the Bluetooth is restarting in the emui 9 based builds.

with this recovery boot the gsi roms? currently only the openkirin gsi boot, but using adb... All the gsi I've flashed by adb or the previous recovery give bootlop

joaomoreira1001 said:
Anyone know ROMs that will work with emui 9?
I Know openkirin a long time but the Bluetooth is restarting in the emui 9 based builds.
Click to expand...
Click to collapse
Probably phh treble

Linux Lounge said:
Probably phh treble
Click to expand...
Click to collapse
i will try it thanks
---------- Post added at 09:09 PM ---------- Previous post was at 08:48 PM ----------
Linux Lounge said:
Probably phh treble
Click to expand...
Click to collapse
nope that does not boot

Yellow_B_ird said:
TWRP for EMUI 9.1​
What's different from TWRP for Android 8?
erecovery_ramdisk option to flash .img
system_root partition for 9.1
Click to expand...
Click to collapse
Hello, please can someone tell me how to flash it in erecovery_ramdisk partition?
I have recovery brick and i can't flash it in recovery_ramdisk...
This is my last hope!

Mustaine635 said:
Hello, please can someone tell me how to flash it in erecovery_ramdisk partition?
I have recovery brick and i can't flash it in recovery_ramdisk...
This is my last hope!
Click to expand...
Click to collapse
Tell me what device do you have (luckily I came back to XDA early enough, I hope)
Also, try flashing stock kernel (I can send mine for HUAWEI P Smart 2018 FIG-LX1C432 EMUI 9.1 B120)

Yellow_B_ird said:
Tell me what device do you have (luckily I came back to XDA early enough, I hope)
Also, try flashing stock kernel (I can send mine for HUAWEI P Smart 2018 FIG-LX1C432 EMUI 9.1 B120)
Click to expand...
Click to collapse
I have p smart fig-lx1.
I tried to flash it using fastboot flash erecevery_ramdisk [file].img but it says failed...
The standard recovery was bricked because i used hurupdater to update to emui 9.1... The phone works but i have no recovery so i can't do anything...

Yellow_B_ird said:
Tell me what device do you have (luckily I came back to XDA early enough, I hope)
Also, try flashing stock kernel (I can send mine for HUAWEI P Smart 2018 FIG-LX1C432 EMUI 9.1 B120)
Click to expand...
Click to collapse
It works! I had to flash 3 files for the stock recovery (recovery_ramdisk, _vbmeta and _vendor). Then i flash the twrp recovery and it works. The only problem is that when i browse internal storage, the folders name are all random characters... Why that?
Another question is, how can i root my device now?

Mustaine635 said:
It works! I had to flash 3 files for the stock recovery (recovery_ramdisk, _vbmeta and _vendor). Then i flash the twrp recovery and it works. The only problem is that when i browse internal storage, the folders name are all random characters... Why that?
Another question is, how can i root my device now?
Click to expand...
Click to collapse
Glad it worked!
Just flash Magisk like you would with any TWRP assuming it works. If you want recovery and root in a stupid way.. just flash my TWRP to recovery and in recovery, flash my or any other TWRP/recovery to e-recovery and after that, flash Magisk like usual.

Thank you for the build. Any chance of flashing this on a device with locked bootloader, like using an official flash tool to flash a signed recovery or using e-recovery (I have experience with bootloader and flashing but not with Huawei/Kyrin)?

I keep getting a (remote: partition length get error) error ... Any help ?

Thanks a lot!! :good:

The Google Drive Link doesn't work!
I am trying to root my Huawei P Smart but the Google Drive Link for TWRP doesn't work https://forum.xda-developers.com/huawei-p-smart/development/recovery-twrp-3-2-1-0-t3953343
Was your Google account terminated. If you are able to can you send me the TWRP Image or if your Google account works can you upload the TWRP image to Google Drive?
Love from Greece![/QUOTE]

Hi, gelber here.
I'm sorry for the confusion, but I really barely touch XDA and as I deleted my old Google account, I lost access to this XDA account (I_am_gelber) and to that gdrive link. However, I can defo give the file back in a bit but I'm surely gonna forget. If you really want the file, please pm me at t.me/ActuallyNotGelb since I still need to give it a quick find.
Thanks!

ActuallyNotGelb said:
Hi, gelber here.
I'm sorry for the confusion, but I really barely touch XDA and as I deleted my old Google account, I lost access to this XDA account (I_am_gelber) and to that gdrive link. However, I can defo give the file back in a bit but I'm surely gonna forget. If you really want the file, please pm me at t.me/ActuallyNotGelb since I still need to give it a quick find.
Thanks!
Click to expand...
Click to collapse
Can you please upload the file to some website. I'm unable to create a Telegram account right now so can you please upload the image to any website? It would mean a lot for me for you to do that!

GreekProgrammer said:
Can you please upload the file to some website. I'm unable to create a Telegram account right now so can you please upload the image to any website? It would mean a lot for me for you to do that!
Click to expand...
Click to collapse
Any luck?

Mi 8 soft brick

Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro

You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2

tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due

ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.

tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem

ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot

ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.

tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again

Is it possible that this is part of the problem..!
I can't check it
@tsongming

ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img

ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.

tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?

ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..

For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.

Patching boot.img for BV6300 Pro (Helio P70 / MTK)

Hi all, I'd like to share my experiences here about trying to patch boot.img for the Blackview BV6300 Pro which is one of the countless MediaTek Helio P70 (aka MT6771) China phones that can be had for a bit of change at every corner nowadays. It features a fairly non-clutter generic Android 10 ROM.
I bought it because of good feature/price ratio. I also like the fairly idiot-proof MTK Preloader/SP Flash Tool combo and expected no big problems having the phone patched. Apparently that estimate was wrong.
I extracted the boot.img (at exactly 32768k) and started patching it with the latest Magisk Manager (8.0.4). When set to "Stable" the patched result came out less than 12Megs which struck me as very odd, so I did not bother trying to flash that and switched to "beta". Et voila, out came a patched image that appeared to have just the right size.
Unfortunately, after flashing the patched image, the device detected a modified boot signature and flagged "Red State, rebooting in 5s", effectively entering a boot loop. Going back to stock, then unlocking the bootloader with fastboot and reflashing patched boot changed the "Red State" to "Orange State" but the boot loop persisted.
The boot loop message also suggests to either reflash stock or "disable verified boot". Yeah, but... Magisk Manager 8.0.4 seems to have lost the "Advanced Options" menu that had been there in previous versions, allowing users to toggle dmverity while patching boot images... so I wonder how to get around this!? Any suggestions?

Any solution for this, or any suggestions to try??

Have you tried this?
https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/

Didgeridoohan said:
Have you tried this?
Click to expand...
Click to collapse
Thanks for your suggestion but it seems like this requires TWRP and, as far as I know, no TWRP recovery is available for the BV6300 Pro.

You have to unlock your bootloader FIRST and not after.Start from scratch and it will work,im sure.Cheers!!!

First make the new,i mean flash fresh firmware blablabla.Extract your firmware,copy boot img to phone,install magisk manager and patch the boot img(im sure you can do it without root(on my Redmi 9 it works),copy patched boot imhg to pc and use adb to flash,but be sure your bootloader is unlocked before.Good luck.

We must unlock the bootloader with fastboot mode or we can do it through developer options??

black_knight_ said:
We must unlock the bootloader with fastboot mode or we can do it through developer options??
Click to expand...
Click to collapse
Fastboot

Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...

black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
black_knight_ said:
Bitmixer have you manage to root your phone?
Because i still get a bootloop when flashing the patched boot image...
Click to expand...
Click to collapse
Did you flashed vbmeta.img ,thats important.

-CALIBAN666- said:
Did you flashed vbmeta.img ,thats important.
Click to expand...
Click to collapse
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?

black_knight_ said:
DId you mean to follow the guide of : https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/ so we can disable verified boot, because that requires twrp and it is no supported on our device.
Or something else?? And where we find vbmeta.img that disable verified boot?
Click to expand...
Click to collapse
Ive flashed vbmeta with adb on my phones,like my Redmi 9,when you dont have vbmeta i think u cant do anything with flashing something,just google for it or look here for it,good luck!!!

Question how to get rid of Dm-VERITY corruption on boot

Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks

forget this..i've got ROOT check the other thread !

How do you fix it?

simika said:
forget this..i've got ROOT check the other thread !
Click to expand...
Click to collapse
How did you managed to fix this?

by reading lol.. check the other thread all written

For reference to whoever that are confused about where to look for the solution.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Download the vbmeta and flash it via fastboot to get rid of the dm-verify.

simika said:
by reading lol.. check the other thread all written
Click to expand...
Click to collapse
Could you reference a link or give me a little how to?
I tried a lot now:
- Installed a new Firmware trough Fastboot
- Using MsmDownload Tool
nothing helped so far.
So it would be great if you could assist in any way.

simika said:
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
Click to expand...
Click to collapse
I done everything but my phone doesn't unlock so now I have the dm-verity warning and I can't do a clean flash with Miflash. Also Miflash Unlock doesn't work. What I can do now?

if you can enter in fastboot mode, reflash stock boot and vbmeta

wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
How can I do? Miflash says:
error:Writing 'crclist' FAILED (remote: 'not allowed in locked state')

bro you have relock bootloader, this is a fatal error. the only way is try to unlock with an mtk tool that do this via pc. you can find on internet. search unlock all mtk devices. i think there a link also on xda

Just realized that the M3 thread, my phone is a M4.

.

@simika how are you sending this question?

1. Hello friends, there are two ways to fix this problem, first you need Root, I read your Root tutorial, your tutorial is very good, and after using Root, you need to download any file manager, give Root Permissions, you need to backup your baseband, nvram nvdata nvcfg backup and save, you also need an MTK Bypass, you can search for MTK Auth Bypass Tool through Google, you also need to use SP Flash to flash the machine, you need to download the official firmware package, which can be downloaded from xiaomirom.com , download the corresponding version, use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, But you have backed up. Boot through fastboot to unlock the BL lock, perform fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. Congratulations The baseband is back, I'm a novice, my instructions are not comprehensive, such as where is the baseband location, but I have too many characters, I will list the baseband location. 2. Replace a new motherboard, all mobile phone problems are all solve.
Hope to help you.

wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
Thanks. This worked on my Umidigi A11 phone.

xdadev_user11 said:
Thanks. This worked on my Umidigi A11 phone.
Click to expand...
Click to collapse
nice!

hello i got the same problem today, my phone is redmi9a can some help me regarding to this error ?

i had this problem even though i never unlocked my bootloader so i couldnt flash anything to fix it. but when i got the miui 13 update it fixed it for me

wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
What if you cant enter fastboot?