Database Develop

Alternate TWRP v3.1.1.0 and Root for Albus/Moto Z2 Play US Retail

What this thread is for:
Booting into TWRP Recovery for the Moto Z2 Play Retus Variant
Rooting the Z2 Play Retus Variant with Magisk
Things you will need:
IMPORTANT: You WILL need a USB C OTG cable and USB Thumbdrive (or a USB C Thumbdrive)
Magisk Zip 13.3 Mod uploaded by Junior Passos: https://www.androidfilehost.com/?fid=889764386195922735
Magisk Manager v5.1.1 apk: https://github.com/topjohnwu/MagiskManager/releases/download/v5.1.1/MagiskManager-v5.1.1.apk
DM Verity and Forced Encryption Disabler v5.1: https://androidfilebox.com/miscellaneous/dm-verity-and-forced-encryption-disabler/
My modified TWRP: https://www.androidfilehost.com/?fid=673368273298983327 md5: ebcecfaf2e00725561555dd398f883dc
Magisk ZIP and DM Verity ZIP must be put on a thumbdrive. Installing from (external) SD Card will not work with this version of TWRP.
Things you will need to keep in mind:
Make sure you fully update your device before unlocking and rooting as it likely will break OTAs. You'll likely have to rely on stock images posted by users to this forum from now on.
In order to be able to do what you need to do in TWRP, you will need to format data due to forced encryption. You won't be able to root and boot your device otherwise.
My version of TWRP is a hacky build. It works, but one feature in particular does not work: External SD card mounting. Until an updated build is made to fix this issue (of which I will require the assistance of people MUCH better at this than I am), you will need to use a USB C OTG cable and a thumbdrive to be able to back up your device and to flash ZIPs.
Try booting (not flashing) the TWRP build here first: https://forum.xda-developers.com/z2-play/development/twrp-3-1-1-0-moto-g5-plus-albus-t3622593 - If it doesn't work (hangs on logo), then try mine.
DO NOT install SuperSU from within TWRP.
These instructions assume you know how to use ADB and Fastboot Android tools. If you need the utilities, you can download the Windows versions from here: https://forum.xda-developers.com/showthread.php?t=2317790
How to boot into TWRP, make backups and root your device:
0) Your device must already be bootloader unlocked.
0a) DO NOT install SuperSU from within TWRP!!
1) Boot into Fastboot (powered off, hold down Power and Vol Down)
2) Plug your USB C cable into your computer and phone, make sure you have the Android tools installed.
3) Use fastboot command to boot into TWRP (NOT flash): fastboot boot albus_twrp.img
3a) I do not recommend flashing this version of recovery to the device because, as I said before, it's a hacky build. I don't want people to rely on it as their permanent recovery in case issues are found and fixed later.
4) Swipe to allow modification, click Cancel when it asks for passphrase to read encrypted partition.
5) Press Wipe on main screen, slide to wipe. This will wipe Data, Cache and Dalvik partitions. You will need to do this because the partitions will have to remain unencrypted after you flash DMVerity and Encryption Disabler.
5a) Yes, you have to wipe. DM Verity and forced encryption will cause your device to fail to boot if you don't disable them.
6) Back up your device. Attempting to back up System Image may fail because the partition is over 4GB and nearly every thumbdrive will be formatted in Fat32. Back up System, Boot and Recovery.
7) Install DM-Verity ZIP.
8) Install Magisk ZIP linked in this thread.
9) Reboot into system. Anticipate a longer first boot.
10) Sideload Magisk Manager.
Magisk running on Z2 Play:
{
"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"
}
What I did:
Extracted kernel, img_info and dt.img from the retus albus system image and dumped it into a harpia twrp build. I suspect the other version of TWRP was built against a different AOSP version, triggering a SELinux boot block. In my version of TWRP, fstab paths are correct but for some reason MicroSD won't mount. I'll leave that to the professionals. Everything else that I did (as described above) worked and was my exact method for doing so.
Finally:
Special thanks to Dees_Troy for TWRP. Without you, devices would suck.
Here's the Moto Z2 Play Albus boot.img for anyone who wants to take on the task of doing an official TWRP build for the device. https://www.androidfilehost.com/?fid=889764386195927416

You're the man. I'll give this a shot today and report back.

Great tutorial! One question: Does your device pass the "SafetyNet check"?

romhippo.com said:
Great tutorial! One question: Does your device pass the "SafetyNet check"?
Click to expand...
Click to collapse
In my case... it does not fully pass. Passes Safetynet Request and Response Signature... but fails on the Basic Integrity and CTS Profile Match tests. I also did modify /system (ad away, removed bootanimation.zip, moved Magisk apk and Substratum apk into /system) so that could be why.
https://i.imgur.com/u9OVkUq.png

Followed the directions to the letter and everything is working for me. Thanks a lot, twelfth!

Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.

Just a heads up guys. Flashed Magisk 14.0. Passed safetynet. Can't download/install modules though, gives Parse Error or something. Haven't tried installing modules through TWRP to see if it works.

atheart said:
Can't download/install modules though, gives Parse Error or something.
Click to expand...
Click to collapse
I have had the same issue with Magisk 13.3 ...

