yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a Guides, News, & Discussion] alliance1975:
Please, on what evidence do you make this statement?
[Google Pixel 3a Guides, News, & Discussion] SCrid2000:
It's explicitly stated by Google on the webpage where they host the system images...
[Google Pixel 3a Guides, News, & Discussion] Golf c:
I don't see that claim anywhere on the factory image website?
[Google Pixel 3a Guides, News, & Discussion] SCrid2000:
https://developer.android.com/preview/download.html

Emphasis in the original.
[Google Pixel 3a Guides, News, & Discussion] Golf c:
The beta has nothing to do with the stable builds. Manually flashing a current stable build doesn't prevent OTA's in the future. Bootloader locked or unlocked
[Google Pixel 3a Guides, News, & Discussion] alliance1975:
I'll give it a few more days.
[Google Pixel 3a Guides, News, & Discussion] Golf c:
Why wait when you can flash it whenever you want?
[Google Pixel 3a Guides, News, & Discussion] Uzephi:
Flashing official release system images shouldn't remove OTA functionality. This would only happen with beta images. Beta OTA packages work fine when flashing from stock recovery. I flashed the beta 3 OTA zip and have taken beta 4 and 5 OTA in system without issue.
[Google Pixel 3a Guides, News, & Discussion] ApeironTsuka:
No, I never updated it for July/newer Magisk versions. I didn't feel it necessary now that there's a TWRP build for 3a/3a XL.
[Google Pixel 3a Guides, News, & Discussion] koichirose:
I don't understand how to update from June to July without sideloading (stock 3a, rooted with Magisk, no TWRP installed).

I went into Magisk Manager, selected Uninstall -> Restore Images, but the phone can't find an OTA update anyway. Is this right?

I won't have access to a computer I can tinker with for the next few days but I did not reboot yet.

Can I still patch the June boot image again from within Magisk so I'll be able to reboot freely?
[Google Pixel 3a Guides, News, & Discussion] alliance1975:
I tried doing the magisk-uninstall-restore images to test if the OTA was available. If the OTA did not appear then you can go back to magisk, tap install the 19.3 zip and tap direct install. If you had ElementalX kernel installed you will need to reinstall. Then it will be safe to reboot.

Yeah I'm still waiting for OTA to appear but no joy.
[Google Pixel 3a Guides, News, & Discussion] taodan:
Did anyone download the pre-patched July image and was able to get it work? I tried two times but couldn't get it to work. I then tried the method #1 and it worked. So I think the pre-patched July image is corrupted.
[Google Pixel 3a Guides, News, & Discussion] smartfaune:
Hi guys,

I flash factory image Sargo 9.0.0 (PQ3B.190705.003, Jul 2019)

