Hey guys can anyone check if you can connect to server with LOS 14.1 July 11 build?
Mine gets stuck on 50% loading screen and "connecting to server" message.
I tried hiding magisk and all. Still no success.
the problem is LOS base is detected by root blocking apps now. Fix is a small kernel and build.prop edit. Using a custom kernel is half done already. Look up fate grand order, LOS fix for more info.
Related
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
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution
GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?
Hi, I've recently installed the lineage os 16 unofficial for Galaxy Note 3 N9005, don't remember from who, but once I've installed it a message kept popping up saying "Bluetooth keeps stopping". I've tried everything and searched everywhere and found nothing. I later installed AOSP EXTENDED to see if that would have fixed the issue, but it's the same story. The crash log url says it's del.dog/pazihuqaku. Please help.
I just downgraded from DotOS 9.0 ROM to LineageOS 15.1, and since then Play Store says Device is not certified, and Magisk Manager fails the cts SafetyNet check, but passes the integrity one.
I have tried literally everything from Magisk Modules and some fidgeting with Termux, to Fully Formatting phone both via fbe_twrp and normal latest twrp.
Prior to 9.0 ROMs (yeah i tested a few of them) I had a fully functioning Resurrection Remix 8.1 with no problems (i say that because RR is based on LineageOS (i think))
Please help me :/
grewicked said:
I just downgraded from DotOS 9.0 ROM to LineageOS 15.1, and since then Play Store says Device is not certified, and Magisk Manager fails the cts SafetyNet check, but passes the integrity one.
I have tried literally everything from Magisk Modules and some fidgeting with Termux, to Fully Formatting phone both via fbe_twrp and normal latest twrp.
Prior to 9.0 ROMs (yeah i tested a few of them) I had a fully functioning Resurrection Remix 8.1 with no problems (i say that because RR is based on LineageOS (i think))
Please help me :/
Click to expand...
Click to collapse
That doesn't make sense play store is saying the device isn't certified, I have never heard of an error like that in all the years I've been flashing.
Are your gapps up to date? You've flashed the right vendor for 8.1? I've gone from 9.0 to 8.1 and vice versa more than a couple times and I never had issues.
Unless some module you're using with magisk is doing it? I don't know anything about that , I use magisk for root, and for v4a and that's it.
Lawlrus said:
That doesn't make sense play store is saying the device isn't certified, I have never heard of an error like that in all the years I've been flashing.
Are your gapps up to date? You've flashed the right vendor for 8.1? I've gone from 9.0 to 8.1 and vice versa more than a couple times and I never had issues.
Unless some module you're using with magisk is doing it? I don't know anything about that , I use magisk for root, and for v4a and that's it.
Click to expand...
Click to collapse
Actually this is the second time I encounter that error, but the first time, a simple cache delete of the PlayStore.apk did the job just fine. This is a way more common problem than you think, but not so much that it has a certain solution.
I flashed radio, vendor and bootloader images that was provided from the original LOS thread here. Gapps were freshly downloaded from original site. The same problem was still there no matter if and what modules I had on Magisk.
Didn't try though to boot the rom without installing root, to see if the problem would still be there
grewicked said:
Actually this is the second time I encounter that error, but the first time, a simple cache delete of the PlayStore.apk did the job just fine. This is a way more common problem than you think, but not so much that it has a certain solution.
I flashed radio, vendor and bootloader images that was provided from the original LOS thread here. Gapps were freshly downloaded from original site. The same problem was still there no matter if and what modules I had on Magisk.
Didn't try though to boot the rom without installing root, to see if the problem would still be there
Click to expand...
Click to collapse
Not saying it cpuld be root, saying it could be the magisk modules you're playing around with. I've been flashing ROMs since 2.0.x over the life span of six devices, this is not common lol
Lawlrus said:
Not saying it cpuld be root, saying it could be the magisk modules you're playing around with. I've been flashing ROMs since 2.0.x over the life span of six devices, this is not common lol
Click to expand...
Click to collapse
Initially I didn't use any modules, the fresh clean install of LOS had this issue by default, then i installed some modules to help with CTS failure, but still ...
With or without modules, the problem is still there.
SafetyNet checks weren't there up until recently so yeah, you wouldn't see any error of that kind even if you started your flashing career from the 1.6 android ...
Hi,
i have a OnePlsu6T, i have used the whole time the Stock OS, that worked perfect with not problems.
Since several days i try to use LOS 18.1 but everythime i install LOS WIFI is not working anymore.... what does this mean:
When i try to turn on Wifi the Phone hangs and i get a error Message for a Timeout in the Systemapp.
When i roll back to the orginal OS Wifi works again with no problems.... i tryed this now several times... everytime LOS is running i have the WIFI Problem.
How do i isnatll LOS:
LineageOS Downloads
download.lineageos.org
Install LineageOS on fajita | LineageOS Wiki
wiki.lineageos.org
I also used diffrent LOS Versions, same problem, i cannot turn WIFI on..... With Stock, no Problem....
nobody has a idea?