[Guide]How to Root Your Pixel 3a and Install Magisk - Android 9, 10 or 11

[hoqpus]

When I try to follow the OTA update instruction from OP (Magisk Method) "Settings/System/System Update" will not find any updates.

Any ideas? I'm currently stuck on 200305.002 update but I remember having the same issue when I finally update to that version.

Unfortunately I don't remember how else I updated back then but it was more complicated.

Thanks!

 

[Completely_Clueless]

I had automatic updates turned off, but just a few minutes ago I got a notification that an update was ready to install, and that I should reboot. Well, I didn't reboot immediately. Instead, I followed the instructions in the OP of this thread, and first installed Magisk to the inactive slot (Step 3) and then rebooted via Magisk (Step 4).

Now my phone appears to be stuck at the "G" logo. It's been this way for the past 10-15 minutes. I don't think it's boot looping, since the boot screen isn't replaying and my phone isn't vibrating. It's just showing the sliding bar for a really, really long time. How long do OTA installations take? I'm getting kind of worried now that something went wrong. I didn't have any Magisk modules installed, other than Systemless Hosts (so I could use AdAway). What should I do?

 

[AndDiSa]

@Completely_Clueless I had similar issues when I was updating to the June version. Easiest way to exit from this situation:

Flash the factory image / full ota package manually (be careful not to wipe your data when flashing the factory image).

After that you can re-root and everything should be fine without loosing any data.

 

[ritchea]

When I try to follow the OTA update instruction from OP (Magisk Method) "Settings/System/System Update" will not find any updates.

Any ideas? I'm currently stuck on 200305.002 update but I remember having the same issue when I finally update to that version.

Unfortunately I don't remember how else I updated back then but it was more complicated.

Thanks!

Did you get notification that the system update was available? If not (usually no update for me), you'll have to go a different route. I think there is a way to update through adb sideload. I never used that method, but someone can explain it to you. I usually just download the full factory image, pull the boot.img, put it into the phone so magisk can patch it, then save it on my pc. I remove the rewrite (-w) from the full factory image then run the .bat. At the end, I go to bootloader to flash the patched boot.img. It sounds complicated, but it's pretty quick for me to do it this way. For the first time in 6 mos, the update actually showed up on my phone. I had to review the steps here before going that (the simplest way, really) route. I think you have to be sure that you have a patched boot image through Magisk on your phone. I'll look for the OTA sideload info. Scroll down on the first post. The instructions are there.

 

[Completely_Clueless]

@Completely_Clueless I had similar issues when I was updating to the June version. Easiest way to exit from this situation:

Flash the factory image / full ota package manually (be careful not to wipe your data when flashing the factory image).

After that you can re-root and everything should be fine without loosing any data.

I flashed the latest July factory image, after removing the -w flag from "flash-all.bat." Flashing in this manner did allow my device to boot, though I lost root. Then I just applied the following instructions to get root back:

1. Extracted "boot.img" from the latest July factory image
2. Copied "boot.img" to my phone
3. Used Magisk Manager to patch "boot.img" and output "magisk_patched.img"
4. Coped "magisk_patched.img" to my computer
5. Rebooted into the bootloader (by typing adb reboot bootloader on my computer)
6. Flashed "magisk_patched.img" (fastboot flash boot magisk_patched.img)
7. Rebooted the phone

Now everything is back to normal and I'm running the latest July software . Thank you for your help!

 

[NameLessThugZero]

I have an odd problem. When i apply the patch July boot img (Pixel 3a, Edxposed, ExKernal), the phone sees the root, but upon rebooting, my touch screen does not work at all. ADB and fastboot stays intact but I cannot do anything on the screen. Sidebuttons work just fine.

How I eventually got here:
- I saw that I had a "google play system update" and it needed to reboot my phone. I thought thought this was finally my july update so I went to Magisk and did the OTA uninstall routine listed on his github. So phone reboots, but hangs on the "G" screen for almost 30 minutes.
- I powered it down and back on again, and when it booted, i didnt have root. Did some research and found that this was NOT an OTA. So i decided id just go ahead and manually update like I always do.
-I sideloaded the OTA update, booted to screen to let it finish, then after patching the July boot img, I reflashed boot to fastboot and flashed it.
- Once it finished, i tried to fastboot reboot but the device would not reboot at all and would only default back to the fastboot screen. After more research and wondering WTH, I ended up flashing the stock img (without rewriting my data) and I eventually was able to reboot, just without root. I decided to redo the patching of the July boot img just to be sure, and reflashed boot.
- Phone booted, with root (i know this because I have my lockscreen PIN numbers scrambled via root) but I had no touchscreen functionality. It seems the only way I can, is if I have the stock boot.img flashed.

