[ROM][S9+/S9][UNOFFICIAL][LineageOS 18.1][21-03-2021]

Search This thread
Mar 19, 2021
21
5
These are your problems on your single install, they all work fine for many. Anyway this ROM has been superceded. The great work here on this ROM by synt4x93 has continued with LOS with kernel updates, Gapps spoofing + apps too. Try that one, but install properly from a clean wipe first. NFC, diode light, vibration, fast charging, wifi/gps etc etc all work on this ROM for many users until the last version in March 21, you really think the whole community was keeping your dramas on this ROM a secret all this time ??? 😂
 
Last edited:

SunnyBoy117

Member
Feb 5, 2019
6
0
Это ваши проблемы с одной установкой, у многих они работают нормально. В любом случае это ПЗУ было заменено. Большая работа synt4x93 над этим ПЗУ была продолжена с LOS с обновлениями ядра, спуфингом Gapps и приложениями. Попробуйте это, но сначала установите правильно с чистого вайпа. NFC, диодная подсветка, вибрация, быстрая зарядка, Wi-Fi/GPS и т. д. и т. д. — все это работает на этом ПЗУ для многих пользователей до последней версии от 21 марта, вы действительно думаете, что все сообщество все это время держало в секрете ваши драмы на этом ПЗУ? ?? 😂
I have been experimenting with different firmware on this smartphone for 2 months. lineage 18.1 I installed 3 times. with different cores, wipes and over pure smart and over stock firmware. the result is the same. I was flashing exactly 9650 with a 9th bootloader. Unfortunately, I don't have another phone like this. Therefore, I can’t say only on my device such problems or on others too. But when I install a stock firmware for myself, everything works perfectly: both SIM cards and sensors and everything else.
 

Kartoniq

Member
Mar 29, 2021
7
0
LG V30
I flashed it and now it says 'Encryption unsuccessfull' and prompts to perform a factory reset. I don't have any data on the phone so it in itself wouldn't be a problem, however after tapping on 'erase all data' it's just stuck on a loading screen. I can't enter neither recovery mode nor download mode to flash the stock firmware. Is it permanently bricked?

Phone: Samsung Galaxy S9

Edit: Solved, managed to boot into download mode somehow. I probably forgot to wipe data before flashing
 
Last edited:

d4foasta

Member
Aug 26, 2012
15
1
Hi

first of all - thank you very much for this rom. It really is amazing, its a pity LOS doesn't support it officially anymore.
I wanted to ask where I can find the changelog. I updated from the november-update today and showing the changelog with the built-in-updater doest work...

Kind regards
D4foasta
 

XDAMntLion23

New member
Mar 11, 2022
1
0
Great!!
Does this support OpenCL?
I want to test Deep learning performance with tensorflow lite OpenCL version
 

Koffietijd

Member
Jun 21, 2018
32
2
If I flash this Lineageos 18.1 on my starlte would it be possible to enable signature spoofing to use MicroG?
So how would I do that?
 

peacepipe

Member
Jul 20, 2016
32
3
Only to get sure, will this ROM still updated or is it already end of life? The last OTA update ist from 21-03-2021

Furthermore, I am currently on the latest official S9 linage OS 17.1 (QQ3A.200805.001), do I have to go back to the stock rom as well or could I update from this without data loss? It's really annoying to shovel all the data from phone to pc and back.
 
Last edited:

Neurotical

Senior Member
Feb 7, 2011
244
400

astrapotro

Member
Nov 22, 2017
7
2
Hi, this build is AWASOME, thanks for doing it <3

