Update to Android 10 on magisk & Edxposed?

[DvLAx3l]

Can anyone with a pixel 3XL on the Android 10 confirm if the latest version of Edxposed works or not? Attempted this 2 weeks ago, got myself in a bootloop in which I just ended up wiping and starting over

You have to use the the latest canary edxposed + a custom magisk from the same dev at moment.

 

[TheXclusive814]

You have to use the the latest canary edxposed + a custom magisk from the same dev at moment.

Thanks!!!

 

[DvLAx3l]

Thanks!!!

Your welcome! Anyway if u end in a bootloop for a magisk module use this, no need to wipe ?

https://forum.xda-developers.com/pixel-3-xl/themes/magisk-modules-disabler-t3966867

 

[TheXclusive814]

3xl Android 10....EdXposed...Yahfa or Sandhook to avoid bootloop?

 

[DvLAx3l]

3xl Android 10....EdXposed...Yahfa or Sandhook to avoid bootloop?

Both works, personally I'm using the yahfa because is more stable with xinsta module

 

[TheXclusive814]

Both works, personally I'm using the yahfa because is more stable with xinsta module

Thanks. I believe it was the SandHook I tried a few weeks ago and put myself into a bootloop and had to reimage.

 

[bush911]

0455beta(YAHFA)+Riru-Core+ latest custom Magisk works well

Finally, I made it.
I am using Pixel 3, I had not made mind to upgrade android 10 as Edxsposed is a must for me.
Yesterday I did a full trwp backup then gave it a go.

For the Latest custom Magisk +0460 build, edxposed seems active, but no module is workable.

 

[fronten]

Pixel 3, Android 10, March update, with Magisk 7.5.1 (267), Riru Core 19.7, Riru EdXposed 4.6.1 (Sandhook) working fine, I am using it to get beloved Gravitybox working again.
You need to install the Version 10.0.0-beta-6 [Q] APK, because EdXposed Manager does not feature it yet (only up to Android 9, will be listed when stable).
It is 100% stable for me, but I only use it for displaying Network speeds in status bar.
I thought you might want to know..

 

[timg11]

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:

Replying to this old thread to see if anything has changed in the last 15 months.
I'm evaluating moving from Pie on Pixel 3XL all the way to the latest Android11 - crosshatch-ota-rq1a.201205.003.

From this Magisk article, I learn than the Pixel 3XL has changed boot methods. I'm currently running Pie (RV 28) which is boot method "Method B - Legacy SAR". Android11 is RV 30, which is "Method C - 2SI ramdisk SAR".

Since this change took place between Android 10 (RV 29) and Android 11 (RV30) there could be an impact on the update process described above by @GunToYoMouth123 .