Database Users

[MiUI Notch Notification Mod] for beta or global version

Requirements
We are updating MiUI Notch Notification Mod every week for MiUI dev and stable firmwares. In order to install this mod, you need to match the following requirements:
Xiaomi Android smartphone or tablet
v10 ROM
Unlocked Bootloader (for TWRP)
TWRP custom recovery
How-To
Click the download-button and select your Xiaomi rom version from the list to get the MiUI Notch Notification Mod for your correct MiUI ROM version. You can choose from two different packages, which will let you either Install or Uninstall the mod.
Download the ZIP File
Download link for all version
https://mi-globe.com/mod-download/?modtype=notchnot&id=13&codename=platina&phone=Mi+8+Lite
Copy the File to your phone/tablet
Reboot to TWRP Recovery
Select ‘Install ZIP from /sdcard’
Select the ZIP File
Install and Reboot

I'm in global 10.3.1.0, which version do I use?

renan1217 said:
I'm in global 10.3.1.0, which version do I use?
Click to expand...
Click to collapse
First backup your data after backup flashing last version

https://play.google.com/store/apps/details?id=zanini.andrea.notchtest
use this. no need to wait.

Bootloop?
My phone doesn‘t boot anymore. It is trying to but after a while seeing the bootanimation it restarts into twrp... I didn‘t backup my system. Is everything away now? Also tried installing the disable zip. Problem still there. I think I need to install the rom again with MiFlash

EEA Global v10.3.8.0 to v10.3.10.0 through TWRP [MI 9T] (SOLVED)

Hello guys,
I'm searching (as the title said) someone that is in my same situation. I'm currently running the MIUI Global on Mi 9T with twrp + magisk. I'd like to update it safely but I don't know how to do. I tried to flash the rom zip through the twrp but it gives me the error "zip file is corrupt". I hope I will found someone to collaborate with.
I think the best things to do are:
- Unistall Magisk from twrp
- Reflash the original recovery through twrp
- Update MIUI Global
- Reflash TWRP and Install magisk
The possible issue is at the first step: if we unistall Magisk we could be stuck into bootloop and then we cannot do anything to restore our phone.
Another possible solution is to flash the fastboot rom through MiFlash but it is still not out and I don't know if it will ever be.
EDIT: I found how to correctly update the device. If anyone is in my same situation, just follow these steps
- Download the rom link from here
- Go to twrp and flash it (don't reboot yet)
- Go back and flash magisk
- Reboot

can you explain steps how you tried to flash by twrp?

slavke1976 said:
can you explain steps how you tried to flash by twrp?
Click to expand...
Click to collapse
Sure, I just downloaded the rom zip through the official updater and then I tried to flash it through twrp
Update: ok, the zip was really damaged. Now I installed it through an external source. How I can safely update now?

now you install which rom? eea or global?

slavke1976 said:
now you install which rom? eea or global?
Click to expand...
Click to collapse
EEA. A developer of my old device suggested me to do this:
- Flash the rom zip
- Flash magisk (since it should disable dmverity to keep the twrp)
- Reboot
But I repeat: I'm scared like crazy because if I go into bootloop my phone will be out since a new fastboot rom will be out.
What's your opinion about this? Should I try anyway?

Before foashing new rom ununstal magisk by twrp. After all should work well
Sent from my Redmi K20 using Tapatalk

I have read of some cases of bootloop after magisk unistall

pfornaro said:
EEA. A developer of my old device suggested me to do this:
- Flash the rom zip
- Flash magisk (since it should disable dmverity to keep the twrp)
- Reboot
But I repeat: I'm scared like crazy because if I go into bootloop my phone will be out since a new fastboot rom will be out.
What's your opinion about this? Should I try anyway?
Click to expand...
Click to collapse
https://xiaomifirmwareupdater.com/miui/
Here fastboot rom.
Im in same position, don't know what to do

Gregor250385 said:
https://xiaomifirmwareupdater.com/miui/
Here fastboot rom.
Im in same position, don't know what to do
Click to expand...
Click to collapse
I succesfully updated it bro, just do these steps:
- Download the rom link from here
- Go to twrp and flash it (don't reboot yet)
- Go back and flash magisk
- Reboot
You are done

pfornaro said:
I succesfully updated it bro, just do these steps:
- Download the rom link from here
- Go to twrp and flash it (don't reboot yet)
- Go back and flash magisk
- Reboot
You are done
Click to expand...
Click to collapse
Yes, it worked, thank you :good:

How to update miui official??

I have unlocked bootloader, and I have twrp and magisk
Please tell me how to update, I've received the notification but I don't know how is the process to update on this situation

Well, if the classic way doesn't work, you can try this :
https://c.mi.com/thread-1890305-1-0.html
And if still not, well this way (but with the correct files for your device !!) :
https://www.androidcentral.com/how-download-and-install-miui-9-redmi-note-4

21vm said:
Well, if the classic way doesn't work, you can try this :
https://c.mi.com/thread-1890305-1-0.html
And if still not, well this way (but with the correct files for your device !!) :
https://www.androidcentral.com/how-download-and-install-miui-9-redmi-note-4
Click to expand...
Click to collapse
Thanks man

When I bought my phone 2 weeks ago (global version) I was notified of the 10.3.6 update, I hope it is ready when I arrive or can I install the latest package?

Were you able to flash it with TWRP? Or how did you do it?

How were you able to update?

sonrics1993 said:
I have unlocked bootloader, and I have twrp and magisk
Please tell me how to update, I've received the notification but I don't know how is the process to update on this situation
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
1) download the full recovery rom for your device from here https://xiaomifirmwareupdater.com/miui/
2) reboot to recovery
3) wipe dalvik art/cache and cache
4) flash the rom and magisk (don't reboot to system until you've flashed magisk)
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip

