Database Info

Xiaomi Black Shark Support/MEGATHREAD

Welcome!
This Megathread is to help bring the different threads together for the Xiaomi Black Shark (SKR-A0 or SKR-H0) since the xiaomi-black-shark tag is broken (at least for me it is). This will also serve as a one-stop shop for people who need general black shark support!
Disclaimer: You (the user) assume the risk for any bootloader unlocking, rooting, or any other modifying of your device. These can lead to phone's being bricked or boot-looped. We aren't to blame if the directions aren't followed to the T!
Tips before modding your phone
1. Stay organized! Make a folder for any files you download or data your backup so you don't lose anything important
2. Backup your user data onto your computer. It is guaranteed 100% of the time that your phone's data will be wiped when installing of uninstalling ANY of the modifications listed below. Unless you have been rooting and unlocking bootloaders for years, you don't want to skip this step.
Common ADB and Fastboot Commands
These are some commands you'll need to get to know:
adb devices: this shows what devices are currently connected to your computer
adb pull: this pulls a file from your phone and saves it to a location on your computer. You will need to specify the location of the file and the save location of the file
adb reboot bootloader: this reboots the phone into fastboot mode to use fastboot commands
fastboot devices: this shows what devices are connected to your computer in fastboot mode
fastboot boot filename.img: this boots the phone with using a image file of your choice
fastboot flash disk_partiton filename.img: this will flash an image file over the disk partition you want.
Example:
fastboot system system.img flashes a new system_a.img over the system parition of your phone's storage. This is where the main operating system is held on the phone.​fastboot reboot: reboots the phone
fastboot continue: boots the phone straight from fastboot into the system, not restarting the phone.
Unlock/Relock your Bootloader
WARNING: This WILL wipe your internal data
On Android, the phone must have an unlocked bootloader to enable some of the common modding features. These steps will unlock your bootloader.
Pre-requisites:
1. You will need the SDK Platform Tools downloaded onto your computer. This has the necessary adb and fastboot programs you will need in order to unlock your bootloader.
2. Enable Developer Options on the Phone
-Go to Settings -> About phone and tap the Build Number 7 times to enable Developer Options
3. Enable OEM unlocking
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
4. Enable USB Debugging. This lets you use ADB (Android Debugging Bridge) to send commands from your computer to the phone.
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable USB debugging.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable USB debugging.
5. Boot into fastboot mode.
-Booting from the Phone:
Turn the Phone off
Press and hold the Volume Down Button
Turn the phone on while holding the volume down button
-Booting from the PC:
Connect your phone to your computer.
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: adb devices
A pop up should show up on your phone. Click the checkmark next to "Always allow from this computer" and click ok. Your computer is now allowed to send commands to the phone.​
Now run the command: adb reboot bootloader
You should now be in fastboot mode!
To check if you're in fastboot mode:
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: fastboot devices
If your device shows up then you're in fastboot mode! You should also see a line of text that says something like:
"Bootloader Locked"
"Bootloader Unlocked"
Unlocking your Bootloader:
1. If your phone says bootloader is locked:
While connected to your PC run the following commands:
-For SKR-A0
fastboot oem unlock
-For SKR-H0
fastboot flashing unlock
If there is a warning click to proceed with the unlock. THIS WILL WIPE YOUR DATA AT THIS TIME.
If your phone says bootloader is unlocked:
Skip this step!
Your Bootloader is now Unlocked!!
Relocking your Bootloader:[/size]
1. Boot into fastboot mode
2. Connect your phone to your computer
3. Run the Bootloader Lock command
3a. For Both Versions
fastboot flashing lock
WARNING: THIS WILL WIPE YOUR DATA.
Your bootloader is now Locked!
Rooting Using TWRP
Unlocked Bootloader Required!
Required files:
The latest Magisk Zip and APK files...it can be found here
A Computer with the latest SDK Platform tools
TWRP image file found at this thread
Do NOT download the installer.
1. Boot into fastboot mode and connect to your computer
2. Run the command: fastboot boot Name_of_twrp_file_.img
Replace Name_of_twrp_file.img with the name of the twrp image file you've downloaded for the blackshark
Tips:
If your screen is upside down, that's ok! Your touches will be in the same spot, the image is the only thing that's upside down.
On first boot, if TWRP is asking for a decryption password, you will need to wipe your data before going forward.
3. Move the Magisk Zip file to your phone's storage
4. On TWRP:
Click install -> Magisk.Zip file -> Swipe to confirm flash
5. After the install is complete: Swipe to reboot the phone
DO NOT INSTALL TWRP APP IF IT ASKS YOU TO
6. After the phone reboots, install the Magisk apk file
7. If you start the magisk app and it says Magisk is not installed, try rebooting your phone.
8. If you start the magisk app, and it asks to download extra resources, click ok.
You're now rooted!
Install GApps
Installing GApps should only be for the CN version!
You can find the directions and required files in this thread here
Factory Images
For the CN version (SKR-A0)
The factory images can be found on Google Drive here
For the Global version (SKR-H0)
[Guide] Restoring Black Shark 1 Global to Stock OTA bug fixed!
Using Project Treble (GSI) System Images!
What is Project Treble and GSI?
The Generic System Image (GSI) was added into Android 8.0 devices to enable OEM partners and developers to help with updating devices. Using an dual system approach (slot a and slot b) android phones can be updated seamlessly (without rebooting) and recover devices from a bad update.
Project Treble is an extension of this feature to enable developers to update their OS easier to new versions of Android! This includes *drum roll* the ROM commmunity!! So if your phone supports project treble and gsi (which the Black Shark does) we already have ROMs available to us!
The Downside to Project Treble Roms
Our Vendor File isn't compatible with Treble ROMs and we can't use other vendor files (as what I have seen so far) so these bugs will exist for now:
The S logo doesn't turn off. Stays Green lit.
You may not be able to increase screen brightness.
Fingerprint may not work on the Treble ROM.
Installing a Project Treble Rom
YOU WILL LOSE YOUR USERDATA. THERE IS NO GETTING AROUND THIS AS OF NOW.
Prerequisites:
Unlocked Bootloader on your phone and adb, fastboot, TWRP image and the most recent Magisk Zip on your computer.
For CN variants (SKR-A0) you may need to use the Global (SKR-H0) vendor and boot images. These steps were tested on using the Global Images
1. Choose your rom over here
2. Download the ARM64 A/B version of your rom of choice. The Black Shark supports Seamless Updates and it's based on the 64bit architecture (as are most modern phones).
3. Factory Reset your phone. You can do this either through the recovery or through the system settings.
4. Boot into bootloader mode on the phone and connect the phone to the PC.
5. Erase the system partition: fastboot erase system
6. Flash the new system OS: fastboot -u flash system system_image_file.img
7. Boot into TWRP from fastboot: fastboot boot twrp_file.img
8. Tap the DO NOT ALLOW SYSTEM MODIFICATIONS
9. Move the Magisk Zip file to your phone.
10. Click Install -> Magisk Zip -> Swipe to Install
11. Reboot the Phone
That's it! Your screen will be upside down during the media locking process (using a Disable Force Encryption file has not worked for me). Once your get to the setup page you may have to set it up with the screen upside down. THIS IS THE SAME AS HOW TWRP IS UPSIDE DOWN BUT THE TAPS ARE IN THE NORMAL SPOTS. If a warning comes up that's normal.
Android 9.0 Pie News!!!
https://forum.xda-developers.com/android/development/news-black-shark-2-features-coming-to-t3924703
How to Get CN Rom's Shark Space and MI Market onto Global ROM:
https://forum.xda-developers.com/an...-cn-shark-space-mi-market-blackshark-t3927854
Credits:
TWRP by @mauronofrio
Offical XDA Magisk Thread
@gilbert32 for factory global images

