yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] digger16309:
I got myself into real trouble trying to return my P6P to stock kernel from Kirisakura kernel.

When I boot into the bootloader it says my device is corrupt. I see no Slot A, etc...

When I try to boot, it just goes into a charge screen and does nothing. Or the Google screen and freezes.

What is the procedure to get back to a working bootloader?

My big issue is that I can't get to fastboot devices - it won't show up in the Command window or the flash tool.

-----------------------------------------------------------------------

EDIT - OK, I don't know what happened here other than I waited about 24 hours and miraculously, the bootloader error cleared, I was able to flash again, and then get back to the stock kernel. I did find posts about this issue while searching for a solution. I will just thank the Universe for this good fortune and continue on.
[Google Pixel 6 Pro] whatsisnametake2:
magisk update problem.

I'm android 12 build from june 22. was happily using canary magisk from that period, version 24 something. in an attempt to get my banking apps working I thought I would try shamiko, which required updated magisk. so I installed latest canary magisk app. app was telling me app was version 26 but magisk was still 24. so I clicked on install next to that, then direct (recommended) and now I seem to have lost root. all modules disappeared. app is saying N/A next to magisk. but zygisk yes.

what did I do wrong? do I need to re flash the original patched bootloader?
[Google Pixel 6 Pro] Lughnasadh:
I would try to patch your current boot image and flash that in fastboot. Usually if you are rooted the direct install method works but could be since you were very outdated in your Magisk app, changes may have taken place between then and now to put a glitch in trying to direct install a patched boot image from 24 to 26.

If that doesn't work, then it sounds like you may have a hidden Magisk app. If that is the case, you would need to delete that so you don't have 2 conflicting Magisk apps.
[Google Pixel 6 Pro] whatsisnametake2:
I'm totally lost here. I tried re flashing the patched boot image but the magisk app still isn't picking it up. interestingly when I uninstall magisk, it still shows up in the app list but without its proper icon.

re hidden version of the app - yes my previous working install I had renamed hidden the app and frozen it. obviously before trying this update I unfroze and undid the hide/rename. but something seems to have gone amiss.

any clues?
[Google Pixel 6 Pro] V0latyle:
It sounds to me like you may still have two instances of Magisk installed. Magisk uses signature verification so that only one app can use the daemon.
[Google Pixel 6 Pro] whatsisnametake2:
hmm, I can't see any sign of the previously used renamed app name anywhere. any way to do a deeper uninstall of the app? if there's a hidden/renamed version still lurking how would I go about finding and getting rid of that? uninstall via adb?

never thought updating magisk would cause such problems!
[Google Pixel 6 Pro] V0latyle:
The only thing I can think of is go through Apps in your device settings. I'm not sure how to find it other than that.

Uninstall Magisk, reboot, then reinstall 26.1, and use Pixel Flasher to patch the boot image.
[Google Pixel 6 Pro] Lughnasadh:
Sound like you have 2 or more Magisk apps.

Uninstall all Magisk apps, hidden or otherwise. TB Checker from Play Store can help with that. Run the Xposed check in the app. Look for things that fail and Magisk package name. After uninstalling all Magisk apps, reboot and re-install the Magisk app you want to use.

My guess is when you unhid the Magisk app it didn't remove the stub. But not knowing your history you may have other Magsik apps in there so that is why I suggested to just uninstall all Magisk apps, hidden or otherwise, and start fresh.
[Google Pixel 6 Pro] whatsisnametake2:
thanks for your help guys. when I uninstall magisk and reboot, magisk still appears in the app list but with a generic android icon. running tb xposed checker it is still indeed finding the com.topjohnwu app. so it seems its not uninstalling correctly. try uninstalling via adb??
[Google Pixel 6 Pro] V0latyle:
You should be able to uninstall it. Long press on the icon, press the little information "i", tap Uninstall.

Just to be safe, reflash the stock (unpatched) boot image
[Google Pixel 6 Pro] whatsisnametake2:
ok so reflashing the unpatched boot allowed me to finally uninstall magisk. thought that was going to be it solved, but reflashed patched boot (i re patched the original boot img with the new magisk app ver26) and still got N/A next to "installed" in the app?? when I click on install it just gives me the option to patch a file, not the "direct" option i've seen before.

edit: is there an incompatibility with this andoid version (android 12 main release from june 22) and this version of magisk?
[Google Pixel 6 Pro] V0latyle:
Why are you so out of date?

