Develop Bugs

Blackview BV9000 Pro-F ROOT SUCCESS [TWRP + Magisk v16 + Stock Rom]

EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have

Congrats! Would it work on the BV9000 HD version?

Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash

hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F

Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?

>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.

>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><

hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected

Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!

Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers

zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone

I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q

Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?

Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889

TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:

help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?

mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)

Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers

Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...

Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.

[Guide] Root for Redmi Note 9 - Mediatek (Helio G85)

Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.

Removing "Bloatware"
Probably one the main reasons for obtaining root privileges is to get rid of some default apps which come bundled with the official MIUI.
Given the current situation for this device, using classic methods (such as Titanium Backup / System App Remover / etc.) is not possible and - most probably - attempting in doing so will result in a soft-brick.
Instead, there is a particularly useful Magisk Module that can be used for this scope: Debloater.
You can read more about it here on XDA; the installation procedure will vary just a bit since there is currently no TWRP support for the Helio G85 Redmi Note 9.
Installing Debloater
Launch Magisk Manager and select "Download" from the menu
Use the search function to locate the package "Busybox for Android NDK"
Install the package, and chose to skip the reboot at the end of the procedure.
Use the search function to locate the package "Debloater Terminal Emulator"
Install the package and this time proceed with the reboot
When the reboot is complete, install any terminal emulator app from PlayStore (like Termux)
Open the terminal and issue:
Code:
su
(confirm the request for superuser access) and then
Code:
debloat
Now you can use Debloat to remove all the unwanted applications that come bundled with the ROM.
Please refer to the video included in the post mentioned above to learn more about Debloat and how to use it.

One Question
Can i know this work for Redmi Note 9 global non NFC?

The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!

dfahren said:
The download link in the first post does not work any longer ... Gives a 404. Please re-upload and don't use XDA's upload space. Thanks!
Click to expand...
Click to collapse
Sorry for the inconvenience, there is still the MEGA link from the first post up and working.
Here it is: https://mega.nz/file/ucFDXIaY#FrUllKuUASoStlSvrcMYABsbYv6ie-WHR4zOqJMdP4E

[email protected] said:
Can i know this work for Redmi Note 9 global non NFC?
Click to expand...
Click to collapse
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.

N3OMOD said:
It should work, since there is no significant difference between the two models regarding the rooting procedure. But I have no way of testing it because I don't have that phone version on hand.
Click to expand...
Click to collapse
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!

dfahren said:
Hi there,
I can confirm the aforementioned procedure to root one's phone does work. I own a Redmi Note 9, Code: merlinnfc, Version: 11.0.5.0 (QJOEUXM). As you can see it's the European variant.
Click to expand...
Click to collapse
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
dfahren said:
However, I didn't use the Zip archive the OP provided since it is meant for the global variant and (as of now) I don't see any necessity to reflash my phone to the global firmware.
I strongly recommend everybody to have Magisk Manager generate patched boot.img files and NOT use the original author's boot.img file! This holds true especially for those guys like me who own, say, an indian, chinese or european variant or run a different firmware version like, e.g., 11.0.3.0.
Click to expand...
Click to collapse
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
dfahren said:
What's also important to mention is that there is no special "patched" vbmeta file. That guy "neko-kun" simply used the one contained in the original full firmare downloadable from Xiaomi's servers. Here you also have to make sure you use the one that matches the installed firmware version on your phone. Do not flash any other or you might get a brick!
Click to expand...
Click to collapse
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
dfahren said:
If anybody of you guys has managed to get AFWall up and running and apply iptable rules without error, please drop me a line.
Thanks and good speed to everybody!
Click to expand...
Click to collapse
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)

Followed the steps, worked flawlessly on my Redmi Note 9 (Merlin) 3gb ram 64gb storage purchased in Europe, running Global 11.0.5.
Thank you so very much!
I had successfully done this in the past but messed something up with xposed later, I won't xposed it this time and just enjoy my root-ness.

N3OMOD said:
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
...
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
...
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
The original explanation from user "neko-kun" seemed to me an automatic translation hence the rather weird language.
I can testify to the statement that you can reflash the original boot.img file should you enter a bootloop (which I got).
AdAway is also working for me as does AFWall+ (I needed to leave logging of blocked packets as it is -> off)