This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....

cantsingh said:
Twelfth, sorry for going offtopic a bit, but was anyone successfully able to install a Substratum theme on the device? I'm running into issues when attempting to theme Android System / System UI. Everything else seems to work flawlessly.
Click to expand...
Click to collapse
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
cmjester6421 said:
This may sound like a bad question but I know that VZW has a locked bootloader is there and successful chance that this will work on the VZW variant?
Please try not to flame me for this....
Click to expand...
Click to collapse
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.

twelfth said:
Substratum is strange. I've had issues getting white text on dark backgrounds to work until I just re-applied specific elements like Android System after I applied System UI and rebooted. Sometimes I couldn't even get notifications to look normal until I applied elements from a second theme (Swift Dark > Reboot > Default Dark > Reboot, it works)... just gotta keep fussing with it until it sticks.
Nope. Locked bootloader means locked bootloader. You must be unlocked first before you can flash or boot unsigned/unofficial images.
That said, if you ordered the Z2 Play Unlocked from Motorola, chances are you'd be able to use it on Verizon by swapping out the sim card since the unlocked Z2 Play is compatible with all carriers. This means swapping out an already activated sim card yourself, NOT activating the device on Verizon.
Click to expand...
Click to collapse
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:

Cameras not working post root
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.

Can you make this alittle more simple like in steps, I recently got this phone and I want to root it

cantsingh said:
Thanks for the response! Yeah, I encountered the same behavior. Seems like I almost got a working combination using just Swift Black, but random UI elements would be black on black rendering them unreadable. No worries, a small price to pay!
As for your second point - I can confirm that the US Unlocked Z2 does work on Verizon with an unlocked bootloader. :good:
Click to expand...
Click to collapse
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!

ihatevz said:
How did you verify this? I recently bought the US Retail (non verizon) version and it isn't letting me unlock the bootloader. So what phone did you buy then that allowed you to unlock the bootloader?
Nevermind I'm an idiot. I forgot to check the button in the developers option to "unlock oem bootloader"
Forgive me all!
Click to expand...
Click to collapse
Haha, we've all been there! :good:

Alabamajackhammer said:
So I basically did the same thing but didn't use this site. Unlocked bootloader, flashed TWRP via adb and fastboot, flashed magisk. I'm rooted and have the XT1710-01 rooted on stock firmware. I did only what I said I did, nothing like sideload and putting anything on or flashing any other zips, only magisk. I need a camera fix ASAP and I can't find one.
Click to expand...
Click to collapse
What's wrong with the camera, after root?

Are there no images to restore out yet?

Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?

Pooper22 said:
Wait so if we have a phone that came from verizon we can't root it because of the locked bootloader right?
Click to expand...
Click to collapse
Yes. I'm surprised that this surprises you.

Is there a specific reason why op says not to flash SuperSU? Will it not work or damage something?

[GUIDE] Full process of installing Magisk & TWRP on a OnePlus 7 Pro (TMOBILE SUPPORT)

For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
You need to start downloading three updates. This patched version of international OOS is where you will start, the developer beta will upgrade the bootloader, and the full downgrade will roll you back so you can start updating. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Now it's time to install international OOS. Place it inside the folder with MSM Download Tool and then start it up. Uncheck the SHA-256 checkbox!
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of EDL mode into fastboot.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. Feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy the developer preview update to the phone. Don't copy it to the Download folder or anything, copy it into the root (just inside the internal storage). Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use fastboot oem unlock. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
After rebooting, since the unlock wiped the phone, you'll have to set it up again. Just breeze through like before, then copy the rollback zip to the phone just like you did for the developer preview.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here (MD5 fcec14e2ec053d67c793a27bfdef17d0), and use local update to install it. (note GM21BA instead of GM21AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM21AA to GM21BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
You can find other versions of OOS in this XDA post.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.

Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.

TheMadScientist said:
Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.
Click to expand...
Click to collapse
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.

Today I had a little incident with SafetyNet.
{
"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 had installed the magisk modules Riru and Riru - EdXposed. Big mistake. Uninstalling them didn't fix it. Reinstalling the OS didn't fix it. I thought I was totally ****ed. However, toggling MagiskHide off and back on again and clearing Google Play Services' data seems to have fixed it:
Phew. This SafetyNet guide really helped
EDIT: Also make sure to clear Play Store's data so it re-checks your device for certification.

LoganDark said:
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.
Click to expand...
Click to collapse
Unfortunately we can't discuss that on xda.

TheMadScientist said:
Unfortunately we can't discuss that on xda.
Click to expand...
Click to collapse
Software spoofing is allowed. EMS flashing is not.

Riru - EdXposed seems to pass SafetyNet if you use HiddenCore module (and DO NOT BLACKLIST GOOGLE SERVICES or else they will not get patched and they will fail you). I haven't checked to see how deep this goes. Perhaps third party apps which do their own SafetyNet check will see through it. Anyone here with experience?
Edit: BAD ADVICE DO NOT USE HIDDENCORE IT WILL BREAK SAFETYNET EVEN MORE

Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards

LokifiedMee said:
Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards
Click to expand...
Click to collapse
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)

