Develop Bugs

[OFFICIAL] LineageOS 17.1 for Xperia Z3 [CLOSED]

Thread depreciated. There won't be anymore official LOS 17 builds for this device. ​
Please jump to:
The official LineageOS 18.1 thread for z3 or dedicated thread for z3dual​
if you are looking for new builds.
-------------------------------------------------------------------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project (AOSP) and can be used without the need to have any Google application installed.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below. There are also inofficial TWRP recovery builds available - if you want to use TWRP you need to ensure that it is compatible with Android 10.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Detailed instructions:
Install LineageOS on z3
Downloads:
Final official build of 17.1 ROM for Z3:
Google Apps (optional): Open GApps (choose ARM as Platform and Android 10)
Changelog:
Changes for z3
Source Code
The source code of LineageOS is available here. If you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The z3 device tree is available here.
The kernel source code for this device is available here. The used configuration is lineageos_shinano_leo_defconfig available at arch/arm/configs/lineageos_shinano_leo_defconfig in the kernel source.
Bug reports:
How to submit a bug report - Please do not submit anymore bug reports for 17.1 - try 18.1 first please.
LineageOS GitLab
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
Thanksgiving
Thanks to everyone who ever contributed to the custom development for this device, especially:
@nailyk
@rcstar6696
@tomascus
@Diewi
@xkeita
@drakonizer
XDA:DevDB Information
LineageOS 17.1 for Xperia Z3, ROM for the Sony Xperia Z3
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12

Remarks, Questions & Answers
Known Major Issues
Official Lineage Recovery is currently broken. There are two options:
TWRP recovery (inofficial build, optional): TWRP
Unofficial Lineage Recovery build.
WiFi issues in some countries (e.g. Iran): low speed @ 5GHz, hotspot and connection issues. This topic is related to a dirty workaround. A solution is here but will not be integrated into our official Lineage kernel.
Disk Encryption: Disk Encryption is working, however not with the default password (no password). Workaround: Set password first, then start disk encryption, not the other way round! Solved
Bluetooth Low Power may create wakelocks in certain scenarios.* Solved
Thermal throttling of CPU cores: Due to a design issue of the thermal manager ("Thermanager") when used with older kernels like ours you have to expect that the frequency throttling of the CPU cores may fail, especially after(!) the device was getting hot and is recovering. This may lead to performance issues until reboot and other issues. Workaround: reboot device after heavy use.*
Reported size of adoptable storage seems to be wrong. However, remaining free space seems to be reported accurately.
Formating a SD card as internal storage may cause the card to be reported as "corrupted".
Screen rotation may not work after a while. Solved, to be integrated into builds from mid April 2021 onwards.
You tell us (with logs please)...
* To our knowledge, these are general issues on all AOSP/LineageOS based custom ROMs for this device family (Shinano). However I would be happy to be mistaken here and if sombody has a solution.
Further hints
This ROM currently does not work with the Z3 Dual SIM variant. Here's a build for the Z3dual.
If you need Google Apps we recommend the OpenGApps "nano" package, however, I personally use the "stock" package which works as well. The ROM also seems to work with MicroG and BiTGApps.
Magisk - see this post for issues with latest Magisk versions
If you need to install a lot of apps you may run out of internal DATA storage capacity, especially if you install one of the larger GAPPS packages. These apps are initially placed on the system partition and do not cost you DATA capacity. However, every update which comes over the Play Store then fills up your data partition. Using an SD card formated as "external" storage does not help you much (unless you use a tool like app2sd which is no more recommended) and isn't encrypted. Formating the SD card as "adoptable storage" comes with the drawback that some apps do not allow to be migrated to this storage, and unfortunately this is true for some streaming music/video apps which need to store a lot of data obviously (for offline use). The solution I am using is to partition a SD card as "mixed", which gives you the possibility to offload at least some apps to adoptable storage while you still have a classical external FAT32 partition where e.g. your streaming app can save its offline files:
Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.
Follow this guide to partition your SD card. Note: all data on the card will be lost.
Restart your phone.
When you are notified that a new storage card has been detected, use it as "external". (Your internal partition has been recognized at that point already and does not need interaction.)
Go to settings / Storage. Verify that you see three entries: 1. Your internal phone storage of 16GB. This includes your SYSTEM partition. 2. Your SD card with an SD card symbol. The size shown should be the full capacity of the card. If you click on it, your "external" partition is shown (misleading) as "System" and blocked. Click on migrate data to migrate all possible apps to your adoptable storage. 3. Your sd card partition formated as mobile storage (unencrypted!).
How to create logs:
Follow How To Logcat
When creating a log, can you make sure you run the command with the -b option to include kernel messages:
Code:
adb logcat -b all
If your device randomly reboots:
Go to Settings -> System -> Advanced -> Developer options -> Store logger data persistently on device. After the reboot occured: Pull the logs from /data/misc/logd/ (root required).
If your device crashes during boot and reboots to recovery:
Code:
adb pull /proc/last_kmsg
Please submit logs from clean systems without "Exposed" or similar modifications in place
Your feedback is wanted regarding the following topics
Please have a look at lineage-18.1!
A big THANK YOU also to @ronnay ryukay for having maintained the inofficial 17.1 thread!