Can anyone offer some help? Sorry for the long story.

---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------

With June OTA update, I've run into problem after flashing patched boot image. The screen is unresponsive after the device booted. Do I need to update Magisk?

Edit: Unfortunately, this one doesn't work with Magisk version 20.4. Tried reinstalling Magisk and patching the boot image extracted via the payload dumper, still a no go.

Regarding your edit, where did you find this information? I have the same issue.

 

[hoqpus]

Did you get notification that the system update was available? If not (usually no update for me), you'll have to go a different route. I think there is a way to update through adb sideload. I never used that method, but someone can explain it to you. I usually just download the full factory image, pull the boot.img, put it into the phone so magisk can patch it, then save it on my pc. I remove the rewrite (-w) from the full factory image then run the .bat. At the end, I go to bootloader to flash the patched boot.img. It sounds complicated, but it's pretty quick for me to do it this way. For the first time in 6 mos, the update actually showed up on my phone. I had to review the steps here before going that (the simplest way, really) route. I think you have to be sure that you have a patched boot image through Magisk on your phone. I'll look for the OTA sideload info. Scroll down on the first post. The instructions are there.

Hi Ritchea,

this was helpful, thank you very much.
To have it step-by-step next time I will document here what I did:

- This is in case you have a rooted Pixel (3a) device but you are not getting automatic OTA updates -
- you could also call it "how to manually apply an OTA update" -
- this method will keep your phone rooted -

Precondition: computer with platform tools

1. download latest factory image from here and extract on your computer
2. put "boot.img" on your phone and patch it using magisk (install -> install > select and Patch a File)
3. copy output "magisk_patched.img" to your computer
4. follow these instructions to modify (remove -w) and run the flash-all.bat
5. Reboot into the bootloader ("adb reboot bootloader" via platform tools)
6. Flash "magisk_patched.img" ("fastboot flash boot magisk_patched.img")
7. Reboot the phone ("fastboot reboot")

 

[ritchea]

Hi Ritchea,

this was helpful, thank you very much.
To have it step-by-step next time I will document here what I did:

- This is in case you have a rooted Pixel (3a) device but you are not getting automatic OTA updates -
- you could also call it "how to manually apply an OTA update -
- this method will keep the phone rooted -

It's great you took the time to consolidate and simplify the info. Newcomers seem to need to have this info in front of them.

 

[Completely_Clueless]

Try flashing the factory image

I have an odd problem. When i apply the patch July boot img (Pixel 3a, Edxposed, ExKernal), the phone sees the root, but upon rebooting, my touch screen does not work at all. ADB and fastboot stays intact but I cannot do anything on the screen. Sidebuttons work just fine.

How I eventually got here:
- I saw that I had a "google play system update" and it needed to reboot my phone. I thought thought this was finally my july update so I went to Magisk and did the OTA uninstall routine listed on his github. So phone reboots, but hangs on the "G" screen for almost 30 minutes.
- I powered it down and back on again, and when it booted, i didnt have root. Did some research and found that this was NOT an OTA. So i decided id just go ahead and manually update like I always do.
-I sideloaded the OTA update, booted to screen to let it finish, then after patching the July boot img, I reflashed boot to fastboot and flashed it.
- Once it finished, i tried to fastboot reboot but the device would not reboot at all and would only default back to the fastboot screen. After more research and wondering WTH, I ended up flashing the stock img (without rewriting my data) and I eventually was able to reboot, just without root. I decided to redo the patching of the July boot img just to be sure, and reflashed boot.
- Phone booted, with root (i know this because I have my lockscreen PIN numbers scrambled via root) but I had no touchscreen functionality. It seems the only way I can, is if I have the stock boot.img flashed.

Can anyone offer some help? Sorry for the long story.

---------- Post added at 05:17 PM ---------- Previous post was at 05:13 PM ----------



Regarding your edit, where did you find this information? I have the same issue.

Hmm, I haven't had any problems like what you've described with your screen. However, I did have a really long "install" time for the OTA update (I left my phone on overnight and it still showed the "G" logo and the install bar!). So I think I also had a botched automatic OTA update like you.

But as I mentioned in my post above yours, I just performed a full factory image flash, without the -w flag. Then I rebooted once into normal, unrooted Android. Then I rebooted into fastboot mode and reflashed "magisk_patched.img," and was able to regain root with no problems. I did not sideload the OTA update.

Maybe you could try installing the complete factory image.

 

[sic0048]

Regarding the issue with phones never booting past the G logo screen - If you had Magisk installed and were using some modules, it could be that one of the modules is incompatible with the update. It happened to me an update or two ago. I had to use the Magisk disabler guide to boot into the phone without Magisk.

 

[Joe333x]

Hey guys quick question. I have a friend with a 3a that wants to get into custom ROMS. I have been doing this since the G1 so I have always and am still a proponent of doing full back ups before flashing a new rom. With TWRP not available with Android 10 from the 3a is there anyway to create a full backup? Is there a way to tell if the device is able to downgrade to 9? I know I read on TWRP that if it shipped with 10 you cannot downgrade it.

 

[AndDiSa]

Hey guys quick question. I have a friend with a 3a that wants to get into custom ROMS. I have been doing this since the G1 so I have always and am still a proponent of doing full back ups before flashing a new rom. With TWRP not available with Android 10 from the 3a is there anyway to create a full backup? Is there a way to tell if the device is able to downgrade to 9? I know I read on TWRP that if it shipped with 10 you cannot downgrade it.

Question is: for what is your need of the backup?
You have the factory images which enable you to recover the phone in any case if you want to go back

If it comes to apps/data it's a bit more complicated. Most of those are generally backuped to the Google cloud and can be restored from there while setting up the device. But it's not a really a backup.
When it comes to real backup of apps and data Titanium or Migrate might work for you or you can try whether the scripts of my Android Backup and Restore Tools work for you.

 

[Joe333x]

Question is: for what is your need of the backup?
You have the factory images which enable you to recover the phone in any case if you want to go back

If it comes to apps/data it's a bit more complicated. Most of those are generally backuped to the Google cloud and can be restored from there while setting up the device. But it's not a really a backup.
When it comes to real backup of apps and data Titanium or Migrate might work for you or you can try whether the scripts of my Android Backup and Restore Tools work for you.

Okay thanks, so there is no way to create a nandroid backup using adb?

 

[AndDiSa]

@Joe333x no, unfortunately not. That's the reason why I started my project, but it becomes more and more difficult to get data off the device ... at least if you want to keep SafetyNet compatibility.

 

[jawz101]

fyi- in case anyone is wondering, this weekend I installled Magisk Canary builds on Android 11 beta and it worked just fine for apps requiring root. Same instructions- just use the canary build on the magisk github site.

 

[sic0048]

I've updated the OP to mention that the technique works for Android 11. I have installed Android 11 today and have rooted it like normal. Just make sure you are using the latest canary builds. The latest "Stable" version will not work.

I would suggest that you remove all modules prior to updating.

Also, to be safe, don't flash the magisk_patched.img the first time. Use the command "Fastboot boot magisk_patched.img" instead. This will prevent you from being stuck in a bootloop should something go wrong. If everything works, then permanently flash the file by using the regular "Fastboot flash boot magisk_patched.img" command

 

[Ritwyk]

Just make sure you are using the latest canary builds. The latest "Stable" version will not work.

This helped. I looked here only after I failed to get it booting the first couple of times.
For other users on 11, remember that you need to not only get the canary manager, but also set the update channel to 'canary' before patching the stock boot image.
If you've accidentally flashed a patched boot created using a non-canary version and have ended up in a bootloop/persistent bootloader, do this to avoid losing your data in a factory reset:

1. Shut down the phone by long-pressing the power button.
2. Boot into recovery by pressing PWR + VOL UP.
3. Follow the instructions in the OP to sideload the latest OTA, then reboot.

 

[merlin6335]

I don't really know if it's the right place to ask, but suddenly the SafetyNet check fails on my device and so does Google Pay. Even after an unroot, it doesn't work again, which seems very strange to me. Maybe someone has an idea.

Edit: Magisk Hide was disabled, my bad!

 

[Dixon Butz]

I don't really know if it's the right place to ask, but suddenly the SafetyNet check fails on my device and so does Google Pay. Even after an unroot, it doesn't work again, which seems very strange to me. Maybe someone has an idea.

Edit: Magisk Hide was disabled, my bad!

G Pay won't work with unrooted and unlocked bootloader.

 

[eevanskiteboards]

just rooted my phone thanks to this forum. thanks everyone