Did you flash clean? I flashed dirty (came from lineage-16.0-20200208-UNOFFICIAL-i9300) and have the same problems. I am back to 20200208, which is working fine.
Maybe a clean flash works for 20201109?
Did you flash clean? I flashed dirty (came from lineage-16.0-20200208-UNOFFICIAL-i9300) and have the same problems. I am back to 20200208, which is working fine.
Maybe a clean flash works for 20201109?
Yeah i flashed cleanDid you flash clean? I flashed dirty (came from lineage-16.0-20200208-UNOFFICIAL-i9300) and have the same problems. I am back to 20200208, which is working fine.
Maybe a clean flash works for 20201109?
Changelog
20.09.2020 - build #7
- Sources update (September 2020 ASB)
- Enabled NearbyMessagingService back (this seemed to break google account login)
- GPS fix (credits to @rINanDO)
- Updated kernel to LK 3.4.67
- Added CPU and GPU OC
- Added more CPU governors (including ZZMoove)
Download:
https://androidfilehost.com/?fid=8889791610682941485
So i've installed this new build and my happiness last 5 minutes.
My SIM card is not detected and when i passed to another phone asks for my PUK and says that the SIM is locked (zero attempts available)...
Now i have no SIM card but can enjoy the build on my forever prefered S3![]()
Any ideas on how to improve my situation?
I tried with another SIM card (PIN unlocked but stills not detecting)
Turn off PIN Code in another phone if possible. If the SIM Card is completely locked ( no PUK Code remainings ) then contact your network provider for replacement card.
Did u made Nandroid backup before ? *#06# check IMEI. Made a EFS backup before ?
Regards !
Mine won't boot.
Wiped everything. Dalvik, cache, internal storage, system and data. Flashed ROM and latest nano gapps. Got stuck on boot animation (for over two hours).
What am I doing wrong?
Gesendet von meinem F1 mit Tapatalk
Mine won't boot.
Wiped everything. Dalvik, cache, internal storage, system and data. Flashed ROM and latest nano gapps. Got stuck on boot animation (for over two hours).
What am I doing wrong?
Edit: I'm using TWRP 3.2.3-0. Could this be a problem?
/*
* Your (probably expired) warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
A rough timestamp of when the issue occurred is also useful.
to quickly & easily capture logcat (Main log), Kernel log (dmesg) & Last Kernel log (last_kmsg which is important in case of unwanted reboot) without using a computer + adb or use a Terminal emulator on the phone:
Done! And make the dev happy.
- Root the phone
- Developer Options > Store logger data persistently on device > select All. More info about it here on developer.android.com
- Install the free SysLog. (screenshot)
View attachment 4644180
- Reboot the phone & reproduce the problem(s).
- Open Syslog & select logcat, dmesg & last_kmsg. Add some significant keywords in the bottom including in Notes describing the bug & hit Take log.
- The individual logs + a .zip of all of them will be saved in /sdcard/Syslog. You must rename them .txt to be able to attach them to an XDA post like logcat.log > logcat_log.txt for example. Or you can choose Share which will .zip them & then you can attach to a post or upload somewhere & link to in your post if the .zip is too big for XDA's attachment service (20 MB max).
***
Bug Reports & Logs?
If the phone is not rooted you can grant this permission to enable Syslog using ADB (15 seconds ADB Installer) & a computer:
You can also install an app like MatLog to analyse the logcat, filter it, search in it, export files etc but Syslog is fast & easy. If not rooted grant permission for MatLog:
- adb shell pm grant com.tortel.syslog android.permission.READ_LOGS
***
- adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Mr @ChronoMonochrome
Given that the lineageos team has begun merging LOS 16 to LOS 17 ...
Will you be back to this device(S3 i9300) with Android 10?