For the last 2.5 weeks I have been unable to update to any of the newer Nightlies for Cyanogenmod 13 on my Asus Zenfone 2. After the update is finished my phone claims I am using the wrong password to try to access my phone. I am not using the wrong password, updating seems to change it for some reason. Because I am unable to access my phone I am forced to boot into TWRP and revert to the last build that was stable for me. So far I have only tried two newer builds, the most recent one as of this post (August 3rd) and another one last week (July 27th). Neither work, the build I currently run that works with my current lock screen password is July 17th.
Nightlies for my specific device.
I have done a bunch of forum and google searching and nobody else seems to have ever had a problem like this. I would try to report this as a bug to the CM team but bug reports aren't allowed for Nightlies.
Any help is greatly appreciated.
Edit: Fixed
I fixed the issue by disabling the lock screen, updating to the latest nightly, and re-enabling the lock screen.
Have you tried clean flash?
Until the maintainers (see Lineage Info/Maintainers at http://wiki.lineageos.org/d2att_info.html)
have a chance to create a thread, let's share our experiences with the LineageOS 14 Nightlies here
Latest LineageOS 14 Nightlies
https://download.lineageos.org/d2att
i am just a novice but.......I did a clean install of the 1/23 rom with the mini gapps and everything went well as expected. Wifi, calls/data, bluetooth, battery life, camera all work perfectly for my limited needs.
The only hiccup I had was in doing the the 1/30 update. When doing the update using settings, Lineage will download the update and boot to TWRP, but will not automatically install the update. Easy enough though, as I performed the update manually.
I can't complain. I have a five year old device with up to date software and security patch. All I can say is thanks to these amazing developers.
yoshkapundrick said:
i am just a novice but.......I did a clean install of the 1/23 rom with the mini gapps and everything went well as expected. Wifi, calls/data, bluetooth, battery life, camera all work perfectly for my limited needs.
The only hiccup I had was in doing the the 1/30 update. When doing the update using settings, Lineage will download the update and boot to TWRP, but will not automatically install the update. Easy enough though, as I performed the update manually.
I can't complain. I have a five year old device with up to date software and security patch. All I can say is thanks to these amazing developers.
Click to expand...
Click to collapse
Did you use the addonsu*.zip file (https://download.lineageos.org/extras) to root the device. If so, did you have any problems?
No I didn't. I was only changing roms from cyanogenmod to lineage.
With 2017-02-13 nightly installed, I was able to finally performed a successful backup and restore in TWRP 3.0.2-0.
Phone was setup with a clean install using the following:
lineage-14.1-20170213-nightly-d2att-signed.zip
addonsu-arm-signed.zip
open_gapps-arm-7.1-nano-20170213.zip
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Other people I know have had this problem and some of them are on different cell providers.
I had to turn off the automatic settings and set the date and time manually.
tjensen said:
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Other people I know have had this problem and some of them are on different cell providers.
I had to turn off the automatic settings and set the date and time manually.
Click to expand...
Click to collapse
Same problem here. Also home button wake the device regardless of the setting under buttons sub menu and a very erratic compass after several attempts to calibrate.
Anyone getting "Updater process ended with ERROR 7" error with installing 20170220 update?
yoshkapundrick said:
Anyone getting "Updater process ended with ERROR 7" error with installing 20170220 update?
Click to expand...
Click to collapse
I did, so downloaded again and still the same... Wiped everything and flashed it anew; working great.... simply can't update existing rom... or so it seems...
nextmouk said:
I did, so downloaded again and still the same... Wiped everything and flashed it anew; working great.... simply can't update existing rom... or so it seems...
Click to expand...
Click to collapse
Yep, previous nightlies I could dirty flash. However, 2017-02-20 nightly I could only clean flash to install.
In TWRP:
Dalvik/ART Cache - Wipe
System - Wipe
Data - Leave
Internal Storage - Leave
Cache - Wipe
Micro SDCard - Leave
USB OTG - Leave
Dirty flash produces error
Dalvik/ART Cache - Wipe
System - Wipe
Data - Wipe
Internal Storage - Leave
Cache - Wipe
Micro SDCard - Leave
USB OTG - Leave
Clean flash produces no error
UPDATE: 2017-02-21 nightly can be dirty flashed
20170221 update works nicely in updating previous versions.
tjensen said:
Automatic syncing of date and time with network does not work all the time on 2017-02-13 nightly.
If you set the date and time to use network provided time (Settings\Date & Time\Automated date & time) it uses the correct time for a while but then switches to some random time.
Click to expand...
Click to collapse
This is still problematic int the 2017-02-27 nightly. At least on my device, it's a time zone issue. That is, the automatic time zone setting isn't working. So, the minutes are right, but the device shows GMT instead of CST/CDT.
Everything else seems to be working, and I find Lineage OS a bit "snappier" than Oct-OS - probably because of the absence of add-ons. But, hey, it's a 4.5-year-old phone.
New TWRP version 3.1.0-0 released!
https://dl.twrp.me/d2att/
Anyone notice a moderate improvement of the compass (I had not checked in months since cm). My readings used to be wildly variable, however now it seems to be consistently off 20 degrees.
FYI: After encrypting the phone with 20170320 nightly installed, the sim card is not recognized.
First I did a CLEAN install of 20170320 nightly; sim recognized.
Next I did not make any changes except encrypted the phone; sim NOT recognized.
SIM not recognized
After the first boot on 20170328 the SIM card is recognized but once the device is rebooted the SIM card is not recognized anymore, the same with 20170320.
FYI: Posted over on reddit an inquiry on the status of the compass accuracy on our D2att LineageOS device.
https://www.reddit.com/r/LineageOS/comments/64v74o/d2att_compass_accuracy/
The d2att does not appear to be supported anymore by LineageOS.
There are no maintainers listed at https://wiki.lineageos.org/devices/d2att anymore.
And then there is this in blazing red on the page:
"The Samsung Galaxy S III (AT&T) is either unmaintained or does not meet the criteria needed for official LineageOS support status. A build guide is available for developers that would like to make private builds, or even restart official support."
If anyone has any news it would be appreciated.
tjensen said:
The d2att does not appear to be supported anymore by LineageOS.
There are no maintainers listed at https://wiki.lineageos.org/devices/d2att anymore.
And then there is this in blazing red on the page:
"The Samsung Galaxy S III (AT&T) is either unmaintained or does not meet the criteria needed for official LineageOS support status. A build guide is available for developers that would like to make private builds, or even restart official support."
If anyone has any news it would be appreciated.
Click to expand...
Click to collapse
Thanks to tjensen For posting this.
For those wondering, Yesterday (04/14/2017), I posted the following on reddit:
Samsung Galaxy S3 not supported anymore?
https://www.lineageoslog.com/14.1/d2att Unless I'm incorrect Lineage 14.1 support for d2att, d2spr, d2tmo and d2vzw has been discontinued. Can anyone confirm this?
Link to reddit post: https://www.reddit.com/r/LineageOS/comments/65diqo/samsung_galaxy_s3_not_supported_anymore/
Chuckles5150 said:
Thanks to tjensen For posting this.
For those wondering, Yesterday (04/14/2017), I posted the following on reddit:
Samsung Galaxy S3 not supported anymore?
https://www.lineageoslog.com/14.1/d2att Unless I'm incorrect Lineage 14.1 support for d2att, d2spr, d2tmo and d2vzw has been discontinued. Can anyone confirm this?
Link to reddit post: https://www.reddit.com/r/LineageOS/comments/65diqo/samsung_galaxy_s3_not_supported_anymore/
Click to expand...
Click to collapse
Just last week the d2att was ranked 89th out of 1,254 devices for the most installs of the LinageOS (according to LinageOS stats page).
With that kind of popularity and interest I thought it was safe and would always have maintainers wanting to continue the builds. :crying:
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
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.
Until now I used a LOS 14.1 with GApps and I decided now to upgrade to lineage-17.1-20200530-nightly-m8d-signed.zip by flashing TWRP 3.3.1-0 and install the rom afterwards.
Everything worked fine except of problems with SD card (Failed to initialize).
But after a several reboots my device got stuck in a bootloop I don't know what has gone wrong - I just have installed apps and customized some settings.
This problem also occurs every time I recover a backup with TWRP.
I did some trials with:
- Flashing 10 different recovery images from TWRP 2.8.1-0 to 3.3.1-0
- Installed Lineage 16.0 and 17.1. Could not find any downloads for 14.1!?
I have also tried installing multiple mokee builds: Same behavior! And other users have similar problems with their devices. So this does not belong to m8d devices only and also not only to lineage but maybe to AOSP!?
I have flashed only TWRP and lineage - not the firmware. And i have exactly done formating as described in the installing-instructions: Formating and wiping system and cache. But additionally I have tried many variants.
I'm not an expert, but I have a look in the dmesg.log and did not find anything interesting.
I have compared a log of a new and fresh installed LOS 17.1 (with NO bootloop) with a damaged (bootloop) LOS.
Info:
I've noticed a repeating and very quied sound like "knock, knock" while got stock in bootlop..!?
---
Now I have installed crDroidAndroid-9.0-20190315-m8d-v5.2 and this works well (e.g. recovering backups) except of smaller issues (as i found so far):
- can't get screen rotation working
---
What I don't understand:
Lineage 16 (based on Android 9) fails, but crDroid (based on Android 9, too) works!?
Is this a matter of a too old firmware? Can't find a new one for my S-ON device:
- modelid: 0P6B64000
- cidnum: HTC__102
Thanks,
Marco
happens the same to me following this post https://forum.xda-developers.com/htc-one-m8/general/rom-lineageos-16-0-htc-one-m8eye-t4081877 and the TWRP by @HarshDB is not working, that goes to the stock recovery menu, I tried another TWRP but that rom doesn't work
raisonier said:
happens the same to me following this post https://forum.xda-developers.com/htc-one-m8/general/rom-lineageos-16-0-htc-one-m8eye-t4081877 and the TWRP by @HarshDB is not working, that goes to the stock recovery menu, I tried another TWRP but that rom doesn't work
Click to expand...
Click to collapse
That TWRP is only for M8_Eye and not for regular M8 or M8 dual sim.
Which one do you have?