Database Develop

XiAOMI MI MAX 2 Official ROM Root twrp

So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-

Thank you! TWRP worked as intended, installed root manually. Donated as well.

TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..

Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864

Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.

noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.

XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?

Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.

XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again

Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse

unlock with developer rom

XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..

yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock

Magisk not detect root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks

Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?

How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )

I'm facing problem when I'm trying to update my K20 Pro Chinese device.

My phone was better before unlocking bootloader. But after unlocking the bootloader I'm facing updating problem. Please see the screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me to solve this

L1mon said:
My phone was better before unlocking bootloader. But after unlocking the bootloader I'm facing updating problem. Please see the screenshot below.
Please help me to solve this
Click to expand...
Click to collapse
No screenshot is visible. Unlocked Bootloader does not prevent OTA, but if you installed a custom Recovery (e.g., TWRP or OrangeFox) OTA will fail (when phone reboots, it looks for stock Recovery to process OTA package)
And/or, if you installed Magisk (or custom Kernel), you need to force Full OTA package (2,4 GB or so) from System Update, Settings - because default incremental OTA lacks full Boot image and cannot update Boot from your custom Boot (Magisk or custom Kernel affect Boot)
Hence if you want to update by OTA, revert Boot and Recovery to stock before you go

zgfg said:
No screenshot is visible. Unlocked Bootloader does not prevent OTA, but if you installed a custom Recovery (e.g., TWRP or OrangeFox) OTA will fail (when phone reboots, it looks for stock Recovery to process OTA package)
And/or, if you installed Magisk (or custom Kernel), you need to force Full OTA package (2,4 GB or so) from System Update, Settings - because default incremental OTA lacks full Boot image and cannot update Boot from your custom Boot (Magisk or custom Kernel affect Boot)
Hence if you want to update by OTA, revert Boot and Recovery to stock before you go
Click to expand...
Click to collapse
I've installed magisk but i uninstalled that also I flash stock rom from orange fox.
But same thing happening.

L1mon said:
I've installed magisk but i uninstalled that also I flash stock rom from orange fox.
But same thing happening.
Click to expand...
Click to collapse
I answered you in the previous post that for OTA you must not have OrangeFox - you must reflash stock Recovery before you go for OTA

Development Redmi note 10 5G TWRP-recovery 3.5.2 android 11

This is TWRP that I compiled. I tested it myself. It works on this version, but the touch screen doesn't work
The decryption function is there, but it doesn't work properly, entering the correct password can't decrypt it, I hope someone fixes it
version:V12.0.6.0.RKSCNXM
android:11
Download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This device tree, I referred to github
@mastersenpai05
This is my modified device tree
github @xxroot/twrp_camellia
flash :
fastboot flash boot boot.img
fastboot reboot recovery

Can i flash magisk with it?is backup working?Can i restore?

g465559090 said:
This is TWRP that I compiled. I tested it myself. It works on this version, but the touch screen doesn't work
The decryption function is there, but it doesn't work properly, entering the correct password can't decrypt it, I hope someone fixes it
version:V12.0.6.0.RKSCNXM
android:11
Download
View attachment 5463601
This device tree, I referred to github
@mastersenpai05
This is my modified device tree
github @xxroot/twrp_camellia
flash :
fastboot flash boot boot.img
fastboot reboot recovery
Click to expand...
Click to collapse
Why english is not working?And why I can't boot the phone?It only boots on twrp i cant boot my phone pls help

i think working only for global 12.0.6.0 dont flash on miui 12.5

wetito said:
i think working only for global 12.0.6.0 dont flash on miui 12.5
Click to expand...
Click to collapse
I tried its working but i can't boot to android,maybe flashing it to recovery partition can fix it

As I understand it, because there's no recovery partition, after using TWRP you need to boot back into fastboot and flash your normal boot image to be able to boot to Android.

skm_1 said:
As I understand it, because there's no recovery partition, after using TWRP you need to boot back into fastboot and flash your normal boot image to be able to boot to Android.
Click to expand...
Click to collapse
This phone does not have a Recovery partition. Its boot partition is integrated with Recovery, so if you have to swipe back to the official boot.img to boot android. If you want TWRP and Android to work, you'll need to modify boot.img

how do i back to mi recovery? Cause the recovery.img is not there with the rom fastboot type

