[POCO M3 Pro / Redmi Note 10 / 10T 5G] 1lopes:
MIFLASHPRO PROCEDURE​

The MiFlashPro procedure is easier (and the easiest to recover your hard-bricked device), as you do not require the installation of any other external program (like python used in MTK Client for example (expect, of course, the drivers)

MTK Client is a more complicated installation as it requires the installation of Python and Git, which can be harder to use commands for people that don't or never used Python and Git, but gives you access to lock and unlock your bootloader with no 168 HOURS wait

In general, newer MTK chips are really easy to unbrick, even from a hard-brick, as it does not requires to open your phone and test-point it (especially this forum MTK 6833), compared to Snapdragon chips, which is the opposite and even costs 25€ to have a "Authorized Mi EDL Account". Keeping that out of the way, lets get to it

FIRST OF ALL​

Install the MTK Preload/BROM VCOM drivers for your computer to recognise your phone in BROM state and follow the instructions given in the installation. Attached at the end of the thread

And download any MIUI ROM version from any trusted website (my favorite is mifirm.net, it downloads faster)

INSTALL MIFLASHPRO Attached at the end of the thread​

There's two different Mi Flash(es). Mi Flash and Mi Flash Pro.

Mi Flash is only used to flash MIUI in your device, nothing special, probably everyone knows about it.

Then theres Mi Flash Pro (MFP for short). It's an All-In-One (AIO) tool, as shown below.

View attachment 5860069

We got the some tabs, but let's focus on the "Recovery" and "SP Flash" tabs, as we do not need the other ones.

Recovery - Recovery flashing. If your device is only booting to Recovery (which can be possible, since someone here has got a case that couldn't boot to fastboot neither system, only to recovery), by writing both your device IMEI's on the spaces, then clicking "Refurbish" leads to a more advanced factory reset than just wiping your data normally. This can get you out of recovery and go back to MIUI however. If it's not your problem, then follow on.

SP Flash - The famous SP Tool. SP Tool is a easy tool to use, may be confusing at first, but then first time a charm and you can get used to it, easily, or after some times. SP Tool is famous for recovering many MTK devices from hard bricks, and thats what we will use to recover your device.

OPEN SP FLASH UP​

Here you are, greeted by a nice interface. There's nothing, but I will explain you to it.

There's 3 blank spaces, called Download-agent (DA for short), Scatter-loading file & Authentication file.

DA is to have access to the devices internal storage to be able to do the flashing;

Scatter-loading shows you the mapping of the partitions it will flash on the MTK;

Authentication is just the MTK protection for newer mtk devices that you need to be able to flash (*its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)

Now, fill the blanks up:

To find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.

To find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.

Finally, to find the scatter-loading file, it is in the ROM folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). The scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.

Done?

Don't flash it yet, as we need to fix a issue with "combo_partisize_check".

Open up the scatter-loading file with Notepad or any text editor, so the text file named "MT6833_Android_scatter.txt".

Now, use the locate function to locate the following:

combo_partsize_check: true

After finding the first one, replace the "true" to "false", and the following one, and so on, till every line of them is set to "false" and isn't able to locate any set as "true".

We are done and finished setting up SP Tool!​

*Now, we need to bypass the Authentication of our device. Why? Just as the Snapdragon chips, Xiaomi has also implemented a security layer where you need to log in with a "Authorized Mi Flashing Account", which costs money (generally only on Snapdragon devices, I am not sure if we can find any paying service for it), which is really easy to bypass due to BROM.

Download the file "mtkauthbypass.zip" attached in the thread below.

Extract it, open it up, and it looks like this:

Now, press the "Disable Auth" button, you will have 60 seconds to get ready, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompt appearing in the blank space. Should be similiar as this:

(thanks to chopwell20 for image)

After that, immediately open up SP Tool, and press "Download" as fast as possible.

Let it flash, from 5 to 15 minutes.

After it finishes, a blue window with a checkmark appears, disconnect your phone, and just press down the POWER button to boot it up.

And thats it! You have recovered your phone!​

If you have any issues or it didn't work out, please reply so someone can help you out

(Simplified image to understand better without explanation)

View attachment 5860075

ISSUES​

CONNECTIONS ISSUE is completely normal!

It is when you try to connect your phone in BROM mode to your computer, but it always shows the error symbol over it.

View attachment 5860831

From what it seems, this should be a issue from the phone and not your computer or the drivers itself

It doesn't mean that it makes you unable to unbrick it, but a lot of patience, as with this issue you will require to keep trying over and over again to bypass it.

So, if you can't bypass the Auth, this is probably it. Just keep trying and trying over again till you get it. There's (probably) no workaround rather than having patience to do it

(This also happens to me every time, so I consider it normal, and with some users such as bg0169 having this same issue, I just considered this was important to address it out, but if you think its not this issue, then reply, better safe than sorry)

I made this thread due to some users bricking their devices, and for every new user that hard-bricks their device to hopefully make this to help them