I was getting random freezes (at least once daily) that I had to force reboot (sometimes twice at a time) using magisk.
It appears to have started on January patch (or android 11). I decided to remove magisk and unroot completely and the freezes were gone.
Then I decided to try magisk (stable channel) with this April security patch and less than 12 hours later I got the first freeze. Just to make sure I did not install any module.
Note: the kind of freeze I'm experiencing makes the phone extremely slow, almost no app start and the app drawers renders with some icons missing. I cannot even power off normally so I need to force reboot.
quera said:
I was getting random freezes (at least once daily) that I had to force reboot (sometimes twice at a time) using magisk.
It appears to have started on January patch (or android 11). I decided to remove magisk and unroot completely and the freezes were gone.
Then I decided to try magisk (stable channel) with this April security patch and less than 12 hours later I got the first freeze. Just to make sure I did not install any module.
Note: the kind of freeze I'm experiencing makes the phone extremely slow, almost no app start and the app drawers renders with some icons missing. I cannot even power off normally so I need to force reboot.
Click to expand...
Click to collapse
I had similar, random freezes starting in January too. I'd try Magisk Canary and either EX or Kirisakura kernel. I'm on April running Magisk Canary, EX kernel with Active Edge, Systemless Hosts, Universal SafetyNet Fix modules and have no freezes.
newkydawg said:
I had similar, random freezes starting in January too. I'd try Magisk Canary and either EX or Kirisakura kernel. I'm on April running Magisk Canary, EX kernel with Active Edge, Systemless Hosts, Universal SafetyNet Fix modules and have no freezes.
Click to expand...
Click to collapse
Which features of Ex kernel are you using?
quera said:
Which features of Ex kernel are you using?
Click to expand...
Click to collapse
DoubleTap2Wake - Enabled
Sweep2Wake - Enabled
Sweep2Sleep - Enabled
Vibrate on wake - Disabled
Memory>ZRAM>Swappiness 100 (can't remember is that's a stock value or not)
Related
Since there are multiple reports of random reboots appearing multiple times a day on OB27, I think it would be a good idea to start a poll about it.
Just report in this thread if you're facing those issues and which setup you are using!
Please list all your Mods and System changes down below plus your apps which needs root. So we can figure out if there are any analogies.
I will post an example below.
Random reboots?
- None
Setup:
- TWRP-3.2.0-x bluSparkv8.60-op3_op3t
- ExperienceOS R30
- SuperSU (NO Magisk)
- SuHide
- BluSpark 208
Installed Root-Apps:
- PitchBlack-Substratum
- Adaway
- ForceDoze
- Kernel Auditor
- SDMaid
- SELinux Changer
Random reboots?
- Yes
Setup:
- twrp-3.2.0-0-oneplus3t.img (Should I use a modded version?)
- AUDAX OP3T O v4.0
- Magisk 14.5
Installed Root-Apps:
- Substratum with Ozone theme
- Greenify
- SDMaid
Magisk Module
HEVC+SM GC OP3&OP3T and OP5 by crashoverride1995
I guess the Oreo OOS is not working well with the Magisk. But I don't have much time to verify it.
I may find the real reason behind the random reboot issue. It's a magisk module called "Greenify4Magisk".
Once you've installed this module, your phone itself will randomly soft reboot. But the real problem here is that even you disable or delete this module, you'll still get random reboots. The only way to fix this issue is to clean flash your ROM. Start over and reinstall everything but the module. Flash without cleaning the /data partition (a.k.a. dirty flash) can't solve this issue. It looks like the module "pollutes" your /data partition.
I've tried to dirty flash several ROMs and kernels, disable and uninstall every module. But I still got random reboots. It almost made me crazy. So I decided to have a completely new start. I reinstalled every apps and module except the Greenify4Magisk. I've used my phone for nearly a week now and no reboot at all. It used to reboot 2~3 times an hour.
BootCoveryXhosts said:
I may find the real reason behind the random reboot issue. It's a magisk module called "Greenify4Magisk".
Once you've installed this module, your phone itself will randomly soft reboot. But the real problem here is that even you disable or delete this module, you'll still get random reboots. The only way to fix this issue is to clean flash your ROM. Start over and reinstall everything but the module. Flash without cleaning the /data partition (a.k.a. dirty flash) can't solve this issue. It looks like the module "pollutes" your /data partition.
I've tried to dirty flash several ROMs and kernels, disable and uninstall every module. But I still got random reboots. It almost made me crazy. So I decided to have a completely new start. I reinstalled every apps and module except the Greenify4Magisk. I've used my phone for nearly a week now and no reboot at all. It used to reboot 2~3 times an hour.
Click to expand...
Click to collapse
I would say, I have a different issue then. I have installed only Magisk for rooting purpose, no modules at all. But still will get random reboots after few days.
Seems like there are rumors that even Pixel with Oreo gets this random reboots too
Sent from my ONEPLUS A3003 using Tapatalk
Ok, in the thread
https://forum.xda-developers.com/oneplus-3/how-to/randomly-reboots-beta28-t3714665/page3
this has already been discussed, I think to avoid this thread to be considered a duplicate of that one other, we should keep this one essentially as a Poll Thread.
In this sense, my experience is:
-Reboots: YES
-ROM: Freedom OS CE 3.1 & 3.2
-Root: Magisk 14.0
-Modules: None
-Frequency: 1 week without reboots at all, then about 2-3 each day.
------------------------------
-Reboots: YES
-ROM: Oxygen OS Open Beta 28
-Root: Magisk 14.5
-Modules: None
-Frequency: 1-2/day, but once I had 5 days without reboots.
------------------------------
-Reboots: NO
-ROM: Oxygen OS Open Beta 28
-Root: NONE
-Modules: N/A
-Frequency: At least 2 days without reboots.
-> In the Magisk thread it has been reported on other devices too, and it has been acknowledged to be a Magisk Issue. Anyway, this thread might be useful for tracking of the issue to check if it has been solved when the patch arrives. Notice that reboots have an extremely random nature and only a couple days without reboots doesn't mean the issue is fixed. Some reboots are slightly silent, so you can check for reboots in a terminal and type "uptime" to check if there has been a reboot while you weren't looking.
BootCoveryXhosts said:
Random reboots?
- Yes
Setup:
- twrp-3.2.0-0-oneplus3t.img (Should I use a modded version?)
- AUDAX OP3T O v4.0
- Magisk 14.5
Installed Root-Apps:
- Substratum with Ozone theme
- Greenify
- SDMaid
Magisk Module
HEVC+SM GC OP3&OP3T and OP5 by crashoverride1995
I guess the Oreo OOS is not working well with the Magisk. But I don't have much time to verify it.
Click to expand...
Click to collapse
maybe this moudle
HEVC+SM GC OP3&OP3T and OP5 by crashoverride1995
** Resolved: Please see post #9 below by @henderjr for a solution and don't forget to thank @henderjr!
--------------------------
Just downloaded DP4 and dirty flashed from DP3 (remove -w), everything looks normal....
Then I install Magisk 16.4 with TWRP (boot only), when I go back to system, System UI just crash continuously...
Also, even with 89% battery, the system still complain "battery low" (with message say the battery will last until tomorrow morning 7 o'clock, which is 19 hrs later! ha ha !)
When swipe down the notification area, the upper part of screen become dark... looks like UI glitch..
Anyone have same issue like this?
(Maybe I should factory reset, but I see somewhere that contact will not sync... So now stuck in the middle...)
Same issues here. And with random reboots also.
That's weird.
I clean flashed from Android 8 and haven't had any SystemUI issues.
I also use Substratum and haven't had any issues.
I've only been running it for a couple of hours, I'll report back if anything changes.
Edit: I'd suggest a clean flash, though. Stuff seems REALLY bugged lol.
For me started failing after a reboot. The first moment I got into the system, UI was broken
Tried factory reset also. Same problem after reboot
Same here (((
It seems we really need update of Magisk. @topjohnwu while your country need you, we also need you!
Even before flashing magsik CTS profile is false.
Sent from my Pixel 2 XL using XDA Labs
Has anyone confirmed this happens only after flashing Magisk? I'm currently trying to reproduce all the other steps (restore apps, config, etc) just to be sure who is guilty
Edit: well, I can't reproduce it. So everything seems to be pointing Magisk as the guilty
lssong99 said:
Just downloaded DP4 and dirty flashed from DP3 (remove -w), everything looks normal....
Then I install Magisk 16.4 with TWRP (boot only), when I go back to system, System UI just crash continuously...
Also, even with 89% battery, the system still complain "battery low" (with message say the battery will last until tomorrow morning 7 o'clock, which is 19 hrs later! ha ha !)
When swipe down the notification area, the upper part of screen become dark... looks like UI glitch..
Anyone have same issue like this?
(Maybe I should factory reset, but I see somewhere that contact will not sync... So now stuck in the middle...)
Click to expand...
Click to collapse
I had the same exact behavior yesterday. If you're still running the magisk module "[APP] 18. Feb ◦ Edge Sense Plus 1.22.0 ◦ Customize Active Edge on your Pixel 2 XL" it will cause SystemUI to behave strange and show the battery saver icon. Disable the module until it gets updated.
Mine was working normally on DP4, Substratum, Magisk...only had the ctsProfile false problems others are having.
Often upon flashing, especially dirty flashing any Rom, when opening Magisk it would force close. Found by just reinstalling the Magisk.apk it would work again.
But, since Google Pay is failing with the ctsprofile false problem, I've rolled back to DP3 for now and all is good.
No issues for me either. I dirty flashed and installed Magisk 16.4 and no issues at all besides the SafetyNet issue.
henderjr said:
I had the same exact behavior yesterday. If you're still running the magisk module "[APP] 18. Feb ◦ Edge Sense Plus 1.22.0 ◦ Customize Active Edge on your Pixel 2 XL" it will cause SystemUI to behave strange and show the battery saver icon. Disable the module until it gets updated.
Click to expand...
Click to collapse
It WORKS! It just WORKS! Thank you SOOOO Much!
It works for me too. Thanks!
...............
Insinuendi said:
So I booted into TWRP 3.2.2-0-taimen on DP4, still can't decrypt,. Tried using ADB sideload with Magisk 16.4 zip anyway, looks like it works. Then I try rebooting and it never starts.
Click to expand...
Click to collapse
Turn off your screen lock and you won't have to worry about TWRP not decrypting (settings > security & location > screen lock > none). Turn your screen lock back on after you've completed the flash.
xunholyx said:
Turn off your screen lock and you won't have to worry about TWRP not decrypting (settings > security & location > screen lock > none). Turn your screen lock back on after you've completed the flash.
Click to expand...
Click to collapse
I've tried both ways, same issue. Twice now I've had to flash DP4 again (without -w) because it gets stuck in a bootloop. Is there something I might be missing?
Sent from my Pixel 2 XL using Tapatalk
Insinuendi said:
I've tried both ways, same issue. Twice now I've had to flash DP4 again (without -w) because it gets stuck in a bootloop. Is there something I might be missing?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Since you flashed Magisk without decrypt data, it's highly likely that the data partition maybe damaged. Just flash-all with -w (don't remove -w) and your phone should boot... Anyway I think your data is already gone the moment you flashed Magisk without decryption...
I have a OnePlus 5T that passes fully the SafetyNet test, but after a few hours it gives false in ctsProfile and BasicIntegrity, I am with Android 8.1 OxygenOS 5.1.5 (I already tried with 5.1.4 doing a thorough cleanup between rom exchange and also unsuccessful ), I unlocked Bootloader and installed TWRP 3.2.3 Blu spark v9.85, then i flash Root Magisk 17.1 by twrp, Installed from a clean ROM and I've already tried with 17.2 and It's the same thing at the end, I have also tried to install Magisk 16.0 from a clean rom and then upgrade to 17.1 directly via Magisk Manager but it was the same, already activated the Magisk Hide in all necessary applications, I hid the Magisk Manager, I've tried flashing Petnoire's SafetyNet Spoofer and me too changed the device fingerprint by MagiskHide Props Config but nothing solved my initial problem, every time I restart the device it passes on the SafetyNet again but after a few hours it fails again, Now i tried to flash the module Universal SafetyNet Fix v3 beta1(MG v17 fix) by Magisk Manager, but Magisk Manager stopped opening even uninstalling the application and installing other versions, I tried more than once and the installation of this module always presents this problem even flashing by TWRP, and after a few hours too SafetyNet failed, Can inform me the latest version of OxygenOS for OnePlus 5T that passes on SafetyNet without any problem? Even though OxygenOS is perfect for me, I'm willing to change rom in the last case, because the most important thing for me is to go through SafetyNet to use the applications I need.
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
anatoly1983 said:
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Click to expand...
Click to collapse
I tried to do this yesterday but the initial problem persisted, every time I restart the device it passes on the SafetyNet again but after a few hours or minutes it fails again.
yoye_cros said:
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
Click to expand...
Click to collapse
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Mega_Monster_X said:
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Click to expand...
Click to collapse
Honestly, I didn't have found any bug. I tried crDroid but I wasn't really happy, and CNP is for my use very stable without bug. I don't know if Volte or VoWifi is working because I don't use this. Also, it's very easy to install compared to other Pie Roms. I just can advise you to try it.
Try a different play services apk. This was the case with me previously.
Seagorilla2 said:
Try a different play services apk. This was the case with me previously.
Click to expand...
Click to collapse
I've tried this but to no avail
With Magisk 16.0 everything went fine, the problem is the Magisk modules I used that are not compatible, but I'll search here to see if I find the modules I want for Magisk 16.0.
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
floborg said:
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
Click to expand...
Click to collapse
I have not found a solution yet, when I fail on SafetyNet I reboot the device and pass SafetyNet a few times for a short time and sometimes lasts several hours but then fails again , I'm using Magisk 18 in OOS Open Beta 20 Android 9.0
Developer Preview is up if anybody wants to try it
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Holy Moly.
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
DoobyDroid said:
Side loaded OTA via ADB all works fine no issues so far no FC can't say much difference
Click to expand...
Click to collapse
Seems like for now, most UI and user facing changes in general are hidden behind flags, this one is meant for the devs, so it's to be expected. The beta, on the other end, will be aimed at users, and then we will see what changes
I upgraded last night. Had to reboot twice after restart. Then everything was stable. First time it rebooted after install, nothing seemed to want to work and kept FCing. Second reboot, everything is fine now. Sometimes, Nova needs to be indicated when I press the home button that it's default, otherwise, everything is working fine.
Is it me or does the Android version still say 11 but the build is "S"?
I downloaded the 12 DP1... and it just isn't ready yet (understandably so) for the daily driver use I need.f
Rooting it requires disable verity and verification. You'll need magisk 23 or canary to patch boot.img as well. Not disabling verity/verification, it will only boot back into fastboot and list the reason as something like, "unable to load boot image".
Once rooted, I moved on to installing edxposed --- using riru, riru edxposed, and edxposed manager. Everything installs without problems. Final reboot, and reboots as normal. But then about 90 seconds later, you'll start getting FC after FC after FC. All apps too, and background apps, and systemui, etc.
Removing the riru components and edxposed manager, doesn't correct this problem.
Did fresh format and reinstall of the DP1... rooted again... and then tried Viper4Android. I use a very simple version. You just flash it, and its done (no manual driver install either). Rather than the 3 reboot, AML, driver install, etc.
V4A installs with good logs. Reboots without a hitch. But I noticed the v4a icon in the status bar is missing. I open it up manually, and start getting freezes and fc's. Within 5 minutes, I get kernel panic reboots -- and non-bootloop freezes on the working G screen.
Reboot manually with long press power, get it loaded back up and immediately remove V4A. Reboot and now I'm back to stock.
Get FC's every hour or two. Random reboots too. Battery life is struggling.
I decided to wait until a better version drops, perhaps the beta or at least a DP2.5 or 3.0. As of right now, having Android S is mostly just a status thing -- to show people how cool we are to have access to it as such an early stage. But unless you are dedicated to helping improve the ROM through daily use and reporting... I highly recommend that you stick with Android R.
Just flashed the 1st public android 12 beta bramble-ota-spb1.210331.013-3c294b13.zip with adb sideload. Listed as android S atm, surprised 5G was enabled as this wasn`t the case with android 11 in the Netherlands. All apps working fine so far and still finding out the new stuff.
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
ekowwillis said:
Has anyone been able to root the Pixel 4a 5G with Android 12 Beta 1?.
Kindly share the steps.
Click to expand...
Click to collapse
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
galza said:
yep i also like to know..tried twice but ended up in fastboot mode and cant get it to boot.i used the old magisk patched method but i probebly missing something
Click to expand...
Click to collapse
Clean wipe and follow the OP instructions in this Pixel 5 thread. Make sure you use the images for 4a5g where needed
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
I have been using canary successfully all week. Today I woke up to a message saying I needed to update magisk canary. When I clicked the message to open the app and see the issue it does the normal splash screen then disappears. Unlike the main version of magisk that changes it's icon and doesn't even try to open this tries. I have uninstalled and reinstalled and there is no difference. I still get su prompts when using new apps that require root, but the app itself will not open fully. Thoughts?
I was going to delete this post but I discovered downgrading from the newest magisk canary to magisk canary version 831a398b fixed everything, thought that info might help someone else.
The latest build fixes the crashing. 25208 works well.