yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] goti(0):
yes your are right this is an ongoing but i have been away for a while so I thought there might have been a fix v17.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] :
Same issue with stock kernel
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] trim81:
Anyone try 17.2?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Been running it since it dropped, not a single issue.

Sept Factory Image

Flash Kernel 3.10

TWRP 3.2.3-1

Magisk 17.2

-installed modules:

Busybox for Android NDK

Greenify4Magisk

UPDATE:

not sure what happened, but when I typed the above, I noticed my modules had updates available, so I updated busybox, module, rebooted, not problem. Updated greenify module, rebooted, stuck in G screen.

Hard reboot doesn't help, it eventually reboots to TWRP.

I tried flashing cust kernel then magisk, no love.

I tried flashing magisk then cust kernel, no love.

Any ideas [MENTION=3730810]Badger50[/MENTION], [MENTION=4565594]CyberpodS2[/MENTION], [MENTION=4100646]Alxoom33[/MENTION], or anyone else magisk savvy?

Oh, and I'm at work to boot (yeah I know, I didn't think updating Magisk modules would end up bootlooping me), so no access to PC (the DoD wouldn't take lightly to my trying to open a command prompt, or connecting my device to their network) :p

Thanks.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Shame...shame...shame! You know better than that my brother!???

Try flashing the magisk uninstaller and let it boot up. If it does, then go back to twrp and flash magisk 17.2. If it boots, then instal your modules again.

If none of that works, then repeat the process with 17.1 :good::cool:

Whataya mean the DoD wouldn't let you open a cmd on the puter!? Sheesh! ????
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] kaped31:
The Greenify4Magisk is causing errors on Pixels. I had to factory reset mine :( I tried to flash the factory image without wiping data but it would never boot up past the Google screen.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Oddly enough, I restored last week's backup, and when Magisk asked to update to 17.2, it updated the greenify4 Magisk as well, and with no issue.

Yeah, I went with the Magisk update right after it bootlooped me, I'm a sucker for a reason to flash at work when away from my PC, and on a technological island by myself, I'm dumb like that :p

So there must be a difference when greenify4Magisk updates along with the newest magisk manager, as opposed to it being updated manually by itself?

Either way, I'm back on 17.2 with Busybox and Greenify4Magisk modules updated :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
We've all been there brother... My wife thinks I'm a moron every time I do something stupid on my phone at work and have to call her on a land line and tell her my phone is dead till I get home. Lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
I can vouch for that! ???
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] kaped31:
Oo I might try to update manually then. After a full backup of course :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Yep, I have an agreement that I always have to have my work phone on and near me if messing with my phone even when at home in the man cave LOL

---------- Post added at 07:52 PM ---------- Previous post was at 07:36 PM ----------

Yep, I have an agreement that I always have to have my work phone on and near me if messing with my phone even when at home in the man cave LOL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] matekaneve:
?? I'm glad I'm not on my own here... My wife always tries to call me when she shouldn't... Then the landline starts ringing and I just say "I'm in twrp" ? she has no idea what it is but knows I'm messing with my phone ? or at home when I'm sitting at the laptop sweating and looking worried she asks what I'm doing and I just look at her and saying I'm hoping it will boot up! ??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Reechings:
Yeah guaranteed that she will call or text while the phone is unavailable. I think she has a sixth sense, I'll reboot my phone or do something quickly in TWRP and there'll be a voicemail waiting for me.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] def-g:
Any fix for the freezing that occurs when phone is off and plugged in? Mine still freezes at battery icon and needs a hard reboot.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
All good here, Running Oct update.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] antiochasylum:
I have always passed safetynet until now. Do we have to flash the uninstaller, then reflash magisk to get it to pass?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
Uh oh, I hope not. I just went through all that. I mean in the end it isn't all that hard but to do it every month... that would be rather offputting.

I had to flash A and B sides to wipe out previous 8.1 stuff that it was detecting about 1 minute into OS boot. (ie: safetynet passed if I jumped into it first thing, but by the time all my widgets got loaded... it had looked around and found traces of Magisk or something)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] newyesor:
[MENTION=2649074]chazall1[/MENTION]

you are flash magisk v17.2 on pacth OCT.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jbarcus81:
I'm about to re-lock and go back 100% stock over Magisk.. Using latest release of Pie, and Magisk 17.2. I do a fresh install of Pie, boot, everything is gravy. Flash Magisk, boot, pass SafetyNet. Restore all my apps from the PlayStore, not a backup. Reboot, pass SafetyNet. Then I can check a bit later, SafetyNet fails. Reboot, SafetyNet passes. Few minutes later? Fails again! It's like a cat and mouse game that I can't figure out! What would cause it to pass, then fail all in the same session? When it passes I can use Google Pay, etc. Once it fails, I can no longer use them and I have Magisk hide on many apps as well.. But I can't keep SafetyNet passing .. I've also tried custom roms, kernels, etc. Nothing seems to be working.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Is your device showing certified in playstore settings?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jbarcus81:
As of right now yes, and SafetyNet is passing as well. But I did another fresh install of everything. So far so good.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Has anyone tried installing Magisk 17.3 (17300) ?