Thank You.
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?

mer5ad said:
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?
Click to expand...
Click to collapse
TWRP and Lineage Recovery are different things. See Post #2 for details. Current TWRP version is 3.3.1.0 iirc.

Mr.Tom_Tom said:
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code:https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12
Click to expand...
Click to collapse
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_

dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing and b. i had to regrant permissions for most apps . but that was because i m using BitGapps instead of opengapps. i confirmed it after reading the BiTGapps post!!
[edit] the permission regranting problem of bitgapps has been fixed

nikapos said:
dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing but thats maybe because i m using mindthegapps instead of opengapps and b. i had to regrant permissions for most apps.
Click to expand...
Click to collapse
Hmm, ok, sounds good. Will try it. :good:

0LDST4R said:
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_
Click to expand...
Click to collapse
download D6603_23.5.A.1.29.ftf rom and use FLASHTOOl software.

Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...

kwasior500 said:
Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...
Click to expand...
Click to collapse
not supported by device hardware. be reasonable!

NOT 4k 120FPS, 4k OR 120FPS

Upgraded from 16 to 17 (dirty flash). Most things seem to work well. A few minor issues:
- Data connection occasionally stops working. Can't figure out why, but I think when I disable/enable wifi is connected. Need to dig deeper
- Smart lock with BT device stops working after a while. Have to remove the device and re-enable
Happy otherwise. Good job!

@Mr.Tom_Tom
how can mount System to boot with RW ?

dsp3 said:
Upgraded from 16 to 17 (dirty flash).
Click to expand...
Click to collapse
Thanks for this feedback, but please do NOT dirty flash. When installing official LOS17.1 the first time, do this with a clean setup.

WiFi 5GHz (Russia) does not work. Can you make changes to the kernel?

new update with working calendar widget. i also had to boot into recovery to reflash bitgapps fo the phone to boot normally.
---------- Post added at 06:08 PM ---------- Previous post was at 06:00 PM ----------
where is the update stored if downloaded from settings->system->update? i want to make sure it is promptly deleted after install.
[edit] ok, you have the option to delete the files after install. the option is found within the update settings.

Just tested Google Duo.
No audio issues. Finally. Thanks, thanks, thanks.
So i guess there are no probs in free hand mode too.

Amazing rom. All very smooth. Thanks a lot!
Unfortunately the back camera does not work for me.
First I was able to start it and a black picture came up. Yesterday I did the new OTA update, that didn't change the problem.
This morning I wanted to save logs about the problem and now the Camera App doesn't start anymore.
Logcat:
2020-09-20 10:59:54.035 8972-8972/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.lineageos.snap, PID: 8972
java.lang.RuntimeException: Unable to resume activity {org.lineageos.snap/com.android.camera.CameraLauncher}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4205)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.PhotoModule.initializeFocusManager(PhotoModule.java:2830)
at com.android.camera.PhotoModule.onResumeBeforeSuper(PhotoModule.java:2598)
at com.android.camera.CameraActivity.onResume(CameraActivity.java:1889)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1453)
at android.app.Activity.performResume(Activity.java:7958)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4195)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)*
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)*
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)*
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)*
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)*
at android.os.Handler.dispatchMessage(Handler.java:107)*
at android.os.Looper.loop(Looper.java:214)*
at android.app.ActivityThread.main(ActivityThread.java:7356)*
at java.lang.reflect.Method.invoke(Native Method)*
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)*
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)*
By forcing stop and restart I was able to reproduce the original error. The log is too big to put it in the post, therefore in the attachment.

SageDroid said:
Unfortunately the back camera does not work for me.
Click to expand...
Click to collapse
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.

Mr.Tom_Tom said:
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.
Click to expand...
Click to collapse
Thanks for looking into it. Yes, I wiped them all. Even the internal storage.

[ROM][UNOFFICIAL][12.1][DISCONTINUED] LineageOS 19.1 for Galaxy S10e/S10/S10+/S10 5G Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_exynos9820/tree/lineage-19.1

Requirements:
Any Q, R or S based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Bixby and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up, Bixby and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and Lygisk by repeating above step
with their zip/apk
Magisk
As this ROM has a working ramdisk sideloading the magisk apk is enough, just as it is
on every other device, no bootimage with magisk included or installing to recovery is needed!
I also strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.

Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
You tell me

Good job as usual!! So live display and natural (sRGB) profile doesn't work yet?

