Database Users

Root RedmI Note 3 snapdradon MIUI 8 6.9.9 developer rom (marshmallow)

Since, the release of the Android M. Google make it hard to root your device. On MIUI 8 with marshmallow I have been trying to figure out a way to root my device. In almost every case I found myself in a boot loop. So after a long work i finally succeed to root my redmi note 3 with no error and bootloop.
I am not responsible for any damage to your devices,loss or damage caused, or alleged to have been caused, directly or indirectly, by the informations or ideas suggested or referenced, etc. If you get a boot loop you can get back to booting by simply flashing the stock "M" system image via fastboot. or Mi flash tool.
Please try at your own risk. Your warranty is now void.
PRE-REQUIREMENTS
1. redmi note 3 ( SD only) with official MiUI 8 6.9.9 developers rom (marshmallow update) :good:
2. officially unlocked bootloader.
3. TWRP recovery ( alka twrp recommended ).
4. patched boot image given below.
5.brain
METHOD RECOVERY METHOD.
1. Download boot.zip and SuperSu.zip
superSu.zip -https://www.androidfilehost.com/?fid=24727369092694142
boot.img - https://www.androidfilehost.com/?fid=24727369092694141
2. copy both the files (boot.img and SuperSu.zip) to your external SD card.
3. now reboot the device in recovery and go to mount section and mount all the partitions.
4. now go to install and go to SD card and flash SuperSu.zip.
5. as the super su is installed go back in install section and select install image.
6. now you will see only .img files so locate to boot.img and select it.
7. In next window you may see two option as " select partition to flash image:" select the first one option BOOT partition and slide the installation slider and reboot your redmi note 3 SD
boot up may take 5-10 mins so don't we panic. and please mention in the comment was it worked for you or not so I can edit boot image for you..
if i help you give me a thanks, by clicking on thanks button

I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?

Just flash supersu stable using ZCX twrp. Head over supersu xda thread for latest stable flashable zip. Worked for me without any issue.

ubaid137 said:
I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?
Click to expand...
Click to collapse
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks

tsrajput said:
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks
Click to expand...
Click to collapse
Also my wifi is not working after root..

Does AUX issue resolved in this ROM?
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.

Satav said:
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.
Click to expand...
Click to collapse
This is not a rom, its a rooting guide.

any news on this ? any new boot.img. I'm on 6.9.22 beta. thanks

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)

Downgrade From Android 10 to Android 9 is working now