I got the notification that a Magisk Manager update was available, clicked intall, all good.

Magisk says latest version 17.3, installed version 17.2

When I opened the new MM, I was prompted to update to 17.3 (17300), clicked 'direct install), all good.

After reboot, I was again prompted to install 17.3 (17300), thinking I might have hit the wrong thing, I clicked "direct install" again, making sure I hit the right option, all good, rebooted.

Magisk says latest version 17.3, installed version 17.2

I was again prompted to install 17.3 (17300). So I downloaded the 17.3 (17300) ZIP and flashed it in TWRP.

Rebooted. Now Magisk says latest version 17.2, installed version 17.2???

What's going on? Anyone else getting this???

Oct Factory image

TWRP 3.2.3-1

Flash Kernel 3.15

Magisk 17.2
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
Mr. Magisk (topjohnwu) pulled 17.3 because of some bugs on the new pixels and others. I'm sure he'll have a revamped version up before too long :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
I went to all the Magisk threads looking for something regarding this, I couldn't find anything.

I'm glad it wasn't something I did wrong :p

Thanks man!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] matekaneve:
v17.3 was re-released to the BETA and Canary channels about 2 hours ago, so you can check it again! :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Yeah, I got the notification and it installed as usual. Thanks for the heads up!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cjrivera04:
I still have the same issue. Has anyone reported this bug? All was good on 16.3 and below.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
Quite a few mentions, NO logs provided.

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cjrivera04:
What's the best way to log this? I'm assuming this sort of quirk would get lost in logging. I was trying to read through the link provided and I honestly don't know which of the options for logging would provide the needed information.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
Since this happens when powered off, it is extremely hard. My best guess is to start an ADB logcat and try to turn the phone on. Maybe hold the power button till it boots, if even possible.

A logcat with the charger connected and the power the phone down *might* show something too. ¯\_(ツ)_/¯
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cjrivera04:
I'm wondering if reporting without a log would upset anyone. I think there's enough people who experience it, but I know how folks are some times about logs, lol.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
You can do that, but it will likely just be ignored since there is no data to track it down the error and fix it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
You can mention the issue, but since it's been mentioned a lot already, it won't really help find a solution.

Reporting an issue on Xda is not like talking to a mechanic... "my brakes make this terrible noise when I stop." Easy to identify the problem there.

Logcats help point the dev to the environment when the issue happens.

Some members get irritated because 100 posts that say "xyz not working, how do I fix, what can I do?" just clog up the threads and doesn't serve any useful purpose in fixing the issue.

Once several people have reported it, no need to keep reporting a known issue without logs to help fix it.

Kinda like 100 people pointing to a house on fire and telling the firefighters "that house is on fire". Unless you can pick up a bucket of water to help put out the fire, you're not really helping the cause :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] showlyshah:
Guys.. a quick question..

I am having issue with vendor partition mounting on September 5 th security patch . Does anyone have it? Even twrp wont mount vendor and cache partitions. On latest twrp, flash kernel 3.12 and magisk 17.1 ( downgraded to 17.1 from 17.3 to check this issue )

Twrp, magisk, apps.. non can mount vendor now..

Any suggestions?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Just curious....what does TWRP state when you attempt to mount the vendor partition?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] blaze9090:
Guys this is slightly ot but I am coming back from an op6 and have a weird issue :

Everytime I flash magisk it first works and is installed. After some hours of inactivity magisk is suddenly uninstalled and I have to flash it again.

Same with stable and beta.

Anyone a solution?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Stock or rom?

Stock kernel?

Other mods?

Steps you took to achieve root?

Need some info so we can try to help ?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] blaze9090:
Sorry!

Pixel Dust, Sultan Kernel (had the issue with flash too)

Flashed Kernel then magisk then reboot.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
So, after a few hours, root is gone and magisk app is gone too?

