My T805Y gets stuck during Lineage boot animation. The problem first occurred after an OTA update from version 7.1.2 Nov to 7.1.2 Dec. Clean reinstalling either version would only yield the same result.
After more tests and going back to stock 6.0.1 I have now found that I can install LineageOS 7.1.2 versions up to about 30Jun2018 (confirmed it with Unofficial/RR/Mokee versions). Newer versions will all hang during boot animation.
What can cause this issue? Incompatible driver in the newer version? Hardware defect?
Is there a log that would give some hints?
Related
Clean Flash Marshmallow ROMs - stuck at "Android is starting... Starting apps"
Hi,
I just performed a clean flash of some of the Marshmallow ROMs and my stock unlocked 16GB maguro didn't take micro-gapps, had to flash only nano gapps. After flashing all the files, the device boots up and performs the 'optimizing apps x of x' but gets stuck at the starting apps. It doesn't go beyond that step even after a couple of hours.
I've tried the following ROMs
CM 13
zzpianoman 6.0.1 ROM
werty100 6.0.1 ROM
Can some one help me with this?
P.S. I have checked the thread here -http://forum.xda-developers.com/galaxy-nexus/help/stuck-android-upgrading-starting-apps-t2825113 and it didn't help
Thanks!
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc, does anyone know what the problem could be?
Have you flashed the latest firmware? If not, I think this is why due to you being on a very old version (6.0.1) and as you are not flashing official OxygenOS you are not getting the newest firmware.
Download and flash the latest firmware here:
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Pick the right one for the ROM you are flashing (For Freedom OS installing firmware Open Beta 14 - Firmware + Modem under 7.1.1 should be good.)
Note: After you have flashed the firmware the next time you reboot the phone it will appear to not turn on for a few seconds, this is normal while it updates, don't worry
Let me know if you have any questions
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 ?
Currently my OP3 has LineageOS 15.1 with installed firmware and modem from Oxygen Open Beta 32. Is it really safe to upgrade firmware to the latest open beta (for now it's version 37), as it is suggested at official LOS 15.1 for OP3 thread? Won't be there a problems with, for example, device encryption, which might be changed in firmware packages?
Always updating my MODEM and Firmware and never had problems.
I did try to flash latest LOS 15.1 today with latest OB37 and had an Encryption Unsuccessful error and could not boot, asking me to Format. I actually do not know what was causing the error as I did not try to troubleshoot, but it was the first time I was trying to flash any rom with the latest OB37. Don't know if that means anything.
I always flash OB31, it has better battery drain than latter ones.
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).