yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
Yeah tell me about it. I did that. No help. I just fastboot boot'd twrp and ran the Magisk uninstall zip. Switched sides with "fastboot set_active a" and repeated. Rebooted many times in between steps. Back to a basic plain system.. supposedly..... and SafetyNet Check says I'm failing "CTS Profile match" ... WTF?? I'm pretty sure some file on the phone is tipping it off but why now all of a sudden and only for me? I can't find what triggers "CTS Profile match" to fail. :(
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
What version of Magisk are you using?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Ohhh...you're on Mac...that may be something...

I can't really recall everything that's different between what NTFS does and everything else, so I may be suggesting some very obvious things, but when you are flashing the Full Factory image, you are using and modifying the flash-all.sh file right? not flash-all.bat. Also, I recall vaguely that the syntax is different and a lot of people had to learn to use ./ or /. or something to get commands to work...that's not what's happening here, right?

The only other advice I can offer is to fully reboot after every install. I believe it's Az Biker constantly preaches doing that...reboot after twrp installation, reboot after a custom kernel installation (if necessary), and a reboot after magisk installation (from .zip)...

good luck to you and hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] v12xke:
If there were residual files, seems like the Magisk uninstaller would remove them... Sounds like it may be time for a full wipe. :eek:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
No I've got the Mac thing down, it's not the issue. Yes, I edit the .sh file, though for a while I was running the commands manually so I could verify the results. The shell scripts (.sh) just wait 5 seconds and assume it flashed OK and continue to plow through. I always remove the -w if I use flash-all.sh though.

So last night I once again flashed the Magisk uninstall zip, twice, then tried to redo magsik via TWRP. ..it would fail to boot (same process was working before), so I went back to my old tried and trusted method of fastboot boot patched_boot.img, and this time it has finally stuck! I keep checking SafetyNet and it's still good after 12 hours. Hooray! Once it was stable for a bit, I redid from scratch all of my root-access apps. This time I only hid a few apps.. previously I had over a dozen apps selected to hide magisk, and that may have causes some strange issues, so I'm starting with just my banking apps, google pay, play store, and verizon services. I have the Magisk Manager name-change thing enabled, on beta (17.3), and did not do enable systemless hosts because AdAway seems to be working without it.

I had trouble reinstalling the magisk module for Active Edge - it would start installing and just stall. So I rebooted, selected download instead of install, which still kicked off an install at the end anyway...?! but, this time it ran after a minute and worked, and has been stable all night/morning. Active Edge had issues last month and I think in December I will take up the practice of deactivating modules before starting the process. I also am going to avoid installing busybox, as I had put it on there at one point "just in case" and wonder if it mucked things up with it's strange installation procedures.

PS: Yes, reboots often throughout the process seem to help also. You at least need to do a "fastboot reboot-bootloader" after flashing each item. It's easy to get excited and jump into the next flash or attempt to install Magisk before you've rebooted and it can definitely get... unpredictable.

So, I don't know why this go-round of "redo everything" worked when it didn't before, but I'm finally out of my hole. (Note: I did NOT end up using a custom kernel, nor installing twrp permanently. In fact, I tried several times the suggestion to install it but when something would freeze and I'd have to reboot to recovery, TWRP NEVER came up! Only if I "temp booted" it via fastboot!)

Thanks to everyone in this thread for ideas and help, you've all been great!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] martyfender:
Why are you hiding the Play Store? I think that could cause issues. You did not mention this but hiding Chrome and Android System Webview will cause issues.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ytbai:
[/COLOR]

That's I wanna to say. I have tried to flash the kernel with ElementalX-P2-2.04.zip,after flash the twrp,well,it can be booted

1. just make a new flash on your phone.(taimen-pq1a.181105.017.a1-factory-e79a94ed.zip) ,and do step by step like this:

2. fastboot boot twrp-3.2.3-1-taimen.img

3. boot into the tem twrp

