• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][11] LineageOS OFFICIAL [SURYA]KARNA]

Search This thread

retroman445

Member
Sep 18, 2021
5
2
Go to settings and enable developer options. Google how to do that if you dont know how.

Then open developers settings and scroll to debug and enabled that. This will stoo the jdwp spam. Thsts related to LOS not having applied one AOSP patch some time ago. It is going to be fixed upstream but cannot predict when.
Ah yes, had developer options enabled all the time, debugging options selected also. Since I wanted to collet as much info about the bug as nessecary. Still the error remains and the application fails to work. I really think this is not an LOS thing but a Bromite thing. Is there any way I can replace the Webview application for another one? The Webview Manager Magisk module does not seem to work. I have no trouble running ADB as root and messing in the shell of my phone. Or installing stuff via ADB. Webview manager seems to install the Webview APK somewhere where LOS does not pick it up.
 
  • Like
Reactions: RulleZz
Uploading net 17.1 build. See OP.
Still uploading, give it some time.
Hi @gardiol thanks a ton for that. It is always good to have in the pocket an alternative of a previous stable Android version for device, specially 10=>11 with some substantial changes for apps.

By the way, can you please write to us your (flashing/wiping) advice, main steps in the 3 scenarios bellow? I have my thoughts although I'm not very experienced with Xiaomi, but it is always good to listen to developer themselves just in case. This may also help other people if written/linked in OP.

1 - currently in stock MIUI Android 11 => going to LOS 17.1 Android 10

2 - currently in LOS 18.1 Android 11 => going to LOS 17.1 Android 10

3 - currently LOS 17.1 Android 10 => going to LOS 18.1 Android 11

Thanks!
 

gardiol

Senior Member
Feb 23, 2011
818
1,060
San Carlo Canavese
photos.gardiol.org
Hi @gardiol thanks a ton for that. It is always good to have in the pocket an alternative of a previous stable Android version for device, specially 10=>11 with some substantial changes for apps.

By the way, can you please write to us your (flashing/wiping) advice, main steps in the 3 scenarios bellow? I have my thoughts although I'm not very experienced with Xiaomi, but it is always good to listen to developer themselves just in case. This may also help other people if written/linked in OP.

1 - currently in stock MIUI Android 11 => going to LOS 17.1 Android 10

2 - currently in LOS 18.1 Android 11 => going to LOS 17.1 Android 10

3 - currently LOS 17.1 Android 10 => going to LOS 18.1 Android 11

Thanks!

The only suggested step is miui/whatever -> los 18.1.

The only suggested approach is to follow flashing guide.
 
  • Like
Reactions: f3r.and0

retroman445

Member
Sep 18, 2021
5
2
Ah yes, had developer options enabled all the time, debugging options selected also. Since I wanted to collet as much info about the bug as nessecary. Still the error remains and the application fails to work. I really think this is not an LOS thing but a Bromite thing. Is there any way I can replace the Webview application for another one? The Webview Manager Magisk module does not seem to work. I have no trouble running ADB as root and messing in the shell of my phone. Or installing stuff via ADB. Webview manager seems to install the Webview APK somewhere where LOS does not pick it up.
For everyone who has problems with applications not able to connect to services with weird logging of not allowing http sockets from https urls and other Bromite related misery. Very very short howto. Please be careful! Running the rm command can damage your install if you are not careful and make typo's.

Code:
Developer Options, Allow debugging as root

adb root
(got suggestion to reboot phone from adb, might not happen to you)
reboot

adb root
adb shell
su -
(check phone for root access)
mount -o remount,rw /
rm -rfv /system/app/bromite-webview
reboot phone

Install Magisk
Install Magisk Webview Manager
https://www.androidacy.com/downloads/?view=%2540Magisk-Modules%2540WebviewManager
Choose webview you want, wait.
reboot

Check Developer Options, Webview Implementation.
Should say someting other than Bromite.

Problem solved! (At least, on my phone)

Ungoogled Chromium Webview works as a charm here. You might need to repeat the procedure to remove Bromite when you flash a new rom, since the rom includes the Bromite Webview out of the box on LOS 18 MircoG.
 
Last edited:
  • Like
Reactions: temporarium

boody shaban

Senior Member
Oct 11, 2014
101
2
Do you have any screenshot to prove this or is it just your personal opinion?

Edit: took me 2 minutes to find out that Lineage or ArrowOS results are very close to stock. You should simply Google it
For your record, im not here to please you, im just saying a fact, i dont really care if u believe it or not
 

Attachments

  • Screenshot_20210920-140139.png
    Screenshot_20210920-140139.png
    896.5 KB · Views: 78

jjcdennis

Senior Member
Jun 20, 2015
494
99
Toronto
So I was just about to wipe this phone and rebuild with Lineage and I see the following screen. I click on the Install button and a box with the chinese characters and OK pops up. I have tried many times and nothing seems to happen. Should I install the drivers manually via the .inf, or does the box mean that I have installed them? Confusing. View attachment 5411449
I'm still not sure about this screen in miflash. I have opened miflash and connected the phone via fastboot and it appears as a device. Does this tell me that I'm good to go and can flash Miui - then reboot to TWRP and follow page 1... Second question, should I pull my sim, or my SD card prior to running miflash. Third - any issues restoring apps with google backups? Sorry for the rookie questions. This method is 100% new to me.
 

camperbh

Senior Member
Feb 22, 2021
99
31
I'm still not sure about this screen in miflash. I have opened miflash and connected the phone via fastboot and it appears as a device. Does this tell me that I'm good to go and can flash Miui - then reboot to TWRP and follow page 1... Second question, should I pull my sim, or my SD card prior to running miflash. Third - any issues restoring apps with google backups? Sorry for the rookie questions. This method is 100% new to me.
1) Don't worry about that screen. If you see Android Bootloader Interface in device manager or your phone's serial number appears in the command line after typing fastboot devices, you should be good to go. Beware that TWRP gets replaced with the stock recovery so you'll have to flash it again.
2) I don't have an SD card, but I've never taken out the sim before flashes and it has always been fine.
3) Google backups work perfectly, though I've always used flame gapps basic and I can't speak for other gapps packages or microg.
 
  • Like
Reactions: jjcdennis

jjcdennis

Senior Member
Jun 20, 2015
494
99
Toronto
1) Don't worry about that screen. If you see Android Bootloader Interface in device manager or your phone's serial number appears in the command line after typing fastboot devices, you should be good to go. Beware that TWRP gets replaced with the stock recovery so you'll have to flash it again.
2) I don't have an SD card, but I've never taken out the sim before flashes and it has always been fine.
3) Google backups work perfectly, though I've always used flame gapps basic and I can't speak for other gapps packages or microg.
So can I reflash TWRP with the stock recovery, or via adb/fastboot?
 

jjcdennis

Senior Member
Jun 20, 2015
494
99
Toronto
Guys I'm about to flash Miui in miflash and just noticed this message at the bottom of the miflash screen. I'm guessing that I choose clean all, but could someone comment on which selection to make.
Thank you.

1632229044367.png
 

camperbh

Senior Member
Feb 22, 2021
99
31
Guys I'm about to flash Miui in miflash and just noticed this message at the bottom of the miflash screen. I'm guessing that I choose clean all, but could someone comment on which selection to make.
Thank you.

View attachment 5415273
I've always chosen clean all, never tried save user data before. FYI if you accidentally choose clean all and lock the bootloader gets locked but you can unlock it right back without waiting.

After the flash is successful, you may get the not catch checkpoint error if you choose to not lock your bootloader. Don't worry about it, just let the phone boot.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Insane battery life on this.

    5h13m screen time, 53% remaining. And that's in an area with not so good coverage. 2h Reddit, 1h Youtube, 1h Twitch.
    2
    Never touch a running System :)
    That is an undeniable truth.

    Except for everyone of us hanging around here in XDA :LOL:
    1
    I've just flashed official lineage-18.1-20211101-nightly.
    WiFi doesn't work. The app freezes the whole UI and has to be stopped / closed in order to be able to use the phone again.
    Same thing happened with the 20211025-nightly.
    I never experienced anything like that with gardiol's unofficial builds though ....
    Any thoughts?

    Flash latest A11 Firmware.



    @xadityax

    Same here on Build 25/10
    1
    Sorted!

    1. Wipe -> Advanced -> Dalvik, Cache, Data
    2. Install MiUI recovery file
    ...... No reboot
    3. Install LineageOS
    4. Format ("yes")
    5. Reboot to System.

    Thanks very much mates!
    1
    I flashed LineageOS 18.1 the other day, and I noticed I have only Widevine Level 3.
    With LineageOS 17 I had Level 1, if I remember correct.

    Did I made something wrong / should I reflash it?

    I flashed the latest EU MIUI before flashing LOS 18.1. And I use Magisk root and the props module.

    I have L1.

    I flashed Miui Global --> LOS

    Maybe this help.
  • 60
    Lineage_OS_Logo.png



    LineageOS 17.1 official trees / unofficial builds for surya and karna.

    LineageOS 18.1 Official.

    We are official!


    17.1 will never be official.
    18.1 is official.

    WARNING - NOTE
    Due to two still unmerged tickets on LineageOS Gerrit, you MUST enable USB debugging in developers options to avoid high battery drain if you flash official build!​

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


    Download:

    There is also a MIcroG build if you don't like Google Apps!
    Note: on the same download links you can find also MicroG builds for both 17.1 and 18.1! If you care for official microg builds, check here they will be ready when they will be ready.

    There is also, for help and support, the:
    Instructions:
    • NOTE: it is MANDATORY to flash latest stable firmware for your region!
    • For 17.1: flash VENDOR + FIRMWARE from Android 10 (Q)
    • For 18.1: flash FIRMWARE from Android 11 (R) - no vendor required.
    • 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...
    • ... (suggested) reboot system and do the initial setup ...
    • ... If you want Magisk and/or gapps: boot back to recovery,
    • Flash GAPPS and/or Magisk.
    • 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
    • ... (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 23.0, newer version should work.
    Suggested GAPPS for LineageOS 17.1: OpenGapps nano or pico.
    Suggested GAPPS for LineageOS 18.1: Mind The Gaps (
    here)


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

    Contributors

    Build by @gardiol
    Thanks to @Maharajah99, @janhammer504 , and quite so many others.

    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
    ROM Kernel: Linux 4.x

    Version Information
    Status:
    Official and Unofficial.

    Created 2020-12-13
    Last Updated 2021-09-98
    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.
    16
    Changelog

    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
    16
    Passing SafetyNet and Google Play Certification

    Most of POCO X3 AOSP derived ROMs incorrectly set the device fingerprint. The reasons are various and can be summarized as:
    1. It's being dome like this by the Great Devs
    2. It's too dangerous to change
    3. In this way we can fake being a Pixel phone
    But this is fundamentally incorrect, as each device has it's own fingerprint signature that shall be preserved, and MUST be preserved in order to achieve official status. Moreover, the recent changes in Play Services about SafetyNet (you can read more here: hardware certification) make impossible to pass SafetyNet with an unlocket bootloader. The workaroud requires a rewrite of the keystore and faking to be an older device which does not support hardware certification. This must be implemented from upstream (and i doubt LOS will ever implement it anyway).

    So, what is the problem?

    First, the hardware certification must be faked.
    Second, the correct device fingerprint must be set.

    So, what is the solution?

    First, use a magisk module.
    Second, use another magisk module to fix it. Maybe this second problem might be solved in the future, but the first one cannot be fixed unless LOS upstream add the fix themselves.

    The procedure

    1. Download Magisk (official magisk page), download latest stable.
    2. Boot to recovery and install magisk. (future dirt flashes will preserve magisk)
    3. Reboot system and open Magisk Manager app.
    4. Install the first module (this: from official github page)
    5. Activate Magisk Hide and "hide Magisk Manager app". This is very important!
    6. Install the module "MagiskHide Props Config", you can find it in the modules repository inside Magisk Manager!
    7. Open a terminal... you have three options:
      1. adb shell from PC with phone connected over USB (first, enable USB debugging in developers options)
      2. Enable terminal app from developers options
      3. Install a terminal app from Play Store or FDroid.
    8. Now, in terminal: type "su" (and give root permissions!)
    9. Type "props"
    10. Now you will see a menu, select "1" (Edit device fingerprint)
    11. From the new menu, select "f" (Pick a certified fingerprint)
    12. Select the brand POCO, not XIAOMI!
    13. Now select the POCO X3 NFC (either global or europe, does not matter)
    14. You should see the fingerprint selected on screen, now accept it with "y".
    15. Accept to reboot immediately!
    16. The phone will reboot, after that SafetyNet will pass.
    Known issues and solutions

    99% of issues are related to incorrectly use of Magisk. Magisk HIDE must be enabled and Magisk MAnager must be "hidden" with the menu selection inside Magisk MAnager itself.