There might be, try previous versions starting wtih 24.0
[Google Pixel 6 Pro] whatsisnametake2:
everything was working as I wanted (until the banking apps stopped working), so I just left it alone.

to wrap this up for anyone whoe might come across this - it was the magisk version was the problem. my android build wouldn't work with latest magisk versions. switched back to the same magisk version I was using before (24305) and it was fine.

so I'll probably update to latest A13. what is the latest with flashing A13 from A12? I remember there was a thing about having to flash the boot img to both slots. is that still necessary? and do I still patch the boot.img? I seem to remeber talk of patching the bootloader img at some point?
[Google Pixel 6 Pro] Nergal di Cuthah:
Bootloader needs to be flahed to both slots before flashing rom (to one slot). you WILL hardbrick (need to send in) if you do not. See pinned message at the top of this board

https://xdaforums.com/t/warning-read-this-before-your-initial-upgrade-to-android-13.4482091/
[Google Pixel 6 Pro] V0latyle:
Flash the latest update to both slots using PixelFlasher. You may want to update to Magisk 25.2 minimum.
[Google Pixel 6 Pro] liber:
Hi,

Has someone installes A14 QPR1 ?

Problems with root ?

thanks
[Google Pixel 6 Pro] Lughnasadh:
No problems with Canary 26301 on this device and Stable 26.3 on a Pixel Pro 7 for me. Just make sure any mods you use are compatible with A14 QPR1 Beta 1.
[Google Pixel 6 Pro] Nicolas....:
Hello,

I meet some problems with Microsoft Intune, so I uninstall the root, but it don't solve my problem because it detect the bootloader is unlock.

So, I want reinstall the root : the first time, I root the rom with raven_beta-upb2.230407.014. So I have the image and I create the magisk_patched.****.img from this rom.

Between I update via OTA, and now I'm on the 5th release (upb5.230623.003). The image isn't on google dev website. Can I use the same magisk_patched.****.img as the first time ?

Thanks
[Google Pixel 6 Pro] V0latyle:
Removing root won't solve problems like this; you'd have to flash factory firmware and relock the bootloader if you're going to go that route.

But, before you go that far, always look for a solution that requires the least amount of work. You need to check your Play Integrity responses. I would guess that because you're running the beta, the device fingerprint is failing.

See here:

[INFO] Play Integrity API - replacement for SafetyNet

THIS IS NOT A SUPPORT THREAD. For questions and support regarding how to fix your Play Integrity verdicts, see the Play Integrity Fix thread. ⚠️BEFORE YOU ASK A QUESTION, READ THIS POST AND THE FAQ!⚠️ ****Update 12/11/23**** Google has been...

xdaforums.com

As for re-rooting, I have no idea what you did wrong. This is why it's generally a good idea to ask for help before you start changing things.
[Google Pixel 6 Pro] Nicolas....:
I understand, root my device will not solve my problem of integrity but I want keep my bootloader unlock. So, if Microsoft Intune don't work without root with an unlock bootloader, I prefer have the avantages of a root device.

So I want re-root my phone, but I don't know if I can use the same file magisk_patched.****.img because I created the img with the factory image of first release of Android 14, and now my phone is on the last release (5). I can't re-do the img, because Google don't publish the factory image of the release 5, but just the 1. I use an ota update to go from the 1 to the last release.

Can I use my current magisk_partched***.img file with my new version ? Otherwise, where find the factory image of android 14, relase 5 upb5.230623.003 ?

Thanks for your help
[Google Pixel 6 Pro] V0latyle:
You should be able to live boot it, then perform Direct Install in Magisk.
[Google Pixel 6 Pro] Nicolas....:
I try, but Magisk only propose the installation by patching a file. Do you know if I can use an old magisk_patch.img created from another release factory image?
[Google Pixel 6 Pro] V0latyle:
Again, you need to live boot the previous patched image:

fastboot boot magisk_patched-*****.img

This commands the phone to immediately boot the image instead of flashing it. This should be sufficient to give you temproary root so you can perform Direct Install.

Did you happen to have the Magisk app hidden/disguised before you tried all this?
[Google Pixel 6 Pro] ROMAD27:
Has anyone been successful in rooting Android 14 on the Pixel 6 Pro? I updated to Android 14 by sideloading the OTA, extracting the boot.img. I patched the boot.img with Magisk 26.3 and booted to the patched image. I had root during that time and did the direct install, but lost root after a reboot. Now, no matter what method I try, I cannot get root back.

FWIW, Magisk was unhidden and all modules disabled prior to sideloading the OTA.

