yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Guides, News, & Discussion] CSX321:
The only thing that springs to mind is, are you sure your platform_tools are up-to-date?
[Google Pixel 3 Guides, News, & Discussion] UK_Wildcats_Fans:
I updated today just to be safe.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Hmm. But it boots okay before you try to install Magisk or flash patched_boot.img?
[Google Pixel 3 Guides, News, & Discussion] UK_Wildcats_Fans:
Yes, it boots normally before I try to install or flash the patched boot. I even tried a patched XL boot and got the same thing.
[Google Pixel 3 Guides, News, & Discussion] FUZER384:
What's the order you took to install Elemental on an already Magisk rooted P3?
[Google Pixel 3 Guides, News, & Discussion] jsauder2:
Flash kernel from twrp. That's it.
[Google Pixel 3 Guides, News, & Discussion] FUZER384:
Didn't make TWRP permanent, just did temporary boot to get Magisk
[Google Pixel 3 Guides, News, & Discussion] jsauder2:
That's fine. Just temporary boot TWRP again to flash elementalx.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
For January, I just installed from the EX Manager after update and root.
[Google Pixel 3 Guides, News, & Discussion] UK_Wildcats_Fans:
I finally got magisk re-installed after the Jan update. Here is what I did.

0.. Ensured that I had the latest SDK Platform Tools (aka adb & fastboot)

1. flash-all (without -w) January factory image

2. Uninstalled Edge Sense

3. Downloaded the latest magisk uninstaller https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/magisk-uninstaller.zip

4. adb reboot-bootloader

5. temp booted twrp

6. Run magisk uninstaller via TWRP

7. Reboot system and make sure it was working correctly

8. adb reboot-bootloader

9. Download the latest magisk canary https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/magisk-debug.zip

10. temp booted TWRP

11. Flashed the latest magisk canary via TWRP

12. Reboot system

13. Checked out system
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Glad you got it working!
[Google Pixel 3 Guides, News, & Discussion] UK_Wildcats_Fans:
Thanks
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
I've reinstall Magisk with Canary version but there is still a few issue.

First and the worst thing is that I've lost my google Pay right from my bank account...

