[OFFICIAL] LineageOS 18.1 for Xiaomi Mi 6 (sagit)

Search This thread

Roddy_Perry

Member
Feb 14, 2012
21
9
Hi. I installed LOS 19.1 15/09/2022 built and Lineage Recovery. I have two sims. But it only detects one sim card. When I remove and replace the sim cards the phone detects both of them. But when I restart the phone it only detects one sim card again. Anyone having the same problem as me? Is there a solution to this?
2 SIMs functionality has not been working for me since 17.1. It has been mentioned in previous threads but it seems pretty difficult to fix and not many people use this functionality. I have a GiffGaff UK SIM that is not detected at all. I use an old phone for it as I do not need it as often. It's a shame that this cannot be fixed. But at least we have a 5 year old phone with modern Android :)
 

hanzn

Senior Member
Apr 12, 2020
51
18
2 SIMs functionality has not been working for me since 17.1. It has been mentioned in previous threads but it seems pretty difficult to fix and not many people use this functionality. I have a GiffGaff UK SIM that is not detected at all. I use an old phone for it as I do not need it as often. It's a shame that this cannot be fixed. But at least we have a 5 year old phone with modern Android :)
Weird! I'm using 2 sims since a long time. Maybe even since v16. So far this is working very well. Both sims are beign recognized. I can chose which one should use data/calls/sms.
 

Roddy_Perry

Member
Feb 14, 2012
21
9
Weird! I'm using 2 sims since a long time. Maybe even since v16. So far this is working very well. Both sims are beign recognized. I can chose which one should use data/calls/sms.
It seems that not all of us are having this problem. When I posted a similar message on a previous thread other people reported not having problems. I guess that's why it is so difficult to debug and fix.
 
  • Like
Reactions: hanzn

GPSMapper

Member
Apr 11, 2009
49
9
Xiaomi 12
Hi All,
I am trying to get custom (unofficial) Android Auto apps working in LKOS 18.1/19.1 and fail.
AA has a protection which bans all applications which are installed not from Play Store.

It is however possible to tweak the system and make it thinking that App is installed ffrom Play Store by manually editing application string in /data/system/packages.xml file

On the stock MIUI and PixelExperience Plus unofficial rom - this method works, I can read and edit the file (with root), but on LOS it seems this xml file is somehow encrypted and it does not look as a normal xml file but rather as a binary with some text.

Any ideas?

1664567858430.png
 

Attachments

  • 1664567836371.png
    1664567836371.png
    26.7 KB · Views: 44
Last edited:

krpa1

Member
Jun 15, 2019
12
2
Hi, can someone please help me. I was using linage os but wanted to convert to a stock MIUI. Linage os recovery was installed and I wiped all data including cache and system partitions. After that, phone can't be discovered by the PC anymore (neither from ADB, nor from fastboot). Linage os recovery is still installed and I can enter it (and therefore enable ADB - but after enabling it PC still doesn't show the device using command ADB devices). I can also enter fastboot, but fastboot command also doesn't recognize that the phone is connected to PC. I tried on PC and laptop, using Windows and Ubuntu without any luck. First I thought it may be a driver on the PC, but now it looks like some partition on the phone that is responsible for communication with PC is deleted.
Any help is appreciated.
 

vip77

Senior Member
Jan 6, 2009
73
20
Hi, can someone please help me. I was using linage os but wanted to convert to a stock MIUI. Linage os recovery was installed and I wiped all data including cache and system partitions. After that, phone can't be discovered by the PC anymore (neither from ADB, nor from fastboot). Linage os recovery is still installed and I can enter it (and therefore enable ADB - but after enabling it PC still doesn't show the device using command ADB devices). I can also enter fastboot, but fastboot command also doesn't recognize that the phone is connected to PC. I tried on PC and laptop, using Windows and Ubuntu without any luck. First I thought it may be a driver on the PC, but now it looks like some partition on the phone that is responsible for communication with PC is deleted.
Any help is appreciated.
Try other cable? Try USB 2.0 port? Also try carefully clean phone port.
 
Last edited:

vip77

Senior Member
Jan 6, 2009
73
20
I don't understand how I can perform OTA update while keeping root on 19.1. Previously, I installed an OTA update and patched the boot.img with Magisk before rebooting. Now the reboot happens automatically and I have to flash the patched boot.img through the bootloader every time. Any advice?
 

Roddy_Perry

Member
Feb 14, 2012
21
9
Actually, I have V11.0.6.0.PCAMIXM stock OTA installed on my Mi6(Sagit).

Have any issues been reported on nightly 19.1 LineageOS?

Thanks in advance.
I just installed the latest nightly and I have to say it's working great. Battery life is not better but not worse I would say. After doing updates from LineageOS 17 I decided to do a fresh install (Format everything except Internal Storage) with the latest TWRP 3.7. It does feel like buying a new phone. Thanks to NeoArian and the LineageOS team.
 
  • Like
Reactions: pmbrs

pmbrs

Senior Member
Aug 18, 2014
96
13
Lisbon
I just installed the latest nightly and I have to say it's working great. Battery life is not better but not worse I would say. After doing updates from LineageOS 17 I decided to do a fresh install (Format everything except Internal Storage) with the latest TWRP 3.7. It does feel like buying a new phone. Thanks to NeoArian and the LineageOS team.
Thank you @Roddy_Perry for your feedback!
 

