MIUI 12.0 MIUI 12 STABLE RELEASE


Do you like this MIUI version?

  • Total voters
    4,215
Status
Not open for further replies.
Sylar82 said:
try this
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
not my fix but someone here made it
Click to expand...

Thank you, but it didn't work. Phone is as dead as it can be.
I need someone who can flash with help off EDL.
But the problem is that in the Netherlands aren't xiaomi certified repair shops. And the xiaomi shop in Rotterdam isn't willing to help.
I'll guess I have to buy another phone. But one thing for sure. Never miui again.
If somone know how to find en certified repair shop, please feel welcome to share,
 
Stirf said:
Thank you, but it didn't work. Phone is as dead as it can be.
I need someone who can flash with help off EDL.
But the problem is that in the Netherlands aren't xiaomi certified repair shops. And the xiaomi shop in Rotterdam isn't willing to help.
I'll guess I have to buy another phone. But one thing for sure. Never miui again.
If somone know how to find en certified repair shop, please feel welcome to share,
Click to expand...
IM VERY SAD FOR THAT,, i hope someone here can help you
 
Stirf said:
Thank you, but it didn't work. Phone is as dead as it can be.
I need someone who can flash with help off EDL.
But the problem is that in the Netherlands aren't xiaomi certified repair shops. And the xiaomi shop in Rotterdam isn't willing to help.
I'll guess I have to buy another phone. But one thing for sure. Never miui again.
If somone know how to find en certified repair shop, please feel welcome to share,
Click to expand...
I'm not Sure, maybe unbrick.ru can help you. Or You can try to send the phone to Store in Germany, Düsseldorf.

Gesendet von meinem MI 3W mit Tapatalk
 
Stirf said:
Thank you, but it didn't work. Phone is as dead as it can be.

I need someone who can flash with help off EDL.

But the problem is that in the Netherlands aren't xiaomi certified repair shops. And the xiaomi shop in Rotterdam isn't willing to help.

I'll guess I have to buy another phone. But one thing for sure. Never miui again.

If somone know how to find en certified repair shop, please feel welcome to share,
Click to expand...

@Stirf i did warn you before, but I'm sad you went ahead and brick your device

geoorg said:
Before you go about applying other suggestions
Please check your current anti-rollback value using
"fastboot getvar anti"
And compare with "CURRENT_ANTI_VER" in "flash_all.bat"
Or "ROM_FOLDER/images/anti_version.txt"
Force flashing could lead to hard-brick and only make the situation worse for you

That number is the rollback index of the MIUI version you want to flash. If that number is equal to or greater than your current rollback index, then it’s safe to flash. If that number is less than your current rollback index, then DO NOT FLASH
Click to expand...
 
Last edited:
  • Like
Reactions: Sörnäinen and Sylar82
geoorg said:
@Stirf i did warn you before, but I'm sad you went ahead and brick your device
Click to expand...

fastboot getvar anti :1

flash_all batt :
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *umi" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *umi" || exit /B 1

::check anti_version
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
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @echo "Antirollback check error" && exit /B 1
 
Stirf said:
fastboot getvar anti :1

flash_all batt :
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *umi" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *umi" || exit /B 1

::check anti_version
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
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @echo "Antirollback check error" && exit /B 1
Click to expand...
What of the value inside "images/anti_version.txt"?
What version of stock ROM did you download?
 
Stirf said:
Failed (remote: 'failed to load/authenticate boot image: load error')
fastboot: error: command failed

windows 10
Click to expand...
You can try to flash boot.img from your previous rom , you have nothing to lose ..
Put boot.img of previous rom to adb folder ( where you have twrp )..
Connect to fastboot , open a cmd and write ..
fastboot devices ( device recognision ) ..
fastboot flash boot boot.img
If it passed OK you can go on with ..
fastboot reboot ( before hit enter hold vol down until phone enter fastboot mode again ) ..
Now try to boot to twrp not flash ..
fastboot boot twrp_umi.img ( or whatever you named it ) ..
 
UMI with 3.4.2B-0623 and V12.2.2.0 PROBLEMS:

CTS Profile Match - Failed , so no GPay etc

and no VoWifi VoLTE
 
JPRode said:
UMI with 3.4.2B-0623 and V12.2.2.0 PROBLEMS:

CTS Profile Match - Failed , so no GPay etc

and no VoWifi VoLTE
Click to expand...
Why you have problems with TWRP?

CTS profile ===> find tutorial, how use props to make CTS working (I add tutorial in a few comments)

I don`t have too, but my cellurar provider (Play) don`t want add my device, to their configuration
 
Like I said yesterday my phone is dead. Now is in repair shop. I hope the warranty will cover this. Good thing is my phone doesn't turn on.
 
As far as I know, Xiaomi should accept the warranty claim even with custom rom, as they are allowing BL unlock.
In my country (Serbia) they don't care if you have a custom or factory rom.
Confirmed.

Послато са Mi 10 помоћу Тапатока
 
Mi 8 Lite was discontinued updates? I haven't seen updates in beta or stable for ages. Last stable rom is from August. I'm always seeing updates from other models.
 
12.2.2's bug
Anyone else?
03c7089ff1a7f98a4c272ef127ae11e5.jpg
 
Sylar82 said:
why this happen to your phone ???
Click to expand...
In the latest update for Mi 10 there is a problem with TWRP. When I decided to check if this is the case with me, the phone went into Fastboot. He did not accept commands. reboot, boot, flash. I decided to use Mi flash and install Stock rom but it went without success. For some reason, I was able to log in to Twrp and reinstall the latest update. Then I tried to enter the recovery again without success. He went into the fastboot and again did not accept my commands, I went to turn it off forcibly and the phone died.
 
Nedk-off said:
In the latest update for Mi 10 there is a problem with TWRP. When I decided to check if this is the case with me, the phone went into Fastboot. He did not accept commands. reboot, boot, flash. I decided to use Mi flash and install Stock rom but it went without success. For some reason, I was able to log in to Twrp and reinstall the latest update. Then I tried to enter the recovery again without success. He went into the fastboot and again did not accept my commands, I went to turn it off forcibly and the phone died.
Click to expand...
Almost the same happened to me. No matter what I try, always booting into fastboot and not able to do anything. I tried to install Magisk and it wend wrong.
 
Nedk-off said:
In the latest update for Mi 10 there is a problem with TWRP. When I decided to check if this is the case with me, the phone went into Fastboot. He did not accept commands. reboot, boot, flash. I decided to use Mi flash and install Stock rom but it went without success. For some reason, I was able to log in to Twrp and reinstall the latest update. Then I tried to enter the recovery again without success. He went into the fastboot and again did not accept my commands, I went to turn it off forcibly and the phone died.
Click to expand...
the same thing happen to my i got error in adb command but i read here that the adb command work with last twrp update so i try and its work but even when the adb not work and i go to fastboot when i restart the phone its work but cant go to twrp
 
Status
Not open for further replies.

Similar threads

ingbrzy
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
33K
HyperOS
emre_66
E
ingbrzy
  • Locked
HyperOS 1.0 24.7.28 (Final)
Replies
292
Views
268K
HyperOS
Igor Eisberg
Igor Eisberg
ingbrzy
  • Locked
HyperOS 1.0 24.7.22/25/26
Replies
51
Views
38K
HyperOS
Ahaba
A
ingbrzy
  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
41K
HyperOS
Mistery88
M
ingbrzy
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
42K
HyperOS
KGVER
KGVER
Top Bottom
Back