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.
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!
Has anyone tried to flash the Xposed Module that came out earlier today/yesterday? If you don't know what I'm talking about, watch this video real quick: https://youtu.be/eADZK17N7rk
I understand it is unofficial and might be unstable with lots of bugs, & that some modules currently don't work, but would I be at (more) risk of bricking my phone if I flashed it?
I flashed it yesterday and everything went well. The bugs are the following that I've experienced:
1. In order to download a module, you must press save instead of download. After that, a toast notification will prompt you on where to go in your file manager to find the apk.
2. Some force closes such as kernel auditor and Google/services. Those were resolved later on for me.
3. I noticed the fingerprint scanner got a little sluggish after, but a reboot fixed that.
4. Sorta made the UI a little sluggish as well so be careful if you've already under clocked your processor.
There we go. I am currently on the latest version of Lineage OS. I uninstalled it today, but I plan on installing it again with a new ROM tonight.
It doesn't seem to work on AOSP or Extended AOSP, but apparently seems to work on other ROMs. Want to switch ROMs unless EAOSP fixes that because I really want Amplify again
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/
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.