Is a chance, that someone with Android knowledge will be able to step up and at least bring 15.1 back? I'd slowly considering moving to some different supported phone until I get my Librem 5 
[ROM][8.1.0][OFFICIAL][WEEKLY] LineageOS 15.1 for S9 and S9+ (Exynos)
- Thread starter jesec
- Start date
Stuck on the boot screen is not only the vendor issue
Is the issue in correct vendor? After installing my phone stuck on the boot screen.
Seems to be NOT as far as I tried the following vendor images: ARAN, BRE5, BRH4, BSB1 and also VENDOR-27_ARI9.
After flashing of each vendor image (no matter via heimdall or TWRP) I installed each of the following Lineage zips made by @jesec
lineage-15.1-20180424-UNOFFICIAL-starlte.zip
lineage-15.1-20180429-UNOFFICIAL-starlte.zip
lineage-15.1-20180508-nightly-starlte-patched.zip
and also
lineage-15.1-20190507-UNOFFICIAL-starlte.zip (by @AzzyC, https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t3927314)
I thought that maybe I have broken hw or miss something in installation process, TWRP initializaton or whatever, however flashing Pixel Experience by @Rainbow_Dash (https://forum.xda-developers.com/ga...development/rom-pixel-experience-8-1-t3834249) in the same conditions was successful, phone booted normally!
What thing could I miss?
Phone: SM-G960F
I tried to start from different stock firmware:
G960FPUU2BRH4
G960FXXU1ARAN
G960FXXU1BRE5
G960FXXU2BRGA
G960FXXU2BRJ
(Region SEK / SER, Ukraine / Russia)
I also built own fw. No success, after boot screen.
BTW, in releasetools.py I found the check:
ifelse(file_getprop("/vendor/build.prop","ro.vendor.build.date.utc") != "1536890700"
1536890700 refers to 09/14/2018
And the one the single vendor image with this build date is VENDOR-27_ARI9.
No stock vendors with this date!
Is the issue in correct vendor? After installing my phone stuck on the boot screen.
Seems to be NOT as far as I tried the following vendor images: ARAN, BRE5, BRH4, BSB1 and also VENDOR-27_ARI9.
After flashing of each vendor image (no matter via heimdall or TWRP) I installed each of the following Lineage zips made by @jesec
lineage-15.1-20180424-UNOFFICIAL-starlte.zip
lineage-15.1-20180429-UNOFFICIAL-starlte.zip
lineage-15.1-20180508-nightly-starlte-patched.zip
and also
lineage-15.1-20190507-UNOFFICIAL-starlte.zip (by @AzzyC, https://forum.xda-developers.com/ga...-s9--s9-cross-device-development/rom-t3927314)
I thought that maybe I have broken hw or miss something in installation process, TWRP initializaton or whatever, however flashing Pixel Experience by @Rainbow_Dash (https://forum.xda-developers.com/ga...development/rom-pixel-experience-8-1-t3834249) in the same conditions was successful, phone booted normally!
What thing could I miss?
Phone: SM-G960F
I tried to start from different stock firmware:
G960FPUU2BRH4
G960FXXU1ARAN
G960FXXU1BRE5
G960FXXU2BRGA
G960FXXU2BRJ
(Region SEK / SER, Ukraine / Russia)
I also built own fw. No success, after boot screen.
BTW, in releasetools.py I found the check:
ifelse(file_getprop("/vendor/build.prop","ro.vendor.build.date.utc") != "1536890700"
1536890700 refers to 09/14/2018
And the one the single vendor image with this build date is VENDOR-27_ARI9.
No stock vendors with this date!
This combination (in this order) works perfect for me:
- no-verity-opt-encrypt-samsung-1.0.zip
- Flashable_G96XF_Firmware_TWRP_BRL3_r19.zip
- VENDOR-27_ARI9.zip
- lineage-15.1-20190517-nightly-star2lte-signed.zip
So, I
- flashed with BRL3 (official G960FXXS2BRL3, all partitions) with heimdall
- flashed twrp-3.3.1-0-starlte.img recovery with heimdall and initialized according to https://forum.xda-developers.com/showpost.php?p=75893923&postcount=3
- flashed VENDOR-27_ARI9.zip using TWRP
- built own LineageOS 15.1 installation package according to https://wiki.lineageos.org/devices/starlte/build
Step of extracting proprietary blobs I changed to replacing content of android/lineage/vendor/samsung/universal9810-common by @jesec 's repo https://github.com/jesec/proprietary_vendor_samsung/tree/lineage-15.1/universal9810-common - flashed my LineageOS 15.1 .zip using TWRP
and stuck on the boot screen!
@jesec ,
@AzzyC ,
@SoLdieR9312,
anybody please help!!!
RF Cal: 20171122
HW Rev: PV 0.801
(Exynos)
Last edited:
Could anyone share latest official LineageOS 15.1 built for Samsung S9? I use 17.1 now, but have troubling bug (no sound over Bluetooth during calls) and want to try earlier LOS version.
Unfortunately can't find any working link for it (and most links points to now-deleted page at lineageos.org)
Unfortunately can't find any working link for it (and most links points to now-deleted page at lineageos.org)
https://drive.google.com/file/d/1KhZ_zTIuHJQ5fC5o0-ehdcTt6OOTDEjw
Sent from my SM-G965F using XDA Labs
Big thanks, but unfortunately it's wrong image. It's for Samsung S9+ (star2lte) and mine is S9 (starlte).
Thanks.
Also Telegram user Ivan Catalin posted https://mega.nz/folder/JrZy3IIC#ALKeMjEqP08Wtyk7tszV1w (the same link) in Samsung S9 telegram chat.
I've downloaded it and mirrored on my homeserver (it have slow connection, so use as last measure): https://files.whitefossa.org/Android/Samsung S9 (starlte)/
Hello.
Anyone has/had problems with freezes when you couldn't even restart? Also, sometimes calls are dropping (both SIMs).
Any solution?
// Could it be because I flashed newest Magisk on it?
Anyone has/had problems with freezes when you couldn't even restart? Also, sometimes calls are dropping (both SIMs).
Any solution?
// Could it be because I flashed newest Magisk on it?
Last edited:
There seems to be a problem with the latest build and Magisk. It bootloops when Magisk is enabled.
---------- Post added at 06:03 PM ---------- Previous post was at 05:44 PM ----------
And even greater - after reverting to the previous build it tells me after entering decryption password, that all my data has been broken and I need to wipe it. REALLY GREAT!
---------- Post added at 06:27 PM ---------- Previous post was at 06:03 PM ----------
Question is, can I update to the new release AFTER the full wipe and without encryption? Or is there an issue with Magisk anyways?
---------- Post added at 06:03 PM ---------- Previous post was at 05:44 PM ----------
And even greater - after reverting to the previous build it tells me after entering decryption password, that all my data has been broken and I need to wipe it. REALLY GREAT!
---------- Post added at 06:27 PM ---------- Previous post was at 06:03 PM ----------
Question is, can I update to the new release AFTER the full wipe and without encryption? Or is there an issue with Magisk anyways?
Hi all,
Thank you so much! Sorry if this is a silly question:
- "Samsung Pay is not working": Can I use the NFC to make payments with a virtual card inside my phone? Or is this is still not possible? (if not, any alternatives?)
I'm asking that because I'm planning on buying this phone, mainly because of the NFC payments (so I can leave my wallet home and I can't live without a TOP rom
Many thanks in advance,
Cheers!
Thank you so much! Sorry if this is a silly question:
- "Samsung Pay is not working": Can I use the NFC to make payments with a virtual card inside my phone? Or is this is still not possible? (if not, any alternatives?)
I'm asking that because I'm planning on buying this phone, mainly because of the NFC payments (so I can leave my wallet home
and I can't live without a TOP rom Many thanks in advance,
Cheers!
ROM is 3 years old, search for another ROM.Hi all,
Thank you so much! Sorry if this is a silly question:
- "Samsung Pay is not working": Can I use the NFC to make payments with a virtual card inside my phone? Or is this is still not possible? (if not, any alternatives?)
I'm asking that because I'm planning on buying this phone, mainly because of the NFC payments (so I can leave my wallet home
Many thanks in advance,
Cheers!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
81
Note: This is not a ROM based on the ROM shipped with your device. Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Features Overview:
https://www.xda-developers.com/lineageos-15-feature-list-overview-screenshots-video/
Screenshots:
View attachment 4491847View attachment 4491848View attachment 4491849
Device Info:
- Galaxy S9 (Exynos): https://wiki.lineageos.org/devices/starlte
- Galaxy S9+ (Exynos): https://wiki.lineageos.org/devices/star2lte
What's working:
- This build is an official LineageOS build. Compliance with our device support requirements is enforced and guaranteed. That means including but not limited to these hardwares will work:
- Wi-Fi
- Bluetooth
- Mobile Network (Calling, Data, etc.)
- Audio
- USB
- GPS
- Camera
- Fingerprint Sensor
- NFC
- Etc. Check device support requirements for more.
What's not working:
- Applicable exceptions granted in device support requirements.
- Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. We may have our own implementation to similar functions, though.
- Iris sensor does not work because AOSP upstream does not support that yet.
- IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Instructions:
- Make sure TWRP has been installed and functional.
- Download the latest build (and optionally gapps).
- Reboot to recovery
- Wipe data and cache (required if you switch from other ROMs)
- Flash the latest build (and gapps)
- Reboot
If you upgrade manually from older official releases to newer releases, you don't need to wipe your data or reflash gapps.
Downloads:
- Galaxy S9 Exynos (G960F/FDS/N): https://download.lineageos.org/starlte
- Galaxy S9+ Exynos (G965F/FDS/N): https://download.lineageos.org/star2lte
- Root addon: https://download.lineageos.org/extras
- Google Apps: https://wiki.lineageos.org/gapps.html
Reporting Bugs:
- https://wiki.lineageos.org/bugreport-howto.html
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /proc/avc_msg.
Please use LineageOS BUG tracker to report BUGs. BUGs reported in the thread could be ignored due to large number of posts.
Channel and Group:
LineageOS Channel (News and Updates):
https://t.me/lineageos_star
AOSP-like ROMs (not limited to LineageOS) Group (Discussion, Quick Tech Support and Early Testing):
https://t.me/joinchat/DTrGs0ygFKxHhc3bb11YKw
XDA:DevDB Information
LineageOS for Galaxy S9 and S9+, ROM for the Samsung Galaxy S9
Contributors
jesec
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2018-04-24
Last Updated 2018-05-0526Changelog:
This post only includes important device-specific changes. It does NOT mean the LineageOS is not updated if this post is not updated as we frequently makes platform-wide changes which benefit all devices (not limited to this one). Check https://download.lineageos.org/ for global LineageOS changes.
For details (sources) of device-specific changes, watch these repos:
https://github.com/LineageOS/android_device_samsung_star-common
https://github.com/LineageOS/android_device_samsung_star2lte
https://github.com/LineageOS/android_device_samsung_starlte
https://github.com/LineageOS/android_kernel_samsung_universal9810
and/or follow me: https://github.com/jesec
May 15th, 2018:
- Use Clang to compile kernel
- Update kernel to Linux 4.9.99
- Other optimizations for performance and battery life
May 7th, 2018:
- Support stereo audio for dual speakers
- Support haptic engine for vibration
- Allow to use auto brightness while dozing (AOD, Ambient Display)
- Add an option to invert navigation bar layout
You can find the toggle at Settings -> System -> Buttons -> Buttons and layout.
Samsung navbar layout is no longer default. - Enable charging LED
- Fix USB accessory mode (Android Auto, etc)
- Boost I/O performance
- Allow device to enter deep sleep when AOD is on or when proximity sensor is blocked (eg. in pocket)
- Decrease booting time
- Update kernel to Linux 4.9.98
- Other optimizations for performance and stability
May 1st, 2018:
- Initial official LineageOS build
24Changelog - May 7th, 2018:
- Support stereo audio for dual speakers
- Support haptic engine for vibration
- Allow to use auto brightness while dozing (AOD, Ambient Display)
- Add an option to invert navigation bar layout
You can find the toggle at Settings -> System -> Buttons -> Buttons and layout.
Samsung navbar layout is no longer default. - Enable charging LED
- Fix USB accessory mode (Android Auto, etc)
- Boost I/O performance
- Allow device to enter deep sleep when AOD is on or when proximity sensor is blocked (eg. in pocket)
- Decrease booting time
- Update kernel to Linux 4.9.98
- Other optimizations for performance and stability
If you upgrade manually from older official releases to newer releases, you don't need to wipe your data or reflash gapps.17Okay I just started recreating the device tree based on newer guidelines from LineageOS. I will also include different cherry picks that haven't been implemented for the past inactive months of the developer and build the HALs directly from hardware/samsung instead of cloning them locally as every new commit needs to get manually picked which wasn't done too and results in outdated HALs. I will directly create a pie device tree.
It will take some more time and even if I am done it could need even more time to test everything and ensure if it works. :laugh:15Troubleshooting and Frequently Asked Questions:
Critical hardwares (Wi-Fi, BT, Mobile Network, etc.) not working for you:
Developer has thoroughly tested hardwares guaranteed to work by official device support requirements.
It is highly unlikely this ROM itself has BUGs which make these hardwares unavailable to you.
If one or more of these critical hardwares are not working for you, there are several possible causes:
1. Vendor files or firmware on your device have been modified in an unexpected way (other ROMs may do those modifications).
In this case, please use Odin or other means to restore your phone to stock and then flash again.
2. Vendor files or firmware on your device is too old to be compatible.
In this case, please update the vendor files or firmware to the latest version.
3. Vendor files or firmware on your device is too new to be compatible.
LineageOS is actively maintained. It is unlikely that you will be faster than the developer in catching updates but this did happen sometimes. In this case, please file a formal BUG report.
4. There are BUGs with ROM but only limited to some devices.
If you believe this is the case, please file a formal BUG report.
Note that vendor firmware is NOT only the baseband and bootloader.
(Tip: Size of adequate vendor firmware package (contains bootloader, baseband AND vendor) should be at least 200MB.)
You can download vendor firmware package from https://www.androidfilehost.com/?w=files&flid=272468 and then flash it via Odin.
These files only contain necessary vendor firmwares. You won't lose your data when you flash them.
How's the camera?
Well. Given the hardware support is there, the camera is pretty much stable but the image quality can not be guaranteed as OEMs like Samsung use proprietary post processing algorithms which can't be made available to this ROM.
If you only use Camera to scan QR code or you don't really care about quality, you are good to go with built-in Camera.
If you want general good quality images and you don't rely on Samsung's features like 960fps slow-mo, you can try to use Google Camera port which can produce pretty decent images. (Optional: After install GCam, you can disable built-in camera so the system will default to GCam)
If you heavily rely on Samsung's camera features, unfortunately this ROM can not give you those features now and in the future.
Note: LineageOS does not provide technical support to GCam ports. Use at your own risk. DO NOT file BUG report of GCam.
How's the audio?
Speakers, earpieces, wired headphones, in-call audios, Bluetooth audio devices. Pretty much all audio hardware supports are there. But here are several things you should know:
1. Dual speaker is working but not perfect. I mean it is functional but it it not "tuned by AKG". Some apps have compatibility issues with dual speakers. If you met apps which don't use two speakers, a workaround is go to Settings -> Accessibility and then toggle "Mono audio" on and off.
2. Samsung's audio addons like Soundlive or Dolby Atmos are not available and they will not be available in the future.
Why some apps don't scale to full screen?
To ensure maximum compatibility, Google defaults max aspect ratio of old apps to 1.86 (roughly 16:9).
This is more of the app's problem instead of system's. If you found new commercial apps that are not compatible with longer screens, you can go to their Play Store page, write a review to demand support.
If you want to force apps to use full screen aspect ratio, go to Settings -> Display -> Full screen apps and choose which apps you want to use in full screen.
VoLTE, VoWiFi?
NO. It is not available now and it will not be available in the future.
Please do not spam the thread with any VoLTE, VoWiFi related requests/questions.
