Develop Bugs

Update to Android 10 on magisk & Edxposed?

What are the steps to be able to update to Android 10?
Can't seem to find it anywhere. Coming from pie. Thank you.

It was said that Edxposed does not work on android 10. Will eye on this as I need Edxposed badly, currently on Pie.

bush911 said:
It was said that Edxposed does not work on android 10. Will eye on this as I need Edxposed badly, currently on Pie.
Click to expand...
Click to collapse
Edxposed I can remove it. But I know that magisk does work. And that's what I need. Maybe disabling it and updating it will work ?

You can update you Pixel downloading the ota and the factory image from Google repository. Sideload the ota, reboot your phone and wait for the "update optimization" (there is a notification), then you have to patch the boot image (get it from factory) with Magisk Manager. Finally, flash the patched boot image.
In details:
1. Download the full OTA image and the Factory image from Google
2. Keep Magisk and root, copy boot.img from Factory in the Pixel
3. Boot into factory recovery (go in bootloader, choose recovery, keep power and press volume up button).
4. Choose Apply update from ADB
5. From windows: adb sideload fullOTAimage.zip
6. The update will take awhile
7. Reboot and let the update finish in android
8. Load magisk and patch the boot.img, copy patch_boot.img to computer
9. Boot into the bootloader
10. Flash the patched boot image with: fastboot flash boot patch_boot.img
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Edit: you need the Magisk Manager canary version, see this post: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359

Simone_ASR said:
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Click to expand...
Click to collapse
According to what I've read .019 is for those who were already on the betas and .020 is for those upgrading from Pie.

Simone_ASR said:
You can update you Pixel downloading the ota and the factory image from Google repository. Sideload the ota, reboot your phone and wait for the "update optimization" (there is a notification), then you have to patch the boot image (get it from factory) with Magisk Manager. Finally, flash the patched boot image.
In details:
1. Download the full OTA image and the Factory image from Google
2. Keep Magisk and root, copy boot.img from Factory in the Pixel
3. Boot into factory recovery (go in bootloader, choose recovery, keep power and press volume up button).
4. Choose Apply update from ADB
5. From windows: adb sideload fullOTAimage.zip
6. The update will take awhile
7. Reboot and let the update finish in android
8. Load magisk and patch the boot.img, copy patch_boot.img to computer
9. Boot into the bootloader
10. Flash the patched boot image with: fastboot flash boot patch_boot.img
BUT in the Google repository there are 2 version of ota/factory images (.019 e .020). I don't know the difference.
Edit: you need the Magisk Manager canary version, see this post: https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
Click to expand...
Click to collapse
Awesome man, thank you !

