yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
Yeah, I gave that a shot as well as wiping internal memory. I'm sure that I'm doing something wrong, so let me retry detailing my process.

FROM SPLASH SCREEN THAT WON"T BOOT

1. Boot into download mode, and from Odin put TWRP on AP and click start, hold volup/bixby/power to boot into TWRP

2. In TWRP, use read only mode and go to wipe

3. Wipe > Advanced Wipe > dalvik/system/data/internal storage/cache all wiped

4. Wipe > Format Data

5. Install > Install Zip > no-verity-opt-encrypt-6.0-star.zip

6. Install > Install Image > star2lte-vendor-CSF2.img

7. Install > Install Zip > lineage-16.0-20190717-UNOFFICIAL-star2lte.zip

8. Reboot

9. Arrive at splash screen, wait 5-10 minutes

10. If phone is still at splash screen, repeat the steps above

This is what I have been doing each time I encounter the splash screen that will refuse to boot. If anyone has any other suggestions I am all ears.

Thanks to everyone else that has helped me out so far as well, I appreciate it.
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
Follow this sequence.

Wipe cache/dalvik cache

Flash vendor.img

Flash Lineage is

Flash gapps

Flash Magisksu

Reboot.

You can skip Magisksu and Gapps if you do not want it.

Follow this sequence without having no-verity-opt-encrypt-6.0-star.zip flashed or vendor.img flashed in the last
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
Gave your method two tries, although both attempts still kept me at the splash screen.
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
Just to be sure (after wiping like [MENTION=7478074]bdwilk[/MENTION] suggested it should work... crazy): You are using G960F or G965F, right? Not U or DS or something, but international F (Exynos) version?
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
Oh man I really hope this isn't the case, I do have the dual sim version of the S9+ although I am under the impression that it is still a G965F (the model number is G965F/DS), my phone always gets detected as G965F whenever installing anything and I have had no problems installing other G965F roms.
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
Well ok, should work. Just wanted to be sure you got no Snapdragon device. ;)

Did you already try flashing a GSI, does that work (e.g. Havoc GSI), means nothing stock based? If that works it's probably a ROM issue and you could maybe fetch a logcat with ADB to help dev fix the issue. You could try that anyways, often logcats are helpful even for normal users to understand what exactly went wrong and sometimes give you a hint what to look for.

adb logcat -v time > log.txt (when in bootloop)

or

adb pull /cache/recovery/last_log or last_log.1 (when in TWRP, just to see if there are issues maybe on install already)

On Windows get ADB here (on Linux your package manager has it): https://xdaforums.com/showthread.php?t=2317790 (use portable version)

- extract contents to C:\ADB

- run cmd.exe

- cd c:\adb

- run one of the above commands to get your logcat

Logcat will only work if system is already booted to a certain state (and then bootloops) where adb interface is already available. There might be a chance that won't work but it is worth a try.
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
I tried multiple GSI roms and none of them worked for me. I wasn't able to run the "adb logcat -v time > log.txt" command on any rom, it wouldn't proceed from waiting for device. However, I am able to get the last_log from TWRP, and I was not able to fully understand it. Is there anything that you can see sticking out as a problem?

Thanks again for all of your help.
[Samsung Galaxy S9 & S9+ Cross Device Development] verynuclear:
Anyone managed to have a working Galaxy wearable app for Gear S3?

I'm also having many app not working from play store as device is not supported :(

Thanks for any help
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
Log seems to be ok for me, flashing seems to be completed well. So there is nothing I can't help you with any further. I feel really sorry for you. Looks like locked bootloader for me (symptoms) but that's surely not the case. If you are sure that it's not locked, that's bad luck, mate. :(

Maybe someone else has an idea, but that's all I can imagine to fix your issue.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
Ok. Try it without read only in TWRP. That has to be the culprit. I know I've read all the guides as well and I'm still not sure why they say to do it that way. Swipe to allow modifications.
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
Try checking it you have the most recent and updated TWRP!!

Reflash TWRP, official one.

TRY flashing stock based in rom and then follow instructions

Hope one of these solutions work.
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
I reinstalled latest TWRP and tried flashing the soldier rom that works just fine and then following instructions, still getting a bootloop. This is not just for this rom either, any of the other GSI ones that I tried made my phone bootloop as well. I tried to reinstall a fresh bootloader onto the phone in Odin but that didn't work either.

Anyone have any other ideas?
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
Did you subscribe to Samsung official beta program before official Pie came out?
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
No, I don't believe so.
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
Would using TWRP to install the zip as an upgrade work? I'm currently on an older unofficial build, from https://xdaforums.com/galaxy-s9/sam...elopment/rom-lineageos-16-unofficial-t3899587, lineage_starlte-userdebug 9 PQ2A.190205.001 eng.alex.20190216.23370 test-keys Seems like I should nuke it all flash this from scratch as if it's new and reinstall everything.

Also, any way to tell which vendor image(s) I have currently? Or do I need to just go and find the right one and flash that anyway first?
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
I had problems with that. Check if your bootloader is in state prenormal with Vol down + Bixby + Power for a few seconds until teal screen appears. Sounds like that as stock ROMs work (stock kernel) but no custom ones. If it's prenormal flash totally stock fw (not Soldier's!) with Odin. Can be found on updato.

Afterwards check again if it's still prenormal. If not, just go through whole process of unlocking bootloader again (don't forget the no-verity part). If finished flashing any ROM should work.

If it's still prenormal after flashing stock... well that would be bad.
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
How do you know if it's in state prenormal? The picture attached is what I can see on my phone. Also, do you know of any alternatives to updato? I am getting an estimated time of a day to download.
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
Stock firmware-> https://xdaforums.com/galaxy-s9-plus/how-to/official-stock-firmware-thread-samsung-t3764479

to check the baseband version/vendor version check build details- the last 4 digits is the stuff you looking for.
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
Should work. Did the same and it worked for me as it's both Lineage. But be aware that this might lead to some weird issues (don't report bugs here if so), but with a bit of luck you will experience no issues. Be safe and make a backup before.

Before dirty flashing, update your vendor with the one that OP provides.

Anyway, clean flash is always better to avoid issues. ;)

---------- Post added at 07:15 PM ---------- Previous post was at 07:07 PM ----------

Well, bootloader is unlocked (FAP, OEM, custom binary), there should be no problem in flashing any ROM but it's strange that stock based work but not AOSP ones not, this is only the case with locked BL but it clearly is unlocked. Still it's worth a try to flash stock and try again, just to try anything possible with a small chance (sorry) to fix the issue.
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
Yea, I'll take a full backup and copy off 100% of my data first before trying the upgrade flashing. And of course do the vendor image first.
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
Flashed the stock rom and went from there, still ended up with being stuck at the same screen.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
Can't remember if you've checked already but make sure the download is good. Check md5. Maybe download the ROM again.
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
I have tried these both and started checking the md5 in twrp before I install the rom, it is a good rom in both my computer and my sd card.
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
So weird. Other than the "swipe to allow modifications" I can't see any difference from your setup to anyone elses.
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
I have seen a few other people have the same issue where they can't boot past splash screen in any custom roms, although none of those were solved. I really want to be able to use this ROM though, I don't know how I should proceed from here :/
[Samsung Galaxy S9 & S9+ Cross Device Development] pshay8:
this is a great rom thanks. does the heart rate monitor works? because in Samsung health it dosent appear
[Samsung Galaxy S9 & S9+ Cross Device Development] comkioxd:
I'm pretty sure that it doesn't work
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
never thought i'd see the day.. i'd given up hope.

so are we in agreement that finally a daily driver lOS S9 exists? I see some bugs listed (mostly camera and some battery) other than no issue with bluetooth or phone calls like the others? thanks!

You must be one of hell of a developer [MENTION=7861769]Synt4x.93[/MENTION] you have succeeded where so many have failed. :)
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
The only bugs so far are things that do not matter to me like face unlock, heartrate sensor, VoLTE, VoWiFi, Brightness slider and few features from LOS to name a few.

Battery is never been better. Not even on stock. I get an average of 6 hrs SOT. On stock, used to get 4hrs with all my stuff active like LTE, WIFI, Location services.

