Develop Bugs

Updating your rooted Pixel 4a 5G on Windows

I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Make sure you have the latest USB drivers: https://developer.android.com/studio/run/win-usb
and the latest platform tools: https://developer.android.com/studio/releases/platform-tools.html
NOTICE: The latest version (34) gave me this error when updating: "FAILED (Sparce file is too large or invalid)". When updating again with version 33 everything went fine.
Some Magisk modules may cause bootloops so it's best to disable them and to reboot before updating.
Unhide Magisk.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/images#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while, and sometimes it even fails the first time. Don't worry and try again.
In the extracted folder there is another zip file. Extract this too.
Now inside the extracted folder, look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file, and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and now rooted device!
Code:
fastboot reboot
Now can can turn back on your Magisk modules and hide it.

You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.

drdionysius said:
I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Some Magisk modules may cause bootloops so it's best to disable them and te reboot before updating.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/ota#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while and sometimes it even fails the first time. Don't worry and try again.
Meanwhile you can download the latest factory image: https://developers.google.com/android/images#bramble
Extract the zip file and open the extracted folder. In there is another zip file. Extract this too.
Now inside the extracted folder look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and rooted device!
Click to expand...
Click to collapse
Perfect, Thank you, would you please to do another guide of how to enable 5G and Volte

mx597turbo said:
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
Click to expand...
Click to collapse
This works perfectly! Thank you for sharing this method! Worked flawlessly on my bramble to get it to the February security update! Very amazing!

drdionysius said:
I'll try to make a step by step to update your Bramble (Pixel 4a 5G) with the latest updates assuming you're rooted (otherwise it would update normally). These steps worked for me. I know there are other ways. If you want to link to another way, please do.
Some Magisk modules may cause bootloops so it's best to disable them and te reboot before updating.
Download the latest Factory Image (look carefully to use the right one: Verizon or other) https://developers.google.com/android/ota#bramble
Unzip this in your adb folder (I'm assuming you have this already set up as you're rooted already)
Edit the 'flash-all.bat' in Notepad and look for the "-w" in the last line. Remove the "-w" as this will wipe your phone
With your device plugged into the computer, open a command prompt in the adb folder. (pen the folder, hold down Shift and right click inside the folder, "Open Command window here")
Run this command to go into bootloader on your phone:
Code:
adb reboot bootloader
Now run the flash-all.bat from the command line
Code:
flash-all.bat
This can take a while and sometimes it even fails the first time. Don't worry and try again.
Meanwhile you can download the latest factory image: https://developers.google.com/android/images#bramble
Extract the zip file and open the extracted folder. In there is another zip file. Extract this too.
Now inside the extracted folder look for boot.img
Your phone should be finished upgrading by now and booted normally
Copy the boot.img file to your phone (remember where you put it)
Open Magisk Manager (you should be on the Update Channel: Canary in the Settings)
Click on "install" (the top one)
Select "Select and Patch a file" and browse to your boot.img
Click "Let's go"
Magisk manager will now patch your boot.img to a rooted version and will tell you where it saved the file and it's name
Now move this file to your adb folder and open the folder in the command line again
Go into bootloader again by running this code
Code:
adb reboot bootloader
When in bootloader mode run this code
Code:
fastboot flash boot magisk_patched_xxxxx.img [replace the filename with the one you have]
Reboot your updated and rooted device!
Click to expand...
Click to collapse
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.929s
Press any key to exit...
hi I am trying to update to the Feb update and I get to "writing boot" but it always fails. What am I doing wrong? I am on stock with Magisk and Elemental X Kernal, that is pretty much it.
Thanks.
_______________________
I figured it out... I need to update my adb folder on my comp, thankssssss worked well.

kazemitsui said:
checking product...
OKAY [ 0.069s]
checking version-bootloader...
OKAY [ 0.069s]
checking version-baseband...
OKAY [ 0.070s]
sending 'boot' (98304 KB)...
OKAY [ 0.409s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 0.929s
Press any key to exit...
hi I am trying to update to the Feb update and I get to "writing boot" but it always fails. What am I doing wrong? I am on stock with Magisk and Elemental X Kernal, that is pretty much it.
Thanks.
Click to expand...
Click to collapse
Did you pick the right version?
{
"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"
}

drdionysius said:
Did you pick the right version?
View attachment 5216649
Click to expand...
Click to collapse
Yea I figured it out, I needed to update my adb folder on my computer!

I'm having a problem myself with patching the boot.img through Magisk Manager. It says "installation failed".
-update-
Solved. I had to update Magisk Manager Canary.

mx597turbo said:
You can also update using the ota.
Download both the full factory image (fi) and ota
Extract boot.img from the fi, and patch on your phone using magisk - place in the same folder as the ota (on your pc)
Disable all modules in magisk. I also disable adaway (may not be necessary)
Reboot
Boot into recovery. Once the android is on the screen, hold power then press vol +
Select apply update from adb, then on the pc in a command window or powershell run
Code:
adb sideload xxx.zip (where xxx is the name of the ota image)
Once done, reboot into bootloader
Code:
adb reboot bootloader
Flash the patched boot
Code:
fastboot flash boot xxx.img (where xxx is the name of your patched boot img)
Reboot into system, give the phone a few mins. Enable all magisk modules, reboot, enable adaway, reboot. Done.
Click to expand...
Click to collapse
Hi ! Great Thank you is the best option without Twrp for update my Pixel 4a 5g.
Very simple, just a mistake with unautorized adb on my mac os but after Google it can resolve it and update quickly no do uninstall magisk but just uncheck mod same as Twrp.
Very Thank you have a good day
EDIT : NO !!! After re-check my mods the Pixel wont start ??? Or Re Start Or factory Reset ??? No no no it(s the second update do factory reset !!!! without Twrp is not good

ggkameleon said:
Hi ! Great Thank you is the best option without Twrp for update my Pixel 4a 5g.
Very simple, just a mistake with unautorized adb on my mac os but after Google it can resolve it and update quickly no do uninstall magisk but just uncheck mod same as Twrp.
Very Thank you have a good day
EDIT : NO !!! After re-check my mods the Pixel wont start ??? Or Re Start Or factory Reset ??? No no no it(s the second update do factory reset !!!! without Twrp is not good
Click to expand...
Click to collapse
I had the same problem, make sure to boot into safe mode, as this will automatically turn off all magisk modules. The clock mod caused this for me, so make sure to uninstall that.
Here is a video I found:
if the volume key to go into safe mode does not work, (it did not for me), as soon as you reach the os, before it shuts down, long press the power button and long press restart. Then click on ok to boot into safe mode. Hope this helps!

3dcantaloupe said:
I had the same problem, make sure to boot into safe mode, as this will automatically turn off all magisk modules. The clock mod caused this for me, so make sure to uninstall that.
Here is a video I found:
if the volume key to go into safe mode does not work, (it didd not for me), as soon as you reach the os, before it shuts down, long press the power button and long press restart. Then click on ok to boot into safe mode. Hope this helps!
Click to expand...
Click to collapse
Hi ! Thanks. I have the center clock too.
I do flash the stock boot img for restart it and test for remove mods but I can't.
I have flash again the Magisk boot img but again bootloop.
I have flash again the stock boot img and see your thread. Thanks

ggkameleon said:
Hi ! Thanks. I have the center clock too.
I do flash the stock boot img for restart it and test for remove mods but I can't.
I have flash again the Magisk boot img but again bootloop.
I have flash again the stock boot img and see your thread. Thanks
Click to expand...
Click to collapse
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me

3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
Ok thanks but now I'm on stock boot img.
If I understand I flash again on fastboot the magisk boot img and restart on safe mod for uninstall magisk mods.
But how restart on safe mod.
Thanks

3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
I'm curious, are you running the current March update?

ggkameleon said:
Ok thanks but now I'm on stock boot img.
If I understand I flash again on fastboot the magisk boot img and restart on safe mod for uninstall magisk mods.
But how restart on safe mod.
Thanks
Click to expand...
Click to collapse
Power off the phone
Turn it on
Once you see the Google boot logo, press and hold the Volume Down key
Keep holding the Volume Down key until the phone enters Safe Mode. You will see a watermark on the bottom-left that says "Safe Mode".

DJBhardwaj said:
Power off the phone
Turn it on
Once you see the Google boot logo, press and hold the Volume Down key
Keep holding the Volume Down key until the phone enters Safe Mode. You will see a watermark on the bottom-left that says "Safe Mode".
Click to expand...
Click to collapse
Ok thanks thank you.
I test it. Have a good day

3dcantaloupe said:
yes, when you go into safe mode, it disables your magisk modules so that you can boot with the magisk patched boot image! Make sure to boot into safe mode when you have the magisk boot image installed and not the stock image. If you have any more questions, feel free to ask me
Click to expand...
Click to collapse
Yesssss ! I don't know how can pass safedod but many times restart on "Restart or Factory Reset"
I have flash many times stock boot img and magisk boot img anf inaly restart on safe mod and restart with magisk install and work !!!!
it's more difficult as Twrp installed. I don't know why Google don't want Twrp

artlan said:
I'm curious, are you running the current March update?
Click to expand...
Click to collapse
yes, I am running RQ2A.210305.006

ggkameleon said:
Yesssss ! I don't know how can pass safedod but many times restart on "Restart or Factory Reset"
I have flash many times stock boot img and magisk boot img anf inaly restart on safe mod and restart with magisk install and work !!!!
it's more difficult as Twrp installed. I don't know why Google don't want Twrp
Click to expand...
Click to collapse
Not that they don't want twrp, but no one is taking the initiative to fork it over to our device yet. It will eventually make it I bet! Using the hardware buttons as DJBharadwaj stated did not work, and I had to instead I had to wait for the phone to boot, then I longpressed restart to boot into safe mode.

Hi ! And it's possible to flash the magisk mod Center Clock ? Or make bootloop ?

How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet

WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!
If you are looking for my guide on a different Pixel, find it here:
Pixel 3
Pixel 3XL
Pixel 3a
Pixel 3aXL
Pixel 4
Pixel 4XL
Pixel 4a
Pixel 4a (5G)
Pixel 5
Pixel 5a
Pixel 6
For best results, use the latest stable Magisk release.
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.
Prerequisites:
Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
USB Debugging enabled
Google USB Driver installed
I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
Spoiler: Downloads
Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub
Spoiler: Unlock Bootloader
Follow these instructions to enable Developer Options and USB Debugging.
Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
Connect your device to your PC, and open a command window in your Platform Tools folder.
Ensure ADB sees your device:
Code:
adb devices
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
If you see "unauthorized", you need to authorize the connection on your device.
If you see the device without "unauthorized", you're good to go.
Reboot to bootloader:
Code:
adb reboot bootloader
Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Code:
fastboot flashing unlock
Select Continue on the device screen.
Spoiler: Initial Root / Create Master Root Image
Install Magisk on your device.
Download the factory zip for your build.
Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
Copy boot.img to your device.
Patch boot.img with Magisk: "Install" > "Select and Patch a File"
Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
Reboot your device to bootloader.
Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here>
Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
Spoiler: Update and Root Automatic OTA
Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
You should now be updated with root.
Spoiler: Update and Root OTA Sideload
Download the OTA.
Reboot to recovery and sideload the OTA:
Code:
adb reboot sideload
Once in recovery:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.
Spoiler: Update and Root Factory Image
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
Download the factory zip and extract the contents.
Reboot to bootloader.
Spoiler: Update bootloader if necessary
Compare bootloader versions between phone screen and bootloader.img build number
Code:
fastboot flash bootloader <drag and drop new bootloader.img here>
If bootloader is updated, reboot to bootloader.
Spoiler: Update radio if necessary
Compare baseband versions between phone screen and radio.img build number
Code:
fastboot flash radio <drag and drop radio.img here>
If radio is updated, reboot to bootloader.
Apply update:
Code:
fastboot update --skip-reboot image-codename-buildnumber.zip
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
The scripted commands should look like this:
Code:
fastboot flash bootloader <bootloader image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot flash radio <radio image name>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot update --skip-reboot <image-device-buildnumber.zip>
Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.
Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>
PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.
For instructions, downloads, and support, please refer to the PixelFlasher thread.
Spoiler: Update and Root using the Android Flash Tool
Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
When the update completes, the device will be in fastbootd. Reboot to bootloader.
Boot the master root image (See note 1):
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
Spoiler: Pass SafetyNet/Play Integrity
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.
Mod available here. Do not use MagiskHide Props Config with this mod.
This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.
Zygisk + DenyList enabled
All subcomponents of these apps hidden under DenyList:
Google Play Store
GPay
Any banking/financial apps
Any DRM media apps
Modules:
Universal SafetyNet Fix 2.3.1 Mod - XDA post
To check SafetyNet status:
YASNAC - GitHub
To check Play Integrity status:
Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.
I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.
Points of note:
The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
"App" simply shows the version of the app itself.
If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.
Credits:
Thanks to @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!

Thanks! Awesome write-up/explanation.

Now THIS is a useful thread! Thanks
I might try to root my P6P this week-end.
If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)
"6. Reflash vbmeta to disable boot verification"

Is it necessary to flash modified boot to "slot all"? I never did this before without issues. I always just did flash boot modifiedboot.img

Ghisy said:
Now THIS is a useful thread! Thanks
I might try to root my P6P this week-end.
If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)
"6. Reflash vbmeta to disable boot verification"
Click to expand...
Click to collapse
Yes. You're basically on a clean factory flash. It might still throw a "corrupted" error at you but a factory reset fixes it.
Cares said:
Is it necessary to flash modified boot to "slot all"? I never did this before without issues. I always just did flash boot modifiedboot.img
Click to expand...
Click to collapse
Not really; I prefer to do that after OTA because OTA is an out of band update that installs to the inactive slot. You don't really have to use the slot commands at all, but I've come into the habit of using them.

The steps for a rooted update via OTA worked perfectly for me! Thank you a tonne for the guide. I was thinking I would have to factory reset for every monthly update, glad we dodged that bullet!
Thanks again.

Is there any way to go back to DM Verity + AVB enabled without wiping after this?

Bandsalat said:
Is there any way to go back to DM Verity + AVB enabled without wiping after this?
Click to expand...
Click to collapse
See @V0latyle's more informed answer below.

Thank you for your time. This thread should be sticky

Bandsalat said:
Is there any way to go back to DM Verity + AVB enabled without wiping after this?
Click to expand...
Click to collapse
Yes - this is in fact the default state if the "disable" flags are not used. All you'd have to do is reflash vbmeta without any flags. Make sure you fully intend to do so, because 1. You won't be able to run a modified boot image, thereby preventing permanent root and 2. If you decided to disable vbmeta again, you would have to wipe data again.

@V0latyle, Is there any downside of using Factory Update vs OTA Sideload for monthly update? Since I will need to download the factory zip anyway for both methods, I would go with the factory update.​

For the Android flash tool method, can't you just patch the boot image and add it to the flash tool and skip the reboot to then flash the patched boot?
Someone needs to make a batch file for the above.

xpdragon said:
@V0latyle, Is there any downside of using Factory Update vs OTA Sideload for monthly update? Since I will need to download the factory zip anyway for both methods, I would go with the factory update.​
Click to expand...
Click to collapse
Nope, no downside that I'm aware of; many people used the factory images for updates on Android 11 and prior without any problems. Just make sure you flash it with --disable-verification --disable-verity
mkhcb said:
For the Android flash tool method, can't you just patch the boot image and add it to the flash tool and skip the reboot to then flash the patched boot?
Someone needs to make a batch file for the above.
Click to expand...
Click to collapse
I think you're confusing Android Flash Tool with something else. Take a look at the link - you connect your phone via USB and can install firmware direct from Google. There is no option to substitute your own files, which is a good thing.
As for adding the boot image to the flash process...I would avoid this, personally. You CAN edit the flash-all.bat to do this and some members here have. But, P6 and P6 Pro users have run into problems using a boot image they patched prior to updating, so here is my recommendation:
Flash the factory image with verity and verification disabled, and let the update complete including a boot to system. Once in system, you can then patch the boot image, reboot to bootloader, and flash it to /boot.

> Yes - this is in fact the default state if the "disable" flags are not used. All you'd have to do is reflash vbmeta without any flags. Make sure you fully intend to do so, because 1. You won't be able to run a modified boot image, thereby preventing permanent root and 2. If you decided to disable vbmeta again, you would have to wipe data again.
Tried that, but the P6 Pro fails to boot and just goes back to the bootloader after this.

Bandsalat said:
Tried that, but the P6 Pro fails to boot and just goes back to the bootloader after this.
Click to expand...
Click to collapse
Tried what, exactly? It's easier to help if you're more specific about what you did and what result you're getting. Is there a message at the bottom of the bootloader screen?

I have a dumb question:
There seem to be two different commands to disable flags:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
&
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Are they equivalent i.e., does the order matter?

biTToe said:
I have a dumb question:
There seem to be two different commands to disable flags:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
&
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Are they equivalent i.e., does the order matter?
Click to expand...
Click to collapse
No, the order doesn't matter; yes, they're equivalent.

roirraW edor ehT said:
No, the order doesn't matter; yes, they're equivalent.
Click to expand...
Click to collapse
The way I like to think of it is like this:
[Application: Fastboot/adb] [Command: What you want to do] [Destination: Where you want it to be done] [Modifiers: How you want it to be done] [Payload: What you want to be put there]
Those of us who grew up with DOS would probably do it like this:
Code:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
But I believe it could also be done like this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

V0latyle said:
Those of us who grew up with DOS would probably do it like this:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Click to expand...
Click to collapse
I'm the old DOS guy. THIS makes sense

biTToe said:
I'm the old DOS guy. THIS makes sense
Click to expand...
Click to collapse
Right? Imagine feeling old because you were born prior to 1990

How To Guide Flash/Install TWRP on Realme GT Master Edition RMX3360 (Indian variant)

TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?

aprilfoo said:
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?
Click to expand...
Click to collapse
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.

aprilfoo said:
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.
Click to expand...
Click to collapse
Screenshot can help better, try taking and sending it here.

{
"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"
}

hello sir is it compatible with rmx3363 ?

Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.

xeltos said:
Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.
Click to expand...
Click to collapse
well yes for some phones but deeptest somehow works for others if your lucky test them all and see ^^

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
hello sir is it compatible with rmx3363 ?

is this method work for latest Android 12 for installing twrp ?

pankaj9pankaj9334 said:
is this method work for latest Android 12 for installing twrp ?
Click to expand...
Click to collapse
Currently, A12 Twrp is under development by twrp team. So you have to wait.

ites working with rmx3363 finally i got twrp to work ^^ thanks

NextB said:
ites working with rmx3363 finally i got twrp to work ^^ thanks
Click to expand...
Click to collapse
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?

guizzzmo said:
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?
Click to expand...
Click to collapse
without any

NextB said:
without any
Click to expand...
Click to collapse
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above

guizzzmo said:
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above
Click to expand...
Click to collapse
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)

aprilfoo said:
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)
Click to expand...
Click to collapse
ok thanks for the reply. wich telegram group?

guizzzmo said:
ok thanks for the reply. wich telegram group?
Click to expand...
Click to collapse
@realmegtmasterupdates - telegram channel publications statistics Realme GT Master | UPDATES
telegram channel publications statistics of Realme GT Master | UPDATES telegram channel. All about Realme GT Master - RMX3366 ROMs, Kernels, Guides, Mods, NEWS, everything. Stay up-to-date with us! Official Group: @RealmeGTMaster Photography : @RMGTMasterPhotography Gaming : @RMGTMasterGaming...
telemetr.io

Use This
https://www.getdroidtips.com/twrp-recovery-realme-gt-master-edition/

Oh i see the problem, it's because the new partition slot A/B.
Ok i have magisk installed on stock rom but i think i will waiting. I stay on UI 2.0 with full root, magisk, lsposed, safetynet, and no bugs

How To Guide [ROOT] [PSYCHE] Root Xiaomi 12x with Magisk

{
"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"
}
Sources used: link
1. First unlock your bootloader. This thread does not cover this. I suggest you do not try to tamper with the 1week~ time gate you will encounter else it may get longer should you fail.
2. Enable Developer mode and adb from Developer settings again.
3 Download the appropriate Fastboot files for your device . See the About section in your phone's settings to know what you are currently running.
4. Download latest Magisk-vXX.Y.apk and install it on your device. Magisk developer only provides files from Github, do not download it from anywhere else.
5. Extract(Install 7-zip if needed) the fastboot .tgz archive and copy the boot.img from it to your phone's sdcard through adb (or other means):
Code:
adb push psyche_eea_global_images_V13.0.3.0.SLDEUXM/images/boot.img /sdcard/
6. Open up Magisk on your phone, press Install and use the patch option to navigate to the boot.img you just copied. Select that, next next next.
7. Read the output to see where the patched boot.img got saved. Pull that.
Code:
adb pull /sdcard/Download/magisk_patched-24300_D2K9V.img
8. Reboot phone to fastboot.
Code:
adb reboot fastboot
9. Flash the modified boot image
Code:
fastboot flash boot recoveryxy.img
10. Flash dtbo (found inside rom zip)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. Say your prayers and reboot, your device should now have functional root with Magisk
Code:
fastboot reboot

This did not work for me. Seemingly flashed okay, but phone is now bootlooping.

weggy101 said:
This did not work for me. Seemingly flashed okay, but phone is now bootlooping.
Click to expand...
Click to collapse
im sorry forgot step 10. flash vbmeta image. updated guide.

nofx161 said:
im sorry forgot step 10. flash vbmeta image. updated guide.
Click to expand...
Click to collapse
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5.0.SLDCNXM/miui-blockota-psyche-V13.0.4.0.SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.

I think it worked here, I patched the boot.img from the EEA ROM I'm running (V13.0.3.0.SLDEUXM_20220528.0000.00_12.0_eea) and the Magisk App says it's installed. The only problem is that I'm not able to edit files and/or paste new ones in the root/system folder.
I'm trying to edit build.prop but it says there's not enough space to complete the operation (using SolidExplorer), I tried to disable my nav buttons with FNG too, but that also won't work.

hey you can use my boot image which is rooted with magisk 25.0
magisk_patched-25000_WA0wW.img
drive.google.com
also the original boot if you messed up
boot.img
drive.google.com

Did anyone solved CTS profile ?

Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.

bjs339 said:
Completed successfully. The steps were really straightforward and easy to execute. The only question I had was about flashing the second slot. These instructions contain the command to flash the active slot only, but the 12x has a and b. I went ahead and flashed the second slot anyway even though it's inactive right now. Also, as was noted in the 12 thread, I was confused why Power-Vol Down boots to "fastboot" while adb reboot fastboot boots to "fastbootd". I don't know, just went with fastbootd and all was fine. Thank you @nofx161 for the instructions.
I haven't really done any testing yet but will report back if I find anything interesting.
Click to expand...
Click to collapse
What ROM do you use? Stock or xiaomi EU or which one? Which modules have you tried? Thanks!

