Database Info

Root Huawei Mate 20

Hi,
I'm looking for a solution to root Huawei Mate 20. I couldn't find much on web search about this topic.
I am also not able to find a way to install TWRP or unlock boot loader.
Any ideas?
Sent from my HMA-L29 using Tapatalk

My phone got an update about a week ago. The details didn't mention Anything about boot loader unlocking but when I checked after the update, there was the ability to unlock the bootloader.
I have already opened the developed settings since november but the bootloader unlock option was greyed out and could not be turned on. I read a post from a different thread that his phone recently got an update with the option to turn on the bootloader unlock option. I have been regularly checking for update since I read that post and so last week I finally got it. I am now able to toggle the switch but I did not finish the process because I want to make sure it doesn't cause any warranty issues. I have been a Samsung user and I am very familia with the "warranty void 0x1" issue so I always waited until my warranty was over before rooting my phone. That way everythung has been tried and tested before I take a leap. If you do get the update please post your experience in unlocking the bootloader and eventually rooting your phone.
Sent from my HMA-L29 using Tapatalk

Maybe try kingroot? If it gets the job done on the pro version it might do it here as well.
Found it: https://www.techdroidtips.com/install-custom-rom-huawei-mate-20-cwm-twrp/ https://www.techdroidtips.com/root-huawei-mate-20/

patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards

Hi please create a new thread how to root the phoneee?

Oem unlock is back :cyclops:

Hi, I can't find Twrp for huwaei Mate 20 can you help me?
Wysłane z mojego HMA-L09 przy użyciu Tapatalka

OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Mate please help us.
EDIT:
sorry, now found your post: https://forum.xda-developers.com/mate-20/how-to/guide-manual-updating-firmware-t3892686
so only way to get root it's paying for bootloader code?

OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?

JazonX said:
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
Click to expand...
Click to collapse
nope, my international mate 20 didn't receive 9.1 yet.
Regards

There is info about root EMUI 9.1 for mate 20X on XDA. "[GUIDE] Root AL00 EMUI 9.1"- https://forum.xda-developers.com/mate-20-x/how-to/guide-root-al00-emui-9-1-t3938483. You need Ramdisk for your device and patche it. Also it is possible to extract Ramdisk from full firmware. Now i have a problem to download full firmware for my phone - HMA-L29 9.1.0.310(C10E10R2P1). I tried https://support.halabtech.com/index.php?a=downloads&b=folder&id=35991 but it is impossible to download zip file. Is there another way to get this firmware?

Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6

ZTNL said:
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
Click to expand...
Click to collapse
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.

Need Unlocked Bootloader?
vstrglv said:
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Click to expand...
Click to collapse
Could you give a short tutorial of how you did that? Did you have to unlock bootloader?

I guess that unlocked bootloader is required to flash boot image, but I hope to be wrong

Yes, I have unlocked bootloader.

vstrglv said:
Yes, I have unlocked bootloader.
Click to expand...
Click to collapse
Where did you get the bootloader unlock codes? HW no longer support to release it...

I got unlock code on this forum from Crys18 on 30.03.2019 for $6.

Root on EMUI 10
Has anyone rooted the new EMUI 10? Can you give me a how to?

vstrglv said:
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Click to expand...
Click to collapse
How can I contact him?

unable to install twrp over 3.1.1.1 on mi4c (trying to go from android 7.1 to 8 or 9)

Hey everyone,
i usually don't post questions but i've been on pretty much every forum the web has to offer and am still stuck so i'll try my luck here.
i'm currently running lineage 7.1 on my mi4c, i've used another phone for a while but now that my mi4c has a new battery i wanted to start using it again, is also decided this would be the time to update it to android oreo or pie, this however seems to be impossible.
i can only use twrp up to 3.1.1.1, all higher (and unofficial versions) will not boot via fastboot 'dtb not found' or when flashed via older twrp will freeze on boot screen.
whenever i try to install a new rom it tells me 'error code 7', when i remove the 'assert' lines in the update it gives me 'error code 6'
my device is unlocked, i have checked this in fastboot.
do i have to install miui again before installing another rom? do i have to go back to the standard recovery? i'm currently running out of ideas and hope you guys might be able to help me. maybe i'm overlooking something simple.
kind regards,
Monstreys

