[ROM][10/12] LineageOS OFFICIAL [SURYA]KARNA]

Search This thread

Master One

Senior Member
Jan 31, 2011
842
310
Europe
I am. Didn't observe any of this. Which build are you on? I'm on 20220905 (tried 20221017 briefly but had to revert back due to lack of SIM connection)...
I tried with
  • LOS 19.1 for microG 20221014
  • LOS 19.1 20221017
but the same problem with both of them (fresh installations after factory reset with nothing else configured or installed).

I can easily reproduce that problem, because it comes up every time:
  1. Boot a fresh new installation.
  2. Go through the install wizard and configure WiFi.
  3. At the end WiFi and both SIMs are active.
  4. SIM1 configured for data and default for SMS.
  5. Activate Airplane mode, wait a little, disabling Airplane mode.
  6. The "Select a SIM for data" pop-up comes up and the configuration for default SIM for SMS reverted to "Ask every time".
This is cumbersome to deal with, because as said, I'm using Airplane mode several times a day. Not sure what to do now.
 

Yoda007

Senior Member
Apr 8, 2012
103
12
This happens to me as well in the latest build (previous builds were OK). Sometimes i get the PIN message, and the SIMS were changed message without turning on the Airplane mode. Hope this is fixed soon since i allways put the phone in airplane mode every night before i go to sleep.
 
  • Like
Reactions: Master One

krzysiekx

Senior Member
Aug 19, 2013
70
9
Dear all,

tl;dr
Should I sideload adb or zip flash TWRP in order to install lineageos on Surya with unlocked bootloader? Do I need one zip only, no vendor or stuff?

Could you give me a little hand as to how I should go about installing LOS and TWRP for the first time?

I just managed to unlock bootloader on my Surya device.
So after installing twrp.img via 'fastboot flash recovery' and 'fastboot boot recovery', is it enough just to install the lineage-19.1-20221024-nightly-surya-signed.zip zip?