Placeholder
---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.

gilbert32 said:
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Click to expand...
Click to collapse
No problem!
The CN version gets messed up on the OTA if your active boot is on B. It seems the OTA updates only work with active boot A. It also gets messed up obviously if the backup boot is not the same version. I had to make sure both system_a and system_b were on CN before updating system_a with the OTA.
Hope this helps.. obviously I'm a CN user, but you never know! :good:
gilbert32 said:
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
Click to expand...
Click to collapse
I already have a linux environment in the works...

I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.

gilbert32 said:
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
Click to expand...
Click to collapse
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!

JengaMasterG said:
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
Click to expand...
Click to collapse
AFAIK, it's gonna be pretty hard to build without having the kernel sources. Unless they release them soon, building for the device directly is gonna be a long shot.
However, checkout the treble device forums. You can download and flash roms from that section, and they will probably boot, but you'll have problems with auto brightness, random reboots, etc.
I still can't get the auto brightness and device specific stuff to work.

I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.

a8530516 said:
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
Click to expand...
Click to collapse
can you share how you did it here?

JengaMasterG said:
The Model version is set by the vbmeta.img files. You should be able to find those here under the factory image files section.
If you want any future support, ask for it in in the megathread so we can keep all the support in one thread :good:
Click to expand...
Click to collapse
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks

khususgw said:
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
Click to expand...
Click to collapse
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.

JengaMasterG said:
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
Click to expand...
Click to collapse
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks

khususgw said:
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
Click to expand...
Click to collapse
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.

Reply:
Xiaomi Black Shark support are the thing which people need to know now a days world is evolving and things are changing rapidly.

JengaMasterG said:
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Click to expand...
Click to collapse
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks

khususgw said:
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
Click to expand...
Click to collapse
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.

JengaMasterG said:
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
Click to expand...
Click to collapse
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a

khususgw said:
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
Click to expand...
Click to collapse
Yeah you can do it that way!

JengaMasterG said:
Yeah you can do it that way!
Click to expand...
Click to collapse
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.

khususgw said:
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
Click to expand...
Click to collapse
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.

JengaMasterG said:
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
Click to expand...
Click to collapse
after i try flash from scratch
and using old vendor b
still i cant do the OTA update

Lenovo S5 Pro - L58041 (Global) [2020.03.21]

Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!​
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***​
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.​
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***​1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***​1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!​
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!​
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***​
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
​
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** ​1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)​
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***​1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!

Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.

kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto

kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.

Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.

kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?

Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.

kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.

Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:

kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.

Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.

kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.

After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"

kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.

Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).

good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g

nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!

Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...

How To Guide [GUIDE][UNLOCK][ROOT] How to unlock bootloader, flash ArrowOS v11.0 ROM and root Xiaomi Poco X3 Pro