Hi @Linux4 ,
ROM boots fine, was a little put off by the change back to nice old lineage recovery style. Two issue I have encountered:
- /sdcard won't mount in recovery so I have to sideload
- I can't skip signature verification so no gapps install right now (I have tried bitGapps but to no avail either)
ROM boots unbelievably fast

Is Material You (Monet) included?

No source code? Whaat

Razuuu said:
No source code? Whaat
Click to expand...
Click to collapse
Read the posts... Bottom of first post: "Source Code: Coming soon"
Thanks a lot for your work Linux4!!

So far the Rom is really smooth and has great battery life.
Unfortunately we are getting a 403 forbidden when trying to download Gapps. Also the Rom asks to format the sdcard for some reason.
Other than that great work guys!

mike_app said:
So far the Rom is really smooth and has great battery life.
Unfortunately we are getting a 403 forbidden when trying to download Gapps. Also the Rom asks to format the sdcard for some reason.
Other than that great work guys!
Click to expand...
Click to collapse
He gave us another Gapps link.
Sdcard can't be mounted for some reason...

@Linux4 , great work, thanks a lot!
I was wondering about firmware updates. Do they come with lineageos updates or do we need to update/flash firmware still manually?

Apologies but I don't know how to do logcats, as I am new to this. However I experienced flickering once I use google maps. Also, there is this instance that the banking app I use treats the phone as emulator and not an actual device. And during login in mobile legends, gboard or the built in android aosp keyboard does not pop up whenever I try to tap the field to login my credentials.
So far, these are the things that I encountered. Other than that rom is great and smooth

mcgi5sr2 said:
Hallo @Linux4 ,
ROM bootet gut, war ein wenig abgeschreckt von dem Wechsel zurück zum netten alten Lineage Recovery-Stil. Zwei Probleme, auf die ich gestoßen bin:
- /sdcard wird bei der Wiederherstellung nicht gemountet, also muss ich seitlich laden
- Ich kann die Signaturüberprüfung nicht überspringen, daher werden derzeit keine Gapps installiert (ich habe bitGapps ausprobiert, aber auch ohne Erfolg)
ROM bootet unglaublich schnell
Click to expand...
Click to collapse
you can use the unofficial LOS18.1 recovery to install the mtg package, as well as to install magisk

does it work if i sideload magisk?

efkhai469 said:
does it work if i sideload magisk?
Click to expand...
Click to collapse
Answer at the bottom of the second post... (item number 5 + final note at the end of the post)

Hi Colleagues
everything is fine for me on this room, I don't know how to send logs, the only issue what I see just like comment.
1. Google Maps has a zoom in on A12, this also happens with other ports.
2. at least for me the audio in calls through Bluetooth, don't work it sound like a robot, in both versions, in both apps of Google Phone and on Lineage Phone app.
The rest it is working fine, just I miss advanced restart for don't make always the key combinations hehehehe.
Regards and Thanks really good job.

Thanks alot for your hard work..
Is it just me or the in-call speaker voice is so low at high-level in every AOSP rom in comparison to stock?