I am asking, because on the official LOS website it says something like this (here's a part of the official guide):

'Installing LineageOS from recovery
Download the LineageOS installation package that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.'

So after I manage to put TWRP (version 3.5 from xda, I believe) on my phone, will it be enough just to wipe and install from zip instead of sideloading mentioned In the guide before?

Asking, because last time I did it Flashing a zip was enough.

Also, i have miui 13 android 12 stable Eea ROM and unlocked bootloader.
 
Wifes phone has been running Lineage for some time now without incident. Tonight with battery <10% screen turned off randomly. No powering off screen, just suddenly died.
When attempting to reboot ph gets stuck on the 'Poco' screen.

Entering recovery mode (twrp 3.5.x) just hangs too. It remains stuck on the twrp splash screen.

I've tried newer versions of twrp (twrp-3.7.0_12-0-surya-29.09-fbev2.img) and it too gets stuck on the twrp splash screen.

Anyone run into this before? Its weird. Possibly hardware failure or am I getting ahead of myself? Don't really want to have to reset etc.

I tried clearing dalvik cache via fastboot erase cache, but it still won't boot lineage.

Edit: Also tried lineage recovery.
I assume fastboot boot twrp-xxx.img is valid and I don't have to flash it directly?
 
Last edited:
Wifes phone has been running Lineage for some time now without incident. Tonight with battery <10% screen turned off randomly. No powering off screen, just suddenly died.
When attempting to reboot ph gets stuck on the 'Poco' screen.

Entering recovery mode (twrp 3.5.x) just hangs too. It remains stuck on the twrp splash screen.

I've tried newer versions of twrp (twrp-3.7.0_12-0-surya-29.09-fbev2.img) and it too gets stuck on the twrp splash screen.

Anyone run into this before? Its weird. Possibly hardware failure or am I getting ahead of myself? Don't really want to have to reset etc.

I tried clearing dalvik cache via fastboot erase cache, but it still won't boot lineage.

Edit: Also tried lineage recovery.
I assume fastboot boot twrp-xxx.img is valid and I don't have to flash it directly?
Left it charging overnight and it booted up no trouble. So weird.
 

gardiol

Senior Member
Feb 23, 2011
897
1,148
San Carlo Canavese
photos.gardiol.org
Freezes are gone from official builds. On Telegram i am also sharing LOS 20 test builds, which are damn pretty stable so far. Anyway, freezes where caused by LMKD which _requires_ zram to be enabled to properly work fine. So i have enabled zarm back in stock kernel and all is fine.

Other kernels did work because they included an "old" LMK implementation which takes priority on LMKD and works without zram. But since LMK is pdeprecated and LMKD is the future anyway, zram is back and we are all the better.
 

Zarausto

Member
Mar 15, 2013
21
2
Hello everyone.
The Brazilian government has an application called Gov.br ( https://play.google.com/store/apps/details?id=br.gov.meugovbr ) which needs use of facial recognition. When starting the application it is not possible to perform the procedure. I believe the app is not getting access to the front camera. Or maybe something else.

I have Magisk and SAFETYNET pass, everything is working fine, I can also use the 3 bank apps. I've tried to blacklist the app as I've done with bank apps, but no success. =(

Can anyone help?
 

tminus3

Senior Member
Hi everyone,

Hopefully someone can help me. It's been a while since I flashed custom roms, but got my x3 nfc stolen during vacation and now bought a used one back that has fresh install of Lineage 19.1 (19-20221031-NIGHTLY-surya) on it.
Thing is, it doesn't offer me the typical Google restore data/settings/apps option when setting it up.
I tried a factory reset, but that rebooted into recovery -> Mount -> Decrypt Data and asked me for a password i'm not aware of (TRWP 3.6.2_11-0-surya).
The recovery has so many options and settings I'd rather not mess about with it.

Any tips on getting a google backup installed on this phone? Or (re-)flashing the rom if need be? The stock MiUI rom would be acceptable for me as well if thats easier to accomplish.

Tia,
Marc
 
Last edited:

gardiol

Senior Member
Feb 23, 2011
897
1,148
San Carlo Canavese
photos.gardiol.org
Hi everyone,

Hopefully someone can help me. It's been a while since I flashed custom roms, but got my x3 nfc stolen during vacation and now bought a used one back that has fresh install of Lineage 19.1 (19-20221031-NIGHTLY-surya) on it.
Thing is, it doesn't offer me the typical Google restore data/settings/apps option when setting it up.
I tried a factory reset, but that rebooted into recovery -> Mount -> Decrypt Data and asked me for a password i'm not aware of (TRWP 3.6.2_11-0-surya).
The recovery has so many options and settings I'd rather not mess about with it.

Any tips on getting a google backup installed on this phone? Or (re-)flashing the rom if need be? The stock MiUI rom would be acceptable for me as well if thats easier to accomplish.

Tia,
Marc

Use the mi flash tool and flash back MIUI.
You are probably using an older TWRP unable to decrypt A12 (LOS19.1)
 

sturges

Senior Member
Apr 14, 2021
122
32
Suddenly when I start my phone I have a message "Can't load Android system. Your data may be corrupt, etc." and it asks if I want to try again or factory reset. I didn't do anything strange, I don't even have magisk installed... just updated a couple of apps via f-droid and turned off my phone... I'm still using release 20221017. Do I have to wipe everything? :eek:

Edit: just booted into recovery and flashed latest build, still same error...
 
Last edited:

sturges

Senior Member
Apr 14, 2021
122
32
Since this is my main phone I had to format and reinstall. Still, I wish I knew what happened and how to avoid it from happening again...

Edit: with only a few apps installed from f-droid, suddenly it was completely frozen (black screen) and I had to force reboot. It seems to work now, but I really don't know what to think... o.s., app or hardware issue?
 
Last edited:

juup

Member
Feb 17, 2014
6
3
Since Update LOS 19.1 from 22-10-31 I need to activate and disable airplane mode after booting the phone to activate the SIM card (enter PIN).
Issue is still in last Update from 22-11-07.
I came from 22-10-03 where PIN was needed to enter directly after boot (how it should be).
 

gardiol

Senior Member
Feb 23, 2011
897
1,148
San Carlo Canavese
photos.gardiol.org
Since this is my main phone I had to format and reinstall. Still, I wish I knew what happened and how to avoid it from happening again...

Edit: with only a few apps installed from f-droid, suddenly it was completely frozen (black screen) and I had to force reboot. It seems to work now, but I really don't know what to think... o.s., app or hardware issue?

Feels like hardware defect. Internat flash getting broken or defective. I would get it on the way for rpelacement if under warranty or buy a new phone ASAP
 
  • Sad
Reactions: sturges

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Anyone tested VOWIFI /WIFI Calling on airplane mode? it seems it is not working.

    By the way LOS20 has already been merged so it is expected to be built next monday
    1
    I dirty flashed LOS 20, MindtheGapps 13 and DFE V6 over the latest LOS 19 build. It seems to have worked fine. I had one forced close with the Play Store but nothing since. My girls use it for games and Messenger, so I'll keep an eye on how it performs over the next few hours and report back if there are issues.

    One issue I had with unofficial PixelExperience builds of Android 13 was the other person hearing themselves in Messenger. I know the issue was at our end, as it never happened when my girls used my Pixel instead.
    1
    I didn't notice it's LOS 20 now, so I dirty flashed it in adb over my perfectly stable LOS 19 and I noticed I had to force close Play Store (as reported above by Pumpino)... then it got stuck and I had to reboot, but the booting animation never seemed to stop...

    So I re-flashed the last LOS 19 in recovery mode but it didn't boot and said system was now corrupt... I tried re-flashing LOS 20 but again, like before, the booting animation took longer than usual and then rebooted, looped, rebooted, looped... I guess I lost everything and I have to reinstall now :cry:
    Hi,
    probably you cannot return to LOS19, but it may work with LOS 20:
    In TWRP recovery you erase the SYSTEM (!) partition, then install LOS20, Google-Apps, and Magisk (or not, as you wish). Then reboot.
    That may bring your phone back to work.

    As long as you do not format DATA, your data should be OK.
    1
    gardiol writes this on telegram:
    "OFFICIAL 20 requires firmware 12.5.8.0. TEST 20 requires firmware 13.0.4.0. Please flash accordingly!"
    1
    Hello

    I have installed this ROM on my Surya model and would like to ask a few questions.

    First thing is if I can turn on developer mode and turn off USB debugging after installing this ROM ?
    yes you can
  • 66
    Lineage_OS_Logo.png


    LineageOS 19.1 Official and currently built by LineageOS official infrastructure.


    17.1 has never been official (and it's upstream dead since 31st December 2021)
    18.1 is official, discontinued builds since 2nd May 2022
    19.1 is official and built weekly.

    /*
    * 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.
    */

    What's working:
    • Everything

    Known issues:
    • Honestly at this time, nothing?

    Camera Notes
    ANX camera is not recomended and will most probably NOT work.
    To get a fully working camera try one of the gcams here.
    Do not forget to copy&load the associated xml file!

    Official LOS uses oss camera service, so xml written for other custom roms might not work.
    The gcams at the above link have modified xmls for LOS.


    Download:

    There is also a MIcroG build if you don't like Google Apps!
    If you care for official microg builds, check here they will be ready when they will be ready, those builds are not done by me nor supported by me, do not ask me about it.

    There is also, for help and support, the:
    Instructions:
    • Make sure to flash at the very minimum firmware 12.5.7.0 (anything newer will work) from XiaomiFirmwareUpdater firmware page
    • (For 17.1 <<only>> : flash VENDOR + FIRMWARE from Android 10, do not use Android 11)
    • Download this build and Magisk (optionally) and gapps (optionally).
    • Put the zip on your MicroSD (suggested) or connect via USB to PC.
    • Boot to recovery (latest TWRP only is suggested! OrangeFox has issues).
    • Wipe Dalvik, Cache and format data. This IS NOT OPTIONAL!
    • Reboot recovery after wipe and format.
    • Flash this ROM zip...
    • ... flash gapps zip ...
    • ... If you want Magisk, flash zip ...
    • Reboot and enjoy!
    If you have any issues flashing, like persistent GApps or booting issues, try to cleanup the phone with the following procedure:
    • Download a full MIUI rom recovery package from XiaomiFirmwareUpdater MIUI page
    • ... (make sure you download the full rom package for RECOVERY, it is about 2.4Gb!) ...
    • From recovery, flash the zip file. This will cleanup all the partitions.
    • Now flash again this ROM.
    This problem is related to the fact that TWRP and OrangeFox both don't support dynamic partitions properly yet.

    Tested with Magisk 25.2, newer version should work, but you MUST follow the SafetyNet fix guide in the next post if you want Play Store certification.

    Suggested GAPPS for LineageOS: Mind The Gaps (here, make sure to download the ones for your android version 10, 11 or 12).



    XDA DevDB Information
    LineageOS 17.1 & 18.1 & 19.1, ROM for the Xiaomi Poco X3 NFC

    Contributors

    Build by @gardiol

    Device tree sources: device tree
    Kernel sources: kernel
    Vendor sources: vendor

    Additional notes

    SafetyNet does not pass by default, you need to follow the steps on post n.3 below. This is due to Google issues and LOS rules.

    ROM OS Version: Android 10 & 11 & 11
    ROM Kernel: Linux 4.x

    Version Information
    Status:
    Official and Unofficial.

    Created 2020-12-13
    Last Updated 2022-08-24
    19
    Changelog

    From May 2022:
    LineageOS 19.1 is official for Surya!

    TO BE CLEAR: there are OFFICIAL releases weekly, those (and the according changelog) is NOT listed here, go to official LOS download page! This list if only for test builds at this point.

    20 December 2021 (17.1)
    Last 17.1 build ever for Surya
    December security patches

    19 September 2021 (17.1)
    September security patches.

    06 September 2021 (18.1)
    New debloated kernel
    Fixed screen recorder rate limiter
    Fixed DriveDroid (and more usb gadget stuff)
    Added proximy check to prevent screen wakeup option
    August patches
    Fixed minor denials (battery improvement)

    31 July 2021 (18.1)
    Fixed lots of denials
    Greatly improved battery life
    more minor fixes.

    20 July 2021 (both 17.1 and 18.1)
    July patches
    For 18.1: mi_thermald added back
    For 18.1: dynamic 30-120Hz fixed

    13 July 2021 (18.1)
    All new trees!
    FORMAT data is MANDATORY

    19 June 2021 (17.1)
    Upstream sync
    June patches

    17 June 2021 (18.1)
    fixed haptic issues
    Fixed Netflix error 5.10
    Fixed idle drain
    Fixed NFC denial
    Upstream sync

    07 June 2021 (18.1)
    Fix aptX
    Fix boot from MIUI to LOS not working

    07 June 2021 (18.1)
    Fix netflix
    Fic video recording length
    Fix GBoard rounded corners

    05 June 2021 (18.1)
    First release of 18.1 build!

    11 May 2021 (17.1)
    LOS upstream sync with May patches

    18 April 2021
    LOS upstream sync with April patches
    Dpmd crash resolved
    ️LOS call recorder enabled
    ️Removed all permissive domains

    09 April 2021
    Upstream sources sync

    28/29 March 2021
    Fixed video recording bug
    Fixed audio crackling (finally!)
    Removed all "parts", added doze and refresh rate specific settings
    Getting trees ready for official
    (note: UnofficlalBuild and Experimental builds are from 28 March, MicroG from 29th)

    13 March 2021
    Two builds are available...
    Unofficial, the same old build, but with March security patches.
    Experimental, featuring a full vendor partition, but still SELinux permissive, but a ton of improvements including fixed video recording length, 4K video recording and playback and more minor issues.
    Pick your choice!

    27 February 2021
    Really fixed yellow tint once for all
    Enabled VoIP transition
    Updated proprietary blobs
    Haptic improvements
    Various minor optimizations
    LOS upstream sync

    19 February 2021
    Improved Wifi
    Improved audio
    LOS upstream sync

    06 February 2021
    Improved brightness levels
    Finished reworking tree
    February LOS upstream sync
    Latest security patches

    24 Jannuray 2021
    Fixed "Fast Charging" string, except for original charger!!! (Fast charging IS working, just does not says it's fast in lockscreen).
    Added 30Hz and 50Hz display frequency in display options
    Cleaned up audio routes


    19 Jannuary 2021
    Reverted a prop which was interferring with whatsapp videos.

    18 Jannuary 2021
    Fixed fingerprints
    Rewritten init_surya.cpp
    Removed more useless stuff
    Activated correctly second SIM card
    Added a few translations
    Improved brighness
    Improved Wifi networks
    Fixed tethering+bluetooth

    05 Jannuary 2021
    WiFi Display fixed, finally!
    Resolved bug with speakerphone and reboot

    05 Jannuary 2021
    WiFi Display not fixed
    Product partition enlarged
    Device Tree reworked for proper contribution recognition
    AOD disabled. Once fixed will be available again.

    01 Jannuary 2021
    DT2W Fixed.

    29 December 2020
    New device tree is up.
    Brightness works again
    DT2W not working
    AOD not working
    FM Radio fixed (again)

    29 December 2020
    Final fix for low volume recording.
    WiFI Display still not fixed (please send logs!!!)
    Device tree cleaned up a lot
    add Higher Aspect Ratio
    statusbar : avoid display parameters on Notch
    SELinux is showing Enforcing in Trust

    28 December 2020
    Added audio fixes for low volume.
    Added full WiFi Display support (to be confirmed)

    26 December 2020
    New parittion size.
    Bluetooth now reporting working properly.

    24 December 2020
    Tentative SELinux enforcing.

    22 December 2020
    Added FM radio support, FM radio working.
    SELinux still permissive

    20 December 2020
    Reworked vendor mixing camera blobs from A10 branch and telephony from A11 branch.
    Camera is reported working.
    SIM card is reported working.
    VoLTE and WoWiFi reported working.
    FM Radio NOT working.

    19 December 2020
    New beta build for camera fix.
    Let me know if it works!

    18 December 2020
    SIM card works
    missing camera
    selinux permissive, will try to fix in later build
    19
    Passing SafetyNet and Google Play Certification

    SafetyNet and Play Store certification

    (guide updated 24 aug 2022, for Magisk 25.2)

    LineageOS, by charter, does not alter any safety ptotection set by Google. In our case, having an unlocked bootloader, safetynet will always fail by Google decision. Now, passing safety net is required for banking apps and even some games. Also, it is required for "play store certification", which will prevent you from even searching for some apps (like Netflix).
    Blame Google for all this.

    --ALL STEPS ARE MANDATORY, NONE CAN BE SKIPPED UNLESS EXPLICITY OPTIONAL--

    Install Magisk

    Download latest stable magisk apk from Magisk website (https://github.com/topjohnwu/Magisk). Rename it as .zip and flash it from recovery. Some recoveries, like TWRP, will flash the apk directly, others will require the rename.
    Boot LOS and install the apk file.

    Hide Magisk apps and Enable Zygisk & blocklist

    Open Magisk App, go to settings and hide the magisk app. Give it a name you will remember.
    After magisk app has been hidden, go back to settings and enable Zygisk (beta).
    Now apply the blocklist and select all the apps you like NOT to detect Magisk. This must include Google Play Services and Google Play Store.

    Install SafetyNet fix module

    kDrag0n developed a fix that can be flashed via Magisk. You must download the module (https://github.com/kdrag0n/safetynet-fix/releases), select at least version 2.2.1, and install it from inside Magisk app.

    Setup Fingerprint

    Download latest Props module for Magisk (https://forum.xda-developers.com/t/...t-prop-edits-and-more-v6-1-2.3789228/page-274) and install it within Magisk. Reboot your phone.
    Now, after reboot, open a terminal (use "adb shell" from pc, or install termux from play store) and type:
    su (grant root access!)
    props (a text based menu will popup)
    Now select "1" (edit fingerprint), type "f" (pick fingerprint) select "22" (poco) then select any one poco x3 model. Which one really doesn't matter, but make sure to choose the right Android version.
    Confirm and reboot phone.

    Clear caches for Google stuff

    Now, open settings - apps and clear data&cache for Google Play Store and Google Play Services.
    One last reboot!

    Don't want root?

    If you dont want root... Just disable it from within Magisk!

    OPTIONAL Additional stuff

    Magisk from 24.1 removed the built-in modules repository. If you like it back, you can install Fox's Magisk Module Manager app (https://github.com/Fox2Code/FoxMagiskModuleManager).


    LineageOS on SafetyNet (https://www.lineageos.org/Safetynet)
    Kdrag0n on SafetyNet (https://github.com/kdrag0n/safetynet-fix)
    SafetyNetFix Magisk Module (https://github.com/kdrag0n/safetynet-fix/releases)
    Magisk download (https://github.com/topjohnwu/Magisk)
    Props Module for Magisk (https://forum.xda-developers.com/t/...t-prop-edits-and-more-v6-1-2.3789228/page-274)
    fox's Magisk Module Manager (https://github.com/Fox2Code/FoxMagiskModuleManager)
    18
    I have some news. I am working on Lineage-18.1 and so far i am having some good progress.
    I managed to boot it, it's still unstable and a lot work is required, but it's steady.

    It is OSS based, so this will be official no doubt this time.
    18
    Official build is again underway and will be ready in a few days.
    Everything has been approved this time we are just waiting for hudson & wiki merge to be approved.

    I think there is good hope that the first official build will be next week.