Well, I am not sure since I just began flashing this phone yesterdayBro , Thank you so much for the heads-up , you a re a life saver ..this is is bad news.
Do you remember or have any idea when this was implemented ? date approx or version?
fastboot getvar anti
Unfortunately they have already implemented that in latest MIUI 11... :crying:Do not install MIUI12 and you will be safe. If you use custom roms, I do not see reasons to install stock rom.
You don't even understand the logic of flash_all.bat ;__;Just a quick alert against hard bricks. It is already known around and has caused a few hard bricks. However, it seems that our device was once said to be unaffected before, so I decided to post it here to alert others.
Short suggestion: Never ever flash any lower/unknown version firmware via recovery again; MiFlash will protect from downgrading by throwing an error beforehand; Non-MIUI ROMs should theoretically remain unaffected.
Long story:
I tried to flash the latest European MIUI from the latest Chinese one via MiFlash, which prompted me with the following error ahead of any actual flashing operation,
So I looked at the log,
Then I tried , which returned
After that I inspected flash_all.bat,
So it is clear that Xiaomi is putting anti-rollback onto our devices. Actually it was a great fear since I could have chosen the recovery firmware rather than the fastboot one. Hopefully nobody will end up with a hard brick again due to downgrading.
P.S. I plan to flash the EEA firmware once MIUI 12 rolls out.
Related article: Xiaomi’s Anti-Rollback Protection Explained: How to avoid bricking your phone
Uh honestly I am not familiar with Xiaomi devices yet so my apologies in advance. However, according to the website I quoted above there should be no value if the anti-rollback is not triggered. Moreover, some posts in Q&A section revealed the possibility of a hard brick due to improper downgrading iirc. After all, if I want to flash that ROM, it should still involve setting the anti value back to 0 IMHO...You don't even understand the logic of flash_all.bat ;__;
MiFlash try to put ARB 0 for some reason but you have ARB 1 so that's make your flash error, sometimes MiFlash act like that on many devices
Many users can rollback to latest MIUI 11 from MIUI 12
If you have anti:1 and MIUI with android 10, you can install each other android 10 but can't android 9.If i'm on MIUI12 (anti: 1) , can i install CrDroid 6.6 Android 10 ?
It does not work that way. If you have "anti:1", then you can flash only ROMs with "anti:X" equal or greater than 1. It does not matter if it is Android 9 or 10, MIUI 11 or 12, etc. Flashing ROM with "anti:0" or without "anti:X" at all will not be possible. Flashing ROM with "anti:X" greater than your actual "anti:X", will increase your actual "anti:X" in the phone.If you have anti:1 and MIUI with android 10, you can install each other android 10 but can't android 9.
If you have anti:1 and MIUI with android 9 , you can iinstall each other android 9 and android 10. I am not sure if custom android 10 will block installing custom android 9. I suppose only installing MIUI with a10 will block device on android 10.
This! So if i unlock my cc9 and flash one of those miui12 weekly roms via twrp, it wont really do anything? Right now on miui11 stock 11.3.5.0 P and in need of a factory reset so ill probably unlock and go for custom romsPlease remember that "anti:X" matters ONLY when flashing original MIUI ROMs on locked bootloaders. It does not matter at all when flashing custom ROMs on unlocked bootloaders.
Please STOP writing B.S and talking about things you don't know !EDIT: I AM NEW TO XIAOMI DEVICES AND REACHED THE CONCLUSION SOLELY BASED ON MY OWN EXPERIMENT AND RELATED READINGS, OUT OF GOODWILL THAT NOBODY WILL POSSIBLY HARD BRICK THEIR DEVICE. I AM NOT CERTAIN ABOUT THE ACCURACY OF ANY INFO BELOW SO PLEASE FEEL FREE TO POINT OUT ANYTHING I HAVE WRITTEN WRONGLY, BUT I WOULD ALSO BE MOST GRATEFUL IF YOU COULD KINDLY REFRAIN FROM POSTING TOXIC COMMENTS. THANK YOU IN ADVANCE!
Okay I do apologize for being so sarcastic...but I was just totally pissed off about the arrogance of someone replying rudely. (that comment has already been deleted by moderators)
Just a quick alert against hard bricks. It is already known around and has caused a few hard bricks. However, it seems that our device was once said to be unaffected before, so I decided to post it here to alert others.
Short suggestion: Never ever flash any lower/unknown version firmware via recovery again; MiFlash will protect from downgrading by throwing an error beforehand; Non-MIUI ROMs should theoretically remain unaffected.
Long story:
I tried to flash the latest European MIUI from the latest Chinese one via MiFlash, which prompted me with the following error ahead of any actual flashing operation,
So I looked at the log,Code:error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done
Then I triedCode:[12:03:03 AM dc26242f]:info1:current device antirollback version is greater than this pakcage, which returnedCode:fastboot getvar anti
After that I inspected flash_all.bat,Code:anti: 1
So it is clear that Xiaomi is putting anti-rollback onto our devices. Actually it was a great fear since I could have chosen the recovery firmware rather than the fastboot one. Hopefully nobody will end up with a hard brick again due to downgrading.Code:if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a)) if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0 for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i) if [%version%] EQU [] set version=0 if %version% GTR %CURRENT_ANTI_VER% ( echo current device antirollback version is greater than this pakcage exit /B 1 )
P.S. I plan to flash the EEA firmware once MIUI 12 rolls out.
Related article: Xiaomi’s Anti-Rollback Protection Explained: How to avoid bricking your phone