When I Hide magisk for Pokemon Shuffle, Google Pay... I just can't acces them. I click on them and nothing happen, the apps won't open, or it's loading for a long time with a black screen and nothing happen.
[Google Pixel 3 Guides, News, & Discussion] GrandMstrBud:
I can't get magisk to work at all. I install it through TWRP and it's not there after the reboot. It doesn't work with my Galaxy Gear S3 either so I am sending it back. This is not an 800 phone that's for sure. Maybe 400 to 500.
[Google Pixel 3 Guides, News, & Discussion] nickporwal:
Do tell me if it works. Because of the Google pay, i am not rooting the phone
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I can't speak to Pokemon Shuffle, but GPay is working fine on my wife's rooted Pixel 3 and my rooted Pixel 3XL. Both are rooted with Magisk 8.0 (stable) and have GPay checked in Magisk Hide. Both pass SafetyNet.
[Google Pixel 3 Guides, News, & Discussion] ShadowJP88:
It was working fine until January update. I need to contact my credit card to add it again... But my bank account is now fine, I just need to connect on the bank apps for this one to add it to gpay
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I followed my usual procedure (https://xdaforums.com/showpost.php?p=78624634&postcount=219), and everything is working perfectly.

If anyone is having problems getting Magisk installed on their Pixel 3, here's my 05 February 2019 security update boot.img pre-patched with Magisk 18.1:

http://www.brasskeysoftware.com/etc/patched_boot.zip

Unzip and then:

adb reboot bootloader
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
[Google Pixel 3 Guides, News, & Discussion] Ezrem:
Which version of Magisk manager are you getting with 18.1 installed? I'm still seeing the old version, but get notifications that 7.0.0 is available to install. When I install it, Magisk Manager insists that Magisk is not installed. If I reboot, I'm back to the old 6.x manager version.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I'm using 7.0.0, but I installed it before I flashed the patched boot image.
[Google Pixel 3 Guides, News, & Discussion] Darth#Mike:
ok. i think im boned. pixel 3. rooted with magisk, elementalx kernel. updated elemental to latest today. magisk popped up and wanted to be updated too. ok. did recommended install through app. rebooted. it went straight to twrp. weird. put my unlock pattern in, and noticed it was saying phone is decrypting?? huh? did it just wipe the phone because i cant see anything in my folders. cant boot system, just goes back to twrp. stuck at work without my laptop with adb, on a work computer. anyone have this issue? do i need to restart from scratch? or is there a way to get back. im good with directions and have some knowledge of this stuff.
[Google Pixel 3 Guides, News, & Discussion] robocuff:
Flash the stock boot.img. Should get you going again. Hopefully anyway.
[Google Pixel 3 Guides, News, & Discussion] GryphonBR:
So, I can see a bunch of people having issues with Magisk 18.1, and I got it working on my P3 with no issues this time around. Here's what I did:

- Had a rooted (Magisk 18.0) Jan stock + Dispair kernel, with Magisk Manager hidden (which, eventually, I determined to be the issue)

- Updated MManager, uninstalled previous MManager version and updated Magisk to 18.1 to make sure it worked; when it did, I hid the app and still it worked

- Downloaded full factory image from Google Developer site, removed the "-w" flag

- Downloaded Proton kernel, since I wanted to give it a spin

- Booted into fastboot, flashed stock image

- Booted into TWRP

- Flashed Magisk, then Proton kernel

- Rebooted

- Opened MManager and hid the app again

- Currently have GPay, PoGo, couple of banking apps and Concur all working on my phone, though sometimes SafetyNet might fail; in that case, I simply go into Settings inside MManager and toggle the Magisk Hide switch off and back on. That has sorted all my issues so far.

Hope this helps someone, cheers!
[Google Pixel 3 Guides, News, & Discussion] brettule:
New Pixel 3, unlocked the bootloader, updated OTA to latest build and security, flashed TWRP which went fine, flashed Magisk and it tries to boot then just dumps you back in TWRP. Flashed the Magisk uninstaller and the phone comes back to life. I guess we wait for a working Magisk release.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Magisk works fine. If you flashed twrp with fastboot that's the problem (falsh the boot image to both slots to clean things up if you did flash twrp). You need to boot the twrp image with fastboot then install the twrp zip within twrp. Then install the magisk zip. Or you can just install the magisk zip and forego installing twrp.
[Google Pixel 3 Guides, News, & Discussion] brettule:
I ran twrp with fastboot, then zip flashed twrp, then I reboot back to recovery to clean up the slots. Reboot once to system to make sure all is good. Back into recovery, flash magisk, reboot and the system spends a minute trying to boot with the G and scrolling loading bar then fails, restarts the system and drops me into twrp recovery. Only removing Magisk at this point lets me back into the system.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
Flash the factory image using the flash all batch file after editing out the -w you'll find in there. That'll clean up your system. Then boot twrp and do your installing of magisk and twrp, if you want it.
[Google Pixel 3 Guides, News, & Discussion] brettule:
Its a brand new device, barely configured. Shouldn't I be using the -w to wipe it if I'm having issues? Either way I ran both with -w and without and it doesn't seem to wipe the unit either way. Tried to reflash magisk and same problem as before, need to run twrp to uninstall magisk to get it to boot.
[Google Pixel 3 Guides, News, & Discussion] jd1639:
After you flashed the factory image did it boot ok? What version of magisk are you using? 18.1 is working fine for me. And how long ago did you download twrp? The early version had some issues, but the version number never changed.
[Google Pixel 3 Guides, News, & Discussion] AndroidGX:
Thanks for sharing, appreciated :highfive:

Just a quick question: I will have my Pixel 3 tomorrow, in the steps you explained (just to be sure) is there a need to unlock bootloader and flash twrp ? :good:
[Google Pixel 3 Guides, News, & Discussion] jd1639:
You need to unlock the bootloader. But you want to boot twrp with fastboot. Then install the magisk zip. If you want twrp permanently you would install the zip once you've booted into twrp. You do not want to flash twrp with fastboot. I boot twrp. Install the twrp zip. Reboot into recovery, twrp now, then install the magisk zip.

I forego flashing the patched boot image. It just seems like extra work. Note that the procedure I just described is different then what described in this thread.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Yes, as jd1639 said, you do need to unlock the bootloader, but I recommend avoiding flashing TWRP unless you really need it. You can install Magisk without TWRP following my procedure, or boot (but not install) TWRP to flash the Magisk ZIP.

My procedure without TWRP is simply what I've done since before we had TWRP available for the P3. It's very slightly more work, but it does eliminate one possible point of failure. I'm a programmer who likes to write HTML by hand, so the little extra work doesn't bother me. :)
[Google Pixel 3 Guides, News, & Discussion] AndroidGX:
Thanks :) yup, I was checking on how to root properly the Pixel 3 and after some search on xda, I retained your post ;)

