yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
Same here when flashing in ADB - does the sending file just fine, but I get that error when it gets to the writing part. On October update of Android, latest platform tools.

EDIT: So I downloaded the latest adb & fastboot and put them in the right folder (durr), and used stable Magisk with v20, and that fixed the issue. Which change was the actual fix? The world may never know...
[Google Pixel 3 Guides, News, & Discussion] PuffDaddy_d:
This worked perfectly to update my pixel 3 from Android 9 to Android 10, and then to the October patch, all via OTA. No more downloading images, extracting files, patching boot loaders, etc. Plain and simple! Thank you for sharing this. Way easier than the OP method. ??
[Google Pixel 3 Guides, News, & Discussion] Pete02:
Worked beautifully for me as well! ? This should definitely be stickied somewhere.
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
So, I'm guessing having something like Adfree that has modified a hosts file in /system (while I was on 9, it isn't working properly on 10) is going to prevent OTAs, rendering this process invalid, correct?
[Google Pixel 3 Guides, News, & Discussion] Chezbel:
Not sure of the differences between Adfree and Adaway, but I used the above method without any problem and I use Adaway.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
If you enable systemless host files in magisk settings you should be ok with either adfree or adaway. If you don't neither will work. See the magisk tutorial on how to take an ota.
[Google Pixel 3 Guides, News, & Discussion] burduli:
Worked great on my Pixel 3. Keep in mind that Magisk Manager has now been updated to stable 7.4, so it fully supports Android 10.
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
Worked perfectly here, thanks!
[Google Pixel 3 Guides, News, & Discussion] _litz:
Doesn't work for me ... there is no "install" option in Magisk Manager, to patch the boot image.
[Google Pixel 3 Guides, News, & Discussion] bush911:
It is supposed to be there:

Press Install → Install → Select and Patch a File,
[Google Pixel 3 Guides, News, & Discussion] scooter1979:
Not to hijack this thread (in fact, I've been discussing it over here: https://xdaforums.com/showthread.php?t=2252747), but Adfree isn't working on 10, at least on my Pixel 3. Magisk systemless doesn't seem to have any effect to get it working. The dev is aware, I'm hoping for an update. If you've got any suggestions I (and I'm sure the Adfree developer) am all ears.
[Google Pixel 3 Guides, News, & Discussion] kulparsan:
Works perfectly thanks. Nov 5 OTA update failed to install from update manager. Is there a way to apply OTA update without losing all data ?
[Google Pixel 3 Guides, News, & Discussion] Pete02:
Try this. https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
[Google Pixel 3 Guides, News, & Discussion] ibolito:
Just updated the 1st post and removed the part with Canary magisk because stable magisk is doing the job now.
[Google Pixel 3 Guides, News, & Discussion] BillyTheBull:
Unfortunately, with the latest (Nov) security patch something seems to have changed. It seems to me as if Google has recently decided to start ignoring the disabled "automatic system updates" toggle in developer options and will try to apply updates on its own terms; I have that setting disabled, of course, but today I woke up to a message of "system update failed", which shouldn't have happened on its own. Subsequently I tried the proven Magisk A/B procedure; unfortunately, not only did the OTA fail to install again, but - what's worse - upon rebooting, Magisk also seems to have failed to (re-)install, at least in my case. So, now I'm stuck without root/Magisk and without the latest security patch. Ugh. :crying:

Has anyone had the same issue and/or found a workaround of any kind?
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Download the full nov. factory image. Edit the flash-all batch file in it to remove the -w (make sure you save it). Run it. Copy the boot.img from the factory image to your device and patch it with magisk. Move that to your pc and flash it with fastboot.
[Google Pixel 3 Guides, News, & Discussion] BillyTheBull:
Done, thanks!

I was actually able to "take" the OTA on the third try ------- come to think of it, I may have caused the problem myself by accidentally rebooting from the OTA update-prompt rather than the Magisk reboot-button. I'm not a hundred percent sure ... but I think I totally did that, like an idiot.

In any case, I would appreciate feedback from others who may have tried it and succeeded (or failed); just so I know whether I caused the issue, or whether the A/B procedure indeed no longer works. Either way, I'm finally on the latest patch and re-rooted, so it's all good!
[Google Pixel 3 Guides, News, & Discussion] jd1639:
You are still able to use magisk to restore the stock boot image, take the ota, and then root with magisk. You just need to be careful when you reboot.
[Google Pixel 3 Guides, News, & Discussion] puma3u:
Pixel launcher crashes