N3OMOD said:
Thank you for the feedback! That is the same version (hardware and ROM) I used to test the procedure before writing the article.
Indeed, as I mentioned in the first post, those files are provided only as a courtesy for those who may have the same device with the same firmware: I strongly encourage everyone to make their own using Magisk Manager.
Thanks for the clarification about the vbmeta file. I will update the post to clarify this aspect.: good:
The original explanation from the user was a bit difficult to understand, hence the warning about the possibility of a "patched" file. (I didn't want to create any trouble for anyone).
Also, a little comforting for anyone who might incur in a (soft)brick: I have seen some people flashing only the "boot.img" and ending up in an infinite bootloop (black screen with "redmi" logo).
Should that happen, you can always enter the fastboot mode (keeping pressed the power+vol down for a bit longer than usual) and re-flash the original "boot.img" extracted from the official ROM image available on MIUI site.
Will let you know as soon as I have some time to test it.
(sidenote for those interested: for now I can confirm that AdAway is working fine)
Click to expand...
Click to collapse
i'm having an infinite bootloop and keep pressing power + vol down didn't help , what should i do ?

@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi

dfahren said:
@noodlelicious
That's very unfortunate. I know this situation only too well. First of all what type of Redmi Note 9 do you have. Please post the "Product Model" number you can find on your phone and package. Mine, for example, is M2003J15SG. Which version of MIUI did you run? Is it MIUI 11 or the newer MIUI 12? Do you run some regional flavor of MIUI such as European, Russian, Indonesian, Indian or China?
Second, did you flash the correct vbmeta file? I mean this is an IMG file that must match the flavor? The original poster supplied a vbmeta IMG file for the global variant that might (I'm really not sure) not fit to your specific flavor.
Ok, how do you get rid of the boot loop? I manged to stop the loop by pressing Volume down continuously for about a minute. After that my phone reboots into fastboot mode. Please DO NOT press the power button, this is unnecessary.
When in fastboot mode reflash your original boot.img according to the steps above.
I hope that helps you a bit.
Best wishes,
Didi
Click to expand...
Click to collapse
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?

What about entering recovery?
noodlelicious said:
Thank you so much for replying my problems.
First, i'm using M2003J15SS
I'm running on latest miui 11 indonesian.
I'm flashing the vbmeta on first post , i skip all the comment section and straight install all the things there.
I already put a rubber band on my vol down since 7 hours ago and still got no fastboot.
What else can i do ?
Click to expand...
Click to collapse
Try to enter stock recovery, if you can, select mi assitant. After that connect trough adb and run "adb reboot bootloader", that should do the trick.
If phone isnt booting none of main enviroments (system, recovery or fastboot/bootloader) battery drainage may restablish normal boot order. Just remember that if in any case it boots to recovery, use adb command to reboot to bootloader.

Tested on RN9 Global non-NFC (M2003J15SS) with MIUI 12 Global
Hi, just to inform. The following was tested in Redmi Note 9 Global non-NFC (M2003J15SS) with MIUI 12 Global.
- Patched boot image from MIUI12 Global (Android 10) works fine if dm-verity and forced encryption are disable at the time of making the boot image with magisk.
- vbmeta file provided by OP also works (I think any file would work if it's flashed with "--disable-verity --disable-verification" option. This option is essential to avoid bootloop after flashing any non-stock (or patched) image to any partition:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
The vbmeta file I used was extracted (and possibly) edited from a previous version of MIUI (MIUI11), and applied over MIUI12 ROM, that's why I think any file could be used.

Hi .. Is there a way to write to system / app. I need to be able to pass an application to system. Thank you.

Does netflix still work in HD after having the BL unlocked and further rooted?

How to patch vbmeta
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
N3OMOD said:
Preamble:
After a bit of research, I've found a simple way to - at least - obtain root privileges on the basic version of Redmi Note 9 (Mediatek - Helio G85).
The procedure has been tested on a Redmi Note 9 Global NFC 4/128 (Model: M2003J15SG) with MIUI Global 11.0.5.
The attached files comprise:
Original Boot Image from MIUI Global 11.0.5 (provided as a courtesy, download your own copy from MIUI Website if you wish)
Patched Boot Image from Magisk on MIUI Global 11.0.5 (again, the file provided as a courtesy; you can generate your own file, on your device.)
VBMETA Patched Image: essential to the process, this file has not been created by me. Courtesy of user Neko-kun from MI.cn Forum. I can only confirm that the file works as expected; please, if you have the required expertise, inspect the file and report your findings.
Warning:
This procedure depends on having previously unlocked the bootloader. Doing so you have read, understood and accepted all the information regarding security and potential stability issues given by XIAOMI before completing the procedure.
Also, this means you have understood and accepted potential warranty issues arising from such procedure, and you understand the risks associated with a rooted device.
I'm not responsible for any damage, loss of personal data, brick or loss of usability arising from following this procedure and/or from any user error committed by doing so.
As a result, your warranty may be void, according to laws in effect in your state.
This procedure is only valid for Redmi Note 9 (not the Pro version, not the 9S version) with MEDIATEK chipset
Note:
Always make a back-up of your data! This procedure will re-initialize the device.
Requirements:
A valid MI Account, associated with the phone, used to certification in the bootloader unlocking procedure. (via official MI UNLOCK)
Unlocked Bootloader (new devices usually have a 7-day waiting period)
A personal computer with FASTBOOT installed, basic knowledge of FASTBOOT commands, drivers correctly installed on your system of choice. (for windows users, a valid solution is "Minimal ABD and Fastboot".)
Resources:
Magisk Manager
Boot Image / Magisk Patched Boot Image / VBMeta Image - link or see attached files
Procedure:
Download the attached files (or generate the first two on your own device, using Magisk Manager).
Copy the prepared files inside the fastboot directory (so you don't have to worry about file path in the following steps)
Reboot the phone into Fastboot Mode (hold Power+Volume Down until fastboot screen)
Connect the phone to the computer, open fastboot terminal and issue the following commands. BE PATIENT AND DOUBLE CHECK EVERYTHING BEFORE CONFIRMING! Text between round brackets are comments, it must not be copied.
Code:
fastboot devices (check your phone is the only device shown)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)
fastboot erase userdata (this will clear user data!)
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
The following first reboot will take a while. After completing the initial configuration, install the latest Magisk Manager (at the time of writing, v. 7.5.1) and continue with the configuration following the in-app prompt.
Phone will reboot at the end of the procedure. Launch once again Magisk Manager, select the "Beta Channel" for updates and enable Magisk Hide.
Reload Magisk Manager, check for Safety Net: you should have the green light.
Enjoy your root privileges. (aka, get rid of the bloatware )
Known BUGs / LIMITATIONS:
Can't modify /system partition
Need to temporary set SELinux to permissive in order to remove system apps. Please refer to this post.
Click to expand...
Click to collapse
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?

can this be used to root the EU model: MZB9410EU ?

farvehar09 said:
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
can i use original vbmeta in rom files for this command
"fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (this disables system changes)"
Because my phone is redmi note 9 (m2003j15ss) updated to 12.03.0(QJOMIXM) miui version
If not with the original, how do I patch this file?
Click to expand...
Click to collapse
Yes u can, i use the original vbmeta from miui_MERLINIDGlobal_V12.0.1.0.QJOIDXM_709d727d58_10.0.zip (ID variant)

[GUIDES & FAQ][Merlin] Bootloader, Magisk, EdXposed, SafetyNet, GSI/Treble ROMs

DISCLAIMERS (please read !)​
This thread is made for the Redmi Note 9, also known as Redmi 10X 4G.
This device's codename is Merlin.
I will not be held responsible if you brick your device.
Follow the instructions shown in this thread at your own risks.
Follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded files.
Feel free to cite parts of this thread in your own, just make sure to give credit where it's due.
Prerequisites for most manipulations​
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Tutorials​
Spoiler: Unlocking your bootloader (Required for all other tutorials below)
Step 1
Make sure you have a Mi Account ready.
You should've created one when first setting up your phone, with your phone number and a password.
- If you have it: Double-check you have access to it by attempting to connect on Xiaomi's official website (Login page).
- If you don't: Create one with the Create an account button below the password form (same link as above), then connect to it.
Step 2
On your PC, go to Xiaomi's unlock page and click the colored Download Mi Unlock button.
{
"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"
}
Step 3
A download should start. Wait for it to finish, move the archive to your desktop and extract its content.
Step 4
Inside the extracted folder, double click the file called miflash_unlock.exe to start Xiaomi's Unlocking program.
Step 5
Read Xiaomi's Disclaimer then agree to their terms, or stop here and leave this thread if you don't.
Step 6
Sign in to your Mi Account we talked about in Step 1.
Step 7
Let's get your phone ready for unlocking.
Go to your phone's Settings > Mi Account and make sure you're logged in.
Now Settings > About Phone and tap the "MIUI Version" box multiple times until it says You are now a developer!
And finally Settings > Additional Settings > Developer Options
Enable the following settings inside Developer Options, and click Accept when warnings pop-up:
OEM Unlocking
USB Debugging
Still in Developer Options, check your Mi Unlock status and click the Add account and device button at the bottom if present.
Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 8
Alright, all backed up? Confident? Let's get going with the final steps.
Turn off your phone.
Turn it back on into fastboot mode by holding down the Power button AND Volume Down together until it vibrates, you may then let go of the Power Button, but keep Volume Down held until you see the fastboot image on your phone.
Connect your phone to your computer with the USB Cable.
Xiaomi's Software should detect it. If not, click on the cog-wheel in the top right, click the Check button to install the driver and follow instructions, then keep going.
Click Unlock, and follow the instructions!
Now there are two possible scenarios
Either you've done all this before and can have your phone unlocked right away.
Or this is the first time and at the end of the progress it'll ask you to wait ~7days, and, well, there's no way around that, so come back in 7 days and start from Step 8 again.
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install custom ROMs/recovery!
Spoiler: Rooting (Magisk)
Step 1
Download the latest Magisk .apk on your phone.
Go to the link above, click the latest (topmost) Magisk-vXX.X.apk you see in the list to start the download, open the file and install it.
Step 2
Go to the download page for the MIUI Official Rom for your region, make sure to get the fastboot version.
OR (if you don't want/can't download 3gb of ROM)
Follow DavitidzeSh's instructions on how to gather the boot.img and vbmeta.img files and SKIP to Step 5.
OR (if you're on a custom rom)
Look into your custom rom's .zip, find the boot.img and vbmeta.img files and SKIP to Step 5.
Step 3
Take the file you downloaded above, it should be a .tgz archive.
Extract it, you'll get a .tar achive.
Extract that one again.
Step 4
You should now have a folder similar to the one below
Go inside the images folder
Step 5
Grab the the vbmeta.img file and copy it to your ADB & Fastboot (Platform Tools) folder.
Grab the boot.img file and copy it to your phone's internal storage.
(where the Android, DCIM, Download, and more are present, just drop it in there)
Here's how it should look inside your phone's storage in the end.
Step 6
On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 7
Link your phone to your PC, grab the file made by Magisk Manager.
It's located in your phone's downloads folder, called magisk_patched.img.
Copy and paste it where your ADB & Fastboot (Platform Tools) are located.
You should now have a folder structure like this:
adb.exe
fastboot.exe
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8
Alright, we're ready to root!
Turn off your phone, then get in fastboot mode.
(Power + Volume Down, like the unlocking tutorial)
Step 9
Link your phone to your PC with the USB cable if not done already.
Step 10
Shift + Right click in an empty space inside the folder we prepared in Step 7,
And click Open PowerShell window here.
Inside the PowerShell window, input the following commands line by line, in order.
.\fastboot.exe devices
Click to expand...
Click to collapse
Make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
.\fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img
.\fastboot.exe flash boot .\magisk_patched.img
.\fastboot.exe reboot
Click to expand...
Click to collapse
Note: Your PowerShell window will look different, I'm using a different program, don't worry
Your phone will reboot.
Open up Magisk Manager, and double check that it's installed.
You're done!
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is rooted.
Check out the Passing SafetyNet tutorial further down below!
Spoiler: Getting EdXposed
I very much discourage to EdXposed your phone unless you have a very good reason for it.
It's a pain to pass SafetyNet.
It doesn't get updated often.
It has very niche use cases for which it's actually worth it.
That said, I explain it here for people who know what they're getting into and want instructions on how to do it.
This procedure requires to be rooted with Magisk.
Step 1
Inside Magisk Manager, go to the Modules tab.
Click the search button (bottom right) and search Riru.
Install the Riru module by Rikka.
Activate it and Reboot.
Step 2
Download and install the latest EdXposed Manager, the same way you did with Magisk Manager when rooting.
Step 3
Open it up, go to the ALPHA tab and click install/update.
It'll start a file download.
Step 4
Go back to Magisk Manager, Modules tab, except this time click Install from Storage.
Point to the .zip file you just got, located in the Downloads folder of your phone.
At the end of the installation, click reboot.
Step 5
Let's double check your installation is operational.
Go to EdXposed Manager, first tab.
It should say EdXposed Framework is active.
You're done!
You should now be able to install EdXposed modules.
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is EdXposed.
Check out the Passing SafetyNet tutorial further down below!
Spoiler: Passing SafetyNet (Magisk/EdXposed)
For Magisk Rooted Phones
Enable Magisk Hide inside Magisk Manager's settings.
You may also need to use the Props module to spoof your phone as another, if you want a tutorial on that, let me know.
For EdXposed Phones
Again, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services Framework
Reboot and enjoy! You're all set and SafetyNet should pass.
Spoiler: Installing GSI's (Non-device specific ROMs)
Step 1
Pick your poison in the Treble Forums!
My recommendations are in the Extras section of this post.
Step 2
Download the chosen ROM's A/B Arm64 version
It should be an .img.xz file
Extract it and you'll get an .img file.
You're almost ready to flash.
Make sure to backup your phone's data.
Continuing this tutorial will wipe your phone!
Step 3
Put your phone into fastboot mode.
(Power + Volume Down)
Connect it to your PC.
Step 4
Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder.
Rename it to system.img
Step 5
Shift + Right click in an empty space inside the folder,
And click Open PowerShell window here.
Inside the PowerShell window, input the following commands line by line, in order.
.\fastboot.exe reboot fastboot
.\fastboot.exe --disable-verification flash vbmeta .\vbmeta.img
.\fastboot.exe flash system .\system.img
.\fastboot.exe -w
.\fastboot.exe reboot
Click to expand...
Click to collapse
Your phone will now reboot on its own.
Set it all up and enjoy!
That said, depending on how old the GSI you picked is, you MAY have issues leaving it at that.
Therefore, I highly recommend checking out the next tutorial section about Fixing GSI Issues.
Spoiler: Fixing brightness/jack on older GSI's
I have worked together with a developer to bring fixes for our device to every custom GSI rom out there.
The most recent GSI's shouldn't need the fixes listed below.
Older GSI (treble) roms have two known bugs that we can fix:
The brightness slider being misscalibrated, and therefore auto-brightness broken too.
The headphone jack not working.
You need to be rooted to do so.
Step 1 - Get yourself a Terminal Emulator, I recommend Termux
Step 2 - Type the following commands inside of it, line by line, in order:
su
setprop persist.sys.qcom-brightness $(cat /sys/class/leds/lcd-backlight/max_brightness)
setprop persist.sys.overlay.devinputjack true
Click to expand...
Click to collapse
You're done! Brightness should be fine, headphones get detected, enjoy!
Spoiler: Resetting your phone
Backup all the data you might have on your phone to restore it after the manipulation!
Step 1
Download the fastboot ROM corresponding to your region here.
(The same one used to grab the boot.img and vbmeta.img when rooting)
And extract it.
Step 2
Download the latest MiFlashTool.
And extract it.
Step 3
Put your device in fastboot mode.
(Power + Vol Down, refer to the rooting tutorial for a more info)
And connect it to your computer via USB.
Step 4
Open MiFlashTool (XiaoMiFlash.exe), your device should appear in the list.
Step 5
Click the Select button in the top left,
And point to your fastboot ROM's folder
(The one containing the "AP", "BP", "BP_IN", "images" folders and a bunch of files)
Step 6
At the bottom right of the software, choose if you either want to just:
clean all
(wipe and re-install)
OR
clean all and lock
(wipe, reinstall and re-lock your bootloader)
Note: If you re-lock your bootloader but wish to unlock it again later, you won't have to wait the 7 days again.
Step 7
Finally, in the top right, click the flash button.
Now just wait a while, your phone will reboot on the stock rom and you're good to go!
Extras​
Spoiler: Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not, it's easily reversable too, check the "Resetting your phone" tutorial.
Q: I rooted/EdXposed my phone and now Netflix won't even open, or doesn't work properly, what's up with that?
A: There's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.
Q: I tried unlocking my bootloader but, Mi Flash Unlock doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
Try another USB port.
Try another USB cable.
Install the Mi USB Drivers manually, they're included in the MiFlashUnlock folder.
Run the driver_install_64.exe, OR go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install.
In the Device Manager, check that the driver provider is Xiaomi.
If not, uninstall it and restart your computer.

RESERVED

Akitake said:
RESERVED
Click to expand...
Click to collapse
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks

HemanthJabalpuri said:
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
Click to expand...
Click to collapse
1.Flashing official firmware is universal method for all devices through fastboot, And for recovery, we can't flash it yet since TWRP doesn't support dynamic partition yet.
2.No, you don't need the same firmware.
3.If you interrupt the process in between, the device would remain in fastboot Mode, and you can still restart the process.

Yxnq_Param said:
1.Flashing official firmware is universal method for all devices through fastboot, And for recovery, we can't flash it yet since TWRP doesn't support dynamic partition yet.
2.No, you don't need the same firmware.
3.If you interrupt the process in between, the device would remain in fastboot Mode, and you can still restart the process.
Click to expand...
Click to collapse
I heard a term called "Anti Roll Back" from https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
Are all our merlin ROMs have same version of anti roll back. That is are we able to flash MIUI 11 on MIUI 12?
Thanks

HemanthJabalpuri said:
I heard a term called "Anti Roll Back" from https://forum.xda-developers.com/redmi-note-5-pro/how-to/faq-questions-answered-t3816185
Are all our merlin ROMs have same version of anti roll back. That is are we able to flash MIUI 11 on MIUI 12?
Thanks
Click to expand...
Click to collapse
Anti-rollback is only an issue if you're trying to downgrade through the stock recovery (Vol + Up) or through MIUI's recovery (About Phone > MIUI Version > Three dots and there is an option there)
If you want to go back to MIUI 11 for some reason, you can, by flashing it through fastboot.
HemanthJabalpuri said:
Hi,
I am also a user of RN9 Merlin.
I think we should add more details like
-how to flash official firmware(both from stock recovery, fastboot)
-should we need the same MIUI firmware that is there before we started booting custom ROM(GSI), if we need to go back to stock?
-what should happen if we interrupt the process in middle
-unlocking bootloader linux, macos or a link for the guide
-why we need to flash vbmeta.img?
-how to make vbmeta.img on our own(some are giving modified one, what is it?)
I know we need more and more time to do these, but these will help a newbie/noob/beginner for Xiaomi and rooting.
Thanks
Click to expand...
Click to collapse
1 - Google, this isn't Merlin specific.
2 - No, you can go back directly to the latest MIUI for your device.
3 - Just start over, your device will remain in fastboot, it's actually really safe.
4 - That's a niche demand, 99% of people use Windows and, if you use something else it's on you. If you're a Linux user, you're used googling information and it's not a problem. And for mac, well, worst case scenario use someone else's pc for 10 minutes.
5 - To prevent boot-loops. If you don't flash vbmeta, it won't boot.
6 - Read disclaimers, the tutorial literally tells you to take the vbmeta from the official rom. There's no such thing as a modified vbmeta, what matters is how we flash it with fastboot, disabling verifications.
Also this is my first post, and I'll add more as time goes on. But even as it is, I think it's miles better than what people care to create for most devices on XDA. It's also pretty detailed with images and such to reassure the user.

can someone help me?
So I wanted to unlock the bootloader
Did the
Turnn on OEM unlocking
Turn on USB debugging
Added my device on my account (the other thing to do in developer setting)
Boot into fastboot
The Mi unlock can't detect my device although the drivers are fine (I checked it in device manager) and I run it in administrator check the driver again in the software it says it is installed.
What can I do? Did I missed some steps?

markevan12 said:
can someone help me?
So I wanted to unlock the bootloader
Did the
Turnn on OEM unlocking
Turn on USB debugging
Added my device on my account (the other thing to do in developer setting)
Boot into fastboot
The Mi unlock can't detect my device although the drivers are fine (I checked it in device manager) and I run it in administrator check the driver again in the software it says it is installed.
What can I do? Did I missed some steps?
Click to expand...
Click to collapse
Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Mi USB Drivers manually (included in the MiFlashUnlock folder, run the driver_install_64.exe, or go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install)
- In the Device Manager, check that the driver provider is Xiaomi. If not, uninstall it and restart your computer.

hi sir , can you tell the gsi rom install tutorial if we installed it from twrp?

fachrizoyy said:
hi sir , can you tell the gsi rom install tutorial if we installed it from twrp?
Click to expand...
Click to collapse
I will not support custom recovery's. I highly dislike them, and they're unofficial for Merlin as well.

Thx for the answer

Akitake said:
Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Mi USB Drivers manually (included in the MiFlashUnlock folder, run the driver_install_64.exe, or go to the driver folder, then the folder corresponding to your windows version, right click the android_winusb.inf and click Install)
- In the Device Manager, check that the driver provider is Xiaomi. If not, uninstall it and restart your computer.
Click to expand...
Click to collapse
thanks but I solved it by moving the unlock folder to C:

Hey man. First of all I appreciate that you spent this much time for redmi note 9 users. I just want to know that how do I know that my device is merlin?

mirzanuman6612 said:
Hey man. First of all I appreciate that you spent this much time for redmi note 9 users. I just want to know that how do I know that my device is merlin?
Click to expand...
Click to collapse
Hey, no problem!
Well, Merlin is just the codename for Redmi Note 9. So if you have a Redmi Note 9, you have a merlin.
BUT, keep in mind the Redmi Note 9 Pro, Pro Max and S are different and have their own section in the forums.

Akitake said:
Hey, no problem!
Well, Merlin is just the codename for Redmi Note 9. So if you have a Redmi Note 9, you have a merlin.
BUT, keep in mind the Redmi Note 9 Pro, Pro Max and S are different and have their own section in the forums.
Click to expand...
Click to collapse
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.

mirzanuman6612 said:
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
Click to expand...
Click to collapse
Yes I could, I will actually add a section to the FAQ soon for better driver installation, it's a driver issue.

Akitake said:
Yes I could, I will actually add a section to the FAQ soon for better driver installation, it's a driver issue.
Click to expand...
Click to collapse
Alrighty, thanks for your replies.

mirzanuman6612 said:
Well, thanks but one more thing, I tried unlocking the bootloader of my phone yesterday. I went into developer options and enabled the following options:
OEM unlocking
USB debugging
I also installed all the drivers needed in my pc and went into fastboot mode in my phone. But Xiaomis mi unlock can't recognise my device. I tried 2 different usb cables but the mi unlock just says, "your phone is not connected" I hope to get a reply from you and you will probably will be able to help me out.
Click to expand...
Click to collapse
Had you tried moving the unlock folder to c:/ ?

markevan12 said:
Had you tried moving the unlock folder to c:/ ?
Click to expand...
Click to collapse
I appreciate you replying to me. But, I already fixed it by installing windows 7 I had windows 10 before and it didn't seem to work on it so I installed windows 7 and it worked flawlessly. Btw, are you a user that has installed a custom rom? And if yes, then which one and is the performance any better?
Thanks.

mirzanuman6612 said:
I appreciate you replying to me. But, I already fixed it by installing windows 7 I had windows 10 before and it didn't seem to work on it so I installed windows 7 and it worked flawlessly. Btw, are you a user that has installed a custom rom? And if yes, then which one and is the performance any better?
Thanks.
Click to expand...
Click to collapse
Nope I didn't YET, I'm still waiting for the unlock to complete. I did tried treble roms in my other device. It just is basically have the same performance (LOSQ) but I had heating problems in my Samsung device, I expect a normal experience with this ROMs.

[GUIDE] Root Umidigi A9 Pro 2021 (Magisk+Android 11)

*This guide is for the A9 Pro 2021 model with 8gb of RAM only. It was tested on the non-EU version but I see no reason for it to not apply to that model as well, so long is it an A/B partitioned device, which i believe it is*
I was having some difficulty rooting this device following the instructions found in an Umidigi posting. The instructions were not for rooting an A/B partitioned device and that's what was causing failure. If you tried the same method, you may have noticed that your device starts and then just reboots before the orange alert text goes away. Over and over...
Since I had not found one single posting about how to achieve root, I will share how I was able to do this thanks in part to an old post from this site combined with the instructions on Umidigi.
Before starting, I have to say something like this:
WARNING
IF YOU MAKE ANY ATTEMPT TO MODIFY YOUR DEVICE BY FOLLOWING THE INSTRUCTIONS OUTLINED IN THIS GUIDE YOUR PHONE WARRANTY WILL BE VOID AND ALSO MAY CEASE TO FUNCTION BY DOING SO. YOU ARE SOLELY RESPONSIBLE FOR YOUR ACTIONS AND ASSUME ALL RESPONSIBILITY FOR ANY AND ALL DAMAGE THAT MAY OCCUR
I'll assume you know what ADB is, you've unlocked the bootloader and have a copy of the EXACT firmware on your PC as you do on your phone. If not, please do that first. You're going to need it in order to follow this guide. Next, I'll assume you've also backed up your device.
*Before starting, run this adb command and if you get a "b" instead of an "a" then adjust your commands in step 6 to boot_b and vbmeta_b*
adb shell
getprop ro.boot.slot_suffix
exit
1) From your phone, download and install latest Magisk apk from Github. At time of writing, this is version 23
2) On PC, copy the boot.img and vbmeta.img files from your CURRENT firmware downloaded from Umidigii to your desktop. You will see 3 files beginning with vbmeta. We only want one of those, vbmeta.img
3) Plug in your phone to PC and copy the boot.img file to your phone
4) Run Magisk and select Install (top of list). You are given the option to patch a boot.img file. Select the boot.img you just copied to your device and Let's Go!
5) From PC, navigate to your phone's internal storage, specifically the Downloads folder and copy the newly created patched_magisk-xxxx.img file to your Desktop
6) From PC, with phone powered on and connected, open powershell as admin, enter these commands and properly input the name of your patched Magisk file. First command is only for those that placed files on the Desktop
cd ~\Desktop
adb reboot bootloader
fastboot --disable-verity --disable-verification flash boot_a magisk_patched-23000_xxxxx.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot reboot
That's it