i updated from pie and patched the boot.image so now i have root. i was trying to edit the build.prop for hotspot tethering, the old net.tethering.noprovisioning=true but it wont allow me to edit and save the changes to the build.prop, root explorer is not getting read write permissions or something, root explorer does have super user [permission though. can anyone shed some light on this please

This seems kind of dangerous. It would be great to hear some more people's experience.

Has anyone confirmed whether or not Xposed works on Android 10? Riru Core says that it's compatible with Android 10. As long as Riru core works then Xposed should work. But I would like some confirmation so that I can update.

Ariel_PR said:
Has anyone confirmed whether or not Xposed works on Android 10? Riru Core says that it's compatible with Android 10. As long as Riru core works then Xposed should work. But I would like some confirmation so that I can update.
Click to expand...
Click to collapse
I haven't yet. I've been busy with work. As soon as I get a moment I'll do the update and confirm if everything is working right.

GunToYoMouth123 said:
I haven't yet. I've been busy with work. As soon as I get a moment I'll do the update and confirm if everything is working right.
Click to expand...
Click to collapse
Awesome, let us know!

Ariel_PR said:
Awesome, let us know!
Click to expand...
Click to collapse
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.

GunToYoMouth123 said:
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
Click to expand...
Click to collapse
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!

GunToYoMouth123 said:
I finally updated through OTA while on magisk and disabled it to enable it again with a patch. But with steps. I'll upload it soon for people coming from Android 9 (rooted in magisk) and OTA updating to Q and rooting back with magisk. Xposed will come in next.
Click to expand...
Click to collapse
Thanks for the update!

ngelee said:
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
Click to expand...
Click to collapse
Sorry it's taking long. I'm gonna post it here now in a few.

Okay, I work at a fulltime job so please bear with me and sorry for my late responses. And acknowledge that I am not responsible for anything that happens to your device. This step-by-step guide was done on an unlocked Google Pixel 3 XL unlocked bought from the Google Play store. I haven't tested it out on other versions of Pixel 3's or any other phone that isn't the Pixel 3 models since I do not own them, so keep that in mind. My situation was to find out how to update my ALREADY ROOTED/MAGISK version of Android 9 PIE through OTA. Upon checking or looking around I couldn't find any tutorials that are easy for me so with all the info I gathered I decided to wing it and compile steps from a lot of sites,risk it all and used my knowledge to put together this guide. In hopes, this helps everyone else! anyways here we go...
First, PLEASE make sure if you have Edxposed or any other modules or anything that is similiar, uninstall it or remove it. (Applications or mods from magisk are fine, I did this while I had a few mods from magisk, like viperfx, youtube vanice etc..)
1. Disable Automatic system updates in developer options, so it won't install OTAs without your acknowledgment.
2. When an OTA is available, first go to Magisk Manager → Uninstall → Restore Images. Do not reboot or you will have Magisk uninstalled. This will restore your boot back to 100% untouched stock images in order to pass pre-OTA block verifications.
3. After restoring the stock boot image, apply the OTA update as you normally would (Settings → System → System Update).
Wait for the installation to be fully done then press the "Restart now"
Wait for the phone to reboot and let it sit for a few minutes. 10-15 minutes give or take.
Don't panic, let it do its thing.
Once you see the "G" with the loading under it, you should be fine.
let it boot up.
4. Now download the factory zip
download 10.0.0 (QP1A.190711.020, Sep 2019)
5. Once downloaded, open the zip using any zip/rar program. (I HIGHLY recommend WinRar) within THAT zip folder extract the image-crosshatch-qp1a.190711.020.zip somewhere on your desktop.
6. Now then open THAT zip file and from it, extract the boot.img file onto your desktop and move it into your Pixel 3 XL's download folder. (I did it this way, so I recommend it)
7. Now uninstall your old magisk manager and install the latest Magisk Manager (app-release.apk)from HERE
8. Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file you extracted from the latest factory image that you placed in your Pixel 3 XL.
9. Magisk Manager will patch the boot.img and store the patched boot.img in the download folder as "magisk_patched.img"
10. Copy the magisk_patched.img file to your computer's Platform-tools folder(The one you use to adb push files in etc.) or the folder that has fastboot.exe(your ADB folder should have the fastboot.exe in it normally lol ) in it.
11. Connect the phone to the Computer with USB type- c cord.
12. Open your platform-tools folder if you haven't, and on the search bar type in "cmd" and tap enter on your keyboard.
(the cmd promt should open already in your location)
13. Now boot your Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
14. Once your phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
15. Once it's done then type the command : fastboot reboot
16. Google logo should show,but don't panic give it a few.
Open Magisk and check if its rooted on the manager
And congrats ! you have a Magisk root on Android Q ! :highfive:
Please let me know if it worked for you and let me know if you need any help! :fingers-crossed:

ngelee said:
I'm exactly the same situation as you, currently on Android 9 rooted with Magisk, and receiving 10 OTA notification, but I don't know how to move foward. Looking for your guide, thanks dude!
Click to expand...
Click to collapse
Just posted it above ! please let me know if it works!

does Dolby work on pixel 3 xl? can anyone confirm?

I installed the OTA update the other day, but did anyone figure out if Edxposed Is working on Android 10?

This also works on Pixel 2 XL going from Android 9.0 July image with xposed 19.3.
Here's a simpler guide:
1. Go to Magisk Manager → Uninstall → Restore Images
2. Apply the OTA update and reboot
3. Download factory ZIP for 10.0 (In this case for taimen: Pixel 2 XL Android 10.0 Image)
4. From ZIP extract "taimen-qp1a.190711.020/image-taimen-qp1a.190711.020.zip/boot.img" and put it somewhere in the phone
5. Update Magisk with this version: Link
6. Open Magisk Manager and press: Install -> Install -> Patch a File and then select boot.img extracted before
7. Copy magisk_patched.img that Magisk has made to PC
8. Reboot phone to bootloader: adb reboot bootloader
9. Flash patched boot image: fastboot flash boot magisk_patched.img
10. Reboot phone: fastboot reboot
TL;DR:
Disable Magisk, update 10.0 OTA, upgrade Magisk, patch factory boot image with Magisk and flash boot image.
btw: I recommend Easy 7zip: http://www.e7z.org/ for handling the ZIP in a ZIP

rooting ( after unlocking bootloader)

So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.

Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?

testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed

pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?

Sorry, no idea, i found the provided link via google,

testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/

zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?

No fastbootd?
One Hyper needs fastbootd in order to flash boot and root

mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.

pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery

mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?

https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know

pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.

Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.

CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super

Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.

Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.

hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.

hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.

(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides

Hi all,
Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself
Please read the process before committing to proceeding, so you know what's required and what you should and shouldn't use!
Stock and patched images are UK/ EU but the guides are universal and could be used on multiple devices.
NOTE:
For these guides the versions used are:
Stable, Canary or BETA depending on firmware, simply change the channel in Magisk settings then select install / update:
11.0.1.1
Magisk Manager - Magisk (Canary) version: 1469b82a (21101)
11.0.2.2
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
11.0.3.3
Boot img patched using Magisk beta 21.4 (21400)
11.0.4.4 (DO NOT UPDATE TO 22.0 YOU WILL BOOTLOOP!
Boot Img patched using Magisk beta
21.4 (21400)
11.0.5.5
Boot img patched using Magisk Stable 22.0 (22000) (18)
11.0.6.6
Boot img patched using Magisk Stable 22.1 (22100)
11.0.7.7
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.8.8
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.9.9
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.10.10
Boot.img patched using Magisk Stable 23.0 (23000) (21)
11.0.11.11
Boot.img patched using Magisk 24
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Thanks @tfae
12 11.C.15 EU. Thanks @tfae
1st
Extracting a boot.img using Payload dumper
Pre-requisites
A device with a working version of magisk manager installed, simply change the channel to the version outlined in the list above relevant to your firmware then select install / update:
A Windows 10 computer / laptop
A full update downloaded firmware zip for your model (recommend oxygen updater)
Payload dumper program for Windows.
Process
On your computer
1. Download and copy the PAYLOAD DUMPER folder to your desktop, there will be one folder with 2 files and 2 folders inside.
Download from here: https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
2. Download the firmware of your choice and open it using Winrar or a similar zip program, extract the file called payload.bin to the folder within the payload folder called payload_input.
3. Run the program payload_dumper.exe, a Command prompt will open to show extraction progress (this will extract a bunch of files to the payload_output folder) allow it to completely finish (the CMD window will close automatically)
4. One of the files will be called boot.img, this is the file we'll be patching, copy this to your phone, root of storage which is called /sdcard.
On your phone
5. Open up Magisk and click Install / Update, if you don't see update then change channel, so this by changing the channel in magisk settings, it'll then show the install/ update buttons.
6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" (which will be in the Downloads folder)
You now have a patched boot.img ready to flash to either slot with fastboot or boot via fastboot, would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash then your phone may bootloop.
NOTE** Some people have noticed that an already patched boot.img when flashed can fail and cause a boot loop when flashed,so if you have downloaded a magisk_patched img from somewhere else then you WILL need to re-patch it on your own device preferably using the afore mentioned magisk manager based on what firmware it's from.
If you intend to follow the guide below with your own patched img then you shouldn't need to patch twice but it won't hurt if you do.
2nd
Upgrading from rooted Android 10 to rooted Android 11
Pre-requisites
A rooted device running Android 10
Canary magisk manager or beta version that works:
Windows 10 computer / laptop
Process
On your phone
1. Disable all Magisk mods
2. Download the Android 11 firmware using Oxygen updater DO NOT INSTALL AUTOMATICALLY, WE NEED TO INSTALL MANUALLY!!!
3. Once downloaded; open settings / system / system updates
4. Click the settings cog and click 'install from local storage'
5. Locate the firmware you downloaded, it's in the root of storage.
6. Click install and allow it to finish, DO NOT CLICK THE REBOOT BUTTON YET!
7. Open Magisk. manager and click "Install / Update"
8. Click "Install to Inactive slot (After OTA) (Once complete, click reboot)
As this is a new base the first boot may take a little longer.
Your phone will now boot with Android 11.0.0 and will have retained root, all your apps will remain as you left them.
Be careful what mods you re-enable as they may not be 11 compatible.
3rd
Update from 11 stable to 11+ stable whilst retaining root
Guide
1. Download the relevant firmware for your device via oxygen updater
2. Open Magisk and remove all the modules you have installed, then reboot
**NOTE- At this point I tend to copy out the whole firmware to my computer, incase I need it in the future, the boot img and patched boot img are at the foot of this guide, I'll always upload the latest firmware as soon as it comes out for the UK/EU model
3. Open up settings / system / system updates , click the cog and select "Local Upgrade" the file should be listed on screen, if not then move the file to the root of your phones storage.
4. Click install and allow it to go through the process
**NOTE- DO NOT REBOOT AT THIS POINT YOU WILL LOSE THE ABILITY TO PATCH ON THE FLY, SIMPLY BACK OUT OF THE SCREEN WHICH SAYS "INSTALLATION COMPLETED. RESTART TO EXPERIENCE NEW FEATURES"
5. Open up magisk and click install (you may see two install buttons, top one is magisk and the bottom is magisk manager, we need the top one)
6. You'll be faced with a screen that has several options, you want to select "Install to Inactive slot (After OTA)" then select "LET'S GO" once complete click reboot.
7. Once your phones booted back up your system / files should all remain as they were and you should have root access.
You can now install all your modules again so long as they're compatible with the firmware you've just updated to.
4th
Rooting using fastboot commands
Method 1
Booting the patched image
1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - The above suggested downloads are for the EU / UK variant- if you have another model / firmware please use that instead, If you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager to avoid a bootloop, if you still get a bootloop it's best to obtain one yourself using the guide at the top of this post.
2. Reboot your phone to fastboot
and connect to your computer.
3. Boot the magisk patched img
fastboot boot magisk_patched (or name of your patched boot img)
Your phone should now boot automatically, you should now be rooted but we need to make this permanent, if you were to reboot you would lose root.
4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.
5. Select Direct install (recommended) then click ok.
6. Allow magisk to permanently root your device then click reboot.
You should now boot and remain rooted.
Method 2
Flashing to both slots
1. Obtain a patched boot img for your device variant or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer
**NOTE - Again the above suggested downloads are for the EU/ UK variant- if you have another model / firmware please use that instead, if you did not obtain the boot.img from a firmware and patch it yourself, you will need to patch it again in magisk manager, to avoid a bootloop
2. Reboot your phone to fastboot and connect to your computer.
Command: adb reboot bootloader
3. Open a command prompt on your computer and navigate to your ADB/fastboot folder.
4. Type the following.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter
6. Your phone should now boot, open magisk and verify you're rooted.
Troubleshooting
If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation enter this command via ADB.
adb wait-for-device shell magisk --remove-modules
3. Allow to boot, modules will be removed and root should then be active.
Thanks @nycdiplomat for this tip.
If there is no magisk install / update buttons.
1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions
2. Make sure that the update channel is on canary, then force close magisk and then re-open
3. If it still doesn't work then update magisk using canary
4. Last method to check would be to change to the beta channel in magisk settings, then install it.
Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.
Window's version
Windows 7 will not work with fastboot, please use Windows 10
USB
Use USB 2.0 not 3.0 or 3.1
ADB
These are the files i use for ADB (1st in the below list) tested these on fresh installs of windows on several windows machines, all win 10
Place them into the root of C so it reads C:\ADB much easier to navigate to that way.
Files:
ADB Files for Windows 10:
7.69 MB folder on MEGA
5 files
mega.nz
Payload dumper program for Windows-
https://mega.nz/folder/vU00FZDa#PIEfjl5w5wonyNAwHW3FBQ
Full OTA - Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 FIRMWARE -
https://mega.nz/file/TZl2WIBR#wSP3_bkoWl1FZZX7zfhobo3cYIAhWvDQ9f0ot3_qNFo
Oxygen OS 11.0.0 EU 11.IN11BA - IN2023 Patched boot.img -
https://mega.nz/folder/TE8yWbIL#a6woc43pCpTX_URX5dWr1A
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/6d1mVYgJ#tE90TcwqTLp71SgZX9Xxhg
Oxygen OS 11.0.1.1 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/CINjAQCZ#Sns
sRugbc0sELF0ajSAEXg
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Stock boot.img -
https://mega.nz/folder/PFsmFDKY#01sGzxzVpiAELjcT0LuZmQ
Oxygen OS 11.0.2.2 - EU IN11BA -IN2023 Patched boot.img -
https://mega.nz/folder/vJs0FRBD#SisIJ5FrmkJ3ej1RB6Yz3Q
Boot img patched using Magisk (Canary) version: 1469b82a (21101)
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.3.3 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.4.4 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.5.5 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Stock boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.6.6 - EU IN11BA -IN2023 Patched boot.img -
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.7.7 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.8.8 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.9.9 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Stock boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.10.10 - EU IN11BA -IN2023 Patched boot.img
96 MB folder on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Stock boot.img
16.98 MB file on MEGA
mega.nz
Oxygen OS 11.0.11.11 EU IN11BA - IN2023
Patched boot.img
https://forum.xda-developers.com/attachments/11-0-11-11-europe-patched-24303-zip.5566283/
Android 12 11.C.15 - Stock and patched images from. @tfae
File on MEGA
mega.nz

Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?

dblane82222 said:
Hi bro thank you so much for this. I don't understand what to do next now. My phone is already updated to 11 and I want to root it and install masigk etc how do I do that? Its already on version 11 I installed normal version 11 stock rom.
So I was on version 10 before and it was rooted and I had magisk I updated and lost root access and magisk. So now I'm on version 11. I have downloaded your patched boot image but what do I do next could you please hell me?
Click to expand...
Click to collapse
Ah so you're on 11 stock? Have you unlocked the bootloader?
I have a guide based on android 10 here for unlocking the bootloader, lot of similarities.
https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-unlocking-bootloader-rooting-t4151823
Please don't dive in without reading first.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section.
Please let me know before you start.
PS: thanks for not quoting the entire post

Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.

dblane82222 said:
Bootloader is already unlocked.
Yes I'm on stock 11.
If you've already unlocked the bootloader then you can simply use the magisk_patched img on step 1 of the Rooting section. (Where is this section?)
I'm about to start the process now.
Click to expand...
Click to collapse
Yep that should be fine. I think you can also do this from magisk under direct install but I've not tried before and I think it's possible that this may require twrp. So yea go with the root guide.
Should be ok.

Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.

dblane82222 said:
Could you give me the link to the Rooting section you have referred too so I know what to do please?
And magisk won't install for me won't let me. So I can't do that. I even tried installing twrp but it won't work.
Click to expand...
Click to collapse
No don't install twrp it doesn't work..
Rooting should be a case of installing the magisk_patched IMG to the active slot, you can do both..
The root process is at the bottom of the link i sent you mate.

This is the section on root.
You'll need the magisk_patched file from the OP
Rooting
1. On your computer
Get the magisk_patched file
2. Copy "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. Type the following into the window
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.

So long as you have magisk manager installed that's all you need to do besides that guide

Let me know how u get on

dladz said:
Let me know how u get on
Click to expand...
Click to collapse
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
dladz said:
Let me know how u get on
Click to expand...
Click to collapse
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?

dblane82222 said:
so every time i do this on my cmd it says unknown partition 'magisk_patched.img'
error cant determine image file name for 'magisk_patched.img'
sorry if i seems stupid.
---------- Post added at 09:44 PM ---------- Previous post was at 09:34 PM ----------
okay so its worked now. i managed to flash it but once i restarted the phone its stuck in a loop keeps going to bootloader menu what do i do now?
---------- Post added at 09:57 PM ---------- Previous post was at 09:44 PM ----------
okay so now its gone to crashdump mode?
Click to expand...
Click to collapse
? What did you flash?

dladz said:
? What did you flash?
Click to expand...
Click to collapse
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?

So you needed the magisk_patched from the beginning of this thread (the OP)
Then boot to fastboot mode and flash to both slots using ADB / fastboot from Windows..
Then fastboot reboot.
That's literally it mate..that's all I did.
If you're in crashdump mode then i have no idea what you flashed or how you flashed it..shouldn't have done that.
You're on the EU/UK model right?
No reason why it wouldn't have worked.

dblane82222 said:
the file you gave .. the bootimage please help me because im screwed now i dont have a working phone...
so basicaly before i installed what u gave me and it was just stuck on the bootloader screen it wouldnt go off it. at all
so i installed twrp and then it jut crashed mode... please please help me?
Click to expand...
Click to collapse
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.

If you add steps besides what you're meant to do I can't help you pal.

dladz said:
Ok so do not install twrp it does not work on 11.
Calm down a moment you haven't broken anything so don't worry..
Tell me what screen you're on please. Also can you boot to fastboot mode? Or even bootloader?
Worse case scenario you will have EDL mode and the MSM tool which can get you back up and running..
Do not attempt to install twrp as it will not work and will cause more harm than good.
Click to expand...
Click to collapse
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
Click to expand...
Click to collapse
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??

dblane82222 said:
yes i think its edl mode. i cant access any mode at all. nothing is accesable. can you please give me the link for the msm tool and what i need to do please thank you ? i really do apprecite all the help.
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
do you have anything that i can speal to u on thats more instant such as whts app or discord or icq or anything ??
Click to expand...
Click to collapse
I'm actually in bed at the moment pal.
Here's the MSM thread
https://forum.xda-developers.com/on...-tool-to-restore-device-t4084953/post82327013
I think it may have been trying to install twrp.
Before you go down the MSM route.
Try to power off the device without the cable connected..press and hold power and vol down..until the phone turns on.
Should go to bootloader.
If not try it the above with the cable connected to your phone and computer.
If you still can't get in then yes it's MSM time..
Personally have never used it but it's an active thread so always people in there and 10000% someone will have been in the same boat as you.
Not sure what happened with your situation tbh..I tested all the files again myself and they're all legit. I used them before I spoke with you and again just now.
Please though, try not to worry, you'd have to do something mental to break a OnePlus.
You'll be fine.
Let me know how your get on and I'll answer when I can..quite tired at moment.

yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.

dblane82222 said:
yeah tried all of that still nothing. going to try the msm solution see what that does its downloading as we speak. but even before the twrp i done what u said and it was stuck on bootloader any idea why that would be ? i can understand it happened becuase i installed twrp and that casued the phone ot enter edl mode. but prior to it it was stuck on bootloader. following just the steps u had said ? once i have got he phone back up and running should i try your mehtod again and see what happens again ?
no problem really apprecite all the help you have given me thank so much.
Click to expand...
Click to collapse
Nah no worries man, just trying to work out what happened..
Once you're back up, maybe ask another thread just to confirm as I'm second guessing myself now..
Don't want you to end up like this again..
See what the chap says in the MSM thread too, his telegram username is in his profile.
To confirm you do have a UK phone right? IN2023 BA
Could have just been the flash didn't go through. You did do a flash and not boot right? To get out of that. Could have just flashed the stock boot.img and that would have saved you

How To Guide [GUIDE] Magisk on LineageOS

I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!

I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.

The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)

sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!

ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed

Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!

ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything

Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.

Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?

Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful

[deleted]

johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.

dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working

[How-To] Root Android 12L/11 - Bootable patched_magisk & Instructions on DIY

Hello Friends,
Android 12L Section
Android 12L has finally been released for Duo 1 and the update makes this device what it should have been from the beginning (again...). But root is always nice.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 12L stock boot img patched with magisk 25.2, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you want to go the payload dumper yourself and make your own boot.img, see below.
Install Magisk Manager 25.2 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
Android 11 Section
Android 11 has finally been released for Duo 1 and the update makes this device what it should have been from the beginning. But root is always nice.
Luckily Android 11 has made rooting a bit easier as well.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 11 stock boot img patched with magisk 23, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you want to go the payload dumper yourself and make your own boot.img, see below.
Install Magisk Manager 23 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
Extraction of payload.bin from OTA.
If you want to extract the boot.img yourself and patch it yourself, download the payload.bin extractor from here. Acquire the OTA either via recovery images or capturing the OTA URL during an update (link).
Use the payload dumper to get the boot.img, install Magisk on your device and transfer the boot.img to it to patch that stock boot.img using Magisk. After that, you will have your own patched boot.img.
Proceed with step number 4.
A huge thank you to @NTchrist and @Perseu5 for pathfinding this all and their amazing guides, give those guys some thanks and kudos please!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Android 11 OTA Link & zip File, .img Files (Unlocked)
Hey friends! These are only for the unlocked Surface Duo. I am sorry At&t users. Here is the OTA link for Android 11: https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip Link to the OTA.zip...
forum.xda-developers.com

Personally I've always been hesitant to provide pre-patched images. People just spam your inbox if it's not up to date five minutes after release. Also, people don't learn about what they're actually doing. I'd never be a developer today if I were just handed all the things I wanted to have and I suspect that'd be true of many of the best developers on this forum. That said, If there's a demand I'll make an updated full guide. Let me know in the comments on my original thread if you guys want that.

NTchrist said:
Personally I've always been hesitant to provide pre-patched images. People just spam your inbox if it's not up to date five minutes after release. Also, people don't learn about what they're actually doing. I'd never be a developer today if I were just handed all the things I wanted to have and I suspect that'd be true of many of the best developers on this forum. That said, If there's a demand I'll make an updated full guide. Let me know in the comments on my original thread if you guys want that.
Click to expand...
Click to collapse
I fully agree with you. I did magisk_patching for old nexus's, oneplus 6t, and a couple of the pixels and I actually didn't get that much spam. But go a ton of spam for system UI tweaks, twrp and such how-tos I posted.
The primary reason I provided a pre-patched one here is because I had a ton of issues getting payload dumper to work on my fresh windows 11. And this was just easier.

Finally a much more streamlined process, and it works perfectly. That back & forth patching each month was getting too hairy. Not too mention how much faster this device is now which has me into it all over again. This has all been worth it so far in my opinion based off of usage today. no random app crashes anymore , much better UI and control panel across the board, Hell it even sounds louder. I'm really happy with this update and root so far.

OK so I've got the AT&T variant (that I use as a secondary device with no SIM) that I've successfully flashed Android 11 onto using the filiphsandstorm script. I haven't reset the phone. Android 11 works fine so far like this. Unfortunately though I'm hanging on the boot screen when I fastboot the patched boot image. If I patch the boot image with an earlier version of Magisk it double boots and returns to the stock image. If I patch the boot image with the latest version of Magisk I get the boot hang. Obviously this could just be AT&T incompatibility but does anyone have any ideas? Has anyone with an AT&T device successfully rooted on Android 11?

-

delfuhd said:
OK so I've got the AT&T variant (that I use as a secondary device with no SIM) that I've successfully flashed Android 11 onto using the filiphsandstorm script. I haven't reset the phone. Android 11 works fine so far like this. Unfortunately though I'm hanging on the boot screen when I fastboot the patched boot image. If I patch the boot image with an earlier version of Magisk it double boots and returns to the stock image. If I patch the boot image with the latest version of Magisk I get the boot hang. Obviously this could just be AT&T incompatibility but does anyone have any ideas? Has anyone with an AT&T device successfully rooted on Android 11?
Click to expand...
Click to collapse
Dumb question on my part but are you booting the patched image or trying to flash it in bootloader?
Just making sure we are on the same page.

eqbirvin said:
Dumb question on my part but are you booting the patched image or trying to flash it in bootloader?
Click to expand...
Click to collapse
No problem. Not flashing, just trying to boot. From
adb reboot bootloader
I'm executing:
fastboot boot patchedboot.img
Trying to flash to the boot partition just gives me an error anyway.
Also, just to be clear, I've tried it with your patched image as well as a boot image that I extracted from payload.bin. Both same results.
EDIT: OK I bit the bullet and did a factory reset through recovery. I wanted to avoid this as it's a pain setting the device up again. However, this solved the problem. I was able to complete the steps above and successfully gained root permanently. Thank you for your help!

eqbirvin said:
Hello Friends,
Android 11 has finally been released for Duo 1 and the update makes this device what it should have been from the beginning. But root is always nice.
Luckily Android 11 has made rooting a bit easier as well.
Pre-requisites
Unlocked bootloader
adb/fastboot set up properly
understanding what adb/fastboot and basic commands using these tools
How to open a CMD/Powershell in a given location
Windows 10/11 (you can make this work for MacOS/Linux but that isn't what this guide is based on)
I do not know if this will for at&t version or not. I do not have the at&t model so I cannot verify.
Download this patched boot.img (link)
This is simply the Android 11 stock boot img patched with magisk 23, I just did the hard work for you because it is a pain in the butt to get payload unloader to work.
If you do not want to use my pre-patched boot that is understandable but at this time I am not providing a how-to on extracting the boot from the OTA. You can use the pre-existing root guide by @NTchrist and @Perseu5 to at least extract the stock boot and then patch it yourself, just make sure you use Magisk 23.
Install Magisk Manager 23 which is the current stable/beta build (link)
either via adb or manually
Open Magisk Manager Once after installation and before moving to the next step
Boot into bootloader
either from cmd adb while the device is booted via adb command
Code:
adb reboot-bootloader
or from issuing a reboot from the power menu and holding volume down while rebooting
or from power off, hold the power button and volume down for 3 seconds
Boot the patched boot.img you downloaded by opening a CMD in the location of the downloaded patched boot and issuing this command
Code:
fastboot boot patched.156.boot.img
The device will boot into Android system
Open Magisk Manager > Click "Install" > "Direct Install"
Maigsk will install and reboot
Your device is rooted
If there is enough demand, I will do a walk thought on extracting the stock boot and patching it because I understand some don't like to trust downloaded boots.
A huge thank you to @NTchrist and @Perseu5 for pathfinding this all and their amazing guides, give those guys some thanks and kudos please!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Android 11 OTA Link & zip File, .img Files (Unlocked)
Hey friends! These are only for the unlocked Surface Duo. I am sorry At&t users. Here is the OTA link for Android 11: https://android.googleapis.com/packages/ota-api/package/a9bfdee15f2137f020fffded98b4bdee5d8bec8e.zip Link to the OTA.zip...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much for providing the patched boot and for the guide (although in my case I know the steps). You save me a lot of work. Excellent.

I got the AT&T version. I just booted the patched image from OP and it works. (i was having trouble patching the AT&T image. probably was my fault because i was using magisk v.24.1 rather than v.23)

Any one get a system update notification?

Quick question:
Can we use the generic boot image to get TWRP working on the Surface Duo?

eqbirvin said:
Any one get a system update notification?
Click to expand...
Click to collapse
Yes , a 565MB file !

How do we update and keep root?

diejuse said:
How do we update and keep root?
Click to expand...
Click to collapse
1st post ( thanks to NTchrist )
==== UPDATE WHILE ROOTED ==== Section
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com

pvillasuso said:
1st post ( thanks to NTchrist )
==== UPDATE WHILE ROOTED ==== Section
Root guide (updated)
==== READ THIS POST BEFORE ROOTING ==== https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/ (ORIGINAL GUIDE BELOW) Since the last guy hasn't been updating his op, I figured I'd start a fresh thread...
forum.xda-developers.com
Click to expand...
Click to collapse
This is actually no longer necessary on A11 in most cases. You can do the magisk "install to inactive slot" workflow here to ota and retain root
tl/dr:
magisk > restore images (do not reboot)
do ota (do not reboot)
magisk > install to inactive slot
reboot
done

NTchrist said:
This is actually no longer necessary on A11 in most cases. You can do the magisk "install to inactive slot" workflow here to ota and retain root
tl/dr:
magisk > restore images (do not reboot)
do ota (do not reboot)
magisk > install to inactive slot
reboot
done
Click to expand...
Click to collapse
Thanks, just did it with today's latest 2022.113.26 OTA !
Super easy

pvillasuso said:
Thanks, just did it with today's latest 2022.113.26 OTA !
Super easy
Click to expand...
Click to collapse
Updated to the latest , 2022.115.10 OTA

pvillasuso said:
Updated to the latest , 2022.115.10 OTA
Click to expand...
Click to collapse
Updated to the latest , 2022.215.137 OTA

pvillasuso said:
Updated to the latest , 2022.215.137 OTA
Click to expand...
Click to collapse
Same process as before?