Hello, I have the following problem, the operating system and the Greenify application worked very well on Magisk v22.1, but after updating to v23.0, there are problems, the operating system itself on the phone is slow and in the Greenify application, I am dissatisfied with this update v23.0 .
Please help what can be done about it.
My HTC U11, Stock ROM.
Greetings.
Noticed this on my Pixel 3 running stock as well. I would have to restart the phone several times to get it running.
GrandAdmiral said:
Noticed this on my Pixel 3 running stock as well. I would have to restart the phone several times to get it running.
Click to expand...
Click to collapse
I understand it turns out there is a problem with this v23.0 update, I wonder who else has a problem with it, besides us.
I'm not seeing any similar issues on v23 (and haven't on the canary releases leading up to it either). That doesn't mean there isn't a possible issue though...
Have you guys checked your modules if there's a possible culprit there?
Didgeridoohan said:
I'm not seeing any similar issues on v23 (and haven't on the canary releases leading up to it either). That doesn't mean there isn't a possible issue though...
Have you guys checked your modules if there's a possible culprit there?
Click to expand...
Click to collapse
I only have these modules and they were on v22.1, they did not cause any problems like this v23.0.
That the modules worked fine in earlier releases doesn't necessarily mean that they work on current/future release...
You need to do some troubleshooting if you're interested in getting to the bottom of this.
Disable modules to figure out if it's one of those. Disable MagiskHide to see if it's connected to that. Etc...
Didgeridoohan said:
That the modules worked fine in earlier releases doesn't necessarily mean that they work on current/future release...
You need to do some troubleshooting if you're interested in getting to the bottom of this.
Disable modules to figure out if it's one of those. Disable MagiskHide to see if it's connected to that. Etc...
Click to expand...
Click to collapse
It may be that the module may not work properly on this v23.0.
Okay, I will follow your suggestion on what to do with it, I'll check it out and let you know.
From the very beginning, MagiskHide is turned off.
MagiskHide off, module turned off, Riru, Riru - Edxposed, phone restart, phone working, fast as it was on v.22.1, probably something is wrong with these modules.
Sounds like EdXposed is causing some issues then... You might want to check the Xposed forums and/or EdXposed Github issues to see if there's some mention of similar problems there.
Didgeridoohan said:
Sounds like EdXposed is causing some issues then... You might want to check the Xposed forums and/or EdXposed Github issues to see if there's some mention of similar problems there.
Click to expand...
Click to collapse
I will check the forums, maybe I will come across something, and if not, I will also write a post there, maybe a new update of these modules will fix something.
Thanks for your interest in the topic.
Related
....!!!!PLEASE ONLY POST ABOUT XPOSED AND MODULES YOU ARE USING ON AT&T STOCK FIRMWARE NOT THE UNLOCKED U FIRMWARE AS THERE MAY BE DIFFERENCES IN EXPERIENCE AND USABILITY THAT MAY CAUSE PROBLEMS!!!!....
This thread is for anyone to posted what Xposed modules you use and if they are or are not working. It will also be a thread to let others see who are new to xposed or havent used it on their s7 edge yet what is and isn't working as well as identifying what modules should be avoided because they are causing problems with the phone ex. lag, freezing, bootloops, other. please comment what you are using along with your experience and any news related to xposed and or modules. i will (when i have time) edit this post with what i have installed what does and doesnt work as well as posting what others put here. of course there will be a working and not working section that will be updated when things break or become useable. hope this thread helps some people out and saves some time and trouble.
....AGAIN!!!!PLEASE ONLY POST ABOUT XPOSED AND THE MODULES YOU ARE USING ON STOCK AT&T FIRMWARE ONLY AS THERE CAN BE DIFFERENCES BETWEEN WHAT DOES AND DOESNT WORK ON STOCK FIRMWARE AND THE UNLOCKED U FIRMWARE!!!!....
....WORKING MODULES ARE IN POST #2....
....modules that work for me and or others....will be update as i use working modules or people post or pm working modules....i will not be including modules that do not work just to save time and space. At this point in time just assume it doesnt work unless someone can confirm it, dont want to kill your phone!!!!....
1. Greenify
2. Amplify
3. Xtouchwiz (turned some setting off that were on by default!!!! Fake system status i'm guessing is best turned off!!!!)
4. Neopower menu
rob219 said:
****ONLY ANPLIFY AND GREENIFY ARE WOTKING OUT OF THE ONES I HAVE INSTALLED IN THE PICS, ALL THE OTHER MODULES SHOWN ARE NOT WORKING AS OF NOW ON MY DEVICE****
Click to expand...
Click to collapse
Did you have any luck with RootCloak or XTouchWiz?
TehPirate_ said:
Did you have any luck with RootCloak or XTouchWiz?
Click to expand...
Click to collapse
rootcloak im unsure as i have uninstalled it (didnt need it) and xtouchwiz i hacent retried. something (maybe a setting in xtouchwiz) was giving me some sim card pop up that wouodnt go away on boot and wouod make me reboot to recovery to do something to ky sim that just failed and the pop up would be there upon boot. i had to odin to get rid of it. it happened 3 times and each time it happened i had rootcloak and xtouchwiz installed. since removing both i hacent had a problem. so no i didnt and i believe one of them caused the problem. if anyone is using both or one or the other let me know what you do and dont have enabled or disabled in each module.
rob219 said:
rootcloak im unsure as i have uninstalled it (didnt need it) and xtouchwiz i hacent retried. something (maybe a setting in xtouchwiz) was giving me some sim card pop up that wouodnt go away on boot and wouod make me reboot to recovery to do something to ky sim that just failed and the pop up would be there upon boot. i had to odin to get rid of it. it happened 3 times and each time it happened i had rootcloak and xtouchwiz installed. since removing both i hacent had a problem. so no i didnt and i believe one of them caused the problem. if anyone is using both or one or the other let me know what you do and dont have enabled or disabled in each module.
Click to expand...
Click to collapse
I appreciate your feedback. It would be inaccurate for me to reply with mine as I use the unlocked firmware. But in this case, the results were the same more or less.
TehPirate_ said:
I appreciate your feedback. It would be inaccurate for me to reply with mine as I use the unlocked firmware. But in this case, the results were the same more or less.
Click to expand...
Click to collapse
i have since installed xtouchwiz and have no problems i turned a few things off that were on by default. i turned off fake system status and the disable scaling feature that was on. it works. rootcloak i have also reinstalled but i don't think it works. im not sure, i know snapchat has problems logging in if your rooted and i am experiencing this problem with or without rootcloak so i believe it is not working but i could be wrong.
Hi, I am new to xda and Android as a whole. So I have rooted (SM-G935A) and I can't find any way to install xposed because TWRP doesnt support the snapdragon variants. Do you mind telling me how you did it?
RileyIssKing said:
Hi, I am new to xda and Android as a whole. So I have rooted (SM-G935A) and I can't find any way to install xposed because TWRP doesnt support the snapdragon variants. Do you mind telling me how you did it?
Click to expand...
Click to collapse
flashfire
I've an OP3T, and I mostly flash 8.1 ROMs. Since V15 came out, I've been having Module issues, they work sometimes and after a reboot, they disappear and they don't work. I've tried flash Magisk over and over again, and also clean flashing different ROMs. Modules do not work, although Root works.
Modules are;
AR stickers Calib files,
IYTBP
V4A for V15
Xposed V90-Beta1
I've also tried both ways of installing the Modules, from Recovery and from the MM app. Nothing works.
thes3usa said:
I've an OP3T, and I mostly flash 8.1 ROMs. Since V15 came out, I've been having Module issues, they work sometimes and after a reboot, they disappear and they don't work. I've tried flash Magisk over and over again, and also clean flashing different ROMs. Modules do not work, although Root works.
Modules are;
AR stickers Calib files,
IYTBP
V4A for V15
Xposed V90-Beta1
I've also tried both ways of installing the Modules, from Recovery and from the MM app. Nothing works.
Click to expand...
Click to collapse
It's an issue with op3t and custom roms. Lots of them, like Omni, etc. No one has posted useful logs or proper bug reports. Just a bunch of posts like this scattered everywhere. Post it in the proper magisk development thread with all logs and relevant info and it may get solved. There are enough ppl having the issue, just not enough info.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75212442
madbat99 said:
It's an issue with op3t and custom roms. Lots of them, like Omni, etc. No one has posted useful logs or proper bug reports. Just a bunch of posts like this scattered everywhere. Post it in the proper magisk development thread with all logs and relevant info and it may get solved. There are enough ppl having the issue, just not enough info.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post75212442
Click to expand...
Click to collapse
Actually I've found out what the issue is. It's the OP3/T Calibration CAD Files Module, which somehow not allowing my other modules to be run on boot. Not installing it worked for other modules.
P.S: I checked my Logs before posting, they didn't show anything out of the ordinary. My modules are supposed to be working as needed, but don't work.
Can you fill me in on how to get the logs?
I did figure out the problem- since Magisk didn't actually update when I tapped to update it, the modules available to install were under the "Downloads" section (found in the drop down menu in top left), instead of the "Modules" section". Before I re-flashed this last time, there was an icon bar at the bottom of Magisk with icons to tap on.
Easy enough of a fix, but I would still like to know which logs to post and how to get them.
BUT, Magisk is not actually updating for me this time around (the app looks the same after updating as it did before and the time before this the whole theme and layout changed)... There is still that issue. I HAVE successfully gained root, though, sp I'm content for now but would like to figure out WHY it isn't actually updating when I try to update it.
I'm trying to use this app: play.google.com/store/apps/details?id=br.com.banrisul
I've added to the hiding list and enable core only mode, it still closes at startup after saying my phone is either root or running a modified system. I've tested with rootbeercheck and it doesn't detect root in any of its tests.
i.imgur.com/60Zs5IH.png
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
Click to expand...
Click to collapse
but what exactly would trigger it? The link talks mostly about methods to hide magisk, I didn't find anything about what to do if magisk is working but the check fails. I've uninstalled titaniumbackup and rootbrowser. I've disable adb and developer options, I've deleted any folder or downloaded file related to magisk or those apps.
I'm running lineageos, would that be it? How would I go about it?
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Didgeridoohan said:
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Click to expand...
Click to collapse
It passes both checks.
I am running lineage OS 14.1 (Android 7.1.2) on a moto g4.
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Didgeridoohan said:
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Click to expand...
Click to collapse
Yes, after searching around a bit more I found about why. I completely forgot that I had flashed supersu on my phone before flashing magisk. So I guess that's what the app was freaking out about. So I flashed a supersu removal and reflashed my ROM, now the app is working normally
Thanks for the help!
Same problem
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
hammohammo said:
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
Click to expand...
Click to collapse
What version of the application do you want?
I have the latest version installed and it does not detect root
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
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!