darhma said:
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
1) download the full recovery rom for your device from here https://xiaomifirmwareupdater.com/miui/
2) reboot to recovery
3) wipe dalvik art/cache and cache
4) flash the rom and magisk (don't reboot to system until you've flashed magisk)
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
I’m on stock rom, MIUI Global 12.0.2, rooted with Magisk 21.4 and Orangefox recovery. Now there is an update to MIUI 12.0.3.
I’m not sure what to do. When I go to https://xiaomifirmwareupdater.com/miui/ there is no recovery to 12.0.3. I can only find firmware 12.0.3. Can I still use this solution with firmware type?

svendsvin said:
I’m on stock rom, MIUI Global 12.0.2, rooted with Magisk 21.4 and Orangefox recovery. Now there is an update to MIUI 12.0.3.
I’m not sure what to do. When I go to https://xiaomifirmwareupdater.com/miui/ there is no recovery to 12.0.3. I can only find firmware 12.0.3. Can I still use this solution with firmware type?
Click to expand...
Click to collapse
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
There is the last 12.0.3!?

EDIT, Sorry wrong thread! I have far too many chrome tabs open

joke19 said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
There is the last 12.0.3!?
Click to expand...
Click to collapse
I'm sorry I only see V12.0.1.0.QFGMIXM for Redmi Note 7 Global.

joke19 said:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
There is the last 12.0.3!?
Click to expand...
Click to collapse
I’m rather confused. When I go to About phone it says my MIUI version is Miui Global 12.0.2 stable (QFGEUXM). But the EEA version in your link has the same number: QFGEUXM. Does that mean I can use the Redmi Note 7 EEA Stable Recovery V12.0.3.0. (QFGEUXM)?
Edit: I can see when I click Download the Package Name includes "Global". So I guess it is usable? But then do I choose the Incremental Update or must I download Full ROM (.zip)?
Edit2: Just an update in case anyone should have the same question. I flashed the EEA version without problems. And I downloaded the Full ROM.

darhma said:
Look here: https://forum.xda-developers.com/redmi-note-7/help/ota-update-unlocked-rooted-device-t3963409
1) download the full recovery rom for your device from here https://xiaomifirmwareupdater.com/miui/
2) reboot to recovery
3) wipe dalvik art/cache and cache
4) flash the rom and magisk (don't reboot to system until you've flashed magisk)
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Is this guide still legit after Magisk 22?

svendsvin said:
Is this guide still legit after Magisk 22?
Click to expand...
Click to collapse
I'm not 100% sure because I don't use MIUI, but I think it's still good, what makes you think it's not good anymore? I don't think there have been any particular changes in how MIUI or magisk works that would make it obsolete