LoganDark said:
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)
Click to expand...
Click to collapse
No worries mate. Just giving you the heads up. Cheers

I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw

Leskanic said:
I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw
Click to expand...
Click to collapse
Apologies for the late reply.
Download the "twrp-installer" zip file and use Magisk to flash it.
After that, you have to "direct install" Magisk again.

I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help

Leskanic said:
I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help
Click to expand...
Click to collapse
The TWRP installer zip is just a Magisk module that you can flash by going to the modules section and tapping "install from storage".
Basically, step 1: go into this section and install the twrp-installer zip this way
Step 2: go here
and direct install Magisk like this
Yes, you are installing Magisk again. That is because the TWRP installer overwrote it, and if you rebooted, you would lose root (and the stock ROM would immediately overwrite TWRP, leaving your device completely stock)
As for flashing both things via TWRP, you would probably flash TWRP first and then Magisk. If you can get the phone to boot into TWRP in the first place, yeah it's probably possible and many others have probably installed their TWRP+Magisk that way.

Thanks i didn't realize the twrp installer zip could be flashed as a module. Sorry it's been a while and I'm trying to get back up to speed

I have a few XPrivacyLua hooks that can be used to change your model number to GM1917 (at least to Java apps). It doesn't have any side effects except peace of mind.
Add these using the XPrivacyLua Pro companion app (you don't need to buy Pro to edit hooks), MAKE SURE to enter GM1917 in the model text box and save, enable them for every app including system apps in XPrivacyLua, and reboot.
Enjoy

LoganDark said:
For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
Start the MSM Downloader tool and make sure that it's open and ready. Uncheck the SHA-256 checkbox!
You need to start downloading two updates. The developer beta will upgrade the bootloader, and the full downgrade will give you a reference boot.img to use for Magisk. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of MSM mode.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. This one will be overwritten, so feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy both updates (developer preview & rollback) to the phone. Don't copy them to the Download folder or anything, copy them into the root. Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use `fastboot oem unlock`. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here, and use local update to install it. (note GM27BA instead of GM27AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM27AA to GM27BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.
Click to expand...
Click to collapse
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?

r4w0ne said:
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?
Click to expand...
Click to collapse
OOPS, fuck, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Edit: Post has been updated

LoganDark said:
OOPS, ****, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Click to expand...
Click to collapse
Glad I asked lol.

r4w0ne said:
Glad I asked lol.
Click to expand...
Click to collapse
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated

LoganDark said:
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated
Click to expand...
Click to collapse
New problem, OEM unlocking is greyed out in the options on the developer preview...
EDIT: I'm a retard and didn't follow instructions. Ignore.

[ROM] DivestOS 20.0 for mata

{
"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"
}
DivestOS is a more private and more secure aftermarket system.
Essential Phone Notes:
- please install PH1-Images-QQ1A.200105.032.zip to both slots first!
edit 2022: firmware is included for a while now
- relocking does work, just take the steps slow and test before locking
- device must be relocked to enable verified boot
- phone call audio can be weird, toggling speaker phone usually fixes it
- phone call audio over bluetooth doesn't always work
- phone call speaker phone volume cannot be adjusted
- in-place upgrade from 17.1 to 18.1 has been tested working
- in-place upgrade from 18.1 to 19.1 has been tested working
Features:
- strong focus on FOSS
- various system hardening
- various privacy enhancements
- automated removal of unnecessary proprietary blobs
- automated kernel hardening and CVE patching
- ability to relock bootloader on supported devices
- verified boot on supported devices
- no root support
- SELinux always enforcing
- encrypted by default
- monthly updates
- OTA delta updates
- OTA updates over Tor (optional)
- F-Droid included
- hardened system WebView with rapid updates: https://divestos.org/misc/ch-dates.txt
Extra Features (not installed by default & also compatible with all systems):
- Mull, our hardened fork of Fenix with rapid updates: https://divestos.org/misc/ffa-dates.txt
- Hypatia, our real-time malware scanner
- Extirpater, our free space eraser
Links:
- Website: https://divestos.org
- Onion: http://divestoseb5nncsydt7zzf5hrfg44md4bxqjs5ifcv4t7gt7u6ohjyyd.onion
- Downloads: https://divestos.org/index.php?page=devices&base=LineageOS#device-mata
- Changelogs: https://divestos.org/index.php?page=news
- Project History: https://divestos.org/index.php?page=history
- Known Issues: https://divestos.org/index.php?page=broken#mata
- Screenshots: https://divestos.org/index.php?page=screenshots
- Security Patching Overview: https://divestos.org/index.php?page=patch_levels
- About + Credits + Notices: https://divestos.org/index.php?page=about
- Donate: https://divested.dev/donate
- Source Code: https://github.com/divested-mobile or https://gitlab.com/divested-mobile
- XMPP Chat Room: xmpp:[email protected]
Device Specific Links
- Device Tree: https://github.com/LineageOS/android_device_essential_mata
- Kernel: https://github.com/LineageOS/android_kernel_essential_msm8998
- Kernel CVE Patches Applied: https://github.com/Divested-Mobile/..._Patchers/android_kernel_essential_msm8998.sh
Other Bits:
- Good and bad feedback is welcomed. Else how can we improve?
- If you find a bug, please report it below or via GitHub/GitLab.
- Testing/Translations/Code contributions are gratefully appreciated.
Important Notes for New Users:
- Please make a backup of your device and copy it to another computer.
- You must wipe before installing this OS.
- This OS has userdata encrypted by default
- You are intended to relock your bootloader with this OS (if your device is marked supported for that).
DivestOS does *not* support the following:
- Google Apps (OpenGAPPS)
- DRM (Widevine)
- alternative recoveries (TWRP)
- root (Magisk)
- runtime modification frameworks (Xposed or theme engines)
All downloads are GPG signed with the following key:
Code:
#B874 4D67 F9F1 E14E 145D FD8E 7F62 7E92 0F31 6994
-----BEGIN PGP PUBLIC KEY BLOCK-----
mDMEXupIxBYJKwYBBAHaRw8BAQdAC1RiTvrqJaAQ4FIHsxX+gzEgdT4mspISS+p0
y847Nge0SERpdmVzdE9TIFJlbGVhc2UgU2lnbmluZyAoMjAyMCAjMSkgPHN1cHBv
cnQrcmVsZWFzZXNpZ25pbmdAZGl2ZXN0b3Mub3JnPoiQBBMWCAA4FiEEuHRNZ/nx
4U4UXf2Of2J+kg8xaZQFAl7qSMQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA
CgkQf2J+kg8xaZR1BgEAwwLVVsG7kbp8M3GTV987XpVl5cZeTtDc/g+66briCHUB
APiuH/dk8eRnhFnq4Up2/j7uD/8FtSvxPbHiz6t1MdgB
=VzP2
-----END PGP PUBLIC KEY BLOCK-----

SkewedZeppelin said:
relocking does work, just take the steps slow and test before locking
Click to expand...
Click to collapse
I'm interested to try DivestOS on mata, especially because of the potential for relocking.
I'm fairly sure that when I first unlocked bootloader it was with fastboot flashing unlock followed by fastboot flashing unlock_critical.
If relocking is still possible would I have to fastboot flashing lock_critical first, followed by fastboot flashing lock?

chrisrg said:
I'm interested to try DivestOS on mata, especially because of the potential for relocking.
I'm fairly sure that when I first unlocked bootloader it was with fastboot flashing unlock followed by fastboot flashing unlock_critical.
If relocking is still possible would I have to fastboot flashing lock_critical first, followed by fastboot flashing lock?
Click to expand...
Click to collapse
Lock should cover critical.

Thanks for that.
Carefully following instructions here to prepare the phone and subsequent flashing of the DivestOS all went smoothly.
Post install I downloaded the latest OTA update and did a bit of testing before locking the bootloader with fastboot flashing lock command.
Very nice, thanks .

Want to give this a try on my PH-1. I am on LineageOS 18.1 latst build. Anything in specific I should take care of? Any pitfalls?
Edit: Took sometime to clean-up and go back to the mentioned stock firmware. The flash went through fine. Will test things out first and then dare to relock

Dear DivestOS maintainer.
I`m using a DivestOS for almost a year.
Recently i start facing an issue, that my camera cannot send information to the servers. I cannot use it for a face identification and QR codes approvals.
Is this a new feature? Or i mess with something and have to reflash the rom?

WillWire said:
Dear DivestOS maintainer.
I`m using a DivestOS for almost a year.
Recently i start facing an issue, that my camera cannot send information to the servers. I cannot use it for a face identification and QR codes approvals.
Is this a new feature? Or i mess with something and have to reflash the rom?
Click to expand...
Click to collapse
Can you elaborate?
mata is my daily driver, it is very stable.
If you mean no camera app works, do you have the 'sensors off' tile enabled? That disables the camera in addition to sensors.
If you mean the camera app works, but some apps that use the camera don't, can you say which app?

SkewedZeppelin said:
Can you elaborate?
mata is my daily driver, it is very stable.
If you mean no camera app works, do you have the 'sensors off' tile enabled? That disables the camera in addition to sensors.
If you mean the camera app works, but some apps that use the camera don't, can you say which app?
Click to expand...
Click to collapse
Sorry for a late reply. Forced to flash back to latest LOS.
Apps which are not working are Binance, Wirex, WhatsApp(I hate it, but have to use it)
Basically operations such as scan QR code or Face Id were not working.

SkewedZeppelin said:
Can you elaborate?
mata is my daily driver, it is very stable.
If you mean no camera app works, do you have the 'sensors off' tile enabled? That disables the camera in addition to sensors.
If you mean the camera app works, but some apps that use the camera don't, can you say which app?
Click to expand...
Click to collapse
It appears to be LOS or MicroG issue. Same here on latest LOS. i was thinking of Bromite, but problem persists on LOS WebView.

WillWire said:
Sorry for a late reply. Forced to flash back to latest LOS.
Apps which are not working are Binance, Wirex, WhatsApp(I hate it, but have to use it)
Basically operations such as scan QR code or Face Id were not working.
Click to expand...
Click to collapse
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.

SkewedZeppelin said:
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.
Click to expand...
Click to collapse
Nope, SafetyNet is passable using MicroG.
WhatsApp is .... , but it required to communicate with my employer.
Otherwise i'm using only Matrix/Telegram/Status/Briar.

SkewedZeppelin said:
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.
Click to expand...
Click to collapse
Nope, SafetyNet is passable using MicroG.
WhatsApp is .... , but it required to communicate with my employer.
Otherwise i'm using only Matrix/Telegram/Status/Briar.
SkewedZeppelin said:
The first two sound SafetyNet related.
I don't use WhatsApp, but afaik it should fully work without Google Apps.
Click to expand...
Click to collapse
Just after couple another atempts, i may say that it is looks like a Zygisk issues. Whent i enable Denylist Binance is giving a WebView error.
I was thinkinh of Bromite WebView at first, but apparently it was not as issue.
Great Rom, will be comming back soon)).
Another anoyance for myself, why Mata camera360 and AptX drivers are disabled? As they are available in LOS.
Camera is heavilly GMS dependant, i understand. But AptX is not.
Is there any security concern regarding this thechnology?

