Is anyone else seeing random freeze + reboot events after the Oreo update. I seem to be getting them about once a day. Not sure if they are Oreo related or due to ElementalX
me too. On OB3+ElementalX 2.01 I have random reboots more 10 times per day but I try flash ElementalX 2.02 random reboots it gone.
Sorry for my English language.
On the first ob 03 with Oos kernel, i got 1 reboot. Phone was in my pocket in his cover. I feel vibrations from the phone. I pull the phone out & i see that it reboots.
Hmm, I am on the official Oreo with EX 2.02 and got a reboot 15 minutes ago. Kind of annoying, considering going back to Nougat, would have already done it had I not needed a full wipe.
It's because of ElementalEx. All custom kernels seem to be experiencing random reboot issues on OOS Oreo except Flash and Blu Spark. Boeffla won't even make an OOS Oreo kernel because he doesn't think the code is stable enough. The random reboots with custom kernels is supposed to be related to bad coding in OOS Oreo WiFi module. Flash doesn't use the stock WiFi module and Blu Spark probably doesn't either.
Same here. On OOS 5.0.1 and ElementalX 2.02. I get around 3-4 reboots per day. Very annoying.
Related
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!
EDIT: THIS WAS RESOLVED IN THE NEW 20171231 NIGHTLY, EVERYTHING WORKS PERFECTLY NOW!
So I have this problem with Lineage OS 13 on my N10, so I flash the following packages:
Super SU 2.78
Busy-box
Open Gapps 6.0 nano
Lineage 13 10/14/17 nightly
The first boot is successful, I install some apps, watch some videos, normal tablet stuff. The problem is when I reboot, every time I reboot it ends in a boot loop. The tablet just won't boot up after I reboot it. The first boot works great, but nothing works after-wards.
Doesn't work on mine either, with CM13 20171017 build. I also made comment on the CM14 build thread here on XDA. I couldn't complete the initial setup using the CM14 build. I'm going back to stock.
I have the same problem with 20171021
I was able to reproduce the Error and attatched a logcat.
The bootloop always started while installing the App "immobilienscout24".
Hope someone can examine my logcat. I attached 2 (split) files, because I don't know, what is relevant.
Best regards
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
BerlinOtto said:
In my case the "BlueMail"-App cause the bootloops. After a factory reset LOS13 works fine, at the end of the install process of BlueMail Android restarts and bootloops. Deleting the bluemail-folder via TWRP solves the problem.
Frank
Click to expand...
Click to collapse
So basically I have to pick my apps wisely or lineage will reboot? **** that noise I'd rather run stock lollipop, lineage on my N10 is awful.
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
I have the same issue of constant boot loops. I tried several LOS nighly build w/o any success.
Funny thing is, after i rolled back to an old CynogenMod backup (v13.0 snapshot from 21.12.2016) it started to boot loop too, after I started updating my apps with Playstore.
So the bug must be very old, and it must be in CM/LOS, not in some specifiy app...
Folks, there is a defect open in the official lineage bug tracking system. please add your comments there - maybe this needs some more support to get looked at:
https://jira.lineageos.org/browse/BUGBASH-1075
Marktplaats causes boot loop
In my case, 'marktplaats', a dutch app, caused the boot loop. At some point I decided to upgrade to Lineage. I never had any issues on Cyanogenmod 13.
There seems to be a solution for this Problem in the newest nightly, See
https://jira.lineageos.org/browse/BUGBASH-1052
I've done a test Installation with my two Problem apps and it works fine for me.
I0tacle said:
Again bootloop at the current nightly version. Official Lineageops version is slowly evolving to crap. I switch to the unofficial nougat version!
Click to expand...
Click to collapse
All the problems were fixed in the in 20171231 nightly, running it without hitch no, stable and fast MM with CM theme support, finally
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
My a20 is randomly restarting during idle. It seems to happen when I receive a notification during idle, but not always. Any idea on why this would happen? (I'm on the unofficial Havoc 4.3 build from Eureka ROMs of you need to / want to know)