I'm on the stock rom and really haven't done much with it yet, so not much to report at this point.

An alternative way for installing magisk is to install twrp ( https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/ ) and then choose "install twrp" from the advanced menu in twrp. Then restart system and tap on the magisk button. The magisk manager will be loaded from web and your good to go with root.

shortek said:
Did anyone solved CTS profile ?
Click to expand...
Click to collapse
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.

bjs339 said:
Working on it. I've followed the instructions here: https://forum.xda-developers.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/ except that I'm using the Shamiko magisk module instead of the Magisk Deny List per guidance here: https://forum.xda-developers.com/t/chase-app-always-detects-root.4099627/page-9. I have two banking apps working, but not Chase and can't add a credit card to my Google Wallet yet. I tested with YASNAC and it says it passes Safety Net, so we'll see if I can get it figured out. It sounds like the Chase app is a constant struggle, and I'm not too concerned about that, but I'd really like to be able to use Google Pay.
Click to expand...
Click to collapse
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517

bjs339 said:
Got it! This Safety Net mod fixed Google Pay: https://forum.xda-developers.com/t/...tynet-fix-2-3-1.4217823/page-91#post-87198517
Click to expand...
Click to collapse
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).

HikL said:
Do you have Widevine Level 1 with this method? So we could use streaming services on high quality while being rooted. (can be checked by app DRM info).
Click to expand...
Click to collapse
Looks like it if I'm reading that right.