The phone works fine otherwise, just no root.
[Google Pixel 6 Pro] niko26:
Have you tried using the Pixel Flasher? That tools makes it so easy to root! And it's foolproof ;)
[Google Pixel 6 Pro] V0latyle:
Update method shouldn't matter.

Since you had Magisk hidden, it sounds to me like you might have two instances of Magisk installed. Go through your apps carefully and remove both of them; restart the phone and reinstall Magisk.
[Google Pixel 6 Pro] ROMAD27:
I did unhide Magisk prior to the OTA. I've tried several other methods, including Pixel Flasher and going to Magisk Canary 26302. None will even give temporary root.
[Google Pixel 6 Pro] V0latyle:
Still, I think you have a stub somewhere. Try what I suggested - search through your apps (use the Apps section in Settings) and make sure you only have one instance of Magisk.

Are you able to get root if you live boot the patched image? If so, it seems Direct Install didn't work properly, so just flash the patched image to /boot.
[Google Pixel 6 Pro] ROMAD27:
I agree, that's what I thought too: there must be something of Magisk left. I've uninstalled Magisk several times and don't see any remnants of it. I've also flashed the patched boot image as well as booted to it, then re-flashed the Android 14 boot.img and then re-flashed the Magisk one, all with no success.

I've also redone the OTA sideload about 4-5 times, trying to start as "fresh" as I can without actually wiping it.

I'm fairly confident that a wipe will fix this, but was trying to avoid that if possible.
[Google Pixel 6 Pro] V0latyle:
A wipe will definitely fix it. The only thing different about Android 14 is that we need Magisk 26.1+ for it. Everyone else has been able to update and root without a problem so I am 98% sure you have a forgotten Magisk stub somewhere. @zgfg, @ipdev or @pndwal, any input?
[Google Pixel 6 Pro] pndwal:
So Magisk Installed = NA?

What does Magisk -c from a terminal emulator return?... PW
[Google Pixel 6 Pro] ROMAD27:
Hmm, from $ prompt,"magisk -c" returns no command found. I do currently have Magisk installed right now.
[Google Pixel 6 Pro] simplepinoi177:
Can't you find stubs or other instances using Momo or TB Checker?
[Google Pixel 6 Pro] ROMAD27:
Uninstalled Magisk, rebooted. TB Checker doesn't seem to find it either.

Checked "Magisk Random Package name" under Xposed in TB Checker. I see this:

Not sure about that one though.

~~~~~~~~~~~~~~~~~~~~~

Update: Yep, there was still a "Settings" app leftover from Magisk. Deleted that, rebooted. Back into ADB and booted to my previously patched Magisk file. Got root, direct install, have root again.

For anyone running into similar, look for your renamed Magisk app and remove it. Thanks for all the help! Saved me a wipe!
[Google Pixel 6 Pro] V0latyle:
Told ya 😉
[Google Pixel 6 Pro] pndwal:
Good for you...

... You weren't using Termux for this then were you? PW
[Google Pixel 6 Pro] ROMAD27:
Yes, is there something better? I'll switch to that.
[Google Pixel 6 Pro] pndwal:
No.. (Termux is better for complex stuff for experienced users), I just didn't say to avoid Termux for this... I've said it so often...

When a TE is called for, it's best to use just that... Termux is much more... It's a whole Linux environment with a TE, and things work differently without specifying complete paths etc...

For general use, any basic TE from Play Store etc will work as expected CLI (ie with basic commands) with standard Magisk/Android Linux environment...

🤠 PW
[Google Pixel 6 Pro] Nergal di Cuthah:
I got an error running the magisk -c

Then i typed su first and then magisk -c and got a result (using "terminal emulator" from fdroid)
[Google Pixel 6 Pro] simplepinoi177:
Ha! I knew one of them is capable of finding the leftover! Normally I hyperlink them and make sure what I'm suggesting is accurate, but I just wanted to drop in and suggest, so I'm really glad it worked out!

