MIUI 12.5 21.1.6/7


Do you like this MIUI version?


  • Total voters
    255
Status
Not open for further replies.
33910

Why is there no Belarusian language?
 
  • Angry
Reactions: psydex
Google Playstore "Play Protect certification" - Device not certified
  • clear Data "Google Play store", "Google Play services", "Google Service Framework"
  • reboot

Tried several times - doesn't help.

The device name changed from Poco F2 Pro to Redmi K30 pro... Probably it causes the problem with device certification?

33911
33912
 
* * * * * * * * * * * * * * * * * * * * * * * * * * *
Redmi K30 PRO rom has 4 issues

1- Google Pay * still don't works on Redmi K30 PRO due to CTS error on Safetynet "probably modified or rooted":

N.B.: Phone with No Root... Google Pay always working with every rom before...

I read about Magisk but not sure about flashing it, I don't need... and I read about flashing issues due to necessary DisableForceEncription.zip

2- quick charge not working anymore (car, 2nd charger,..)... only on its original charger is still Fast

3- battery drain issue...its Original ROM was veeeery long lasting!

4- top toggle bar lose continuously toggle my favorite position
* * * * * * * * * * * * * * * * * * * * * * * * * * *
 
Last edited:
  • Like
Reactions: dattohead
Взаимодействие с другими людьми
[QUOTE = "truelutti, post: 583049, member: 248193"]
Redmi k20 pro: Хорошо, после обычного обновления OTA я вернулся в twrp. Что мне теперь делать? Я попытался перезагрузить систему, но ничего не вышло.
[/ QUOTE]
Такая же проблема k20pro orange fox
 
My battery is draining absurdly quickly. I lost 5% in 7 minutes using instagram. Screen brightness at 50% and using wifi. Anyone else with a battery drain problem? The previous rom was twice as long.

Poco f2 pro
 
Поко f2 pro
[/ QUOT
My battery is draining absurdly quickly. I lost 5% in 7 minutes using instagram. Screen brightness at 50% and using wifi. Anyone else with a battery drain problem? The previous rom was twice as long.

Poco f2 pro
Такая же проблема k20pro
 
K20 pro keeps booting to twrp. Is it because I have to use a pin on twrp? If so I to disable pin.
 
I give up this weekly rom. I’m going back to the first 12.5 because it was stable and the battery was running very well.
 
MI 9T Pro
I migrated from 18.11.20 to 06.01.21, that went without problems, so no TWRP issues or bootloop (running latest magisk beta)

I have however a problem with 5ghz wifi: auth seems to work, but no application is able to reach the internet. My 5ghz wifi is operating in channel 52.
2.4 ghz wifi works fine.
 
Mi9 SE here:
So far tried as it is written in the 1st post under WARNING FOR Mi 9 SE:

Fastboot start recovery
Handy starts in recovery
I have to decrypt my memory as always
then I flash the rom with no errors displayed
then I press restart into the system ...

And then nothing else,
it restarts and goes straight back into recovery, every time the phone is started
I've already tried 3 different TWRPs and always got the same result.
Besides The 3.5.0_10 TWRP doesn't work for me because this version doesn't even let me decrypt the memory.

Factory reset doesn't change anything either, even tried that with several twrp's.

I also tried to flash the older Rom version from 28.12.2020 again with all 3 twrp's, without success, the mobile phone only boots into recovery although it ran without problems before....

I even tried flashing the vbmeta.img of the rom again with:
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
because I read it could help to break the bootloop and that didn't help either.

Are there still people here where the Mi9 SE runs with the latest version or does the version just generally not work?
I have tried these steps (different TWRP's, ROM's) even usb-otg, but depending on twrp the phone stucks in fasboot or twrp no reboot to system possible.. The latest TWRP 3.5.0_9-0 even does not recognise the ROM - error 7.
I am suffering from this since yesterday the ROM was published and I am going crazy because there is no solution to get a working system. Moreover many 9SE owners experiencing the same.
I would like to ask our devs @ingbrzy @Igor Eisberg to deal with the problem, because it exists since the 12.5 was published.
 
Status
Not open for further replies.

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
41K
Replies
51
Views
38K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
42K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
33K