I like simple things (generally speaking), and the solution to avoid flashing TWRP interests me :good: I will do a little bat script to help remember :cowboy:

I will maybe make a SimpleGX kernel for Pixel 3 :highfive: (I'm coming from OnePlus 5 and 5T as previous devices)

Cheers'
[Google Pixel 3 Guides, News, & Discussion] brettule:
Thanks for sticking with me through this jd1639, I appreciate the help. Here are all the steps, logs and versions:

I unlock Pixel 3 bootloader and fastboot boot twrp-3.2.3-0-blueline.img

flash twrp-pixel3-installer-blueline-3.2.3-0.zip then let it reboot

adb reboot-bootloader

Download factory image 9.0.0 (PQ2A.190205.001, Feb 2019) "blueline" for Pixel 3. Don't touch the flash-all.bat file and just run as is.

Logs from flash-all:

target reported max download size of 268435456 bytes
sending 'bootloader' (8493 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
(bootloader) Flashing Pack version b1c1-0.1-5155331
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 1.041s]
finished. total time: 1.325s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.052s
target reported max download size of 268435456 bytes
sending 'radio' (71132 KB)...
OKAY [ 1.642s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g845-00009-181130-B-5157073
(bootloader) Flashing partition modem_a
OKAY [ 0.476s]
finished. total time: 2.121s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.052s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: variable not found)
--------------------------------------------
Bootloader Version...: b1c1-0.1-5155331
Baseband Version.....: g845-00009-181130-B-5157073
Serial Number........: xxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.352s
Press any key to exit...

System doesn't wipe and reset as I would have expected so looks like something has failed but not sure what. Variable not found?

Flash Magisk-v18.1.zip and reboot

System shows google icon during boot, scrolling bar for 20 sec or so, then reboots into TWRP.

Flash Magisk-uninstaller-20190204.zip and system boots again.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Your platform tools are not up-to-date. Make sure you have the ones from here: https://developer.android.com/studio/releases/platform-tools
[Google Pixel 3 Guides, News, & Discussion] jd1639:
delete
[Google Pixel 3 Guides, News, & Discussion] brettule:
Duh! Thanks. That fixed flashing the factory image step.

Still no joy!

I booted once into the setup after the factory wipe, rebooted into bootloader.

fastboot boot twrp-3.2.3-0-blueline.img

flashed Magisk-v18.1.zip and reboot

System shows google icon during boot, scrolling bar for 20 sec or so, then reboots again.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
If you already have the Feb update successfully flashed now, you could just try flashing my pre-patched boot image. Download from http://www.brasskeysoftware.com/etc/patched_boot.zip , unzip it, and then:

fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
[Google Pixel 3 Guides, News, & Discussion] brettule:
Thanks, finally that worked.
[Google Pixel 3 Guides, News, & Discussion] RuffyMonkey:
not for me.

if i install twrp and then patch with the zip, i see the Google logo and then i get a reboot into recovery.

With the patched boot.img (downloaded and patched by me) the same.

installed via fastboot Flash boot or boot_a boot_b results in the same error.

(Magisk v18.1 and february update)

What else can i try?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Don't install TWRP. Just run flash-all (with -w removed), let it boot normally once, then flash the patched boot image to a and b with fastboot. TWRP is not involved at all.
[Google Pixel 3 Guides, News, & Discussion] RuffyMonkey:
Also doesn't work.

After i flash the patched_boot.img i can't boot into Android.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Are you sure your platform tools are up-to-date? If you run flash-all, let it boot and completely and finish updating (it continues updating in the background after boot for a couple of minutes; check the status bar), adb reboot bootloader, fastboot flash boot_a patched_boot.img, fastboot flash boot_b patched_boot.img, it should definitely work.
[Google Pixel 3 Guides, News, & Discussion] RuffyMonkey:
Yes i'm using the newest Plattform Tools (fastboot version 28.0.1-4986621).

After the first boot after flash-all, there is nothing in the status bar. And in System ->Systemupdate it says that i'm on the newest Version.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Hmm. I'm running out of things to suggest. Stupid question, but we are talking about a Pixel 3, right? (And not a Verizon edition; I don't really know if anything is different about those.)
[Google Pixel 3 Guides, News, & Discussion] TonikJDK:
Don't flash the patched boot img.

Run the flash all again minus the -w. Or flash the stock boot.img to BOTH slots.

Copy the whole Magisk zip to your phone. Boot to TWRP and install the Magisk zip with TWRP. Then start the phone and use the manager to directly install root.
[Google Pixel 3 Guides, News, & Discussion] RuffyMonkey:
Normal pixel 3 black (no verizone or other simlocksor modifications)

I've removed also all modules from magisk with suMount.

Ok i try this now. (but last time I've also got the error from above)

Update:

It's working.

I've flashed the system (without -w(ipe)).

booted into twrp. (only boot, didn't installed it)

installed magisk.zip

done

(after booting, the root worked out of the box, without any installation inside magis-manager)
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Super! Glad you got it working. I might start doing it that way myself, now that we seem to have a stable enough TWRP and Magisk.
[Google Pixel 3 Guides, News, & Discussion] wangdaning:
Why so many posts on this? Starting from fresh boot.img:

1) fastboot boot (twrp.img)

2) twrp installer (adb push "path to twrp installer" /sdcard)

3) reboot system

4) reboot recovery