very happy with this rom so far. I have been using it as a daily driver for 2 weeks now and I will continue to use it. i will be sure to post any issues i find here.... thanks!

Anyone had issues with the "adb sideload copy-partitions-mata.zip"? It fails for me on setup to install sideloaded zip with `permission denied` on unmount of /vendor/firmware_mnt.
This particular phone really doesn't like fastboot (any version) and/or my USB cables, but occasionally it will work. One lucky session I got DivestOS (system, vendor, and boot) onto slot a successfully.
Aside: I appear to have triggered the dm-verity corruption along the way with my flashing of various ASOP (GSI thread) and lineageOS. I don't think it is related to this error.

chaseadam said:
It fails for me on setup to install sideloaded zip with `permission denied` on unmount of /vendor/firmware_mnt.
Click to expand...
Click to collapse
This is a known issue with the DivestOS recovery for mata. I have no idea why it happens, spent hours trying to figure it out.
chaseadam said:
This particular phone really doesn't like fastboot (any version) and/or my USB cables, but occasionally it will work. One lucky session I got DivestOS (system, vendor, and boot) onto slot a successfully.
Click to expand...
Click to collapse
Mata was my daily driver, and is still actively tested. It does work well aside from the recovery quirk.
chaseadam said:
Aside: I appear to have triggered the dm-verity corruption along the way with my flashing of various ASOP (GSI thread) and lineageOS. I don't think it is related to this error.
Click to expand...
Click to collapse
Recommend flashing stock then DivestOS again.
The official mata stock is no longer available, but you can find mirrors of it.
Here is the sha512sum for you to verify against
a9d979fdde4b2b59ff9c0c1256f440b4d5250242179648494a9b641ca75b4911cae666b6197162b6a93009b94cdc07f9f04df2bd0a72e819db09f7392f60ddde PH1-Images-QQ1A.200105.032.zip

