[Google Pixel 7 Pro] simplepinoi177:
If you are very concerned, I might try uninstalling Magisk and installing a Magisk Canary version (it’s experimental, but the absolute bleeding-edge version of it might address the glitch/issue; and/or it might act as a proper re-install to install over the bug)

Mmmm….if you’re talking about Magisk, Magisk is a very special more-than-ordinary “Android app” (I mean, it gets to be since it has “root” access). It will persist unless you factory wipe – Magisk and its modules reside separately in the root directory; and I imagine that factory wiping is the only thing that wipes that. So I believe the storage and cache stored in the OS may not completely connect with all the other settings/data it handles.

I believe that’s where it would show up if you did have another instance; but I’m not certain for sure as I’ve never needed to look myself – I just read of situations that called for looking for them in such a way and that was the method used; I don’t recall how exactly it results when there are other instances.

I believe TB Checker is an app that just “checks” if things are found and/or triggered – if a rooted app/service is properly removed, not-installed, or hidden (purposely), it will show as Pass; if it is installed or a remnant remain or not hidden properly, it will “Fail”. So, basically, the app detects that Magisk (com.topjohnwu.magisk) and Lucky Patcher are on the system.

The main point of the app is to confirm if all you’re hiding (whether to pass security checks or literal root detection hiding) is working and not triggering – not just SafetyNet or Play Integrity API checks, but if one wishes to hide particular other root apps as well (like that Lucky Patcher, or LSPosed, or whatever else might trigger root detection). So it’s not quite a “Fail” in terms of those apps/services not working or applying properly.

I think you’ll be happy with it. You shouldn’t expect any “crashes” – those usually only happen when the user neglects/overlooks the changes that they’ve done previously with custom kernels or Magisk hiding/un-hiding or not disabling all the modules. Under normal circumstances, PF/badabing2003 makes sure to do all the checks, double-checks, verification, and everything else to mitigate slip-ups like that happening. If your setup isn’t too complicated and you usually simply just do a “reflash with platform tools…into…fastboot mode”, then PF does basically all of that in just an automated way (with certain checks) and roots for you as well.

I don’t know anything about emulators or virtual machines in relation to Android or Magisk, but as I understand it, Magisk works best (meaning with the least amount of issues) when you patch the image on the device you plan on applying it to; I know PF can do it standalone, but I imagine it still takes a particular considerations than a regular emulator does to get it patched correctly. In the end, this explains why it doesn’t come out identical.

I’m going off of the assumption that you are patching the image on your emulator and applying/comparing it to your phone; if I’m misunderstanding, sorry for the confusion.

That could easily be the explanation. I know what you mean though – I’m sorry to hear you were one of those that got caught in that mess of the new platform-tools messing things up – but I don’t imagine the old version and new version would be much different when flashing an image to the init_boot partition.

But I would be surprised if Google didn’t fix it under warranty – like you said, it was months ago (so within the manufacturing year) and the Pixel is one of the easiest smartphones to flash partitions (unlock the bootloader) by intention by Google; so I would think they would be accepting of such circumstances since they allow (and almost encourage) it.

Wait, Pixel6?! Like I mentioned above, Magisk patches based off of the device it’s installed on – why would/should a patched file from another device (most notably another model) be identical than the one PixelFlasher “spit[s] out”? PixelFlasher itself doesn’t do the patching, it runs it through Magisk, so essentially it’s what Magisk “spit[s] out” than it is PF. In any case, Pixel6 image, whether it worked or not, shouldn’t be expected to be identical to a Magisk patched one from the Pixel 7 Pro.

No doubt he’s very busy – and for what it’s worth, he hasn’t been active in engagement/support here or elsewhere for a while.

But you really should/would find experts here that should be able to help, assist, and illuminate it for you – case in point, badabing2003 wouldnt’ve been able to make such a great successful program if he wasn’t an expert at patching and flashing Magisk; if not him there are many others here that are very knowledgeable that with their deep knowledge/experience might provide insight that would lead you to where topjohnwu would’ve….

Verity and Verification is only required if you were planning on employing a custom kernel. I just mentioned it because as you were speaking on bemoaning if you had to wipe, I wanted you to be aware that if you so chose later on to flash a custom kernel, this would be a requirement.

Of course! I’m very happy to!