5) if you did not do it before (adb push "path to magisk" /sdcard) or just flash

6) done
[Google Pixel 3 Guides, News, & Discussion] CSX321:
When this thread started, there was no TWRP yet for the P3. There have sometimes been buggy versions of TWRP and/or Magisk, or alpha or beta builds were needed to work properly. Sometimes people don't have the right version of the platform tools. Right now we seem to be at a point where we have stable versions of things. It hasn't always been that way.
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Trying to flash Magisk 18.1 after updating to the March update gave me bootloops. Is that a known issue?

I (think I) have the latest platform tools installed and ran TWRP 3.2.3.0 via fastboot to install Magisk...

Or am I doing something wrong?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I followed my usual manual updating procedure (described elsewhere in this thread), and it worked fine. I also updated the pre-patched boot image on my site, if anyone wants to use it instead of using TWRP.
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
hmmm that's really strange! I wanted to go back to the february update now - It hung on the G-Logo. so I reinstalled the march update again without flashing magisk. Now I'm running on March now without Magisk...
[Google Pixel 3 Guides, News, & Discussion] CSX321:
This is what I did yesterday to install the March update, and it worked perfectly for me, as it always has: https://xdaforums.com/showpost.php?p=78624634&postcount=219
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Wow, that's way more complicated than what I always did. I followed these instructions https://www.youtube.com/watch?v=2A_ILWdEO1I&list=FLmDMCXA_HYn3HS_U9hiPgCw.