If you've recently purchased a Xiaomi Poco X3 Pro, but were on the fence about using it until an AOSP ROM became available then you're in luck. Kudos to @kubersharma for his contribution by providing us the first official AOSP release, ArrowOS v11.0 [vayu].
Now, throughout this guide, I have linked the page or post based on information I gathered to put this guide together in order to credit that person instead of having to name drop them individually. These are fully detailed instructions to make it easier for newbs.
I've spent the better part of my day figuring all of this stuff out so hopefully you won't go through the trouble I did. PLEASE DO NOT PM ME FOR HELP. REPLY TO THIS GUIDE BELOW, THANKS. NOW LET'S BEGIN!!!
UNLOCK BOOTLOADER
1. Unlock the bootloader with Xiaomi Unlocker tool.
a. Be aware this process will factory reset the device before proceeding.
b. Download the Mi Unlock app onto your PC. Extract the contents within the zip file into an empty folder then run the app.
c. Register for Xiaomi account and sign in with your Mi Account.
d. Your Mi Account must be added to your Mi Settings
Sign into your Mi Account on the device.
Go to Settings –> About Phone –> tap on MIUI version (For POCO) until it says Developer options is enabled.
Back out of About Phone, Additional Settings –> Developer options –> Mi Unlock status.
Agree, then "Add account and device".
e. Shut down your phone manually, and hold Vol down + Power button to enter Fastboot mode.
Download and install the latest Xiaomi USB Drivers or here (or Google's latest USB drivers for Windows if all else fails) for your PC.
Connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface" (in Device Manager), and click "Unlock" in the Unlock app.
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
f. After your first initial unlock attempt, you MUST wait 168 hours before unlock process can fully complete.
Wiping the device or removing the Mi account from the device could result in the timer being reset.
g. After the waiting period expires, click "Unlock" in the Unlock app. You will notice the phone will restart followed by subsequent different screens during the phone's boot sequence including the "POCO" screen which now displays an "open lock icon" at the top, indicating your bootloader unlock attempt and will eventually end up on a "This device is locked" screen where you have to confirm you are the device owner by entering your Mi Account password to "activate this device"; connect to your WiFi prior to doing so if the device lacks an active sim card.
FLASH CUSTOM RECOVERY, DECRYPTION DISABLER, & ROM THEN ROOT
2. Download the Official ArrowOS v11.0-vayu fastboot ROM for POCO X3 Pro [direct link here].
a. NOTE: ArrowOS requires MIUI V12.0.4.0 firmware so it recommended to downgrade to this version before flashing ArrowOS otherwise the ROM may not boot.
b. Choose the GApps build type which "includes Play services and now some AOSP apps have been replaced with GApps... All GApps packages and other[sic] files [were] extracted from original firmware images for Pixel4XL (coral)."
3. [OPTIONAL] Download the latest version of Encryption Disabler then copy it along with the fastboot ROM into a folder named 'TWRP' on the root of your microSD.
4. Ensure USB Debugging is already enabled on your device (in Settings –> Additional Settings –> Developer options).
5. Remove any screen unlock (i.e., fingerprint, PIN, pattern or password) in MIUI.
6. Power off device and put it in Fastboot mode (Vol down + Power button).
7. Download the latest SDK Platform Tools from Google for adb compatibility and create a folder called "adb" in the root of the "C:\" drive.
a. Extract the files adb, AdbWinApi.dll, AdbWinUsbApi.dll, and fastboot into the folder.
b. Ensure the latest USB drivers are installed for your PC, connect the device to the computer via USB cable, and confirm that your phone shows up recognized as "Android Bootloader Interface".
c. Launch "Command Prompt" on your PC and run the command:
cd C:/adb
To show a list of devices (including your phone) connected to your PC, enter the command:
fastboot devices
8. Download the unofficial Pbrb (test3) recovery file (PitchBlack Recovery Project 3.1.0 unofficial) by Alex Besida and copy it into the ADB install folder and rename it to "recovery.img".
9. Flash custom recovery file in CMD, run commands:
fastboot flash recovery "recovery.img"
fastboot boot recovery.img
10. Your device should automatically boot into custom recovery. At this point, the microSD will become accessible from recovery or the PC, but the device's internal storage will not be which makes using a microSD card much more imperative for this process since the recovery is in early access development.
a. Go to Wipe –> Format Data, type "yes" to perform data wipe; Back out to the main menu.
b. Go to Install –> Navigate to the TWRP folder on the microSD (via "external_sd").
Select "Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip" and flash the ROM, but do not change any of the checkboxes that show up before doing so.
Format data (not wipe) before rebooting into the new ROM.
NOTE: At most it takes around 1 minute to boot back up.
11. [OPTIONAL] Power off the device and boot back into recovery.
a. Go to Install –> Navigate to the TWRP folder on the microSD.
Select " Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" and flash it, but do not change any of the checkboxes that show up before doing so.
NOTE: This will disable forced encryption of data partition for better performance and internal SD + Data mounting in TWRP. It's not needed for the ROM to work, but due to disabling encryption it compromises security.
Reboot into the new ROM.
12. After going through the phone's boot sequence, you'll be presented with the initial phone setup process onscreen where you can begin recovering your data.
13. Go to Settings –> About phone –>tap on Build number until it says Developer options is enabled.
a. Back out to Settings –> System –> to access Developer options –> Enable USB Debugging.
14. Installing Magisk via custom recovery will fail in the background, resulting in an unresponsive "POCO" screen which is caused by installer scripts not being able to properly detect the correct device info or the recovery environment does not meet its expectation. In this case, you will need to use the Patch Image method as it is guaranteed to work 100% of the time. Installing Magisk through custom recoveries on modern devices is no longer recommended due to this reason.
a. Pull down the Notification Bar from the top of the screen and change "Charging this device via USB" to "File Transfer".
b. Open " Arrow-v11.0-vayu-OFFICIAL-20210424-GAPPS.zip " and copy "boot.img" to the phone's internal storage.
c. Download the latest version of Magisk (Magisk v22.1) and copy it to the phone's internal storage and use the native "Files" app to install the apk.
NOTE: Magisk binaries (ZIP) are now included within Magisk Manager APK file. Now you don’t have to download it separately. You can install the .apk file or rename its extension to .zip then flash it through custom recovery / TWRP.
d. Launch Magisk from the app drawer and go to "Install" under Magisk –> "Select and Patch a File," select the "boot.img" you copied internally –> "LET'S GO".
e. Copy the generated patched file to the ADB folder and flash it via fastboot by running the following commands:
cd C:/adb
fastboot flash boot boot.img
f. Reboot into the new ROM and voila!
fastboot reboot
g. Use an app such as Root Checker or BusyBox Checker (from the Play Store) to confirm root status.
h. To bypass/restore SafetyNet validation, open the Magisk app, go to Settings (cogwheel icon) and enable MagiskHide.

SIDENOTES:
These are either my comments or other user's comments that may be considered helpful as it relates to ArrowOS
Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro (Credits to @pl1992aw)
Using TWRP to install OTA Updates
Installing OTA updates
Stability of 'PitchBlack Recovery Project' Recovery
How to verify SafetyNet status
Feel feel to let me know of other threads or comments that are also related to installing ArrowOS.

Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here

kamild_ said:
Excellent guide
My suggestions in terms of improvements:
- 7-day waiting time before unlocking: I would mention that wiping the device or removing the Mi account from the device could result in the timer being reset;
- DFE/Encryption Disabler: it's optional, not needed for the ROM to work and thanks to disabling encryption it compromises security;
- Firmware: Arrow OS requires MIUI V12.0.4.0 firmware, so before flashing Arrow OS it's recommended to downgrade MIUI to this version, otherwise the ROM might not boot
In the future, once more custom ROMs come out, it should be easy to turn this guide into general flashing instructions instead and not just for Arrow OS, which would be a great resource to have here
Click to expand...
Click to collapse
Fair enough, thanks for the suggestions. I can add them in.

Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?

Aulig said:
Thanks for this detailed guide! I'm currently on MIUI 12.0.2 - do you know if I have to update to 12.0.4 first or if I can follow your guide directly?
Click to expand...
Click to collapse
Yes, you have to update to MIUI 12.0.4.0 before flashing.

How stable is the PBRP Beta? Great Guide btw

DeblaGaming said:
How stable is the PBRP Beta? Great Guide btw
Click to expand...
Click to collapse
More stable than other unofficial custom recoveries such as OrangeFox, especially when it comes to functionality. Based on my experience using OrangeFox, it failed to flash anything that was already present on my microSD, but PBRP worked OOB w/ no issues first time, and allowed me to copy over files onto the microSD while the device was in recovery while simultaneously being connected to my PC. Thanks btw.

AusVGM said:
Yes, you have to update to MIUI 12.0.4.0 before flashing.
Click to expand...
Click to collapse
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide

Aulig said:
Thank you, I did that now and then followed the guide (without disabling encryption as that's an important feature to me). Super easy to follow even though I haven't been modding a lot these past years. Worked perfectly, thanks @urbanman2004
Tip: make sure to check safetynet with an app and not magisk, as described in the thread linked regarding magisk hide
Click to expand...
Click to collapse
Thanks for the compliment... I didn't feel the need to include how someone could check their device's SafetyNet status, but the app I use is called SafetyNet Helper Sample in the Play Store.

Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone

bla.tiga said:
Very detailed instruction thumbs up...
My questions
1. For miui requirement the MIUI V12.0.4.0 , is it free or need specific version like chinese or europe or asia or america for more clearly
2. In future when twrp or custom recovery available , can we just flash the rom via recovery as simple as that. Like other phone
Click to expand...
Click to collapse
Thanks for the compliment. To answer your questions:
1) Any version of MIUI V12.0.4.0 will do.
2) To flash future OTA updates (ROMs), it will require flashing the "compatible recovery" (vayu ArrowOS Recovery) in fastboot mode, rebooting the device then followed by installing the OTA update once it becomes available and letting it flash automatically.

