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

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

Search This thread

Davy-Jones

Member
Aug 2, 2021
13
0
Aaand - here I go again. Sorry. :-(

This evening there was an Update via OTA and I tried. I downloaded and startet the file, the phone went into TWRP, flashing was good, no problems. The phone startet again and then - bootloop. The LOS logo was shown for about 2-4 min and after that, the phone boot back into TWRP.

I could fix it by wiping dalvik, system and cache und flashed Version 08.08. and Nickgapps and Magisk again.

First try by only flashing Version 08.08. did not work -> still bootloop.

Did I do smth wrong, do I have to prepare sth?

Thank you, Guys.
 

Neurotical

Senior Member
Feb 7, 2011
132
158
Aaand - here I go again. Sorry. :-(

This evening there was an Update via OTA and I tried. I downloaded and startet the file, the phone went into TWRP, flashing was good, no problems. The phone startet again and then - bootloop. The LOS logo was shown for about 2-4 min and after that, the phone boot back into TWRP.

I could fix it by wiping dalvik, system and cache und flashed Version 08.08. and Nickgapps and Magisk again.

First try by only flashing Version 08.08. did not work -> still bootloop.

Did I do smth wrong, do I have to prepare sth?

Thank you, Guys.
From what I understand, using the recovery file that comes with this build is the best way to get best compatibility. You may have to start fresh with full wipe, install recovery that comes with the weekly, then install ROM. This will only have to be done once because each weekly updates the Recovery (if you choose it to).

There are posts in here or the other thread that get TWRP working, but there are several steps taken to make that work, making using LOS with TWRP cumbersome; especially with encryption.
 
  • Like
Reactions: Davy-Jones

Klaus20

Senior Member
Nov 20, 2013
369
61
Can someone tell me something about the recovery image?
I installed the following version (lineage-18.1-20210809-UNOFFICIAL-starlte.zip) and everything is going well so far.
What is the recovery image for (lineage-18.1-20210809-UNOFFICIAL-starlte-recovery.img), should you install it beforehand?
How can I control which Baseband Firware is installed or should I -> Modem_G960FXXUFFUE1_10.05.2021-flashable.zip install ??
Regards Klaus
 

Neurotical

Senior Member
Feb 7, 2011
132
158
Can someone tell me something about the recovery image?
I installed the following version (lineage-18.1-20210809-UNOFFICIAL-starlte.zip) and everything is going well so far.
What is the recovery image for (lineage-18.1-20210809-UNOFFICIAL-starlte-recovery.img), should you install it beforehand?
How can I control which Baseband Firware is installed or should I -> Modem_G960FXXUFFUE1_10.05.2021-flashable.zip install ??
Regards Klaus
For best compatibility and OTA support, it's best to install the Lineage OS Recovery at least once the first time. After that the OTA should take care of everything else.

As for the baseband updating, this thread has it all: https://forum.xda-developers.com/t/...0-17-07-2021-android-10-pie-stockrom.3858990/
 
  • Like
Reactions: Klaus20

Klaus20

Senior Member
Nov 20, 2013
369
61
Can I also install Lineage OS Recovery over an installed LineageOS 18.1? I mean TWRP -> OS Recorey and LineageOS 18.1 ??
I have the same question with Baseband Update?

Regards Klaus
 

ipilcher

Senior Member
Jul 10, 2010
70
10
Dallas, TX
So just to double-check ... nothing has changed re (absence of) VoLTE support, right?

(I can't help thinking that the carriers are using VoLTE to force us back to the days of carrier-specific phones.)
 

Monvigliero

New member
Aug 20, 2021
4
2
[SOLVED] Thank you very much for the amazing effort. The OS is fantastic. Unfortunately I am facing with a bug, and I don't know how to fix it. Is it just some settings problem, my phone, or something else?!
On stand by during the night connected to wi-fi the battery drains very fastly if the cell/phone is turned on (nothing else, no mobile data, no nfc, no bluetooth cca. 30% in 6-7 hours). Without cell/phone, only with wi-fi connection it is perfect (only 3% in the same period). I am happy for any idea.
 
Last edited:

Davy-Jones

Member
Aug 2, 2021
13
0
Hey Guys,

just one quick question: Do I have to install the official Google App to use the voice recognition? Or is there an unofficial "lighter" way?

Thank you very much.
 

quangthai_itdlu

New member
May 5, 2015
4
0
Hi @Synt4x.93
I'm trying to compile lineage starlte using your source code, include device, common, kernel and vendor.
When I run brunch starlte to begining compile, I got an error: build/make/core/Makefile:2347: error: hardware/samsung/mkbootimg.mk: No such file or directory.
Where I can clone samsung hardware source code for lineage 18.1?
I'm looking forward to hearing from you!
Thanks for reading.
 

ElPakoTech

Member
Apr 18, 2020
21
30
Hi @Synt4x.93
I'm trying to compile lineage starlte using your source code, include device, common, kernel and vendor.
When I run brunch starlte to begining compile, I got an error: build/make/core/Makefile:2347: error: hardware/samsung/mkbootimg.mk: No such file or directory.
Where I can clone samsung hardware source code for lineage 18.1?
I'm looking forward to hearing from you!
Thanks for reading.
Hi,
You need to apply this fix to the code source: https://github.com/pakaoraki/androi...mmit/7397c44c12fdc3fe669bf0ead10c908b16d88ab0

Fix is not present yet in the original Synt4x.93 repo.
 
  • Like
Reactions: quangthai_itdlu

quangthai_itdlu

New member
May 5, 2015
4
0
Hi,
You need to apply this fix to the code source: https://github.com/pakaoraki/androi...mmit/7397c44c12fdc3fe669bf0ead10c908b16d88ab0

Fix is not present yet in the original Synt4x.93 repo.
Hi, @ElPakoTech
I'm trying to get all buildprop properties from default.prop, /system/build.prop and vendor/build.prop, but it not of all.
For example: [ro.product.brand] and [ro.product.odm.brand], i cannot find them in any file I just find [ro.product.system.brand] in /system/build.prop and [ro.product.vendor.brand] in /vendor/build.prop
Where I can find them?
How to write ro.product.brand, ro.product.odm.brand in to /system/build.prop when I compile the lineage starlte
 

ElPakoTech

Member
Apr 18, 2020
21
30
Hi, @ElPakoTech
I'm trying to get all buildprop properties from default.prop, /system/build.prop and vendor/build.prop, but it not of all.
For example: [ro.product.brand] and [ro.product.odm.brand], i cannot find them in any file I just find [ro.product.system.brand] in /system/build.prop and [ro.product.vendor.brand] in /vendor/build.prop
Where I can find them?
How to write ro.product.brand, ro.product.odm.brand in to /system/build.prop when I compile the lineage starlte
For example, to me (as I am not an expert android dev) you can modify this file for starlte: /device/samsung/starlte/lineage_starlte.mk

Code:
...
# Device identifier. This must come after all inclusions
PRODUCT_DEVICE := starlte
PRODUCT_NAME := lineage_starlte
PRODUCT_BRAND := samsung
PRODUCT_MODEL := SM-G960F
PRODUCT_MANUFACTURER := samsung
...

If you just want to build for starlte/star2lte (S9/S9+), you don't need to modify any files but I am not sure about what you to do.
 
  • Like
Reactions: quangthai_itdlu

quangthai_itdlu

New member
May 5, 2015
4
0
For example, to me (as I am not an expert android dev) you can modify this file for starlte: /device/samsung/starlte/lineage_starlte.mk

Code:
...
# Device identifier. This must come after all inclusions
PRODUCT_DEVICE := starlte
PRODUCT_NAME := lineage_starlte
PRODUCT_BRAND := samsung
PRODUCT_MODEL := SM-G960F
PRODUCT_MANUFACTURER := samsung
...

If you just want to build for starlte/star2lte (S9/S9+), you don't need to modify any files but I am not sure about what you to do.
Hi @ElPakoTech
Thank you so much :)
 

cybermiguel

Senior Member
Feb 12, 2011
52
16
Angol
Samsung Galaxy S9
Is there any way to transfer (or keep) the samsung "hidden" system apps to this rom?

The thing is that I need to use the "Samsung Network Settings" app, which cannot be downloaded from Google PlayStore, nor Galaxy Store, and comes preinstalled with the phone.

I need to use specifically that app because the high-frequency antennas in my machine are working poorly and 4G LTE only works well on the 700 Mhz band, and I use that software to lock the radio on my phone on those frequencies (900 Mhz for 3G and 700 Mhz for 4G LTE).
 
  • Like
Reactions: jehemera

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Hi,

    I just realized yesterday that there is new updated sources from synt4x.93 since a long time, I'm very happy to see that dev are still maintaining/working on it.


    Making my own build, I wanted to try a new updated version from the new sources but unfortunatelly it break my data encryption: I was not able to recovered it, so I lost all my recent data (and forgot to do a recent backup...).

    So I just want to acknowledge other self builder like me, be careful if you play/build your own from this sources, backup everything and prepare to reinstall.

    EDIT: the new test build I made do not start at all (always want to erase data at startup even with full factory reset so be carrefull ).
  • 42
    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.