Develop Bugs

December update not rootable?

Hi Y'all,
I just dirty flashed the December update, and then attempted to patch boot.img with magisk and flash that with fastboot, same as I've always been doing on Android 10 without fail. However, this time, it starts to boot, I get ADB, it bootloops twice, then goes back to fastboot with an error saying something to the effect of "no available slots"
I re-patched and it came out with the same md5sum of b1d09aa00e3376f3d4ceba4e97b99eae
I was able to get an adb logcat on both attempted boots, they're too large for any paste service so I threw them on a VPC I have
http://irc.killingkittens.net/logcat1.txt
http://irc.killingkittens.net/logcat2.txt
Magisk Canary, manager version 7.4.1-72edbfc4 (260)
Magisk 20.2-72edbfc4 (20108)
Happy to provide any other info that would help.

Worked fine for me.

I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file

phoe zay said:
I update ota by magisk method and work fine.
http://www.mediafire.com/view/k1r6pzneqwcrp4d/Screenshot_20191203-112633.png/file
Click to expand...
Click to collapse
I see that you're on older versions of both Magisk and Manager than I am. Which update channel are you on?

OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.

Works as normal for me.
I always sideload ota and then patch the boot.img from the full download

sliding_billy said:
OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.
Click to expand...
Click to collapse
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!

swieder711 said:
Are you saying that if I update by having the phone in fastboot mode and running flash-all with -w removed than the phone update fails or gets wiped?
I had that experience last month where my phone was wiped even with -w removed! I would like to avoid getting wiped this time!
Click to expand...
Click to collapse
Thankfully, no. I can't speak for any possible error when doing a flash-all (without -w), but the one that fails with the "sending product FAILED (Write to device failed (Invalid argument))" just shows a press any failure in command prompt and press any key to continue. The phone remains in fastbootd where you can use the volume keys and power to select recovery he use the keys again to select "sideload OTA from ADB" and while it is waiting use the "adb sideload [OTA path/filename].zip" command in commander and it acts as if you used the sideload in the first place changing slots, not erasing any data/settings/apps. I am not 100% sure yet, but I tend to think that the script is now acting differently if used without the -w but started without flashing stock .boot to both slots to unroot and remove any non-stock kernel. I have been doing it that way for 3+ years now on a Pixal, Piixel XL, Pixel 3 and Pixel 3 XL without issue until last month. I wanted to try it one more time this month after messing with my path and such, but I guess I will have to wait until January to try again. The 3 XL is on Havoc, so I can't test that one. My proposed instructions before doing it are 1)disable all modules, 2)reboot to system, 3)go to BL, 4)Flash previous stock .boot to both slots, 5)boot to system, 6)go to BL, 7)flash-all (without -w), 8)cross your fingers.

Can someone give me the md5 of the patched boot.img from this release? Or, upload a working patched file?
The specific error I got was "no valid slot to boot"
I tried flashing each slot manually, same error. I see that happened a year ago and it related to magisk versions: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712/page2

I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img

I have the same problem with the same version of Magisk as you and the -w flag in flash-all didn't make a difference.

nomisunrider said:
I always update via flash-all with -w option removed.
Did the same this time and no issues.
Not sure how to attach the patched boot as it is too large.
Here is the patched md5:
02536812e6b2e09e4707f98d65e7918f magisk_patched.img
Click to expand...
Click to collapse
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?

DOMF said:
Completely different md5 as me when I try either magisk canary or stable! Can you please upload it to something like https://mega.co.nz/ and generate a share link?
Click to expand...
Click to collapse
Well, crap, I was able to get the same md5sum by flashing Canary-non-debug, but I still get the crash back to the bootloader with the error "no valid slot to boot"
Anyone have any suggestions before I try a full wipe?

I'm rooted in December but my network connectivity took a serious downgrade with it.

I'm having the same problem on Pixel 3, it just can't boot after patching the boot.img :\

