• 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

whuupwhuup

Member
Feb 6, 2021
9
4
A couple of questions as I am somewhat new:
1. Why is this build unofficial resp. what is preventing this build to become official again (as starlte official was discontinued after LOS 17.1)?
2. How trustworthy is an unofficial build compared to an official build?
 

ElPakoTech

Member
Apr 18, 2020
21
30
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 ).
 
Last edited:

francoism90

Member
Dec 18, 2016
9
1
Thanks for the instructions! I was aware of the new repo's, although I don't know if this means development has started again.

Isn't it normal encryption breaking when switching ROMs? For this reason I always sync my data so I don't loose any important files.
 
Mar 19, 2021
20
5
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 ).

ElPakoTech,​

this screen ??
fix-Decryption-unsuccessful.jpg


Is it the synt4x93 repo ?? I tried wipe ( data,system,cache ) then clean install of working version 14 sept ( mybuild), then flashed 10 october build over the top. Encyption OFF on fresh build. and it still showed this screen. Then I tried wipe, and

Neurotical latest build from the 10th October and still showed the encrypt error screen in my case, maybe I didn't wipe something before install ??​

Even thou the system was wiped and not encypted. Same error. I too lost all data / apps etc, but there is something wrong with this LOS / android build??
I can't build my own with the current manifest below ( synt4x93 / geokynda kernel / LOS )

Heres my roomservice

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!--
<project name="synt4x93/android_kernel_samsung_universal9810" path="kernel/samsung/universal9810" remote="github" revision="4.9.118" /> -->
<project name="Geoknyda/android_kernel_samsung_universal9810" path="kernel/samsung/universal9810" remote="github" revision="4.9y" />
<project name="synt4x93/android_device_samsung_universal9810-common" path="device/samsung/universal9810-common" remote="github" revision="lineage-18.1" />
<project name="synt4x93/android_device_samsung_star2lte" path="device/samsung/star2lte" remote="github" revision="lineage-18.1" />
<project name="synt4x93/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-18.1" />
</manifest>

NOTE: this only builds the star2lite ( S9+ ), I removed the others cause its a personal build and are not required.

Note the kernel has been <!-- comment out --> to use the latest 4.9y, this worked fine all the way up to yesterday. I also tried to build with kernel 4.9.118 and yesterdays updates, and that did the same error above. Kernel 4.9y can dirty flash right over the top of 4.9.118 and synt4x93 repositories. 4.9y gets about 15-20% longer batter life on a daily use.

I have a build from the 14th Sept with 282 kernel ( public keys ), I'll use that. But interested whats gone wrong with android / LOS build.

Also what backup do you use? Built in seedvault is kinda useless as it doesn't recover all my apps and some dont allow access to it anyway.

I like making my own builds, i did try to clean wipe / install Neuroticals build ( handy to have OTA working ), but even that didn't work for me. Probably didn't wipe before hand everything that was needed to.

Thoughts?
Ideas on getting past this error screen?
Changing filesystem >> fat >>ext4 as suggested and other things from search didn't work. Once the phone has been wiped, you'll try anything, nothing to lose !!!

:)
 
Last edited:

ElPakoTech

Member
Apr 18, 2020
21
30
Hi @Galaxy9plus-support ,

Its not the synt4x93 libraies. I tried wipe ( data,system,cache ) then clean install of working version 14 sept ( mybuild), then flashed 10 october build over the top. Encyption OFF on fresh build. and it still showed this screen. Then I tried wipe, and

@Neurotical latest build from the 10th October and still showed the encrypt error screen​

Even thou the system was wiped and not encypted. Same error. I too lost all data / apps etc, but there is something wrong with this LOS / android build??
So I had the same problem using a custom build fully based on synt4x93 updated sources and I had the same error as you. After wiping and clean everything, it was not possible to boot and use the build at all, I rollback to my previous build. (I have also to wipe/clean everything again before installing my previous working build otherwise the error was still there).

You should avoid using this sources until synt4x93 publish a new build maybe.
I personally do some cherry-pick code from Geoknyda repo and I will try also to get more from synt4x9 in a near future.
I haven't used the last sources from Geoknyda yet but I will build this week and I let you know if something wrong (I use his updated kernel).

You can check here my repo:
device
kernel
OTA

I can't build my own and Neurotical clean wipe / install doesn't work either.

Try to build again from Geoknyda (or mine if you want) but remove any synt4x93 sources in your roomservice file and replace it. For example:

<?xml version="1.0" encoding="UTF-8"?> <manifest> <!-- <project name="Geoknyda/android_kernel_samsung_universal9810" path="kernel/samsung/universal9810" remote="github" revision="4.9y" /> <project name="Geoknyda/android_device_samsung_universal9810-common" path="device/samsung/universal9810-common" remote="github" revision="lineage-18.1" /> <project name="Geoknyda/android_device_samsung_star2lte" path="device/samsung/star2lte" remote="github" revision="lineage-18.1" /> <project name="Geoknyda/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-18.1" /> <project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-18.1" /> </manifest>


Also what backup do you use? Built in seedvault is kinda useless as it doesn't recover all my apps and some dont allow access to it anyway.

Well, I made and use a custom bash script (linux) based on ADB to backup/restore my phone. It save all data (files, photos,..) plus apps/data apps, contacts, phone logs, SMS/MMS, and custom tricks for chrome/firefox to get bookmarks for example.

The drawback is that some data apps can't be backup so it's not perfect (related to ADB and apps policies). With android 12, it will be worse as ADB won't backup any data from apps. I thinks google will remove "ADB backup" completely from android in the future.

I plan to use seedvault next but I think we may have the same issue as ADB to get the data apps. Wait and see.
 
Mar 19, 2021
20
5
Hi @Galaxy9plus-support ,


So I had the same problem using a custom build fully based on synt4x93 updated sources and I had the same error as you. After wiping and clean everything, it was not possible to boot and use the build at all, I rollback to my previous build. (I have also to wipe/clean everything again before installing my previous working build otherwise the error was still there).

You should avoid using this sources until synt4x93 publish a new build maybe.
I personally do some cherry-pick code from Geoknyda repo and I will try also to get more from synt4x9 in a near future.
I haven't used the last sources from Geoknyda yet but I will build this week and I let you know if something wrong (I use his updated kernel).

You can check here my repo:
device
kernel
OTA



Try to build again from Geoknyda (or mine if you want) but remove any synt4x93 sources in your roomservice file and replace it. For example:

<?xml version="1.0" encoding="UTF-8"?> <manifest> <!-- <project name="Geoknyda/android_kernel_samsung_universal9810" path="kernel/samsung/universal9810" remote="github" revision="4.9y" /> <project name="Geoknyda/android_device_samsung_universal9810-common" path="device/samsung/universal9810-common" remote="github" revision="lineage-18.1" /> <project name="Geoknyda/android_device_samsung_star2lte" path="device/samsung/star2lte" remote="github" revision="lineage-18.1" /> <project name="Geoknyda/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="lineage-18.1" /> <project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-18.1" /> </manifest>




Well, I made and use a custom bash script (linux) based on ADB to backup/restore my phone. It save all data (files, photos,..) plus apps/data apps, contacts, phone logs, SMS/MMS, and custom tricks for chrome/firefox to get bookmarks for example.

The drawback is that some data apps can't be backup so it's not perfect (related to ADB and apps policies). With android 12, it will be worse as ADB won't backup any data from apps. I thinks google will remove "ADB backup" completely from android in the future.

I plan to use seedvault next but I think we may have the same issue as ADB to get the data apps. Wait and see.

---=== UPDATE TO WORKING METHOD ===---
Using the manfest above from ElPakoTech but with this change

<project name="Geoknyda/android_device_samsung_universal9810-common" path="device/samsung/universal9810-common" remote="github" revision="lineage-18.1_beta" />

Note: version 18.1_beta <<<< who knows if this is significant

Built fine, installed without a hitch. DIrty flashed directly over previous working synt4x93 repo / Geokynda kernel / LOS with September patch. No data lost.

Now with kernel 286, patch 1st October.

Looks like synt4x93 repos cannot work with LOS anymore. Tried using kernel 118 ( synt4x93 kernel ) + all his manifest, builds fine, but on install gave the error. For kicks and giggles, because I had to wipe the phone completely, I even tried leaving a fresh wipe > install from 14th septemeber ( 118 kernel ) and NO ENCRYPTION. Then tried both 118 kernel AND 4.9y kernel builts with synt4x repos over the top, error. How can I get the "encryption" error if the system in UNencrypted ?? LOL

No idea why a fresh wipe and install of neurotical latest prebuilt file didn't work for me.

Anyway, going forward, use complete Geokynda manifest with LOS and you can build and install on 9+. That was my experience.

Massive thanks to neurotical ( for providing his manifest ) and ElPakoTech above

⭐️⭐️⭐️⭐️⭐️
👍

Feel like squid player 456 now :O
9+ working fine like before

Need to find a good backup solution, would love something like clonezilla for a mobile LOL
 

Top Liked Posts

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