Database Info

[STOCK] [MM] Root Xperia Z5 Premium Sony Stock Marshmallow (Android 6.0) Guide

The updated cross-device Sony thread tested with Nougat is here.
Guide updated on 21 October 2016.
PREFACE
First of all, this guide will probably work for all recent Sony phones.
This guide is based on a work of number of people. The information how to get this goal achieved is very sparse and it is scattered across the Internet. There are lot of guides, but typically they require a strong familiarity with many things, so inexperienced users may became confused. I decided to assemble a detailed newbie-friendly guide myself. So here it is.
Get rooted stock Sony firmware is not a straightforward and easy task, but if all steps covered in this guide are performed well, the goal will be achieved. Since the creation of this guide, stock firmware versions got bumped multiple times, but nothing has changed fundamentally in terms of rooting.
In this guide I (and you) will use the stuff from these notable people:
@Androxyde — Flashtool
@IgorEisberg — XperiFirm (integrated into Flashtool)
@Dees_Troy et al. — TWRP
@Chainfire — SuperSU
@tobias.waldvogel — Kernel repack script and DRM fix
@zxz0O0 — iovyroot
The whole process divided into the following steps:
Getting your phone recognized by your computer (driver installation).
Backup your DRM keys.
Unlocking a bootloader.
Flashing stock firmware with Flashtool.
Repacking and flashing a kernel.
Rooting with SuperSU.
Restore your DRM keys.
Optional tasks.
The one thing to consider before the flashing of your Xperia phone is the unlocking of the bootloader. There is the official way of doing this provided by Sony. It's easy and straightforward. Check step #3 below.
Before unlocking, one should know the main caveat: once you have unlocked your phone, you have lost your DRM keys. These keys are used to make certain proprietary Sony functions to work, such as X-Reality for Mobile, camera noise suppression and some others. It is possible to backup your keys in beforehand and restore them once the phone is rooted. This will be covered in this guide.
The repack script mentioned before, incorporates a so called DRM fix which effectively emulates lost DRM keys and most of proprietary functions remain in a working state. This fix will suffice for most users, so you probably may want to root your phone straight away, nevermind the keys. I hadn't myself extracted and restored DRM keys ever, since DRM fix works perfectly for me, so you may want to forget about these keys too. Some users are not ready to just erase them, however. The choice is up to you, but if the camera performance is your sole concern, I can confirm that with DRM fix it works perfectly.
After the completion of this guide, your phone contents will be completely erased, so you may want to backup all what is important to you to some external locations. External microSD card will not be erased, so you may copy your stuff to it. If you are on a rooted Lollipop or older Android, you may want to use some specialized tools like Titanium Backup or like. TWRP also have a nice backup features, if you have one already installed.
The guide was tested on Windows 10 Pro 64-bit and Sony Xperia Z5 Premium Dual-SIM E6883 official model for the Russian market. During the course of this guide you will get a specific firmware for your particular market so don't worry, this guide is market-agnostic. It is even model-agnostic. I believe this guide works for most Xperia phones on the market, but I personally tested it just with my Z5 Premium.
Let's go.
1. GETTING YOUR PHONE RECOGNIZED BY YOUR COMPUTER (DRIVER INSTALLATION)
During the course of this guide, your phone will comminicate with your computer in Fastboot and Flashmode connection modes. When connected in these modes, for the phone to be properly recognized by a computer, you have to provide special drivers. Thanks to Flashtool creators, it comes bundled with generic drivers compatible with all recent Windows operating systems, so at first you should install Flashtool. You can get installer from the official website.
Next, you should install Fastboot and Flashmode drivers for your phone.
One caveat here however, these drivers are not from a "recognized Windows developer", that is they are not Windows-certified, so to get them installed on Windows 8/10, you should reboot with the disabled driver signature enforcement. Use Google to know how to perform this.
Once booted in the aforementioned mode (or in a regular mode if you are still on Windows 7), proceed to the actual driver installation. The drivers are packed into the Flashtool\drivers\Flashtool-drivers.exe executable, but it didn't work on my system, perhaps because it is 64-bit (but feel free to try it yourself), so I simply unarchived it with 7-Zip (right-clicked it and chose 7-Zip > Extract to "Flashtool-drivers"). I got a Flashtool-drivers folder, which contained all the drivers from the executable.
Once drivers are unpacked, connect your phone in a Fastboot mode. Recent Sony devices can boot in Fastboot just like this: shutdown the phone, press and hold Volume Up rocker button and connect USB cable to the phone while the other end is connected to a running PC. The phone's LED will turn blue shortly. That's it, you are in a Fastboot mode. Open Device Manager (Win + X, Device Manager) and check if there is some unknown device (with the name S1Fastboot or something like this).
Double-click this unknown device in the Device Manager, click Update Driver..., then Browse my computer for driver software, and choose the Flashtool-drivers folder created earlier with 7-Zip (leave Include subfolders checked). Shortly you will get a red warning dialog window, which inform you that this driver doesn't have a proper signature:
{
"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"
}
Very scary. Just proceed with the install despite all the red flags, it's safe.
Once Fastboot driver is installed, plug out the USB cable off the phone and connect it in a FlashMode mode. This is done just like for Fastboot, but in this case you should press and hold Volume Down rocker button during the cable plugging in. The LED in this case will be green and not blue. The procedure to install the driver is exactly the same.
After the successful installation, try to reconnect the phone in these modes again couple more times to make sure all devices get properly recognized by Windows. If all seems good, proceed to the next step.
2. BACKUP YOUR DRM KEYS
There is a tool called iovyroot, with which you can backup your DRM keys from an unrooted phone, but at the time of the writing it doesn't support latest firmwares. It does support a lot of older firmwares so it may be useful to not upgrade your phone before checking up this tool.
If you're into this backup DRM thing, go to the original thread, download the latest version and check if it is working for you. For now I just skip this step. Basically, you want to download the zip, connect your phone in USB Debugging mode, run the tabackup.bat script and see the output.
I will not cover DRM keys extraction/restore in details, since I never did it, so I don't want to write about something I haven't myself performed. Please check corresponding threads.
Note that most proprietary Sony features will work even without DRM keys, such as X-Reality for Mobile, camera denoise filter and some others. DRM fix will be covered later in this guide. Some features will not work with DRM fix, Widevine for example. Most users will not even notice these.
3. UNLOCKING A BOOTLOADER
Sony does provide its own guide. It is a plain and simple and — good news! — if you have followed the previous steps, you just got all the prerequisites covered!
4. FLASHING STOCK FIRMWARE WITH FLASHTOOL
The Flashtool was installed on the completion of the first step, so let's start it. If you are on 64-bit Windows, start Flashtool64 (there is a shortcut in the Start menu). It does require administrator privileges.
Once you are in Flashtool, at first you need to obtain the most recent official stock firmware from Sony. Press the "XF" icon (the right-most one in the toolbar) to start XperiFirm. The window will open, choose the phone from the left part of the window (Xperia Z5 Premium (Satsuki)), then choose your particular model (I chose E6883 Dual) and after that choose your market and operator from the right part of the window. I chose 1299-4828 Russia Customized RU. Of course, you don't have to choose exactly this, click on the entries of your own choice. The entry will become highlighted and shortly there will be some info in the last column (Latest Firmware). This definition will be also in the right-most part of the window just under the phone thumbnail, click on it. Not a brilliant design decision, but that's it. Here is a screenshot for your reference:
The new window will pop up, press Download. The stock firmware will be downloaded to your computer and unpacked. Once the download is completed, close all XperiFirm windows to return to the main Flashtool window. Flashtool will begin creation of the .ftf file from the downloaded files which will be used for a (subsequent) flashing. FTF-files are similar to ZIP-files, and may be opened with 7-Zip. I've got E6883_32.2.A.0.305_1299-4828_R4C.ftf after the completion of this procedure. Flashtool places firmwares in the C:\Users\<Your Windows Username>\.flashTool\firmwares.
Now, once the stock firmware is downloaded, packed into .ftf and ready to be installed, let's do this. Disconnect the phone for now, physically extract microSD card (if any) and press the left-most button on the Flashtool's toolbar (the "Lightning" one) and choose Flashmode. The Firmware Selector window will appear with a selected default folder and list of all firmware available for a flashing. I've got a single entry, the firmware I just downloaded. Before actual flashing, you can check some checkboxes from the Wipe section, I usually check all to start clean (all the data on the phone is erased). Once again, just to be safe, extract the microSD card from the phone at this moment. It is not needed for a flashing anyway. Here is how the window looked to me:
After all is set up, press Flash. The flashing process will begin. At first Flashtool will prepare files for a flashing. After a while, window will appear which will ask you to connect the phone in the Flashmode mode. Shutdown the phone, hold the Volume Down button, connect the USB cable. Once Flashtool detects the phone in the Flashmode mode, it will start the actual flashing automatically.
After the completion of the flashing procedure after some minutes, you'll get a stock Sony firmware installed, and now it is perfect time to proceed to the next step. You may leave your phone off at this moment, but if you are curious, start it up and check if the new Android is actually there. Note however that first start after the firmware installation takes a long time.
5. REPACKING AND FLASHING A KERNEL
To get the stock firmware rooted, you need a way to install SuperSU. SuperSU is some tool which enables root access to the Android system. To install SuperSU, you need TWRP. To run TWRP, you need a kernel, which supports both TWRP and your Android version.
You can extract the kernel from .ftf file, prepared by Flashtool earlier, repack it and integrate TWRP (and DRM fix) into it, and finally flash it to your phone back modified. Sound like a complex task but it's definitely achievable.
At first you should extract the actual kernel from the .ftf file. Reminder: it's in the C:\Users\<Your Windows Username>\.flashTool\firmwares folder and may be titled E6883_32.2.A.0.305_1299-4828_R4C.ftf or something like this. Open it as an archive (right-click on a file, 7-Zip > Open archive) and extract kernel.sin. It's your phone's packed kernel.
If it is packed, obviously you need to unpack it. Thankfully the almighty Flashtool can do this. Open Flashtool, navigate to the Tools > Sin Editor, select a kernel.sin you've just extracted and press Extract data. As a result, you'll get a kernel.elf file in the directory where your packed kernel was. As you may have guessed, kernel.elf is an unpacked kernel. It can be modified, repacked and flashed back to the phone. Let's do this.
You will need a Stock kernel repack script from @tobias.waldvogel. Here is the original thread. Grab the script there. I used v5.0 and it worked perfectly for .253 and older.
Once the contents of the zip-file are extracted to some directory, copy the kernel.elf there and summon command prompt in this directory (right-click in the empty space of this folder in File Explorer with the Shift button pressed and choose Open command windows here).
In the command line type the following:
Code:
rootkernel.cmd kernel.elf boot.img
You'll get some questions about adding some features/tools to your kernel, feel free to answer "Yes" (type Y) to all of them. Screenshot for your reference:
If all went smoothly, you'll get a repacked kernel, boot.img in the script folder, supercharged with TWRP and DRM fix, and most importantly, which also supports rooting. Now it is time to flash it to your phone.
Turn off your phone and connect it in a Fastboot mode: hold the Volume Up rocker button and connect USB cable. The LED on the phone will turn blue.
Flashing images in this mode is typically done with a fastboot.exe from the Android SDK. Android SDK weighs many gigabytes but thankfully you don't need to download it. Fortunately Flashtool contains fastboot.exe from the SDK. It's in the Flashtool\x10flasher_lib folder. For the brevity of the following steps, copy the newly generated boot.img to this folder. Shift-right-click in the empty space of this folder window and choose Open command window here entry from the context menu. Windows console will appear.
At first try this command:
Code:
fastboot.exe devices
If all is good, there will be one device in the output of this command, just like this:
If not, perhaps there is some driver issue, so head back to the step #1 and make sure the drivers are installed correctly.
If your device is shown correctly, let's flash some files to the phone. Execute the following command to flash the modified kernel:
Code:
fastboot.exe flash boot boot.img
The proper output of this command will be like this:
If you get any errors, the first and more likely reason is that you still have a locked bootloader. Head to the step #3 to verify its state and unlock it if necessary.
If there were no errors, you now just flashed a custom kernel with TWRP recovery and DRM fix. You're almost done! You may plug out the cable from your phone. If you are attentive to the details, you'll notice that now, once your phone is started, its LED turns amber for 2-3 seconds. This is a special signal for those looking to boot into a recovery (TWRP).
Although @tobias.waldvogel claims his script is able to also integrate SuperSU during the kernel repacking, I didn't managed to get this working, so the SuperSU installation is a separate step in my guide. The next step.
6. ROOTING WITH SUPERSU
Now when you have TWRP in place and Marshmallow installed, let's root it. SuperSU distributed in a TWRP-friendly .zip archives, so you should copy one to your microSD card. I used beta version 2.78 SR1 from here. At the time of your reading, there probably will be some newer versions available, try them instead.
Once SuperSU zip-file is copied to your microSD card, reboot to recovery (TWRP). To do this restart or power up your phone and look at the LED. Once it lights amber, press Volume Up rocker button and you'll get into recovery — TWRP 3.0.
To install SuperSU, press Install, go to the /external_sd and select the .zip (in my case SR1-SuperSU-v2.78-SR1-20160915123031.zip). Swipe right to confirm installation. Once it is installed, press Reboot System button. Phone will reboot twice. Do not interfere with the phone during these multiple reboots, the things are getting done right, so just wait once Android is started. Once it's started, the phone is rooted and functional!
7. RESTORE YOUR DRM KEYS
If you had successfully backed up your DRM keys in step #2, it is now time to restore it back to the device. There is a flash_dk.cmd script shipped with the Root kernel repack script you used in the previous step. flash_dk.cmd can be used to flash the DRM partition back to your phone.
At first prepare the flashable .ftf:
Code:
flash_dk.cmd <ta backup image> dk.ftf
And then flash dk.ftf via Flashtool, just like you flashed the whole firmware in the step #4, but don't wipe anything this time.
8. OPTIONAL STEPS
8.1. Xposed installation
Since Z5P uses Lollipop and later, you should install Xposed APK from here. At the time of writing there is XposedInstaller_3.0_alpha4.apk installer there.
Once APK is installed, grab the latest .zip from the repository, I've got xposed-v86-sdk23-arm64.zip. Install it in a regular TWRP way covered in step #6.
Once all these steps are done, you should have Xposed Installer app in your phone, and if you open it and check Framework section, if everything is alright, there will be text in green, something like "Xposed framework version 86 is active".
Installation of actual Xposed modules can be performed in different ways. For example you may install HideSimIcons module from @tobias.waldvogel if you've got dual-SIM Z5P and you're mad at SIM-card icons in the system tray. Get the APK from the original thread and install it just like you install regular APKs.
8.2. Resolving Voice Search and random volume up/down issues while using regular headphones
See this thread.
8.3. Disable startup notification if there is a newer firmware available
Some people get annoyed by a persistent notification, which is displayed once the new firmware become available (new Android version from Sony). Rooted users cannot just tap it and update over-the-air, because they need to perform a complex rooting procedure in beforehand (covered in this guide). It is possible to disable this notification. You may get these notifications by email anyway.
The easiest and safest way is to use some autorun manager. I used Autorun Manager Pro and disabled all receivers of system apps com.sonymobile.fota.service, fota update service and Software update. Notification vanished after a restart.
You may even freeze or remove these apps via some app manager like Titanium Backup Pro.
THAT'S IT
At this point you have a stock Sony Android enhanced with root privileges. SuperSU app is also installed, so you are ready to use root right away. SuperSU now can be updated in a regular way via Play Store.
P.S. WHEN NEW FIRMWARE IS AVAILABLE
Once the new firmware is released, you may perform the same procedure for it beginning from the step #4, but if it is a minor upgrade, you may want not to wipe anything during Flashtool flashing this time. If it is a major upgrade, e.g. Marshmallow > Nougat, you probably may want to start with a clean system and wipe all.