SkewedZeppelin said:
This is a known issue with the DivestOS recovery for mata. I have no idea why it happens, spent hours trying to figure it out.
Click to expand...
Click to collapse
So if you haven't run that copy-partitions-mata.zip, did you re-lock your bootloader? If so, what was your procedure? My understanding is both slots need to be the same for the re-lock to work (without bricking?)
SkewedZeppelin said:
Mata was my daily driver, and is still actively tested. It does work well aside from the recovery quirk.
Click to expand...
Click to collapse
That quirk is annoying, and just when I am about to give up, it starts a "working" fastboot session
SkewedZeppelin said:
Recommend flashing stock then DivestOS again.
The official mata stock is no longer available, but you can find mirrors of it.
Here is the sha512sum for you to verify against
a9d979fdde4b2b59ff9c0c1256f440b4d5250242179648494a9b641ca75b4911cae666b6197162b6a93009b94cdc07f9f04df2bd0a72e819db09f7392f60ddde PH1-Images-QQ1A.200105.032.zip
Click to expand...
Click to collapse
Had that stock already downloaded, so after a bunch of "banging" at it, the flashboot writes finally got through (lots of reboots and re-plugging).
This was my sequence to get past the "device is corrupt” dm-verity message and boot to DivestOS
slot A has latest Stock
slot B has DivestOS
Boot to slot A
adb reboot "dm-verity enforcing"
boot into Stock
switch to slot B
format userdata
boot DivestOS without dm-verity warning!

double post

double post

chaseadam said:
So if you haven't run that copy-partitions-mata.zip, did you re-lock your bootloader? If so, what was your procedure? My understanding is both slots need to be the same for the re-lock to work (without bricking?)
Click to expand...
Click to collapse
My bootloader has been locked for like 3 years, never unlocked except for testing.
In the case of mata, that isn't needed because firmware is included.
Also try cleaning out your usb port, and using a usb-2.0 port on your computer.