BUT i'm suffering usb tethering not working in debian/ubuntu. In windows is working fine.
This is /var/log/syslog when usb tethering is activated on the phone :
Code:
May  5 14:32:51 ideapad kernel: [  155.998386] usb 1-3: new high-speed USB device number 7 using xhci_hcd
May  5 14:32:51 ideapad kernel: [  156.149202] usb 1-3: New USB device found, idVendor=04e8, idProduct=6863, bcdDevice= 4.00
May  5 14:32:51 ideapad kernel: [  156.149208] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May  5 14:32:51 ideapad kernel: [  156.149212] usb 1-3: Product: SAMSUNG_Android
May  5 14:32:51 ideapad kernel: [  156.149215] usb 1-3: Manufacturer: SAMSUNG
May  5 14:32:51 ideapad kernel: [  156.149218] usb 1-3: SerialNumber: 2c1400813e037ece
May  5 14:32:51 ideapad kernel: [  156.153815] rndis_host 1-3:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-3, RNDIS device, 6e:21:48:4e:3b:29
May  5 14:32:51 ideapad NetworkManager[775]: <info>  [1651753971.6849] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/9)
May  5 14:32:51 ideapad mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
May  5 14:32:51 ideapad mtp-probe: bus: 1, device: 7 was not an MTP device
May  5 14:32:52 ideapad gvfsd[5850]: Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
May  5 14:32:52 ideapad gvfsd[5850]: Android device detected, assigning default bug flags
May  5 14:32:52 ideapad systemd-udevd[5884]: Using default interface naming scheme 'v250'.
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.3873] device (usb0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.3918] device (usb0): carrier: link connected
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.3955] device (usb0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4007] policy: auto-activating connection 'Conexión cableada 1' (787e76cf-5e07-316a-82ca-e64466949929)
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4029] device (usb0): Activation: starting connection 'Conexión cableada 1' (787e76cf-5e07-316a-82ca-e64466949929)
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4032] device (usb0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4041] manager: NetworkManager state is now CONNECTING
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4047] device (usb0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4059] device (usb0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
May  5 14:32:52 ideapad NetworkManager[775]: <info>  [1651753972.4087] dhcp4 (usb0): activation: beginning transaction (timeout in 45 seconds)
May  5 14:32:52 ideapad avahi-daemon[732]: Joining mDNS multicast group on interface usb0.IPv6 with address fe80::39a3:a7b4:7e0b:4b25.
May  5 14:32:52 ideapad mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3"
May  5 14:32:52 ideapad avahi-daemon[732]: New relevant interface usb0.IPv6 for mDNS.
May  5 14:32:52 ideapad avahi-daemon[732]: Registering new address record for fe80::39a3:a7b4:7e0b:4b25 on usb0.*.
May  5 14:32:52 ideapad mtp-probe: bus: 1, device: 7 was not an MTP device
May  5 14:32:52 ideapad systemd[1]: Run anacron jobs was skipped because of a failed condition check (ConditionACPower=true).
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2838] policy: ipv6-pd: no device to obtain a subnet to share on usb0 from
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2841] device (usb0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2892] device (usb0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2899] device (usb0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.2909] manager: NetworkManager state is now CONNECTED_LOCAL
May  5 14:32:54 ideapad NetworkManager[775]: <info>  [1651753974.3119] device (usb0): Activation: successful, device activated.
May  5 14:32:54 ideapad ModemManager[788]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3': not supported by any plugin

Someone knows how to fix this?
Thanks in advance
 

