yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
[MENTION=5368702]avg2424[/MENTION] the short answer is: it's no longer possible to get r/w access to /system as system is mounted as root partition now. If you want to change anything on /system you need to bind mount overlays replacing the original content.
[Google Pixel 3a Guides, News, & Discussion] avg2424:
In Q only though, right?

I'm redoing my Pie (9) install because I found out I couldn't do so in Q (10)
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
Sorry, I misread that you are still on pie. Or did you probably downgrade from 10?

Edit: as you already were on 10 and you are downgrading, there is a chance that partition layout changed and now your phone mounts system as root. Just as a guess ...
[Google Pixel 3a Guides, News, & Discussion] avg2424:
I used a Q image and then learned about the system r/w and downgraded back to Pie.

So, on Pie, it should just work right? I can try formatting in twrp and reflashing the pie image if it should just work without anything special.
[Google Pixel 3a Guides, News, & Discussion] avg2424:
[MENTION=2188693]AndDiSa[/MENTION] I just wiped my system, data, and cache in twrp and reflashed the google image "9.0.0 (PQ3B.190801.002, Aug 2019)" and still can't write to the system.

I am able to write to the system in twrp. I even did a chmod 777 on the system and still can't write to it from Solid Explorer, I can't uninstall bloatware from Titanium.

Any other suggestions?

---------- Post added at 05:42 PM ---------- Previous post was at 05:11 PM ----------

Did you ever get this figured out?

I recently reflashed my phone and am having this exact issue
[Google Pixel 3a Guides, News, & Discussion] Archangel:
From what I have been told it is something that is not possible now to mount system as rw so trying to do it going forward wont work,,,kinda sucks but what do you do.
[Google Pixel 3a Guides, News, & Discussion] meazz1:
I looked and searched but did not find it.

What is "Q"?

I got the Pixel 3a today and this is the spec. Is it a Q?

Build# PQ3B.190705.003

bASE v. g670--00011-190411-B-5457439

Security patch July 5, 2019

Thanks
[Google Pixel 3a Guides, News, & Discussion] kc6wke:
Q is what everyone thought would be the next Os letter, but google just went with android 10 instead.

Yours is on android 9 or Pie
[Google Pixel 3a Guides, News, & Discussion] meazz1:
I rooted my Pixel 3a yesterday. The time I had the ph and the time I rooted it, the OS went from And 9.0 to 10.0.

Anyway, I followed Method#2 and it was smooth sailing.

How is it suggested to keep up with updates in the future?

Thanks OP!
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
The simplest method (for me) when a new OS version drops (and if custom kernels arent your thing) is to just redownload and patch the new boot.img and then flash the patched version. It literally takes 5 min max. You will have to unroot to take the OTA though unless you plan to manually flash it each month.
[Google Pixel 3a Guides, News, & Discussion] AutomaticFailure27:
I've been having decent luck doing the OTA sideload method, then patching the boot img and flashing ontop.
[Google Pixel 3a Guides, News, & Discussion] meazz1:
@ ctfrommn

@ AutomaticFailure27

Ok, let me see if I understood it correctly.

1. I'm on stock kernel rooted & running android build 10.0.0 (QP1A.190711.020.C3, Sep 2019

2. now I download the 10.0.0 QQ1A.191205.011, Dec 2019 and extract the "boot.img" and put it on my pixel

3. run magisk mgr which is already installed on my pixel and patch the boot.img (new file "patch_boot.img")

4. copy the "patch_boot.img" back to pc and run adb to write new image to correct slot

is this all I need to do?
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
Exactly this. Though I would start by just booting the new image to make sure all is well before actually flashing it.
[Google Pixel 3a Guides, News, & Discussion] meazz1:
How do I boot the image before flashing?
[Google Pixel 3a Guides, News, & Discussion] sic0048:
There is no need to specify a slot when flashing. In fact, by doing so you greatly increase the chance of messing things up. Simply use the "fastboot flash boot magisk_patched.img" command.
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
Depends on how you got to where youre at now. I cant flash any boot image via fastboot without specifying a slot anymore. This started after I clean flashed the November image.
[Google Pixel 3a Guides, News, & Discussion] mihaixp:
Hello guys,