Hello friend, I recently tried to install a custom ROM which in this case is DotOS 5.2, I downloaded everything correctly and it worked, my cell phone turned on ok. So I tried to install magisk and it bootloops, do you have any solution to make magisk work in a custom ROM? On my ROM, the stock works perfectly
Sorry for my English, I'm translating from the translator

mindlery said:
*This guide is for the A9 Pro 2021 model with 8gb of RAM only. It was tested on the non-EU version but I see no reason for it to not apply to that model as well, so long is it an A/B partitioned device, which i believe it is*
I was having some difficulty rooting this device following the instructions found in an Umidigi posting. The instructions were not for rooting an A/B partitioned device and that's what was causing failure. If you tried the same method, you may have noticed that your device starts and then just reboots before the orange alert text goes away. Over and over...
Since I had not found one single posting about how to achieve root, I will share how I was able to do this thanks in part to an old post from this site combined with the instructions on Umidigi.
Before starting, I have to say something like this:
WARNING
IF YOU MAKE ANY ATTEMPT TO MODIFY YOUR DEVICE BY FOLLOWING THE INSTRUCTIONS OUTLINED IN THIS GUIDE YOUR PHONE WARRANTY WILL BE VOID AND ALSO MAY CEASE TO FUNCTION BY DOING SO. YOU ARE SOLELY RESPONSIBLE FOR YOUR ACTIONS AND ASSUME ALL RESPONSIBILITY FOR ANY AND ALL DAMAGE THAT MAY OCCUR
I'll assume you know what ADB is, you've unlocked the bootloader and have a copy of the EXACT firmware on your PC as you do on your phone. If not, please do that first. You're going to need it in order to follow this guide. Next, I'll assume you've also backed up your device.
*Before starting, run this adb command and if you get a "b" instead of an "a" then adjust your commands in step 6 to boot_b and vbmeta_b*
adb shell
getprop ro.boot.slot_suffix
exit
1) From your phone, download and install latest Magisk apk from Github. At time of writing, this is version 23
2) On PC, copy the boot.img and vbmeta.img files from your CURRENT firmware downloaded from Umidigii to your desktop. You will see 3 files beginning with vbmeta. We only want one of those, vbmeta.img
3) Plug in your phone to PC and copy the boot.img file to your phone
4) Run Magisk and select Install (top of list). You are given the option to patch a boot.img file. Select the boot.img you just copied to your device and Let's Go!
5) From PC, navigate to your phone's internal storage, specifically the Downloads folder and copy the newly created patched_magisk-xxxx.img file to your Desktop
6) From PC, with phone powered on and connected, open powershell as admin, enter these commands and properly input the name of your patched Magisk file. First command is only for those that placed files on the Desktop
cd ~\Desktop
adb reboot bootloader
fastboot --disable-verity --disable-verification flash boot_a magisk_patched-23000_xxxxx.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot reboot
That's it
Click to expand...
Click to collapse
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't

