Not sure if I'm posting this in the right place feel free to move or delete it if needed.
My question is...
I recently flashed cm 10.2 nightly onto phone. Now the first one I flashed gave me an option to change the reboot button to show an additional menu for reboot options (boot to recovery, reboot, etc). But after flashing that latest nightlies for the past 2 nights I still have the option to select for a reboot menu but nothing shows up. Thought maybe it was just the latest update until I flashed today's/last nights update.
Not a huge issue as I can always hard key into my recovery but it was a nice feature. Just wondering if anyone knows why this may have happend.
Thanks
Sent from CM 10.2 optimized sph-l710
So, I have a rooted OnePlus 3 with CM 13.1 Snapshot. But wanted to try CM 14.1. So I wipe Cache, Dalvik, Data and system, and install CM 14.1 nightly. After messing with it for a few days its was not daily driver ready for me. So same ting and install CM 13.1 back.
Now, I setup phone and all. I want to go back to TWRP to flash Exsposed. Suddenly it asks for a password (said no thanks in setup) so I assumed it would be my pin, but that was incorrect. I started the phone back up and asked for a start-up pin (even I said no thanks in setup) but that was my pin. So I tried to chance it into a pattern and hoped it would update in TWRP.
I go back to TWRP still incorrect, I go start my phone back up, but now it saying that the startup pattern is incorrect. I'm 100% sure is correct.
Now I can't enter TWRP and/or my phone.
Please help me, thanks.
Did u happen to restore from backup ?
You need clean install, else the pin information might had an issue,
This issue presence in 3.0.2.0 TWRP not sure whther it's been fixed or not.
Solution is dont use PIN (remove it) prior to doing backup
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:
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
Ever since updating to A10 on my OnePlus 5t, I can no longer access the "SIM & network" menu within "Wi-Fi & internet". Each time I do, it loads a white page briefly with com.android.phone.oneplusOPMSimActivity as text across the top before kicking back to the previous page. If I try more than once, then the popup for "com.android.phone keeps stopping" comes up with the options for "App info" or "Close app". Each time I try to open this menu, the cell network drops and then reconnects. All of the other options in the "Wi-Fi & internet" menu work as expected.
Yesterday is when I started this whole process. I initially had my phone on the OOS version from late December 2019 (I don't recall the exact version number) with TWRP 3.3.1-0 for recovery and Magisk 20.4. I went into recovery, flashed the A10 OTA full zip, flashed the TWRP 3.3.1-x blu_spark v9.110 recovery, flashed Magisk 20.4, then booted like normal but had no cell connectivity at all (no baseband, IMEI was unknown, etc). After a lot of troubleshooting and reflashing several times, it turns out the one Magisk module that I had installed was not compatible as once I removed it and rebooted, the cell connectivity worked fine.
Fast forward to today and I noticed that I could not access the "SIM & network" menu. I have tried reflashing everything again; removing Magisk and leaving TWRP; going back to full stock without root; booting into safe mode; flashing back to TWRP, wiping Dalvik / ART cache, Cache, and System, then flashing OTA, Magisk, and blu_spark kernel 199; booting into TWRP and wiping Dalvik / ART Cache, Cache, and System, then flashing the OTA without TRWP or Magisk; etc. I could not access the "SIM & network" menu without the app crash at any point, even in safe mode on the factory ROM without root or custom recovery. I also tried clearing the cache and data for com.android.phone, SIM Toolkit, and Phone without any change.
I have not yet tried to take my device completely back to factory state yet (wipe all partitions and start from scratch) as that will take an eternity to restore from. If I have to I will, but I will try every option available to me before I do.
I did a logcat through adb and reproduced the problem. I'm not an Android dev so the logs are of questionable use to me but may point me to something to look at.
Any thoughts on what I should do? Is this something having to do with the previous recovery or root? Is this something caused by existing files on my phone? Is this something broken in the factory OTA and I need to contact OnePlus? The phone is functional otherwise, but man it is annoying not being able to access this menu.
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
---------- Post added at 07:32 AM ---------- Previous post was at 07:31 AM ----------
Have you tried wiping data while on "full stock" state? (you will not lose /sdcard)
If that doesn't work, I would suggest that you use Unbrick tool 9.0.11 (which wipes everything including /sdcard) and OTA to OOS 10 (and reunlock).
I had the same problem, dirty flashing the ETA from this xda post has fixed the issue for me for now: https://www.xda-developers.com/oneplus-5-5t-stable-android-10-oxygenos-10-update/
So, I hadn't messed with this for a while and just put it on the back burner. That was until I realized that I could not make calls as I would just get a bunch of chirping, garbled, chipmunk like sound which made the call useless. It worked fine if I answered a call, but not if I made one. I figured it was related to this issue so I went through the process of trying to get things working again. I tried just flashing the A10 OTA again with the blu_spark TWRP and Magisk 20.4, but that didn't fix it. I then proceeded to try and do a full backup of my phone as I was going to try the full wipe and start over fresh, but trying to backup everything is a joke through the USB2.0 connection on this phone let alone trying to get everything just in case I wanted to roll back to how the phone was working prior to the wipe.
At some point I gave up on the backup stuff and just got my user data. Then I got the idea to try going back to the previous working version of Android Pie. I don't recall what my thought process was, but it didn't end up working. For whatever reason, the 53 update was doing the same thing the 54 update did where it would boot up and immediately power off once the lock screen came up. It worked fine before with update 53, but now it wasn't so I flashed back to A10. Now, suddenly, I've noticed that I can access the "Network & SIM" section of the menu without that error from before. I don't know when or what fixed that issue, but it works every time now. Mind you, I did wipe the Dalvik/ART cache, cache, system, and vendor partitions at various points in my attempt to get things working, some of them more than once. I also played around with what partitions were mounted within TWRP though I really did not know what I was doing.
The chipmunk, chirping, garbled thing is still there, but it sounds like many people have had that issue with A10 on other phones. So luckily enough, just turning on and off speaker phone fixes the issue immediately (but I believe for just that call). That is an easy enough work around for me. As much as I want to leave my phone alone, I still have an issue where the phone always boots into recovery first and I have to select reboot > system through TWRP for the phone to boot up normally. I tried reflashing things multiple times, wiping the various partitions, and even some commands from a Nokia forum, but nothing worked. I imagine this is because I messed with the mounted partitions within TWRP and did a flash, but I am not sure on that. I think it could be that the system is booting into recovery because it thinks that is the "normal" partition with the whole A/B partition system, but again, I am not sure on that. I may post again if I end up figuring that all out.