It seems that when all the experienced experts/members speak on other "instances" of Magisk, this is what we mean; when it is hidden and renamed (usually the user has forgotten or it has slipped user's mind) -- I'm sorry we weren't clearer on that, but it's a troubleshooting resolution ran into quite often and it's easy to take it for granted to be aware of...

I'm super glad I helped and saved you the wipe....I completely understand and absolutely loathe setting things back from a factory reset...!
[Google Pixel 6 Pro] dilligaf56:
Went to use Google Pay last night and got the red exclamation point - "your device does not meet security requirements". It worked fine a few days ago. On A14, rooted of course, latest Magisk and SafetyNetFix mod (2.0) module installed, DenyList is OK. WTF? I don't think the GooglePay app was updated in the meantime. Integrity Checker says only BASIC_INTEGRITY passes now, previously DEVICE_INTEGRITY did also. Anyone else seen this?
[Google Pixel 6 Pro] Lughnasadh:
Yes, know issue for several days. Use this instead of USNF (2.0).
[Google Pixel 6 Pro] Nergal di Cuthah:
Use latest Play integrity fix (12.1 at the time of this post) to replace usnf (it will uninstall usnf if you install it i believe)

Edit ninja'd
[Google Pixel 6 Pro] iwearthebelt:
I've been using this fix for about 24 hours now and it works good. One thing I've noticed though is if you check integrity more than the initial update it may fail. If you come across this issue just install it one more time and leave it, it will be fine. Just for reference I updated to V12.3 and that works good too. Looks like the Dev is doing a good job and keeps updating the module as Google throws a wrench at it.
[Google Pixel 6 Pro] nil?:
Could one with a working PIF (Play Integrity Fix) module please share some details about the setup used? In have: stock A14 (UP1A), Magisk 26.4, LSPosed 1.9.2 (7024), PIF 12.3, and Magisk says that "Zygisk module not loaded due to incompatibility". Do I need to migrate to ZygiskNext with KernelSU?
[Google Pixel 6 Pro] V0latyle:
It's probably due to LSposed.
[Google Pixel 6 Pro] nil?:
I disabled LSPosed, and nothing changed with PIF after reboot.

This thread seems dead, where is the point of discussion for urgent problems? I don't believe I am the only person on this planet who uses rooted P6P and suffer nowadays because of inability to pay with the GPay.
[Google Pixel 6 Pro] Nergal di Cuthah:
If i remember correctly lsposed leaves folders and/or files behind after uninstall. Maybe someone in the lsposed thread can help. I have a p6p on Canary magisk with no gpay troubles. I use no extra addons only PIF 12.3
[Google Pixel 6 Pro] iwearthebelt:
Look at my post about 3 above yours, I've been using it for a few days now without any issues. Let me know if you get it working, if not I'll see what I can do to help you. I'm on my way home now so give me a few to get there...
[Google Pixel 6 Pro] V0latyle:
The point of this thread is the guide in the OP and questions related thereto. Magisk and module troubleshooting doesn't really belong here.
[Google Pixel 6 Pro] nil?:
But my question is exactly about the guide in the OP as it doesn't work for SafetyNet pass anymore.
[Google Pixel 6 Pro] Nergal di Cuthah:
Other than PIF instead of displax mod usnf the guide works perfectly imho
[Google Pixel 6 Pro] V0latyle:
Did you miss this part?
[Google Pixel 6 Pro] nil?:
No, I don't. I don't ask you personally for any help if you misunderstand this. We're in the thread having 85 pages because previously here were discussions on how to pass SafetyNet once again after Google's fixes. Currently I found a new way to bypass that check here (PIF) and ask people for help as the way doesn't work for me because of some incompatibility.
[Google Pixel 6 Pro] Nergal di Cuthah:
You can rule out incompatibility of pif and p6p as i and many others run it fine. It comes down to lsposed or one of its modules i can almost guarantee
[Google Pixel 6 Pro] nil?:
I tried to completely disable LSPosed and the error persisted.

But could you or those distinguished gentlemen who run it fine describe your/their setup for poor me who can't run it to make it possible to look where is the difference? ROM version, Magisk version, maybe they use KernelSU instead of regular Magisk (I can't keep up with how fast the world is moving), maybe they install the module with a recovery (I have no custom recovery so I install modules via Magisk itself, Modules → Install from storage). Probably I'm missing something but I don't know what. I have no second Pixel to test and I'm doubt I have a reliable way to backup the whole device state not just a bunch of partitions I'd have to juggle later.

About a week ago I had USNF and all was good, then GPay stopped working, I installed PIF, saw an error, upgdaded Magisk to latest release and... and I'm here. Not only module doesn't work but also Magisk displays no data about author and version, looks like a parsing problem or so.

I have this in Magisk logs related to PIF and it doesn't work:

rg -a integrity magisk_log_2023-11-15T03.06.17.log
1429:11-15 02:57:03.706 899 899 I : playintegrityfix: exec [post-fs-data.sh]
1433:11-15 02:57:03.713 892 894 I : playintegrityfix: loading [system.prop]
1442:11-15 02:57:04.877 892 894 I : playintegrityfix: exec [service.sh]
[Google Pixel 6 Pro] Nergal di Cuthah:
As i said my setup is basic