I don't understand, why I would suddenly have to do the stunt with the patched boot.img, when before it always worked like that...
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I started doing it this way before we had a working TWRP, and I've just kept doing it this way. I don't have any other need for TWRP right now, and it seems like most people who are having problems are using it.
[Google Pixel 3 Guides, News, & Discussion] georgs_town:
Thanks for your patience! It worked fine! The only thing that didn't work was the flash-all.bat command.

What I did was edit the file in windows editor, removed "-w" and safed the file. What command exactly do I have to put in for it to work? I ended up seperatly flashing the bootloader, radio and zip...

Glad i can reinstall adaway now. XDA is a nightmare with all the ads ;)
[Google Pixel 3 Guides, News, & Discussion] CSX321:
In Windows, just flash-all from the command line, assuming your path includes the location where you have the platform tools (usually C:\Android\platform-tools\). Doing them separately as you did is equivalent, though.
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I get doing something out of habit (God knows I do plenty of things for that reason), but not "needing" TWRP doesn't preclude you from using the 'fastboot boot [twrp].img' method to simply install Magisk. Your recovery is still stock, nothing is installed and that method has been pretty failsafe.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
True, true. I may do it that way at some point. I'm a software developer myself, so I'm perfectly comfortable with doing it the manual way.

Although...I was just now thinking, is it necessary go through any of this and flash anything at all? Once MM is installed, can it not install Magisk by patching the boot image itself? Isn't that what we were doing early on, or did something happen to make that no longer work?

(Have I said hello to you in North Texas? I used to live in Plano and Murphy through the 90's and early 00's.)
[Google Pixel 3 Guides, News, & Discussion] sliding_billy:
I don't think anything has changed, but you still needed to create the patched boot even before using TWRP as far as I remember. I've been using either the [twrp].img or installing TWRP since the first time it worked on the OG Pixel/XL. With the exception of the one time it wouldn't decrypt (that was a long time ago), the .img method has always been the easiest way to go and gives you the option to use stock recovery to load an OTA if needed (though I had use the factory image without the -w every month for years until I broke down and installed dotOS last month).

P.S. Cool about Plano/Murphy. I have been here for 8 years after spending 40 years in W and NW PA. I worked in NW and SE Plano (almost to Murphy on Plano Parkway) and live pretty much straight north of Murphy past Lake Lavon. If you haven't been here in a while, you'd barely recognize how Collin County has exploded beyond Plano.
[Google Pixel 3 Guides, News, & Discussion] CSX321:
We left in 2005 and first came back for a visit in 2017, and yep, Murphy was almost unrecognizable. During the years we lived there it grew from 1500 people to about 9000. I don't know what it is now, but likely a lot more.

Back on topic :), next month I may play around with a couple of alternate Magisk install methods and see what works best.
[Google Pixel 3 Guides, News, & Discussion] acidspider:
I look forward to those results
[Google Pixel 3 Guides, News, & Discussion] acidspider:
With the new update to magisk manager is it safe do just download and install or does that lose safety net/root?

Sorry, having a brain fart
[Google Pixel 3 Guides, News, & Discussion] CSX321:
I'm on stable channel v18.1 and had everything working. Updated to the new MM, and everything is still fine. I just bought a drink in our break room to make sure Pay still works.
[Google Pixel 3 Guides, News, & Discussion] acidspider:
So just download and install the update from the notification of magisk manager?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
Yes, that's what I did.
[Google Pixel 3 Guides, News, & Discussion] fahmi182:
Update to magisk 19.1? Just direct method?
[Google Pixel 3 Guides, News, & Discussion] CSX321:
A while back I switched to the canary channel and have been updating with the direct method. No problems with Magisk, but I can't currently use Pay.
[Google Pixel 3 Guides, News, & Discussion] Exokan:
I updated to 19.1 via Magisk Manager today. Seems to be fine. There was a second of lag after the first boot (stock OS) but I can't be sure that was Magisk's fault. Haven't tried Google Pay yet but it hasn't worked for me in ages so I'm not hopeful.