bjs339 said:
View attachment 5699583
Looks like it if I'm reading that right.
Click to expand...
Click to collapse
Great news! Thank you!

Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
boot.img
drive.google.com

kiknalex said:
Hello. Please help me. I did everything as in instructions except one thing and it reboots in MIUI Recovery 5.0 as in this photo https://prnt.sc/Oyjs9lxGVFX8 (not my photo). The only thing that I didn't follow is instead of installing my current MIUI version official boot.img which updated tonight 13.04 Global, I used 13.02 Global because I couldn't find fastboot version of 13.04.
edit: now it started just constant bootloop without going into recovery mode, they just uploaded 13.04 fastboot version and I'm downloading it in with high hopes. I hope that if I patch the boot.img with Magisk in emulation on PC nothing bad will happen.
edit2: Sadly I was unable to do it with PC emulator, I'd appreciate if anyone patched it for me, attached file.
Click to expand...
Click to collapse
I patched boot.img with another phone (huawei or smth) repeated all steps and now it's just stuck in fastboot bootloop...
I tried this
Still gets stuck in a bootloop. Just for fun I downloaded the tgz archive from another source, same situation.
If anyone else gets stuck, here's how to get out of it:
1) Reboot into RECOVERY mode. Select the option for help. It should show a picture of the phone and a USB cable.
2) Follow the onscreen URL for the MiPhoneAssistant Tool
3) I was not able to download via the tool, so I loaded the image in manually with the 2nd option. For my Chinese phone, it was a ~380 MB ZIP file called V13.0.5.0.SLDCNXM, downloaded from:
https://hugeota.d.miui.com/V13.0.5....SLDCNXM-V13.0.5.0.SLDCNXM-ffe7c45215-12.0.zip
4) After finishing, it just boots up to a black screen. Reboot into FASTBOOT mode.
5) From here you can reflash your ROM and be back in business.
But my Mi PC Suite doesn't detect phone when I plug cable, although the icon on phone shows that it's plugged in. Please help me...
Edit: issue was fixed in this thread
Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.
Hello. I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/ only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available...
forum.xda-developers.com

Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla

Voodoojonny said:
Hmmm.... First I would reflash the 13.0.4.0 boot.img to both slots using fastboot.
Copy boot.img to fastboot folder and type
"fastboot flash boot_a boot.img" and then "fastboot flash boot_b boot.img". Now it should boot again. Then you can patch your boot.img and flash it: Copy the patched boot.img to fastboot folder "fastboot flash boot patched_boot.img". Alternatively you can flash magisk via twrp. Therefore download twrp (search our thread), rename the file to twrp.img, copy the twrp.img to fastboot folder, boot the img with "fastboot boot twrp.img" and after twrp is booted go to advanced and tip "flash current twrp" now you have twrp installed. Now you can download the magisk.apk from github, copy it to your internal storage via your pc and flash it via twrp... Violla
Click to expand...
Click to collapse
Thank you for your answer. I already fixed issue in another thread, will edit my comment.

Question Stock boot image - Realme GT Master Edition - RMX3363

Hello!
Can somebody provide a stock boot.img file? (current firmware i have installed is stock RMX3363_11_A.13)
Is it possible to use the boot.img from a higher version for rooting via Magisk Manager (without TWRP).
OTA Update doesn't go higher than A.13 version. I can't find a rom for A.13 version online to download. (so i need boot.img from A.13 version if i can't use it from a higher version number)
Thanks for your support!
Edit: I managed to update and don't need the file anymore.
For update see this thread: https://forum.xda-developers.com/t/rmx-3360-3363-full-ota-c-08.4470035/
Many thanks to Przemek212 for posting this.

i have rmx3363 realme gt master edition android 13 f06 update do you have boot.img file and magisk flash patch to do root ? instead of ADB I use bugijaeger with a second smartphone via USB cable.

piotras3566 said:
i have rmx3363 realme gt master edition android 13 f06 update do you have boot.img file and magisk flash patch to do root ? instead of ADB I use bugijaeger with a second smartphone via USB cable.
Click to expand...
Click to collapse
You have to put .img files into phone, install Magisk-25.2.apk, patch .img files with Magisk then flash .img patched files with fastboot.

Robro86 said:
Hello!
Is it possible to use the boot.img from a higher version for rooting via Magisk Manager (without TWRP).
Click to expand...
Click to collapse
No, you have to use the stock .img files from your installed ROM. You can find A13 ROM here : https://androidfilehost.com/?fid=15664248565197202925, but I don't know if that's the correct ROM for you so use at your own risk !

So I can flash boot.img via magisk and from older Android 12 even though I have Android 13 F06 now and then this file RMX3363_F06_IMG-TO-PATCH.tar.gz flash to fastboot via CMD fastboot flash RMX3363_F06_IMG-TO-PATCH.tar. gz
???

piotras3566 said:
So I can flash boot.img via magisk and from older Android 12 even though I have Android 13 F06 now and then this file RMX3363_F06_IMG-TO-PATCH.tar.gz flash to fastboot via CMD fastboot flash RMX3363_F06_IMG-TO-PATCH.tar. gz
???
Click to expand...
Click to collapse
you need to extract boot.img from Full OTA, fix in Magisk and install via fastboot.

piotras3566 said:
So I can flash boot.img via magisk and from older Android 12 even though I have Android 13 F06 now and then this file RMX3363_F06_IMG-TO-PATCH.tar.gz flash to fastboot via CMD fastboot flash RMX3363_F06_IMG-TO-PATCH.tar. gz
???
Click to expand...
Click to collapse
NO ! Sorry, but I don't think you've mastered the rooting procedure...
In the tar.gz archive, you'll find original stock F06 boot.img and vendor_boot.img + Magisk-25.2.apk. You have to install Magisk, patch the 2 img files with Magisk on your phone, then copy patched img files to your PC and flash them using fastboot (only if you have Android 13 F06 installed on your phone !) :
fastboot flash boot patched-by-magisk-boot.img
fastboot flash vendor_boot patched-by-magisk-vendor_boot.img
(But if you don't really understand what you are doing, don't do it)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I extracted this 51mb file and there are 3 files

piotras3566 said:
I extracted this 51mb file and there are 3 files
Click to expand...
Click to collapse
Ok. Install Magisk then patch the img files

these are 2 files patched and I have to flash them via fastboot?

piotras3566 said:
these are 2 files patched and I have to flash them via fastboot?
Click to expand...
Click to collapse
Yes, as mentioned above

what fastboot command in cmd? fastboot flash boot file name ?

piotras3566 said:
what fastboot command in cmd? fastboot flash boot file name ?
Click to expand...
Click to collapse
I posted the commands at 1:23PM. Replace "patched-by-magisk-boot.img" and "patched-by-magisk-vendor_boot.img" with your correct names.

still please make TWRP work for rmx3363. the marmalade is not working properly

piotras3566 said:
still please make TWRP work for rmx3363. the marmalade is not working properly
Click to expand...
Click to collapse
Sorry but I don't use TWRP (I'm on lunaa LOS recovery which works perfectly for RMX3363) and you're off topic (rooting via Magisk).

one question befor i start flashing the patched files i must do this
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
i am on Original Realme firmware and only want root.

unfortunately, rmx3363 has become a brick and is bricked, go to the realme logo and enter the fastboot state. is the realme repair tool?