Sirkev said:
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't
Click to expand...
Click to collapse
Hey Sirkev,
I am about to start looking into getting Android 12 running on this same device.
Umidigi A9 6GB + 128GB, currently running Android 11.
Please keep me updated with your progress, and I will do the same.
I MIGHT try to compile a custom Android 12 (Possibly even Android 13...) rom for this device if I can find enough time to look into it...
Side question - When you go to Google Play store with YOUR A9 Pro running the stock Android 11 rom, click on your profile picture in top right corner, click "Settings", then expand "About"...
What does your A9 say at the very bottom under "Play Protect Certification"???
Thanks!

mindlery said:
*This guide is for the A9 Pro 2021 model with 8gb of RAM only. It was tested on the non-EU version but I see no reason for it to not apply to that model as well, so long is it an A/B partitioned device, which i believe it is*
I was having some difficulty rooting this device following the instructions found in an Umidigi posting. The instructions were not for rooting an A/B partitioned device and that's what was causing failure. If you tried the same method, you may have noticed that your device starts and then just reboots before the orange alert text goes away. Over and over...
Since I had not found one single posting about how to achieve root, I will share how I was able to do this thanks in part to an old post from this site combined with the instructions on Umidigi.
Before starting, I have to say something like this:
WARNING
IF YOU MAKE ANY ATTEMPT TO MODIFY YOUR DEVICE BY FOLLOWING THE INSTRUCTIONS OUTLINED IN THIS GUIDE YOUR PHONE WARRANTY WILL BE VOID AND ALSO MAY CEASE TO FUNCTION BY DOING SO. YOU ARE SOLELY RESPONSIBLE FOR YOUR ACTIONS AND ASSUME ALL RESPONSIBILITY FOR ANY AND ALL DAMAGE THAT MAY OCCUR
I'll assume you know what ADB is, you've unlocked the bootloader and have a copy of the EXACT firmware on your PC as you do on your phone. If not, please do that first. You're going to need it in order to follow this guide. Next, I'll assume you've also backed up your device.
*Before starting, run this adb command and if you get a "b" instead of an "a" then adjust your commands in step 6 to boot_b and vbmeta_b*
adb shell
getprop ro.boot.slot_suffix
exit
1) From your phone, download and install latest Magisk apk from Github. At time of writing, this is version 23
2) On PC, copy the boot.img and vbmeta.img files from your CURRENT firmware downloaded from Umidigii to your desktop. You will see 3 files beginning with vbmeta. We only want one of those, vbmeta.img
3) Plug in your phone to PC and copy the boot.img file to your phone
4) Run Magisk and select Install (top of list). You are given the option to patch a boot.img file. Select the boot.img you just copied to your device and Let's Go!
5) From PC, navigate to your phone's internal storage, specifically the Downloads folder and copy the newly created patched_magisk-xxxx.img file to your Desktop
6) From PC, with phone powered on and connected, open powershell as admin, enter these commands and properly input the name of your patched Magisk file. First command is only for those that placed files on the Desktop
cd ~\Desktop
adb reboot bootloader
fastboot --disable-verity --disable-verification flash boot_a magisk_patched-23000_xxxxx.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot reboot
That's it
Click to expand...
Click to collapse
I have Umidigi A9 Pro 2020 version with android 10 is there any way I can Update it to Android 11?

GooballDiesel said:
Hey Sirkev,
I am about to start looking into getting Android 12 running on this same device.
Umidigi A9 6GB + 128GB, currently running Android 11.
Please keep me updated with your progress, and I will do the same.
I MIGHT try to compile a custom Android 12 (Possibly even Android 13...) rom for this device if I can find enough time to look into it...
Side question - When you go to Google Play store with YOUR A9 Pro running the stock Android 11 rom, click on your profile picture in top right corner, click "Settings", then expand "About"...
What does your A9 say at the very bottom under "Play Protect Certification"???
Thanks!
Click to expand...
Click to collapse
I have Umidigi A9 pro 2020 with Android 10 is there any way I can Update it to Android 11?

Isaac™ said:
Hello friend, I recently tried to install a custom ROM which in this case is DotOS 5.2, I downloaded everything correctly and it worked, my cell phone turned on ok. So I tried to install magisk and it bootloops, do you have any solution to make magisk work in a custom ROM? On my ROM, the stock works perfectly
Sorry for my English, I'm translating from the translator
Click to expand...
Click to collapse
I have Umidigi A9 pro Android 10 how can I update it to Android 11?

Sirkev said:
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't
Click to expand...
Click to collapse
Can you please help me I have Umidigi A9 pro Android 10 how can I update it to Android 11 ?