CAMERA works for me. I got GCam and Asus Rog Phone Camera doing the service
[Samsung Galaxy S9 & S9+ Cross Device Development] zohaibshafijutt:
Kindly share link of Asus Rog Phone Camera port
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
Here it is
[Samsung Galaxy S9 & S9+ Cross Device Development] Akhayev:
Flash brk3 bendor then flash the rom then flash endurance's oreo aosp kernel , if u do that all gsi roms will work
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
Appreciate the write up mate! How does camera compare to stock?
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
I would rate 6.5/10. It's better than stock LOS cam but not as great as OneUi cam
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
The ROG phone camera is great! Best one yet as the Gcam port can't get focus here (3.5 version, 4.1 just crashes very often).

This one is a great replacement. Not many options in settings, but that doesn't matter much if the quality is that good. :)
[Samsung Galaxy S9 & S9+ Cross Device Development] mix99mix:
Very good ROM, fast and stable. Tks again

Very good ROM, fast and stable. Tks again
[Samsung Galaxy S9 & S9+ Cross Device Development] afcaajax:
Yes is stable enough for daily use. Everything is working smooth and fine
[Samsung Galaxy S9 & S9+ Cross Device Development] nicomari29:
The instagram camera, snapchat and watshapp are laggy
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
Does anyone know why I would be able to flash and install lineage 15.1 just fine, but when I try to take the same steps to flash and install lineage 16, I can't boot past the "secured by knox" screen? I am flashing the csf2 vendor image to vendor partition and the zip file is installing normally without error, although it refuses to boot. Any ideas?
[Samsung Galaxy S9 & S9+ Cross Device Development] afcaajax:
Use the system camera. Snapchat and Instagram are always laggy on Android
[Samsung Galaxy S9 & S9+ Cross Device Development] burninitup:
Whatsapp camera is laggy during video calls. Else it's okay to capture pics. You can use duo though. It works fine
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
Did you follow all.the steps on OP?
[Samsung Galaxy S9 & S9+ Cross Device Development] Newsplash:
Yeah, to a T.
[Samsung Galaxy S9 & S9+ Cross Device Development] zeyaan:
Please read some of the previous posts, should help you.
[Samsung Galaxy S9 & S9+ Cross Device Development] paul c:
Before you flash, take a full backup in TWRP (everything apart from the caches). Then, you can investigate the ROM's capabilities, and if you don't like it you can wipe then restore your backup.

If you haven't yet installed TWRP on your phone, first follow the instructions in the TWRP thread.
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
Google Camera port is very much comparable to stock OneUI, not quite as crystal clear but it is very, *very* good. 9/10.

If you want anything better, stick with OneUI, the Samsung camera is *for sure* the best you will find for your device.

*All* other camera apps, including the built-in are, indeed, around the 6.5/10 mark, mediocre quality at best. You will be disappointed.
[Samsung Galaxy S9 & S9+ Cross Device Development] ulysse132:
How can you get OneUI cam for non stock rom ? Do you have a link to install it on lineageos ?
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
You can't.
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
Wow, this newer build, 7/17, is SO much better battery life than the old version of LOS 16 I had installed.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
I assume you're using iDans port v3.5 with the OneUI fix?
[Samsung Galaxy S9 & S9+ Cross Device Development] ggow:
Hi @Synt4x.93,

Thanks for the nice rom :good:
[Samsung Galaxy S9 & S9+ Cross Device Development] ggow:
Don't worry, its started working somehow. Very strange
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
Well, I'm using one of these, not sure which one as post install only the package name is visible in System.

I don't use OneUI, otherwise there would really be no point installing G-Cam at all, since Samsung's camera is already superior but yes, I think the version you are referring to is the same one.

Either:

GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix

Or:

GCam_5.1.018.177470874.41362666_IDan_N6_4.1_fix

One of them force closes for me, the other works great, I just can't remember which I ended up with.
[Samsung Galaxy S9 & S9+ Cross Device Development] geronimoge:
Thanks, so it's this one with the OneUI fix:

https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_3.5_fix.apk

I'm using the same and was curious if there's a better and newer one.
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
Yep, [MENTION=7641259]geronimoge[/MENTION]. I've found no other camera app which comes close to acceptable when I'm not using Samsung's proprietary software. The OneUI camera, actually, OneUI as a whole, is quite a dream to use, when compared to their older TW OS's. Trouble is, I really much more enjoy an un-skinned Android experience. iDan's G-Cam ports are miles above and beyond any other third-party camera apps, in terms of quality.

Snap Camera, a superb paid app I own(not the LOS Snap camera) comes quite close, and has almost infinite options and customisation features but it still isn't as crystal-clear in picture/video quality as a Google Camera port.