hello all,
I have flashed vanilla version of ArrowOS, and magisk...
could somebody help me with installing microG for VANILLA build ROM? I'm new to microG stuff, so I don't really know from where should I install, what version etc.
some apps are not running as they require Google play services

I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.

as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
Best that your question be taken up w/ the devs.

as400l said:
I have asked this question elsewhere but maybe somebody here has some experience. Is it possible to install ArrowOS OTA with another TWRP than from ArrowOS ?
I'm asking because this AOS TWRP is very limited in functionality.
Click to expand...
Click to collapse
So I have some breaking news:
I can confirm that the latest unofficial alpha version of TWRP (TWRP-3.5.1-vayu-Nebrassy-1) is capable of decrypting and reading internal storage. Due to this advancement, I can also confirm that ArrowOS OTA updates will officially work using TWRP. There is NO NEED TO USE ANY OTHER CUSTOM RECOVERY BESIDES TWRP.

Hi everyone, i have one dubt in unlock bootloader process...
When phone wipe /data partition???, after or before wait the time to unlock???

Let's remain on topic and avoid bickering.

My bootloader unlocks in 4 days and I am planning to change the room using your guide. I have a doubt, I am a beginner. can I do step 8 with TWRP instead of Pbrb (test3)? Would the steps be the same with the change?

@newbrn of course. Pitch Black is literally a dark themed TWRP with some tweaks.

How To Guide [MIUI12~13 A11~12.0/12.1][UNLOCK][ROOT] Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro

Thanks for @urbanman2004 guide for Poco X3 Pro. Some sentences still needed, so keeping it similar.
This guide provides photos & screenshots.
Simulate all process and reduce misunderstanding.
Spoiler: Disclaimer
* May loose warranty after unlock according to Xiaomi policy of the country you bought phone from. Check it yourself.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected users.
Section 1: Unlock bootloader
(Works for most Xiaomi/Redmi/Poco phones)
Keep phone with more than 60% battery.
Spoiler: Click to show
1. Register Xiaomi account on PC or Phone doesn't matter. (Use same account in all steps)
Might ask SMS verification. Keep phone number for this Mi Account until all unlock process done and successfully booted into MIUI after step 21.
Click to expand...
Click to collapse
2. On phone, sign in your Mi Account from setting. (Use same account in all steps)
Spoiler
{
"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"
}
3. Turn on Developer option:
Spoiler
Settings→ About Phone (My Device)→ tap on MIUI version (For POCO) until it says Developer options enabled at the bottom.
4. Turn ON "Find my device"
Spoiler
5. Back out to Settings, Additional Settings→ Developer options→ Mi Unlock status.
Spoiler
6. DON'T DO STEP 6 ANYMORE after done it ONCE. Will reset countdown timer if you do that.
DON'T DO STEP 6 ANYMORE after done it ONCE. Will reset countdown timer if you do that.
SIM card inside phone with mobile data doesn't need to be the one linked to Mi-account. Can put a different SIM card as long as it can use mobile data.
Only during step 6 you turn off WIFI and turn on mobile data.
Can do whatever you want to WIFI and mobile data anytime before and after step 6. There's no restriction other than step 6.
Can remove your SIM card once step 6 was done. But you still need the number linked to Mi-Account accessible to receive SMS if Mi-Account ask for verification.
7. Wait for 7 days (Day 1). DO NOT LOG OUT your Mi-Account on your phone.
Try not to use phone too much as later will do factory reset and loose all data.
Or backup manually. Not gonna write how to backup.
No need to connect internet (mobile data and WIFI) all the time.
Can use your phone
Can even power off phone in the meantime. (Thanks for @kamild_ answer)
Spoiler
8. Wait for 7 days (Day 2). DO NOT LOG OUT your Mi-Account on your phone.
9. Wait for 7 days (Day 3). DO NOT LOG OUT your Mi-Account on your phone.
10. Wait for 7 days (Day 4). DO NOT LOG OUT your Mi-Account on your phone.
11. Wait for 7 days (Day 5). DO NOT LOG OUT your Mi-Account on your phone.
12. Wait for 7 days (Day 6). DO NOT LOG OUT your Mi-Account on your phone.
13. Wait for 7 days (Day 7). DO NOT LOG OUT your Mi-Account on your phone.
14. Download Xiaomi Unlock tool for Windows PC.
Direct download link (English Version 5.5.224.55)
Spoiler
Spoiler: Linux and macOS users
XiaoMiTool (v2)
https://www.xiaomitool.com/
https://github.com/francescotescari/XiaoMiToolV2
15. Extract all files into short-named folder. Go into folder and double click on miflash_unlock.exe
Different versions, double click on batch_unlock.exe
Spoiler
16. Sign in your Mi Account. (Use same account in all steps)
Spoiler
17. Connect phone with official USB cable to PC. Check on PC if see device.
Turn OFF all locks (screen lock, face lock, fingerprint, pin, bluetooth lock.)
Turn ON "Find my device"
Logout Google
If not detected, do as in spoiler:
Spoiler
Double click on MiUsbDriver.exe
Should see your phone now.
Reboot your PC.
or Google's latest USB drivers for Windows if it else fails
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
Backup your data from your phone now. You will loose ALL your data on your phone after step 20.
Click to expand...
Click to collapse
18. Shutdown/ Power off phone normally manually.
When screen turns all black for about 30 seconds, hold Vol down + Power button together to enter Fastboot mode.
(Picture from GSMarena)
Should see Fastboot on phone screen
Spoiler
19. Connect your phone with official USB cable to PC. Should see on PC a device listed. (Locked)
Spoiler
If not detected, do as in spoiler:
Spoiler
Double click on MiUsbDriver.exe
Connect phone to computer via official USB cable, and confirm your phone shows up recognized as "Android Bootloader Interface" (in Device Manager)
Reboot your PC.
or Google's latest USB drivers for Windows if it else fails
NOTE: If Windows does not recognize the device due to it automatically installing the wrong "Kedacom Device Driver" then you will have to manually install the drivers for "Android ADB Interface/Android Bootloader Interface".
WARNING !!! From the step later, you will loose ALL your data on your phone. Backup your data from your phone.
Click to expand...
Click to collapse
Take out microSD card from device in case something went wrong and destroy microSD card.
Click to expand...
Click to collapse
20. Press Unlock, Unlock, Unlock anyway, Unlock anyway. (If you are worried of what it's warning you, don't unlock and don't think of custom Roms or root.)
Spoiler
If see this or some hours left, wait for remaining countdown hours (count it yourself) and start from step 17 again.
The countdown is done on Xiaomi server. Can close the unlock program during the meantime.
Exit Fastboot mode:
Spoiler
Unplug phone from PC and hold power button until screen turns black. Will boot into MIUI.
21. Wait phone boot up, or press Reboot phone if it did not reboot itself.
If you see this after boot up, use Wifi or insert SIM card with mobile data access and enter your Mi Account password.
##End of Unlock Bootloader process
Donate if you find it helpful: paypal.me/pl1992aw

Updated to work with MIUI 12~13 or Android 11~12.0/12.1 custom ROMs
Unlock bootloader to do the followings.
Keep phone with more than 60% battery.
Section 2: Clean Flash custom ROMs
(Official Recovery ROMs can be flashed with same method)
Spoiler: Click to show
Make it simple using program mentioned in INDEX thread.
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
If you don't trust the tools or link below,
upload files to Virus Total
or turn on Antivirus
or do manual way urbanman2004 written.
1. Download here:
https://androidfilehost.com/?fid=8889791610682940341
Original github source: (not maintained anymore)
https://github.com/Szaki/XiaomiADBFastbootTools/releases
Spoiler
2. For this program to work, install Oracle Java or OpenJDK (Mentioned in Readme)
Spoiler
Here use Windows to as demo.
Oracle Java download here or here (Choose either one to install)
Spoiler
Double click and install that on your Windows.
3. Keep PC connected to internet, find XiaomiADBFastbootTools.jar downloaded and double click on it.
Spoiler
4. Will automatically download SDK Platform Tools.
5. Turn ON USB debugging in Developer options (access mentioned in Unlock bootloader step 5)
Spoiler
Logout Mi Account, Google, all accounts.
Remove all fingerprint, PIN, password, picture password.
Turn OFF Find My Device function.
Backup your data from your phone.
Click to expand...
Click to collapse
6. Connect phone to PC, swipe down notification on phone and tap MTP/ File transfers
Spoiler
Or
If it's your first time doing this, should see this screen. Choose "Always allow from this computer" and press OK.
7. Confirm on PC to see information of your device.
8. Find custom ROM and read all reply and original thread of the Custom ROM. Sometimes firmware requirement and updated info is in replies.
(Step 8, 9 and 12 and links are POCO X3 pro specific)
Click to expand...
Click to collapse
ArrowOS as example: Download on PC Official ArrowOS -vayu ROM for POCO X3 Pro [direct link here].
Check the date and version as well.
Spoiler
If phone is not on MIUI version for required firmware, do additional as spoiler:
Spoiler
Download on PC official MIUI Recovery ROM or MIUI by Xiaomi.eu ROM ZIP (2~6 GB) of POCO x3 pro.
EEA is official ROM
Xiaomi.eu is custom ROM
Click to expand...
Click to collapse
9. Download recovery TWRP from here by Nebrassy for POCO x3 pro.
10. On PC, press "Device" -> "Reboot to" -> "Fastboot"
Should see Fastboot on phone
Spoiler
11. Program on PC should jump to Fastboot tab
If it did not jump to that tab,
Spoiler
click on Fastboot tab and choose "Option" -> "Reload device"
Warning !!! Look at the Anti version:
This is important for Xiaomi/Redmi/Poco phones.
Spoiler: About Anti version
Only Official MIUI ROMs may have ARB index.
Customs ROMs should not have ARB index.
If your device is Anti version: 2,
1) you can flash Rom with Anti Roll Back (ARB) index: 3, 4, 5, 6... etc. and the Anti version will become 3, 4, 5, 6... etc.
2) you can flash Rom with ARB index 2, and the Anti version will remain 2.
3) you CANNOT flash Rom with ARB index 1. Don't use that ROM in anyway, flashing through custom recovery will likely brick your phone.
4) If ARB index is 0, that means no ARB of that ROM. It will not check or change your device Anti version.
Make sure look at ARB index of MIUI ROM and Anti version of your phone. I don't have your phone. You decide to flash.
How to check ROM ARB index is written in the Source.
Source:
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
12. Assume confirm MIUI ROM safe from ARB, click
Choose
for Poco X3 pro.
Change next drop down menu to "recovery".
Do not choose wrong option, or may be in BIG trouble.
Press Flash Image (Some device cannot do this step, check at your device XDA tutorial)
Confirm at the Status " Writing 'recovery' Okay "
13. Boot to TWRP
Phone should boot into TWRP.
Spoiler
14. Copy or Drag MIUI and custom Rom zip into phone Download folder for easy finding.
If PC did not see any folders in your phone from "My Computer" or "This PC", use either options:
Spoiler: microSD card or USB OTG
Copy the ROM zip file in and [put microSD into / connect USB OTG to] your phone, then continue to step 15
Spoiler: ADB sideload
A)
B) Connect phone USB cable to PC.
C) On PC, navigate to folder C:\user\your user name\XiaomiADBFastbootTools\platform-tools\
D) Copy or drag the ROMs.zip files into the folder.
E) Hold keyboard Shift and mouse Right Click in the folder blank space, left click Open command window here
F) In the Command enter the following code in the command window:
adb sideload custom_ROM_name.zip
G) After it's done (shown on phone screen), skip to step 16
15. In TWRP on phone, tap Install
Spoiler
If Firmware did not meet needs of custom ROM, do additional in spoiler
Spoiler
Choose Download folder, or press Select Storage and choose microSD card or USB OTG where you put the ROM, then tap on MIUI ROM zip.
Swipe to confirm Flash
After it's done, press back.
In Download folder, or press Select Storage and choose microSD card or USB OTG where you put the ROM, tap on custom ROM zip.
Swipe to confirm Flash
Wait until it's done
16. Press back, back, until you see Wipe, tap it and then tap Format Data.
Type yes, press enter.
17. Press Reboot System. Wait for like 10~15 minutes until initialization setup shows.
## End of Clean Custom Rom flashing.
Dirty Flash / ROM update
Do this only when developer or users said it can.
Spoiler: Click to show
Spoiler: If using Magisk, do this as well
First disable all Magisk module and reboot to prevent issues.
α) Remove ALL fingerprint, PIN, password, picture password, ALL locks
β) Do Section 2 step 15 with the update custom ROM zip file in your phone storage.
If TWRP or OrangeFox cannot see any folders in your phone, use either options:
Spoiler: microSD card or USB OTG
Copy the ROM zip file in and [put microSD into / connect USB OTG to] your phone and do Section 2 step 15 with the update custom ROM zip file, then do step γ
Spoiler: ADB sideload
A)
B) Connect phone USB cable to PC.
C) On PC, navigate to folder C:\user\your user name\XiaomiADBFastbootTools\platform-tools\
D) Copy or drag the ROMs.zip files into the folder.
E) Hold keyboard Shift and mouse Right Click in the folder blank space, left click Open command window here
F) In the Command enter the following code in the command window:
adb sideload custom_ROM_name.zip
G) After it's done (shown on phone screen), continue step γ
γ) When done, do the following:
δ) Then Reboot System.
## End of Dirty flashing.
Donate if you find it helpful: paypal.me/pl1992aw