I followed all the steps without any issues, but when I reboot after flashing the patched boot image and unlock my phone the pixel launcher just keeps crashing. Any ideas on what's happening?
[Google Pixel 3 Guides, News, & Discussion] BBobby:
It appears as if Magisk Hide does not work for Google Pay in this Nov 5 security patch. It was working for me in October. Any workarounds?

Thanks!
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Are you using the rest of the steps in this thread or just hiding GPay? https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Google Pixel 3 Guides, News, & Discussion] BBobby:
no i had not. THANKS! It now works. i dont use mobile pay much, but for those "i forgot my wallet moments" it is a marriage-saver
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Excellent. Glad it's working for you.
[Google Pixel 3 Guides, News, & Discussion] Vinotas:
Hello All,

I just got a new Pixel 3a with Android 10 and have been enjoying it for several weeks on T-Mobile. So now it's time to root it. A few (partial noob) questions:

will the instructions in Post 1 work with the 3a? I've searched but can't find a separate forum for the 3a, so apologies if I missed something;

will I lose T-Mobile's Wifi calling? I seem to recall this is more an OS thing than a root issue but just want to make sure it doesn't disappear;

I've read through parts of this thread but I'm curious if we'll still get OTA updates and if doing so will unroot the device?

where can I find instructions on how to extract the boot image? I downloaded Blueline to my phone and when I unzip it I don't find a boot.img file, but there is a bootloader-blueline....img file;

Thank you in advance, and thanks for the instructions on rooting this great phone.

Cheers! :cool:
[Google Pixel 3 Guides, News, & Discussion] jd1639:
I don't have a 3a but would think the same procedure to root would apply. After you've unzipped the factory image you'll find another zip file in there. Unzip that too and you'll find the boot.img.

OTA's won't work while you're rooted but you have two ways to update. One is to download the full factory image and edit the flash-all batch file in it to remove the -w you'll find in it. Run that batch file to update. Then you'll need to patch the boot.img again to root. Or, you can unroot with magisk, take the ota, root again with magisk, then reboot the device. Don't reboot until you've completed the process. There is a magisk tutorial for this process.
[Google Pixel 3 Guides, News, & Discussion] Pete02:
I don't think you should be using a Blueline factory image. The 3a is listed as Sargo.
[Google Pixel 3 Guides, News, & Discussion] Vinotas:
Any clue where to find that? There doesn't seem to be a dedicated 3a forum so I apologize for all the noob questions. Also, once I download it and extract its boot.img, will the procedure be the same? There are multiple YouTube videos showing how to root the 3-series Pixel, but none specifically for the 3a.

I just don't want to brick my new toy.

Cheers!
[Google Pixel 3 Guides, News, & Discussion] Pete02:
Just Google 'Pixel factory images' and scroll down till you get to the 3A. The procedure will still be the same. I did this same procedure for my bros Pixel 2 and it worked just fine.
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Only thing I will mention is please put adb/fastboot into your path. There really is no reason to be stuck sticking things in the same folder as they are in. If you set it in PATH, then wherever you run command prompt from will be where it reads files or pulls files. Makes life easier.
[Google Pixel 3 Guides, News, & Discussion] eneka:
looks like it's not working for december update. Pixel 3, magisk canary build.
[Google Pixel 3 Guides, News, & Discussion] schalacker:
Just updated my wifes & my P3 with the December update and used the same Android 10 root process on both. Worked like a charm. Just make sure you're running the latest platform tools (r29.0.5)

Download blueline Factory Image

extract Dec Factory zip file to its own folder on PC (windows 10 for me)

edit the "flash-all.bat" and remove the "-w," save, close editor

open factory image sub-zip (image-blueline-qq1a.191205.008) to extract the "boot.img," upload that to phone running latest Canary Magisk

open MM and "install magisk" with the "select and patch a file" method. Use the uploaded Dec "boot.img" file uploaded from the previous step

take the newly created "magisk_patched.img" file off phone, transfer it to the pc in your same Dec folder

adb reboot bootloader

fastboot devices (sanity check)

flash-all.bat make sure it runs to completion & reboots fully to system

make sure the Dec update took in "Settings/about phone/build number""

adb reboot bootloader

fastboot devices (same sanity check as always)

fastboot flash boot magisk_patched.img

fastboot reboot

go to MM and make sure you're rooted
[Google Pixel 3 Guides, News, & Discussion] kkjb:
I did a both slots Full flash (wiped) of dec images and I tried both canary release manager, Manager v7.4.0. Didn't work.

Edit 1: Wrong tried again, working fine Ignore.

I was on a working rooted Nov. I did notice a lot more file structures being written during the Dec install. So I am guessing the different file structures will require some patience for Magisk Dev's to correct. Welcome to 10, it is a moving target.

Edit 2: Now it could have been hadn't allowed magisk canary to check for something on wifi. Had nothing on just a first system start, install try.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
OK, root worked on my wife's P3. Canary 7.4.1-72edbfc4 (260) Manager an 20.2.72-edbfcr (20108) Magisk after flashing patched. Both show up to date. Install was a hyrbrid of flash-all and OTA. Still nobody seams to have found a reason why the flash-all (no -w) fails in fastbootd at product, but if you then switch to recovery while still on and then ADB sideload the OTA all is fine. 29.0.5 platform tools of course.
[Google Pixel 3 Guides, News, & Discussion] schalacker:
Successfully updated 2xP3s with the Dec factory image. I was running MM 7.4.1 (260) and Magisk 20.2 (20108) with platform tools r29.0.5 when patching boot.img and updating. Updating from a rooted Nov package successfully updated with the same method.
[Google Pixel 3 Guides, News, & Discussion] kkjb:
"Sanity Check" so after full flash_Both slots_ Dec very last night---my excuse--- failed to get past red "?" on install button. Had not enabled wi-fi just tried root from first start up. So gave up and did "set up new device data transfer" and tried this morning. Of course it worked just like its supposed to. So ignore my mistake in previous post.
[Google Pixel 3 Guides, News, & Discussion] Incanity:
can't get it to work. Flashed the december update to both slots, and flashed a (tried both stable and canary) patched boot.img to the active slot. It still won't boot. It shows me a google logo and a moving bar beneath it, but I can't get it to boot any further.

Tried disabling all modules with the adb command 'adb wait-for-device shell magisk --remove-modules' but it didn't work either... Does anyone have any idea what's wrong here? There must be something I'm missing here... :|
[Google Pixel 3 Guides, News, & Discussion] arktay:
Same thing is happening to me. I updated platform tools and tried with magisk stable and canary but after i flash the patched boot img file i get a bootloop :/
[Google Pixel 3 Guides, News, & Discussion] Serial Kazama:
Magisk canary dont work by me either with Dec OTA. Bootloop after flashing the patched IMG.
[Google Pixel 3 Guides, News, & Discussion] arby80:
Tulsa has a magisk module disabler that will allow you to boot with root on the December build if you are getting a boot loop . He has one in the Pixel 3XL thread that worked for my Pixel 3.
[Google Pixel 3 Guides, News, & Discussion] Incanity:
great tip, thanks, I'll try! :)

EDIT: Worked! Booted into the patched boot.img from Tulsadiver's thread and after that booted into the magisk patched img (from the canary channel), installed magisk, all the modules and presto! I'm rooted again.

Thanks again for the tip!
[Google Pixel 3 Guides, News, & Discussion] Pete02:
Pixel 3 here. I just followed this guide and took the OTA Dec build with no troubles. https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
[Google Pixel 3 Guides, News, & Discussion] bush911:
Tried restoring the factory image, but it said factory boot image does not exist.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
You were lucky. I followed the same guide and boot looped. I tried all the fixes I could find on XDA, and finally wound up wiping the phone. I haven't tried to re-root yet.
[Google Pixel 3 Guides, News, & Discussion] Pete02:
Well... I got lucky twice then cause I used the same guide on my bro's Pixel 2 and it worked just fine. (They're both Google unlocked phones. I'm not sure if that makes a difference.)
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Dec is definitely rootable. The problem seems to be magisk modules you might have installed. Remove modules before you root and you shouldn't have any problems.
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
I don't think it is related to modules. I've try from a brand new fresh installation of December Rom, with just magisk installed and nothing else. I've been stuck too...

I also try installing October, root, update and root again and stuck again.

Fastboot wrote something about the wrong boot image, even flashing the stock boot image and can't get my phone to open, needed to install the package from Google to made it work again.

At least, with -w remove, it was fine to boot.
[Google Pixel 3 Guides, News, & Discussion] Skysurfer77:
Same for me. Worked like a charm. :good:
[Google Pixel 3 Guides, News, & Discussion] Mawtin:
Rooted Dec with Magisk stable following OP's guide. No issues
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
I missed the first step (Remove Magisk modules) when trying to take the December OTA and am stuck on an "Android Recovery" screen that says: "Cannot load Android system...". I haven't been able to find [MENTION=5346465]Tulsadiver[/MENTION] patched boot.img in his XDA Pixel 3XL thread other than one that's from July 15. Is that still the one to use? I didn't have any problems with this method when updating to the November OTA.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
[MENTION=5346465]Tulsadiver[/MENTION] thread on this is at https://xdaforums.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433

Unfortunately, it did not fix my bootloop due to the December update - I had to wipe the phone twice to resolve it.
[Google Pixel 3 Guides, News, & Discussion] Tulsadiver:
For December

https://www.androidfilehost.com/?fid=4349826312261654031
[Google Pixel 3 Guides, News, & Discussion] Tulsadiver:
Try booting this one

https://www.androidfilehost.com/?fid=4349826312261659814
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
Thanks for your prompt reply!!!

No joy, Still have the Android Recovery - Cannot load Android system. Your data may be corrupt... screen after flashing.

Here's the flash log;

PS C:\Users\aquil\Desktop\Dec Platform tools> .\fastboot devices

89QX0DNUB fastboot

PS C:\Users\aquil\Desktop\Dec Platform tools> .\fastboot boot "C:\Users\aquil\Desktop\Dec Platform tools\image-newpixel3Remove.img"

Sending 'boot.img' (30208 KB) OKAY [ 0.726s]

Booting OKAY [ 5.766s]

Finished. Total time: 6.561s

PS C:\Users\aquil\Desktop\Dec Platform tools>

I haven't been able to find how to flash to both partitions, etc. Would that possibly help?

---------- Post added at 04:21 PM ---------- Previous post was at 04:03 PM ----------

I now see that on the Fastboot Mode screen on the phone it says "Enter reason: no valid slot to boot".
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Use "fastboot --slot all ......" to flash both slots. "fastboot --slot other ......" will flash the non-current slot. The current active slot is flashed if there is no --slot option specified.
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
Thanks [MENTION=5346465]Tulsadiver[/MENTION] and [MENTION=7423542]dcarvil[/MENTION]). I set "A" active (was on "B" during all this) and it boots to the "G" screen and hangs. Would it be worth trying to flash the "image-newpixel3Remove.img" now that I'm on "A" before starting from scratch?

(I REALLY don't want to wipe!!!)

Log:

PS C:\Users\aquil\Desktop\Platform Tools NEW\platform-tools> .\fastboot --set-active=a

Setting current slot to 'a' OKAY [ 0.370s]

Finished. Total time: 0.441s

PS C:\Users\aquil\Desktop\Platform Tools NEW\platform-tools> .\fastboot reboot

Rebooting OKAY [ 0.054s]
[Google Pixel 3 Guides, News, & Discussion] Tulsadiver:
Certainly wouldn't hurt. Only you can determine if it's worth it.
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
I'd try flashing tulsadiver's remove image. If that doesn't work, try flashing both slots. I don't know what my advice is worth, though. I had the bootloop problem with the Q December update, and had to wipe the phone after trying everything else.
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
Nope, bootloop on it also. Guess I'll have to look into wipe/reinstall. Any good threads/instructions to follow? BTW, I'm 78 yo and getting too old for this s**t! Thanks for trying!
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
There is a lot of good info here. https://xdaforums.com/pixel-3/how-to/complete-pixel-3-how-to-guide-newbie-t3922269

I had to run flash-all.bat with the wipe option twice to get out of my bootloop situation. It failed the first time (don't remember the error), but worked the second time.

Good luck.
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
Must have been lucky to try one last thing before collapsing. I flashed the Dec. image (not OTA) to the "A" partition with the "flash-all" command. It spewed out several screens of the process and took over three minutes, but it's up and running. Just need to install Magisk and never touch it again <G>. Thanks again for all the help!

One last (I HOPE!) question:

Magisk Manager says Magisk is not installed. Under "Select Method" are "Download Zip Only" and "Select and Patch a File". I'm too tired to start over again if I screw it up (again) now...
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
You are at step 4 of the original post in this thread. If you have already uploaded boot.img to your phone, "Select and Patch a file", then download the patched file to your PC and continue with step 5.
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
I'm losing my mind (and my patience). I downloaded the Dec. Blueline factory image to the phone, extracted the boot.img (boot.img -67.11 MB), did the "select and patch a file" in Magisk, got "magisk_patched,img (30,196 KB). Flashed with this result:

PS C:\Users\aquil\Desktop\Dec Platform tools> .\adb devices

List of devices attached

89QX0DNUB device

PS C:\Users\aquil\Desktop\Dec Platform tools> .\adb reboot bootloader

PS C:\Users\aquil\Desktop\Dec Platform tools> .\fastboot flash boot "C:\Users\aquil\Desktop\Dec Platform tools\magisk_patched.img"

Sending 'boot_a' (30196 KB) OKAY [ 0.822s]

Writing 'boot_a' OKAY [ 0.469s]

Finished. Total time: 1.560s

PS C:\Users\aquil\Desktop\Dec Platform tools> .\fastboot reboot

Rebooting OKAY [ 0.046s]

Finished. Total time: 0.061s

AND... go into Magisk Manager (7.4.1) and it shows "Magisk is not installed". I've tried twice with same results.

GRRRRRRR.... WHAT AM I MISSING??? (and thanks for your support!)
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Are you booting from slot A? It should tell you what slot is booting at the bottom of the boot screen of the phone.
[Google Pixel 3 Guides, News, & Discussion] bbxs:
Hi, I have a problem with the wifi and magisk (sw December).

If I flash the boot modified by adb, I have root, but the wifi does not work.

If I restart the phone, I lose root and the wifi is ok.

To have root I have to patch the modified boot.img again, but I am the same, or root or wifi :(

I have flashed other valid boot for December and the same thing happens to me.

How can I fix it, and have magisk root and wifi?

Why if I restart I lose root?

Thank you very much
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
I assumed that since it flashed the boot.img to Slot A that it would reboot into Slot A. Not seeing anything on the bottom of the screen when I do a restart, are you talking about when it's rebooting after flashing the image? Should I try "Fastboot --set-active = a" before flashing the modified boot.img although that must be where it goes?

I'm considering rebooting into slot B to see if it's hosed and hosed and hope that I'm able to reboot the current slot A.

Sure is a lot different than the G-Nex I started flashing on...
[Google Pixel 3 Guides, News, & Discussion] dcarvil:
Sorry, it is the fastboot screen that says what slot will be booted, not the regular boot screen. You can go to the fastboot screen, see what slot is booted, then select "start" from the fastboot screen to boot. Make sure the boot slot is the same slot you flashed.
[Google Pixel 3 Guides, News, & Discussion] AquilaDroid:
I started from the beginning, checked the checksum for the December Blueline zip, extracted the files again, did the Magisk select and patch file routine, result was exactly the same. magisk_patched.img is 30,196KB. Still flashing to Slot A

Log: (same as before)

PS C:\Users\aquil\Desktop\Dec Platform tools> .\fastboot flash boot magisk_patched.img

Sending 'boot_a' (30196 KB) OKAY [ 0.801s]

Writing 'boot_a' OKAY [ 0.479s]

Finished. Total time: 1.540s

PS C:\Users\aquil\Desktop\Dec Platform tools> .\fastboot reboot

Rebooting OKAY [ 0.046s]

Finished. Total time: 0.054s

PS C:\Users\aquil\Desktop\Dec Platform tools>

Start Magisk - "Magisk (20.1) is not installed. Magisk Manager is up to date - Installed 7.4.1 Latest 7.4.0

Are there any problems with 7.4.1?

Would it be worth trying to flash the "image-newpixel3Remove.img" again?
[Google Pixel 3 Guides, News, & Discussion] Pakabidu:
Thanks for the tutorial, worked great.

The only thing I never seem to be able to make work is google pay. I get "Couldn't finish setup to pay in shops. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way". I was getting this message since my first root in March. Shame, great feature when it worked... Otherwise - vanced, adaway - all good :)
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

This work flawless! ;)
[Google Pixel 3 Guides, News, & Discussion] Pakabidu:
Certainly does! Big big THANK YOU :highfive: