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

Search This thread

Beaster

Senior Member
Feb 20, 2009
268
59
From telegram support channel...

1652100624021.png
 

robogo1982

Senior Member
Apr 24, 2011
2,065
711
Osijek
Realme 6
Xiaomi Poco X3 NFC
oh, how nice to know that this will only be posted to TG.. Guess we can stop coming to xda then...
Flash a different ROM then, I guess?

Other than the fact that people have their own lives to live outside of ROM development, Telegram IS STILL a much more convenient communications channel than XDA. XDA forums have been on a downhill slope for years now, and the latest mobile app is just a dumpster fire icing on top of a crap cake.

It's the mobile device and development forum that is super unintuitive and unfriendly towards mobile users. Why??
 

paradøx

Senior Member
Apr 16, 2021
104
106
From TG: "As I told you Lineage 19.1 is still being heavily developed and its basically still experimental. This is proof. Last week LOS upstream added "wrappedkeys" support. This is a feature for encryption, which change the way A12 encrypt files. This caused 9May build (and all future builds) to not dirty flash. So, anybody who flashed before 9May MUST CLEAN FLASH any future Los 19 builds. Sorry guys there is no way around it. If you are on 9May build, keep it as you will be able to dirty flash in the future."
 
  • Like
Reactions: robogo1982

_exian_

Member
May 12, 2021
27
7
17.1 has been supported long after 18.1 was released. . . I don't understand why support for 18.1 ended only because that the not-so-stable 19.1 is available. My reasoning for choosing LOS was that it wouldn't die and leave me without updates like many unofficial roms do. But android 12 is such a mess right now and there's no decent recovery with encryption support for surya
 

v44r

Member
Nov 28, 2020
24
14
I flashed the test version from gardiol trying to fix the audio recording and now I cannot boot =/. Can anyone post the 0502 version that was pulled from the servers, to test if I can flash that again an boot?
 

minax007

Senior Member
Jan 1, 2021
55
20
I flashed the test version from gardiol trying to fix the audio recording and now I cannot boot =/. Can anyone post the 0502 version that was pulled from the servers, to test if I can flash that again an boot?

I do not have the 0502 version but the LineageOS with MicroG, which is based on the 0502 version can be downloaded here:


I have installed it on two devices as an upgrade to LineageOS 18.1 with MicroG and it works without any bugs.

But I am not sure if you can flash it over LineageOS without MicroG - without bricking it.

So you should only use it if you want to have a flawlessly running LineageOS 19.1 with MicroG.
 

v44r

Member
Nov 28, 2020
24
14
I do not have the 0502 version but the LineageOS with MicroG, which is based on the 0502 version can be downloaded here:


I have installed it on two devices as an upgrade to LineageOS 18.1 with MicroG and it works without any bugs.

But I am not sure if you can flash it over LineageOS without MicroG - without bricking it.

So you should only use it if you want to have a flawlessly running LineageOS 19.1 with MicroG.
Nope, flashing the microG version does not fix it. If these (test/microG) versions don't touch /data when trying to boot I should be able to recover by flashing the previous 0502 /system (I think, I don't understand very well these new dynamic partitions)... but my only chance is someone having the 0502 zip still in their hard disk and uploading it somewhere.

(Rant: this is why I hate when they simply remove things from servers. I understand they do it to keep users safe from a bad/dangerous build, but they could just HIDE it, or keep the zip somewhere else... it may be useful to someone!)

(edit) Found it on telegram. Didn't fix it. I have to format data. Oh well.
 
Last edited:
  • Like
Reactions: Pumpino

minax007

Senior Member
Jan 1, 2021
55
20
Nope, flashing the microG version does not fix it. If these (test/microG) versions don't touch /data when trying to boot I should be able to recover by flashing the previous 0502 /system (I think, I don't understand very well these new dynamic partitions)... but my only chance is someone having the 0502 zip still in their hard disk and uploading it somewhere.

(Rant: this is why I hate when they simply remove things from servers. I understand they do it to keep users safe from a bad/dangerous build, but they could just HIDE it, or keep the zip somewhere else... it may be useful to someone!)
I agree.

But you should always make a backup via TWRP before flashing a new ROM.

Then you have the possiblity to recover your system in case anything goes wrong.

Furthermore I advice you to remove the "security" (fingerprint, pattern, ...) before flashing a new ROM.

Otherwise, when the data partition is locked, you will not be able to recover it.

That was the experience I have made.

Since then I am removing the "security" settings and never had a problem again when something went wrong.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Updated to the latest build without issue through adb sideload. Just FYI for those interested.
    1
    Hello @gardiol
    I have been using your LOS 17 and 18 on my phone, and since I'm now going to use 19.1 I thought it was about time to join this forum and say thanks for your work ;)
    1
    Tried NikGapps, everything works as it should: isGooglePlayServicesAvailable returns 0 and my app functions as it should. So MindTheGapps seems crippled.
    This seems the same issue https://github.com/RikkaW/YASNAC/issues/22
    1
    @v44r I asked Alessandro (MindTheGapps' author) and he released a new build, in case you want to try it
    1
    @v44r I asked Alessandro (MindTheGapps' author) and he released a new build, in case you want to try it
    Thanks. I tried that version (because the addon.d script in NikGApps failed when I tried to update to latest LOS) and now my app works without problems. Calls to GoogleApiAvailability.isGooglePlayServicesAvailable() now return 0 and subsequent calls to Wearable.* work as expected.
  • 67
    Lineage_OS_Logo.png


    LineageOS 19.1 Official (18.1 discontinued as of 2nd May 2022)

    We are official!


    17.1 will never be official (and it's upstream dead)
    18.1 is official, discontinued builds.
    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:
    • WiFi
    • VoLTE
    • VoWIFI
    • FM Radio
    • RIL (telephone, SIM, 2G/3G/4G/LTE/+/blah...)
    • Tethering
    • Bluetooth + AAC
    • Tethering + bluetooth working
    • Safety net passed
    • SELinux Enforcing in Trust
    • DT2W
    • WiFi Display fully working
    • Infrared (IR)
    • NFC (Surya only)

    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.4.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 24.1, 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-05-02
    19
    Passing SafetyNet and Google Play Certification

    SafetyNet and Play Store certification

    (guide updated 01 feb 2022, for Magisk 24.1 and Zygisk)

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