Hi! I don't know if this is a coincidence or not, but I was about to start a similar thread.
I try to do exactly what you are doing. I want to install LineageOS 16, unofficial ROM.
For this you need a newer TWRP, like 3.2.3.0, but it doesn't work 'dtb not found' like you said. I found out that this doesn't work because you need to have nougat bootloader. Most probably you have lollipop bootloader like I have, and thats why newer versions of TWRP are not working. I think the only way to update your bootloader to a nougat one is to flash the latest MIUI ROM. But, unfortunately, when you do that the bootloader gets locked, and I can't unlock it via MiUnlock due to Error:20091 when I try to link the phone to the Mi account. In MiUnlock it gives me the "this account cannot unlock the phone" or something like that.
Now I removed the "assert" lines from my rom and flashed it without the error 7 or 6. Some error still apears, but it also apears when I flash LineageOS 14.1, and that version is working even with those 2 errors I can't remember during flash.
After I flashed LineageOS, I flashed gapps and then superSU, and now my mi4c is stuck on mi logo for about 20 minutes, and I think it will remain that way.
So, there are 2 things we need to solve. We need to find a way to install latest MIUI without relocking the bootloader because I can't unlock it via MiUnlock, or to find out why after I flashed LineageOS 16 it gets stuck on MI logo.

I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
i
i was unable to install the patch file, this nonetheless fixed my problem, thanks!!

if above not working, another method to do it based on my method.
https://forum.xda-developers.com/showpost.php?p=81573941&postcount=199

makaveli97 said:
I think I found the solution. Do exactly what this guy is doing here and it might work.
https://forum.xda-developers.com/showpost.php?p=78640737&postcount=63
I followed that guy instructions and I managed to install TWRP 3.2.3.0 and LineageOS 16, and it booted. Now I am at the setup part but it has very big lag...
Click to expand...
Click to collapse
My MI4C has been successfully flushed into lineage-17.1-20200220-UNOFFICIAL-libra.zip. It has been updated on TWRP 3.1.1 and keeps reporting error 7, and then abandoned TWRP3.1.1 and flashed into OrangeFox-R10.0-1-Stable-libra.zip After brushing libra-aqua_firmware_7.2.9.zip on this REC, you can flash lineage-17.1. I do n’t think it will be impossible to refresh because of partition problems. If you only need to upgrade lineage-17.1, you can refer to this method.:good::good:（Translation is not easy to use）

celrau said:
There is a 3.2.x around. If you don't want to bother go in the zip, /META-INF/com/google/android/ and delete the first lines (the ones starting with "assert") from updater-script, save and flash again.
Click to expand...
Click to collapse
rianawirawan said:
Right now, i'm using 3.1.1 -1 btw
It's latest twrp ver from official
Click to expand...
Click to collapse
TWRP-20190418-3.3.0.0-libra.img for the Xiaomi Mi 4c, by GuaiYiHu :
https://androidfilehost.com/?fid=1395089523397945946
Latest firmware for the Xiaomi Mi 4c libra :
https://github.com/XiaomiFirmwareUp...iui_MI4c_V10.1.1.0.NXKCNFI_13b9b312d0_7.0.zip

OnePlus6 fastboot boot twrp not possible after OTA

Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!

Hilzerak said:
Just need to flash root after every OTA.
Click to expand...
Click to collapse
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.

Hilzerak said:
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Click to expand...
Click to collapse
You should you twrp by
remewer said:
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Click to expand...
Click to collapse
Try to in to recovery mode,if not,you try to flash twrp by mau.....

remewer said:
You could do that without TWRP. You just need to use Magisk's "Install to inactive slot" feature after installing OTA but before rebooting.
Click to expand...
Click to collapse
Thx for the info, helps for future.
But know i rebootet.
soihuvuontrang said:
You should you twrp by
Try to in to recovery mode,if not,you try to flash twrp by mau.....
Click to expand...
Click to collapse
Thx for reply but i dont know what excactly do you try to say me.
"You should you twrp by"? What should i try in recovery mode? And im looking forward for an solution without permanent flash, as i sayn above.