Android 10 downgrade.
now the tools are available in realme website to unlock the bootloader...
install deep testing apk and unlocking the boot loader with the android 10 ( procuder will be found in realme website)
After the bootloader is unlocked......follow the procedure below..
second reboot to bootloader and flash the twrp recovery
and reboot using fastboot command itself
it will go straight to twrp recovery mode.
just give wipe data function which is default...
then flash the android 9 ozip , after that dont reboot to system
go back and flash the stock recovery from android 9 which is attached with this post and then reboot..
now you are back to android 9.
this method is working for me ..
after sitting many hours with stucked twrp recovery i just flashed the stock recovery and it get in to the device
Please read whats the state of my realme x2 pro so that you can understand what I have done.
I purchased the realme x2 pro 12gb/256 in the uk , it is shipped with the android 9, there was some OTA update and I had done that and the phone was still in Android 9 with some bugs fixed. Again I recheked the software update for Realme ui update but nothing was found.
So I headed to realme uk website and downloaded the Android 10 realme ui ozip , copied to the phone and updated. Now the phone was in android 10 with realme ui.
The software update is good but I don’t like the finger print animation and also I noticed a sight battery drain,but I am not sure if it was same like in android 9 , I mean the batter life. So decided to go back android 9 . so after so many tries and all finally downgraded to android 9 with the bootloader locked and widevine to L1 and google pay working. Now all stock and all finger print this and that working !!!
Downgrade procudure :-
Backup All the things that are required, All will be wiped.
1.First thing is to unlock the bootloader in Android 10 because of I updated to android 10.
Follow this link below , download the deep testing apk and unlock the bootloader.
https://c.realme.com/in/post-details/1253651898825703424
2.Make sure you all had the proper working adb drivers in pc and android bootloader drivers,
After completing the 1st step , Download the twrp from the link below:
I downloaded the one in this name TWRP 3.3.1-13 Unofficial by mauronofrio
https://forum.xda-developers.com/re...covery-unofficial-twrp-realme-x2-pro-t3997879.
How to flash twrp in realme x2 pro follow this guide below:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
follow the procedure above and until flashing recovery and don’t flash vbmeta and all
3. Download the Android 9 firmware with stock recovery , this was the lastest one I dowloaded from xda
(https://forum.xda-developers.com/realme-x2-pro/how-to/rmx1931ex11a-10-available-t4059607)
4.Downloading stock recovery :
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download
download this zip file and use only the recovery.img after unzip , this is the only file we need from this folder
Second part:
I Assume the bootloader is unlocked , the device wiped and rebooted to os , copy the ozip in the and stock recovery in internal memory, we might need to use this for later.
now flash the twrp using the guide above and reboot to twrp recovery.
In twrp install the android 9 ozip that we downloaded in the phone memory , after it flashed don’t reboot.just go back and flash the (recovery.img) from twrp itself and choose the path recovery and flash , after that the phone will reboot and it will go to stock recovery. Then give a wipe in the stock recovery and reboot. Now you are back to stock android 9.
Now we are in android 9 with the unlocked bootloader. That’s all.
For those who needs to lock the bootloader read the information below
Check the stock recovery version number ( if it shows rooted near the version number) if it says rooted don’t relock the bootloader. From the phone just run stock ozip again and let it boot in to os, after that again check the stock recovery if rooted string is gone. If it is gone now you are good to lock the bootloader.
Because with unlocked bootloader the google pay is not working so for me locking the bootloder is important for me , also I checked in the device info that widevine is change back to L1.
dont lock bootloader with twrp recovery

where can i get in depth test for global version ?
and did i lose the fingerprint after unlocking bootloader?

Where is the stock recovery that you attached? Can u show step by step with more detail explaination?

rhazes305 said:
Where is the stock recovery that you attached? Can u show step by step with more detail explaination?
Click to expand...
Click to collapse
Hi,
from this link i had downloaded the stock recovery of android 9, it is 54 mb zip file , after you unzip use only recovery.img
i will post properly the procedure..
https://forum.xda-developers.com/realme-x2-pro/how-to/boot-stock-recovery-boot-t4003971
download link :
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download

arthajudeenuk said:
Android 10 downgrade.
now the tools are available in realme website to unlock the bootloader...
install deep testing apk and unlocking the boot loader with the android 10 ( procuder will be found in realme website)
After the bootloader is unlocked......follow the procedure below..
second reboot to bootloader and flash the twrp recovery
and reboot using fastboot command itself
it will go straight to twrp recovery mode.
just give wipe data function which is default...
then flash the android 9 ozip , after that dont reboot to system
go back and flash the stock recovery from android 9 which is attached with this post and then reboot..
now you are back to android 9.
this method is working for me ..
after sitting many hours with stucked twrp recovery i just flashed the stock recovery and it get in to the device
Click to expand...
Click to collapse
Thanks, but I would also like a more detail explanation of the steps. Where to download the deep testing apk? And will fingerprint also work after unlocking bootloader?

rhazes305 said:
Where is the stock recovery that you attached? Can u show step by step with more detail explaination?
Click to expand...
Click to collapse
nightzun said:
Thanks, but I would also like a more detail explanation of the steps. Where to download the deep testing apk? And will fingerprint also work after unlocking bootloader?
Click to expand...
Click to collapse
Hi mate,
i typing the procedure in word document now and upload soon, afte unlocking the bootloader in android 10 the fingerprint is working good , it didnt affect the fingerprint because the realme didnt block it in this update.

you are the best! thanx
** sadly i cannot unlock bl coz i got error " This is carrier-customized phone" on deep testing apk.
I would appreciate it if anyone would help me to solve this problem

Is there something wrong with Android 10?
Or why downgrade to 9?

Yerry said:
Is there something wrong with Android 10?
Or why downgrade to 9?
Click to expand...
Click to collapse
- More battery long lasting on A9, perhaps more services are running in A10 rising power consumption or not well updated.
- In early versions of A10 call recording was capped due privacy rights. With the last update C.26 I can record calls but not tag the records accesing to the contacts list.
- Also in the last C.26 update of A10, you can take RAW photos in 'expert mode'.

pr0orz1337 said:
- More battery long lasting on A9, perhaps more services are running in A10 rising power consumption or not well updated.
- In early versions of A10 call recording was capped due privacy rights. With the last update C.26 I can record calls but not tag the records accesing to the contacts list.
- Also in the last C.26 update of A10, you can take RAW photos in 'expert mode'.
Click to expand...
Click to collapse
Thank you for the info.
Just upgraded, first there was an odd connectivity issue, every GPS fix loss, deactivated mobile and WiIfi for 5 seconds
After turning Smart power savings mode off and on, the issue disappeared.
About raw mode: Odd raw mode that does not save in 64 MPix

arthajudeenuk said:
Android 10 downgrade.
Check the stock recovery version number ( if it shows rooted near the version number) if it says rooted don’t relock the bootloader. From the phone just run stock ozip again and let it boot in to os, after that again check the stock recovery if rooted string is gone. If it is gone now you are good to lock the bootloader.
Because with unlocked bootloader the google pay is not working so for me locking the bootloder is important for me , also I checked in the device info that widevine is change back to L1.
dont lock bootloader with twrp recovery
Click to expand...
Click to collapse
It is possible after lock bootloader,unlock one more time?

The links on step 3 are not correct.
Can you update the post?

Yerry said:
The links on step 3 are not correct.
Can you update the post?
Click to expand...
Click to collapse
Updated ...please download from the XDA page link , downoad the firmware with stock recovery.

Thanks bro...i downgraded to color os and now it ia running smoothly..

This method works with RMX1931 (CN version)? Because i see that the recovery used in the op is for RMX1931EX

Thanks for ur help But is there a way to get a stock recovery for Chinese version ?

Are you sure that we don't have to flash vbmeta.img.because somewhere i have read that if i don't flash vbmeta my phone will be dead

will still working on CN Rom based devices?

Even after installing the ozip from phone my recovery says rooted! Anyway to change that or remove the root?

[RECOVERY][3.4.0-14][toco]Unofficial TWRP Xiaomi Mi Note 10 Lite (TEST)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-13 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_toco
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-05-29

Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!

Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you

Did anyone boot it?
hello, work boot it?
fastboot boot twrp.XXXX.img

StanGumn said:
hello, work boot it?
fastboot boot twrp.XXXX.img
Click to expand...
Click to collapse
Yes

iron maiden said:
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Click to expand...
Click to collapse
Let us hope so.

I would like to apologize in advance as I am a noob when it comes to the recent changes made by Google to android. So on a lot of the recent devices launched with android 10, an essential step before flashing Magisk is to disable the vbmeta partition by flashing the "vbmeta.img" using a fastboot command with the --disable-verify and --disable-verification argument. My question is that is the "vbmeta.img" modified by developers or is this the same identical file found in the stock firmware files?
I do apologize if this is the wrong thread but there's not many resources online or even on xda for this device.

Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.

Reanimax said:
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Click to expand...
Click to collapse
ask to xda to make a dedicated section and i will ask to move this thread

mauronofrio said:
ask to xda to make a dedicated section and i will ask to move this thread
Click to expand...
Click to collapse
Yes. You right about it.

Kediraksith said:
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Click to expand...
Click to collapse
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
Update: 5/16/2020
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY. ***This is only if OP asks to flash VBMETA PATCHER, otherwise skip to Step 5***
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM. ?
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.

Wmateria said:
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY.
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM.
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Click to expand...
Click to collapse
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!

cerme said:
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
Click to expand...
Click to collapse
The root and flash process is basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.

Wmateria said:
The root and flash process is basically basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Click to expand...
Click to collapse
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties

cerme said:
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
Click to expand...
Click to collapse
Same here, i was on the Mi 9T before, I didnt understood the whole new flashing process and carefully updating from EU Rom to AOSP Roms and back, I think i was messing with with thwe wipe and change partition feature (f2fs to ext 4 with an EU Rom) - then the Mi 9T bricked big time. Never recovered after that, luckily got it refunded for it but not many may have that second chance. After learning how to flash propeely and root, ect. I try to help out here when needed and ask too. I just got my Mi Note 10 2 weeks ago and rooted a week ago. So if anything, am willing to help out and repeat the following flash process or any changes in the future and feedback on future Roms.

Was thinking about which rom to use... does xiaomi.eu is stille faster with providing updates? what about the situation with OTA with that.
Now I have the phone with global rom, I want at least flash the EEA rom. But I also know that at some point i want to root, install magisk and get nice features. Still don't want to update manually everytime for an update...

will be watching this thread with much interest..
I recently bought this device (Global version) for use here in Australia.
my first time owning a Xiaomi - quite happy with it so far.
would be nice to have the themeing stuff work properly - I have used MIUI based ROMs back a LOoonggg time ago, in the days of the Nexus S and Galaxy Nexus etc.
used to have a new ROM flashed every couple of days lol, back then. But recent years I've stopped all that, no cool ROMs no snazzy kernels TWRP no nothing not even root lol, very boring!
anyway thanks for posting I hope to try this sometime soon

Hello is there any Eu rom for Mi note 10 lite?

Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
yes, there is the EEA ROM you can find on miui website. You can flash it after unlocking bootloader with miFlash

Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
I'm not sure if you mean the official ROM or xiaomi.eu.
The link to the official EEA(EU) ROM:
Recovery: https://bigota.d.miui.com/V11.0.7.0.QFNEUXM/miui_TOCOEEAGlobal_V11.0.7.0.QFNEUXM_7926bf9c02_10.0.zip
Fastboot: https://bigota.d.miui.com/V11.0.7.0...EUXM_20200508.0000.00_10.0_eea_4eb1c694c9.tgz
I have yesterday seen a xiaomi.eu Stable build for toco which is based on Global Stable ROM:
https://sourceforge.net/projects/xi...e10LITE_V11.0.4.0.QFNMIXM_v11-10.zip/download
I can not promise that it's working.

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