Stock (no kernal, no overlays no nothing except systemless hosts) rooted with magisk canary 26401

Pif 12.3

No lsposed no shamiko no nothing.

Question for you, are you clearing data from gpay when you reach play integrity passes in device and basic? Are you even clearing play integrity.
[Google Pixel 6 Pro] Nergal di Cuthah:
Google flipped a switch and everybody failed pif 12+ fixed it.

You, must as i insinuated, clear data from gpay everytime you apply a fix, until it fixes
[Google Pixel 6 Pro] nil?:
I don't clean nothing as I don't get the module loaded. Cleaning these things mean I need to add all of my cards again, log in to my apps again etc, so I'd go to this step only after I got the module loaded without an error.
[Google Pixel 6 Pro] Nergal di Cuthah:
Don't know why module doesn't work, post in modules thread (I'm there too) are you on latest magisk maybe try beta or canary (i don't think latest is in stable yet). Do you have other modules? Remind us what lsposed modules you're using yes i understand you disabled it but it's good to know still. Did you clear gpaydata after you disabled it? Yes this is necessary sorry but it is.
[Google Pixel 6 Pro] majorfigjam:
I was exactly the same, found I was failing checks, and then PIF 12.1 (or 12.2 or 12.3) solved it.

I have stock November update on a P6Pro, updated by OTA method, rooted with Magisk Canary 26410, Kirisakura kernel, and the additional following modules -charging limit, bootloop protector, PIF 12.3, Shamiko and Systemless Debloater. It worked fine before Google switched something, and it works fine since I updated to PIF 12.1.

Once you get rid of every last trace of LSPosed, then go into Airplane mode, clear data from GPay, Play Store etc and then reboot.

Or, to answer your original question, which was "... where is the point of discussion for urgent problems?" then look here:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/ or

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/ or

Magisk General Support / Discussion

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread

xdaforums.com
[Google Pixel 6 Pro] nil?:
What is Magisk Canary? Did you mean Magisk Delta Canary or so?

I actually don't understand where do you get these versions.

I tried app-release.apk from the latest github action in TJW's repo and it's 26400; I tried app-release.apk from huskydg's website (by Download Canary link) and it's 26301.

And with clean Magisk install without LSPosed at all I still see this instead of correctly displayed and loaded module:
[Google Pixel 6 Pro] nil?:
So I moved to Magisk Delta, no LSPosed, no other modules (just hosts). It's totally broken, apps that are in the sulist and allowed in Superuser tab don't have root access... and I still can't get the PIF work nor pass SN. Cleared data for Wallet, Play, Play Services, no way. Still can't understand what's wrong with modules metadata parser. It's the same .zip with modules from my device with more old version of Magisk, but no info except for name displayed.

UPD: I found a reason, my Magisk installation was full of zero-filled files. I don't know how that weird thing can survive several reinstalls and what was the root cause but since the moment I keep an eye on Magisk files during all of my manipulations nothing bad happened and I got PIF working.
[Google Pixel 6 Pro] Nergal di Cuthah:
Canary is one step above beta. You have to get the canary from magisk github i believe.

Delta and alpha are forks of magisk, canary is a pre-beta
[Google Pixel 6 Pro] Nergal di Cuthah:
https://github.com/topjohnwu/Magisk canary under downloads, however canary is likely to at times be instable or cause issues (i have never had problems (that weren't immediately rectified by TJW) but it is experimental level usage (ie if you have issues you install the debug version and take copious logs or remain silent and wait for a fix))
[Google Pixel 6 Pro] V0latyle:
I just stick with stable and let everyone else be the guinea pigs.
[Google Pixel 6 Pro] dilligaf56:
That fixed it. Thanks, much appreciated!
[Google Pixel 6 Pro] luis181193:
Releases · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

Working safety check fix, can use google wallet now
[Google Pixel 6 Pro] mhrussell1:
Getting a BL with Magisk 27001 and March update. Cannot communicate with phone to reload once I have forced it into Fastboot Mode.

Update:

Just decided to try running the flash-all.bat script again and the first time failed but then I was able to see the device in adb and running the flash-all.bat again got me back to a clean install without Magisk.
[Google Pixel 6 Pro] V0latyle:
BL meaning boot loop?

Strange problem, you should always be able to communicate with the device in bootloader mode.

I would have started by reflashing the stock boot image.

What version of Platform Tools are you using?