Hilzerak said:
Hey guys,
got a OP6 for years. Stay on Stock OS with root. Never flashed any CustomRom or OS.
Bootet with fastboot boot twrp-version.img and flashed Magisk in twrp.
Works absolut fine until now. I installed the OTA and now i cant enter any twrp.
Information about my device:
Device: OnePlus6 A6003
OSS: 10.3.3
Android: 10
Build-Number: A6003_22_200414
USB-Debuggin: Enabled
OEM-Unlock: active
I tried all .img files from here:
eu.dl.twrp.me/enchilada/
and
twrp-3.2.3-x_blu_spark_v9.91_op.img
twrp-3.2.3-x_blu_spark_v9.86_op.img
No version working.
After flashing the 3.2.x versions i get a screen with
"qualcom crashdum mode
-------------"
With the newer 3.3x versions the screen just switch to "fastboot mode" and stay there forever.
How can i just boot into twrp with the new version? I wont twrp forever (flash). Just need to flash root after every OTA.
Thx for help!
Click to expand...
Click to collapse
The version you tried to boot is not for android 10.
Versions for android 10 are blu_spark 9.108 and 9.109. Unfortunately, i think @eng.stk stopped providing img, but you can download lastest @mauronofrio TWRP and then flash @mauronofrio or blu_spark TWRP

Hilzerak said:
Thx for the info, helps for future.
But know i rebootet.
Thx for reply but i dont know what excactly do you try to say me.
"You should you twrp by"? What should i try in recovery mode? And im looking forward for an solution without permanent flash, as i sayn above.
Click to expand...
Click to collapse
After fashing twrp.img you boot into recovery and flash the file twrp.zip(the same series and name with file twrp.img)then reboot recovery.

[CLOSED] Deleted

Here was a Guide. Someone said people don't care about Me or My Work so...​

Thank you

Hello,
I'm going into boot loop when I'm trying this :
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot continue
I have downloaded your img for Xperia 1
Can you help please ?

After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks

kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.

kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
Thats due to the Gesture Navigation. Please enable 3 Button Navigation To fix it... :angel:
daphix said:
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.
Click to expand...
Click to collapse
It was about My Work. There are No other Modules for the Pixel Launcher...
Since My Threads got moved from the Development Section am i No longer contributing Images Myself. Thanks to XDA and the Moderators!

Guide overhauled like promised to some <3 Let Me know if i missed something

Updated the Guide

Updated the Thread again with more exactly Instructions and a typo fix

Attempting to flash the vbmeta.img I have this problem:
unknown option fastboot --disable-verity
Any idea why fastboot can't figure this command? adb version 30.0.5
Also, what exactly is the reason to flash the vbmeta.img? Is this to allow the phone to boot with the patched image..?
I was still able to boot into android but I can't confirm if the devices is rooted or not.. all programs just hang with no confirmation if root access is granted or denied...

Will this work with android 11?

I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Miustone said:
Updated the Thread again with more exactly Instructions and a typo fix
Click to expand...
Click to collapse

jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases

jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
Sorry I meant 22.1 magisk

Miustone said:
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
Any news on this ? I used the latest Magisk 23.0

My Xperia 5 is dead so i can't Test anymore... Sorry

Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Miustone said:
If You want to relock Your Bootloader...
-Just go into fastboot mode any type in the command prompt (like before in this Guide):
Code:
cd\
cd platform-tools
fastboot oem lock
-Wait for Your Device and disconnect it from USB
-Download and Install the "Xperia Companion" from SONY
-Open the Xperia Companion and select Software Repair
-Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
-Go to the next Page and select the Xperia Smartphone Option
-Continue and wait for the Initialization
-Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
-Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and most of Your DRMs are restored. But please Note, that unlocking Your Bootloader erases Your unique Device Key FOREVER. That will flag Your Device as "it was unlocked". This can be checked by SONY and everyone else who has this Device in his Hands... (SONY knows it anyways).
Click to expand...
Click to collapse
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?

OutOfSync said:
Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?
Click to expand...
Click to collapse
You need to choose.
Unlocked = Magisk/Root, Freedom, Control
Locked = No Magisk/Root, Freedom, Control
I do also recommend to wait for Pixel Experience. It will come soon with Mainline Kernels for many Xperias... Including OTAs