I've never tried pixel dust but regardless, a rom should not have anything to do with it. I would unroot, delete magisk and try again. Maybe reflash pixel dust, reboot, root, and see if it sticks around longer than normal, take it one step at a time. This way you can narrow down the culprit. I would use the stable version 1st.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cjrivera04:
Just an FYI. I did an install of of the new November security update (I'm using latest twrp). I went back in and flashed 17.3 and then upgraded to the latest canary build 17.4.411 and now everything is back to normal as far as the charging issue is concerned. I'm also using a custom kernel, which I have been this whole time. I can't tell you if it was the Nov. update, the uninstalling of Magisk, or flashing from 17.3 to 17.4.411, but it's working now. Hope this helps someone with a similar issue (Pixel 2 xl).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
That sounds like something in OTA fixed (nothing relevant in Nov. Security Bulletin) and not Magisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
I am also having issues with Magisk on Nov patch (Pixel 2 XL). I have now done a full uninstall, flashed latest taimen to a and b sides, and patched boot each time and pushed patched boot img and rebooted or reboot-bootloader after each step. ie: covered all bases taht I'm aware of. My ctsProfile still fails. And eventually Magisk dies and says it's not even installed (reboot fixes that). 17.3 worked last month.... should I drop back to 17.1? Doesn't seem like a wide spread issue, I haven't seen much re: Nov patch.

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM ----------

Note: I discovered I still had an old directory at /sdcard/MagiskManager with old imagesk. Apparently uninstall doesn't look for old locations too well! I deleted that before doing the above "re-do", but I wonder if it's still finding other evidence..? I cleared out all old img files from /sdcard/Download/ where things go now.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Is there a particular reason why you don't run the magisk installer .zip instead of flashing to both "...a and b sides" and having "pushed patched boot img" and all of that...??? Not that that way doesn't work (necessarily), but I've found installing it via the official .zip installer offers the least issues post-install (i.e. passing safetynet checks). If anything, I have a taimen and Nov. update and have had no issues (magisk related)...

Most people who don't install via the installation .zip are usually misinformed about using TWRP custom recovery and they are usually concerned about replacing their stock recovery..... you could choose to merely

temporarily

boot into TWRP (temp boot via twrp image [.img] file) that one single time, install the .zip magisk installer file, and never touch TWRP again; if you so choose...

And, if desperate enough to never touch TWRP at all ever, I ran across this very interesting guide by [MENTION=3694505]Telperion[/MENTION] that even just only uses adb commands to install Magisk; you can find it HERE.

So, I know you said you "...covered all bases...", at that may be true in terms of manually flashing/patching/overwriting the boot image/partition, but try these (more full-proof) methods; to cover some more "bases" so to say... and hopefully you'll find that installing Magisk via these methods might install just right to make it not glitch on the safetynet passes...

good luck and hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] bulletbling:
I am having so many issues with the latest November update. I did a clean install of the November on my Pixel 2 XL. Then I temp booted TWRP and installed the latest TWRP zip. I reboot to recovery and flash the latest Magisk 17.3 (I've tried 17.1 as well) via zip install and I get stuck at the Google boot logo.

After this I tried an alternate route. I clean installed the November again and did the same TWRP install, but then I used fastboot to flash the patched_boot.img. Now, this allows me to boot the phone just fine, but Magisk Manager then says I am not rooted and offers to install. What could be the issue? Ive clean installed twice now and reattempted with no luck. Had no issues with TWRP and Magisk on November update when I had initially rooted on the October update and OTA'ed to November. The only reason I clean installed was because my notifications were being delayed and auto brightness wasn't working well.

---UPDATE---

I tried it for maybe the fifth time and it finally took. This time I did the following:

1. Clean factory image reinstalled (kept data this time since I just had my apps restored and didn't want to redo that)

2. Temp booted TWRP 3.2.3-1

3. Installed TWRP 3.2.3-1 zip

4. Rebooted phone

5. Installed Magisk Manager

6. Re-extracted the latest factory for the boot.img

7. Sent the boot.img to the phone and patched it with a reinstalled Magisk

8. Rebooted to recovery via ADB

9. Installed Flash kernel

10. Flashed patched_boot image

Now it's working for some reason.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] JarMagic:
Boot Loop

Good evening. I was attempting to root my Pixel 2 xl using Magisk, and now I am in a boot loop. I have tried wiping and starting over, but it doesn't work. I can see the multi colored circle start, but then it goes into right into a boot loop. After a while, I get a message that there may be corruption and should wipe and do a factory reset, but it does not wipe. I'm pretty lost, any help much appreciated.

Thank you
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
https://xdaforums.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761

Try that
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] steviewunderr:
For people having issues, I'll share my method which worked flawlessly. I flashed a full factory Nov image, booted twrp 3.2.3-1, flashed twrp, reboot system (important step, skipping this would cause an infinite booting process), flash magisk 17.1, then flash Sultan kernel. Everything works perfectly for me at this point.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ytbai:
I am having so many issues with the latest November update，too.

I did a clean install of the November on my Pixel 2 XL（taimen-pq1a.181105.017.a1-factory-e79a94ed.zip）. Then I temp booted TWRP and installed the latest TWRP zip（twrp-pixel2-installer-taimen-3.2.3-1.zip）. I reboot to recovery and flash the latest Magisk 17.3 (I've tried 17.1 ，Magisk-v16.2(1620).zip，v17.2,v17.3,v17.3.1,v17.3.2 as well) via zip install and I get stuck at the Google boot logo. and must flash Magisk-uninstaller-20180921.zip fo fix it.I have tried a lot of times, Now I 'am waiting for the new Magisk .

---------- Post added at 06:45 AM ---------- Previous post was at 06:45 AM ----------

I am having so many issues with the latest November update，too.

I did a clean install of the November on my Pixel 2 XL（taimen-pq1a.181105.017.a1-factory-e79a94ed.zip）. Then I temp booted TWRP and installed the latest TWRP zip（twrp-pixel2-installer-taimen-3.2.3-1.zip）. I reboot to recovery and flash the latest Magisk 17.3 (I've tried 17.1 ，Magisk-v16.2(1620).zip，v17.2,v17.3,v17.3.1,v17.3.2 as well) via zip install and I get stuck at the Google boot logo. and must flash Magisk-uninstaller-20180921.zip fo fix it.I have tried a lot of times, Now I 'am waiting for the new Magisk .
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
After flashing twrp, you said you booted back to twrp, did you not boot to system 1st and let it boot up and settle prior to booting back to twrp?

Must boot up the system after twrp, before flashing anything else. Then, boot to twrp and flash magisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
For what it's worth, in the beginning, after installing the magisk .zip installer, it would always get stuck at the Google boot logo; the only way to get past it was to do a hard-reset. After one time, the next time loading it would successfully load into the system. Maybe this is all that's needed...?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ytbai:
Thank you very much. Now I have tried Magisk-v17.3_3.zip,Magisk-v17.4_3.zip,and also boot up before back to twrp,well ,There rae the same issues.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
Flash TWRP installer.zip then Magisk.zip then and only then reboot to system.

If you can't boot you probably have modules that are not compatible with the November update or the Magisk version you are using. One culprit is the older version of the Active Edge module.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
Hi all, sorry I had to deal with rebooting my phone every couple of hours while I was on vacation all week! As part of "covering all the bases", I DID try the temporary boot-to-TWRP method of installing the .zip. Same old story. :( I may try again today to make sure. It's almost like I get a limited number of root attempts before it "sees what I'm up to" and shuts me out.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] v12xke:
Extract the boot.img from the full Google image and fastboot flash it, then twrp.img directly behind it. Then from your phone flash twrp.zip , kernel, magisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
I've noticed a few solutions all mentioned another kernal.. is that a requirement these days perhaps?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] v12xke:
Not with Magisk, but with TWRP. Applying a custom kernel is optional, but in almost all cases solved the "no touch" issues reported earlier with TWRP. I have always flashed TWRP, kernel, magisk queued together and it has never failed. Give it a whirl and stick with it if it works for you, too. Disclaimer: I have always used a 4 digit PIN, so can't speak to other login security methods, eg. swipe patterns. :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
Ah.. the new TWRP works with pattern method just fine. As in, it loads and patches and such. However, I'm still failing even with this:

(Lines with # are comments)

----------

cd ~/Downloads/Android/Pixel2XL

# ---- Added to start over ---

adb reboot-bootloader

fastboot flash boot boot.img

# ----

adb reboot-bootloader

fastboot boot twrp-3.2.3-1-taimen.img

adb shell twrp install /sdcard/Download/twrp-pixel2-installer-taimen-3.2.3-1.zip

adb shell twrp install /sdcard/Download/Magisk-v17.3.zip

# [On phone: hit back, then Reboot, then System in the TWRP UI.]

# SafetyNet fails here after about 1 minute into the reboot

# Held power, selected Restart

# Still failed both checks in Magisk

# Full shutdown and power on.

# Still fails.....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] v12xke:
Read all that. The only thing I do differently is pre-position the TWRP.zip, kernel.zip and Magisk.zip on the root of my phone. After fastboot booting the twrp.img file I take over on the phone. Within twrp (booted) I queue up the zips- twrp, kernel, magisk. Since you are beginning with a clean boot.img, I don't see anything you are doing wrong. Maybe the fastboot/adb binaries are outdated? In any case try placing the files on your phone first and flashing them with twrp. Best of luck. :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
Yep that's what I did, only they're in /sdcard/Download (which has always worked thus far, as long as I do everything right). And I checked the sha-256 of the download to make sure it wasn't bad, so it's not a bad source zip. So teh only thing missing seems like flashing a kernel, which I have never had to do before. My adb was up to date a few months ago but I suppose I should double check today considering this mess.

Thanks all for the help so far. I may try rolling back to Oct at this point...

---------- Post added at 06:06 PM ---------- Previous post was at 05:47 PM ----------

I'm on fastboot 28.0.1 (Mac) which is still the latest. :\
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] v12xke:
Fastboot the full November Google image again (not OTA) (removing -w from flash-all) and then proceed as recommended. It's working for everyone else, including root/Magisk/SafetyNet.... SUP Mac boy? (jk) :silly: