• 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

testerS4

Senior Member
Mar 7, 2019
144
31
security update:

I am also interested in when the new security update will be installed in the ROM. I have now tried ArrowOS which is based on AOSP. The May security update is already included there. Would want to stay here at Rob's ROM already.
(sorry for engl ... I use translators)
Device: G960F (starlte)
 
  • Like
Reactions: dreas74

Tzira

Senior Member
Sep 27, 2009
80
5
Campina
With latest build I get " app won't run without Google Play services, which are not supported by your device" when I try to run an app that uses Google Maps. Though I have Google Apps installed with MindTheGapps-11.0. Anyone else experienced this?
 

testerS4

Senior Member
Mar 7, 2019
144
31
With latest build I get " app won't run without Google Play services, which are not supported by your device" when I try to run an app that uses Google Maps. Though I have Google Apps installed with MindTheGapps-11.0. Anyone else experienced this?
I used the NikGapps-core-arm64-11. No errors since the last update.
 

Queeq

Member
Jun 21, 2016
19
8
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.
 

murtzsch

Member
May 10, 2014
36
20
Didn't know about ArrowOS, it's probably worth a try.
IMHO it's worth a try because everything is documented to compile it myself.

IOW, WRT lineageos 18.1 for s9/s9+, how about documenting how to build it from source.
The old official doc is here : https://wiki.lineageos.org/devices/star2lte/build

I guess it's matter of changing some repo urls and using https://github.com/synt4x93/, but are there more changes made to this unofficial build ?
After that, you'll be able to compile it yourself and start sharing it.

The "build it yourself" instructions are missing from a lot of unofficial builds, that's a bit sad if not worrying.
 

litong18

New member
Aug 3, 2019
2
0
Hi, all. I'm trying to install Lineage on my S9+. When I finished flashing the rom and gapp and reboot back to the system, my phone keeps on bringing me to the "Downloading..." screen. I already wiped cash, system, and data prior to the flashing process, so I don't know why this keeps on happening.
 

sarius02

Senior Member
Feb 19, 2017
75
30
Karlsruhe, Germany
Hi, all. I'm trying to install Lineage on my S9+. When I finished flashing the rom and gapp and reboot back to the system, my phone keeps on bringing me to the "Downloading..." screen. I already wiped cash, system, and data prior to the flashing process, so I don't know why this keeps on happening.
You are sure, that you're flashing the right version of the ROM?
Could you probably make some pictures of the recovery log while flashing with a different device or somehow obtain the TWRP log file from the device and post it here?
 

testerS4

Senior Member
Mar 7, 2019
144
31
You are sure, that you're flashing the right version of the ROM?
Could you probably make some pictures of the recovery log while flashing with a different device or somehow obtain the TWRP log file from the device and post it here?
With the right ROM, TWRP 3.3.1.1 and NikGapps everything should work
 

gusnz

Member
May 12, 2013
31
8
IOW, WRT lineageos 18.1 for s9/s9+, how about documenting how to build it from source.
The old official doc is here : https://wiki.lineageos.org/devices/star2lte/build

The official doc isn't bad but you need an extra step:
1) Before running repo sync, add roomservice.xml from Synt4x93's Github to .repo/local_manifests/ in the Lineage root folder.
2) Then run repo sync and the rest of the instructions. You can skip the "Extract proprietary blobs" step.

Of course make sure you are checking out 18.1 not 17.1 during repo init. My first build attempt crashed out after running low on RAM but hopefully you folks have luck!
 
Last edited:

asmarena6

New member
May 26, 2021
1
0
hello the top speaker is not working only work bottom speaker. How can I activate the dualspeaker?
 

preetfzr

Member
Aug 13, 2011
17
1
Berlin
Hi all,

Is there any way to pass security net on this ROM?
I am having trouble while using Google pay. Even tried to hide with Magisk, but it didn't work.

Thanks in advance.
Simer
 

litong18

New member
Aug 3, 2019
2
0
You are sure, that you're flashing the right version of the ROM?
Could you probably make some pictures of the recovery log while flashing with a different device or somehow obtain the TWRP log file from the device and post it here?
Sure thing. Here's my latest twrp log:


And these are the rom and gapp I use.

1622120557372.png
 
Last edited:

gusnz

Member
May 12, 2013
31
8
Addendum to previous post: I've managed to build it for star2lte. If your computer has <32Gb RAM you can replace brunch in the official build script with:

breakfast star2lte
mka bacon -j 4


(where '4' is the number of threads you want to use).
 

sarius02

Senior Member
Feb 19, 2017
75
30
Karlsruhe, Germany
Hi all,

Is there any way to pass security net on this ROM?
I am having trouble while using Google pay. Even tried to hide with Magisk, but it didn't work.

Thanks in advance.
Simer
Yes, there luckily is!
I'm using the ROM since it came out and passing SafetyNet is a necessity for me a I need to use my tan app for online banking. Had been causing me a lot of pain at some times tough.

As our device defaults to hardware based key attestation, simply enabling Magisk hide won't do the job. You need a module for this. Currently the only working way I'm aware of is safetynet-fix (GitHub, XDA-thread see here).
AFAIK it is not available in the Magisk app for now, so you will have to download it from GitHub. In the README there are additional instructions. Like stated there, you may also need "MagiskHide Props Config" (available within Magisk Manager) to spoof CTS profile, but I think there was no need for me to do this.

Hope you can get it to work with this hint!
Good luck and greetings!
 

preetfzr

Member
Aug 13, 2011
17
1
Berlin
Yes, there luckily is!
I'm using the ROM since it came out and passing SafetyNet is a necessity for me a I need to use my tan app for online banking. Had been causing me a lot of pain at some times tough.

As our device defaults to hardware based key attestation, simply enabling Magisk hide won't do the job. You need a module for this. Currently the only working way I'm aware of is safetynet-fix (GitHub, XDA-thread see here).
AFAIK it is not available in the Magisk app for now, so you will have to download it from GitHub. In the README there are additional instructions. Like stated there, you may also need "MagiskHide Props Config" (available within Magisk Manager) to spoof CTS profile, but I think there was no need for me to do this.

Hope you can get it to work with this hint!
Good luck and greetings!
Many thanks @sarius02 .
Let me try and will let you know if i would be successful.
 

ElPakoTech

Member
Apr 18, 2020
21
30
The official doc isn't bad but you need an extra step:
1) Before running repo sync, add roomservice.xml from Synt4x93's Github to .repo/local_manifests/ in the Lineage root folder.
2) Then run repo sync and the rest of the instructions. You can skip the "Extract proprietary blobs" step.

Of course make sure you are checking out 18.1 not 17.1 during repo init. My first build attempt crashed out after running low on RAM but hopefully you folks have luck!

Hi,

Thanks for the tips, I build my own and it work really good, big thanks to Synt4x93's for his work, Rom is stable and smooth. Maybe the battery life was a tiny little bit better with official Lineage 17.1 but that's just a feeling, and it's still really good to me. In fact I also use NikGapps instead OpenGapps on this rom witch maybe impact differently the battery, not sure about that.

I just discover a small bug: when I reboot, some settings are being reset (dark mode, lock screen settings, quick settings on the top). Is it just me or do you have the same problem ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 43
    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.