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

Search This thread

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
Ok, I went back to stock rom (this is what I had to do the first time) and then reinstalled Lineage.
The good news, Lineage boots but then complains that the data cannot be encrypted.
I need to erase the data but it stays forever on the screen erasing data.
So what now?
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
Ok, I went back to stock rom (this is what I had to do the first time) and then reinstalled Lineage.
The good news, Lineage boots but then complains that the data cannot be encrypted.
I need to erase the data but it stays forever on the screen erasing data.
So what now?
Format data in twrp and wipe all system dalvik cache then install lineage
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
Almost hurray, Lineage installed and starts booting (the living lineage logo appears) but after a couple of minutes the phone reboots again into twrp.
Did you install lineage directly after stock?
Which is your model? S9+ or S9? Exynos? 960F?
Before installing lineage, try OneUi 2.5.
Wipe the partitions then flash this https://androidfilehost.com/?fid=2188818919693789647

If it's working proceed with lineage.
Be sure to wipe and install only lineage 18.1 without any gapps and root.
 

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
It's a 965F Samsung S9+ exynos.
I'll have another look but I thought it was OneUI 2.5.
So I need to start with xFire before Lineage, stock ro is not enough?
 

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
Did you install lineage directly after stock?
Which is your model? S9+ or S9? Exynos? 960F?
Before installing lineage, try OneUi 2.5.
Wipe the partitions then flash this https://androidfilehost.com/?fid=2188818919693789647

