yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Guides, News, & Discussion] teapea:
Aha good spot - sounds like the issue we're having. I'll wait until it's out in the normal beta as I don't really need to hide my manager.
[Google Pixel 3 Guides, News, & Discussion] RootTheMachine:
Is anybody successfully able to generate their own patched boot image, or is everyone just using the provided one for the XL? If so, why doesn't it work for some of us?
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Are you flashing both boot slots? What version of magisk are you using.
[Google Pixel 3 Guides, News, & Discussion] RootTheMachine:
Looks like the latest stable, which may be the issue if the beta/canary is needed. No, I am not flashing both slots, nor do I have to when using the linked boot.img for the 3 XL. I also tried flashing from TWRP, this also produced a boot.img that wouldn't boot.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Yeah, you need 17.3. I think it's still under beta. You can go into magisk settings to use the beta version.
[Google Pixel 3 Guides, News, & Discussion] furrypotato:
I got it working using beta first time . Allowed me to have a go at getting Call Screening working in the UK, which was almost successful , but I still have to set language to US English.
[Google Pixel 3 Guides, News, & Discussion] cambunch:
Anyone been able to get Magisk installed after flashing to the latest November update? It is bootlooping for me...
[Google Pixel 3 Guides, News, & Discussion] dethknite:
Same here.. tried patching it manually still no go.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Mine worked fine. Removed -w, ran flash-all, booted, extracted boot.img and pushed it to sdcard, ran MM and let it patch the image, pulled patched_boot.img, booted to bootloader and flashed it to boot_a and boot_b, rebooted. Everything is working fine.
[Google Pixel 3 Guides, News, & Discussion] oryanh:
Someone want to try the Nov Patched 3 XL boot.img?

-nevermind, looks like its working.
[Google Pixel 3 Guides, News, & Discussion] cambunch:
Odd, I did exactly that and it won't boot. Also tried flashing TWRP and flashing the Magisk zip, still a no go. Can you share your patched_boot.img so I can try it?

That didn't work for me. Must just be something on my side.
[Google Pixel 3 Guides, News, & Discussion] dethknite:
Yea.. me too. I have done this for years.. Pixel and Pixel 2... something is off. Perhaps if I flash the Sept. back on and OTA it instead of flashing the factory image... it feels to me like it has something to do with the switching A/B.
[Google Pixel 3 Guides, News, & Discussion] tysj:
Magisk is force closing for me right when I select the boot image to patch.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Patched November Pixel 3 boot.img:

http://www.brasskeysoftware.com/etc/patched_boot.zip
[Google Pixel 3 Guides, News, & Discussion] oryanh:
Thanks, That worked for me.
[Google Pixel 3 Guides, News, & Discussion] tysj:
Thanks for this - worked great. Not sure why it's so temperamental between different users.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Just noticed I had to clear Play Store data to get it to say my device was certified again after installing the Nov update and Magisk again. I guess maybe that's normal? Not sure. I was running LOS and Magisk for so long on my previous Nexus, and it was so seamless and painless, that I've forgotten what it was like on stock Android.
[Google Pixel 3 Guides, News, & Discussion] cambunch:
For those of you still having issues getting the November update to boot with a patched image, give this a try. Note that it will uninstall all of your Magisk modules and Magisk settings, so you will have to restore them when you're done.

- Flash stock November boot.img to both boot_a and boot_b from the stock image, or download just the stock boot.img

- Copy the latest Magisk Uninstaller .ZIP to your phone from this thread

- Boot (don't flash) the latest TWRP .img file from here

- Enter your PIN in TWRP (if you have one), then flash the Magisk Uninstaller .ZIP

You should now be able to reboot back into your OS with no issues, and install Magisk either via patching the stock boot.img and flashing via ADB, or installing TWRP and flashing Magisk with the latest .ZIP

This seems to be caused by the Active Edge module for Edge Sense Plus. I would avoid updating OR remove this module before updating until the developer has fixed the issue.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I don't have any modules installed. Maybe that's why it worked for me?
[Google Pixel 3 Guides, News, & Discussion] cambunch:
Yes, seems to be caused by the Active Edge module for Edge Sense Plus.
[Google Pixel 3 Guides, News, & Discussion] Archangel:
Yeah, Active Edge Module will def cause a bootloop,,,the dev is working on updating now. Def remove the module then update and reroot.
[Google Pixel 3 Guides, News, & Discussion] DarkSolos:
Trying ...

i try after the november update with no magisk before and i have only bootloop, , with twrp or with the flashed img from here or made by MM and i noticed that the stock image is 65mb and the patched one is 25 mb ? normal ? but now i can't install magisk and i dont know why :)
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Yes, I don't know why, but the patched one is much smaller. Maybe it's packed or compressed somehow? I guess you're sure your platform tools are up to date?

---------- Post added at 07:52 AM ---------- Previous post was at 07:40 AM ----------

I just realized why the file I posted might not be working for some people. It is an actual zip archive containing the img. You have to extract the img file from it first and flash the img, not just flash the zip.
[Google Pixel 3 Guides, News, & Discussion] bbs3223474:
Thanks a lot!

Google always trying to block any root methods. It's understandable but also too unfriendly to our unlocked users.

So I'm not suprised about failed of Magisk on November patch.
[Google Pixel 3 Guides, News, & Discussion] st40611:
How I did it:

1) Flashed http://www.brasskeysoftware.com/etc/patched_boot.zip in boot_a and boot_b (I used the 3XL/crosshatch boot.img, so had to do this so OTA passes verification)

2) While in bootloader, use Volume keys to boot into recovery

3) adb sideload <ota_file>

4) boot once, lost root

5) reboot back to bootloader and do 1) again

6) reboot, root back
[Google Pixel 3 Guides, News, & Discussion] soapbox23:
Anybody have an issue with their microphone after rooting? It seems after I install magisk manager and hide it, it causes people on the other end of my phone call not hearing me when I hold the phone to my ear. Speaker works fine and if I move the phone farther from my face in non-speaker mode they hear me. Seems like an issue with magisk and the noise cancelling mic?
[Google Pixel 3 Guides, News, & Discussion] dazdnknfuzd:
I'm in the same situation (running the crosshatch boot image), but I cannot successfully sideload anything. All transfers die at 47%.

From the phone it looks like it's trying to open the file and verify it before it is complete, so it throws the following:

I'm using the Google USB drivers, and the latest ADB and FastBoot applications.
[Google Pixel 3 Guides, News, & Discussion] st40611:
You'll have to flash a blueline boot image for the sideload to work. So either go back to a pre-magisk stock boot.img, or flash a blueline November boot.img, take a leap of faith (don't boot the phone to Android) and sideload immediately after flashing the boot image.
[Google Pixel 3 Guides, News, & Discussion] dazdnknfuzd:
Thanks st40611 for the tip. I've tried that, but the transfer doesn't occur at all, it sits at 0% for a moment then dies. The phone reports the same errors I mentioned previously.

What's frustrating is that I cannot see the phone in ADB or Fastboot devices unless I set the phone to accept an ADB sideload from the stock recovery, and then it only appears under ADB devices in sideload mode.

I'm also wondering where TWRP disappeared to, as I certainly flashed it after unlocking the bootloader, and that's how I attempted to install Magisk.

Aarrgh!
[Google Pixel 3 Guides, News, & Discussion] cambunch:
Why not just flash the full image at this point and remove the wipe command? ADB sideloading is always a PITA...
[Google Pixel 3 Guides, News, & Discussion] st40611:
It reports the same error when you try to flash a boot.img? Boot.img should be flashed in fastboot, along the lines of 'fastboot flash boot_a boot.img', not in recovery.

Just to make sure:

1) Get a hold of a September/stock boot.img. Let's call this boot_stock.img; and get ahold of a November patched boot.img. Let's call this patched_boot_nov.img.

2) Get the ota file. We'll call it ota.zip.

3) While your phone is on, run `adb reboot bootloader`

3) fastboot flash boot_a boot_stock.img

4) fastboot flash boot_b boot_stock.img

5) Use volume keys, toggle to Recovery, then power key to boot it to Recovery

6) Press Vol. Up while holding down Power to get options; get to "Sideload via USB"

7) adb sideload ota.zip

8) once it finishes, choose "Reboot to bootloader"

9) fastboot flash boot_a patched_boot_nov.img

10) flastboot flash boot_b patched_boot_nov.img

11) Let it boot, should work
[Google Pixel 3 Guides, News, & Discussion] dazdnknfuzd:
Thank you Cambunch and st40611.

The phone no longer boots in to the OS. It stays on the loading screen with the grey progress stripe under the G logo for quite a while, eventually it reboots and goes into Android Recovery telling me that it "Can't load the Android system. Your data may be corrupt". I can either try again, or do a factory reset. I've done both.

Clearly something has corrupted somewhere, I just can't seem to get the phone to a state where I can fix it. I've tried at all stages to get access to the phone via ADB and Fastboot, and the only time I can is if I manually get it into Android Recovery and set it to sideload. I do see the phone appear in Device Manager, but I cannot see it in FIle Explorer to drop files onto.
[Google Pixel 3 Guides, News, & Discussion] Cares:
Just use Magisk Canary build and you can root like before.

1) flash-all.bat (remove -w flag if you don't want to wipe)

2) reboot and let Android update

3) adb reboot-bootloader

4) fastboot boot twrp

5) flash Magisk Canary in temp twrp

6) reboot and profit
[Google Pixel 3 Guides, News, & Discussion] Cares:
Yes an unlocked bootloader will always cause SafetyNet to fail.

You can flash Magisk Canary through TWRP if you want to easily root.
[Google Pixel 3 Guides, News, & Discussion] Archangel:
Did anyone just suddenly lose root today? I just flashed the magisk zip again and all is well just wondering why it lost root?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I've never lost root so far. I don't use any modules, so that might be why.
[Google Pixel 3 Guides, News, & Discussion] TheCheese45:
For me, it was the magisk greenify module. I went through all mods 1 by 1, installing and rebooting device. Active edge works fine on my Pix2, but the greenify mod was the one bootlooping me. Instead of deleting all modules, you can also use the uninmod to just uninstall a single mod that's causing issues: https://magiskroot.net/uninstall-magisk-module-twrp/
[Google Pixel 3 Guides, News, & Discussion] -Michael_:
I did, completely random, and fine up to this point. Doesn't make a lot of sense
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I have had root fail to give SU, but then after closing the app and launching again, it grants.
[Google Pixel 3 Guides, News, & Discussion] piccit:
Are you guys using the latest canary build? He made changes to fix things on pixel 3 and I'm not sure if those have been pushed to beta yet
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I'm just using beta and haven't had a single problem. But again, I'm not using any modules. I seems like maybe everybody who's had problems is using at least one module?
[Google Pixel 3 Guides, News, & Discussion] -Michael_:
I switched to it, root is back. Safety net fails.

---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------

I was only using the edge sense module. I've disabled it though, hoping maybe it's a module.
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
Lost root too after updating to november security patch.

I try to install magisk v17.3 and it failed. Had to install back the boot.img from november.

Anyone know when Magisk will have an update for that?
[Google Pixel 3 Guides, News, & Discussion] Archangel:
I havent installed the canary build for Magisk yet but I guess i will try it if I lose root again, so far it only happened once
[Google Pixel 3 Guides, News, & Discussion] cambunch:
Look for my post earlier in this thread, I posted instructions on how to fix it.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
No canary for me on the Pixel 3 or 3XL. I don't consider mine loosing root, so I am just chalking it up to 17.3 being in beta.
[Google Pixel 3 Guides, News, & Discussion] badhatdanny:
latest image?

can some one link the latest root img to flash? nothing seems to work. not even the stock boot.img

im stuck here in bootloader...
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Did you flash the boot image to both slots, a& b? And is the boot image from the same factory image version as is currently on your device. If you can't get your device to boot with the stock image the rooted one probably won't work either.
[Google Pixel 3 Guides, News, & Discussion] mrnovanova:
I've never had such a hard time obtaining root. Is there a tutorial for a method that actually works? I can't boot after flashing the zip VIA TWRP. It says no available slots. When I flash the patched boot img it won't boot. I get error booting boot.img
[Google Pixel 3 Guides, News, & Discussion] jascolli:
This tutorial is for the Pixel 2 but should be fine

https://xdaforums.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
[Google Pixel 3 Guides, News, & Discussion] mrnovanova:
Same. Error booting boot.img

The answer was 17.3 SMH...

#Facepalm

I just installed and rebooted with out a hitch

Root aquired

3 hours wasted

