Related
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
I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.
timg11 said:
I see "11.0.0 (RQ1A.201205.003, Dec 2020" is available for Crosshatch and Blueline.
I'm still on Android 9 with Magisk installed by patching the boot image.
Is the following process still valid and supported for applying an OTA update to Android 11, and then re-installing Magisk?
1) Magisk Manager → Uninstall → Restore Images
2) Apply the OTA update :
__a) Boot into factory recovery
__b) Choose Apply update from ADB
__c) From windows: adb sideload crosshatch-ota-rq1a.201205.003-4d6e609b.zip
__d) Reboot phone and let the update finish in Android
3) Separately download the corresponding Factory image: crosshatch-rq1a.201205.003-factory-d5cb2a93.zip. Extract the boot.img, move it into the Pixel 3 XL's download folder
4) Uninstall old Magisk manager and install the latest Magisk Manager (Direct Install Magisk Manager v8.0.4 from here, per Magisk installation instructions)
5 ) Open Magisk Manager and Press Install ==> Press Install again ==> Select Patch a File ==> Select the boot.img file in "Download". It will be patched.
6) Copy the magisk_patched.img file to your computer's Platform-tools folder
7) Boot Pixel 3 XL into fastboot mode by typing the commad: adb reboot bootloader
8) Once phone is on fastboot mode then type: fastboot flash boot magisk_patched.img
9) Once it's done then type the command : fastboot reboot
10) Open Magisk Manager and check if its rooted
This is based on the process from about a year ago. so please reply if anything has changed.
Click to expand...
Click to collapse
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.
TonikJDK said:
You might be able to skip all the step 2's and just check for update after unrooting and take the ota normally. That has worked for me for quite awhile.
Other than that, your steps are spot on and work with 11.
Click to expand...
Click to collapse
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
Best practice would be to do an actual update and reboot bootloader to flash your patched boot.img. If you are jumping android releases problems might arise that no one can account for and generally you should do a full wipe when switching releases. Google has by no means accounted for any contingencies in the ota process, read the disclaimer they give upon an ota (any data lost in the process is never their fault, so backup you stuff). Patching the boot image through the manager is the preferred method, anything else is very difficult to troubleshoot.
timg11 said:
Thanks for the reply. So to take the OTA (which I do get periodic prompts for), I'd just use the "uninstall" function at the bottom of Magisk Manager, then take the update?
Can you confirm that you moved from Pie (9) to Android 11 in one step?
I just posted in a Magisk thread asking about the boot method change between Android 10 and Android 11. I'm unclear of the implications. Hopefully Google has tested all the from/to contingencies in their OTA process?
Click to expand...
Click to collapse
By boot method do you mean unroot, do not boot, update do not boot, then root the inactive slot?
Do not do that, on 11 it can go bad in fact if you have 11 it will not even be available in Magisk. He took it out for now due to problems.
What I was suggesting bead unroot, boot, take the OTA, boot. Then patch the boot img and flash it.
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
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?
Hi guys!
I am new here, recently unlocked bootloader (guide)
Eagerly want to flash lineage OS, but can't. Always ended up multiple reboots or some black screen.
Can anyone write step by step guide?
Currently using Android 9 Stock ROM (came back from android 10 stock rom using this method)
Used TWRP from here
Have you read the wiki page for LineageOS for N 6.1?
Info about PL2 | LineageOS Wiki
wiki.lineageos.org
Update: Installed.
NOTE: It is recommended to update your stock ROM to Android 10 before flashing this custom ROM. ( this method )
Just reboot to bootloader and download this TWRP for our Nokia 6.1, boot it (fastboot flash boot twrp.img), and everything will be fine.
Power + Volume Up
and leave power button when you see the android one logo but keep pressing volume up
Now you can flash TWRP.zip file.
Format Data by typing yes
Reboot to TWRP.
Flash latest ROM zip via TWRP
Switch to an alternative slot (if you are on slot a, switch to b if you are on b, switch to a) - (if you don't know where is the option to switch: reboot >> select slot)
Reboot system
Thanks to this guy https://forum.xda-developers.com/t/rom-12-1-unofficial-pixysos-pl2.4454103/
hello @chsiva, I would like to know if when installing the version of lineageOS 19.1 you used the lineageOS recovery, in my case I have reinstalled LineageOS 19.1 more than once without any problem. In fact, it is not so necessary to have the latest version of Android from the manufacturer installed to be able to install this version of lineageOS, I will explain the steps to be successful in the process.
1) Do not leave any custom recovery as permanent.
2) Since I have Windows 10, I had to look for the drivers that really work for Nokia, in which there are 2 drivers that are needed and apply some additional configurations to the main installer, one of them is compatibility with old versions of the operating system.
3) Download the tool that includes fastboot + adb and verify that the device is really recognized by the operating system regardless of the mode in which it is.
4) Being in the stock version, I recommend you to factory reset the device, then configure it.
5) Enter the download mode and through the cmd and in the adb mode use it to change the slot A/B (A or B), In both you will have to install the lineageOS recovery.
6) Having the recovery installed in both Slots (Remember to use Fastoboot to install the recovery) I recommend you to be in Slot B to proceed with the installation of the rom.
7) Then access the recovery, in my case I decided to perform a data format from the recovery and then select the ADB installation, I recommend you disconnect the device before accessing this option, when you access this option, connect the device to the computer (the recovery should indicate that you are in slot b before continuing with this).
8) Install the lineageOS rom and after it finishes, reboot the device and wait for it to boot.
9) When booting into lineageOS, apply settings and then reboot back into recovery mode.
10) Install the necessary Gapps to have the basic services of google, remember to be in slot b to continue, after installation, restart and when starting, connect to a network and configure.
11) The normal thing is that it is configured but in a partial way, the contacts that you have saved in your google account should not appear if you have it saved, if this happens, you only have to reset the device from the factory.
12) When starting again, apply the configuration connected to the network since the gapps are already included in the device, more configuration options should appear than the previous time when you installed the gapps and at the end the contacts should appear.
13) now if you can install magisk in version 25.2 if I'm not mistaken, remember to change the .apk to .zip and from the recovery install it from slot b and reboot.
14) and the last thing you need is to install 2 modules to certify the device with magisk (before this, I recommend you activate the option to hide root from applications, magisk should request a reboot, before rebooting, apply the deny settings of root to the applications that you deem convenient, but those of google if or if they have to be denied, in google services, mark all the options to deny root in its entirety).
15) For this procedure you will need a terminal and from the terminal, type the command (props), then press ENTER and sign the device.
16) and then delete data from play store and google services and then reboot the device and voila, your device is ready to use.
-In the event that you do not have a windows operating system, you can use the virtualbox tool and if it is possible to install the version of windows 7 ultimate, although you will have to install some necessary drivers so that you do not have a problem with the execution of applications from the virtualized system.