Unlock bootloader to do the followings.
Keep phone with more than 60% battery.
Section 3: Install Magisk (Root)
Install steps and methods were written by topjohnwu (Magisk author) here, but still putting picture guide for POCO X3 Pro.
Spoiler: Click to show
1. Download Magisk on you phone, click and install.
Spoiler
Or find this and tap it once
A) the Easy traditional custom recoveries way :
(PC/Computer is not needed)
Spoiler
2A. Rename the downloaded APK file extension to ZIP.
Magisk-vXX.X.apk
↓
Magisk-vXX.X.zip
Click to expand...
Click to collapse
3A. Reboot to custom recoveries (TWRP, OrangeFox, etc)
3A-α) manually
Spoiler
Power off your phone, wait until screen turns black,
press and hold Vol+ and Power button Together (most Xiaomi/Redmi/Poco phones) until screen turns on.
(Picture from GSMarena)
keep holding Vol+ button, release Power button until booted into recovery.
3A-β) or with PC program/command
Spoiler
4A. In custom recovery on phone, tap Install
Spoiler
5A. In Download folder, tap on Magisk-vXX.X.zip.
Swipe to confirm Flash
Wait until it's done
6A. Wipe cache/dalvik
Then Reboot System
B) the Pro Patch image way :
(PC/Computer used)
Spoiler
2B. Choose boot.img and extract from custom Rom/MIUI Rom on PC which match current phone OS.
Connect phone to PC and copy that boot.img into phone Download folder.
3B. In Magisk app, click Install. Select and Patch a file.
Spoiler
4B. Copy the patched file to PC somewhere easy to find.
5B. Open PC program XiaomiADBFastbootTools
1) Select image magisk_patched-*****_*****.img
2) confirm selecting the patched image file name
3) choose boot partition in next drop down menu
4) Flash Image into boot partition, Yes.
Wait for "Writing 'boot' OKAY"
6B. Reboot to system
7. Go into Magisk app and check if it's installed.
Spoiler
8. Voila... or can do something more (Didn't feel the difference, though it said Recommended)
9. Reboot. Voila! Enjoy Magisk
##End of Magisk (Root) installation.
Section 3.5: Update Magisk
For Poco X3 Pro, repeat Section 3.
Donate if you find it helpful: paypal.me/pl1992aw

Reserved... Maybe for troubleshoot
Q. Why not use Mi-Flash?
A. Because one may easily accidently Clean All and Lock with different region MIUI and brick the device.
Go Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40 and see how many users brick their device using Mi-Flash.
Be sure to check ARB index of MIUI.
Q. Why flash MIUI with TWRP not Fastboot?
A. To check you actually had unlocked bootloader. Without unlocked bootloader, you shouldn't be able to boot into TWRP.
Q. Widevine issues?
A. Read threads in spoiler:
Spoiler
You can have Widevine L1 on custom Roms.
https://forum.xda-developers.com/t/4267263/page-2#post-84919939
You can lost Widevine L1 on official MIUI Roms even without unlocking or root.
https://forum.xda-developers.com/t/4281695/
Devices supporting Widevine L1 certificate renewal officially:
POCO X3 Pro (vayu) [Stable V12.5.1.0.RJUMIXM+]
* Cetain devices have been losing Widevine L1 certificate randomly. The reason is unknown to us.
* Certificate renewal is done via Settings -> Passwords & security -> Fingerprint unlock -> Fingerprint payments -> Widevine (L1)
https://xiaomi.eu/community/threads/info-widevine-l1-support.61064/
If your device haven't officially receive MIUI update to 12.5.1.0, try Xiaomi.eu
Read also:
https://xiaomi.eu/community/threads/info-widevine-l1-support.61064/#post-606155

Thanks for your efforts bro..

i just unlocked the bootloader of my poco x3 pro 6/128 global stable(VAYU) and tired to root it with Magisk method before that i found a patched file of boot image from a post and i just directly did the flashing now its stuck in the MIUI logo dont know what to do next anyone can help me out with this,,, and im going to attached the boot image aswell try to look at it if its fine and what should i do next.

Faysal_khan_070 said:
i just unlocked the bootloader of my poco x3 pro 6/128 global stable(VAYU) and tired to root it with Magisk method before that i found a patched file of boot image from a post and i just directly did the flashing now its stuck in the MIUI logo dont know what to do next anyone can help me out with this,,, and im going to attached the boot image aswell try to look at it if its fine and what should i do next.
Click to expand...
Click to collapse
Are you sure your phone is Global? Which country?
What version of MIUI?
How did you flash your boot image?
What partition did you flash the boot image into?
Were you using this one? If yes, flash the boot.img from here into your phone boot partition and see if your phone can boot up.
Boot your phone into Fastboot or TWRP. If you can, there's still hope. Do the step in above Unlock bootloader step 18.

pl1992aw said:
Are you sure your phone is Global? Which country?
What version of MIUI?
How did you flash your boot image?
What partition did you flash the boot image into?
Were you using this one? If yes, flash the boot.img from here into your phone boot partition and see if your phone can boot up.
Boot your phone into Fastboot or TWRP. If you can, there's still hope. Do the step in above Unlock bootloader step 18.
Click to expand...
Click to collapse
YES, im dam sure its GLOBAL and im from Pakistan.
it was the MIUI 12.0.4 BUT Before unlocking it i updated to MIUI 12.0.6
ok so i just followed the MAGISK method and i downloaded a patched file from a post now i don't know where to find that post but it was for the MIUI 12.0.6 so i started to flash it through fastboot mode with a PC and i was done with it but when i pass on the command to reboot my phone it took so much time and then i released that it was stuck there in the LOGO . now im downloading the full ROM of miui 12.0.6(fasboot) to see if i can patch the boot image from there and hope it work.

Faysal_khan_070 said:
YES, im dam sure its GLOBAL and im from Pakistan.
it was the MIUI 12.0.4 BUT Before unlocking it i updated to MIUI 12.0.6
ok so i just followed the MAGISK method and i downloaded a patched file from a post now i don't know where to find that post but it was for the MIUI 12.0.6 so i started to flash it through fastboot mode with a PC and i was done with it but when i pass on the command to reboot my phone it took so much time and then i released that it was stuck there in the LOGO . now im downloading the full ROM of miui 12.0.6(fasboot) to see if i can patch the boot image from there and hope it work.
Click to expand...
Click to collapse
How you going to patch boot image if you cannot get into MIUI and use Magisk to patch boot.img?
You will need another phone to do that though.
Safe way is to do a complete clean data format and flash MIUI Rom.

i have another phone to patch it but the problem is what version should be used for patching magisk 22 or the latest one? how to flash miui rom and can i now go back to miui 12.0.4?

pl1992aw said:
Are you sure your phone is Global? Which country?
What version of MIUI?
How did you flash your boot image?
What partition did you flash the boot image into?
Were you using this one? If yes, flash the boot.img from here into your phone boot partition and see if your phone can boot up.
Boot your phone into Fastboot or TWRP. If you can, there's still hope. Do the step in above Unlock bootloader step 18.
Click to expand...
Click to collapse
i flashed the boot image from this attachment and its still stuck in there.

Faysal_khan_070 said:
i have another phone to patch it but the problem is what version should be used for patching magisk 22 or the latest one? how to flash miui rom and can i now go back to miui 12.0.4?
Click to expand...
Click to collapse
Now my suggestion is to do a Clean complete Rom install. So all your data and files will be gone.
If you agree to clean all your data, follow above Clean Flash custom ROMs. Start from step 8. When you need to get into Fastboot, do it manually.
You don't need to download ArrowOS. Download MIUI 12.0.6.0 Recovery Rom and flash through TWRP.
Don't think of Magisk and MIUI 12.0.4.0 just yet. First get back to be able to see MIUI working.

Do I have to keep a SIM card in the phone throughout the entire unlock process? I would be taking it out of my actual daily driver phone so I'm just curious

spookykidmm said:
Do I have to keep a SIM card in the phone throughout the entire unlock process? I would be taking it out of my actual daily driver phone so I'm just curious
Click to expand...
Click to collapse
You don't have to keep that SIM card after you done Unlock bootloader step 6.
You can remove your SIM card once step 6 was done. But you still need to have the number accessible to receive SMS if Mi-Account ask for verification.

Did you lose anything by unlocking bootloader? Like Widevine or something. Also, any special partition or file one should backup before unlocking (Not counting user data)? In Sony phones user have to backup TA partition or they will lose some features.
Thanks in advance

Rapier- said:
Did you lose anything by unlocking bootloader? Like Widevine or something. Also, any special partition or file one should backup before unlocking (Not counting user data)? In Sony phones user have to backup TA partition or they will lose some features.
Thanks in advance
Click to expand...
Click to collapse
Loss from Unlocking bootloader is written in above tutorial.
Partition backup is generally not needed if you do things correctly. For now, even if you have full backup of qcn, maybe can't even restore.
Read here: https://forum.xda-developers.com/t/4276823/post-85014473
Widevine issue, Read both:
You can have Widevine L1 on custom Roms.
https://forum.xda-developers.com/t/4267263/page-2#post-84919939
You can lost Widevine L1 on official MIUI Roms even without unlocking or root.
https://forum.xda-developers.com/t/4281695/

How can I use the Xiaomi Unlock tool on GNU/Linux? I tried using Wine, but I cannot log in.

wertguygywe said:
How can I use the Xiaomi Unlock tool on GNU/Linux? I tried using Wine, but I cannot log in.
Click to expand...
Click to collapse
Third party unlock tools that claim works on Linux and Mac. Trust it or not is your decision, can't tell you about it since it's 3rd party. Didn't use it before.
[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux
[TOOL][WIN/LIN/MAC] MiUnlockTool - Unlock bootloader of xiaomi devices on mac & linux Ciao xda users, I'm here to introduce a new tool of mine, MiUnlockTool. MiUnlockTool is an unofficial tool used to unlock bootloader on Xiaomi devices. This...
forum.xda-developers.com
Or find a Windows PC.
Or find USB drive and make a Windows To Go bootable disk. With this, you can boot from USB that contains Windows inside while not removing your Linux and MacOS.
Xiaomi Unlock tool (provided by Xiaomi officially) had only designed for Windows.

I have the latest arrow os on poco x3 pro now. But magisk failed to be installed.
It rebooted fastboot mode repeatedly after flashing magisk_patched_[random_strings].img.
If I flash original boot.img, it can be rebooted to system.
Below are some error in magisk install log I think:
cp: can't preserve ownership of 'busybox': Operation not permitted
cp: can't preserve ownership of 'magisk32': Operation not permitted
cp: can't preserve ownership of 'magisk64': Operation not permitted
cp: can't preserve ownership of 'magiskboot': Operation not permitted
cp: can't preserve ownership of 'magiskinit': Operation not permitted

This does not work due to a bad Java dependency. @
pl1992aw​

How To Guide How to downgrade rmx3560/3561 and flash India version rom (for Android 13)

I realized that updating version to Android 13 realme ui 4.0 using image flash method will cause brick even hardbrick, downgrading ota to Android 12 version really isn't safe anymore . The main cause is due to the bootloader version of android 13. In this post I will show everyone how to downgrade to Android 12 and make rom transfer from rmx3560 to india version rmx3561
The article I have detailed and easy to understand is pinned by my group
How to downgrade Android 13 (realme ui 4.0) to Android 12 (realme ui 3.0):
STEP 1
1. Download app OPLU see link (I am not authorized to post links here. Instead the app name OPLocalUpdate_For_Android 12)
2. Download the roll back package in your phone and remember the location (leave it out of main memory, not contained in any directory)
3. Open app OPLU - select the setting icon in the top right corner - You will see the downgrade file there - Click select package and click update (it will say wipe all data after update)
4. After restarting the phone, the phone is set up normally, but please download the OPLU application again and download the update package (usually I download the downgrade package, I usually copy it to my computer).
5. Repeat the downgrade operation but still use the downgrade package you just used - Wait for 100% progress and the phone will factory reset one more time.
STEP 2:
Advanced downgrade: required unlocked Bootloader
1. After doing the 5 steps I mentioned above, find the OTA file (zip file that contains payload.bin) of your device and download it to your computer and remember the location.
2. Download Fastboot enhance from github source
3. Plug your phone into the computer - Boot the phone into fastbootd with the command: adb reboot fastboot
4. You will see an interface with China language - you choose English and it must be Fastbootd
5. From the computer screen open Fastboot enhance - you will see on it display the serial number of devices
6. Extract the downloaded OTA file and on the Fastboot enhance screen select flash payload.bin.
–> Wait for the green progress bar to run to 100% then success.
8. On the phone screen we select "wipe data" - Enter the wipe code - Select yes
9. Wait for the phone to reboot => Successful downgrade
(You can use this to flash other firmware)
#Tumodpro
If you have any questions, don't hesitate to message me.

TuLy2702 said:
The article I have detailed and easy to understand is pinned at the following link: Mod edit: TG link removed
If you have any questions, don't hesitate to message me. I will support you all the time.
Click to expand...
Click to collapse
While we appreciate you wanting to share your guide, we would prefer that you share it on XDA rather than directing members to an off site location that requires registration. Thank you.
-Regards: Badger50

So this method only work for ubl device?

can i put Rom from other regions?

Hey bro how you doing, can you make a youtube video instead of writing and send us the link would appreciate it.