Sidrickel_SD said:
I have Umidigi A9 pro 2020 with Android 10 is there any way I can Update it to Android 11?
Click to expand...
Click to collapse
Not sure what model you have, but if it its the 2020 64G (NON "E") model, then the newest firmware available is - "UMIDIGI_A9_PRO_64GB_V1-0_20220325"
No clue if the ROM is Android 10 or 11, but if it's 10 the only way you're ever getting 11 or higher on that device is to build it yourself... Not a simple task...even if you're already experienced with building ROMs.
Go here to see firmware (ROM) downloads for all Umidigi models - https://community.umidigi.com/forum.php?mod=forumdisplay&fid=125
Good luck!

GooballDiesel said:
Not sure what model you have, but if it its the 2020 64G (NON "E") model, then the newest firmware available is - "UMIDIGI_A9_PRO_64GB_V1-0_20220325"
No clue if the ROM is Android 10 or 11, but if it's 10 the only way you're ever getting 11 or higher on that device is to build it yourself... Not a simple task...even if you're already experienced with building ROMs.
Go here to see firmware (ROM) downloads for all Umidigi models - https://community.umidigi.com/forum.php?mod=forumdisplay&fid=125
Good luck!
Click to expand...
Click to collapse
Thanks for the reply I really Appreciate it and yes it's the non e version, I am curious when making roms for your device do you take the firmware of other device running on Android 11 port it to your phone or you just download The Official AOSP Android GSI from Google and modify it? And what is the language when Roming is it Java,Kotlin or Python?