Hi guys, I cannot watch Netflix after unlock bootloader my J9110, it shows error 5.8. Tried many workarounds but none of them work.
I'm on Android 12 beta 5. Please help!

Thread Updates coming soon including Android 12 GSI flashing + Magisk

Verified Root Method

1. Unlock bootloader via MI Flash Tool
2. Install ADB and Fastboot Drivers
3. Downloader Latest Platform Tools
4. Open command prompt window in platform tools folder
5. Take phone to fastboot mode (Adb reboot bootloader)
6. Flash the given boot image (Fastboot flash boot boot.img)
7. Flash the given vbmeta (Fastboot flash vbmeta vbmeta.img)
8. Reboot (Fastboot reboot)
9. Download, install and open latest magisk manager in phone. It will reboot phone.
10. Done. You have root now. Verify via root checker.
Credits: @Tigrouzen

is there any bug or issue with miui rom after root? and how to install twrp or any other custom recovery?

ji-r47 said:
is there any bug or issue with miui rom after root? and how to install twrp or any other custom recovery?
Click to expand...
Click to collapse
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.

ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
Thank you very much

ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
Do you have source code for it?

VD171 said:
Do you have source code for it?
Click to expand...
Click to collapse
Not my work, ask @Tigrouzen .

It's working. I don't have to install any ROM to root the phone. Thanks.

This can be done with any version of ROM? I have India version 12.0.9

@sakeyo i dont think region is important for this process, the only diference is the bloatware inside the rom,
if it doesnt works, you can just flash back the stock boot.img and vbmeta.img
or if you want, you can change the ROM to Global
I used XiaomiToolv2 https://www.xiaomitool.com/V2/

It works perfectly on my device. Thanks!

Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance

asia559571 said:
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
Click to expand...
Click to collapse
Im using the latest magisk version, it works flawlessly
its the version 23

yoshijulas said:
Im using the latest magisk version, it works flawlessly
its the version 23
Click to expand...
Click to collapse
Thank You yoshijulas for your reply and Kind Regards

asia559571 said:
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
Click to expand...
Click to collapse
Hello. I am currently not rooted. I removed Magisk and closed the bootloader. But when I was rooted I always used the latest versions of Magisk.

sakeyo said:
Hello. I am currently not rooted. I removed Magisk and closed the bootloader. But when I was rooted I always used the latest versions of Magisk.
Click to expand...
Click to collapse
To be honest, I only wanted root for the sake of having ViPER4Android. I tried the rootless version, but it failed on my phone... got stuck in a boot loop. I'm using Black Player Ex, the equalizer in tandem with the Mi Sound Enhancer works like a charm. One thing I noticed, is that the sound level on the Global Rom is very low compared to the Chinese version, so I'm sticking to the Chinese Rom. If You come across ViPER that can be installed on our device without the need for root, Please let me know. It's a shame that Xiaomi wouldn't/don't have ViPER pre-installed as a system app?
Best Regards

ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
@ahsan.ey.ca I know you just need boot.img and vbmeta.img to get root, but when you installed recovery.img did you get the frozen screen where you can't swipe to unlock twrp?

I'm paranoid, will this boot and vbmeta work on any MiUI version?

Reyproject said:
I'm paranoid, will this boot and vbmeta work on any MiUI version?
Click to expand...
Click to collapse
Not sure.
Probably boot can works.
But the vbmeta certainly works on any version.

Where can I find the boot.img for flashing recovery?

criza said:
Where can I find the boot.img for flashing recovery?
Click to expand...
Click to collapse
Try here:
[IMG][ROOT][PATCHED] Magisk Patched Boot: ROOTED Images Partitions for DANDELION (Redmi 9A / Redmi 9AT)
Magisk Patched BOOT.IMG for DANDELION ROOT / PREROOT ROOTED / PREROOTED Works with: - Xiaomi Redmi 9A - Xiaomi Redmi 9AT Does NOT work with: - Xiaomi Redmi 10A Firmware Versions: - (Engineering) 246 - (Engineering) 440 - (Indonesia)...
forum.xda-developers.com