LMAO
[Google Pixel 3 Guides, News, & Discussion] elkay:
Canary works fine for me except MM hide doesn't work. I saw a new build was pushed last night but I haven't tried it yet.
[Google Pixel 3 Guides, News, & Discussion] daswahnsinn:
None of this is my work and I'm not taking credit for it. This was originally for the pixel 3XL "Crosshatch" and some lines have been changed to suit the pixel 3 "Blueline". Extracted from the OP that I linked. I think this should help out. https://xdaforums.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712

Updates

November update is a bit different and we cant seem to get patched_boot.img method to work. So I will outline the process that works for rooting November below. Any guide below requires that you have the latest adb/fastboot installed and that you have an unlocked Bootloader.

If coming from rooted Sept software use this guide:

Uninstall all Magisk Modules then reboot.

Download the stock factory images for Nov.

Extract and find the "flashall.bat" .bat file

Right click > Edit

In the .bat find "-w" and DELETE it

Safe the file

After removing "-w" put phone into fastboot, plug it in, and run "flashall.bat"

Wait for it to get done and reboot

boot to system > go to settings > security and remove any pin or password or pattern

Download the latest Magisk Beta (17.3 as of writing this) and transfer to device internal storage

Now, head over to the TWRP thread and download the twrp_boot.img

Return to fastboot and open cmd in its download location

run "fastboot boot twrp-3.2.3-1-blueline.img" and give your device a minute or two to boot into TWRP

Once there, find and flash the magisk beta on the internal storage

reboot and test to make sure it says you're rooted

If starting fresh from November (.A1.) Update

Install November update

Download latest Magisk Beta (17.3) and move it to the internal storage of the device

Reboot to bootloader

Download the .img version of TWRP for "blueline"

In the location of downloaded TWRP .img, open cmd and enter

fastboot boot twrp-3.2.3-1-blueline.img

Allow twrp to boot (this will take a minute or two)

Then go to install and install the Magisk zip

Reboot and find magisk manager and make sure it says you're rooted
[Google Pixel 3 Guides, News, & Discussion] jd1639:
This is the Pixel 3 forum, not the 3XL. You don't want to use twrp for crosshatch which is the XL.
[Google Pixel 3 Guides, News, & Discussion] daswahnsinn:
I understand that this is the pixel 3 forum, I was just saying these steps could help out. But I'll delete my post due to inaccuracy.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
You don't need to delete it. You might clarify it like done in the twrp thread of Dees_Troy where crosshatch and blueline are both referenced.
[Google Pixel 3 Guides, News, & Discussion] daswahnsinn:
Sorry, jumped the gun before my coffee. I made some changes to my post.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
December patched_boot.img for the Pixel 3 (extract from the .zip before using):

http://www.brasskeysoftware.com/etc/patched_boot.zip
[Google Pixel 3 Guides, News, & Discussion] Cares:
Why do you need patched boot img? I've been rooted P3 for November and December patches without one.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
This is just the Dec image patched with Magisk. Last month it seemed like a lot of people had trouble getting the patch process to work, so I posted mine for anybody who wanted an already-patched one.
[Google Pixel 3 Guides, News, & Discussion] tracymckibben:
Same here. Flashed the stock image with -w, fastboot into TWRP, re-flashed Magisk 17.3, successfully rooted and passing Safetynet.
[Google Pixel 3 Guides, News, & Discussion] Pakabidu:
THANK YOU!

4 hours spent trying to root my Pixel 3 and I'm finally here :)

Might help someone: I couldn't get Magisk installed via TWRP, would get stuck on Google logo, and patching the boot.img myself via Magisk Manager would eventually bring me to error booting boot.img pixel 3 Then tried CSX321's patched img and it's running - MM shows all installed, passing safety net too :cowboy:

SO, to get root on your Pixel 3 (I'l assume you've already unlocked your bootloader and have all the drivers, adb and fastboot on your computer)

1. Download https://dl.google.com/dl/android/aosp/blueline-pq1a.181205.006-factory-af1829a6.zip (this is December image)

2. Extract the zip and run flash-all with your phone connected to PC and in bootloader menu (phone will be wiped)

3. Android will start, open developer settings and re-enable USB Debugging

4. Download https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.1/MagiskManager-v6.0.1.apk and install

5. Download CSX321's patched boot.img from http://www.brasskeysoftware.com/etc/patched_boot.zip unzip and place patched_boot.img to your adb folder

6. Reboot your phone to bootloader and run these commands:

fastboot flash boot_a patched_boot.img