Sirkev said:
thank you, works perfectly, one request though...could you please make a flasjing tutorial for android 12 gsi on the same phone, I have been trying to flash as usual, but I keep getting bootloops on all GSIs I have tried, Android 11 GSIs boot well but the 12 ones don't
Click to expand...
Click to collapse
The umidigi android 11 build does not start the gsi at all, the only ones I tested and worked on were: DotOs(A11) and BlessOs(A11), the rest resulted in bootloops, searching the old a9 pro roms, I found the build with android 10 and I tested gsi on it and it worked very well, but the one rule, which is the flash limit on fastbootd, which is 3,000,000kb, I recommend downloading the compressed file up to 1.1gb after that it will not accept
Here A10: https://www.getdroidtips.com/stock-rom-umidigi-a9-pro/
probably what i explained was confusing and weird, because i'm using translator, more briefly: umidigi's os10 is the best to initialize gsi.
Gsi port oficial/unofficial:https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I tested Miku UI....

GooballDiesel said:
Hey Sirkev,
I am about to start looking into getting Android 12 running on this same device.
Umidigi A9 6GB + 128GB, currently running Android 11.
Please keep me updated with your progress, and I will do the same.
I MIGHT try to compile a custom Android 12 (Possibly even Android 13...) rom for this device if I can find enough time to look into it...
Side question - When you go to Google Play store with YOUR A9 Pro running the stock Android 11 rom, click on your profile picture in top right corner, click "Settings", then expand "About"...
What does your A9 say at the very bottom under "Play Protect Certification"???
Thanks!
Click to expand...
Click to collapse
I'm still on GSI nearly an year since I reflashed stock, but I've always had play protect certification, it was broken when I first flashed dotOs but I found a fix for it

Sidrickel_SD said:
I have Umidigi A9 pro 2020 with Android 10 is there any way I can Update it to Android 11?
Click to expand...
Click to collapse
[How to] flash GSI on Umidigi A7 Pro - Functional Guide
This guide is for flashing GSI on Umidigi A7 Pro device, which was released in 2020 with Android 10. This device supports Project Treble and comes with a super partition that contains system, product and vendor partitions. I tried flashing the...
forum.xda-developers.com
This works just as fine for flashing android 11 and android 12 on umidigi A9 pro(android 10 variant)

Question Beginners step-by-step guide to installing Xiaomi.EU on POCO F3?

I have finally unlocked the bootloader (no guides mention it will wipe my phone at the same time!).
Now I am looking again at Roms, HentaiOS and ArrowOS were contenders but Xiaomi.EU sounds like the best of all factors, a Poco F3 centric, manufacturer update with added functionality and removed bloat.
I have watched several "guides" to install, including this one (
) and this one (
) both seem to assume that I am not retarded!
I would like a really easy, step-by-step guide to how to install this Rom.
Do I need to install ADB? Some people say to load the Xiaomi.EU rom in internal storage but to wipe the phone first, so how would I do that? Some say I should BOOT TWRP, others say I need to install it? huh?
There has to be a "explain it to me like im three years old", guide to this!? ACK!