darhma said:
I'm not 100% sure because I don't use MIUI, but I think it's still good, what makes you think it's not good anymore? I don't think there have been any particular changes in how MIUI or magisk works that would make it obsolete
Click to expand...
Click to collapse
Mainly because of the installation guide - https://topjohnwu.github.io/Magisk/install.html#custom-recovery - and Lavender's missing ramdisk. But I'm not sure and therefor I ask.

svendsvin said:
Mainly because of the installation guide - https://topjohnwu.github.io/Magisk/install.html#custom-recovery - and Lavender's missing ramdisk. But I'm not sure and therefor I ask.
Click to expand...
Click to collapse
I'm on official lineageos 17.1 and yesterday I've updated magisk to version 22, then updated the rom without problems. But I've updated magisk from magisk app not from recovery, so I'm not sure that installing magisk from recovery still works in rn7. Anyway after the rom update, magisk still works correctly. Maybe it's better to ask on the magisk thread: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/

svendsvin said:
Mainly because of the installation guide - https://topjohnwu.github.io/Magisk/install.html#custom-recovery - and Lavender's missing ramdisk. But I'm not sure and therefor I ask.
Click to expand...
Click to collapse
FYI there could be a bug in Magisk 22 regarding missing ramdisk in Xiaomi: https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84557999

Status of TWRP with Android 10 on Mi 9T

Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!

Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^

Micdu70 said:
Hi!
"TWRP constantly being replaced with the stock recovery"
=> That's nothing to do about Android version: It's a Xiaomi/MIUI boot protection feature. Some TWRP flash a modified VBMeta image, at first TWRP boot, to disable this protection.
- What you can do:
1) Download latest OrangeFox and put ZIP file in phone storage
2) Download latest Official TWRP, flash it via fastboot then hold "Power" and "Vol+" buttons (both) until TWRP is booted
3) Select OrangeFox ZIP file in TWRP and flash it (phone will automatically restart to OrangeFox Recovery).
4) Done! You can now flash latest Magisk version. ^^
Click to expand...
Click to collapse
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!

Annie the Eagle said:
Hey there. Thanks for this. Do I need to flash the VBMeta file also when I follow this? Would you mind sending a link to the latest official stuff, just wanna make sure I got the right things!
Click to expand...
Click to collapse
You normally don't need to flash VBMeta file.
- Official TWRP => https://dl.twrp.me/davinci/
- Latest OrangeFox (actually "R10.1_1" because "R10.1_2" is a broken version) => https://files.orangefox.tech/OrangeFox-Stable/davinci/
EDIT: Flash "R10.1_1" version over bad "R10.1_2" version if you already downloaded/flashed via my previous MEGA link.

Annie the Eagle said:
Hey
So my bootloader unlock wait time is coming up tomorrow, but this forum is not giving me much hope as all I can see is problems with TWRP constantly being replaced with the stock recovery and general incompatibility (recovery loops or bootloader loops), no one seems to know which of the 10,000 versions of TWRP and OrangeFox (????) recovery to use.
Can anyone clarify what the situation is with Xiaomi Mi 9T or is this phone doomed and its just worth throwing on eBay (a phone without custom recovery and root is absolutely worthless to me).
Thanks a plenty!
Click to expand...
Click to collapse
Sorry but this is not teally true - or maybe it's the case for custom roms and/or custom twrps
Using (not alone, you can find several peopke reporting the same):
-QFJEUXM 11m0.4.0 (Global, Stable,v Android 10)
-Official TWRP 3.3.1-0-davinci
Just flash that twrp through fastboot, do not wipe or fornat anything (vbmeta, internal storage, whatever), you will not loose anything and everything will work
And the same holds if twrp is replaced by orangefox (since recently, using R10.1_2)
Eg, when booting to twrp, you will enter your pin/password you use in system for unlocking the screen - and twrp will recognize and work with your encrypted Internal memory (so again, without formatting data, wiping vbmeta or whatever)
However, if you want to use some custom roms whose installation requires to format or wipe something, and/ot to use some custom twrps, that's another story (but not a problem in miui or in the official twrp)

Guide to flash realmeUI 2.0 beta builds [Global Variant Only]

DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DO​The only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery

reserved

Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA

Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader

bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work

ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you

What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?

kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.

It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""

Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.

Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance

4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?

Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.

kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too

How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?

Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?

Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks

Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks

tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me

So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again