Can't we have any developer? For this device...? It sucks.... Every other redmi phones have twrp and roms.. but not this one.

Question Cant wipe system in TWRP

I have been using crdroid on my redmi note 10 for a couple months, I've just tried to update but I have ended up getting stuck at the crdroid logo on boot every time after trying to reinstall flame gapps. When I go to wipe in TWRP there is no option to wipe the system.. how can I wipe the phone to clean flash crdroid? or is there a way I can uninstall the flamegapps zip in twrp? I used another gapps in the past that allowed to to uninstall by renaming the zip to uninstall, but that doesn't seem to work with flame gapps.

itsfatso said:
I have been using crdroid on my redmi note 10 for a couple months, I've just tried to update but I have ended up getting stuck at the crdroid logo on boot every time after trying to reinstall flame gapps. When I go to wipe in TWRP there is no option to wipe the system.. how can I wipe the phone to clean flash crdroid? or is there a way I can uninstall the flamegapps zip in twrp? I used another gapps in the past that allowed to to uninstall by renaming the zip to uninstall, but that doesn't seem to work with flame gapps.
Click to expand...
Click to collapse
Wipe/format data(yes)/reboot twrp.

NOSS8 said:
Wipe/format data(yes)/reboot twrp.
Click to expand...
Click to collapse
This doesnt help. In the wipe menu there is no option for storage. which is why i'm having problems

itsfatso said:
This doesnt help. In the wipe menu there is no option for storage. which is why i'm having problems
Click to expand...
Click to collapse
isn't there that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yes I can format data but it doesn't change anything.. I have formatted then rebooted countless times but the rom doesn't get cleared from the phone, if I boot into system it goes back to being stuck at the crdroid logo

It's good practice to make a full twrp backup of your device before installing zips like gapps or installing stuff like magisk. Any change to your system or boot partition can result in a bootloop so back these up at least.

itsfatso said:
yes I can format data but it doesn't change anything.. I have formatted then rebooted countless times but the rom doesn't get cleared from the phone, if I boot into system it goes back to being stuck at the crdroid logo
Click to expand...
Click to collapse
Also check that you are using the correct TWRP/O.F.https://androidfilehost.com/?w=files&flid=321666
A12/A11
Start from zero
flash firmware recommended by O.P or complete rom** without re-lock the bootloader(**best solution).
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

Should I update to Magisk 25.2 after flashing 24.3

According to this thread: https://forum.xda-developers.com/t/...1-legendarypixieos-4-1-for-galaxy-m21.4379385
Flashing 25.x with that certain rom bootloops, and I have that version of Magisk flashed and installed to my device, but the app is bothering me to download the latest version of it.
Should I continue? Since this is after the fact?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Magisk stopped patching avb and some other stuff since 25.0 so some roms and kernels that need it wont work anymore. But if you already had v24 installed everything should be already patched. I've noticed that if you're only flashing v25*, flashing dmverity disabler along with it fixes bootloops.
So in theory it should be okay if you already have magisk installed. However, dont forget to take a backup of your boot before doing anything.

Alright, I'll update the thread if everything goes well.
Thank you!

Whelp, it is bootlooping with no access to twrp and shutdown.
I'll try to turn it off by removing the battery and reflashing back the working 24.3.
Note to future-self:
You can uninstall the newer magisk version by renaming the APK of the version you updated to by renaming it to `uninstall.zip` and flashing it.
You can also get an infinitely bootlooping device to odin mode by holding the power up and down keys while being connected to a computer when the boot cycle starts.

I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.

newt23 said:
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
Click to expand...
Click to collapse
Greetings Friend,
Can you attach the Dmverity Disabler zip?

OldNoobOne said:
Greetings Friend,
Can you attach the Dmverity Disabler zip?
Click to expand...
Click to collapse

Greetings Friend newt23,
Can you also elaborate on the exact steps you did to get the GSI to boot.
I mean steps like which GSI booted? & did you put the GSI in sdcard then use terminal commands like- { mount partition system, cd documents, super flash system.img etc., did you use chodoe flasher, gapps }?
Thanks in advance.
Also, Magisk 26.1 seemed more stable on stock rom without the addon.d script ability on stock but some devs insisting on staying with 24.3 stable even though 26.1 has better SafetyNet but. What would be your advice?