Cheers!

EDIT: The excellent Snap Camera, which I've used for years(also comes in a trial version):

https://play.google.com/store/apps/details?id=com.marginz.snap
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
* Edit: Post re-added below, since both XDA app and Web make it impossible to modify attachments.
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
* Outdoor natural light, back to back quick shots. G-Cam is significantly better in quality, also with much lower file-size than Snap.
[Samsung Galaxy S9 & S9+ Cross Device Development] D4ND310:
* EDITED as noted above:

Kind of off topic but could help in aiding choice of camera(as others have already posted before here) when choosing to install a new custom ROM on your S9/+

1: Snap third-party(pretty much equivalent to the stock LOS Cam mod included in this ROM).

2: G-Cam(version mentioned above).

* Full view is recommended to see the difference in detail clarity(and my apologies for the low-light, indoor shots).

* Oops and, apparently, my device believes I was horizontal using Snap camera. I wasn't. However, the difference is quite clear in these very quick snaps, grainy and rough for Snap, much smoother and far less grain with G-Cam.

I have already unistalled LOS Camera and can't supply a test shot but the quality is equivalent to any third-party camera you might install.

Overview: Use G-Cam port by iDan for any S9/+ custom rom/Use OneUI Samsung camera for stock ROMs.

OneUI Camera is the best on your stock S9/+, obviously.

G-Cam is close to it but not quite there. It's really a balance of quality over comfort.

I say, use whatever firmware/OS you are most comfortable with, if it's custom build ROM, install G-Cam by iDan.

If stock, you literally *can't* get better than Samsung Camera.

Fin.
[Samsung Galaxy S9 & S9+ Cross Device Development] ColdIllyrian:
If you have installed stock gapps or big gapps it makes it lag if you install pico gapps no lag though if you havent done that don't know sorry
[Samsung Galaxy S9 & S9+ Cross Device Development] Aquajd:
Hi firstly - a most excellent rom and thank you for bringing it to my s9+

Initially the rom was very smooth - I've installed gapps and rooted with magisk. My one concern is that SElinux is disabled and that even though rooted the the root is not enabled under the trust section. I have followed your instructions for installing to the letter and all appeared fine. Is this normal or has something been overlooked?

Thanks in advance

J
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
I've got Magisk installed, it prompts for root and such as expected, but in the Android settings my Root is set as Disabled. That's fine.

But yea, I do see SELinux is disabled, and haven't been able to enable it.
[Samsung Galaxy S9 & S9+ Cross Device Development] odysseus84:
root is only set to "enabled" if you use the official su addon from the LOS download page.

You can enable SELinux with a magisk script, but it breaks stuff like Bluetooth.
[Samsung Galaxy S9 & S9+ Cross Device Development] Zwulf:
SELinux works with Endurance kernel. Flash kernel, Magisk and after reboot you can set SELinux to enabled (e.g. with Kernel Adiutor in Misc section).
[Samsung Galaxy S9 & S9+ Cross Device Development] Drizzt321:
I also had trouble earlier with encrypting my data. I plugged it in, set it to start encrypting over night but when I woke up in the morning it would boot to the unlock pattern, I'd put the pattern in, it'd sit there for a bit, and then restart back up to TWRP. Had to wipe my user data, which included me not having it encrypted.

Thoughts?
[Samsung Galaxy S9 & S9+ Cross Device Development] zzattack:
Nice ROM. Is it possible to remap bixby button with this? Seems bixby remapper in magisk and bxactions do nothing for me.
[Samsung Galaxy S9 & S9+ Cross Device Development] Sage:
you could try this:

https://play.google.com/store/apps/details?id=flar2.homebutton&hl=en
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
There's a way to do it manually. If you go to

/system/usr/keylayout/gpio_keys.kl and edit key 703 to one of the following then it should work. I use POWER and I know 100% it works.

key 703 BACK

key 703 CALENDAR

key 703 CALL

key 703 CONTACTS

key 703 HOME

key 703 EXPLORER

key 703 MENU

key 703 MESSAGE

key 703 MEDIA_NEXT

key 703 MEDIA_PLAY_PAUSE

key 703 MEDIA_PREVIOUS

key 703 POWER

key 703 QPANEL_ON_OFF

key 703 SYSRQ

key 703 SEARCH

key 703 SLEEP

key 703 WAKEUP

key 703 APP_SWITCH

key 703 VOICE_ASSIST

For OneUI users it's under

/system/usr/keylayout/generic.kl
[Samsung Galaxy S9 & S9+ Cross Device Development] odysseus84:
Under System -> buttons is a basic button maper function
[Samsung Galaxy S9 & S9+ Cross Device Development] zohaibshafijutt:
I have tried several apps including ur method but it does not work for voice assistant for one press whereas it is working fine for long press and double press (voice assistant does not work on double press and long press). Other functions and tasks work
[Samsung Galaxy S9 & S9+ Cross Device Development] madbehaviorus:
I wonder who is the source of the "android_device_samsung_universal9810-common" ? There isn't in the github repository? Is the repo marked as private?
[Samsung Galaxy S9 & S9+ Cross Device Development] rupert3k:
Root & Kernel Query

Very grateful to Synt4x.93.

wishing to avoid KGG Prenormal RMM state whenever I flash this rom I also flashed RMM_Bypass_v3_corsicanu.zip.

Also because no-verity-opt-encrypt-samsung-1.0 is referenced in a Root S9 guide I read I tried installing the following zips in TWRP to no avail:

lineage-16.0-20190717-UNOFFICIAL-starlte.zip

open_gapps-arm64-9.0-pico-20190810.zip

no-verity-opt-encrypt-samsung-1.0.zip

RMM_Bypass_v3_corsicanu.zip

Magisk-v19.3.zip

ElementalX-S9-2.09.zip

After failing I eventually managed to load it by simply flashing:

lineage-16.0-20190717-UNOFFICIAL-starlte.zip

open_gapps-arm64-9.0-pico-20190810.zip

RMM_Bypass_v3_corsicanu.zip

The rom is running beautifully, I am using the Pixel launcher.

My only annoyance is "Hey Google" assistant doesn't voice activate.

Anxious to get rooted with ElementalX but everytime I try flashing ElementalX it fails so I have to start again.

Can anyone advice me on the best way to get this excellent rom rooted with ElementalX, should I use SuperSU or Magisk?

Should I just try:

ElementalX-S9-2.09.zip

Magisk-v19.3.zip

RMM_Bypass_v3_corsicanu.zip

?

Regards rupert3k
[Samsung Galaxy S9 & S9+ Cross Device Development] bdwilk:
1) you don't need RMM Zip.

2) EX doesn't have an LOS kernel.

Just use stock kernel or Endurance or White Wolf. Use the AOSP or LOS versions of those kernels.

ROM

GApps

Kernel

Magisk
[Samsung Galaxy S9 & S9+ Cross Device Development] CM@S5:
Problems with WiFi Hotspot function

My old LineageOS 15.x had no problems with the wifi hotspot, but this one.

The connection is made with pwd and sid, (and wrong pwd is recognized) and registered at the phone, but i.e. the browser does not work.

Any ideas?

Anyway, great work! Hope it will be available at the official port soon for all the s9s.

EDIT:

The cause is the misconfigured APN for Deutsche Telekom within the german LineageOS 16 distribution. To be more precise to my original message: Some URLs don't work, some URLs do.

Using the pre-configured APN alternative called Lebara (a sub provider of Deutsche Telekom) there are no problems, also if switched to the mixed protocol option v4/v6.

I tried to change different parameters, but i did not found the real reason of the misbehavior.
[Samsung Galaxy S9 & S9+ Cross Device Development] jujehawkar:
how to download CSG8vendor.img??

please help me
[Samsung Galaxy S9 & S9+ Cross Device Development] ejdan:
This rom requires CSF2. Why do you need CSG8?
[Samsung Galaxy S9 & S9+ Cross Device Development] EagleSoldier:
CSG8 works too
[Samsung Galaxy S9 & S9+ Cross Device Development] mrmodzix:
How are you using the pixel launcher? Thought it didn't work on this build
[Samsung Galaxy S9 & S9+ Cross Device Development] rupert3k:
It worked when I installed pico gapps but ever since I started using stock gapps it’s crashing for me too.

Wish I could get Hey Google to respond from sleep.
[Samsung Galaxy S9 & S9+ Cross Device Development] afcaajax:
I think you need the Google Assist app mate. Because i can do this with the default launcher