SkewedZeppelin said:
My bootloader has been locked for like 3 years, never unlocked except for testing.
In the case of mata, that isn't needed because firmware is included.
Click to expand...
Click to collapse
Great news! I hope to get to a locked state soon as well.
I see references to "firmware is included" (your comment) and "firmware-empty" and "A/B devices only without firmware enabled".
What is this "firmware" in relation to the boot, system, vendor and other images? Is the firmware related to AVB?
Is the PH-1 an AVB device? (does it require working with `avb_custom_key` in fastboot)
I am attempting to be thorough because of all the warnings about locking resulting in a brick.
Aside: There is mention of "full" and "yes, ue" in the firmware-empty status. What do "ue" and "full" mean?

Question Downgrading from Android 12 to Android 11 without adb

Hi. Is there a way to downgrade from Android 12 to Android 11 without using a computer? I have a firmware package in the root path however phone does not show the possibility to downgrade (i've read it should be in notification panel but it's not). Regards

hello
in first you need the right dongrading firmware for yoyr device :from asus server :
exemple :
{
"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"
}
firmware must be in root or sd card and follow step 3 here:
GUIDE: How to unbrick your Zenfone 6 (ZS630KL)
Hello. This guide will help you unbrick your device in case your devices hangs as it boots, and always boots into fastboot mode and recovery is unavailable and the like. Note: Unlocked bootloader is not required to do any of the actions...
forum.xda-developers.com
regards

I have a correct firmware .zip file in root path however in Android Fasboot menu I have only following options:
- Reboot system now
- Enter recovery (it just takes back to the previosu menu)
- Reboot to bootloader
- Power off
How to use command adb reboot recovery without using a computer (as stated in first post)?

so maybe you have one of the lastest andoid 12 version and now you can't downgrade
if we don't know which version you have and you try to downgrade it's very hard to help you

My current firmware version is 31.1010.0410.72
I'm trying to downgrade by flashing firmware that is visible in the screenshot in post #2

I have the same problem, A12 firmware version is 31.1010.0410.72 , the phone doesn't pop up a message which detected a firmware update info.
maybe also interesting
(in recoverymode only :
Reboot system now
Reboot to bootloader
Enter fastboot
Wipe data/Factory reset
Run graphics test
Power off)
I do have a PC and adb
Can I downgrade with these instructions ? I'm scared:
Android-12-Beta | ASUS Global
www.asus.com
the bottom of the link

eboelens said:
Can I downgrade with these instructions ? I'm scared:
Android-12-Beta | ASUS Global
www.asus.com
the bottom of the link
Click to expand...
Click to collapse
Hi
yes , I did that and it worked
But keep in mind that the script used to downgrade will delete ALL files on your phone.
And as far as I know there is no other way to downgrade the OS from 12 to 11.
regards
Bernd

Thanks,
1.can you tell me when you did that that the bootloader was untouched and locked ?
2.can I do something wrong ?
3.Is it better unlock the bootloader and install twrp ?
(the basic recoverymode gives me no possibilty for use an upgrade or adb sideload)
4. I want install /e/ on it , /e/ expect A11 on it
I'm still scared:
I get an answer from Asus:
Usually, the downgrade is only intended for the first batches of Android 12. According to the data you provided, your phone is up to date and you are therefore using the most recent Android 12 version. The downgrade is not written for such a version given that it is now 4 months old and was intended for users at the time where the first upgrade to Android 12 did not suit.
I will check internally for you what the possibilities are, but keep in mind that there is a chance that we no longer offer a downgrade for this version of Android 12.