sliding_billy said:
Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product,...
Click to expand...
Click to collapse
I found the reason:
Bad cable -> Solution: try another cable,
bad USB port -> Solution: try another port or computer,
or old SDK version -> download and update.
Definitely one of these.
Anyway, I also have the problem with bootloop after patch.

Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)

v12xke said:
Worked just fine here flashing full image (-w) and then applying the patched boot.img from Magisk (20108). Not sure what is going on, but make sure you are on the latest binaries 29.0.5 (October 2019)
Click to expand...
Click to collapse
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!)
I'm on 29.0.5.1
Code:
~ fastboot --version
fastboot version 29.0.5-1
Installed as /usr/bin/fastboot
but now that you mention it, I've run into an issue with Arch's implementation of android-tools in the past. Will try from my mac tomorrow.

DOMF said:
Ugh I don't wanna wipe, especially without having taken a TiBu backup first (I know, bad me, it's just worked every time flawlessly so far!) I'm on 29.0.5.1
Click to expand...
Click to collapse
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:

v12xke said:
You wouldn't need to wipe... just fastboot flash the original (stock) boot.img and then get it sorted once back into System. Best of luck :good:
Click to expand...
Click to collapse
When I got into the bootloop after applying the Magisk modified boot.img, flashing stock boot.img didn't fix it for me. I had to flash-all again to get it to boot.
I have the latest Canary Magisk Manager 7.4.1-72edbfc4(260) installed, but I also tried the stable channel and still had the same problem. I noticed that my phone faile SafetyNet over ctsProfile: false. Could my problems be related to not un-hiding Magisk? And thinking back, I may not have rebooted after disabling my modules before I started flashing.

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

Fairphone 4 - Root

Here's a quick guide for rooting your Fairphone 4.
DISCLAIMER
I'm not the author of this method, merely sharing the informations that can be found on fairphone community forums.
All credit goes to hirnsushi from fairphone community forum.
I will not be held responsible for any damage caused by this operation, flashing your device always implies a risk of manufacturing your very own plastic brick.
PREREQUISITES
- Unlocked bootloader
- Computer with adb & fastboot
- Magisk app installed on your device
- FP4's official stock boot.img
HOW TO ROOT
1. Copy the boot.img file on your device's internal memory
2. Patch the boot.img file using Magisk -> Installation -> Patch a file
3. Transfer the patched boot.img back to your computer
4. Reboot to fastboot: Power + vol up from off device OR adb reboot bootloader
5. Boot from the patched img by running: fastboot boot patched_boot.img where patched_boot.img is actually replaced with the path and name of your patched file
DO NOT FLASH THE PATCHED IMG. BOOT ONLY.
6. Your device will take much much more time to boot than usual, be patient.
7. Once booted, open Magisk, run a direct Install and reboot.
You are now rooted.
This will break your ability to use Google Pay. Though a workaround is described below.
[OPTIONAL]- PASS SAFETYNET AND GPAY CERTIFICATION
1. Download and enable the following Magisk mod:
- Riru module
- Riru’s universal SafetyNet’s fix 2.1.2
- SQLLite for ARM aarch64 devices
- GPay SQLLite Fix 2.5
2. Enable Magisk hide and hide Magisk from the following packages:
- Google Play Store
- Google Pay
- Google Play Services
3. Now the part that is very important to follow otherwise it will not work :
- Put your phone in Airplane mode
- Clear all data from:
Google Play
Google Pay
Google Play Service: remember, clear ALL data, not just cache, even for this one
- Reboot
- Toggle Airplane mode off
You should now have a rooted device that can be used to pay for groceries. How cool is that.
If Pay app states device is not certified, there is high chances you did not follow exactly the described steps.

I really like a rooted phone as always. I will wait till there is a way to reinstall the standard ROM. Then it will be safe for me to try.

I'm on the latest update and not able to unlock the bootloader. I enabled OEM unlocking in developer options and rebooted to bootloader. On the first screen it says "Device status: Locked" and doesn't react on any fastboot command. When I enter recovery and start fastboot, each command will fail (command not present in this implementation). Any hints?

Finally managed to unlock the bootloader. The trick was to use an USB2.0 port on my PC.