If it's working proceed with lineage.
Be sure to wipe and install only lineage 18.1 without any gapps and root.
Thanks for all the help so far but still no success.
Before installing xfire, formatting data, wiping system, cache and dalvik cahce.
If I do not format data I get an error on mounting data.
At installation xFire (I did not take the file you mentioned because that's for the S9, took the one for the S9+ instead).
Applying CSC feature MOD and then the next line
Failed XML File is encrypted

At the end of the installation I get following line in red
Failed to mount /odm no such file or directory

After restarting xFire the installation process looks exactly as the one for the Stock ROM, after booting it also looks exact as stock ROM.

Installing lineage (with format data, wipe system, cache , dalvik cache).
Lineage starts up, moving logo and then reboots into twrp (recoveryà just as happended before.

Any other ideas?
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
Thanks for all the help so far but still no success.
Before installing xfire, formatting data, wiping system, cache and dalvik cahce.
If I do not format data I get an error on mounting data.
At installation xFire (I did not take the file you mentioned because that's for the S9, took the one for the S9+ instead).
Applying CSC feature MOD and then the next line
Failed XML File is encrypted

At the end of the installation I get following line in red
Failed to mount /odm no such file or directory

After restarting xFire the installation process looks exactly as the one for the Stock ROM, after booting it also looks exact as stock ROM.

Installing lineage (with format data, wipe system, cache , dalvik cache).
Lineage starts up, moving logo and then reboots into twrp (recoveryà just as happended before.

Any other ideas?
well, so you have S9+ while I have S9, so the procedure may be different. Anyway why you want go with Lineage if S9+ is fast enogh for OneUi?
The custom OneUi doesn't miss anything.

The message you got is when the partition is encrypted and can't be written, so to format data is required, but not only wipe data, format data is a button apart on the bottom right of screen, you write yes and then data can be formatted from twrp.
If you already did it, then something is missing but I have not S9+ so I don't know exactly all the steps for that phone.
What I know is that not being able to write the partition is due to the wrong recovery. So it's about to get the right one twrp-3.5.2_9-0-star2lte from https://dl.twrp.me/star2lte/
Try with this and follow this guide
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
Thanks for all the help so far but still no success.
Before installing xfire, formatting data, wiping system, cache and dalvik cahce.
If I do not format data I get an error on mounting data.
At installation xFire (I did not take the file you mentioned because that's for the S9, took the one for the S9+ instead).
Applying CSC feature MOD and then the next line
Failed XML File is encrypted

At the end of the installation I get following line in red
Failed to mount /odm no such file or directory

After restarting xFire the installation process looks exactly as the one for the Stock ROM, after booting it also looks exact as stock ROM.

Installing lineage (with format data, wipe system, cache , dalvik cache).
Lineage starts up, moving logo and then reboots into twrp (recoveryà just as happended before.

Any other ideas?
In case you still haven't been successful, try this, flash twrp 3.3.1-0 which should work to wipe partitions and rightly install the rom. https://dl.twrp.me/star2lte/twrp-3.3.1-0-star2lte.img.tar.html
Flash custom rom OneUi 2.5

PS
You can flash the last twrp 3.6.0 and then install a custom OneUi 2.5 ROM, but after you flashed the rom before rebooting, install Magisk v23.0 too https://cdn.magisk.us/Magisk/Magisk-23.0.zip
 
Last edited:

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
well, so you have S9+ while I have S9, so the procedure may be different. Anyway why you want go with Lineage if S9+ is fast enogh for OneUi?
The custom OneUi doesn't miss anything.

The message you got is when the partition is encrypted and can't be written, so to format data is required, but not only wipe data, format data is a button apart on the bottom right of screen, you write yes and then data can be formatted from twrp.
If you already did it, then something is missing but I have not S9+ so I don't know exactly all the steps for that phone.
What I know is that not being able to write the partition is due to the wrong recovery. So it's about to get the right one twrp-3.5.2_9-0-star2lte from https://dl.twrp.me/star2lte/
Try with this and follow this guide
Hurray, following the video and installing without wiping dalvik cache worked.
Lineage up and running.
Installed gapps but contacts do not synchronize (installed nikgapps).
Running but not there yet.
At least thanks for all the help and replying time after time with new suggestions
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
Hurray, following the video and installing without wiping dalvik cache worked.
Lineage up and running.
Installed gapps but contacts do not synchronize (installed nikgapps).
Running but not there yet.
At least thanks for all the help and replying time after time with new suggestions
No problem, you're welcome. Helping when you can is always a challenge
To syncronize try open gapps or bitgapps.
For open gapps it's better to use these fixed for Q https://androidfilehost.com/?fid=10763459528675593688
 
Ok, I went back to stock rom (this is what I had to do the first time) and then reinstalled Lineage.
The good news, Lineage boots but then complains that the data cannot be encrypted.
I need to erase the data but it stays forever on the screen erasing data.
So what now?
In the future when faced with data partition/encryption problems...
In TWRP goto wipe, repair or change filesystem.
Select ext2, swipe.
Then go back, select ext4 swipe.
Return to main menu and reboot system.

If you need Playstore certification also.
Use a filemanager such as mixplorer.

Goto Root directory /Data/Data/com.android.vending/SharedPrefs/Finsky.xml.

Open Finsky.xml and look for the line :
<boolean device.google.certified =<"false"> (maybe worded slightly different from device to device)

Change "false" inside the quotes to "true" save the amendment, exit and reboot phone.
This will give you google certification also.



Regards
 
Last edited:

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
No problem, you're welcome. Helping when you can is always a challenge
To syncronize try open gapps or bitgapps.
For open gapps it's better to use these fixed for Q https://androidfilehost.com/?fid=10763459528675593688
for the time being I gave up with Lineage.
I get things installed but I cannot get my bank app to work..
I know about magisk but then you have to root ad it does not always work.
I know my bank is very strict about security, but even then I can run it wit Noble rom.
If there is a working solution fr bank apps I will give it another try.
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
for the time being I gave up with Lineage.
I get things installed but I cannot get my bank app to work..
I know about magisk but then you have to root ad it does not always work.
I know my bank is very strict about security, but even then I can run it wit Noble rom.
If there is a working solution fr bank apps I will give it another try.
Of course. Everything is as usual. Everyone uses bank apps and so anyone needs to them working. The procedure exists.
After rooting with Magisk, there a safety net pass package to flash and then hide the banking apps from Magisk settings and it's done.
 

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
Of course. Everything is as usual. Everyone uses bank apps and so anyone needs to them working. The procedure exists.
After rooting with Magisk, there a safety net pass package to flash and then hide the banking apps from Magisk settings and it's done.
I've got some spare time left so I will give it another go.
What version of magisk do I need because I heard the latest ersion doesn't have the hide option anymore.
What package do I need for the safety net pass?
 

Pierfranc

Senior Member
Nov 20, 2011
414
35

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
Magisk installed ok.
I tried the safetenynet twice (once directly after flashing magisk and a second time after opening magisk and rebooting into recovery).
Both times I get this message
Updater process ended with ERROR: 123
Error installing zip file '/external_sd/backups/apps/magisk/safetynet-fix-v2.1.3.zip'
Updating partition details
...done

Previous time I installed nikgapps and now I installed bitgapps.
Both have the same problem
Google play knows my account but I have problems synchronizing contacts and calendar..
When I go to settings - settings for google apps - google contacts sync.
If auto sync is off and I try to sync I get the message: Trouble syncing, waiting to try again.
When autosync is on is a red exclamation markfllfsed by the text need contacts permissions
 

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
Magisk installed ok.
I tried the safetenynet twice (once directly after flashing magisk and a second time after opening magisk and rebooting into recovery).
Both times I get this message
Updater process ended with ERROR: 123
Error installing zip file '/external_sd/backups/apps/magisk/safetynet-fix-v2.1.3.zip'
Updating partition details
...done

Previous time I installed nikgapps and now I installed bitgapps.
Both have the same problem
Google play knows my account but I have problems synchronizing contacts and calendar..
When I go to settings - settings for google apps - google contacts sync.
If auto sync is off and I try to sync I get the message: Trouble syncing, waiting to try again.
When autosync is on is a red exclamation markfllfsed by the text need contacts permissions
I found out how to nstall safetynet as a module but the the afetynet check wasn't passed. Installed the extra magiskhide props config end then the safetynet bypass. Safetynet still didn't pass
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
Magisk installed ok.
I tried the safetenynet twice (once directly after flashing magisk and a second time after opening magisk and rebooting into recovery).
Both times I get this message
Updater process ended with ERROR: 123
Error installing zip file '/external_sd/backups/apps/magisk/safetynet-fix-v2.1.3.zip'
Updating partition details
...done

Previous time I installed nikgapps and now I installed bitgapps.
Both have the same problem
Google play knows my account but I have problems synchronizing contacts and calendar..
When I go to settings - settings for google apps - google contacts sync.
If auto sync is off and I try to sync I get the message: Trouble syncing, waiting to try again.
When autosync is on is a red exclamation markfllfsed by the text need contacts permissions
About safetynet it must be installed through Magisk, means after opening Magisk app you have to choose the puzzle icon on the bottom right and then install it from device option as a module. After that reboot.
For the Google apps I gave you a link which is open gapps and it's working Aosp and lineageos roms
 

Pierfranc

Senior Member
Nov 20, 2011
414
35
I found out how to nstall safetynet as a module but the the afetynet check wasn't passed. Installed the extra magiskhide props config end then the safetynet bypass. Safetynet still didn't pass
Did you read this message?
You need to install Riru from online modules and then safetynet fix.
If still not working needs an update.
 

Attachments

  • Screenshot_20220101-144611.jpg
    Screenshot_20220101-144611.jpg
    166.6 KB · Views: 9

deboopi2

Senior Member
Nov 12, 2011
562
43
MECHELEN
I found out how to nstall safetynet as a module but the the afetynet check wasn't passed. Installed the extra magiskhide props config end then the safetynet bypass. Safetynet still didn't pass
I set a correct fingerprint and no safetynet check is passed, in safetynet I get
basicintegrity = ok
ctsProfile = ok
evaltype = Basic

But my ankapp still refuses to work
 

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.