Just installed freshly downloaded lineage os 15.1 with open gapps on nextbit robin. After a factory reset, going through the registration screens, when I get to the final "LineageOS Features" page, the "next" button has no effect. Has anyone observed this behavior? I've been through the entire process several times but the problem persists. I think I can work around it by rebooting the phone several times, but I'd like to know that I have a clean install. Any advice would be appreciated. Here are the latest release files I'm working with:
open_gapps-arm64-8.1-mini-20180905.zip
lineage-15.1-20180903-nightly-ether-signed.zip
addonsu-15.1-arm64-signed.zip
Related
I can't activate the developer option. I've tried hitting android version 7-10 times...the clicks register but nothing happens. I've wiped data, cache and Davlik and even system, used TWRP sideload to install lineage-14.1-20170619-nightly-clark-signed.zip along with open_gapps-arm64-7.1-full-20170621.zip. Still can't activate developer option after going through setup.
Is there something else I have to wipe?
I've been using CM and LineageOS for over a year, but this problem just suddenly appeared. Actually what happened was that Developer Option disappeared when I was in Developer Option...running lineage-14.1-20170605-nightly-clark-signed.zip....I must have hit some button by accident but Developer Option just disappeared and I can't get it back.
Adendum: I decided to bit the bullet and flash with the latest nightly of AICP and Developer Option is back....in fact the phone seems much quicker. I suspect that there's a bug in LineageOS somewhere....so anyone with this problem....try another ROM...maybe one with nightly updates.
I tried to flash my Wileyfox Swift 1 to Lineage today, from its Android 7.0 rom.
I downloaded twrp-3.1.1-crackling.img and lineage-14.1-20170703-nightly-crackling-signed.zip.
I then followed the instructions on the Lineage OS site for a Wileyfox Swift to the letter to get the Lineage rom flashed (with the one exception being I also "wiped" Internal Storage, along with Cache, System and Data partitions). I didn't try to install, or want to install, the Google Apps.
Everything worked exactly as expected, right down to the absolute final step in the guide. When I chose to Reboot, then System, I just found myself back in the bootloader. No matter what I do, I just keep booting back up to this. I still have full access to recovery mode, but I just can't load an OS or get past the bootloader screen when I restart.
I have an old Cyanogen mod I have been able to revert to in the mean time, but I'm struggling to understand what I did wrong here. Can anyone provide any help/suggestions?
I tried again this afternoon and everything appears to have worked. I've loaded Lineage OS successfully and everything is working well. I'm still not sure what happened the first time, but all is good now.
I had the same issue. After installing an old CM13 release (with TWRP), turning everything off and then start from scratch with LOS 14.1, everything worked. It seems that CM13 does have a side effect that is needed for LOS 14.1.
I have been running Lineage OS on my OP3TMBE since the April 20th edition.
I am using TWRP 3.1.1-2 and Magisk 13.3.
Up to the Lineage OS 14.1-20170721-NIGHTLY-oneplus3 update, things have been working fine with each and every update.
Once I installed the above update, I lost my home button but it was remedied by installing the Open Beta 11 Firmware/Modem software from OnePlus.
I tried to install the Lineage OS 14.1-20170728-NIGHTLY-oneplus3 update and all hell breaks loose.
Google services continually crashes.
Play Store starts and just sits at the refresh screen.
I can't get any application to run for more then a few seconds.
I have had to revert to the Lineage OS 14.1-20170721-NIGHTLY-oneplus3 image I have backed up in TWRP in order to get my phone running again.
Is there something I am missing to go forward with this new nightly ???
Thanks,
Pete...
Oneplus 3T lineage 17 Bluetooth issue
I have fresh install of lineage 17 and all has been great other than not being able to hear anything phone ringing through any of my Bluetooth devices and the phone does a short start to the tone but ends it after one second or so. This is boggling my mind as to what is the problem. I've reset the Bluetooth and cleared the cash but nothing has worked. Please help me ?
Hello, long time lurker, first time poster because I started having an issue that I couldn't find any information about. Over the past few months, my power button has become increasingly unresponsive. It started just taking a couple clicks to lock/unlock every once in a while, but now I'm lucky if it will function properly a couple times a day. I am currently on the most recent LOS 15.1 build, but have had the problem on several different ROMS. It perplexes me because it works perfectly in recovery and in making selections in the unlocked bootloader boot menu, but has issues when booted into the ROM. Since the problem started I have tried stock Nougat, Resurrection Remix, OmniRom, OOS open beta 38 , and now LOS 15.1 with the same issue in them all. The fact that it works fine in recovery is what really throws me off. Any help would be greatly appreciated. Let me know if you need any more information.
I recently upgraded the Motorola One Action LOS4M to the latest 4-7-2022 build and, after the typical LineageOS loading screen (which lingered an abnormal amount of time), it shut off on its own and was sent to the LineageOS Recovery saying the ROM was "corrupt," and to do a factory reset to possibly fix it. After trying that a few times (including a TWRP advanced wipe), I get the same result of being sent back to the recovery with the same message installing the Official ROM from LOS4M official site. Anyone else having this problem with this build, and any of the recent Official LineageOS builds (not the 'for MicroG' builds) so we can tell where the issue is? The previous build (3-21-2022) still works fine so had to downgrade to get the phone to work.
You should try the new 19.1 build and see if it works.
From reading the wiki, you should use "MindTheGapps".
If you're not looking to do that, isn't a way to use MicroG "rootless" (without flashing it)?
This could be a bug, as none of the builds are stable (nightly).