Hello
THX for this guide
ihave this problem
C:\Android\sdk\platform-tools>fastboot.exe flash boot E6883_MM_ROOTABLE_PERMISSIVE_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15548 KB)...
OKAY [ 0.353s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
I dont have this folder with"Flashtool\x10flasher_lib f"

get2easy said:
Hello
THX for this guide
ihave this problem
C:\Android\sdk\platform-tools>fastboot.exe flash boot E6883_MM_ROOTABLE_PERMISSIVE_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (15548 KB)...
OKAY [ 0.353s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------
I dont have this folder with"Flashtool\x10flasher_lib f"
Click to expand...
Click to collapse
Hello. This seem like a driver problem to me. Or maybe bootloader is locked. Was fastboot driver installed from the Flashtool package? Do you have your bootloader unlocked?

Hy THX for ure answer.
Drivers are installed, but myBL is LOCKED!! Must i have UL BL??

get2easy said:
Hy THX for ure answer.
Drivers are installed, but myBL is LOCKED!! Must i have UL BL??
Click to expand...
Click to collapse
Sure, I've explicitly stated in the preface section of this guide, that you need to unlock your bootloader to get things done.

OK THX. I dont will loose my performance and the quality from the cam. I wait when is available from the Locked BL.

Hey thank you for posting this it helped a lot! But I don't really know what happened after I flashed the custom kernel and TWRP my phone won't recognize the microSD, not even when booting at recovery. Help.

renezada88 said:
Hey thank you for posting this it helped a lot! But I don't really know what happened after I flashed the custom kernel and TWRP my phone won't recognize the microSD, not even when booting at recovery. Help.
Click to expand...
Click to collapse
I heard about this issue with some large microSD cards of sizes >=128 GB. What is your card?

128gb indeed

renezada88 said:
128gb indeed
Click to expand...
Click to collapse
That's probably a kernel issue. You can try to ask support from its creators, but don't expect anything, because this all is a volunteer work.

get2easy said:
OK THX. I dont will loose my performance and the quality from the cam. I wait when is available from the Locked BL.
Click to expand...
Click to collapse
Just updated the guide, adding the last section (P.S.). Check it out, you may be interested.

Fragmentation said:
That's probably a kernel issue. You can try to ask support from its creators, but don't expect anything, because this all is a volunteer work.
Click to expand...
Click to collapse
Solved it! I needed the E6583 kernel not the E6883. Thanks for everything now root is working with that kernel and it reads the microSD.

Fragmentation said:
Just updated the guide, adding the last section (P.S.). Check it out, you may be interested.
Click to expand...
Click to collapse
sir are all the drm protected features restored by the mod????, and my phone is already MM can I proceed to the 3rd step??

renezada88 said:
Solved it! I needed the E6583 kernel not the E6883. Thanks for everything now root is working with that kernel and it reads the microSD.
Click to expand...
Click to collapse
That's good. I will update the guide and explicitly mention, that it is needed to pay attention to what particular model the phone is. There are different kernel options for different models of Z5P.
1dave said:
sir are all the drm protected features restored by the mod????, and my phone is already MM can I proceed to the 3rd step??
Click to expand...
Click to collapse
I think they are all restored, however I applied the mod just yesterday and checked only photo quality in dark conditions. X-Reality is also seems like works properly, but honestly I didn't tested it before and after the mod. So far so good.
If you already have stock MM, proceed to the stage 3 directly. But of course you should have fastboot drivers properly installed, if not, head to the stage one.

Does anybody have some problem with whatsapp notification when the smartphone is wifi connected?
Sometimes I don't receive any message until I enter the application. This does not happen if I am connected via 3g.
Edit: Sometimes I received delayed whatsapp notification even if the smartphone is connected through 3g.
Inviato dal mio E6853 con Tapatalk 2

We needs this! A light for LB users... Someone can port for Z5? ?
http://forum.xda-developers.com/showthread.php?t=3337357
Enviado de meu E6853 usando Tapatalk

Guto ViP said:
We needs this! A light for LB users... Someone can port for Z5? ?
http://forum.xda-developers.com/showthread.php?t=3337357
Enviado de meu E6853 usando Tapatalk
Click to expand...
Click to collapse
1. There is no dm-verity on Z3 Beta MM but we have it
2. Flashing needs working recovery for locked bootloader (it needs root to install recovery!)

Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom

Black_Focus_X said:
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Click to expand...
Click to collapse
That'd be great !

Black_Focus_X said:
Is it possible to make a flashable.zip of twrp? For a pre-rooted stock rom
Click to expand...
Click to collapse
If you are talking about the PRFCreator, then no, currently it doesn't work with Marshmallow for some reason. Check the corresponding thread.

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

[Stock ROM][Combination][RMM state solution][GUIDE AIO] and many more for M30s

What's currently included in this thread :-
TWRP (With/without magisk)
Installing EdXposed
Root with magisk (not recommended due to bootloops, use twrp with magisk)
RMM state Prenormal solution
Stock and combination firmware and Kernal source Gdrive links
Tools for flashing and downloading latest firmware
Post 2
Hide bootloader unlocked warning message
DeGoogle & debloat M30s and install MicroG
Enable Haptic feedback on m30s (or any other samsung phone)
BACKUP YOUR EFS PARTITION BEFORE DOING ANYTHING​If EFSpartition is corrupted or lost, you would not be able to get calls and wifi and your IMEI will be permanently lost.
There is currently no way of restoring corrupted EFS partition since it is device specific, so flashing stock firmware will also be useless
Here is one guide. follow this or any other that works for you.
Here is another (droid view.com/restore-efs-imei-galaxy-s7/)
OR You can Backup all partitions using twrp (nandroid backup) and store in someplace safe (make sure to tick all partitions including EFS)
This is an excellent guide regarding EFS (thanks to @PlayingPoise). I HIGHLY RECOMMEND READING IT BEFORE PROCEEDING.
TWRP (With/without magisk) (huge thanks to @santhoosh)
Thread
there are two .tar files, flash the one you need
Pro Tip: I would recommend Smalipatcher module to reboot directly into magisk system.
Installing EdXposed
See This for installation video OR This Or This for installation guide.
This, for official website
And This for github!
NOTE: v0.4.6.0_beta from github requires custom magisk otherwise the system wont boot since github hosts alpha versions, so i advice to follow the video tutorial since it has installed the most stable EdXposed
Rooting with Magisk (Currently causing random bootloops since custom Kernal is req., i recommend flashing twrp with magisk)
From magisk official repo and This Link, Both are same, but i just wanted to make AIO thread)
thanks to @santhoosh and @topjohnwu
Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
* Allow bootloader unlocking in Developer options → OEM unlocking
* Reboot your device to download mode. Either use adb reboot download, or use turn off m30s, press vol+ and vol- simultaneously (while powered off) and connect to pc.
* Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
* Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
* Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
* if there is no OEM unlock option, set phone's date to 7+ days and back and now see.
* Your bootloader now accepts unofficial images in download mode.
Instructions
* Download the firmware for your device.
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
* Install the latest Magisk Manager
* In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
* Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
* Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
* Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
* Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
* We now want to boot into the stock recovery to factory reset our device.
* Full data wipe is mandatory! Do not skip this step.
* Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the Vol up and power to boot to recovery . Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
* Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
* This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
* The device will automatically reboot for the first time it boots. This is completely normal and done by design.
* After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
* You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
* Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
Additional Info
* Magisk actually patches 3 partitions on your device:
vbmeta: replace with empty vbmeta image to disable partition verification
boot: remove the signature of the image to prevent soft bricks
recovery: this is where Magisk is actually installed
* Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
* If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
* If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC
used instead of CSC)
RMM state Prenormal solution
Flash stock firmware
Boot up WITH sim inserted, CONNECT to internet during setup (or you can connect after setting up, but perform below operations only when connected to internet).
Enable developer options and go to them.
Now connect to internet and go to dev options, now set date 8 days back and check dev options for OEM unlocking
if it's still not there set date to today and again 8 days back and again check.
This worked for me and OEM unlocking was there and RMM state was changed to checking.
(what we are doing is fooling phone to believe that sim was inserted for more than 7 days)
Stock and combination firmware and Kernal source
Below are Gdrive links for Combination firmware for (M307FXXU1ASH9) and (M307FXXU2ASK2) and ROM M307FXXU1ASHI, M307FXXU2ASL2, M307FXXS2ATB3 (FOR INS ONLY, for other regions, use frija or samfirm).
I have also uploaded Kernal source for M307FXXU2ASL2 on gdrive for faster download.
Tools included
The following tools are also included in the shared folder, they are up to date as of FEB 2020, but i have attached links to original threads of xda to give credits and in case they are updated, you can download them from there. (As i said, this is AIO thread to find tools, none of them are my creation)
Frija, Samfirm continued and Samfirm are Tools for downloading Official firmware from samsung servers with high speed (so no to sammobile and other ****ty premium websites)
Frija thanks to @invmini, Github
SamFirm thanks to @zxz0O0, Github
SamFirm_continued, Github
Odin
Patched Odin by @realbbb
Frija not working ? install both vcredist_x00 for your device !
(check your windows settings to know which version to install)
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-m307f) and your CSC : (mine is INS).
(All models on samfrew: https://samfrew.com/model/SM-M307F/).
Thanks to @BK
Other Tools
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Samsung firmware naming convention and explanation (Outdated)
SM-M307F - Galaxy M30s Samfrew
Extract Samsung PIT File from Samsung Firmware -> www.droid views.com/extract-samsung-pit-file-from-firmware (remove space b/w "droid" and "views")
NAND Erase Samsung Devices in Odin -> www.droid views.com/nand-erase-odin-samsung-firmware (remove space b/w "droid" and "views")
Latest Odin Downloader: https://odindownloader.com/category/download
Samsung USB Driver: https://samsungusbdriver.com/category/download
Samsung Firmware: https://firmwarefile.com/category/samsung
Links​LINK (Pm me if link is dead. If there is error like "try after some time", make a copy of file to your drive and then download)

Hide bootloader unlocked warning message
See Here
DeGoogle & debloat M30s and install MicroG
Here
Enable Haptic feedback on m30s (or any other samsung phone) (thanks to ak****)
1- download "Settings database Editor" from playstore.
2- scroll to bottom and find "haptic_feedback_enabled" and change it to 1

Just in case

great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )

BK said:
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
Click to expand...
Click to collapse
Are you talking about the frija and samfirm part?
I think i took it from some other thread which i cant find now. (maybe s10 or note10 ones)
Edit: Gave credits to you

How to flash Combination firmware?
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.

nobody_nowhere said:
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
Click to expand...
Click to collapse
it's currently impossible to install a test/debugging firmware without a samsung dev account that work as an authorization to flash combination files.

Sm-m307f/ds
Hi i got OTG update and my phone didnt restart after that, i have been trying to find the right Stock firmware for my Samsung M30S SM-m307F/DS but i couldnt find the right one, can you please help me out with the link of the right firmware for my phone.
Thanks

Watch this video broo...you will get to know how to download all latest updated frimware

How To Guide Rooting the ROG Phone 5 - my notes

I just received my ROG Phone 5 today and rooted it using Magisk. These are my notes. (I like to keep rooting notes for each device in case I ever need to check how I did it or repeat the process.)
If you are already familiar with rooting a device with Magisk, then you will find these notes very familiar. These are based on the generic Magisk method listed here: https://topjohnwu.github.io/Magisk/install.html
Magisk's instructions note that the device should be running a stock ROM. If you are using a brand new device, this should already be true BUT there are reports online that some resellers are selling a locked device that was previously unlocked, flashed with a custom rom, and then re-locked. (The people reporting this issue have devices that say Tencent on the back and come in a rectangular box, but it's also possible that you have a Tencent version that can be unlocked. Asus made a deal with Tencent to release a special Tencent edition of the phone, but Asus is also selling the phone as well. I have not heard any reports of the non-Tencent version coming in a state that cannot be unlocked. I bought one that was more expensive and got sent the pro in the non-rectangular box, without Tencent on the back of the phone.)
I rooted the phone from a machine running Ubuntu. I imagine it would also work from other linux distros or from osx, but I have no idea if it will work from Windows.
1) Turn on Developer Options:
Start phone, go through setup process (skip as much as you can because you will lose all of these settings in the rooting process), go to Settings->System->About Phone->Software Information->click on the build number seven times, enter your pin when/if prompted
2) Enable USB Debugging:
Go to Settings->System->Developer Options
Enable USB Debugging
Connect via USB from the side of the phone to your computer (do not use the usb port on the bottom of the phone)
When prompted on the phone, agree to allow File Transfer and USB Debugging and trust the PC
3) Check whether the bootloader is already unlocked:
Open a terminal on your computer
(install adb and fastboot if you have not previously done so)
$ adb reboot bootloader
Wait for device to reboot, then from the terminal do
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
... etc
^^ This is what the output may look like if your device is not already unlocked.
If the bootloader is already unlocked, you can skip step 4.
4) Unlock the phone:
Start up your phone
Download the unlock utility on your computer:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
from the terminal do
$ adb install ./AsusUnlock_1.0.0.7_210127_fulldpi.apk
This will install the unlock tool on the phone
Open the newly installed unlock app on the phone
Follow the instructions in the app to unlock your device.
After unlock, you will have to go through the phone setup all over again. Annoying, I know.
From this point on, you can expect a warning about your bootloader being unlocked every time you boot the phone. This is normal.
(If unlock fails, you may have been sold a phone that was unlocked by a reseller, flashed with a custom ROM, and then re-locked. If that's the case, this method of rooting your phone will not work. You can always try to return the phone if it was advertised as being unlocked and isn't.)
5) Install Magisk:
Download the latest Magisk apk onto your PC from https://github.com/topjohnwu/Magisk/releases and rename it to Magisk.apk
Open a terminal on your PC and
$ adb install ./Magisk.apk
This will install the Magisk app on the phone
Open it and verify that it says "Ramdisk Yes" two lines under the blue word Magisk. The ROG Phone 5 *should* say this and if it does not something is wrong, refer to the official Magisk instructions.
6) Download the firmware from ASUS:
Let your phone update if it has not already. Mine was pushed an update after install.
Check the exact version you are currently on after the phone updates.
Go to Settings->System->About Phone->Software Information
You need to know your Extension Rom and your Build Number
Then download the firmware from Asus for your build number by going to the URL corresponding to your build number and extension, such as:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-18.0840.2103.26-1.1.81-user.zip
Where 18.0840.2103.26 from the link above is my build number and 1.1.81 is my extension ROM. If your build number and extension are different, change those values in the URL.
7) Extract the boot.img from the firmware:
Unzip the downloaded firmware
Install Payload Dumper on your PC: https://github.com/vm03/payload_dumper (instructions for installing payload dumper are on the github)
Copy payload.bin from the extracted firmware into the payload dumper folder
Open a terminal, cd to the folder containing payload dumper and payload.bin and then run
$ python3 payload_dumper.py payload.bin
Note: depending on how python is installed, you may need to type python instead of python3 here.
Once this completes, the boot.img file will be in payload dumper's output folder
$ cd output
$ adb push boot.img /sdcard/boot.img
8) Patch the boot file using Magisk:
Open Magisk
Press the install button to the right of the word Magisk
Press "Select and Patch a File", browse to the boot.img from the file folder (if you put it in SDcard like me, try checking the Rog Phone 5 folder for it)
Magisk will patch the boot.img to make it usable for your phone and place it in a file named magisk_patched_[random_strings].img in the Downloads folder of your phone.
9) Flashing the rooted firmware:
Transfer the patched file to your PC and rename it to ./magisk_patched.img
Reboot into fastboot by opening a terminal and entering
$ adb reboot bootloader
Test the image file prior to flashing:
$ fastboot boot ./magisk_patched.img
If that did not error (the bootloader unlock warning is normal), reboot into flashboot and flash:
$ adb reboot bootloader
$ fastboot flash boot ./magisk_patched.img
$ fastboot reboot
After the warning about the bootloader being unlocked, the phone should boot as normal. Once booted, open Magisk and verify that it is rooted by looking for the version of Magisk that is installed. Under the word Magisk in blue, it should say Installed: version. If it says Installed: N/A then your device is not rooted.
You should be able to further test whether you have root access at this point by doing
$ adb shell
$ su
Then clicking accept on the su request on your phone. If that works, the device is definitely rooted.