kachoman said:
Hi Colleagues
everything is fine for me on this room, I don't know how to send logs, the only issue what I see just like comment.
1. Google Maps has a zoom in on A12, this also happens with other ports.
2. at least for me the audio in calls through Bluetooth, don't work it sound like a robot, in both versions, in both apps of Google Phone and on Lineage Phone app.
The rest it is working fine, just I miss advanced restart for don't make always the key combinations hehehehe.
Regards and Thanks really good job.
Click to expand...
Click to collapse
Second one will be fixed later during 19.0 bringup (lineage had some patch for that which isn't in 19.0 yet)
Also advanced reboot is a lineage feature so that's why it's not there yet.
It's more or less plain AOSP at the moment

Linux4 said:
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
All cameras are working
Ramdisk is working
Known issues
VoLTE/VoWiFi
LineageOS specific features like livedisplay (for now)
You tell me
Click to expand...
Click to collapse
Another issue: the apps installed on my device can't access the phone's storage, even if I grant access to it.

ThePS4Gamer said:
Another issue: the apps installed on my device can't access the phone's storage, even if I grant access to it.
Click to expand...
Click to collapse
This isn't an issue is the consequences of the fact that selinux is enforced...

[ROM][11.0][OFFICIAL][Vanilla & GApps]Havoc OS v4.x Sofiar

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.​Has a refined Material Design 2 UI crafted by @SKULSHADY.​Many useful features that provide a smooth premium experience.​Just flash and enjoy...​
Founder & Lead Developer:​SKULSHADY (Anushek Prasal)​​DevOPS & Scaling:​Irongfly (Sukeerat Singh Goindi)​
If you like our work and would like to support this project then please consider donating.​
PayPal: https://www.paypal.me/ANUSHEK​
UPI: [email protected]​
Download ROM: https://havoc-os.com/device#sofiar​
About Havoc-OS: https://havoc-os.com​
Recovery: Vache's unofficial TWRP​
Magisk: https://github.com/topjohnwu/Magisk/releases​
FlameGApps: https://flamegapps.github.io/​
Official Havoc-OS Telegram Group: https://t.me/havocofficial​
Official Rav/Sofia-R-P Havoc-OS Telegram Group: https://t.me/+ioAiJwr1DKZiMjJl​
Havoc-OS Announcements Telegram Channel: https://t.me/Havoc_OS​
Code Review: https://review.havoc-os.com​
1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.​
2. Wipe System, Data, Dalvik, Cache.​
3. Flash the ROM, GApps (Optional), Magisk (Optional).​
4. Reboot and Enjoy.​
LineageOS (https://github.com/LineageOS)​
Crdroid (https://github.com/crdroidandroid)​
Pixel Experience (https://github.com/PixelExperience)​
And all the other Developers, Testers, Donators and Users.​
https://github.com/Havoc-OS​
https://github.com/Havoc-Devices​
Known Issues
• FM Radio doesn't work
• USB tethering doesn't work on first boot
• Must use android 10 vendor like other sofiar roms
• Android Auto doesn't work on android 10 vendor
• Stylus actions dies between reboots, just open it within settings
Havoc-OS, ROM for Rav/Sofia-R-P(commonly shortened to sofiar)
Devices: Sofiap (Moto G Stylus/G Pro), Sofia/Sofiar (Moto G Power/G⁸ Power), and Rav (Moto G⁸/G Fast)
Maintainer: ph4n70m
Build Type: Official
Credits
- Vache: The initial device and vendor tree
- Beetle84: Giving me a ton of help

What are the differences between this build and the last one? Maybe a change log?
This is a awesome build. I will say the launcher crashes at times but recovers fine. I also have to reboot occasionally to fix a bug in the sd card. It will randomly complain about the card not being formatted. It never occurred before departing stock. Running the Moto G Stylus 2020.
What exactly causes the stylus to die? Perhaps a script the runs an action in the Java app to jumpstart it?

temperne said:
What are the differences between this build and the last one? Maybe a change log?
This is a awesome build. I will say the launcher crashes at times but recovers fine. I also have to reboot occasionally to fix a bug in the sd card. It will randomly complain about the card not being formatted. It never occurred before departing stock. Running the Moto G Stylus 2020.
What exactly causes the stylus to die? Perhaps a script the runs an action in the Java app to jumpstart it?
Click to expand...
Click to collapse
Changelogs are done on telegram because i can't be bothered to update the xda post every month, maybe in the future ill have a github posted changelog, i remember the sd card issue being an issue that was complained about awhile back with havoc being extremely picky but i don't know what causes it, it dies because motorola uses proprietary stuff to start it in the background from what i can tell so its a bunch of manually editing the apk with apktool but the current brickwall is everything java is naturally output to smali files so you have to compile and decompile with that unless you want to try and do further processing which just leads to more issues. Its a big mess you when you look at the manifest and realize it uses the native android boot receiver stuff but seemingly not for starting the app. Eventually I'll get around to trying more things to fix it.

ph4n70m-404 said:
Changelogs are done on telegram because i can't be bothered to update the xda post every month, maybe in the future ill have a github posted changelog, i remember the sd card issue being an issue that was complained about awhile back with havoc being extremely picky but i don't know what causes it, it dies because motorola uses proprietary crap to start it in the background from what i can tell so its a bunch of manually editing the apk with apktool but the current brickwall is everything java is naturally output to smali files so you have to compile and decompile with that unless you want to try and do further processing which just leads to more issues. Its a big **** you when you look at the manifest and realize it uses the native android boot receiver crap but seemingly not for starting the app. Eventually I'll get around to trying more things to fix it.
Click to expand...
Click to collapse
Don't bother.. a reboot is fine with me as I only use the SDcard as a "backup" destination. I use FolderSync to copy all internal storage to the SDCard daily. Then I do TWRP backups once in a while for a full system backup (in theory). I have Titanium Backup but.. it is seriously out of date and needs work in my opinion.
I love all the Pixel integrations. A lot of the time my power screen shows the home automation stuff. That is working right now. Think turn off/on TVs etc.

Looks like there was an unannounced build uploaded on. 11/25/2021
So, maybe you might need to upgrade

Have you checked the SD card format?
I currently use a 64gb SD card with exFAT file system format and I have not yet been able to test the rom because I need to save a copy of my internal data to the pc or SD card and I would like to use this rom more stable.

This may sound like a dumb question, but how do I flash this? Do I use TWRP and flash both slots? Or am I supposed to do it from my computer via adb sideload? I ask this because when I flash through TWRP, it doesn't work. It just defaults to the OS I had installed prior, like if it didn't flash it at all. Please advise.

Android auto doesn't appear to work with the included gapps. Anyway to fix it? Thanks

deviousconundrum said:
This may sound like a dumb question, but how do I flash this? Do I use TWRP and flash both slots? Or am I supposed to do it from my computer via adb sideload? I ask this because when I flash through TWRP, it doesn't work. It just defaults to the OS I had installed prior, like if it didn't flash it at all. Please advise.
Click to expand...
Click to collapse
Install TWRP and when you flash it, it will flash it to the inactive slot.
If your phone is on slot A and you try to flash it, TWRP will flash it to slot B.
You can change the active slot by clicking on "Reboot" and you will see an option to change the active slot.

Was testing this rom out and was working great. But after the latest update 20220127, my phone started to connect to wifi hotspots randomly and forcibly even when I turn off wifi. Maybe it's a hardware issue but will definitely be switching back to the previous version. Overall, the latest update is faster in my experience besides that issue, thank you nice work!

I have the Moto G stylus xt-2043-4 that I just rooted with magisk and I'm not sure how to flash the rom I downloaded all the files so any help would be really appreciated thanks

[email protected] said:
I have the Moto G stylus xt-2043-4 that I just rooted with magisk and I'm not sure how to flash the rom I downloaded all the files so any help would be really appreciated thanks
Click to expand...
Click to collapse
Flash the rom zip with twrp

archtechmod said:
Flash the rom zip with twrp
Click to expand...
Click to collapse
Yeah I thought the same thing I figured I could just flash with TWRP but I don't have TWRP I wish I did so I guess they rooted without TWRP just magisk so I appreciate your response thank you again

[email protected] said:
Yeah I thought the same thing I figured I could just flash with TWRP but I don't have TWRP I wish I did so I guess they rooted without TWRP just magisk so I appreciate your response thank you again
Click to expand...
Click to collapse
Just a thought ,have you tried searching for a unofficial twrp for your moto g stylus and flashing ?That’s the solution I did then flashed this rom on my moto g stylus . With magisk included .

archtechmod said:
Just a thought ,have you tried searching for a unofficial twrp for your moto g stylus and flashing ?That’s the solution I did then flashed this rom on my moto g stylus . With magisk included
Click to expand...
Click to collapse
archtechmod said:
Just a thought ,have you tried searching for a unofficial twrp for your moto g stylus and flashing ?That’s the solution I did then flashed this rom on my moto g stylus . With magisk included .
Click to expand...
Click to collapse
No I haven't but I'm going to try and find an unofficial TWRP to give it a shot and thank you for the help I appreciate it TY

I use Arrow Os A13. Can I downgrade directly with havoc os 4.19?

[ROM] [12.1] [TREBLE] [UNOFFICIAL] [Gapps/Vanilla] CherishOS V3.9.5 for Nokia 8 [NB1] [DISCONTINUED FOR A13]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your 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.
*/
CherishOS is an AOSP based rom focusing on a Unique UI with many customizations.
Known bugs
- Loudspeaker is loud and creates some echo in calls
- TWRP recovery does not decrypt internal storage with a pin set, this is TWRP's fault, but does not affect OTAs, cancel when prompted for pin it will say its incorrect. [fixed with latest twrp]
- Offline charging animation does not work [FIXED in 3.5.2]
- SIM2 mobile data does not work (for dual sim users) but the sim itself works fine [FIXED in 3.5.2]
- gyro sensor creates a drift in some games [FIXED in 3.6]
- requires flashing atomix zip for WPA2 hotspot to work (attached) < now included, needs test. [no longer required]
- you tell me
Please ensure T-virus-2.0 is installed before attempting to flash this rom! follow this guide here: https://forum.xda-developers.com/t/nokia-8-nb1-full-rom-installation-guide.4349525/
Selinux status: Enforcing
Download
ROM
Release CherishOS 3.9 [12.1] [Gapps/Vanilla] [Unofficial] · megafire91/NB1-CherishOS_Releases
CherishOS for NB1 treble only [T-virus 2.0 required] Changelog: https://t.me/CherishOS/1120 Device changelog: Changed to LOS camera to resolve not saving issues Audio visualiser now working Offlin...
github.com
Recovery
TWRP:
Release TWRP 3.6.2 A12.1 for NB1 · Niemandausduisburg/android_device_nokia_A1N-NB1-TWRP-new
TWRP 3.6.2 A12.1 for Nokia 8 (NB1) Flashable bootimage & flashable zip availible. Known Features xD: - MTP / ADB don't work sometimes. To fix disable & re-enable MTP in Mount-options. - ADB sidelo...
github.com
The Zip installer is used for easier access when flashing roms, the img is there in case you have forgotten to flash the zip and have lost recovery.
Flashing instructions
Clean Flash:
1. Take a full backup of both your data and internal storage as it may be wiped.
2. Download the ROM from above link and flash the recovery zip
3. Download the recovery zip of your choosing and flash it if not already on latest twrp.
4. boot into recovery and either remove rom pin or wipe internal to have it accessible to copy rom zip over (due to the decryption bug) or just use external sd card to flash.
5. flash the rom zip and recovery zip again right after the rom zip before rebooting , it will reboot you to recovery automatically in other slot. (optional) cherish recovery included.
6. Flash any mods you may want
7. run factory reset from recovery, or wipe /data and /dalvik if you don't want internal wiped.
8. reboot to system and enjoy!
(flashing Atomix zip is only needed if you flash the .img to fix hotspot, but not with the zip)
Installing an OTA (Dirty flash):
1. Download the ROM from above link
2. flash the rom zip and recovery zip and let it reboot into recovery.
3. wipe Dalvik cache only
4. flash any mods you had previously flashed.
5. reboot to system and enjoy!
(flashing Atomix zip is only needed if you flash the .img to fix hotspot, but not with the zip)
Device support:
https://t.me/HMD_Nokia_8
Credits
Me for building the rom
@emufan4568 for the NB1 device and vendor tree, atomix kernel and TWRP.
Rany42 for all his help and contribution and for using his device trees, he doesn't have an XDA account.
@oaid for contribution to vendor tree and atomix kernel and countless hours of bug fixing
@CherishOS team for the amazing ROM
@THMSP for T-virus
all users in our telegram groups that helped us contribute and find bugs as well as sent us logs.
if i missed anyone in credits please let me know and ill add you to this list.
coffee:
Pay Marcel Dos Santos using PayPal.Me
Go to paypal.me/marceldossantos91 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
paypal.me
if you do decide to donate, thank you, appreciate it more than you know.
Sources:
CherishOS: https://github.com/CherishOS
Device trees: https://github.com/GPUCode, https://github.com/c79

Reserved

in case anyone is wondering, the rom is considered stable and mostly everything works, but please when reporting bugs, attach a log, thanks!

Thanks!!!

build updated
Happy flashing!

In your instructions
I'm guessing step one should be make sure device bootloader Unlocked
And t virus is installed

johndaog said:
In your instructions
I'm guessing step one should be make sure device bootloader Unlocked
And t virus is installed
Click to expand...
Click to collapse
Yes you are correct. Ive updated the post accordingly, however it is always to be assumed any rom besides stock needs T-virus to work as it requires the treble base.

Thanks for making this! Out of curiosity, is this rom using the latest A11 DDV by @emufan4568 you mentioned in another thread?

r100 said:
Thanks for making this! Out of curiosity, is this rom using the latest A11 DDV by @emufan4568 you mentioned in another thread?
Click to expand...
Click to collapse
Yes, its using all the ddv blobs and hal's, and everything has been upgraded. All A12 roms for NB1 going forward will use them

Just flashed this ROM. Buttery smooth. Thanks a lot for your time and efforts.
Couple of possible bugs
1) Do not change the display cut out from default- it blanks the whole screen without any way to change back other than by factory resetting.
2) I can't connect to Internet when I turn on expressvpn. Might be just me though.
This just proves that the Nokia 8 is still a very capable device in 2022.
Can't really get a logcat for the first one but will look into the second one to see if there's a workaround for the VPN issue.

And just in case anyone is wondering, banking apps work just fine. Safetynet passes and Selinux is indeed enforcing

Latest Gcam seems to be a hit and miss for some modes. I'll share if there's a better one out there more suited to the Nokia 8
**Edit: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1434/
This one seems good and stable for me

Xda2022 said:
Just flashed this ROM. Buttery smooth. Thanks a lot for your time and efforts.
Couple of possible bugs
1) Do not change the display cut out from default- it blanks the whole screen without any way to change back other than by factory resetting.
2) I can't connect to Internet when I turn on expressvpn. Might be just me though.
This just proves that the Nokia 8 is still a very capable device in 2022.
Can't really get a logcat for the first one but will look into the second one to see if there's a workaround for the VPN issue.
Click to expand...
Click to collapse
Hi all, found a fix for the VPN not connecting. I found that I had to be on a TCP protocol for it to work. I had issues with a UDP connection. Didn't have this issue on Pie so assume it's to do with this ROM, but nonetheless here's the solution if you've got the same problem.