3.1 flash the twrp-pixel2-installer-taimen-3.2.1-1.zip (well it works well on my phone,and that realy don't have "no touch" issues )

3.2flash the ElementalX-P2-2.08.zip ( that's very important step!!!)

3.3 flash the Magisk-v17.3.zip

4. reboot your phone,and just install MagiskManager-v6.0.1.apk,and now you got su !!!

---------- Post added at 09:02 AM ---------- Previous post was at 08:56 AM ----------

That "no touch" issues I have met too.I solved it by this: 1. you can just hot plug one mouse with a otg Micro usb-cable ,2.reboot ,and just leave the charging ware in the phone,and then your touch screen works.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
There have been instances where a user has had to run the Magisk uninstaller zip multiple times to eradicate a stubborn file or two. Worth a shot?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
Magisk-v18.0 running as expected here.

Great job
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pj1000:
Persistent charging smbol that also locks up phone when it's turned back on (20 second power button hold to force reboot) is very annoying because I like to turn my phone off at night. I found this problem talked about but I couldn't find a solution. Everyone has a different theory as to what's at fault (TWRP, Kernel, or Magisk). I decided to find out cause, for whatever reason, it's annoying. I start with a clean install of December's update (taking out the "w") and it's all good. My phone turns off, charge symbol appears, then disappears after about 20 seconds as it should. I add TWRP. and recovery works fine along with the behavior of the Flash Symbol icon. In other words, it disappears after 20 seconds. I then install Magisk (the latest 18.0) and reboot. Magisk passes all its tests. I turn the phone off and plug in the charger for the 3rd time and the Charging Icon stays lit and the phone requires a hard reboot. So I've proven, at least to myself, that it's something in Magisk that breaks the ability to charge the phone when it's turned off unless you don't mind risking a burned in charge icon on your phone. Others have suggested leaving the phone on while charging as a workaround, but I like turning my phone off at night - I like clearing out all the caches and temporary what-not the accumulate on my phone. Has anyone found a way while using Magisk to charge the 2XL when it's turned off without keeping the charge symbol up all night or without leaving the phone on?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Didit_Anshari:
November build with magisk didnt have this issue if i remember correctly..so its something with December update and magisk on my pixel 2 xl.. I tried uninstalling magisk and it work again. Hope it will get fixed soon., I kinda scared running out of battery and have to charge (is it charging or just freeze the phone ?) with that dreaded symbol on my screen for so long.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
for what it's worth, I've had this happened to me once; but I don't really turn off my phone and charge like this frequently. Magisk 18 installed via TWRP installation .zip, December update, ElementalX kernel, using stock charger -- I accidentally set it to power off instead of restarting and forgot about the phone for the night...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Pkt_Lnt:
This has been reported fairly often. Magisk and kernels have been examined and tested. The problem has not been identified, and the reason for that is that there is no way to get logging on a device while off. Many have tried to get a logcat, last klog, other kernel data immediately on startup, and nothing helpful shows up. I don't know if this will ever be found, since it seems to not happen on stock, unrooted, unmodified phones. Maybe *IF* we get lucky, someone with knowledge of the ROM charging while off shows up. I doubt anything will be resolved, at least not soon if ever.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
It's probably a byproduct of unlocking the phone or rooting. Take it as a badge of honor. Just unplug your phone before shutting down and at start-up and you will be fine. The ultimate solution if you don't like unplugging your phone is to unroot and relock your phone. If that dosn't work, throw it in the garbage and buy an iPhone. Lol;)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] an21281:
I think it happens even when the phone is already off, then plugged in. Not just when phone on, plugged in and powering off...

A hard reboot fixes it. I remember something like this (charging not animated, but it didn't freeze the phone) happening with my Nexus 6 and I think that ended up being a kernel problem. Not sure if this is similar?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Alxoom33:
I don't think it's a kernel problem, since I've seen it on a number of different kernels, but it might :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] martyfender:
I don't own one of these devices, but I see this posted quite frequently on the Magisk forums.

[MENTION=4470081]topjohnwu[/MENTION] recommends not installing TWRP, but having the stock boot.img/recovery on the device, then temp boot TWRP with fastboot from a PC to then flash Magisk. Has any of you tried this to see if you still have the charge bug?

I do know that doing this has solve another user with a Pixel 3XL's problems in flashing the latest Magisk v18 stable.

See [MENTION=4470081]topjohnwu[/MENTION] 's Dec. 4th entry on his Twitter blog for what he states about this:

https://twitter.com/topjohnwu

Out of curiosity, do any of you know if all A/B devices, such as this, have the boot.img/recovery in one partition, unlike many older devices that have separate partitions for the boot.img and recovery?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pj1000:
To be clear, when the phone is turned off for the night, and the charge cable is attached, the charging icon appears and disappears as it should when BOTH TWRP and the latest ExKernel is installed. It ONLY only stays on all the time when the phone is turned off and when Magisk is installed. I get why it's next to impossible to figure out - because we can't generate a logcat when the phone's off...I was just wondering if someone stumbled on a solution other than to "keep my phone on while charging."
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] CPngN:
I can confirm this problem with the December build with Magisk 17.3 installed. I let my phone die over night 2 nights ago and had to charge it while off, and the nice bright white battery icon stayed on the whole time it was plugged in. Pixel 2 XL from Google store.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] martyfender:
[MENTION=4470081]topjohnwu[/MENTION] states here that he can't fix this problem:

https://github.com/topjohnwu/Magisk/issues/906
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ZeroSkylineX:
Is anyone else getting random Magisk uninstalls? I occasionally have to restart my phone to regain root access.

-Running Android 9.0 on Havoc OS
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
It's a known issue with some custom roms and kiri kernel.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharpz811:
Hey badger50, but does this affect stock ROM with custom kernel like Flash? I'm still in magisk 16.7 from Flash kernel's thread. Just wanna know if i should remain on the current magisk I'm running because it's working fine as is.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Badger50:
I haven't had any reboots or freezes on stock rom with 18.0 with whatever kernel I've tried. You shouldn't have any trouble upgrading to 18.0. Not to mention you'll need to if you use substratum :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharpz811:
Thanks for speedy reply sir! Ok good i should be fine when i finally upgrade lol can you believe I'm still on August security patch! I've been so caught up with work and also not to mention i was so addicted to this game called open transport tycoon deluxe. That game is way too addicting so i had to quit after my final map lol.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] chazall1:
Magisk-v18.1 and Magisk Manager v7.0.0

