yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] Klaus20:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] Neurotical:
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://xdaforums.com/t/basebands-m...0-17-07-2021-android-10-pie-stockrom.3858990/
[Samsung Galaxy S9 & S9+ Cross Device Development] Klaus20:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] ipilcher:
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.)
[Samsung Galaxy S9 & S9+ Cross Device Development] Monvigliero:
[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.
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] quangthai_itdlu:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] quangthai_itdlu:
Thanks bro, I will be try with this commit
[Samsung Galaxy S9 & S9+ Cross Device Development] quangthai_itdlu:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
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

...
# 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.
[Samsung Galaxy S9 & S9+ Cross Device Development] quangthai_itdlu:
Hi @ElPakoTech

Thank you so much :)
[Samsung Galaxy S9 & S9+ Cross Device Development] Gueste4555:
how to activate do not disturb mod in settings?
[Samsung Galaxy S9 & S9+ Cross Device Development] squarty:
Hi all,

can you confirm VoLTE isn't working yet ?
[Samsung Galaxy S9 & S9+ Cross Device Development] cybermiguel:
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).
[Samsung Galaxy S9 & S9+ Cross Device Development] whuupwhuup:
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?
[Samsung Galaxy S9 & S9+ Cross Device Development] zhelev81:
which magisk and gapps do we flash ?? can someone post links ?
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
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.

GitHub - synt4x93/android_device_samsung_universal9810-common

Contribute to synt4x93/android_device_samsung_universal9810-common development by creating an account on GitHub.

github.com

GitHub - synt4x93/android_device_samsung_starlte

Contribute to synt4x93/android_device_samsung_starlte development by creating an account on GitHub.

github.com

GitHub - synt4x93/android_kernel_samsung_universal9810

Contribute to synt4x93/android_kernel_samsung_universal9810 development by creating an account on GitHub.

github.com

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 ).
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
ElPakoTech,​

this screen ??

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 !!!

:)
[Samsung Galaxy S9 & S9+ Cross Device Development] ElPakoTech:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
---=== 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
[Samsung Galaxy S9 & S9+ Cross Device Development] king1990:
To use rob latest trees you need to format your data to f2fs. Rob is forcing f2fs in his latest trees.
[Samsung Galaxy S9 & S9+ Cross Device Development] Galaxy9plus-support:
My build works and filesystem still shows its ext4, can i use recovery >> wipe >> advanced wipe >> change the file system to f2fs ?? Do i need to in the future ??
[Samsung Galaxy S9 & S9+ Cross Device Development] dreas74:
Thanks @ElPakoTech for your new realease.

With this release the safetynet test can passed again.

with the older release i had issues to pass safetynet.
[Samsung Galaxy S9 & S9+ Cross Device Development] Im1Random:
Is the project dead?
[Samsung Galaxy S9 & S9+ Cross Device Development] heni63:
Hey gnarf, can you help me?

Got a similiar problem with my Lineage OS (Beyond0Lte S10e). I realla don't know what to do (and barely understood anything with your "selfbuild". Any guidelines you can give me to fix the error? Would

be super cool id be really thankful! :))

I kinda solved the "failed to create unix domain" (just disabling stuff and some settings, not sure what)

But the "Lightsservice" error remains.
[Samsung Galaxy S9 & S9+ Cross Device Development] stts44444:
I love LineageOS. It turned my bogged down S5s into wonderful little gadgets. But the world is changing. My Sprint S5s are about to be shut off. And they say dont buy any phone that cant do VoLTE. Well, Lineage OS cant do VoLTE either. So is this the end on the line for non 5G phones on LineageOS ??? I was going to get s9 or s10 exynos to replace my USA s5 but it looks like its just a waste. May as well get a Snapdragon since Lineage is out of buisness in a VoLTE world. Lots of Snapdragons in USA at better prices.
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
I was running on NobleROM 1.7, therefor I had t download the most recent samsung firmware.

I want to try Lineage 18.1. After installing and rebooting the phone always reboots into the download window.

Anybody an idea how to solve this?
[Samsung Galaxy S9 & S9+ Cross Device Development] Davy-Jones:
Try another (older or newer) Version of TWRP.
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
I started of with twrp 3.3.1.1,thereafter I tried 3.6.0.9.0 and 3.2.3.0.

Always the same problem, after installing and rebooting I end in the download window.
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
You probably wiped vendor or there is one not compatible with Lineage 18.1. Install a ROM with OneUi 2.5 like Alexis one or xFire which is the best I tried and then wipe dalvik cache data system and flash the ROM with gapps
[Samsung Galaxy S9 & S9+ Cross Device Development] francoism90:
I don't know if someone is interested, but I'm planning in continuing developing this ROM for my S9, based on the sources here (without them, it wouldn't be possible) and the 9820 repo (adding some features/changes).

Checkout my sources here:

GitHub - francoism90/android_device_samsung_starlte

Contribute to francoism90/android_device_samsung_starlte development by creating an account on GitHub.

github.com

GitHub - francoism90/android_device_samsung_exynos9810-common-old

Contribute to francoism90/android_device_samsung_exynos9810-common-old development by creating an account on GitHub.

github.com

GitHub - francoism90/local_manifests-old

Contribute to francoism90/local_manifests-old development by creating an account on GitHub.

github.com

Things missing:

- SELinux could use improvements, but so far my knowledge is lacking.

- Kernel updates, could someone please explain how to bump the kernel?

I can share a build, but it's buggy and I really want to stress out, I'm not responsible for any damage whatsoever.
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
Both Alexis and xFire cause a bootloop.

I'm now running Noble rom, that's the successor of Alexis rom.

Since I tried xFire I'm stuck with the xFire logo at startup, is there a way to get rid of it?
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
What I can tell you, is to try to install TWRP 3.5.2_9-0 which is the most stable. If it doesn't work return to the basic settings. Wipe the system and flash the latest stock ROM for your country with Odin.

Then wipe and install xFire or Alexis 2.5 and then wipe again before install Lineage.
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
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?
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
Format data in twrp and wipe all system dalvik cache then install lineage
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
Almost hurray, Lineage installed and starts booting (the living lineage logo appears) but after a couple of minutes the phone reboots again into twrp.
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
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?
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
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?
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] Bertonumber1:
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
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
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.
[Samsung Galaxy S9 & S9+ Cross Device Development] deboopi2:
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?
[Samsung Galaxy S9 & S9+ Cross Device Development] Pierfranc:
Magisk https://cdn.magisk.us/Magisk/Magisk-23.0.zip

Safetynet fix to flash with Magisk https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.3/safetynet-fix-v2.1.3.zip