Xda2022 said:
Hi all, found a fix for the VPN not connecting. I found that I had to be on a TCP protocol for it to work. I had issues with a UDP connection. Didn't have this issue on Pie so assume it's to do with this ROM, but nonetheless here's the solution if you've got the same problem.
Click to expand...
Click to collapse
I just tested UDP now with windscribe and i connected without any issues. Likely the issue is your vpn providers app not fully compatible with A12 yet.

marceldossantos91 said:
I just tested UDP now with windscribe and i connected without any issues. Likely the issue is your vpn providers app not fully compatible with A12 yet.
Click to expand...
Click to collapse
Interesting... I guess it's a fix for anyone on Express VPN.

new cherish build up, QC is finally fixed with this update. happy flashing

marceldossantos91 said:
new cherish build up, QC is finally fixed with this update. happy flashing
Click to expand...
Click to collapse
Probably me being a bit stupid, but how do you update? I don't see an update menu- does this need a microsd card to flash over twrp for every update?

Xda2022 said:
Probably me being a bit stupid, but how do you update? I don't see an update menu- does this need a microsd card to flash over twrp for every update?
Click to expand...
Click to collapse
You have to dirty flash through twrp. I am looking into how i can integrate an OTA updater but for now dirty flash procedure

build is updated, the only change is that the H/W lights for keys should now work.
Happy flashing!

Nice one Marcel!

[UNMAINTAINED][ROM][12L][STABLE][G8141] ArrowOS 12.1 Unofficial VANILLA [07-04-2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS​
ABOUT​ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end of the day, aiming to deliver smooth performance with better battery life.
Website : https://arrowos.net
Telegram Group : https://t.me/arrowos
Telegram Channel : https://t.me/arrow_os
Github : https://github.com/ArrowOS
Code Review : https://review.arrowos.net
Email : [email protected]
Blog : https://blog.arrowos.net
Paypal : https://www.paypal.me/TeamArrowOS
WHAT WORKS?​Everything should works except the one mentioned in the bug list.
BUGS​-TWRP can't decrypt data.
-You tell me.
​INSTALLATION​CLEAN FLASH
-Flash latest 47.2.A.10.107 firmware with newflasher.
-Enter fastboot mode.
-Flash latest official TWRP.
-Boot into TWRP.
-Wipe data, cache & dalvik.
-Flash the ROM.zip followed by additional flashable like gapps/magisk.
-Format data and type "yes".
-Reboot system.
IF YOU'RE ALREADY ON ANDROID 12L ROMS
-Boot into TWRP.
-Wipe data, cache & dalvik.
-Flash the ROM.zip followed by additional flashable like gapps/magisk.
-Reboot system.
UPDATES
-Boot into TWRP.
-Wipe cache & dalvik.
-Flash ROM.zip.
-Reboot system.
CHANGELOGS​07/04/2022
-Initial release.
DOWNLOADS​ROM
AFH Link
GAPPS RECOMMENDATION
MindTheGapps (12.1 ARM64).
MAGISK
HERE
SOURCES​ROM
Device Sources
Device Configurations (Maple)
Device Configurations (Yoshino)
Kernel Tree
Vendor Tree
Local Manifests
THANKS TO​Tux111, Rooted_Ansh, derf_elot, everyone in the Telegram Group.
Sorry if I missed someone.
ArrowOS for Sony Xperia XZ Premium
Device : Maple.
Build Type : Unofficial.
Build Variant : Vanilla, userdebug.
ROM Android OS Version : 12L.
ROM Kernel : 4.4.
ROM Firmware Required : 47.2.A.10.107.
Based On : AOSP.
Security Patch Level : March 2022.
Version Information
Status : Stable.
Current Stable Version : 12.1.
SELinux : Enforcing.
Created : 08/04/2022.
Last Updated : 04/04/2022.

Tested Rom, works well, but Android Auto Not working, Says connected to Car but wont Start.

hi,
i have a sony xperia xz premium (g8141) still running stock firmware and android 9, battery and phone in good shape, so why get a new one... Not sure if this is the right place to ask, but ... i'll give it a try ;-)
1) build is unofficial, but is it considered stable? e.g. crashes, freezes or the like?
2) is signature spoofing enabled? i want to avoid google apps and install microg instead.
Signature Spoofing
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
3) one needs this TWRP version?
Sony Xperia XZ Premium
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Download TWRP for maple
Download TWRP Open Recovery for maple
dl.twrp.me
thx

