Over the last few days I've been having seemingly random instances where the system slows right down, becomes almost completely unresponsive, the home screen goes blank and sometimes only half the screen displays. I then have to long press to power off, but instead of shutting down the phone reboots, then everything is fine again. Usually this has been happening once every few hours, and when left overnight the display doesn't even turn on prior to rebooting (I can use fingerprint sensor and feel it vibrate to unlock though). A few times I have seen the error message saying 'System UI has stopped' but most times I reboot before seeing that.
I was running stock 8.0 unlocked and rooted with TWRP 3.1.1.0 and Magisk 14, and also using the pixel launcher installed as a system app, with no issues previously. I can't remember exactly now, but I am pretty sure I had this occur while on 8.0 prior to updating to 8.1 (possibly following an update to Magisk 15), but mostly it has been happening post-update to 8.1. I followed the stickied guide using step 9 first, and after that was getting very frequent instances. Then realized I was using an old 8.0 pixel launcher app so thought that might be the problem, so re-flashed everything, updated to TWRP 3.2.1.0, re-rooted and installed pixel launcher via the linked post below. Was then stable for almost 24hrs before having the issue re-occur, but with longer gaps between successive instances. Yesterday I re-flashed using the flash-all script (8.1) to try to clean out any gremlins - all went smooth, then re-flashed latest TWRP/Magisk and installed pixel launcher. Seemed fine for an hour or so...
https://forum.xda-developers.com/nexus-6p/themes-apps/pixel-2-xl-launcher-google-feed-t3715294
Not sure what is going on, I don't think its the zip file, since I checked the hash prior to doing the very first update. Could be the launcher I guess, but wasn't having any issue before so don't see why that would be a problem. Only root apps I'm using are root explorer, naptime and f.lux. Naptime I haven't installed yet on this go around, and f.lux I uninstalled this morning to see if it makes the problem go away. I tried searching around and saw similar issues reported for people using substratum/themes, but I have never used anything like that.
I have a log but can't link it yet...?
cooke6 said:
Over the last few days I've been having seemingly random instances where the system slows right down, becomes almost completely unresponsive, the home screen goes blank and sometimes only half the screen displays. I then have to long press to power off, but instead of shutting down the phone reboots, then everything is fine again. Usually this has been happening once every few hours, and when left overnight the display doesn't even turn on prior to rebooting (I can use fingerprint sensor and feel it vibrate to unlock though). A few times I have seen the error message saying 'System UI has stopped' but most times I reboot before seeing that.
I was running stock 8.0 unlocked and rooted with TWRP 3.1.1.0 and Magisk 14, and also using the pixel launcher installed as a system app, with no issues previously. I can't remember exactly now, but I am pretty sure I had this occur while on 8.0 prior to updating to 8.1 (possibly following an update to Magisk 15), but mostly it has been happening post-update to 8.1. I followed the stickied guide using step 9 first, and after that was getting very frequent instances. Then realized I was using an old 8.0 pixel launcher app so thought that might be the problem, so re-flashed everything, updated to TWRP 3.2.1.0, re-rooted and installed pixel launcher via the linked post below. Was then stable for almost 24hrs before having the issue re-occur, but with longer gaps between successive instances. Yesterday I re-flashed using the flash-all script (8.1) to try to clean out any gremlins - all went smooth, then re-flashed latest TWRP/Magisk and installed pixel launcher. Seemed fine for an hour or so...
https://forum.xda-developers.com/nexus-6p/themes-apps/pixel-2-xl-launcher-google-feed-t3715294
Not sure what is going on, I don't think its the zip file, since I checked the hash prior to doing the very first update. Could be the launcher I guess, but wasn't having any issue before so don't see why that would be a problem. Only root apps I'm using are root explorer, naptime and f.lux. Naptime I haven't installed yet on this go around, and f.lux I uninstalled this morning to see if it makes the problem go away. I tried searching around and saw similar issues reported for people using substratum/themes, but I have never used anything like that.
I have a log but can't link it yet...?
Click to expand...
Click to collapse
Try using supersu again or maybe downgrade magisk. Mine for some reason after going back to supersu randoom reboot stopped. This even after ive downgraded to 8.0 thinking 8.1 was the reason though it was running fine before.
Sent from my SM-N950F using Tapatalk
[email protected] said:
Try using supersu again or maybe downgrade magisk. Mine for some reason after going back to supersu randoom reboot stopped. This even after ive downgraded to 8.0 thinking 8.1 was the reason though it was running fine before.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Thanks will give it a shot and report back. Like I said I think the instability coincided with an upgrade from Magisk 14.0 to 15.0 which happened right before I went to 8.1, so going back to 14.0 might be the first step for me.
Were yours just random reboot or also the system glitching/freezing?
cooke6 said:
Thanks will give it a shot and report back. Like I said I think the instability coincided with an upgrade from Magisk 14.0 to 15.0 which happened right before I went to 8.1, so going back to 14.0 might be the first step for me.
Were yours just random reboot or also the system glitching/freezing?
Click to expand...
Click to collapse
Just random reboot so far
Sent from my SM-N950F using Tapatalk
Well... flashed the Magisk uninstaller from 15.1 and re-flashed 14.0 and no system crashes yet.
However now I can't enable assistant vice activation. Possibly a separate issue I suppose, but it was working before.
Edit: Uninstalled Google app updates and reapplied from play store and now working.
So just as a follow up I've been running fine on Magisk 14 without issue for some time now. Have not tried the recent 15.2 release.
However f.lux is not behaving normally and for some reason is acting almost like a yellow filter. I found the thread below which seems to indicate some issue between f.lux / Android 8.1 / Magisk.
https://forum.justgetflux.com/topic/4667/f-lux-not-compatible-with-android-oreo-8-1/7
I have been having this exact problem on my Nexus 6P. Glad to know that I'm not going crazy. The switchover point for me was exactly from Magisk 14.5 to 14.6. 14.5 works fine for me with no issues. 14.6 and onwards (including 15.2) has exhibited this behavior very regularly.
One thing that I just tried that might have "fixed" it is I recently was in 15.2 beta (installed via TWRP) and it was having the problem. I was on the beta in order to capture some of its verbose logs. At one point, I wanted to just try a different installation method so I made sure to check the two options in the MagiskManager ("forced encryption" and "dm-verity") so that they are on and then reinstalled Magisk 15.2 directly from MM. After doing that, I haven't seen the issue crop up, so maybe installing from MM to make sure that it uses those options on install is the way to address this? I'll update if I see any more issues.
Thanks for the replies here and in the Magisk beta thread.
After installing with your described method/settings I reinstalled f.lux, and had a couple of glitch/reboots. I then uninstalled f.lux and I'm now over 24hrs without going into the glitched state. So it seems maybe this a compound issue. Can you confirm whether you had this or another similar app installed? I've seen other reports of this kind of behavior when using substratum.
mastercko said:
I have been having this exact problem on my Nexus 6P. Glad to know that I'm not going crazy. The switchover point for me was exactly from Magisk 14.5 to 14.6. 14.5 works fine for me with no issues. 14.6 and onwards (including 15.2) has exhibited this behavior very regularly.
One thing that I just tried that might have "fixed" it is I recently was in 15.2 beta (installed via TWRP) and it was having the problem. I was on the beta in order to capture some of its verbose logs. At one point, I wanted to just try a different installation method so I made sure to check the two options in the MagiskManager ("forced encryption" and "dm-verity") so that they are on and then reinstalled Magisk 15.2 directly from MM. After doing that, I haven't seen the issue crop up, so maybe installing from MM to make sure that it uses those options on install is the way to address this? I'll update if I see any more issues.
Click to expand...
Click to collapse
Hey just a heads up - I am now on opm3 (Jan) and 15.2 beta with the just preserve encryption checked and no glitches yet after ~15hrs. Will be installing f.lux soon to see if it triggers.
Installed f.lux and maybe an hour later started glitching. Uninstalled and had to reboot to clear things up, and now haven't had a glitch since. So definitely the source of the issue, but it's a compound thing since it only started happening since Magisk 14.6 onward. However, there are other reports saying f.lux hasn't been behaving properly on both 8.0 and 8.1, so likely not the fault of Magisk at all.
Hey, I was linked to this thread from Magisk thread, I had the same issue on my Nexus 5X with Magisk 14.6+, so I uninstalled f.lux and issue is gone as you said. Now I'm testing CF.lumen on Magisk 15.3 and it is w/o any issue so far.
Related
Hey everyone.
Like many Android users, I've been struggling to find a ROM and systemless root combo that passes SafetyNet (ever since Pokemon GO 0.37 update). I eventually found a ROM that can be unrooted cleanly (AryaMod S7 Edge port), and managed to get SafetyNet working via Phh's Superuser (first with Magisk + r251, now using hidesu version r266).
However, I soon ran into a problem: The systemless root appears to be causing my phone to bootloop. There seems to be a gradual degradation of the bootimage somehow caused by systemless roots; my phone would work fine for a while, then gradually apps would force close or the phone would freeze. If I try to reboot, the phone then gets stuck in a boot loop (which occurs before the ROM even starts loading). I am very sure this is caused by an error in the bootloader because this bootloop behavior persists through nandroid restore or clean ROM installations. The only way to fix it is to flash the stock bootloader via ODIN.
I noticed a few users in the dev threads of ROM's I've tried reporting the same issue, but in the dev thread for Phh's Superuser there seems to be a lack of mention of this issue (likely model-specific, as I am using Phh's Superuser on my wife's Note 4 and her phone isn't bootlooping). Just wondering if anyone has experienced the same problem and found a solution?
Try the TMobile forum .
Sent from my SM-N930F using XDA-Developers mobile app
I also have an N900T, and magisk v7 + phh is working fine for me if I don't install any extra systemless modules. When I installed the better battery stats module, I started getting bootloops, so there are definitely some issues with it.
Magisk is still being worked on, so it's probably only at alpha or beta status right now. Hopefully it will get more stable in the future.
btw.. I'm running the latest stock Samsung 5.0 rom (N900TUVSFPH3), which has the latest bootloader, since it seems the most stable to me.
So I just updated Magisk from v11 to v12 and my phone is totally douched up. After rebooting there's an "Unable to use fingerprints" message at the bottom of the screen, the touch screen is janky and my unlock pattern no longer works. The screen goes to sleep randomly too and then comes on without being touched. On the off occasson that the unlock pattern DOES work, the screen loads with no icons, just the page dots and status bar with my wallpaper and nav buttons. Uninstalled Magisk and got the same. Rebooted after uninstall, same thing. I guess I'll be reflashing the ROM, but this is a huge pain in the ass. :/
This isn't a question--more of an answer. DO NOT UPDATE to v12. If you did and have trouble, downgrade to 11.x.
I can second this. Updated to 12.0 and my phone started rebooting randomly and fingerprints started not working. Thought it was something with the rom so clean flashed it again, all was fine till I updated Magisk again. Downgraded to 11.6 and so far no more reboots and fingerprint works.
that's odd. it is working great for me. (currently using Weta 4.9.2 and Tilde's latest kernel + latest magisk manager and magisk 12.0 zip flashed)
Def breaks the systemui and causes the device to repeatedly crash on the ls997.
Was how it acted on pre 11.0 builds for us on v20.
Im testing with the dev on magisk now.
Updated to the latest, no issues here on RR with original kernel.
xxxrichievxxx said:
Updated to the latest, no issues here on RR with original kernel.
Click to expand...
Click to collapse
yeah aosp versus stock lg os act differently
i believe last time ls997 was the only one really having issues, but its breaking ui on the ls997
don't do it
I updated also, put phone in a never-ending 30 seconds to reboot. Had to restore.
Hi,
I have problems with a Nexus 10 (Lineage OS 13, latest nightly, rooted with SuperSu 2.82 and Nova Prime). Worked fine till now. Then reboots when I want to unlock with gesture. Did a factors reset, worked for about a day. Then reboots again by unlocking.
I saw that when the problems started, on the lockscreen was only the return button visible, I missed the Home- and Taskbutton.
I started in safe mode, uninstalled Nova and everything workes fine now.
If any further Information is needed I will try to give them.
Greetings
P.S. Did a posting in reddit also: https://www.reddit.com/r/NovaLauncher/comments/6z8lmy/bug_nova_crashed_phone_bootloop/
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Happened to me too. Got rid of magisk for now so running stock un rooted until this gets sorted. Haven't ran into the issue since un rooting.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Rowdyy Ronnie said:
Xposed is not yet stable for Oreo. So just get rid of that first. Moreover, it depends on what Magisk version did you flash. V16.0 is the latest stable version and you are recommended to flash it only. I have been using magisk for a long time on both stock and custom rom and never had an issue.
Click to expand...
Click to collapse
I flashed 16.0 too, but I have to say the issue became real even before I installed Xposed. Guess it's something Magisk-related
Try older Magisk, for example 15.3.
Same to me. Just reboot and it´s fine.
BetaPix said:
Hello guys! I know it's a common issue, but when I reboot my phone there's roughly a 50% chance it gets stuck on the boot screen and I have to reboot. It's surely caused by Magisk, but has someone found a fix already?
The bricks got more frequent and really annoying when I began to install some modules (Xposed, Viper ecc.). Sometimes it takes even 2-3 reboots to start my phone properly, and sometimes it boots without recognizing my sim card.
Is there a fix for this, or do I have to live with it?
Click to expand...
Click to collapse
Same. I don't have Xposed or other mods, so I think it's a Magisk's issue.
Made over 20 reboots in order to find the"right" combination of substratum themes the last two days.only 2-3 times i had stucked in reboot. I have magisk, xposed ,gravitybox .
Huh, I get this sometimes too. So it's Magisk v16 you say?
TrueMS said:
Try older Magisk, for example 15.3.
Click to expand...
Click to collapse
Good idea, will give that a go. I don't use any modules anyway, only use it for Safetynet-friendly root.
Same problem here.
I Will follow the topic.
Double post, Sorry!
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
laugeek57 said:
With beta magisk v16.4 my mi A1 boot normaly...with v16.0 must force reboot 3 times out of 5
Click to expand...
Click to collapse
Currently testing 16.4b and no boot issues atm!
Must have been topjohnwu's boot operations code change.
Thank you really much
Hi folks, my stock 6T just offered me the 9.0.12 update. I'm holding off for now as everything works well on 11, but interested to hear experiences.
My only gripe with 11 is idle battery drain that occurs after about 48 hours post boot; no drain problem before that.
Sent from my ONEPLUS A6013 using Tapatalk
Battery life is amazing! (end sarcasm)
Everything seems to be fine
No issues here...installed early Monday morning.
Tried Canada and Germany VPN but nothing yet... Will wait for OTA
Still waiting OTA
Sent from my ONEPLUS A6013 using Tapatalk
Frankenscript said:
Hi folks, my stock 6T just offered me the 9.0.12 update. I'm holding off for now as everything works well on 11, but interested to hear experiences.
My only gripe with 11 is idle battery drain that occurs after about 48 hours post boot; no drain problem before that.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Region/country? Tia!
I have the OnePlus 6T McLaren edition, I'm in the U.S.A and have a T-Mobile SIM in it (but it's not the T-Mobile version of the phone). I got notified of the update about an hour ago. It detected my phone was rooted so it downloaded the full version of the upgrade, not just a patch file. It then auto-installed the update just fine (I haven't modified my recovery). It booted up just fine and everything is looking good. I did a few simple test calls and loaded a few apps, nothing looked out of the ordinary. I can't speak to battery life or performance though.
I'm now using a direct-launched TWRP to re-flash the ElementalX 3.10 kernel and the Magisk 18.1 zip files (to hide the unlocked bootloader from the OS and also have root back with the ability to hide root from various programs). Those are the only 2 mods I've ever installed on this phone and they've proven solid.
Sometimes reading mode fails to work.... I restarted the phone and worked perfectly
My device bootloops with RescueParty into TWRP with 9.0.12. I believe Magisk is the cause of the problem because as soon as I flash it in TWRP, the device will immediately bootloop into TWRP with RescueParty. The only way to recover was to flash the 9.0.12 boot.img to both boot partitions. So if you plan to use Magisk and Magisk modules, you might want to stick on 9.0.11 for now.
theDUD3 said:
Region/country? Tia!
Click to expand...
Click to collapse
U.S. Indiana on AT&T
Sent from my ONEPLUS A6013 using Tapatalk
Seems really good here. No complaints. Gaming is much smoother and wifi seems much more stable for me too. I like it
Can't believe how fast I got the update. With a "Google" phone I had to wait weeks even over a month sometimes and sideloading on Windows 10 is a PITA when it decides not to find the phone even though it did only a few minutes ago.
Deleted
No issues yet did mine yesterday in Maine USA with German VPN on T-mobile/AT&T sims
parker.stephens said:
My device bootloops with RescueParty into TWRP with 9.0.12. I believe Magisk is the cause of the problem because as soon as I flash it in TWRP, the device will immediately bootloop into TWRP with RescueParty. The only way to recover was to flash the 9.0.12 boot.img to both boot partitions. So if you plan to use Magisk and Magisk modules, you might want to stick on 9.0.11 for now.
Click to expand...
Click to collapse
Yup, experiencing the same issue currently. Gonna follow what you did for now :good:
Did you extract the boot.img from the update file or is it here somewhere? I tried looking .. didn't find it.
Jok3r10 said:
Yup, experiencing the same issue currently. Gonna follow what you did for now :good:
Click to expand...
Click to collapse
You guys could try uninstalling magisk from TWRP, and reflshing it. It worked for me after struggling with the bootloop.
AleiATCG said:
You guys could try uninstalling magisk from TWRP, and reflshing it. It worked for me after struggling with the bootloop.
Click to expand...
Click to collapse
Did you do it with the latest magisk?.. 18.1?
Jok3r10 said:
Yup, experiencing the same issue currently. Gonna follow what you did for now :good:
Did you extract the boot.img from the update file or is it here somewhere? I tried looking .. didn't find it.
Click to expand...
Click to collapse
I used a python script to extract the image from the update .zip. Also reinstalling Magisk does nothing to solve the issue. 18.0 I know worked in 9.0.11, I only ran 18.1 for a little while. Neither fix the issue.
A quick update, it seems that @AleiATCG's suggestion worked for me. I uninstalled Magisk using their uninstaller and reinstalled Magisk 18.1 and voila.. I booted into the rom.