CTS Profile Mismatch after updating Magisk - Google Pixel 4 XL Questions & Answers

Hey guys. Apologies for the username.. not sure when I made that :laugh:
I was running stable on the 007.a3 image with Magisk v20.1 and Manager 7.4.0 when I made the terrible mistake of trying to update them. Since then, I've flashed the factory 200205.002 image in an attempt to get back to a stable setup, but I'm running into errors getting the CTS verification to go green, on a totally blank slate - even if I roll it all back to 007.a3 and the old boot image. I've tried the Props Config module from Didgeridoohan to no avail, and pretty much every (unlocked) factory image that exists. I'm half ready to throw in the towel and send it back under warranty, but I'm less than keen on waiting 7-10 days for what could amount to a simple firmware fix.
To recap: I've tried flashing factory firmware with a full wipe, different versions of Magisk and its Manager, Props Config module (assigned the build number for 200305.003, no bueno), Core-only Mode, toggling Magisk Hide on and off plus targeting the Play Store, and no small amount of frustrated sighing. Hasn't budged an inch.
Curiously, on any image I flash, the Bootloader unlock toggle is grayed out and can't be interacted with - but, the bootloader is still unlocked. Any thoughts on that?
EDIT: Neat. Bootloader toggle is working as normal now, on 200205.002. No idea what did it but hey.
Second edit: Just noticed that the latest few pages of MagiskHide Props is about this same issue. Sorry guys, didn't see it.

I have this problem as well. I think we just have to wait for Magisk to patch this for us

Good to see I'm not crazy. I happened to reset my phone and this issue came up, so I thought I did a bad.

Related

Troubles With Latest Android Monthly Patch (Pixel 3)