m00ns0rr0w said:
hi,
i have a sony xperia xz premium (g8141) still running stock firmware and android 9, battery and phone in good shape, so why get a new one... Not sure if this is the right place to ask, but ... i'll give it a try ;-)
1) build is unofficial, but is it considered stable? e.g. crashes, freezes or the like?
2) is signature spoofing enabled? i want to avoid google apps and install microg instead.
Signature Spoofing
Free implementation of Play Services. Contribute to microg/GmsCore development by creating an account on GitHub.
github.com
3) one needs this TWRP version?
Sony Xperia XZ Premium
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Download TWRP for maple
Download TWRP Open Recovery for maple
dl.twrp.me
thx
Click to expand...
Click to collapse
hi!
1. yes it is stable like any other a12L roms beacuse it uses the same device, kernel, and vendor tree. even though it's unofficial.
2. yes arrowos have signature spoofing enabled. so it supports microg.
3. i personally use the latest twrp from the official website. https://dl.twrp.me/maple/twrp-3.6.1_9-0-maple.img.html

isosceleshampa said:
Tested Rom, works well, but Android Auto Not working, Says connected to Car but wont Start.
Click to expand...
Click to collapse
what gapps are you using? can you please provide a logcat?

hey,
wow, cool, what a fast answer thx!
ok, so it's stable (based on whatawurst iirc, clicked a while through the many pages), signature spoofing is enabled which allows microg (will be enough for me, just a couple of apps via aurora store, nothing fancy, and google apps stuff finally gone). sounds great!
last question: how often will there will be updates/releases? every x weeks/months? and if A12L is installed: OTA updates or flash always necessary? Just curious.
well, i think i'll give it a try, maybe easter weekend. flashed only one rom (/e/OS on a samsung s5) before, but, hey, what could possibly go wrong?