Dester.exe

New member
Jul 7, 2018
3
1
Tried everything except USB 2.0... I dont have a device with 2.0.
I had the same issue. It is a Windows 10 USB 3.0 issue.
Create a .bat file with the following content:


@)echo off reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f pause
 
  • Like
Reactions: krpa1

krpa1

Member
Jun 15, 2019
12
2
I had the same issue. It is a Windows 10 USB 3.0 issue.
Create a .bat file with the following content:


@)echo off reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f pause
Mate, you just saved my phone. Thanks a lot.
 
  • Like
Reactions: Dester.exe

Top Liked Posts

  • There are no posts matching your filters.
  • 25
    2okPze5.png


    Code:
    [COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
    [COLOR="Navy"]/*
    * 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.
    */[/COLOR]

    Introduction
    LineageOS, an open-source Android distribution, is available for several devices,
    with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
    Join us and breathe new life in your device, be it old or new.
    If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

    Features
    Individuality

    Customization is paramount to productivity.
    That’s why LineageOS promises to push for user personalization and preference.
    Everyone is unique and your device should be too.
    Security
    Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
    Trust will help you understand the security of your device and warn you about possible threats.
    We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
    And to make your device more secure, lock everything behind an enhanced lock screen.
    Longevity
    LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.

    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.

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

    More detailed instructions at:
    Install LineageOS on sagit

    Downloads
    Download LineageOS 18.1 for Xiaomi Mi 6.
    ###
    The first builds is still running and will be up within a few hours. https://buildkite.com/lineageos/android/builds/32355
    ###
    If you prefer TWRP over Lineage recovery, you can get it here.
    Recommended Google apps package: MindTheGapps (choose arm64).
    More information about Google apps can be found here.

    Sourcecode:
    xiaomi msm8998 kernel
    sagit specific device tree
    xiaomi msm8998-common device tree

    Changelog:
    Changes for sagit

    Bug reports:
    How to submit a bug report
    LineageOS GitLab

    Donate to support development:
    Donate via PayPal to NeoArian
    Donate via PayPal to mikeioannina
    Donate via PayPal to LineageOS
    9
    As some of you already noticed, we started working on LineageOS 19.1 for Mi 6 and Mix 2. You can find builds here: https://sourceforge.net/projects/ephedraceae/files/sagit/lineage-19.1/ Note that google apps are included.
    They latest build should be working pretty good, but swiping up on lockscreen (when not using fingerprint sensor) needs to be done slowly (the system thinks that it's an accidental swipe up, i didn't figure that out yet).

    You can find automated release messages about future builds here: https://t.me/releases_by_arian
    4
    I'm posting a total success with my upgrade to 18.1:

    - Previous version was last 17.1 image
    - I had problems flashing lineage recovery so I flashed latest TWRP (it ended up being an issue with the cable, though)

    Once booted into TWRP:
    - Flashed latest firmware just in case, but I'm pretty sure I was up to date
    - Dirty flashed LineageOS 18.1 20210603
    - I flashed MindTheGapps
    - I flashed @NeoArian's Miui camera from late in the 17.1 thread.

    Everything worked flawlessly, Miui camera included! 😎 I only had to reverse the back button again in the preferences.

    I had a weird charging issue since January (it would only charge if I plugged the cable in and then rebooted), which is now gone too.

    11/10, this is awesome!
    4
    Hey guys, regarding the issue I reported on last summer:
    On boot the date and time are reset to the day and time the ROM was build (and it stays this way as long as you don't connect to the mobile network)
    I SOLVED it! By flashing the latest stock ROM. I tried the latest Xiaomi.EU weekly and stable ROMs as well as the latest official global ROM, so I'm not sure which one fixed it or if they all do. (I was flashing them for other purposes and only thought of checking if this problem had been solved somewhere along the process.)

    I did notice that after flashing the latest global ROM my baseband version changed into a higher number. It seems the Chinese ROM—which my phone originally shipped with and on which the Xiaomi.EU ROMs are based—comes with a lower baseband version (AT20-0305_1024_3754711 according to a screenshot I took). I'm now on baseband version AT20-0307_2204_3754711. I'm not sure if it was the baseband version though, I seem to remember the date-time-issue already being solved after only flashing the Xiaomi.EU ROM.

    Anyway, the problem was clearly with the firmware, and reflashing all partitions solved it. I found this out a few months ago but didn't get around to write this up. Hope it can still help someone!

    @NeoArian @anderson997 @jordiet

    Edit: forgot to say, afterwards I flashed LineageOS again and the problem didn't return
    3
    Hi all.

    I upgraded yesterday from 17.1 (end of april or may version?) to last 18.1.

    First I replaced the old OrangeFox Recovery I had with TWRP 3.5.2_9-0 (dirty flash to recovery, boot to recovery).

    Then I dirty flashed from TWRP, in a single operation:
    . lineageos 18.1 (lineage-18.1-20210722-nightly-sagit-signed.zip)
    . magisk (v23)
    . NikGapps Core (NikGapps-core-arm64-11-20210718-signed.zip)
    . MiuiCamera (from this post: https://forum.xda-developers.com/t/official-lineageos-17-1-for-sagit.4077651/page-25#post-85011613 )

    And rebooted.
    Everything seems to work fine (android auto and bluetooth to be tested).

    Thanks a lot for this.