For Android 10, you need to flash the magiskboot.img and vbmeta patched by Magisk with verification disabled.
Download Platform Tools (we unpack the folder itself and throw it on disk c) and the oppo drivers (install them), also the patched Magisk boot and the stock vbmeta (we throw the boot and vbmeta into the Platform Tools folder)
go to the phone settings and turn on the developer mode, tapping several times on the build number, go there and turn on usb debugging, go to the c drive, open the folder from the tool platforms, write cmd on the command line of the folder and press enter, the adb console will open.
Spoiler: first way
1 (more difficult way). In the console we enter:
Code:
adb devices
your serial number will be displayed
then enter:
Code:
adb reboot bootloader
phone will reboot and boot into fastboot mode
now in the console we enter:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
to patch vbmetu.
then enter the command to fill our patched boot:
Code:
fastboot flash boot magiskboot.img
after we enter the command to enter the recovery:
Code:
fastboot reboot recovery
We make wipes in recovery.
we go into the system, install the magisk program, then run it, and a window will immediately fly out that an advanced installation is required, we agree, and the body will go to reboot, we enter the system and enjoy root rights.
Spoiler: second way
2 (easier way). you can also boot directly into fastboot mode when the phone is off, for this we hold down the power button and the adjustment button -, the phone will immediately boot into fastboot mode, connect the phone to the computer, then open the console on the computer and enter these commands in turn:
Code:
fastboot devices
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Code:
fastboot flash boot magiskboot.img
Code:
fastboot reboot recovery
We make wipes in recovery.
we go into the system, install the magisk program, then run it, and a window will immediately fly out that an advanced installation is required, we agree, and the body will go to reboot, we enter the system and enjoy root rights.
I have seen vbmeta is optional in Magisk document so I did not write it.
Also, for me, because I usually have problem with ADB command, so I root mine without it. (install Magisk.apk & moving boot and patched one manually.)
Only tool I used here is MTKclient, and got some something interesting here, because I got bootloop with orange state, differs to other into launcher. So I decided to flash patched boot with other partitions
at the same time just after unlock my devices with MTKclient's GUI. Escaping bootloop, then I can use Magisk smoothly like others.
p.s. If u cannot connect devices with ADB, changing USB option to MTP.
to me, I never be in fastboot.
logforjj said:
I have seen vbmeta is optional in Magisk document so I did not write it.
Also, for me, because I usually have problem with ADB command, so I root mine without it. (install Magisk.apk & moving boot and patched one manually.)
Only tool I used here is MTKclient, and got some something interesting here, because I got bootloop with orange state, differs to other into launcher. So I decided to flash patched boot with other partitions
at the same time just after unlock my devices with MTKclient's GUI. Escaping bootloop, then I can use Magisk smoothly like others.
p.s. If u cannot connect devices with ADB, changing USB option to MTP.
Click to expand...
Click to collapse
It is not necessary to sew the MTKclient, it is enough for them to unlock the bootloader with one command, then you charge the flash drive, and sew all the partitions, after that you make a root, patch with a magic boot, fill it with anything, at least with a flash drive, at least through a fastboot, at least with a mtk client, why sew with a flash drive, because the filling speed of the super section is very low for the client's mtc.
logforjj said:
to me, I never be in fastboot.
Click to expand...
Click to collapse
fastboot works perfectly on this device and only on android 10, and it is more convenient to use it, unlike the mtk client
seems this guide is the most fastest way to root this phone, hoping new players can see this topic as soon as they start rooting their devices!
leon2299 said:
fastboot works perfectly on this device and only on android 10, and it is more convenient to use it, unlike the mtk client
Click to expand...
Click to collapse
something did not match this topic: could you share any suggestion to push this devices to the best performance?
I see no custom rom or kernel to overclock or neaten, this make me dissapointed after rooted.
logforjj said:
something did not match this topic: could you share any suggestion to push this devices to the best performance?
I see no custom rom or kernel to overclock or neaten, this make me dissapointed after rooted.
Click to expand...
Click to collapse
You can do custom, download the GSI firmware, unpack the super partition, there will be an image of systems.img, delete it, rename the GSI firmware to system.img, copy it instead of the remote system.img, and pack all this into a format raw then sew the mtk client, well or pack in spars format and sew with a SP Flashtool, if GSI 11 is an android, then you must have realme UI2.0 installed
if you want, I can make you a custom, unpack and pack, I know how, and there just sew a mtk client, a section with a super team:
Code:
python mtk w super super.img
super itself needs to be thrown into the client's mtk folder
all at your own peril and risk
well, or do it yourself, in any case, I shared the information, try it, I put these on this device myself GSI
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net
you can try this
leon2299 said:
if you want, I can make you a custom, unpack and pack, I know how, and there just sew a mtk client, a section with a super team:
Code:
python mtk w super super.img
super itself needs to be thrown into the client's mtk folder
all at your own peril and risk
well, or do it yourself, in any case, I shared the information, try it, I put these on this device myself GSI
TrebleGSI - Browse /LiR/2022.03.25 at SourceForge.net
sourceforge.net
you can try this
Click to expand...
Click to collapse
Well, it seems that these operations are beyond my comprehension.
I've been trying to understand your instructions and find information about them for a while now:
GSI firmware
A/B system
what is super.img
tool to unpack and edit it
It seems that I can't finish the previous operation
unpack tool says: logical partition metadata has invalid geometry magic signature
simg2img says: it is not a super.img
I might know how to write super.img to my device since I have fixed it about unbrick and no sim & IMEI
The phone turns into a brick after using the MTK client client (GUI) function, please help!
When I click on all the erase options, the client only recognizes them but cannot save me back to the phone. The volume and power buttons are not responding. Please help me!
forum.xda-developers.com
I would appreciate it so much if you would explain the steps in more detail(or just make me a custom because of my brainless...)
wait...
What agZ bgZ avZ bvZ and lite mean? · Issue #20 · eremitein/treble-patches
github.com
Maybe I can hadle it by myself.
logforjj said:
Ну, кажется, эти операции выше моего понимания.
Я уже некоторое время пытаюсь понять ваши инструкции и найти информацию о них:
прошивка GSI
А/Б система
что такое super.img
инструмент для распаковки и редактирования
Кажется, я не могу закончить предыдущую операцию
инструмент распаковки говорит: метаданные логического раздела имеют недопустимую магическую подпись геометрии
simg2img говорит: это не super.img
Я мог бы знать, как записать super.img на свое устройство, так как я исправил его с разблокировкой и отсутствием симки и IMEI.
https://forum.xda-developers.com/t/...t-gui-function- пожалуйста, помогите.4420657/Я был бы очень признателен, если бы вы объяснили шаги более подробно (или просто сделали бы мне обычай из-за моего безмозглого...)
Click to expand...
Click to collapse
┤Mod Edit├┤Download link removed├
stuck in orange state, can not boot in (have been wait for a while)
logforjj said:
stuck in orange state, can not boot in (have been wait for a while)
Click to expand...
Click to collapse
if you did everything correctly as in the manual, then when there will be an inscription when loading the orange state, you need to wait 5 minutes, then the system should start, if it does not start, then you are doing something wrong.
leon2299 said:
if you did everything correctly as in the manual, then when there will be an inscription when loading the orange state, you need to wait 5 minutes, then the system should start, if it does not start, then you are doing something wrong.
Click to expand...
Click to collapse
sorry for that I do not I have to wait for so long, I go into recovery and wipe data last night, I think I can do custom rom again now and should be success after 5 mins.
{
"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"
}
After super flashing step is done, I will plug off directly to disconnect without mtk reset.
it does not start after 40 mins.
logforjj said:
After super flashing step is done, I will plug off directly to disconnect without mtk reset.
Click to expand...
Click to collapse
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
I think I got problem due to some manual operation before, like using Magisk patched boot as version 24.2 before processing,
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this is what I concerned about, maybe I never do this on my device？Trying AOSP you provided after waiting an hour for lineage OS, any suggestion is welcome!
logforjj said:
How to flash a Generic System Image (GSI) on Project Treble supported devices
So your device supports Project Treble, what does that mean for you? It means you can flash a Generic System Image such as LineageOS or Resurrection Remix! Enjoy AOSP-based custom ROMs! Here's a guide on how to install these ROMs.
www.xda-developers.com
I think I got problem due to some manual operation before, like using Magisk patched boot as version 24.2 before processing,
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this is what I concerned about, maybe I never do this on my device？Trying AOSP you provided after waiting an hour for lineage OS, any suggestion is welcome!
Click to expand...
Click to collapse
name your region, what firmware and what region you installed before further manipulations, I will download the firmware for your region, get super from there and make you a custom
leon2299 said:
name your region, what firmware and what region you installed before further manipulations, I will download the firmware for your region, get super from there and make you a custom
Click to expand...
Click to collapse
leon2299 said:
if GSI 11 is an android, then you must have realme UI2.0 installed
Click to expand...
Click to collapse
Need to apologize to you for my careless here again, I have not known what that hint means in English exactly, I suppose that it is okay to work on android 10 with realme UI 1.0. I started rooting and unbricking when I initially was android 11 with realme UI 2.0 and end up with android 10 with realme UI 1.0. with magisk 24.2. now I am unbricking device to get information for your demand to getting clear about my region and other.
Related
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?
craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?
U not able to flash boot the stock boot.img?
i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
You need to be in fastbootd,
Code:
fastboot reboot fastboot
craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"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"
}
danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)
@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse
djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support
djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked
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
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
{
"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.
I recently purchased a 9 Pro T-Mobile edition. It was supposed to be a global edition, but this information was willfully obscured by the eBay seller. Whatever, I figured I could follow this guide to convert it to global firmware. I've rooted plenty of OnePlus phones before and am very comfortable with the process, as well as using MSM to fix things when they go wrong. However, things went even worse than normal. I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed. Now I cannot access fastboot or recovery, or do quite literally anything with it.
I figured I'd use MSM and fix it just like I did when things like this happened to my OnePlus 8. So I downloaded the T-Mobile MSM from this thread and ran it. When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
I assumed that this error was due to the fact that some of the images that were successfully flashed are from the global image, while this MSM tool is for TMO specifically, so I tried to the global MSM tool from the same thread instead. It also fails Sahara communication with the exact same error. If I use Lite Firehose, it gives the error "Unsupported Target TMO."
At this point, I'm at a complete loss. I've tried to power off the phone via holding the power button + volume up button, but it never gives any response no matter how long I hold it. I'm not sure that the phone is able to turn on at all. My next guess would be to disconnect the battery and reconnect it, but I'm very hesitant to pull apart the phone without seeing if anyone has any better suggestions first. If I could access fastboot, I could have a download of a clean TMO firmware and could easily re-flash everything, but I can't get a single response out of the phone besides MSM errors. Any help would be much appreciated.
I just realized that that article is for the Oneplus 9 and NOT the Pro. That definitely explains why it broke in the first place, but doesn't help me get it back. The MSM Tools I'm using ARE for the Pro.
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
CZ Eddie said:
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
Click to expand...
Click to collapse
They're both using COM3
blindcat97 said:
They're both using COM3
Click to expand...
Click to collapse
Qualcomm.......9008?
TheGhost1951 said:
Qualcomm.......9008?
Click to expand...
Click to collapse
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
blindcat97 said:
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
Click to expand...
Click to collapse
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
TheGhost1951 said:
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
Click to expand...
Click to collapse
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
CZ Eddie said:
Is there something in this link that will help?
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com
Click to expand...
Click to collapse
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
blindcat97 said:
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
Click to expand...
Click to collapse
I'm a little confused about how you got your phone to its current state.
Your first paragraph has some minutia in it.
" I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed."
What images did you download and how did you apply them to your phone?
I was following this guide to convert OP9 (not *pro*, which is where I messed up and I feel very stupid for not realizing that) from T-Mobile to Global firmware. It provided download links to a zip file full of img files, and a flash-all.bat which used fastboot commands to flash the individual files. Half of the files didn't flash because "Flashing critical partitions is not allowed", but some of them did flash successfully. There's no log file to tell me which ones did and did not work. Here's the chunk of the flash-all script that actually contains the fastboot commands:
Spoiler: flash-all excerpt
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot --disable-verity flash vbmeta_vendor vbmeta_vendor.img
fastboot reboot fastboot
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash splash splash.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash abl abl.img
fastboot flash bluetooth bluetooth.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash tz tz.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot reboot fastboot
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash odm odm.img
It got through the first reboot okay (despite booting to fastbootd and me having to manually redirect it back to fastboot), but when it reached the second reboot command, it just died and wouldn't turn on any more, and the third block of commands were never executed. So I'm guessing that something it flashed in that second block is what completely broke its ability to boot. I would flash the images from a clean copy of OP9Pro TMO firmware, but I can't get to fastboot at all.
blindcat97 said:
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
Click to expand...
Click to collapse
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
im not really that experienced with this stuff but this kind of happened to me today so i decided to make an account and try to help you. Basically what I did was I deleted everything on it, like I could only use fastboot mode. Then i used an msm tool from here. make sure you get the tmobile one because i tried global and it didn't work. after i used the msm tool it started working again. once again, i am not experienced in this stuff, so my advice may screw you over, but at this point you don't really have anything to lose.
TheGhost1951 said:
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
Click to expand...
Click to collapse
From my original post: When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
I've never run into the firehouse issue before.
But it's very common and is talked about in dozens of threads here.
But it looks like you've actually flashed some system files from a different phone.
I hope that doesn't mean MSM is rejecting you because it thinks you're a different phone.
Maybe try flashing a 9pro boot.img that would match the software you're supposed to be at right now?
Not sure if that'll mess you up more or not though.
Double-check that you've downloaded the correct MSM file
Research the SMT mode.
It's disabled for a reason - because it'll wipe your IMEI & other important things.
I don't know how to use it yet, but supposedly it'll fix unfixable things. When used properly.
{
"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 have no way of flashing. I can't get to fastboot, I can't get the phone to respond to quite literally anything other than MSM. Any combination of buttons does nothing. I'm not a professional with this stuff; if there's a way to flash to EDL without MSM, I don't know it. It looks like MSM rejecting because it thinks it's a different phone is exactly what's happening, and the only thing I can think to do would be essentially to mod it so that it thinks it's allowed to flash OP9 as well as 9Pro, or otherwise bypass the device check.
I'm certain I've got the right MSM tool. Doing some research into the SMT Download mode, it looks like it breaks core features, like the IMEI, and widevine. Is it possible to backup those partitions from EDL mode?
Basically, if my only way of recovering the device is to destroy critical sectors entirely, I might just send the device to OnePlus for repairs. My warranty was already voided by unlocking the bootloader.
blindcat97 said:
I can't get to fastboot
Click to expand...
Click to collapse
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.
CZ Eddie said:
Why not? What happens when you power off the phone.
Wait 15 seconds.
And then press + hold the volume(-) and power button at the same time?
Remember to hold them until *after* the splash screen comes up.
Click to expand...
Click to collapse
The phone is already off and cannot be turned on in any way, to any mode. Nothing happens when I hold that combination, nor any other. The phone is completely unresponsive.