ArghMonkey said:
I have finally unlocked the bootloader (no guides mention it will wipe my phone at the same time!).
Now I am looking again at Roms, HentaiOS and ArrowOS were contenders but Xiaomi.EU sounds like the best of all factors, a Poco F3 centric, manufacturer update with added functionality and removed bloat.
I have watched several "guides" to install, including this one (
) and this one (
) both seem to assume that I am not retarded!
I would like a really easy, step-by-step guide to how to install this Rom.
Do I need to install ADB? Some people say to load the Xiaomi.EU rom in internal storage but to wipe the phone first, so how would I do that? Some say I should BOOT TWRP, others say I need to install it? huh?
There has to be a "explain it to me like im three years old", guide to this!? ACK!
Click to expand...
Click to collapse
You don't "install" ADB and Fastboot. Those are protocols through which a PC can talk to an Android device for debugging purpose and other purposes like this.
The Fastboot Mode on an Android phone lets you deep system stuff, like modifying partitions (flashing, erasing, etc.)
ADB lets you do more high-level stuff, like removing system apps, granting/removing permissions to apps, pulling/pushing files from/onto storage.
To speak to those protocols, you need the portable Command Line Tools for ADB & Fastboot built by Google:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
First, you unlock the bootloader (which factory-resets your phone, lol),
then you put the ROM zip-file (e.g. Xiaomi.eu Custom ROM) onto the phone storage,
then you reboot your phone into Fastboot Mode (POWER + Volume Down),
then, in Fastboot, you boot TWRP (a Custom Recovery):
Open Command Prompt inside the Platform-Tools folder,
do "fastboot boot TWRP.img" (assuming the TWRP file name is "TWRP.img")
then you flash the ROM inside TWRP,
then you format data & clear Dalvik Cache,
that's it. I hope I haven't forgotten anything.

I'd also like to include some Notes that I have made for myself in a text file:
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
Xiaomi ADB & Fastboot Tools: github.com/Szaki/XiaomiADBFastbootTools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Magisk: github.com/topjohnwu/Magisk
Poco F3 - Clean Install of Xiaomi.eu ROM:
Download Stock ROM (EEA Fastboot) & Xiaomi.eu Weekly
Delete Anti-Rollback Code from Flash_all.bat
Patch Xiaomi.eu boot.img with Magisk
Flash Stock ROM with Mi Flash
Boot System
Boot TWRP @Nebrassy
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
Click to expand...
Click to collapse

dreamytom said:
You don't "install" ADB and Fastboot. Those are protocols through which a PC can talk to an Android device for debugging purpose and other purposes like this.
The Fastboot Mode on an Android phone lets you deep system stuff, like modifying partitions (flashing, erasing, etc.)
ADB lets you do more high-level stuff, like removing system apps, granting/removing permissions to apps, pulling/pushing files from/onto storage.
To speak to those protocols, you need the portable Command Line Tools for ADB & Fastboot built by Google:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
First, you unlock the bootloader (which factory-resets your phone, lol),
then you put the ROM zip-file (e.g. Xiaomi.eu Custom ROM) onto the phone storage,
then you reboot your phone into Fastboot Mode (POWER + Volume Down),
then, in Fastboot, you boot TWRP (a Custom Recovery):
Open Command Prompt inside the Platform-Tools folder,
do "fastboot boot TWRP.img" (assuming the TWRP file name is "TWRP.img")
then you flash the ROM inside TWRP,
then you format data & clear Dalvik Cache,
that's it. I hope I haven't forgotten anything.
Click to expand...
Click to collapse
Good job!
You could almost give us a guide on the dedicated "how to" section
However I read that to start twrp from fastboot using cmd you need to put the twrp(filename).img on the platform tool folder. Right?

RollDload said:
Good job!
You could almost give us a guide on the dedicated "how to" section
However I read that to start twrp from fastboot using cmd you need to put the twrp(filename).img on the platform tool folder. Right?
Click to expand...
Click to collapse
Oh yes, that command also assumes TWRP.img is inside the same folder.
What I do is drag 'n drop the TWRP file into the CMD-window. The full path to the TWRP-file will automatically be written in the CMD-window.

dreamytom said:
Oh yes, that command also assumes TWRP.img is inside the same folder.
What I do is drag 'n drop the TWRP file into the CMD-window. The full path to the TWRP-file will automatically be written in the CMD-window.
Click to expand...
Click to collapse
I remembered well then...
Thanks!
Since I rooted the galaxy s5 I try to carefully read as much information as possible before performing any modding operation.
Both from the positive and negative experiences of the users it is possible to avoid errors and bricks.
In a few hours I can unlock the bootloader and move to the stable of xiaomi.eu, I can't wait

I went from "miui stock 12.5.3" EEA to "xiaomi.eu stable 12.5.6." and everything went well!
The steps I took are as follows:
1) I have unlocked the bootloader;
2) I copied the image of the latest TWRPnebrassy recovery in C: \ platform-tools;
3) I copied the .zip file of xiaomi.eu-12.5.6 in the phone memory;
4) After enabling usb debug I restarted the phone in fastboot and connected it to the pc;
5) in the "C: \ platform-tools" folder, I started a cmd window;
6) in cmd I typed the following command
Code:
fastboot boot TWRP.img
Then the phone rebooted into TWRP;
7) "in TWRP" I went to "INSTALL" and selected the .zip file of the rom and started the flash;
8) Completed the flash (it takes a few minutes) I went to "WIPE" and I formatted "data";
9) Subsequently I rebooted in the system (the first start takes a few more minutes, wait);
Done;

Can vasishasht's TWRP be used instead of Nebrassy's?

Dhruv.m said:
Can vasishasht's TWRP be used instead of Nebrassy's?
Click to expand...
Click to collapse
Yes. They're both TWRP 3.5.2, but they are still different from each other.
With Vasishoth's you may get "Failed to mount" errors right at the start.
If you face any errors, you can always switch TWRP.

also, can this be flashed directly from an AOSP ROM?

@Dhruv.m Xiaomi.eu can't be dirty-flashed on an AOSP ROM, if that's your question.
There's a low chance that it may boot, but it'll be broken & unusable.

dreamytom said:
@Dhruv.m Xiaomi.eu can't be dirty-flashed on an AOSP ROM, if that's your question.
There's a low chance that it may boot, but it'll be broken & unusable.
Click to expand...
Click to collapse
Nah I'm not asking that, I'm asking that do I need to go back to MIUI before flashing xiaomi.eu or can it be installed cleanly from an AOSP ROM?

Dhruv.m said:
Nah I'm not asking that, I'm asking that do I need to go back to MIUI before flashing xiaomi.eu or can it be installed cleanly from an AOSP ROM?
Click to expand...
Click to collapse
That's right what @dreamytom says, I personally haven't tried vasishasht's, so I can't tell you.
I know that the xiaomi.eu flash works well if you start from the stock, starting from an aosp I don't know, errors could arise, so I would avoid.
I used the nebrassy one because the xiaomi.eu installation package flashes the nebrassy twrp, so it seemed like the right choice.
So I advise you to install the .eu starting from a stock miui.