Hi
1. can you tell me when you did that that the bootloader was untouched and locked ?
Click to expand...
Click to collapse
As far as I know the bootloader is not touched (I'm not sure if downgrading via that script works with a locked bootloader - but I did not test that)
2.can I do something wrong ?
Click to expand...
Click to collapse
Well, there is always the change that something goes wrong doing this kind of stuff. But regarding the script the only thing you do is starting the script - the script will execute all neccessary steps for the downgrade without user intervention and will only ask for confirmation for the last reboot from the new installed Android 11
But if the script fails for whatever reason you should know how to fix this kind of error before using it.
3.Is it better unlock the bootloader and install twrp ?
(the basic recoverymode gives me no possibilty for use an upgrade or adb sideload)
Click to expand...
Click to collapse
As far as I know you can not downgrade using the standard installation via TWRP or any other recovery ROM (but that might be wrong - you can try it before using the script ...)
4. I want install /e/ on it , /e/ expect A11 on it
Click to expand...
Click to collapse
I never tested that OS, probably you should wait for an A12 based version of the OS.
Usually, the downgrade is only intended for the first batches of Android 12. According to the data you provided, your phone is up to date and you are therefore using the most recent Android 12 version. The downgrade is not written for such a version given that it is now 4 months old and was intended for users at the time where the first upgrade to Android 12 did not suit.
Click to expand...
Click to collapse
The installation of Android 11 here is only to prepare the phone for another Android 11 based distribution as far as I understand so this can be ignored. But if you stay on the original ASUS Android 11 you should update the OS to the latest version of Android 11 released by ASUS after downgrading.
regards
Bernd

sqfaaa said:
Hi. Is there a way to downgrade from Android 12 to Android 11 without using a computer? I have a firmware package in the root path however phone does not show the possibility to downgrade (i've read it should be in notification panel but it's not). Regards
Click to expand...
Click to collapse
Yes, the instructions state to download the zip file into the root directory and wait for a few min after rebooting preferably, no need to unzip. However, the person uploading the files seem to be mixing up the file name format for various devices. You need to check which format is compatible for your device : UL-ASUS_I006D-ASUS or UL-I006D-ASUS. The file name has to be EXACT for the update for upgrade or downgrade to TRIGGER. Hope that helps.

Downgrading to Android 11 was possible with either through PC and the developer system image zip or downloading the zip file and letting the phone detect it, though out of the box after updating to A12 the phone didn't detect the zip. I had to go through the PC and run the update_image.bat from the provided firmware.
Problem is, after starting A11, right after getting an internet connection the phone starts downloading and updating to Android 12 automatically. It can't be stopped, or disabled. God damned infuriating, makes me want to return the phone, but I know there are no other options for this kind of phone.
I have no other option than to unlock the bootloader, root, and disable the update apps through adb. At the same time I'm possibly denied warranty. F*cking senseless bull**** that if I prefer to use A11 I can't without problems. Sure the security patches are a bit older, but people make too big of a deal out of them. You aren't instantly getting hacked even with a few year old security patches.
edit:
I have managed to stop the update service permanently in android 11. You need to enable developer options, then connect usb debugging and open an adb shell, which should as for authorization on the phone.
In the shell, type
pm uninstall -k --user 0 com.asus.dm
pm uninstall -k --user 0 com.asus.UpdateLauncher (this might be just the new phone wizard for restoring files etc)
which should return "Success", even without root. I'm not sure if you need to uninstall both of them, or just dm, which is the main update process. In any case, the whole system update section in settings has disappeared. Fine by me, I can install them manually, which is all that I wanted as an option. You can uninstall other packages too, pm listpackages produces a list of them, and you can filter it like "pm listpackages facebook" to show only results with facebook in the name.

Jgruar said:
Downgrading to Android 11 was possible with either through PC and the developer system image zip or downloading the zip file and letting the phone detect it, though out of the box after updating to A12 the phone didn't detect the zip. I had to go through the PC and run the update_image.bat from the provided firmware.
Problem is, after starting A11, right after getting an internet connection the phone starts downloading and updating to Android 12 automatically. It can't be stopped, or disabled. God damned infuriating, makes me want to return the phone, but I know there are no other options for this kind of phone.
I have no other option than to unlock the bootloader, root, and disable the update apps through adb. At the same time I'm possibly denied warranty. F*cking senseless bull**** that if I prefer to use A11 I can't without problems. Sure the security patches are a bit older, but people make too big of a deal out of them. You aren't instantly getting hacked even with a few year old security patches.
edit:
I have managed to stop the update service permanently in android 11. You need to enable developer options, then connect usb debugging and open an adb shell, which should as for authorization on the phone.
In the shell, type
pm uninstall -k --user 0 com.asus.dm
pm uninstall -k --user 0 com.asus.UpdateLauncher (this might be just the new phone wizard for restoring files etc)
which should return "Success", even without root. I'm not sure if you need to uninstall both of them, or just dm, which is the main update process. In any case, the whole system update section in settings has disappeared. Fine by me, I can install them manually, which is all that I wanted as an option. You can uninstall other packages too, pm listpackages produces a list of them, and you can filter it like "pm listpackages facebook" to show only results with facebook in the name.
Click to expand...
Click to collapse
Thanks for the tip. I was laughing since I had the same exact frustration as you but unfortunately my way of disabling the update was to unlock and relock the bootloader without any changes to avoid a possible brick. Unfortunately I noticed there is a bootloader lock count and it changed to 1 after I did this so my warranty is now voided most likely since they can tell it was unlocked with the counter. Any particular reason why you choose to revert to A11? Cheers
PS
Fortunately I noticed widevine L1 was still intact after unlocking / relocking bootloader so seems to be unaffected by both instances.

maxsterling said:
Thanks for the tip. I was laughing since I had the same exact frustration as you but unfortunately my way of disabling the update was to unlock and relock the bootloader without any changes to avoid a possible brick. Unfortunately I noticed there is a bootloader lock count and it changed to 1 after I did this so my warranty is now voided most likely since they can tell it was unlocked with the counter. Any particular reason why you choose to revert to A11? Cheers
PS
Fortunately I noticed widevine L1 was still intact after unlocking / relocking bootloader so seems to be unaffected by both instances.
Click to expand...
Click to collapse
It seems wanting to root your phones is harder and more inconvenient every year. It should really be a simple process that simply allows you to decide what is running or installed on your phone. I can understand the security implications, but that should be all be dealt with a disclaimer. It is now your responsibility to make sure you don't allow shady programs root access, that's it.
With every new phone I get it's more convoluted, there are less roms available, less people on the forums. Driven to extinction because god damned the manufactures don't care about you after they get your money.
Well anyway, my reason was simply that I really really dislike the UI in 12. Doesn't sit well with me at all, and can't get used to it.
I know I'm making things difficult for me but I refuse to accept that garbage and if I want to run 11 for the time being I should be able to. It's the principle.
I'm going to have to root in the end, but just for now I wanted to test drive the phone without too much work if it's going back.

@eboelens have you received an answer from Asus?
@eboelens @bnsmb @Jgruar when trying to downgrade by method from https://www.asus.com/Content/Android-12-Beta/ I'm getting following error "Command not supported in default implementation" and since it worked for you I have a following questions:
1. You were using Recovery mode or Fastboot mode?
2. Have you enabled USB debugging in Developer options? I did.
3. Have you enabled "OEM unlocking" in Developer options? I tried, but I can''t cause it's visible in the search but not in Developer options (looks like a bug).

sqfaaa said:
@eboelens have you received an answer from Asus?
@eboelens @bnsmb @Jgruar when trying to downgrade by method from https://www.asus.com/Content/Android-12-Beta/ I'm getting following error "Command not supported in default implementation" and since it worked for you I have a following questions:
1. You were using Recovery mode or Fastboot mode?
2. Have you enabled USB debugging in Developer options? I did.
3. Have you enabled "OEM unlocking" in Developer options? I tried, but I can''t cause it's visible in the search but not in Developer options (looks like a bug).
Click to expand...
Click to collapse
Hi
the instructions from the Beta Website will only work if the phone is connected via USB and booted into the bootloader (=fastboot mode).
USB debugging on or off should be irrelevant for this action (I did the reinstallation using this method with and without USB debugging enabled)
AFAIK the phone must be unlocked to reinstall via fastboot commands . Unlocking the phone can/must be done with the Unlock App from ASUS:
https://www.asus-zenfone.com/2015/10/official-asus-zenfone-2-unlock.html
regards
Bernd

@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?

bnsmb said:
AFAIK the phone must be unlocked to reinstall via fastboot commands . Unlocking the phone can/must be done with the Unlock App from ASUS:
https://www.asus-zenfone.com/2015/10/official-asus-zenfone-2-unlock.html
regards
Bernd
Click to expand...
Click to collapse
I haven't unlocked and did the downgrade through fastboot mode with the A11 image file and instructions from ASUS beta program. If they provide the image freely and don't mention anything about voiding the warranty it has to work without unlocking. Just had to make sure my usb connection was stable, had a problem of corruption during install with one cable.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
Make sure your device is visible to the computer (fastboot devices) and is in the fastbootd mode (like in your 1st picture).
You then should be able to excecute the "update_image.bat" file from the package, but I used "update_all.bat". Not exactly sure what the difference is, but someone at some post said to use that. I think the update_image.bat would have worked fine if I had a stable usb connection at the time.
Male sure to disable the update service via the method I posted, or else the Android 11 version will force an install of A12 as soon as it gets a network connection.

sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
HI
see the other reply - it seems to work without unlocking ( I did not test this -- all my phones are unlocked)
regards
Bernd

Thanks.
sqfaaa said:
@bnsmb I have two separated modes - Fastboot and Bootloader (screenshots). Which should be used for update?
Do you suggest there is no way to downgrade from Android 12 to Android 11 without voiding warranty?
Click to expand...
Click to collapse
Neither of those modes is correct. For me mode from the below screenshot worked.
@Jgruar The version that we uploaded via script is a very old Android 11. How did you update from it to the latest Android 11 version since you have uninstalled update service?
Comment for other people, who just bought Zenfone 8 and are struggling like I did: Consider returning the phone. UI of Android 11 is better than 12, but it's still much worse than Android 8 with Samsung add on (Samsung Galaxy S7). Notification list has ridiculously big margins and the opacity is too big (it's hard to see what's in the background). Also view of last application is much worse (one can see name of only one application - the one which is currently open and in Samsung I could see names of last 5 apps). IMHO using pure android is a pain and it's better to buy some phone with pre installed add on or root the Asus but that's voiding the warranty and costs time.

sqfaaa said:
Thanks.
Neither of those modes is correct. For me mode from the below screenshot worked.
@Jgruar The version that we uploaded via script is a very old Android 11. How did you update from it to the latest Android 11 version since you have uninstalled update service?
Comment for other people, who just bought Zenfone 8 and are struggling like I did: Consider returning the phone. UI of Android 11 is better than 12, but it's still much worse than Android 8 with Samsung add on (Samsung Galaxy S7). Notification list has ridiculously big margins and the opacity is too big (it's hard to see what's in the background). Also view of last application is much worse (one can see name of only one application - the one which is currently open and in Samsung I could see names of last 5 apps). IMHO using pure android is a pain and it's better to buy some phone with pre installed add on or root the Asus but that's voiding the warranty and costs time.
Click to expand...
Click to collapse
>>Neither of those modes is correct. For me mode from the below screenshot worked.
That 's the bootloader (with fastboot support)
regards
Bernd

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"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"
}

The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait

I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img

parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse

notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.

parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html

@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download

parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)

notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.

parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?

notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.

notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?

creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission

Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.