[ROM][S9+/S9][UNOFFICIAL][LineageOS 18.1][21-03-2021]
- Thread starter Synt4x.93
- Start date
For the time being I went back to Noble ROM.
But I made a backup of LineageOS.
Restoring the backup gives me the same problem as with Noble ROM.
I first need to do an new installation of Lineage before I can restore the backup.
Is there no possibility to restore the backup without first instaling the rom?
But I made a backup of LineageOS.
Restoring the backup gives me the same problem as with Noble ROM.
I first need to do an new installation of Lineage before I can restore the backup.
Is there no possibility to restore the backup without first instaling the rom?
What kind of backup you did? If you make android backup it's like you freeze the entire system and files at the state of the time you did it.
If you backup with Google you can try to restore the backup back, but I always recommend to make a clean installation.
Also if time is needed, I always wipe everything, except internal memory, vendor and some others.
So just install new ROM, after that gapps fixed I linked, then MagiskHide activating the hiding function and to rename it if necessary, plus the safety net fix it necessary. But just to avoid conflicts I choose to remove everything and start from fresh.
any working camera ? zgcam is crashing for me .. anyone knows how to fix it ? i am running the latest update , latest gaps, magisk, open gapps "nano"
edit: open camera is crashing too ... i have removed the zgcam and installed oppen camera, but i get an error message that something is using the camera ... any ideas what can I do to fix this ?
edit: open camera is crashing too ... i have removed the zgcam and installed oppen camera, but i get an error message that something is using the camera ... any ideas what can I do to fix this ?
Last edited:
hi mate, can you give me stepp by step guide how to fix my camera because when i installed ZGcam from KoopahtManiac it simply crashes, how did you make it work ? Where do i get latest libexynoscamera3.so and where to install it .?
first you install zgcam and then libexynoscamera3.so ?
I will be very thankfull if you help me
If I remember well I used the libexynoscamera3.so from Android Pie (9) stock rom. With that I was able to use the front camera.hi mate, can you give me stepp by step guide how to fix my camera because when i installed ZGcam from KoopahtManiac it simply crashes, how did you make it work ? Where do i get latest libexynoscamera3.so and where to install it .?
first you install zgcam and then libexynoscamera3.so ?
I will be very thankfull if you help me
But in the telegram group found on KoopahtManiac you can find some instructions libs and xml's too.
Bugs I noticed in this ROM. I would be grateful if you put them in the topic header so that people downloading this ROM know what problems they will face:
1. When calling, on the second SIM card, I do not hear any sounds from the interlocutor and he does not hear me.
2. The NFC antenna does not work.
3. It is not possible to select the normal battery charging mode. There is only fast charging. Fast is harmful to the battery and the cooler on the charger is always on when fast charging. And on slow charging, the cooler does not turn on.
4. If there is a Pincode on the SIM cards, then after rebooting the phone and entering the Pincode of the first card, everything goes fine (instantly), and after entering the Pincode of the second card, it takes much longer to unlock it, about 5 seconds.
5. Wi-Fi direct does not work if GPS is not enabled. This bug is minor, but it causes inconvenience to turn on the GPS every time before turning on Direct.
6. The strength of the vibration response is not configured in the settings. Rather, there are 4 vibration settings, but they do not change the actual vibration level and 3 of them work as one (except for one option - off). This is provided that there is a standard kernel from this Lineage 18.1 firmware. And if you install the kernel version 6.5 from Klabit, then the vibration settings become relevant and at all 4 levels, the vibration is different.
7. there is no EDGE petal. This is such a thing, pulling which opens additional functions on the screen such as quick contacts, clipboard, compass, and more.
1. When calling, on the second SIM card, I do not hear any sounds from the interlocutor and he does not hear me.
2. The NFC antenna does not work.
3. It is not possible to select the normal battery charging mode. There is only fast charging. Fast is harmful to the battery and the cooler on the charger is always on when fast charging. And on slow charging, the cooler does not turn on.
4. If there is a Pincode on the SIM cards, then after rebooting the phone and entering the Pincode of the first card, everything goes fine (instantly), and after entering the Pincode of the second card, it takes much longer to unlock it, about 5 seconds.
5. Wi-Fi direct does not work if GPS is not enabled. This bug is minor, but it causes inconvenience to turn on the GPS every time before turning on Direct.
6. The strength of the vibration response is not configured in the settings. Rather, there are 4 vibration settings, but they do not change the actual vibration level and 3 of them work as one (except for one option - off). This is provided that there is a standard kernel from this Lineage 18.1 firmware. And if you install the kernel version 6.5 from Klabit, then the vibration settings become relevant and at all 4 levels, the vibration is different.
7. there is no EDGE petal. This is such a thing, pulling which opens additional functions on the screen such as quick contacts, clipboard, compass, and more.
Also, another bug was found:
8. When connecting a smartphone to a PC on a wire, the phone is recognized by the PC, but as the drive is not visible and, therefore, you can not see the contents of the phone, internal memory and flash drives on the computer.
8. When connecting a smartphone to a PC on a wire, the phone is recognized by the PC, but as the drive is not visible and, therefore, you can not see the contents of the phone, internal memory and flash drives on the computer.
Last edited:
Another bug:
9. Not a single notification is indicated by a light diode. that is, if there are missed calls, unread SMS and other notifications, then the indicator light does not blink and does not light. those. you won't see it flashing when you have an unread notification. this indicator is blue only when the smartphone is rebooted. how could it be possible to roll out such a raw, crooked and unfinished firmware for users to see? now I understand why the developer did not indicate all the bugs of the firmware, because if he had, no one would have downloaded it. Pizdec rezrab krivorukiy!
9. Not a single notification is indicated by a light diode. that is, if there are missed calls, unread SMS and other notifications, then the indicator light does not blink and does not light. those. you won't see it flashing when you have an unread notification. this indicator is blue only when the smartphone is rebooted. how could it be possible to roll out such a raw, crooked and unfinished firmware for users to see? now I understand why the developer did not indicate all the bugs of the firmware, because if he had, no one would have downloaded it. Pizdec rezrab krivorukiy!
These are your problems on your single install, they all work fine for many. Anyway this ROM has been superceded. The great work here on this ROM by synt4x93 has continued with LOS with kernel updates, Gapps spoofing + apps too. Try that one, but install properly from a clean wipe first. NFC, diode light, vibration, fast charging, wifi/gps etc etc all work on this ROM for many users until the last version in March 21, you really think the whole community was keeping your dramas on this ROM a secret all this time ??? 
Last edited:
I have been experimenting with different firmware on this smartphone for 2 months. lineage 18.1 I installed 3 times. with different cores, wipes and over pure smart and over stock firmware. the result is the same. I was flashing exactly 9650 with a 9th bootloader. Unfortunately, I don't have another phone like this. Therefore, I can’t say only on my device such problems or on others too. But when I install a stock firmware for myself, everything works perfectly: both SIM cards and sensors and everything else.Это ваши проблемы с одной установкой, у многих они работают нормально. В любом случае это ПЗУ было заменено. Большая работа synt4x93 над этим ПЗУ была продолжена с LOS с обновлениями ядра, спуфингом Gapps и приложениями. Попробуйте это, но сначала установите правильно с чистого вайпа. NFC, диодная подсветка, вибрация, быстрая зарядка, Wi-Fi/GPS и т. д. и т. д. — все это работает на этом ПЗУ для многих пользователей до последней версии от 21 марта, вы действительно думаете, что все сообщество все это время держало в секрете ваши драмы на этом ПЗУ? ??
I flashed it and now it says 'Encryption unsuccessfull' and prompts to perform a factory reset. I don't have any data on the phone so it in itself wouldn't be a problem, however after tapping on 'erase all data' it's just stuck on a loading screen. I can't enter neither recovery mode nor download mode to flash the stock firmware. Is it permanently bricked?
Phone: Samsung Galaxy S9
Edit: Solved, managed to boot into download mode somehow. I probably forgot to wipe data before flashing
Phone: Samsung Galaxy S9
Edit: Solved, managed to boot into download mode somehow. I probably forgot to wipe data before flashing
Last edited:
Hi
first of all - thank you very much for this rom. It really is amazing, its a pity LOS doesn't support it officially anymore.
I wanted to ask where I can find the changelog. I updated from the november-update today and showing the changelog with the built-in-updater doest work...
Kind regards
D4foasta
first of all - thank you very much for this rom. It really is amazing, its a pity LOS doesn't support it officially anymore.
I wanted to ask where I can find the changelog. I updated from the november-update today and showing the changelog with the built-in-updater doest work...
Kind regards
D4foasta
Great!!
Does this support OpenCL?
I want to test Deep learning performance with tensorflow lite OpenCL version
Does this support OpenCL?
I want to test Deep learning performance with tensorflow lite OpenCL version
If I flash this Lineageos 18.1 on my starlte would it be possible to enable signature spoofing to use MicroG?
So how would I do that?
So how would I do that?
Only to get sure, will this ROM still updated or is it already end of life? The last OTA update ist from 21-03-2021
Furthermore, I am currently on the latest official S9 linage OS 17.1 (QQ3A.200805.001), do I have to go back to the stock rom as well or could I update from this without data loss? It's really annoying to shovel all the data from phone to pc and back.
Furthermore, I am currently on the latest official S9 linage OS 17.1 (QQ3A.200805.001), do I have to go back to the stock rom as well or could I update from this without data loss? It's really annoying to shovel all the data from phone to pc and back.
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
45
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 "[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
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://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
In open source nobody owes anything to anyone. People are working in their free time. Which is kind of obvious.
