Use Frija to download Samsung stock ROM. Unpack it and flash CP part (which contains modem) via Odin.
[ROM][S9+/S9][UNOFFICIAL][LineageOS 18.1][21-03-2021]
- Thread starter Synt4x.93
- Start date
gps.xml != gps.conf
There's nothing wrong with the gps.xml file in vendor, but you need a separate (and very different!) gps.conf to find the other satellite clusters. (Yes, you will get an occasional GLONASS or BeiDou without it - but I see 32+ satellites for my fix, which I suspect is a lot more than what you're seeing ...)
The GPS works tolerably without the conf file, but it's so much faster to get a cold fix (and should be more accurate in suboptimal conditions) with it.
Just have flashed my Galaxy S9+ Duos but I had no success although I strictly followed the installation procedure given here: https://wiki.lineageos.org/devices/star2lte/install
First I made sure to have an exynox CPU and that Android 10 is installed and downloading the correct recovery image. Then I have installed adb following the advice given here: https://wiki.lineageos.org/adb_fastboot_guide.html
and checked it via "adb shell". It was answered by "daemon started at tcp:5037"
My Heimdall version is that from the link within the LineageOS guide.
Then I flashed the phone via heimdall as recommended, using the recovery image:
lineage-18.1-20210321-UNOFFICIAL-star2lte-recovery.img
It was loaded very quick to the phone completely (loading bar).
But even after 10 minutes waiting, I got no display report, that the flashing process is finished. Instead, the display showed the following lines (only the first five lines):
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G965F
CURRENT BINARY: Custom (0x4)
KG STATE: Checking
....,
After rebooting, I got a distorted display and with the help of a magnifying glass I could read the message, that the software did not fit the check. I assume, that Samsung Knox did prevent to start up the phone with LineageOS. But I have bought the phone as a used device and so we don't have the 7 days limit for new devices.
After about 10 minutes, the phone rebooted automatically in the Samsung original software. I am lucky, that I had not bricked the phone.
But how should I proceed now, to flash LOS 18 on it? And I fear now, that I am next time not so lucky and really would brick my phone!
Any idea what I did wrong?
First I made sure to have an exynox CPU and that Android 10 is installed and downloading the correct recovery image. Then I have installed adb following the advice given here: https://wiki.lineageos.org/adb_fastboot_guide.html
and checked it via "adb shell". It was answered by "daemon started at tcp:5037"
My Heimdall version is that from the link within the LineageOS guide.
Then I flashed the phone via heimdall as recommended, using the recovery image:
lineage-18.1-20210321-UNOFFICIAL-star2lte-recovery.img
It was loaded very quick to the phone completely (loading bar).
But even after 10 minutes waiting, I got no display report, that the flashing process is finished. Instead, the display showed the following lines (only the first five lines):
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G965F
CURRENT BINARY: Custom (0x4)
KG STATE: Checking
....,
After rebooting, I got a distorted display and with the help of a magnifying glass I could read the message, that the software did not fit the check. I assume, that Samsung Knox did prevent to start up the phone with LineageOS. But I have bought the phone as a used device and so we don't have the 7 days limit for new devices.
After about 10 minutes, the phone rebooted automatically in the Samsung original software. I am lucky, that I had not bricked the phone.
But how should I proceed now, to flash LOS 18 on it? And I fear now, that I am next time not so lucky and really would brick my phone!
Any idea what I did wrong?
Last edited:
Sorry to say, that my S9+ is broken in a strange way: While I tried to set it up with the original Samsung stock firmware, which seemed to work at first, I got a message on the display, that Samsung wanted to install an update, dated from April 1st.
I made the mistake, to agree to that update. After it has been installed, the phone rebooted automatically and it showed up a very distorted display with some dim green lines at the top of the display. No error messages did show up.
While I was writing this text, suddenly the phone rebooted again and showed a regular screen from stock ROM and showing a message, that the apps would be optimized. The progress bar was creeping slowly. When it finished at 100%, the regular main screen showed up and now the phone seems to work regularily.
But I am sure now, that I will run into problems again, as soon as I reboot again. And this probably will prevent me from further trying to flash my S9+ with LineageOS.
What should I do????
I made the mistake, to agree to that update. After it has been installed, the phone rebooted automatically and it showed up a very distorted display with some dim green lines at the top of the display. No error messages did show up.
While I was writing this text, suddenly the phone rebooted again and showed a regular screen from stock ROM and showing a message, that the apps would be optimized. The progress bar was creeping slowly. When it finished at 100%, the regular main screen showed up and now the phone seems to work regularily.
But I am sure now, that I will run into problems again, as soon as I reboot again. And this probably will prevent me from further trying to flash my S9+ with LineageOS.
What should I do????
Is it possible to activate signature spoofing to use microG on this version of lineage 18.1? Sorry if question has been asked already!
Concerning my two requests here:
I have found the reason for my problems: I thought, my S9+ would have been rooted, because OEM-unlock would tell me. Instead it is still unrooted, because VaultKeeper and Knox are preventing it.
I have found some advice here:
www.droidwin.com
But they tell, that you have to enter the DownloadMode by pressing volume-down + power + bixby. And then you get a screen, offering three options. The second one should be available by pressing the volume up button some seconds in order to start the root process.
But on my screen, I do not have this option! And I do not know, how this option can be gone. You can see it on my two Screenshots. On the second screen, it is remarkable, that in the fifth line is showing up: KG STATE : Checking
And Warranty Void: 1 (0x0000) is set. In spite, the Current Binary is Samsung Official.
So what can I do, to get rid of the problems and get real root? I am on Linux and don't have access to Windows / Odin.
I have found the reason for my problems: I thought, my S9+ would have been rooted, because OEM-unlock would tell me. Instead it is still unrooted, because VaultKeeper and Knox are preventing it.
I have found some advice here:
How to Unlock Bootloader on any Samsung Device [New VaultKeeper Method]
In this guide, we will sho you how to unlock the bootloader on any Samsung device, keeping in mind the new VaultKeeper mechanism.
But they tell, that you have to enter the DownloadMode by pressing volume-down + power + bixby. And then you get a screen, offering three options. The second one should be available by pressing the volume up button some seconds in order to start the root process.
But on my screen, I do not have this option! And I do not know, how this option can be gone. You can see it on my two Screenshots. On the second screen, it is remarkable, that in the fifth line is showing up: KG STATE : Checking
And Warranty Void: 1 (0x0000) is set. In spite, the Current Binary is Samsung Official.
So what can I do, to get rid of the problems and get real root? I am on Linux and don't have access to Windows / Odin.
Attachments
This rom is amazing, nice to look at and with good performance. I especially like the integration of seedvault - thats exactly what i missed since going Android Open Source...
Thank you.
PS: not sure yet who is the culprit (rom or vlc), but when listening to audiobooks (single big audio files), sometimes it shows my position at something quite ahead of the max duration of the file.... happens most of the time after i pause and resume playback. s/o with the same phenomenon?
Thank you.
PS: not sure yet who is the culprit (rom or vlc), but when listening to audiobooks (single big audio files), sometimes it shows my position at something quite ahead of the max duration of the file.... happens most of the time after i pause and resume playback. s/o with the same phenomenon?
Last edited:
With the newes FakeGApps Version ( https://github.com/whew-inc/FakeGApps/releases ) for the Xposed Framework signature spoofing with MicroG works on this Rom
Last edited:
Hello. Everything went smoothly with the installation of my Samsung S9 plus (SM-G965F). The phone works quickly and smoothly. So far, I haven't noticed any problems, except that Wi-Fi doesn't sleep when the phone is in deep sleep mode. The battery has a good life, but I believe it will improve even more if Wi-Fi falls asleep. Does anyone know how to solve this problem?
Bertonumber1
Senior Member
You should be able to do this in build.prop
Edit the text file with any root explorer with root and copy/paste this :
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
After the last line in the build.prop.
Save and exit then change the file permission (in properties) to :
rw r- r-
Reboot
If someone with more knowledge than me could advise.
I have all the build.prop tweaks in my s9+ G965F android 10 stock firmware rooted with locked bootloader and magisk 22.1.
Obviously what works for some doesn't always for others so be careful.
Regards
Interesting.
I noticed that the phone is rebooting, if connected to a device with USB and I switch the connection type from 'charging' to 'file transfer'.
If I switch from 'charging' to 'Midi' to 'file transfer' it's working without reboot.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
46
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-20216
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 "you@example.com" 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://xdaforums.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/emailAddress=android@android.com' 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
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 thanks4
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#L2435th 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
There is a build with July security update and an upstreamed kernel here: https://xdaforums.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
In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.