I'm having issues with Magisk on my Pixel 3 after installing the latest Android monthly patch.
The first issue:
Even with latest Canary build I was not able to patch the boot image...it looked like it worked but the image was the same size as the original and booting it did not give me root. I'm pretty sure this issue was occurring before the Android update, since I patched the boot.img before performing the update (but did not notice any issue with it until after the upgrade was complete). So I used an old patched boot image I had (unfortunately not the latest Magisk version), which booted and gave me root (and allowed me to do a direct install of latest)...but that leads to the second issue.
Second issue:
No sound! None at all. No UI sounds, video plays with no sound, etc. Have not tried a phone call yet. If I flash the stock boot image everything works fine, so it has something to do with the Magisk patched boot image. This occurs both with the old version I had and the latest canary version (direct installed over the old version). Not sure if it's related, but right after entering my login PIN it always says "System UI isn't responding," which also does not occur with stock boot image.
Update: I'm getting a bajillion of these firing multiple times per-second in logcat: 2020-12-08 10:14:04.521 1437-4414/? E/AudioSystem-JNI: AudioSystem::listAudioPorts error -19
Thanks in advance for any help you can provide. Happy to provide any logs or anything you think might be helpful to troubleshoot.
My first guess would be that it's one of your modules that's causing problems (that's usually the case when experiencing device issues after updating the OS). Disable the modules and try again.
Didgeridoohan said:
My first guess would be that it's one of your modules that's causing problems (that's usually the case when experiencing device issues after updating the OS). Disable the modules and try again.
Click to expand...
Click to collapse
I had not tried that...but unfortunately after doing so the issue still persists (I only had one module enabled -- the props config to make ctsProfile pass).

Note9 Randomly Reboots and Partly Goes Back to a Previous State

Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem.
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
If you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Maspon said:
Hey guys!
I recently flashed my Galaxy Note9 (SM-N960F, One UI 2.5) with TWRP and Magisk, all being the latest version. However my phone would just reboot randomly and I could barely find a pattern. I could only infer that the reboot is system level since most of the time I was launching a system-level app like Bixby, Torch, or just simply swipe down the notification panel. If related, 19:30 seems to be the time my phone would definitely reboot recently.
By ''partly goes back to a previous state' I mean some of my apps would be replaced to their factory version. Like I used YouTube Vanced, and after this one reboot it went back to its factory version. And Gboard was exiled of all its permissions once. My Edge Panel was reset after one boot. Some of the adb tweaks were reset.
I'm half sure this is a kernel problem, and the only modifications I did to my kernel were Magisk and Universal DM-Verity. I don't know if it's a DM-Verity problem or I just disabled too many system apps (Galaxy Themes, Bixby Service, Galaxy Friends and stuff).
I tried to disable my root permission for apps but it didn't help. Also Googled how to catch system logs but none of these worked.
Whether you're experiencing the same problem or have an idea of how to solve this issue please feel free to leave a comment!
Click to expand...
Click to collapse
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
xfakexbloodx said:
Happened to me as well few months ago.
I suspect it is related to safetynetfix or hideprop. I used safetynetfix for samsung, and update latest hideprop, now i never experienced the random reboot.
Click to expand...
Click to collapse
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Maspon said:
Thanks for the reply! I just flashed Universal SafetyNet Fix. Now my phone is stuck in bootloop. It would just reboot infinitely. May I possibly get the SafetyNet Fix you're using?
Click to expand...
Click to collapse
Based on this post
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
xfakexbloodx said:
Based on this post
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Try to read each page, some people say it works, some people say it doesn't. I've tried and updating my magiskhide prop and it works.
Click to expand...
Click to collapse
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Maspon said:
Thanks a lot! My phone now boots normaly and it's a Success on SafetyNet. Hope no more random reboots afterwards.
I'm particularly curious what variant of DM-Verity did you use? I googled for DM-Verity for Samsung this morning and did get a Samsung-only patch. I'm not sure if DM-Verity patch could contribute to these reboots.
Click to expand...
Click to collapse
Sorry no idea about that. I'm using alexis rom though..
xfakexbloodx said:
Sorry no idea about that. I'm using alexis rom though..
Click to expand...
Click to collapse
Sadly my phone still rebooted this morning. I caught the last kernel message and I hope it will help

A71 Data & Root Issues

Hello,
The last couple of months and completely out of no where my 4g data randomly stops working. The status bar icon shows that it's stuck on upload and won't download any data. The only way I've found to fix it outside of restarting the phone is to change the cell band type from auto to wcdma then back.
Anyone have any ideas on how to fix this?
Second issue is with Magisk and I know this is for Samsung but I figure why not ask anyway. As of yesterday after a reboot I lost root. Magisk apps shows I need to install magisk and install the app even though I'm in the app. Also a bunch of my apps are acting like I've never uzed them before and they need to be setup again. I haven't installed any updates so I'm not sure what caused it.
I've tried completely uninstalling Magisk and reinstall and that didn't do anything. The install went through fine but after launching the app it still says no root.
Any ideas?
Thanks
Hi, I think it has been updated and Magisk is useless due to new layers of security. I guess we'll wait until a new rom is made for the new update, including stock. I don't know if Magisk can release a new version and overcome this.
Thanks.
Reflashing the custom firmware then also Reflashing Magisk did get it working for me again.
I've since updated to the newest firmware, flashed OneOS and Magisk and it's been working fine until a little while ago when Magisk randomly shows as not installed again after a reboot.
I take it no one else has had this issue still?
Thanks

S10 bootloop, when restarting

Hey, everybody. First post. I need some serious help. I've been rooting and modding for years, but I don't know everything, so please don't assume that I do. Right, my Exynos G973F is rooted with Thunderstorm Kernel, and has TWRP installed. The phone functions perfectly and all of my apps pass root detection. However, if I restart the phone, it gets to the point where all my icons load and I can use the phone, then it suddenly goes back to the Samsung logo. The case used to be that if I left it long enough, it wouldn't continue to bootloop, but recently I'm having to restore TWRP images just to use my phone. I've done a factory reset, and tried to do the same thing with a custom kernel, but it will not pass safetynet. I've got Riru installed, LSExposed, safetynet patch 2.2.0 and Magisk Hide patch, with a different fingerprint set, and it absolutely won't pass cts. So, starting from scratch is not an option, because I've tried everything. How can I figure out what's making it bootloop? As I've said, the phone is perfect, other than this. It's really bizarre. Hope someone can help! Thanks in advance!

Question [issue] GrapheneOS, Magisk and June update [SOLVED]

The latest OTA update made my phone bootloop if i re-flash magisk patched init_boot image...
After I asked Stock users, it looks like it's a GrapheneOS june update + Magisk specific issue.
Do someone else also have this issue?
Phone boots normally, then reboot to recovery instead of reaching lock screen.
For now, I re-flashed panther-factory-2023061402 init_boot.
Have you tried Magisk canary version? or maybe GrapheneOS doesn't like june update and newest Magisk and you need to either go back down to stable Magisk or an older version of Magisk?
Actually, after re-reading your OP, a module might be the cause of the bootloop -- I've recently seen similar behavior from other members where device bootloops or crashes during/right-after loading & starting up -- if you were on the stock ROM I would suggest you loading up in Safe Mode to see if it is a module issue; I don't know anything about GrapheneOS so I don't know if it offers anything similar. I wonder if the adb command to remove modules at boot would work....
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Albirew said:
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Click to expand...
Click to collapse
knew it....
glad I helped get you there!

Categories

Resources