[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted

[pbanj]

i decided to post the link now. has stock and patched. i also provided the newest canary manager

 

[Geo52rey]

i decided to post the link now. has stock and patched. i also provided the newest canary manager

Thanks for posting the patched image. It works great.

I did the following:
1) fastboot boot boot.img # to test to see if it worked
2) once it worked, I used the direct install method
3) after a reboot I still had root

My question is... How did the patched version I made with Magisk Manager not work, but yours does? After doing a diff of the two images it seems that the magisk_patched.img is different from the patched image you provided. Should I post an issue on the Magisk GitHub? @pbanj

 

[meazz1]

Thanks for posting the patched image. It works great.

I did the following:
1) fastboot boot boot.img # to test to see if it worked
2) once it worked, I used the direct install method
3) after a reboot I still had root

My question is... How did the patched version I made with Magisk Manager not work, but yours does? After doing a diff of the two images it seems that the magisk_patched.img is different from the patched image you provided. Should I post an issue on the Magisk GitHub? @pbanj

I believe it has to do with the right version of magisk to work. You needed a specific canary version of magisk to create the boot.img file.

 

[Geo52rey]

So now I'm facing a similar issue to @meazz1. I installed a module to enable miracast on Pixel devices and when I boot off the patched boot.img, my phone gets stuck at the G. I can still boot off the stock boot.img tho. Is there a way to disable all Magisk modules at boot or remove all Magisk modules from the /data partition?

 

[captain sideways]

Make sure you phone is recognised and authorised in adb, then turn it off.

Run this:

adb wait-for-device shell magisk --remove-modules

Then boot your phone and it should disable your modules ?

 

[Geo52rey]

Make sure you phone is recognised and authorised in adb, then turn it off.

Run this:

adb wait-for-device shell magisk --remove-modules

Then boot your phone and it should disable your modules

When I run this command, my pixel 3a reboots to bootloader with the error message "no valid slot to boot". And it won't start unless I explicitly flash the boot partition.

Edit: It seems that a process named "[mmc-cmdqd/0]" is waiting for and I/O opteration to finish. Could this be related to my issue?

 

[captain sideways]

Ah OK, sorry about that, I don't have any other advice - I had a dodgy module a long time ago and that's how I disabled them in order to boot. That was on an S7 which doesn't have the A/B partitioning that a pixel has

 

[captain sideways]

Not sure if this will help but try flashing it:

fastboot flash boot magisk_patched.img

It a clean boot img from 11.0.0 (RP1A.200720.009, Sep 2020), Patched with Magisk 20425 - also included.

I've just tested this on my phone and it booted first time

I'll leave it up until Sunday 23:59

http://bit.ly/xdamagiskpatched

---------- Post added at 07:30 PM ---------- Previous post was at 07:28 PM ----------

So now I'm facing a similar issue to @meazz1. I installed a module to enable miracast on Pixel devices and when I boot off the patched boot.img, my phone gets stuck at the G. I can still boot off the stock boot.img tho. Is there a way to disable all Magisk modules at boot or remove all Magisk modules from the /data partition?

Boot from stock, remove your magisk modules and manager and see my post to the link with working versions, hope this works for you ?

 

[Geo52rey]

Boot from stock, remove your magisk modules and manager and see my post to the link with working versions, hope this works for you

It seems removing magisk manager was a crutial step to removing the bad modules. Thanks

 

[Afdabrikman]

Thank you very much

 

[Drakax]

People having issue, follow this:
https://github.com/topjohnwu/Magisk/issues/3292#issuecomment-706514525

 

[LightC]

Does anyone know how to disable specific EdXposed modules without removing the EdXposed module from Magisk? It seems like one of the modules I had enabled in Xposed before upgrading to Android 11 is causing a boot issue. I might want to downgrade to Android 10 but I would like to figure out which specific Xposed module is causing the issue first. If I remove all magisk modules and add them back one-by-one, the boot stalling issue happens only after enabling the EdXposed magisk modules (which have a few modules I had enabled in Android 10).

I tried looking in /data/misc/riru/modules/ but didn't see any files to delete there. I think I'm using instaprefs and kmod FWA in Xposed right now. I'd like to be able to disable those to see if it is causing the boot stalling issue or whether it is just EdXposed.

 

[Brandroid28]

Does anyone know how to disable specific EdXposed modules without removing the EdXposed module from Magisk? It seems like one of the modules I had enabled in Xposed before upgrading to Android 11 is causing a boot issue. I might want to downgrade to Android 10 but I would like to figure out which specific Xposed module is causing the issue first. If I remove all magisk modules and add them back one-by-one, the boot stalling issue happens only after enabling the EdXposed magisk modules (which have a few modules I had enabled in Android 10).

I tried looking in /data/misc/riru/modules/ but didn't see any files to delete there. I think I'm using instaprefs and kmod FWA in Xposed right now. I'd like to be able to disable those to see if it is causing the boot stalling issue or whether it is just EdXposed.

I thought edxposed canary was working when I first flashed it, but then hung on boot after enabling modules. idk. how were you able to boot with root afterwards? I was able to reboot into safe mode to disable magisk modules a couple times, but for some reason I can't get it to work now

edit: you can flash the stock image, reboot to safe mode using the power menu, hold volume down to enter fastboot, flash magisk boot, reboot.

edit: are you sure all your xposed modules are supported in 11? I've got my issue fixed and now have xposed enabled with a few modules. I don't think you can disable one with the edxposed magisk module disabled. should be able to *uninstall* the xposed modules one-by-one, though to troubleshoot

Sent from my Pixel 3a using XDA Labs

 

[LightC]

The only way I've been able to get to boot after enabling the edxposed modules is by removing all magisk modules using this adb command:
adb.exe wait-for-device shell magisk --remove-modules

I guess the problem I'm having is that I need to revert back to Android 10 to even be able to disable the modules *within* edXposed as the only way I know how to disable them is in Xposed Manager. I was wondering if there is another way to disable modules within the edxposed framework from adb like you can with the above magisk shell command

I thought edxposed canary was working when I first flashed it, but then hung on boot after enabling modules. idk. how were you able to boot with root afterwards? I was able to reboot into safe mode to disable magisk modules a couple times, but for some reason I can't get it to work now

edit: you can flash the stock image, reboot to safe mode using the power menu, hold volume down to enter fastboot, flash magisk boot, reboot.

edit: are you sure all your xposed modules are supported in 11? I've got my issue fixed and now have xposed enabled with a few modules. I don't think you can disable one with the edxposed magisk module disabled. should be able to *uninstall* the xposed modules one-by-one, though to troubleshoot

Sent from my Pixel 3a using XDA Labs

 

[Drakax]

Pixel 3a - Sargo - magisk_patched - boot.img - December 2020
https://gofile.io/d/7CV7Zb

 

[azadarradaza]

I sideloaded Dec ota on stock Nov factory image and used patched boot. I am losing root on reboots. Any ideas?

 

[oldbear3]

Hi,
I didn't see it throughout the post but for me, I can take OTA updates only with the alternative method, described here.
So, I'm afraid to flash TWRP, as I won't be able to flash the OTA updates with the "apply update from adb" option.
Is there a post or someone who knows how I can apply the OTA updates with TWRP ?