Troubles With Latest Android Monthly Patch (Pixel 3) - Magisk

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).

Related

[Ask][Troubleshooting] Magisk Makes the ROM Super Laggy

What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
I have Resurrectionremix and Magisk 14.3
No any lag on my phone.
Tapatalk - Xiaomi Mi6
You need to list what modules you're using.
BIGWORM said:
You need to list what modules you're using.
Click to expand...
Click to collapse
I only flash the ROM, GApps and Magisk without any additional flashable ZIPs.
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
yung40oz84 said:
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
Click to expand...
Click to collapse
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
irfanfadilah said:
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
Click to expand...
Click to collapse
Ya I was gonna say cause I use all AOSP and CAF based
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Danilo-Sanchez said:
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Click to expand...
Click to collapse
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
Yes.
Try it and let me know if this also fix the problem for you.
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
dragos281993 said:
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
Click to expand...
Click to collapse
I'm glad I'm not the only one experienced this issue, that's mean it's not entirely user fault. Maybe you're right, on more high-spec phones they won't really notice the lags/stutters.
Looking forward to the news/updates regarding this issue.
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Camandros said:
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Click to expand...
Click to collapse
I haven't got the chance to try it.
Currently I'm using SuperSU to root my device.
I tried installing magisk on my currently in use ROM, i.e., a long time after flashing it, and although it got less laggy, there still was a heavy lag impact in some applications. Maybe it has less impact on lineage or on lighter ROMs? I'm using official LG nougat.
I'm using Mi 6 in Xiaomi.eu rom
YES, magisk causing laggy.
Same here
Mi5, tested on MIUI 9 and 10
Without Magisk everything was great and after flashing Magisk, the phone got laggy!
I have the same problem with my LG G6
interesting, first I thought that emmc will be broken. because the problem is the same (lag). but after i replace emmc, all back is fine. I just think emmc is broken because it is often flashing rom.
ChessPiece said:
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
Click to expand...
Click to collapse
what magisk version 16.0 or beta? magisk can't make the phone lag but kernel or something in ROM may interrupt try to change kernel or flash the lastest Gapps

Magisk 20 update issue(s)?

I have Magisk 20.1 (Magisk Manager 7.5.1) currently installed on my Samsung Galaxy Tab A (2016). While initially installing it was not as straight forward as it might have been (install doc could use some work; I think it's written for folks with more familiarity with android devices on a day to day basis than those who root a phone maybe once every few years); I installed Magisk and it's been working fine.
However, this morning I had a notification that I needed to run Magisk setup. I told it to do so; it downloaded something; rebooted the tablet ( which wasn't warned of in the notification); and on coming back up ran Busybox so I'm assuming that was the setup. Going into Magisk Manager, however, I got the same notification over again. So I let it update again with the same result.
This time I told it to cancel the update/setup. I then tried to manually do the update from 20.1 (20100) to 20.3 (20300, latest available version). Update proceeded normally until repacking; which failed. Since Magisk is already installed and working (with several root level apps) on this phone; I can't see where this could be the "wrong image problem" which seems to be the most prevalent root cause of this kind of error. Unfortunately the update as distributed doesn't say anything about *why* it can't repack the image; so the message doesn't help us ordinary folks in debugging.
Any ideas as to what the actual issue is?
Android info:
Version 8.1.0
Kernel 3.18.14-1570595
Build M1AJQ.T580UEU4CSC1
Note: Busybox had an update I believe came out sometime yesterday (saw notification it updated successfully). Could it be that something in the Busybox update broke the Magisk update process?

CTS Profile Mismatch after updating Magisk

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.

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

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