all running as expected
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] me_droid:
Due to a bad support experience with Fi (received a new Pixel 2 last october after MUCH pain), I've held off rooting my pixel 2. I've decided to root again and I just wanted to confirm that for first time root with complete stock, I just need to use the following steps:

1. fastboot boot the appropriate twrp.img - I don't need to permanently install twrp

2. in twrp, sideload the latest magisk.zip

3. reboot phone

I think that this install will also install magisk manager, or do I need to install that separately?

Thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] madmuthertrucker:
I put magisk.zip on the phone. Then flash it w/ twrp.

1. Fastboot boot twrp.img

2. Install magisk.zip

3. Reboot
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pa.pn2:
I uninstalled magisk via uninstaller zip in twrp.flashed new kernel in twrp and latest magisk 18.1 zip in twrp.now i can't install the magisk manager 7 apk anymore

Any idea why that happens? first time for me
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Sometimes you have to use the uninstall zip a couple times, I would try that, boot to OS, making sure it's all gone, boot back to twrp and flash the install zip again then boot back to OS. I had to give it a couple minutes for 7.0 app to show up, but it worked.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pa.pn2:
I uninstalled the apk via adb.all fine now
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
I am on a Pixel 2 XL, Bootlegger ROM.

I go into GP to verify my card details. I enter the CVV, it is correct. Then I get the error (screenshot). Does anyone have an idea what the culprit is?

PS: my cards are okay to use in the Chrome browser for my phone or the desktop. I have already uninstalled and reinstalled Google Pay. Because it works on the browser I have to think it is a Google Pay issue?

I deleted and reentered my card on the Google Pay browser site. Still coming up with error message.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] clothednblack:
Never seen that before, maybe you need to hide something from root? Android pay maybe, I'm not sure
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
I have hidden GP and not hidden GP. No difference.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I'm not quite certain this is a Magisk/root issue, but....

It would be good for you to try clearing the data cache of "GP" (or any app that shows random, weird error messages like that), even so far as to uninstall/re-install it, and try entering the card information again. BUT I've had nothing but this type of issue...with ONE card! Long story, short; I had to keep resetting my smartwatch and phone (a couple times) and after repeatedly inputting and "verifying" the card, the bank's system freaked out and put a "flag" on the card and account. Point is: you might want to call the bank and talk to them, this could easily not be caused by Magisk or rooting...

Just a thought...hope this helps...good luck to you!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
PS: my cards are okay to use in the Chrome browser for my phone or the desktop. I have already uninstalled and reinstalled Google Pay. On Google Pay I was just verifying my CVV number. Because it works on the browser I have to think it is a Google Pay issue? I deleted and re-entered my card on the Google Pay browser site. Still coming up with error message.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
I'm gad you uninstalled and reinstalled -- it's always good idea when having a "glitchy" experience with any app.It may well be a Google Pay issue, but in my experience, they''ll just play the "blame game" and direct you to the bank...but, for what it's worth, I once was able to perfectly get my "trouble" card to work perfectly on the Google Pay app on my phone, but it would not work (going through the same exact process and steps) on my smartwatch...not that I'm doubting you or anything Socttay, I'm just saying that I've personally seen GP work in one "medium" and still crap out in another -- it still ended up being a bank-side "server" or authorization issue...

