Mi 10 pro - problem with rollback

[julien31700]

Hello,

I tried to install a global Xiaomi rom site, but I had problems with the TWRP.

I wanted to install an official version with miflash, but I have a rollback problem.

My phone is in version 1, and the official roms are in version 0.

I don't know what to do anymore, would anyone have a solution?

Version of my phone:

Version of the latest rom found:

sorry for my English
----------
In french :
Bonjour,
J'ai tenter d'installer une rom Xiaomi global du site, mais j'ai eu des problèmes avec le TWRP.
Je voulais installer une version officiel avec miflash, mais j'ai un problème de rollback.
Mon téléphone est en version 1, et les rom officielles sont en version 0.
Je ne sais plus quoi faire, quelqu'un aurait-il une solution?
Version de mon téléphone :

Version de la dernière rom trouvée :

Je suis complètement bloqué?

 

[B!GBOY]

What is the problem?
The line you marked means if the variable is not defined set it to 0. also there is a check for it just 4 lines after that.

For example the following:

echo setting variable to 0
set CUR=0
if [%CUR%] EQU [] set CUR=2
echo %CUR%

echo removing the variable
set CUR=
if [%CUR%] EQU [] set CUR=2
echo %CUR%

produces the following result:

setting variable to 0
0
removing the variable
2

 

[marcel112]

i believe i had the same.
I am pretty sure you dont have the file extracted to the root off your c drive.
I mean, when its extracted to a subfolder , miflash can give this problem.
So extract to root off c drive and try again

 

[julien31700]

Thank you for his feedback! I finally solved my problem thanks to this trick:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

For me it has to work, after being careful, because one is close to the manipulations that can brick the phone

 

[B!GBOY]

Thank you for his feedback! I finally solved my problem thanks to this trick:

For me it has to work, after being careful, because one is close to the manipulations that can brick the phone

This is actually not a good idea if you are really flashing a firmware with anti roleback protection! Those lines basically ensure that you don't flash such firmware if it's number is lower than the current one. They do the following:

1. Check firmware files for an anti roleback version and set it to "CURRENT_ANTI_VER" ( set it to 0 IF not found)

2.Check phone for anti roleback and set it to "version" ( set it to zero IF not found)

3.At the end check and prevent flashing if the new firmware has a lesser ARP version

So if you really had a roleback problem in the first place your phone would have been a brick now But luckily they decided not to use that feature as far as I know. Meaning they do not enforce it by incrementing the number with each update. To make sure of this I checked the lasted fastboot firmware available and found out that it's ARP version is 1 just like my device that still has the ARP version it was launched with (also 1).