Thank you for the notes.
Unlocked bootloader and Rooted my ROG phone 5 WW firmware today.
Double checked with my firmware and extracted boot.img
Payload dumper was not working in both of my pc for some reason (bsdiff4 error). Tried with Android phone through termux and successful to extract the boot image.
Rooted with magisk passing safetynet.
Thank you

jhosharath said:
Thank you for the notes.
Unlocked bootloader and Rooted my ROG phone 5 WW firmware today.
Double checked with my firmware and extracted boot.img
Payload dumper was not working in both of my pc for some reason (bsdiff4 error). Tried with Android phone through termux and successful to extract the boot image.
Rooted with magisk passing safetynet.
Thank you
Click to expand...
Click to collapse
Awesome. Please write up an alternative for step 7 if you can, in case anyone else needs it.
Also, I actually am getting a SafetyNet API Error, so I'm curious if you did anything special to make it work.

hey, thank you very much for your notes, they would have been very helpful a few weeks ago when i almost bricked my device eheh.
i'm also getting a safetynet error (ctsProfile), wonder what that could be.
also didn't know about the build number, i kept flashing raw firmwares blindly like a moron, accidentally getting the right ones it seems... so thanks for that too.
i too have been wanting to write my notes on the forum for others to read, but you... you made the difference !!
amazing work

To extract the payload.bin through android phone I followed the steps as mentioned in this link
https://forum.xda-developers.com/t/tutorial-android-ota-payload-dumper-on-android.4061799/
Credits to GuestK00376 for the tutorial.
Until TWRP recovery comes this will be very much useful for those who have issues with that python or payload dumper in pc.
Safetynet API error is a problem with magisk recently. You can download Safetynet testing apps from playstore and check it. Mine had CTS profile false only which i sorted with universal safetynet fix magisk module. Also check playstore certification of device in playstore settings. If not certified then you have to hide it with magisk hide fully then have to clear Google play services and google play store data in aeroplane mode. Reboot, revert aeroplane mode to normal and then it was certified.
Thank you. Hope this will help. Good luck

I just successfully rooted my device I purchased it from Amazon it was the tencent edition it already had the global ROM installed I used the app to unlock the bootloader successfully I was able to extract the boot image from my Android device I made a small tutorial video I'm going to edit it and post it in case anybody's interested and wants to see it done

chairman011 said:
I just successfully rooted my device I purchased it from Amazon it was the tencent edition it already had the global ROM installed I used the app to unlock the bootloader successfully I was able to extract the boot image from my Android device I made a small tutorial video I'm going to edit it and post it in case anybody's interested and wants to see it done
Click to expand...
Click to collapse
Very much appreciated and useful for those who are trying to root. Good work bro

I am not a YouTuber or anything I just took bits and pieces from everybody's advice I couldn't have done it without the help of you guys hopefully this helps somebody I hope I didn't make it too difficult to understand.
Hopefully it helps somebody

Sorry guys I forgot to mention you need the safety net universal fix module here's the XDA link I forgot to mention that in the video my apologies
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com

I am happy to report that I am now passing SafetyNet after Installing both the Universal SafetyNet Fix from github and the MagiskHide Props Config plugin within Magisk (press the puzzle piece button on the lower right hand corner of the Magisk app, then search for it). I'm not sure what exactly made it work though. After install, I was able to configure which applications to hide from via the Superuser->Magisk Hide menu within Magisk.
I had some difficulty with props and ended up reverting changes after trying to update my fingerprint to match the Rog Phone 3. Then things started working after several reboots. I'm not sure what is going on here, so I'm not confident that someone else will be able to reproduce this via the steps I used. Otherwise I'd write up a comprehensive set of steps used here.
I had to use another app to verify safetynet because the check is not working within Magisk.

You forget to explain for the safetynet
You way are good but not complete,
-magisk hide
-Univerversal SafetyNet 1.1.1 (patch)
-canary (new magisk)
Without that you are rooted but, with SafetyNet error
And after bootloader unlock after phone restart before root upgrade your Netflix, because after it's too late impossible to upgrade and no Netflix fix

chairman011 said:
I am not a YouTuber or anything I just took bits and pieces from everybody's advice I couldn't have done it without the help of you guys hopefully this helps somebody I hope I didn't make it too difficult to understand.
Hopefully it helps somebody
Click to expand...
Click to collapse
I tried to use termux and when i paste the last "apt update && apt upgrade -y" i get a error that tells me that its under maintenance

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​