Hope you get it narrowed down....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
Your reply is helpful. I will ring the bank.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
I've called my bank twice now and they say it's not on their end.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Live I've suggested previously, you might try calling actual Google, but I'm sure they'll merely "pass the buck" onto the bank -- most likely after determining you've uninstalled and reinstalled the app...

and...maybe I should've asked before, but it would be helpful to know if you are on a stock ROM, correct? I mean....maybe it is Magisk and/or rooting, and I would imagine maybe running the Magisk uninstaller 3+ times (in a row), and re-applying the root process may get it properly working...

Oh, one thought that just came to me now is you should see if downloading an older version of Google Pay (apkmirror comes to mind) comes out with the same issue. If it works in an older one, then that narrows it down to a bug in the latest version.....

good luck to you...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
Of course, no one is taking responsibility for this. In the OP, BootleggerROM. I did uninstall once. Three times is better?

I will try the older version of GP.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
3+ times is what's suggested by the great [MENTION=4670411]Az Biker[/MENTION]! (here's an early example of his philosophy: https://xdaforums.com/showpost.php?p=78204537&postcount=2481 ; I've seen him say it a couple of times, but I can't seem to remember or find those instances). He talks about Magisk leaving residual files and not getting everything the first time or two...

If you are on the BootleggerROM, I also suggest bringing this up to their support forum/page as well; it's been well known (and documented I presume) that custom ROMs have issues and a hard time with Google Pay and NFC and all of that...so another thing to keep in mind....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Actually, I was just repeating measures others have had to do to completely remove Magisk. I believe it was [MENTION=3730810]Badger50[/MENTION] who started pushing the "multiple flashes of Magisk uninstaller" when stubborn Magisk issues persisted.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
Mr. Az;

Thanks much for the information. I will try later today.

Is there anything else but I should uninstall or do besides Magisk uninstall 3X's?

Off the record, from your perspective, it is a Magisk uninstaller issue?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Ahhh....between you two GREATS, and all of the super awesome advice you guys give on a constant basis, it's hard to keep all of it straight ;)

Mr [MENTION=3433100]Scottay5150[/MENTION], I'm not looking for any praise, and I know Az Biker is a "top dog" around here and I'm sure his reputation proceeds him, and I can understand you wanting him and his type of assistance and being excited for it...but i can't help but start feeling a bit dismissed and overlooked as you make it a point to "address" him when it's been me giving you advice and that specific help...:( just saying....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
Sometimes it takes a willage! Sorry about that. Thanks to all, including Mr. simplepinoi177!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
I think it's just stubborn file fragments that sometimes don't get deleted when Magisk is uninstalled.

I don't think it's a Magisk issue, per se, but more of a mechanical failure to efficiently remove all the files.

Flashing the uninstaller several times isn't a for sure thing, but it HAS helped several users in the past with hard to figure out Magisk related issues.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Scottay5150:
Update: the uninstaller trick worked for two of the three cards. The people at Chase Bank still think it's a Google Pay issue. What are your thoughts?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Az Biker:
Since I do not use Android Pay or Google Pay, I'll side with the law of averages.

If flashing the uninstaller multiple times worked for 66% of your cards, I'd agree with Chase Bank :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alphamale:
Anyone having trouble with hide function on latest version 18.1.. When I hide playstion Vue app it won't open
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
Have you done/tried the obligatory clear cache, uninstall then reinstall app (in your case, the Vue app), uninstall Magisk using the uninstaller(multiple times/3+ times), make sure everything is set up in Vue and Magisk before enabling the hide function on that specific app...?

If anything, logs would be most helpful as well....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alphamale:
Tried clearing cache and uninstalling app. I can't set up Vue app bc it detects root. I've tried magisk 18.1 on multiple ROMs and it won't work with this app. It worked fine on version 18. I'll try 18 again
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pa.pn2:
Did u hide magisk app also?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] alphamale:
The actual magisk manager app? It's not an option
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] simplepinoi177:
A couple of thoughts/ideas...

In my iteration, after running the uninstaller, install the Vue app before anything, set it up, and then install Magisk, have everything set up (outside of enabling the hide option) there, reboot, and only then enable the hide option and try opening the Vue app at that point...see if it doesn't work then...

Some other thoughts are that for you -- if you aren't on already -- try 18.1 BETA. And if you are already on that, then to try Magisk Canary beta builds(I linked for you HERE); which is touted as "bleeding edge builds"...I see that those on the Magisk forum often suggest trying that route as well...see what it can do for you, I guess...

Good luck to you and hope this helps...
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] martyfender:
The option is in Magisk Manager settings.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] pa.pn2:
Skygo also Just works this way.

Hide skygo in magisk hide.then hide the magisk app in settings