fastboot flash boot_b patched_boot.img

fastboot reboot
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Glad it worked for you! I'll add that if you don't want to wipe, you can remove the -w in the flash-all script or batch file and eliminate steps 3 and 4 (if you already have MM installed).

It's odd how patching seems to work for some people and not for others. It will probably be figured out eventually by our smart devs, and the process will get easier. Before getting a Pixel 3 I was still using my old Nexus 5 running LineageOS, and I miss how smooth the update process was there, with Magisk automatically reinstalling itself after.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Just an FYI, if you edit the flash-all batch file and remove the -w you won't wipe your device.
[Google Pixel 3 Guides, News, & Discussion] rczrider:
FYI: the new stable release (18.0) works for the Pixel 3 (mine, at least). No beta necessary.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Installed it on 5 different devices using OS 9 (Pixel 3/Pixel 3XL), 8 and 7 overnight. Used the direct install option (recommended) on all. No issues on any, and they are all passing SafetyNet. Not that I am in any hurry to re-root, but installing Magisk 18.0 instead of upgrading will come soon enough.
[Google Pixel 3 Guides, News, & Discussion] meleelord:
Tried latest official and canary builds, I flash kernel and then magisk and I get to the Google loading screen but it then reboots to TWRP. Anyone else experiencing this? Works fine with just kernel installed.
[Google Pixel 3 Guides, News, & Discussion] DarkReaper90:
Same issue here. I am able to flash the December official build and boot in fine. When I install the newest version of Magisk and reboot, it sends me into a bootloop at the Google loading screen. No TWRP installed.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Have you tried running the Magisk uninstaller from the TWRP .img (are you installing TWRP or just running from fastboot boot)? Do you have any old modules from a previous Magisk install? The uninstall will get rid of those. At worst, install the boot.img to both slots, fastboot boot the TWRP .img, run Magisk uninstaller and then start over again with temp TWRP, kernel and then Magisk.
[Google Pixel 3 Guides, News, & Discussion] meleelord:
Using the uninstaller and installing magisk worked. Thank you :)
[Google Pixel 3 Guides, News, & Discussion] laill:
Assume you do not have TWRP flashed and Edge Sense Plus is not active/installed

adb reboot bootloader

fastboot boot YOUR-TWRP-NAME.img

Apply Dec OTA without -w augment

reboot system to let Pixel finish the update

adb reboot bootloader

Flash Magisk uninstaller

Flash Magisk v17.3 (v18 keeps giving CTS fail for me)

Flash ElementalX 1.02

Reboot

These steps worked for me.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Glad you got it working.

---------- Post added at 01:54 AM ---------- Previous post was at 01:43 AM ----------

Happy that you are at least working on 17.3, but your steps don't make sense. There is no -w (since there is no flash-all batch) in the OTA, and you can't run the OTA or the factory image from inside TWRP.img as your sequence of steps shows. I think you need to start over using the factory image (minus the -w) and then TWRP.img, kernel and finally Magisk. The OTA as well as using ADB instead of the button combos to get into BL are great but learning the more manual way of doing things is a good place to start.
[Google Pixel 3 Guides, News, & Discussion] laill:
Woops, you are right, should be adb reboot bootloader, then directly apply the Dec update.

adb reboot bootloader

Apply Dec OTA without -w augment

reboot system to let Pixel finish the update

adb reboot bootloader

fastboot boot YOUR-TWRP-NAME.img

Flash Magisk uninstaller

Flash Magisk v17.3 (v18 keeps giving CTS fail for me)

Flash ElementalX 1.02

Reboot

For magisk v18, my case is the phone passes the safety net at first, after awhile it fails.

For the citi bank app, I never get it working on v17.3 but it works for the first few mins on v18.

Few mins after boot, CTS failure and I cant use citi bank app or play dragalia lost;)
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
On Magisk 18, does SafetyNet continue to pass if you stay away from those two apps. I have been running 18 since a few minutes after he released it to the public channel and have tested SafetyNet many times on 5 different devices with full green on all checks. Maybe try the SafetyNet Helper Sample app as well just for giggles. That works for me as well obviously.

P.S. Still no such thing as OTA without -w augment :). It would be factory image without the -w argument.
[Google Pixel 3 Guides, News, & Discussion] DarkReaper90:
Uninstalling and reinstalling worked! Thanks.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
Excellent news.