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

[duh1]

Are you sure it is Magisk? My Nexus 6 is on 19.3 as well and Netflix works and still appears in the Play Store. I did nothing more than install 19.3. The Nexus 6 is on LineageOS.

On my Pixel 3a Netflix is working for me because I had it installed from before the June update, but it has disappeared from the Play Store now. Magisk 19.3, Elemental X 1.02. Magisk hide is enabled for Netflix.

I downgraded to 19.2, set Magisk to core mode, turned off USB debug, cleared store/services data and cache, still no Netflix. I wouldn't be surprised if Google and Netflix are testing out some new methods of detection...

 

[CAExempt911]

Ok might have an issue here...

Pixel 3a, rooted via Method 2.

Followed the steps

adb reboot recovery
adb sideload sargoota.zip
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.061s

fastboot flash boot_b june_boot.img
C:\Users\SysAdmin\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot_b june_boot.img
Sending 'boot_b' (65536 KB) OKAY [ 1.598s]
Writing 'boot_b' OKAY [ 0.726s]
Finished. Total time: 2.539s

I received a message upon reboot "Your device is corrupt and cannot be trusted", it rebooted and is now on the G screen loading and has been a while now.

What's my options here?

 

[duh1]

Ok might have an issue here...

Pixel 3a, rooted via Method 2.

Followed the steps

adb reboot recovery
adb sideload sargoota.zip
fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.061s

fastboot flash boot_b june_boot.img
C:\Users\SysAdmin\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot_b june_boot.img
Sending 'boot_b' (65536 KB) OKAY [ 1.598s]
Writing 'boot_b' OKAY [ 0.726s]
Finished. Total time: 2.539s

I received a message upon reboot "Your device is corrupt and cannot be trusted", it rebooted and is now on the G screen loading and has been a while now.

What's my options here?

I assume after flashing the OTA you rebooted directly to bootloader mode before flashing the boot image? If that was done correctly, you have a corrupt boot image. Over in the Magisk thread others say 19.3 and the June update don't play well together.

When you are stuck on the boot screen, you can turn off by holding the power button until it shuts down.

Press & hold Power + Volume down button for a few seconds to boot your phone into bootloader mode. Reflash a fresh copy of the June patched boot image to slot b as before and reboot.

If that still doesn't work, see if you can go back to your previous March system. In bootloader mode...
fastboot set_active other
and reboot. It that boots correctly, go with update method 1 this time using March stock, or stay with March for a while -- June is a bit buggy...

 

[jmtjr278]

I just did the automated Google pay trick. Worked well. Do I need to copy/paste those commands into a terminal emulator every reboot? I think that's why he created the script. Am I correct?

Sent from my Pixel 3a using Tapatalk

 

[netllama]

Just got a brand new 3a, and I'm attempting to root it per the 'method 1' instructions, but I keep getting stuck in a boot loop immediately after the 'fastboot flash' and 'fastboot reboot' steps.

The phone currently has build number PD2A.190115.032. I installed Magisk Manager v7.3.0 (attempts to use older builds refuse to let me click install, then select the "Select and Patch a File" option, as it always insists on updating to the latest Manager version first (if there's some work around, please let me know).

Here's exactly what I'm doing (this is on a Linux system):

$ adb reboot bootloader
$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.011s
$ fastboot flash boot_a magisk_patched.img 
Sending 'boot_a' (29064 KB)                        OKAY [  1.030s]
Writing 'boot_a'                                   OKAY [  0.574s]
Finished. Total time: 1.685s
$ fastboot reboot
Rebooting                                          
Finished. Total time: 0.168s

After that point, it goes to a boot loop, and the only way to boot into the OS again is to reflash the original boot.img. I'm guessing there's either some bug lurking somewhere, or I'm making a stupid mistake.

Any suggestions appreciated!

 

[fearsparks]

Just got a brand new 3a, and I'm attempting to root it per the 'method 1' instructions, but I keep getting stuck in a boot loop immediately after the 'fastboot flash' and 'fastboot reboot' steps.

The phone currently has build number PD2A.190115.032. I installed Magisk Manager v7.3.0 (attempts to use older builds refuse to let me click install, then select the "Select and Patch a File" option, as it always insists on updating to the latest Manager version first (if there's some work around, please let me know).

Here's exactly what I'm doing (this is on a Linux system):

$ adb reboot bootloader
$ fastboot getvar current-slot
current-slot: a
Finished. Total time: 0.011s
$ fastboot flash boot_a magisk_patched.img 
Sending 'boot_a' (29064 KB)                        OKAY [  1.030s]
Writing 'boot_a'                                   OKAY [  0.574s]
Finished. Total time: 1.685s
$ fastboot reboot
Rebooting                                          
Finished. Total time: 0.168s

After that point, it goes to a boot loop, and the only way to boot into the OS again is to reflash the original boot.img. I'm guessing there's either some bug lurking somewhere, or I'm making a stupid mistake.

Any suggestions appreciated!

I was having very similar issues, I went ahead and flashed the new June update (came from pd2a.190115.032) by extracting the files to my platform-tools directory and running the flash-all.bat. After that I started over with installing magisk-manager (newest update), patching the original boot.img from the june update, fastboot flashed it to boot_a and I'm now rooted and good to go.

Hope this helps.

 

[creeve4]

If following Method 1, would it be better to flash EX kernel after installing magisk?

This way magisk can restore the stock boot.img before taking an OTA.

 

[netllama]

I was having very similar issues, I went ahead and flashed the new June update (came from pd2a.190115.032) by extracting the files to my platform-tools directory and running the flash-all.bat. After that I started over with installing magisk-manager (newest update), patching the original boot.img from the june update, fastboot flashed it to boot_a and I'm now rooted and good to go.

Hope this helps.

I considered that, but I see multiple people complaining about boot loops after updating to the June update.

---------- Post added at 09:45 ---------- Previous post was at 09:44 ----------

I was having very similar issues, I went ahead and flashed the new June update (came from pd2a.190115.032) by extracting the files to my platform-tools directory and running the flash-all.bat. After that I started over with installing magisk-manager (newest update), patching the original boot.img from the june update, fastboot flashed it to boot_a and I'm now rooted and good to go.

Hope this helps.

If following Method 1, would it be better to flash EX kernel after installing magisk?

This way magisk can restore the stock boot.img before taking an OTA.

I don't know what the EX kernel is.

 

[pbanj]

Here is a fix for those who updated with edge sense plus installed. https://cdn.discordapp.com/attachme.../589904771545300992/boot-magisk-core-only.img

Use "fastboot boot" instead of "fastboot flash". After that boots open up Magisk manager and remove the edge sense plus mod. You can then root properly.

The file is based on the June update and was made by @ApeironTsuka so everyone should thank them.

Once I get home I'll add this to the main post, but I wanted to share this asap.

 

[pbanj]

the fix has been added to the main post, along with a little guide for using it.

 

[ApeironTsuka]

Here is a fix for those who updated with edge sense plus installed. https://cdn.discordapp.com/attachme.../589904771545300992/boot-magisk-core-only.img

Use "fastboot boot" instead of "fastboot flash". After that boots open up Magisk manager and remove the edge sense plus mod. You can then root properly.

The file is based on the June update and was made by @ApeironTsuka so everyone should thank them.

Once I get home I'll add this to the main post, but I wanted to share this asap.

For those wondering, it's Magisk 19.3 with the /data/cache/.disable_magisk check effectively forced to always succeed, so it will only boot into Core-Only Mode with that image. Hopefully we get a TWRP before the July update, but if not, I'll try to remember to update it.

 

[pbanj]

For those wondering, it's Magisk 19.3 with the /data/cache/.disable_magisk check effectively forced to always succeed, so it will only boot into Core-Only Mode with that image. Hopefully we get a TWRP before the July update, but if not, I'll try to remember to update it.

hopefully people will remember to at least disable the mod before updating this time lol

 

[aziz.yankee]

Use "fastboot boot" instead of "fastboot flash". After that boots open up Magisk manager and remove the edge sense plus mod. You can then root properly.

Thanks - I've downloaded this, but my phone wouldn't boot it just got stuck like this on command promt and my phone screen on Fastboot Mode. I can reboot to normal phone condition though - so phone isn't dead.


C:\Users\aaziz\Desktop\platform-tools>fastboot boot boot-magisk-core-only.img
Sending 'boot.img' (26906 KB) OKAY [ 0.148s]
Booting

 

[pbanj]

Thanks - I've downloaded this, but my phone wouldn't boot it just got stuck like this on command promt and my phone screen on Fastboot Mode. I can reboot to normal phone condition though - so phone isn't dead.


C:\Users\aaziz\Desktop\platform-tools>fastboot boot boot-magisk-core-only.img
Sending 'boot.img' (26906 KB) OKAY [ 0.148s]
Booting

i just tried it on mine and it booted up fine. try redownloading the file

 

[aziz.yankee]

i just tried it on mine and it booted up fine. try redownloading the file

I did redownload - tried to unblocking from Windows Properties (This file came from another computer and might be blocked to protect this computer) as well.

When I try to boot with original boot.img file - it boots up fine....

 

[pbanj]

I did redownload - tried to unblocking from Windows Properties (This file came from another computer and might be blocked to protect this computer) as well.

When I try to boot with original boot.img file - it boots up fine....

you're on the june update correct?

 

[aziz.yankee]

you're on the june update correct?

Yes I am on June update with Pixel 3 (PQ3A.190605.003).

By the way, there is a ActiveEdge shortcut that I've setup before - when I launch it - it does work but no root...

 

[pbanj]

Yes I am on June update with Pixel 3 (PQ3A.190605.003).

By the way, there is a ActiveEdge shortcut that I've setup before - when I launch it - it does work but no root...

stupid question, but your adb and fastboot are up to date right?

 

[HighDesertTrekker]

This fix worked for me. Back to being rooted. Thanks man.

 

[pbanj]

This fix worked for me. Back to being rooted. Thanks man.

really glad to hear that.