is there a mirror link? I can not visit google drive in my region. Thanks guys.

Hmm... just read this thread:
[ROM] LineageOS 19.1 UNOFFICIAL - 1.6 [2022-09-18]
LineageOS 19.1 for Sony Xperia XZ1 RELEASE This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features. Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything...
forum.xda-developers.com
Do i need a microSD card to flash? Or via adb sideload?

m00ns0rr0w said:
hey,
wow, cool, what a fast answer thx!
ok, so it's stable (based on whatawurst iirc, clicked a while through the many pages), signature spoofing is enabled which allows microg (will be enough for me, just a couple of apps via aurora store, nothing fancy, and google apps stuff finally gone). sounds great!
last question: how often will there will be updates/releases? every x weeks/months? and if A12L is installed: OTA updates or flash always necessary? Just curious.
well, i think i'll give it a try, maybe easter weekend. flashed only one rom (/e/OS on a samsung s5) before, but, hey, what could possibly go wrong?
Click to expand...
Click to collapse
rom will be updated accordingly to arrowos source. maybe it's monthly or when a new security patch is up.

m00ns0rr0w said:
Hmm... just read this thread:
[ROM] LineageOS 19.1 UNOFFICIAL - 1.6 [2022-09-18]
LineageOS 19.1 for Sony Xperia XZ1 RELEASE This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features. Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything...
forum.xda-developers.com
Do i need a microSD card to flash? Or via adb sideload?
Click to expand...
Click to collapse
if you have flashed a12 before, you need to put the files in microsd/usb otg/temp directory or install through adb sideload because the twrp can't decrypt data for now (in a12 roms). but if you're on stock rom or any stock based rom that isn't a12, then you can use the internal storage in twrp.

Cool, thank you. Yes, still stock rom. So only copy it to the internal storage and flash. Sounds easy
edit: ok, i think i can remember why - with one of the android9-followers encryption was introduced...

ok, couldn't wait and did the install. some problems during the installation, will report maybe later, but the boot into the system then succeeded. did some settings (clock, timezone etc.); the problem now: the system boot seems to hang.
i tried to transfer some files (contacts and apk for f-droid) but the copy somehow got stuck. I then tried a reboot, but after sony logo and the android robot head i see the moving/glowing arrow symbol. And that's it. boot process doesn't proceed. Well... what could be wrong?

LOL... i think i know what went wrong: for login i wanted to have a PIN, and the system offered me to secure the system boot with that PIN as well. I think the system got stuck when the PIN has to be entered - but i never get offered to enter the PIN. Great

hanlincn said:
is there a mirror link? I can not visit google drive in my region. Thanks guys.
Click to expand...
Click to collapse
sorry for taking a long time, here you go
Arrow-v12.1-maple-UNOFFICIAL-20220407-VANILLA.zip | by Aviellyan for Xperia XZ Premium
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

m00ns0rr0w said:
LOL... i think i know what went wrong: for login i wanted to have a PIN, and the system offered me to secure the system boot with that PIN as well. I think the system got stuck when the PIN has to be entered - but i never get offered to enter the PIN. Great
Click to expand...
Click to collapse
did you enable secure boot?

hm, no, never saw smth like "secure boot". As i said, the only thing that i can remember: i was asked for setting a PIN for screen unlocking, and there it was offered to use that PIN for system boot as well. Nothing else.

avl.callistá said:
sorry for taking a long time, here you go
Arrow-v12.1-maple-UNOFFICIAL-20220407-VANILLA.zip | by Aviellyan for Xperia XZ Premium
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
thx bro, you did a great thing.

strange, still having problems with my SIM card. System boots, asks for SIM PIN, but then says: "Service not available". German provider congstar (telekom daughter). By default no APN is elected (available: lebara internet and telekom internet); i added the congstar apn manually -> no difference, doesn't work.
i tried a different phone, a samsung galaxy s5, with lineageOS 18.1 - no problems there. Any related issues known? someone else has this problem?

created a logcat.txt via 'adb logcat -d > logcat.txt', is attached here. some congstar related messages, not sure if they help.
i can see a couple of error messages, probably not related, not sure if interesting ;-)

strange, now it works, phone calls work... the small radio cell icon shows 3-4 bars, but with an ! - very strange... i don't trust it at the moment, will check it regularly the next days.