I live in US so don't have one in my hands yet. Has anyone done a .QCN dump of the phone yet? Do you program the phone with Firehose EDL? Are there qualcomm drivers? I have so many questions.

I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems

Generally speaking I can only but encourage you to register and browse the fairphone forum as there are much much more resources, guides and activity around the fairphone 4 than on xda.

I'm using latest magisk 24.1 and todays OTA fails. I tried with Zygisk on and off. In the magisk app under install there is a install to new slot thing but I feel like that's supposed to be used if it don't fail. will I brick my phone if i click it?
edit:
found this on fp forum
Fixing OTA after rooting
Because my FP is rooted, I couldn’t install the update right away. Message: Couldn't update, installation problem The problem is that the boot partition gets modified when you root your phone and this prevents the OTA package from installing. It’s described well on Quora. This is how I was...
forum.fairphone.com

citroniais said:
I tried it with the latest boot.img avaliable here ('cause I have the A.094 ROM version on my phone)
Fairphone 4 Kernel Source Code — FAIRPHONE open source documentation
code.fairphone.com
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
And that works perfectly, that's my daily driving phone, and no problems
Click to expand...
Click to collapse
My Build-Number say I am on:
FP4.FP3R.A.099.20220112
So it seems my Bootloader version should be A.099 but there is no file like this:
https://storage.googleapis.com/fairphone-source/FP4/A.099-boot.img
Is it okay to take a older boot img or another?
Latest seems to be
https://storage.googleapis.com/fairphone-source/FP4/A.094-boot.img
and before that:
https://storage.googleapis.com/fairphone-source/FP4/A.091-boot.img

yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.

I'm using latest magisk and safetynet-fix-v2.2.1, GPay.SQLite.Fix.v2.5, SQLite for ARM aarch64 devices.

Thomas.swe said:
yes I used 094 to root 099 yesterday, just don't flash the 094 or the modded 094.
Click to expand...
Click to collapse
okay, so you are on a magisk-boot-v-A.094? I thought Magisk, run a direct Install then is only able to patch your current running patched-A.094 boot.
Am I wrong?

I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.

Thomas.swe said:
I have rooted 099 with latest magisk 24.1 you only boot with the 094 versions to root the 099.
Click to expand...
Click to collapse
Yes that it true, you are have root now.
But I think you are on the bootloader version A.094.

the 099 came from OTA so why whould bootloader be 094?

Thomas.swe said:
the 099 came from OTA so why whould bootloader be 094?
Click to expand...
Click to collapse
I am just thinking that you are on 094. Perhaps I am wrong.
But in step 5 you boot the patched 094 img and with this 094 boot image you run the direct magisk install on step 7. If I a not wrong magisk used the current running boot-image. So magisk patched your 094.
Perhaps I am wrong, I am not sure.
EDIT:
You are right @Thomas.swe Sorry for confusing.
See here: https://forum.fairphone.com/t/fp4-root-access-is-possible-maybe-a-bit-risky/76839/144
EDIT2:
@Eznaa does "our device will take much much more time to boot than usual, be patient." mean more than 20 minutes?
EDIT3:
No I used the wrong bootloader. Iode OS has its own bootloader-image upsi

I had root working using this method on A.116-boot.img. I then uninstalled Magisk, did an OTA (to A.128), did "Install Magisk to inactive Slot" (as I successfully did in older OTA updates), but it bootloops. If I `fastboot flash boot A.128-boot.img` it boots normally, but as expected, without root.
I tried an `adb wait-for-device shell magisk --remove-modules` to make sure no Magisk modules are causing the bootloop. I am on Magisk 25.1, btw.
Do you have any idea what could cause the Magisk-patched image to bootloop?

Hi,
Did you try to patch A.128 and boot on it ?
fastboot boot [image]
Please note : the best way to find an answer about any issue related to Fairphone is in the "Fairphone Community Forum" : forum.fairphone.com - The Fairphone users are not using that much XDA

I am thinking of buying Fairphone 4 and need magisk. Can anyone answer a question about the installation instructions above? Magisk website says to flash the magisk patched boot image but here the instruction is to first boot from the magisk patched image, not flash it, and then once booted run a direct install from the magisk app. What is the reason for this extra step?

Just a heads up. Root/Unlock voids FairPhone warranty unfortunately. Only reason I haven't bought this phone.

[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?

Initial Installation of Magisk v24 - patch boot.img

Hey guys, has someone ever installed Magisk v24 by using this Guide:
I have shortened it in the way that I think it's right, NOT TESTED YET
Can anyone with the knowledge about this "proof read it"?
############################################
Get a copy of the boot.img.
You should be able to extract the file you need from official firmware packages or your custom ROM zip.
Next, we need to know whether your device has a separate vbmeta partition.
If your official firmware package contains vbmeta.img, then yes, your device has a separate vbmeta partition
You can also check by connecting your device to a PC and run the command:
adb shell ls -l /dev/block/by-name
If you find vbmeta, vbmeta_a, or vbmeta_b, then yes, your device has a separate vbmeta partition
Otherwise, your device does not have a separate vbmeta partition.
Quick recap, at this point, you should have known and prepared:
Whether your device has boot ramdisk
Whether your device has a separate vbmeta partition
A boot.img or recovery.img based on (1)
Let’s continue to Patching Images.
Patching Images​
Copy the boot image to your device
Press the Install button in the Magisk card
Choose “Select and Patch a File” in method, and select the boot image
Start the installation, and copy the patched image to your PC using ADB:
Code:
adb pull /sdcard/Download/magisk_patched_[random_strings].img
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
Flash the patched boot image to your device.
For most devices, reboot into fastboot mode and flash with command:
Code:
fastboot flash boot /path/to/magisk_patched.img
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
Code:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
Reboot and voila!
Uninstallation​The easiest way to uninstall Magisk is directly through the Magisk app. If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip.
Best, dj

derjango said:
Hey ...
Click to expand...
Click to collapse
Why people look for troubles ?
That guide is for people who don't have custom recovery
it's a long process and some people will make mistakes
renaming to zip and flash in recovery is the easiest way
also with patching img way you will not have a magisk folder in data/adb and magisk will tell you that the install is not complete and probably will need couple of reboots to work ...

To be honest, my trouble is, that the Magisk App does not work properly and I'm searching the reason for that.
It says:
Magsik:
Installed: N/A
Zygisk: No
Ramdisk: No
In the bottomline Superuser is inactive as well as Modules.
How can I fix this?
I've installed Magisk.zip via TWRP, Root Checker tells me that Root is not installed properly
Best, dj
/edit
got it, I had to install it after booting into rom, not directly after flash ROM

derjango said:
In the bottomline Superuser is inactive as well as Modules.
/edit
got it, I had to install it after booting into rom, not directly after flash ROM
Click to expand...
Click to collapse
Hey brother, I've been searching high and low for this problem and got excited seeing your post.
Care to elaborate on how you managed to solve the inactive SU & Modules sections problem?

loopypalm said:
Why people look for troubles ?
That guide is for people who don't have custom recovery
it's a long process and some people will make mistakes
renaming to zip and flash in recovery is the easiest way
also with patching img way you will not have a magisk folder in data/adb and magisk will tell you that the install is not complete and probably will need couple of reboots to work ...
Click to expand...
Click to collapse
I tried doing that with lineage but it stopped internet working

Nebster7 said:
I tried doing that with lineage but it stopped internet working
Click to expand...
Click to collapse
i used .ZIP method on over than 200 rom (including lineage builds) and never had such problem
maybe in new magisk builds ? or miui based rom ?

Done it now using boot_a and boot_b method https://www.getdroidtips.com/how-to-root-poco-x4-pro-5g/

Nebster7 said:
Done it now using boot_a and boot_b method https://www.getdroidtips.com/how-to-root-poco-x4-pro-5g/
Click to expand...
Click to collapse
so you look on how to root "Poco X4 Pro 5G" on "redmi note 8" forums ?