Top Liked Posts

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


    REQUIREMENTS:
    • Stock Samsung Oneui 2 - 2.5 (Android 10) Firmware. (Bootloader + Vendor)

    INSTRUCTIONS:
    • Lineage Recovery or TWRP
    • Format /system + /data + /cache
    • Flash
    • Reboot

    WORKING:
    • Wi-Fi
    • Bluetooth
    • Mobile Network
    • GPS
    • NFC
    • Audio
    • Camera
    • Fingerprint Sensor
    • HDMI
    • Ethernet
    • MTP/ADB
    • Call Recording
    • Encryption
    • SELinux Enforcing
    • Android Auto
    • Glove Mode
    • OTA Updates

    BROKEN:
    • Iris Scanner
    • VoLTE

    DOWNLOADS:

    XDA:DevDB Information
    LineageOS 18.1, ROM for the Samsung Galaxy S9

    Version Information
    Status:
    Stable
    ROM OS Version: Android 11
    ROM Kernel: Linux 4.9.118
    ROM Firmware Required: Oneui 2 - 2.5

    Contributors
    synt4x.93

    Source Code: https://github.com/synt4x93/

    Created: 16-12-2020
    Last Updated: 21-03-2021
    6
    would you mind specifying exactly what you did to build this? I am using the lineage for microg docker based build and it currently succesfully builds 17.1. I would like to build 18.1 with OTA and sign it myself and provide the OTA like you do.
    There are fragments of info across this thread, it would be great if you or anyone else can put them together.
    Thanks!
    Hi,

    Sure I can share what I did.

    1. Prepare directories and get Lineage sources (https://wiki.lineageos.org/devices/starlte/build)

    # Create directories
    Bash:
    mkdir -p ~/bin
    mkdir -p ~/android/build
    mkdir -p ~/android/build/src
    mkdir -p ~/android/build/ccache
    mkdir -p ~/android/build/keys
    mkdir -p ~/android/build/logs
    mkdir -p ~/android/build/zips
    mkdir -p ~/android/build/manifests

    # Get repo tools
    Bash:
    curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
    chmod a+x ~/bin/repo

    # Create a "~/.profile" file and paste this into:
    Bash:
    “if [ -d "$HOME/bin" ] ; then
        PATH="$HOME/bin:$PATH"
    fi”

    # Prepare git
    Bash:
    cd ~/android/build/src
    git config --global user.email "[email protected]"
    git config --global user.name "Your Name"

    # Init repo
    Bash:
    source ~/.profile
    repo init -u https://github.com/LineageOS/android.git -b lineage-18.1

    # Time to sync (it can take a very long time, so be patient).
    Bash:
    repo sync

    2. At this point, I forked all Synt4x.93 related repositories on my Github. But, you don’t really need to do that if you just want to build.

    For OTA, the only repo you will need to fork is android_device_samsung_starlte.

    3.
    Create an other repository named OTA.

    4. From your forked android_device_samsung_starlte repository, modify the file lineage_starlte.mk

    Change the last line with your GitHub username:
    Code:
    PRODUCT_PROPERTY_OVERRIDES += \
    lineage.updater.uri=https://raw.githubusercontent.com/<Your_username>/OTA/lineage-18.1/starlte.json

    5. Then you need to add the roomservice.xml file to add the device and kernel sources.

    You can use the resources from Synt4x.93, mine or from Neurotical (He’s maintaining a more recent version of the kernel, you should have a look: https://forum.xda-developers.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/ )

    Get one of the manifests:
    -Synt4x.93: https://github.com/synt4x93/local_manifests
    -pakaoraki: https://github.com/pakaoraki/local_manifests
    -Neurotical: https://github.com/Geoknyda/local_manifests

    Then modify the file roomservice.xml: change "project name" with your GitHub username to match your repository:
    Code:
    ...
    <project name="synt4x93/android_device_samsung_starlte" path="device/samsung/starlte" remote="github" revision="lineage-18.1" />
    ...

    Copy your version of roomservice.xml into ~/android/build/manifests directory.

    # Update source again
    Bash:
    repo sync

    6. Generate your own keys (https://wiki.lineageos.org/signing_builds.html)

    From the root of your Android tree, run these commands, altering the subject line to reflect your information:
    Bash:
    subject='/C=US/ST=California/L=Mountain View/O=Android/OU=Android/CN=Android/[email protected]'
    
    cd ~/android/build/src
    for x in releasekey platform shared media networkstack testkey; do \
        ./development/tools/make_key ~/android/build/keys/$x "$subject"; \
    done
    make a copy of the “keys” directory and keep it safe.

    7. Install docker and get docker-lineage-cicd image:

    You can use lineaos4microg : https://hub.docker.com/r/lineageos4microg/docker-lineage-cicd/Dockerfile
    Bash:
    docker pull lineageos4microg/docker-lineage-cicd

    Or

    I also re-write my own docker image to add some options. You can try: https://hub.docker.com/r/pakaoraki/docker-lineage-cicd
    Bash:
    docker pull pakaoraki/docker-lineage-cicd

    8. Then you are ready to build:

    Execute this command (change pakaoraki/docker-lineage-cicd with lineaos4microg/docker-lineage-cicd if needed)

    Bash:
    docker run \
    -e "BRANCH_NAME=lineage-18.1" \
    -e "DEVICE_LIST=starlte" \
    -e "INCLUDE_PROPRIETARY=false" \
    -e "SIGN_BUILDS=true" \
    -v "~/android/build/src:/srv/src" \
    -v "~/android/build/zips:/srv/zips" \
    -v "~/android/build/logs:/srv/logs" \
    -v "~/android/build/ccache:/srv/ccache" \
    -v "~/android/build/keys:/srv/keys" \
    -v "~/android/build/manifests:/srv/local_manifests" \
    pakaoraki/docker-lineage-cicd

    9. When build is done, create a new release on your OTA repo: choose a tag and upload recovery.img and zips file.

    you will need to create a starlte.json that match to your build and release information:
    Code:
    {
       "response": [
          {
             "datetime": 1627204505,
             "filename": "lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
             "id": "39b85208c5c30edfafd983673a703d60",
             "romtype": "UNOFFICIAL",
             "size": 608774193,
             "url": "https://github.com/<username>/OTA/releases/download/<tag>/lineage-18.1-20210725-UNOFFICIAL-starlte.zip",
             "version": "18.1"
          }
       ]
    }

    <tag>: the tag you use when creating the release on Github.
    <username>: your username.

    Then, upload starlte.json to your OTA repository.

    It's possible that I forget something but you get the global idea.
    4

    @ElPakoTech

    Thanks for your work!
    I will test the build and give you feedback.

    Nice , if we have a maintained LOS with current security patches.
    Have you a paypal adress, that i can buy you a beer?

    Regards
    dreas
    I will do my own build anyway if there is no official support so I'm happy to share it. No need to tips but thanks :)
    4
    5th July security update ready on this build if you are compiling your own.
    How to check when its available besides going thru the make process and checking
    ~/android/build/core/version_defaults.mk
    once complete for the security update date ?

    Also checking the
    //source.android.com/security/bulletin
    for the monthly date and
    https://lineageos.org/blog/
    changelog
    isnt helpful. How to know what patch is ready to build before I go thru the whole process ???

    Need to keep the device patched to the latest at all times to be able to use as a daily for work :p
    To check for security update version of Lineage 18.1 before building your own: https://github.com/LineageOS/android_build/blob/lineage-18.1/core/version_defaults.mk#L243

    There is a build with July security update and an upstreamed kernel here: https://forum.xda-developers.com/t/rom-s9-s9-unofficial-lineageos-18-1-weekly.4302901/

    I am upstreaming the kernel daily and building these new builds daily as well.
    4
    Don't mean to be a jerk, simply stating my choices. The person who made this unoffical rom has been online several days this past week and has given us zero communication on future updates.

    I'll be heading to arrow os soon.
    In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.