Still stuck :(

Full story here:

https://xdaforums.com/showpost.php?p=79962044&postcount=34961
[Google Pixel 3a Guides, News, & Discussion] sic0048:
You may need to reinstall the OEM factory image. You can find those here with instruction on how to flash it

Once that is done, you might try following these instruction on how to root. They are the same as this thread, but I've tried to go into more detail on each step and therefore might be easier to follow and get a positive result.
[Google Pixel 3a Guides, News, & Discussion] smartfaune:
Perfect!

I do not know exactly what I did wrong the first time.

This may have come from ADB that needed to be updated, or USB debugging that had to be reconfigured

Thank you anyway

Everything works fine now :good:
[Google Pixel 3a Guides, News, & Discussion] pasha_d:
We're you able to get OTA? I'm in the same boat as you with no luck on getting it, and leaning towards sideloading July. I hope it will fix my Captive Portal issue - https://xdaforums.com/pixel-3a/help/captiveportallogin-apk-t3940042
[Google Pixel 3a Guides, News, & Discussion] alliance1975:
I too gave up waiting and sideloaded the OTA. It loaded into inactive slot as expected. I then used bootloader to install magisk patched file to inactive slot. After reboot I added elementalx kernel. I am keeping stock, so did all via adb instead of TWRP. I would still like to know if anyone was successful in getting the OTA via settings-system-advanced-update.

Edit: Saw your op on captive portal, sorry it is a bit more advanced than I can handle.
[Google Pixel 3a Guides, News, & Discussion] Groteski:
Same thing. Doing it manualy works
[Google Pixel 3a Guides, News, & Discussion] octavioromo:
Im also currently unable to see the July update when i check for one. im on june update on Google Fi. I did Method 1 to root and have EX kernel installed. Am i missing anything?

Thanks so much!
[Google Pixel 3a Guides, News, & Discussion] nxt:
I had no issues with June and July update using twrp method to install magisk 19.3.

But with August 2019 update, it doesn't work :(. After installing Magisk 19.3, when it boots up it's taken to a corrupt screen with the option to Try Again or Factory Reset.

Can go back to fastboot, boot up twrp, and uninstall Magisk.zip and it'll boot up fine though.
[Google Pixel 3a Guides, News, & Discussion] bonfire62:
I rooted the July image. I can see the update, but out fails to install. (I did the restore images in manual before hand) anyone else?
[Google Pixel 3a Guides, News, & Discussion] Rudi154:
I'm still on june, and yesterday i got my first OTA notification. (1138.4 MB: maybe august?)

After restoring stock boot.img from magisk the update also fails. Tried a few times...
[Google Pixel 3a Guides, News, & Discussion] selfecce:
Yesterday I got the August OTA notification (~60/70Mb), and successfully updated following the instructions on OTA Updates with Magisk. Root method n.3

Inviato dal mio Pixel 3a utilizzando Tapatalk
[Google Pixel 3a Guides, News, & Discussion] bonfire62:
I'm just trying to remember if I've blocked ota update somewhere in options/rooting process. Can anyone think of another reason that it would keep failing to install?
[Google Pixel 3a Guides, News, & Discussion] spcd:
The guide tells me I can do an update in 3 steps:

1. Uninstall Magisk through Magisk Manager (Restore Images)

2. Go to System -> System Update -> Install update but do not restart

3. Install Magisk on inactive partition after OTA

Well, step 2 doesn't let me install the OTA. It only shows me a restart button. The update must have been installed in the background without my permission. Automatic updates is turned off in developer options.

I was actually still on the June update. Today I received a notification that I could press restart to install the security update (The July update of 1000+ MB which apparantly was already downloaded and installed on the second partition??? )

I believe that the option "Automatic Updates" in developer options doesn't really stop the automatic update from installing to the second partition. But it does stop the phone from switching to that partition until you give permission by pressing restart.

It's confusing.
[Google Pixel 3a Guides, News, & Discussion] AutomaticFailure27:
Yeah, it seems to be the case. I haven't restarted my phone or anything since getting that notification last night. I'm still on the June update as well.
[Google Pixel 3a Guides, News, & Discussion] rootuser11:
same problem for me. I followed the steps and nothing should have edited the system partition. and yet OTA simply fails during the download/install step. oh well, don't want to go through the sideloading step
[Google Pixel 3a Guides, News, & Discussion] Rudi154:
Now I sideloaded July update and then rooted with method 1.

August OTA shows up but fails again.

---------- Post added at 09:03 PM ---------- Previous post was at 08:52 PM ----------

Do you had already root with method 3 BEFORE installing the OTA?

How did magisk create the boot.img backup then (when rooting via twrp)?
[Google Pixel 3a Guides, News, & Discussion] selfecce:
1. Yes, that was the first thing I did after I got my phone actually.

2. When I selected "Magisk Manager → Uninstall → Restore Images" it didn't complain at all and successfully completed the operation, so I assume that the backup was there somehow.
[Google Pixel 3a Guides, News, & Discussion] Rudi154:
Now I tried this:

- Complete uninstall magisk instead of "Magisk Manager → Uninstall → Restore Images"

- Reboot

-> OTA worked!!!!

- Then I rooted successfully with TWRP.

Now I have to wait for the next OTA....
[Google Pixel 3a Guides, News, & Discussion] koichirose:
My experience:

I was on rooted stock (June), never received an OTA. Even tried restoring images with Magisk, still no OTA.

Yesterday I received the July update (like many of you it seems... did Google decide we were worthy?). Auto update was turned off in developer setting, but it updated anyway and the system updater only showed "restart now".

Instead of rebooting, I installed Magisk to inactive slot, rebooted and I'm now rooted with the July patch.

I immediately received the August OTA (68 Mb), but this time it seems it's having trouble installing it - it simply says "Installation failed".

I'll try again a couple of times, then I'll try restoring images and installing to inactive slot again (as detailed in the Magisk tutorial).
[Google Pixel 3a Guides, News, & Discussion] sic0048:
I too had the "installation failed" error with the Aug OTA. I'm impatient, so I sideloaded it last night at home and then reinstalled Magisk using the TWRP method. It is super easy to do and doesn't take long at all.
[Google Pixel 3a Guides, News, & Discussion] bombadier:
Same story for me, the update keeps failing, as per the magisk ota instructions, magisk tells me restore done but its still installed and the ota update fails, off to sideload it like I have been doing up till now with previous updates
[Google Pixel 3a Guides, News, & Discussion] spiou:
I too just received the August notification update (first time I get the ota notification). I tried to restore stock boot before updating, but still no luck. Anyone has an idea ? Is google implementing new detection of root in recent update ? Maybe, we should hide some process with Magisk hide ?
[Google Pixel 3a Guides, News, & Discussion] pasha_d:
If OTA doesn't work as per Magisk guide ( I also ended up with sideloading August update), is there a way to truly disable system updater on rooted phone? Maybe some wakelock to tinker with?
[Google Pixel 3a Guides, News, & Discussion] koichirose:
I don't know why it didn't work for you. I restored images after the August OTA (as I said, I was having trouble installing it). It completed the installation without any issues. Then I installed Magisk to inactive slot and rebooted.

To recap and for future reference:

- have been on June patch since I got the phone (I rooted it the day I got it), never received an OTA update

- randomly received July patch on August 7th and it got installed successfully without me doing anything (weird)

- installed Magisk to inactive slot and rebooted

- right after rebooting, received August patch, this time it couldn't install it (saying "Installation Failed")

- restored images from within Magisk, installed the August patch correctly

- installed Magisk to inactive slot and rebooted
[Google Pixel 3a Guides, News, & Discussion] spiou:
Thank you for your feedback.

Is there anyone else who successfully updated the August patch with the Magisk procedure ?

I do not see what could be the culprit : except Magisk root, I am completely stock...
[Google Pixel 3a Guides, News, & Discussion] nxt:
I was on July with magisk, removed magisk. I manually installed august update ota. booted up twrp via fastboot, flashed magisk. phone dead. wants me to try again (booting) or wipe. I flash uninstall magisk and it boots up fine. so magisk isn't working for me to root august update.
[Google Pixel 3a Guides, News, & Discussion] Rudi154:
I was on August too, and rooting with twrp worked fine.

Maybe it depends on the twrp version:

I used 3.3.1-2
[Google Pixel 3a Guides, News, & Discussion] nxt:
Where did you get that version? On official TWRP page for Pixel 3a shows 3.3.1-1.

https://dl.twrp.me/sargo/
[Google Pixel 3a Guides, News, & Discussion] Rudi154:
I think from this thread a few weeks ago:

https://xdaforums.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413

But now I can't find a beta link.
[Google Pixel 3a Guides, News, & Discussion] ggibby:
Same thing happening to me. Tried several times, sometimes with the 'Installation paused' prompt (even though I'm not touching it),

but always resulted in the Couldn't update / Installation problem message.

Notable that the 'Installing security update...' screen looks like it should have a progress bar, but mine never moves, so I think it's not downloading the file, even though I'm on strong unmetered home wifi.

Reinstalling Magisk via direct install and rebooting worked, but I'm still getting the prompt to update, even with the Updates switch off in Developer Options.

Uninstalling FDroid didn't change the sequence or result, FWIW.
[Google Pixel 3a Guides, News, & Discussion] AutomaticFailure27:
I am a little lost on what I actually need to do to update correctly here

Currently I am under the June patch, installed with the prepatched image provided in OP

Trying to figure out the correct steps on how to get upto August. I want to prepatch the boot img for Aug, then install that way, but I don't see an option to do that in Magisk. Is it possible to get a prepatch image for August [MENTION=4396787]pbanj[/MENTION]?
[Google Pixel 3a Guides, News, & Discussion] Rudi154:
To patch a boot.img by yourself you have to tap on "install" (top right) > "install" > "select and patch a file"
[Google Pixel 3a Guides, News, & Discussion] AutomaticFailure27:
Dammit, I tried and somehow I messed it up and now I am stuck in the bootloader, can't get into the recovery at all to start over.

Well... this isn't how I wanted to spend my Friday night, but I am back, completely redone, lost everything... Time to start fresh I suppose
[Google Pixel 3a Guides, News, & Discussion] Wiebenor:
Ok... I have rooted and unlocked phones before, but when looking for information on different phones, I see that some phones have custom radios so they can only work on 1 network, and since I use a Verizon based network carrier, I was wondering what the difference is between buying a Pixel 3a from Verizon and Google, if there is one??? I want to buy one from Google, but I'm not sure how the whole cellular radio thing works... If I bought it from the Google store, would it have all the Verizon bands, and if so I would be able to bootloader unlock it, yes???
[Google Pixel 3a Guides, News, & Discussion] alphahere:
Don't buy the Verizon version it is bootloader locked. The Google version works fine on Verizon.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
If you used the pre-patched file, there are two ways to upgrade.

One is to sideload the OTA using ADB. This is probably the easiest option.

The second is to get the stock boot.img file from the June OS version and flash it, thereby removing root and the pre-patched file you used. Then will you be able to download and install the OTA via normal channels.
[Google Pixel 3a Guides, News, & Discussion] Wiebenor:
Lol!!! I know the Verizon version is bootloader locked, which is why I was wondering about getting one directly from Google??? now I just need to get someone to build a working Resurrection Remix rom I can put on it, if I buy one??? it is my favorite Rom after all... Speaking of, do all versions and variants of the pixel, sold in the Google store support Verizon??? I'm assuming yes, but would like clarification...
[Google Pixel 3a Guides, News, & Discussion] Velcorn:
I'm still in the position that Magisk won't backup stock boot.img when I patch it, thus preventing me from restoring stock boot.img in order to do an OTA update.

Any help on how to force Magisk to update the stock boot image?

Can I flash the current stock boot image and install Magisk over it?
[Google Pixel 3a Guides, News, & Discussion] Atiqx:
Pixel 3a OTA

Hello, i have rooted without any Problems with TWRP method

Today It showed up with the First new OTA For me and i followed your OTA Install Guide ,but every time i tryed to Install the OTA via System i get an error with "Installation Problem occured"

Need Help pls
[Google Pixel 3a Guides, News, & Discussion] sic0048:
For all those having problems updating (I did too), you can follow my guide . There is a section on how to sideload an OTA update. It is very easy and the result is the same as letting the phone update itself (ie it doesn't wipe your apps or data).
[Google Pixel 3a Guides, News, & Discussion] nxt:
So Magisk 19.3 latest stable does not work with August security update.

Tried flashing via twrp didn't work, tried patching the boot.img manually via Magisk Manager then flashing the modified boot.img didn't work.
[Google Pixel 3a Guides, News, & Discussion] Dixon Butz:
Worked for me. I sideloaded OTA today.

Extracted boot.img

Patched it with Magisk. And flashed with ABD. Def have root.
[Google Pixel 3a Guides, News, & Discussion] alphahere:
Yes the Google US store 3a works with Verizon.

See this thread for details.

https://xdaforums.com/pixel-3a-xl/how-to/pixel-3a-xl-models-t3931603
[Google Pixel 3a Guides, News, & Discussion] nxt:
Okay I'm going to reflash stock image and start from scratch.
[Google Pixel 3a Guides, News, & Discussion] kc6wke:
Had no issues with magisk 19.3 and August security update. Flashed using full firmware not OTA.
[Google Pixel 3a Guides, News, & Discussion] nxt:
Okay reflashing stock image and flashing patched boot worked on august.

Before I had july did magisk uninstall within the app, then flashed august ota. wouldn't work.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Sorry I've been mia. Been busy with irl stuff, haven't even gotten a chance to try twrp or any roms yet. But I can tell you that patching the boot.img most definitely creates the backup if you've used a prepatched image. Not only does it allow you to restore, but otas will work. I was finally able to confirm the ota part because I finally got the notification that it found one. I'll have the stock boot image up later today. I'm debating on even putting the prepatched ones up anymore as we have twrp now and there really isn't a need for them anymore.
[Google Pixel 3a Guides, News, & Discussion] Velcorn:
Had issues with Magisk 19.3 too. I sideloaded the OTA and Magisk would be stuck on updating. Maybe a reinstall of the app would've been enough, but I just went with Canary and that worked fine. Flashed it through TWRP.
[Google Pixel 3a Guides, News, & Discussion] ritchea:
Worked for me, too.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
main post has been updated. i shuffled stuff around, added actual twrp steps instead of linking to another thread, added a fully automated method for getting pay working, depreciated the pre-patched method as we have twrp now, and added the stock image for August.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
Well all you are trying to do by not allowing automatic updates is preventing it from rebooting. The only reason you are trying to prevent it from rebooting is to allow you the option of installing Magisk on the other partition before booting into it the first time.

So all you have to do if/when you see that message again is to go install Magisk - specifically the "Install to second/inactive slot (After OTA)" option. Then reboot and you should reboot into the other partition and have both the update and root.
[Google Pixel 3a Guides, News, & Discussion] zzumba:
I was on prepatched march and reinstalled stock boot for march.

I then used method 1 twrp + Magisk. When trying to uninstall Magisk (according to the Magisk update guide) it says "Stock backup does not exist" and does nothing.

What am I missing?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
That's weird as the zip should have backed up the stock boot image when flashing it. Use a root browser and go to /data/ and see if you see any stock_boot files like the attached pic
[Google Pixel 3a Guides, News, & Discussion] zzumba:
Nope, /data/ has only folder no images.

Edit:

https://1drv.ms/u/s!AvyuX8MsOU8yhUxRw6Y3x_Z4mVlQ?e=xqv61J

Here is the install log.

It says "Magisk patched boot image detected" but I installed stock image before twrp.
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Well that's weird, I wonder if it was a slot thing. Grab the stock boot.img for your current ver from the first post, have Magisk patch that image in the manager and then see if it will allow you to uninstall from inside the manager
[Google Pixel 3a Guides, News, & Discussion] sic0048:
It is probably best if you run the Magisk uninstaller zip in TWRP. This should remove all parts of Magisk. Then reinstall it via TWRP and I bet you will be OK.

EDIT - Actually probably the easiest solution is to simply sideload this OTA. This should remove Magisk during the process as well. Then simply install Magisk using TWRP again. By sideloading the OTA, you save a few steps and some time vs uninstalling and reinstalling Magisk and then taking the OTA and reinstalling Magisk again.
[Google Pixel 3a Guides, News, & Discussion] Drakax:
Flashing the August full firmware:

1. Method 1, twrp is showing 0mb internal storage without access to data. (twrp is not asking me any password at the beginning although I have one)

2. Method 2, flashing the magisk_patched_boot.img doesn't change anything although I got no error.

What should I do?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
ngl sideloading the ota is faster than having the built in updater do it.

what doesnt change?
[Google Pixel 3a Guides, News, & Discussion] zzumba:
That did the trick. After using the Magisk Uninstaller it properly did a backup of the stock image.

Still the OTA update fails after uninstalling Magisk according to the guide.

If I try to sideload it, the device will not be recognized by my Win10 when in recovery mode. Adb commands work fine when in the phone is booted.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
I also had trouble with the Aug update "failing" when trying to take the OTA. I ended up sideloading it. I use a Win10 machine as well and didn't have any connection issues. My only thought is to make sure you have the latest drivers on the computer. I think there is a link in the first post. It might be you are using a slightly older driver version and it isn't working correctly.
[Google Pixel 3a Guides, News, & Discussion] zzumba:
I am using the driver provided in the first post. Also tried some "clockwork" driver provided from google dev page. Both are not working when the device is in recovery mode. In recovery I only see the Android guy and it says "no command".

It behaves as if it isn't connected at all. I tried two different PCs and also did some google searching and found the same issue on older post that where never realy solved.

Just to make sure I am doing the right thing, because I never sideloaded an OTA.

adb reboot recovery

adb sideload "ota_image.zip"

Nothing more?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Read the main post..... I give you a guide on sideloading the update. You are missing a crucial step
[Google Pixel 3a Guides, News, & Discussion] zzumba:
Ah sorry, thanks for pointing that out. I accutually used the sideload guide from google and missed this step.

Nevertheless the recovery could not verify the image and aborted the update. I tried all of the images, none worked.

I then put everything back to stock and did normal OTA. (and here I thought a Google device would be easier to tinker with).

Anyway thanks for your support and the guides.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
Delete
[Google Pixel 3a Guides, News, & Discussion] pasha_d:
When you see Android on his back with the words No command underneath -

Press and hold the Power key and then press the Volume up key once while still holding down the Power key.

You should see the Android system recovery options pop up at the top of the screen. Use the Volume keys to highlight the options and the Power key to select the one you want. In your case "Update from ADB". At this point ADB would recognize your device and you can proceed with "adb sideload "ota_image.zip" command.