I was on the November build. I have followed the guide here (https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation) exactly like I did the previous month and this time I got in a bootloop. :(

I got the "Cannot load Android system" message and I can only reboot the device (but it's in a continuous bootloop) or Factory data reset but I'm afraid this will delete my photos (I had no backup) or even brick my device.

I tried rebooting into recovery (not successful - so I cannot try and clear cache), I can only go into fastboot. Have also tried "Rescue Mode", doesn't seem to do anything. Can anyone help me please?
[Google Pixel 3a Guides, News, & Discussion] sic0048:
I'm sorry you find yourself in that situation, but I think you just proved my point (that is if you specified a slot when you flashed the Nov update).
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
I didnt specify anything. I just ran the flash_all script. And its neither here nor there to me, I just wanted to clarify this in case someone faced the same thing.
[Google Pixel 3a Guides, News, & Discussion] meazz1:
Here in the link I see option for Factory Images and Full OTA image files, what's the differences and which one do I use to exact the boot.imge file?

https://developers.google.com/android/images
[Google Pixel 3a Guides, News, & Discussion] sic0048:
To get the stock boot.img to use in the rooting process, you need to use the factory image (not the OTA). You download it to your computer and unzip the folder, and then inside will be another folder that will contain the boot.img.

The Factory image by default do a factory reset on your phone and will delete all data. However you can modify the script before running it to remove the "-w" command at the end of the script which is the wipe command that erases everything. You also need an unlocked bootloader to flash the factory images.

The full OTA images can be flashed on locked phones and will not normally do a factory reset. You flash these images using a method called "sideloading".

The end result is the same regardless of which version you flash.
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
You can flash the factory image and if you remove the -w within the flash-all.sh script your data will even not get touched.

I was in a similar situation last month and was able to solve it in this way.
[Google Pixel 3a Guides, News, & Discussion] meazz1:
For some reason I patched the Dec factory imaged but the touch did not work, I had the Sept image installed.

Execpt for the Dec every other imaged worked.

The ph boots all the way up and I can see my home screen with all the icons but I could not enter PIN or any touch on screen was unresponsive.

The Nov imaged works fine and that's what I have now.
[Google Pixel 3a Guides, News, & Discussion] mihaixp:
Thanks for the reply.

I did just that (installed drivers, downloaded latest platoform tools, deleted -w), everything seems to go smoothly, I only get OK's, no error in the logs. And the device reboots in the same manner and only stays in fastboot. :(

Are there any additional steps to this? Or it should just boot up correctly after running flash-all.bat with the -w deleted?
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
Well, in that case probably something with your data is causing the issue (an uninstalled Magisk module ?). I suppose you will need to wipe data as there is no custom recovery available yet to try anything different.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
Before you take the nuclear option of doing a full wipe, I would direct you to this thread. https://xdaforums.com/pixel-3a/themes/magisk-modules-disabler-booting-magisk-t3976621

It should walk you though how to create and flash a patch that will allow you to boot without any Magisk Modules being active. If it is a Magisk module causing the issue, this will allow you to use the Magisk manager to disable the modules or update them.

If that doesn't work, then doing the full wipe should get you back to an operating phone. I've never tried it (so I can't say it will work), but it might be possible to use the ADB "pull" commands to pull files off your phone before wiping it. This would help, especially with pictures, etc that you might want to save before doing the full wipe.
[Google Pixel 3a Guides, News, & Discussion] kodiak:
Updated to the latest OTA following Magisk instructions and now I keep getting a am alert "Google keeps stopping".

Any idea how to solve this?
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
I would just do a "normal" flash of the OTA and then if you need root just repatch the Dec boot.img. Ive never found the Magisk method of maintaining root through updates that simple or effective so I dont ever do it that way.
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
[MENTION=4110652]ctfrommn[/MENTION] for me it's the same: I always flash the original boot.img before taking the OTA update. After having that applied I am just flashing the new patched_boot.img and everything is working well.
[Google Pixel 3a Guides, News, & Discussion] meazz1:
I successfully rooted my device.

Only thing I'm not able work right is the GPay.

I followed the steeps in OP, put the file, changed permission and added the module in magisk.

I also enabled in magisk the hide option but no luck.
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
Pretty sure Gpay doesnt work on any unlocked device.
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
GPay is working with unlocked / rooted devices but you need to have Magisk hide and you need to modify some values in a database. There is a thread about this here in XDA.
[Google Pixel 3a Guides, News, & Discussion] ctfrommn:
Good to know, thanks. I havent tried Gpay for years as it was always a pita to get it working on unlocked/rooted devices.
[Google Pixel 3a Guides, News, & Discussion] Cancambo:
Try this module: https://github.com/stylemessiah/GPay-SQLite-Fix/releases

Source/instructions: https://xdaforums.com/showpost.php?p=80924511&postcount=718
[Google Pixel 3a Guides, News, & Discussion] nowster:
I can confirm this works for Google Pay. It didn't help that my bank's security systems locked the card due to too many consecutive Google Pay activations. A phone call to them fixed that.
[Google Pixel 3a Guides, News, & Discussion] mbk17:
I've been having issues booting with a patched magisk image after getting the OTA Android Q update for 3A XL. Looks like you guys have a solution for the 3A . Is there a way to implement it for the XL? Thanks
[Google Pixel 3a Guides, News, & Discussion] nowster:
If you have used a pre-patched boot partition you can't uninstall Magisk as the original partition image hasn't been backed up by Magisk. This is why that method is no longer recommended.
[Google Pixel 3a Guides, News, & Discussion] AndDiSa:
Well ... as long as you flash the original boot.img from the corresponding factory image everything is fine.
[Google Pixel 3a Guides, News, & Discussion] nowster:
Except you're not rooted any more if you do that. What you need to do is get back to stock that way using the boot.img from the old version, update, then use Magisk Manager to patch a boot.img from the updated version which you then flash. See the first post in this thread.
[Google Pixel 3a Guides, News, & Discussion] mbk17:
I did those steps but the patched img results in the phone being stuck with the Google logo or if I boot instead of flash it just reboots to fastboot mode and then starts up normally. There are some img's in the thread for people with my issue but I have an 3A XL and there are none of these img's in the threads on our forums. What is different with these img's compared to the one I patched on magisk so I can to fix this?
[Google Pixel 3a Guides, News, & Discussion] mspasov:
You have to check which slot is active for you and specify it in fastboot command line, t.i. flash the patched boot image to that slot

fastboot flash boot_a(or b) patchedimagename
[Google Pixel 3a Guides, News, & Discussion] mbk17:
I am aware and it was stuck at the Google logo when that flash command was used.
[Google Pixel 3a Guides, News, & Discussion] poudigne:
I used the Method 2 to try and root my phone. My bootloader was unlock and everything. I patched the boot.img. However, my build number in my phone was QQ1A.20191205. (I'm from Canada). So I decided to try anyway. But im in bootloop, everytime I try to start my phone it brings me to the bootloader.

anyone can help please ?

Edit : think I bricked my phone, i'm stucked in bootloader and computer can't detect the phone.
[Google Pixel 3a Guides, News, & Discussion] jmtjr278:
You have the December build. What boot.img did you try? Have you downloaded the factory images for December? If not, I would recommend downloading the January factory images and flashing those. Then patch that boot.img. Flashing whatever factory images you have should get you back up and running at the very least
[Google Pixel 3a Guides, News, & Discussion] Bramton1:
Out of curiosity, has anyone ever tried to patch the boot.img for an update, then replace the original boot.img for the update with the patched version, then run the update through ADB? Conceivably, couldn't that retain root through the update process? Or would there be a high risk of the update failing and bricking the phone?
[Google Pixel 3a Guides, News, & Discussion] HtHNightwolf:
I have tried to follow method 2. So I did the following:

- Enabled all recommended options

- Checked my Build: (Android 10), QQ1A.200105.002

- Downloaded the original firmware from google: bonito-qq1a.200105.002

- extract the boot Image and move it to the phone's Download folder: bootloader-bonito-b4s4-0.2-5736883.img

- Open Magist which updates itself to 7.5.1 and click "Patch a file"

- I choose the boot file bootloader-bonito-b4s4-0.2-5736883.img and get the following error:

Unsupported/Unknown image format

Installation failed.

Can someone tell me if I did a mistake and help me get root to the Pixel 3A?
[Google Pixel 3a Guides, News, & Discussion] bejunk:
You patch the wrong file. You need to patch the kernel (boot.img):

1. From your factory image extract the boot.img

2. Open Magisk and choose to patch the file

3. After it's done, you need a pc to flash the new kernel in fastboot. You can use the "minimal adb and fastboot" search it, its on xda

4. Connect phone in fastboot mode to pc.

Put the patched magiskboot.img in the folder where adb is

5. Open a terminal here and type: "fastboot flash boot magisk.img" > replace "magisk.img" with the filename of your patched file, dont forget the .img at the end

6. After its done, "fastboot reboot"

7. In most cases you don't need to specify the boot slot etc. Just use those 2 commands.

8. After the bootup open magisk, should be done now.
[Google Pixel 3a Guides, News, & Discussion] HtHNightwolf:
Thanks! That was the hint I needed. I ran into different issues but I am still trying. No final success yet, will keep you updated.
[Google Pixel 3a Guides, News, & Discussion] HtHNightwolf:
Okay, I made a mistake. I did not understand that there were so many different Google Pixel types and installed the wrong Stock Rom. I tool a bonito but I would have needed sargo.

To flash Sargo I have to use sideload.

That left me with a problem:

- USB Debugging state: unknown

- the sargo firmware has no batch, no ISOs, nothing that I have ever seen. It is a strict zip to be loaded via sideload.

- When in recovery, my computer (windows) recognizes no phone. I mean, not a driver issue, there is literally no device being addes in Device Manager when I attach it in Recovery.

What can I do now? As far as I understand, in Recovery I should have the phone show up in the device manager. Get a driver and blabla ...

Without that feature, I can not install a sargo Firmware. But I can not install another Pixel firmware aswell, if I do, they boot up but no tough works. So I can not get to the USB Debugging options.

Does anyone have any ideas on that situation?
[Google Pixel 3a Guides, News, & Discussion] HtHNightwolf:
Done!

I figured it out. I had to put the phone to recovery mode, it said "No command". I had to use this guide to get to the sideload option.

After I flashed the stock image, I had to extract the boot.img from the payload.bin following this guide. Then I could continue: Patch it with Magisk, flash it with fastboot an Voila ... Root :)
[Google Pixel 3a Guides, News, & Discussion] jobe3101:
Managed to update to Q by mistake when the popup saying my system was out of date, now I've lost root and if I try to flash a patched magisk image it's just stuck on the google logo during boot.

I was having the same problem when I upgraded between pie versions and if I remember right all I had to do was temp boot into twrp and flash magisk uninstaller, but now theres no working twrp.

Any ideas?
[Google Pixel 3a Guides, News, & Discussion] LowTier:
Just got an open box 3a for a great deal from Bestbuy. Try to oem unlock and it's greyed out. Check MEI with Verizon BYOD and it's a Verizon version. Am I screwed?

And the box isn't the verizon box... thanks Bestbuy
[Google Pixel 3a Guides, News, & Discussion] bejunk:
Yes. As of now, there is no method to unlock Verizon version afaik.

You should RMA it. I mean, you got the wrong product? You could just state you're a dev and need it to be unlockable.
[Google Pixel 3a Guides, News, & Discussion] sic0048:
You will never be able to bootloader unlock that phone, so yes you are screwed in that sense.

BUT.......

The fact that the box isn't for a Verizon version should be your saving grace. Take that thing back to BB and demand a refund because you did not get the product you thought you were buying. It's deceptive or false advertising and they should be very willing to take it back. They may not initially understand the difference between the two devices, so don't get mad if they initially say no, but definitely demand to speak to a manager and calmly explain the differences to them. In the end, don't take no for an answer because you are clearly in the right here.
[Google Pixel 3a Guides, News, & Discussion] dex4k:
Thank you for putting all this info together, OP. Works perfectly. I have my Pixel 3a rooted and everything (Gpay etc) works as it should.
[Google Pixel 3a Guides, News, & Discussion] LowTier:
I talked to online chat and they told me to go in store. I went to the store and they can't do anything about the automatic restock fee and told me to call online. I'm gonna have to go and do that when I reorder. Is there a color that's exclusive to Google store so I don't get another Verizon version from Best Buy? Verizon doesn't have a white color on their website, but I don't know if that's because they're out of stock or if it's a google exclusive.

Edit- Best buy phone cust service sent me a new phone. Got it today and it's a pixel 3a XL lmao
[Google Pixel 3a Guides, News, & Discussion] dkryder:
i understand the method of applying the ota when using magisk. however my phone has not yet been served the ota so i'd like to try the sideload.. i'll add that i use elementalx kernel. so i'm guessing if i do the magisk restore images that will restore the original stock kernel. is that correct? so at that point i can reboot ? then i boot to recovery and do the adb sideload which will apply the feb patch. then i can patch the feb kernel using magisk and flash that which will give me root on the feb update. this is the steps i have in my head but i'm asking the forum if there is another better way before i do anything. thank you for any advice.
[Google Pixel 3a Guides, News, & Discussion] amd_h4x0r:
Download Feb factory image, extract boot.img, transfer to phone, patch with magisk, transfer patched img back to computer.

Download Feb OTA image, boot into recovery, adb sideload OTA image, reboot to bootloader, flash patched boot image to other slot.

Then install elementalx kernel using their instructions.
[Google Pixel 3a Guides, News, & Discussion] dkryder:
Ok. Thank you.
[Google Pixel 3a Guides, News, & Discussion] kodiak:
Hi.

The February ota died not show up when I search for updates.

Any way to force it to show?
[Google Pixel 3a Guides, News, & Discussion] nowster:
Not really. Most of the instructions you'll find online are snake oil and possibly harmful.

The most reliable way at the moment is to use the instructions above and apply the full OTA from Google's website, and then patch the boot.img using Magisk, and flash that. (See instructions in first post in this thread.)
[Google Pixel 3a Guides, News, & Discussion] shtewps:
Hi all,

Rooted using method #2 without a hitch while I was on the Jan update. Now I'm looking to apply an OTA. So I restored my boot with Magisk and proceeded to check for updates however I keep getting prompted with "Your system is up to date ... January 1 2020".

No idea why it can't see any OTAs.

Any insights here?

Many thanks.
[Google Pixel 3a Guides, News, & Discussion] IVIetalMilitia:
Same situation. What is the best option for retaining root and applying the current update?
[Google Pixel 3a Guides, News, & Discussion] sic0048:
The only real option is to sideload the update. You loose root during this process, but it's simple to get it back using the normal root method.
[Google Pixel 3a Guides, News, & Discussion] captain sideways:
Can confirm this is the way to do it. Did this yesterday with the April update and it worked like a charm. I've noticed that there's not really much happens in /pixel-3a on here but most of the information, like this method, is usually spot on ?
[Google Pixel 3a Guides, News, & Discussion] pbanj:
Sorry for not uploading the images and kind of being mia. Life's been hectic. I've updated the first post so it is more future proof and added a snippet about how I personally handle my updates as it's faster than doing it by the normal ota method.
[Google Pixel 3a Guides, News, & Discussion] OryZ:
Thanks again!

Just wanted to write another thank you... I always come back to this thread and it always has all the information I need. In this case, I lost root after accidentally touching the update notification :silly:

But phone is now updated to latest and running with Magisk and Google Pay :good::good::good:
[Google Pixel 3a Guides, News, & Discussion] gunnerrrrr:
When trying to flash the patched image I get the error

FAILED (remote: Not allowed to flash (boot_2))

I used the command

fastboot getvar current-slot

to find the correct slot.

Yes, my bootloader IS unlocked. When I restart, I get the warning prompt of my bootloader being unlocked.

10.0.0 (QQ3A.200605.002) with Windows 10
[Google Pixel 3a Guides, News, & Discussion] GrandMstrBud:
C:\platform-tools>fastboot flash boot_"slotb" magisk_patched.img

Sending 'boot_slotb' (30392 KB) OKAY [ 0.768s]

Writing 'boot_slotb' FAILED (remote: 'Not allowed to flash (boot_slotb)')

fastboot: error: Command failed
[Google Pixel 3a Guides, News, & Discussion] infectedorganism:
fastboot flash boot_b magisk_patched.img
[Google Pixel 3a Guides, News, & Discussion] GrandMstrBud:
Thanks, I ended up going back to android 9 just to get root. Can I update to 10 and keep root by removing the -w flag in the flash-all.bat file?
[Google Pixel 3a Guides, News, & Discussion] infectedorganism:
I've had this phone for less than a week, so I'm the wrong one to ask. Hopefully someone will be along to give you a definitive answer.
[Google Pixel 3a Guides, News, & Discussion] GrandMstrBud:
I just got the Pixel 3a, have the 3XL and had that forever but can't remember exactly what it all took. Your right someone will be able to. I'm pretty sure I can but not 100%.