• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL] LineageOS for Samsung Galaxy S5 LTE+ (G901F) / LTE-A (G906S/K/L)

Search This thread

Marvin732

Senior Member
Can you elaborate by what you mean by unofficial builds never having gone good for you. Are you experiencing any problems with any unofficial builds that are out there, mine or anyone else's, that you haven't experienced with official builds? Keep in mind that official builds were made from the same sources as unofficial builds, the only difference is the filename and build label.

Lineage didn't discontinue the 16.0 builds just out of nowhere. They needed the infrastructure to run 18.1 builds alongside 17.1. One thing is for certain, official 16.0 will never come back.

On a related matter, if I ever get 18.1 working on kccat6 and lentislte, I will not be submitting them for official support. It's too much of a hassle to go through the process and too much of a time commitment to maintain the sources on a regular basis.
Is there anything I can help to port 18.1 to kccat6?
 
  • Like
Reactions: maanteel

dziugas1959

Member
Jan 22, 2018
22
12
A full reformat would be necessary from 16.0 to 18.1, you can't avoid it. The battery drain bug remains, but since the S5 Plus was affected by it even in its official builds, it's not something I will be working on unless I manage to fix it by accident.
That was what i was afraid of „A full reformat“
I will watch your progress, but since i have important programs i probably won't be jumping to it, when back in the day the move from 14.1 to 15.0 to 16.0 was without data loss (Formating).
 
  • Like
Reactions: maanteel

ripee

Recognized Developer / Recognized Contributor
yeah it was because it stayed on official build i think
You need a specially built experimental build (that's what it's actually called) to migrate between unofficial and official builds. But this is unrelated to being able to dirty flash from one version to the next. While in your case it was possible, it's generally not recommended since any logs generated from dirty upgrades are usually useless for debugging.

It just so happens that dirty upgrading from 17.1 to 18.1 is the easiest and cleanest upgrade to make since Google is running out of backend ideas to make new versions different from old versions, so the upgrade is a smaller jump. As much as I'd like to run 17.1 builds when the time comes, there's no point if I have the apq8084 commit history ready to go straight to 18.1 and fix its bugs directly.

As for your inconvenience in clean flashing the new version, well none of us like to reinstall all our apps and set up our devices from scratch, but dirty flashing many version on top of one another is a recipe for bugginess which can be incorrectly blamed on any bugs that appear in the new version.

Progress on 18.1

The commits keep on coming! There are around 60 more to add, plus a handful of vendor changes, but the small device trees and kernel should be ready.
 
Last edited:
  • Like
Reactions: maanteel
D

Deleted member 11736329

Guest
I'm sorry for posting. I need help with this, I'm really sorry. I've used CyanogenMod/LineageOS for the Samsung Galaxy S2, S4, and S7 as old backup phones. They die, I get another - and I got a Samsung Galaxy S5. I'll give as much detail as possible. The summary is I've never had a problem because instructions are always really good for us non-technical people, unfortunately, for the S5 I'm not being booted into the environment and instead it's stuck on the boot screen.

I hit a problem immediately because:
- The sticker under the battery states SM-G900F
- The internals tell me it is a SM-G901F

What I did without a problem following this thread's instructions after fully charging the phone using the internals SM-G901F (which I can't display now after installing TWRP):
1 Rooted;
2 Installed TWRP 3.2.3.0
3 Installed ROM from front page
4. Installed Gapps
5 Cleared cache and davik
6 Rebooted
7 Stuck at boot screen

I thought hmm interesting, waited a while, but nothing. I repeated steps 3-6. Not working, repeated again and didn't do step 4, 5, in different tests. Same issue.

Wondered whether it was a SM-G900F/901F issue, downloaded the G900F ROM, went to install, and was reported it is it the wrong ROM for the device. This gave me some peace of mind! But it didn't fix the problem.

Tried some other ROMS: older LOS16, RR, and a Pie ROM from https://community.e.foundation/t/unofficial-build-samsung-galaxy-s5-plus-kccat6/8308/8 (1Aug21 release). Same issue.

The above was all on a 64GB Samsung SD. I tried most of the above after removing the SD and using the install ROMS on the device's internal memory.

I also extracted a couple of the LOS into separate directories and packaged them in a .tar for Odin, but Odin crashed with all versions I have.

Did a lot of Googling. This is beyond me.

I've never had to install a bootloader before, so I thought - good opportunity to learn. Unfortunately, the SAM mobile site doesn't have my model/country - Australia
(https://www.sammobile.com/samsung/galaxy-s5-plus/firmware/#SM-G901F).

If it did exist, I don't know how to extract the bootloader to a .tar for flashing.

I got the phone second hand. It's possible somebody has already tinkered with it.

Used Odin version 3.12.13 for flashing, no issues. Have legacy ones from older phones (3.07, 3.09). Haven't had issues before.

Any ideas - in non-technical language? Treat me as if a child wanting to understand :)

Thanks for any help.
 
  • Like
Reactions: maanteel

Marvin732

Senior Member
I'm sorry for posting. I need help with this, I'm really sorry. I've used CyanogenMod/LineageOS for the Samsung Galaxy S2, S4, and S7 as old backup phones. They die, I get another - and I got a Samsung Galaxy S5. I'll give as much detail as possible. The summary is I've never had a problem because instructions are always really good for us non-technical people, unfortunately, for the S5 I'm not being booted into the environment and instead it's stuck on the boot screen.

I hit a problem immediately because:
- The sticker under the battery states SM-G900F
- The internals tell me it is a SM-G901F

What I did without a problem following this thread's instructions after fully charging the phone using the internals SM-G901F (which I can't display now after installing TWRP):
1 Rooted;
2 Installed TWRP 3.2.3.0
3 Installed ROM from front page
4. Installed Gapps
5 Cleared cache and davik
6 Rebooted
7 Stuck at boot screen

I thought hmm interesting, waited a while, but nothing. I repeated steps 3-6. Not working, repeated again and didn't do step 4, 5, in different tests. Same issue.

Wondered whether it was a SM-G900F/901F issue, downloaded the G900F ROM, went to install, and was reported it is it the wrong ROM for the device. This gave me some peace of mind! But it didn't fix the problem.

Tried some other ROMS: older LOS16, RR, and a Pie ROM from https://community.e.foundation/t/unofficial-build-samsung-galaxy-s5-plus-kccat6/8308/8 (1Aug21 release). Same issue.

The above was all on a 64GB Samsung SD. I tried most of the above after removing the SD and using the install ROMS on the device's internal memory.

I also extracted a couple of the LOS into separate directories and packaged them in a .tar for Odin, but Odin crashed with all versions I have.

Did a lot of Googling. This is beyond me.

I've never had to install a bootloader before, so I thought - good opportunity to learn. Unfortunately, the SAM mobile site doesn't have my model/country - Australia
(https://www.sammobile.com/samsung/galaxy-s5-plus/firmware/#SM-G901F).

If it did exist, I don't know how to extract the bootloader to a .tar for flashing.

I got the phone second hand. It's possible somebody has already tinkered with it.

Used Odin version 3.12.13 for flashing, no issues. Have legacy ones from older phones (3.07, 3.09). Haven't had issues before.

Any ideas - in non-technical language? Treat me as if a child wanting to understand :)

Thanks for any help.
You just can use any region firmware, as long as it is g901f, its only the provider rom thats why.
I have used this one

as stated in the first post
"
  • For kccat6, use bootloader CQJ1, CQJ2 or later."
 
  • Like
Reactions: maanteel

ripee

Recognized Developer / Recognized Contributor
I'm sorry for posting. I need help with this, I'm really sorry. I've used CyanogenMod/LineageOS for the Samsung Galaxy S2, S4, and S7 as old backup phones. They die, I get another - and I got a Samsung Galaxy S5. I'll give as much detail as possible. The summary is I've never had a problem because instructions are always really good for us non-technical people, unfortunately, for the S5 I'm not being booted into the environment and instead it's stuck on the boot screen.

I hit a problem immediately because:
- The sticker under the battery states SM-G900F
- The internals tell me it is a SM-G901F

What I did without a problem following this thread's instructions after fully charging the phone using the internals SM-G901F (which I can't display now after installing TWRP):
1 Rooted;
2 Installed TWRP 3.2.3.0
3 Installed ROM from front page
4. Installed Gapps
5 Cleared cache and davik
6 Rebooted
7 Stuck at boot screen

I thought hmm interesting, waited a while, but nothing. I repeated steps 3-6. Not working, repeated again and didn't do step 4, 5, in different tests. Same issue.

Wondered whether it was a SM-G900F/901F issue, downloaded the G900F ROM, went to install, and was reported it is it the wrong ROM for the device. This gave me some peace of mind! But it didn't fix the problem.

Tried some other ROMS: older LOS16, RR, and a Pie ROM from https://community.e.foundation/t/unofficial-build-samsung-galaxy-s5-plus-kccat6/8308/8 (1Aug21 release). Same issue.

The above was all on a 64GB Samsung SD. I tried most of the above after removing the SD and using the install ROMS on the device's internal memory.

I also extracted a couple of the LOS into separate directories and packaged them in a .tar for Odin, but Odin crashed with all versions I have.

Did a lot of Googling. This is beyond me.

I've never had to install a bootloader before, so I thought - good opportunity to learn. Unfortunately, the SAM mobile site doesn't have my model/country - Australia
(https://www.sammobile.com/samsung/galaxy-s5-plus/firmware/#SM-G901F).

If it did exist, I don't know how to extract the bootloader to a .tar for flashing.

I got the phone second hand. It's possible somebody has already tinkered with it.

Used Odin version 3.12.13 for flashing, no issues. Have legacy ones from older phones (3.07, 3.09). Haven't had issues before.

Any ideas - in non-technical language? Treat me as if a child wanting to understand :)

Thanks for any help.
What is your phone's CSC? This is the 3-letter country and carrier code that Samsung invented. For the purpose of simplicity, you can flash the original one based on where your phone was sold.

Better yet, can you post a photo of the sticker in the battery compartment. This will give us some information about what your phone actually is.

Edit: Nevermind, this bit of info narrows it down:
Wondered whether it was a SM-G900F/901F issue, downloaded the G900F ROM, went to install, and was reported it is it the wrong ROM for the device. This gave me some peace of mind! But it didn't fix the problem.

Anyway, flash stock and install the DevCheck app. It will tell us the original CSC of your phone. I will attach a .tar file with the properly matched bootloader and modem for your CSC here.

@Marvin732 , the bootloader listed in the OP is a rough guide and by no means an absolute requirement. If a newer bootloader/modem are available, there's no reason not to flash it.
 
  • Like
Reactions: maanteel
D

Deleted member 11736329

Guest
What is your phone's CSC? This is the 3-letter country and carrier code that Samsung invented. For the purpose of simplicity, you can flash the original one based on where your phone was sold.

Better yet, can you post a photo of the sticker in the battery compartment. This will give us some information about what your phone actually is.

Edit: Nevermind, this bit of info narrows it down:


Anyway, flash stock and install the DevCheck app. It will tell us the original CSC of your phone. I will attach a .tar file with the properly matched bootloader and modem for your CSC here.

@Marvin732 , the bootloader listed in the OP is a rough guide and by no means an absolute requirement. If a newer bootloader/modem are available, there's no reason not to flash it.

Thank you for talking plain English. I'm really not very technical!

- I couldn't download from Sammobile without a subscription so I downloaded stock from the link below, in case anybody has this problem too. I downloaded the Marshmallow version

- Was easy to flash.
- The Devcheck application gives this code:
CSC: DBT

- I've enclosed a picture without the bottom part giving the IMEI. You can see it says SM-G900F and not SM-G901F, which is what I flashed. I don't know anything about this.

Thank you. It's interesting to learn how these things work.

EDIT
====

I thought I'd go through the process again and download the most recent build for this phone, but the LineageOS page does not exist - https://download.lineageos.org/kccat6

EDIT2
=====
Out of interest, I went through the process with the new stock ROM installed after rooting and TWRP, flashed lineage-16.0-20210211-nightly-kccat6-signed and it booted to the environment. Ooh it worked.
 

Attachments

  • GalaxyS5.jpg
    GalaxyS5.jpg
    64.1 KB · Views: 22
Last edited by a moderator:
  • Like
Reactions: maanteel

andreoide

Senior Member
Your phone is G900f the Samsung S5
It is not the S5+ (plus) wich has better hardware and called S901f
So I expect one of these days you run in trouble flashed S901f on a S900f hardware model.
I can't understand how you got this working anyway, but no need answering that question, you have put the wrong ROM on the wrong model now
 
  • Like
Reactions: maanteel

andreoide

Senior Member
So why did he mention having flashed the kccat6 build and it's having booted for him?
Like the French say:
Je ne sais pas ;-)
But he showed a picture of the inside of his phone wich sit under the battery
It says his phone is the g900f not the g901f
He might be the first one in the world flashing the wrong ROM working ever, I don't know what he did.
 

ripee

Recognized Developer / Recognized Contributor
Like the French say:
Je ne sais pas ;-)
But he showed a picture of the inside of his phone wich sit under the battery
It says his phone is the g900f not the g901f
He might be the first one in the world flashing the wrong ROM working ever, I don't know what he did.
The sticker being inconsistent with what the system reports the hardware as being, is the fault of a shady device vendor, but of course you have to flash what can be flashed.
 
Last edited:
D

Deleted member 11736329

Guest
Your phone is G900f the Samsung S5
It is not the S5+ (plus) wich has better hardware and called S901f
So I expect one of these days you run in trouble flashed S901f on a S900f hardware model.
I can't understand how you got this working anyway, but no need answering that question, you have put the wrong ROM on the wrong model now
The correct ROM wouldn't flash. I found a square peg for a square hole and don't see the point trying to hammer in a round one. You don't have to understand.
 
D

Deleted member 11736329

Guest
@Fluffybrain , I ran a kccat6 build in July with the latest security updates, see my Google Drive in my signature, but you probably can't dirty flash it on top of the official build.
Thanks so much. I'll keep an eye on alerts for it. It's been interesting and I appreciate the tutorial. I will download the file in the signature and prepare the phone. I'll write up what works so others can see what to do.
 

andreoide

Senior Member
The correct ROM wouldn't flash. I found a square peg for a square hole and don't see the point trying to hammer in a round one. You don't have to understand.
I think your answe is way beyond a form of arrogance , as if you did not post a picture if the inside of your phone telling its the model g909f, so whatever you say, it is there in posting 2810
What you flashed I don't even want to know, you yourself are the one causing confusion here.
I hope you have a mirror at home, I suggest you go practice a friendly face.
 
Last edited:

ripee

Recognized Developer / Recognized Contributor
The 18,1 branch is almost ready, just need to work on sepolicy before I post builds. At first selinux will be permissive to catch as many avc denials as possible and fix them in sepolicy, then I will enforce the kernel and collect more logs to finish up with sepolicy, but this will take a few builds over a number of days.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    As long as @ripee works on it, we have to be patient and hope it turns out right.
    Or else that he tells us: I quit with this %@&#-ing kccat6.
    1
    Is ripee still in town? I followed this thread curiously, how it developed.
    I can imagine that Ripee got a bit pissed off by all those negative comments here.
    Still hoping he will continue with kccat6-development.
    I'm not pissed off but my interest in the S5 Plus is limited to my enjoyment of facing challenges and solving puzzles. I have no sense of urgency to get 18.1 to work.
    1
    I'm not pissed off but my interest in the S5 Plus is limited to my enjoyment of facing challenges and solving puzzles. I have no sense of urgency to get 18.1 to work.
    I am very sorry to hear that, if i can somehow help let me know anytime!
    1
    I'm not pissed off but my interest in the S5 Plus is limited to my enjoyment of facing challenges and solving puzzles. I have no sense of urgency to get 18.1 to work.

    Well, if you enjoy challenges than we might have the fun of it .
    It makes me coming back in this thread :)
    1
    New builds.
  • 83
    lineage-os-logo.png

    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A

    Code:
    - Your warrenty is now void.
    - You [b]WILL[/b] trip KNOX!
    - You have been warned.
    - Use at your own risk.
    Introduction:

    This is the thread for the offical port of LineageOS to
    • Samsung Galaxy S5 LTE+, SM-G901F, codename kccat6, and
    • Samsung Galaxy S5 LTE-A, SM-G906S/K/L, codename lentislte.
    • This port is mostly stable. Still, there's no software without bugs.

    How to install:

    • For kccat6, use bootloader CQJ1, CQJ2 or later.
    • For lentislte use bootloader CPL1.
    • install custom recovery, ideally directly from the TWRP project.
      For kccat6: twrp-3.3.0-0-kccat6.img
      For lentislte: twrp-3.3.0-0-lentislte.img
      Note: TWRP 3.2.1-0 is required starting with Lineage-15.1/Oreo!
    • Enter recovery mode
    • Factory reset
    • Flash below ROM
    • Optionally flash Gapps. I suggest OpenGapps.
    • Optionally, if you want SU, install the LineageOS SU addon.
    • Reboot

    Know problems:

    • Sometimes the SIM doesn't show up after reboot.
    • Occasional Camera hiccups.

    State of kernel security:


    Download from:

    Official nightly builds:
    Test builds (only on demand or request):

    Sources:


    XDA:DevDB Information
    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A, ROM for the Samsung Galaxy S5

    Contributors
    cvxda, sassmann, xamio, sktjdgns1189
    Source Code: https://github.com/LineageOS

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: kccat6: CQJ1/CQJ2, lentislte: CPL1
    Based On: Lineage OS

    Version Information
    Status: Beta

    Created 2017-01-08
    Last Updated 2019-04-17
    51
    Notes:

    Thanks to @Stamgastje for the first cut of these notes.

    History and older builds (LineageOS)

    The Lineage OS project -- a.k.a. Lineage Android Distribution (LAD) -- is a continuation of the CyanogenMod project, which was discontinued in December 2016. Before maintaining Lineage OS 14.1 ROM for this phone, @xamio maintained CyanogenMod ROMs (CM13, CM14.1). You can still find these builds via the link to his site (ionkiwi.nl) above. The original (and oldest) CyanogenMod builds for this phone were created by @sktjdgns1189. His original builds are still available here: http://fsrv1.sayanogen.com/KCCAT6-13/, and this was the original thread on this forum.

    Installation

    Below some hints that may help you to install these ROMs on your phone.

    Clean install, or dirty flashing?

    What is the difference?
    The difference is whether you clean (format) the entire /data partition (which contains your apps and user data, as well as the dalvik cache), or not, before flashing the new ROM image:
    • A clean install means: clean the /system, /data (incl. dalvik cache) and /cache partitions, and then install the ROM
    • Dirty flashing means: clean the /system and /cache partitions, as well as the dalvik cache, but not the entire /data partition, before installing the ROM
    With a clean install, you need to manually restore your apps and user data after flashing the new ROM image. With a dirty flash, there is no need to do this -- so this is the faster, but riskier solution. Therefore, it is always recommended to make a backup of your apps (e.g. with Titanium Backup) and user data (internal storage) before flashing any ROM image.

    When could you consider a dirty flash?
    It is, generally speaking, possible to perform a dirty flash:
    • When upgrading a ROM to an newer build of the same ROM (but be careful when upgrading between major versions, e.g. from CM13 to CM14.1)
    • When upgrading from CyanogenMod 14.1 to Lineage OS 14.1 (as Lineage OS is the continuation of CyanogenMod, based on the same sources)

    When should you perform a clean install?
    In all other cases, so e.g.:
    • When downgrading a ROM to an older build of the same ROM
    • When switching between ROMS, e.g. from CyanogenMod to Resurrection Remix (or vice versa). Reason: different ROMs use different code bases that are usually not 100% compatible (exception is upgrading from CyanogenMod 14.1 to Lineage OS 14.1, see above)

    (Note: in case you choose to perform a dirty flash over your existing ROM, don't forget to re-flash the GApps package immediately afterwards!)

    How to dirty flash an official weekly over an unofficial build (and vice versa)?

    When trying to update an unofficial build to an official weekly build, I get an error message in TWRP saying
    "Can't install this package on top of incompatible data. Please try another package or run a factory reset". How do I fix that?


    At the start of an installation the installer checks the build keys. They differ between unoffical and official builds, and the installer refuses to overwrite builds with different keys. To fix this you have to install the official keys before trying to install the official build:
    1. Run this script called lineage-migration-signed.zip in TWRP.
    2. Then install the official ROM zip.
    You only have to do this for the first switch from unoffical to offical build.

    There may be reason to dirty flash an unofficial build over an official build, for instance, if you're developing or testing new stuff. The problem is the same, just in the other direction: You have to install the unofficial build keys:
    1. Run this script called lineage-migration-unsigned.zip in TWRP.
    2. Then install the unofficial ROM zip.

    Modem and bootloader

    Which version do I need?
    Builds from Sept. 19 (cm-13.0-20160919-UNOFFICIAL-kccat6xx.zip) and later should use a Marshmallow modem & bootloader (starting with 'C', so e.g. CPE1, CPH3, CPJ1). Older builds require a Lollipop modem & bootloader (starting with 'B', so e.g. BOH4, BOK2).

    Generally, it is recommended to use the latest modem that is compatible for your device.

    How do I get these images?
    The original ROM files containing the modem and bootloader files are available from the Sammobile site. You have to extract bootloader and modem files and flash them to your device using Odin (Windows) or Heimdall (Linux, MacOS, Windows).
    • Download the firmware file from Sammobile's firmware page for the G901F, G906S, G906K or G906L, depending on your device. The last ones available are CQJ1/CQJ2 for G901F, CPL2 for G906S/K/L. Assuming you download the CQJ1 version for G-901F, the resulting file will be called G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip.
    • Unpack that file. On Windows, right click on the file and choose "Extract all...". On Linux/Mac, simply use the command line:
      Code:
      $ unzip G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip
      After unpacking you get a new file G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. This is a standard tar archive and can be opened with any archiver capable of handling the tar format (especially with tar itself). The attached .md5 suffix indicates, that a md5 checksum has been attached to the file.
    • Extract the file. On Windows you can do this by installing the swiss-army knife of archivers, 7zip. It installs an entry for the right-click context menu. Use it to extract G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. On Linux/Mac, simply use the command line:
      Code:
      $ tar xf G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5
      Apart from the different download page and the different file names, the procedure is the same on the G906 variants.

      Either way, this extracts the following list of files:
      Code:
      NON-HLOS.bin  cache.img.ext4   recovery.img  sdi.mbn
      aboot.mbn     hidden.img.ext4  rpm.mbn       system.img.ext4
      boot.img      modem.bin        sbl1.mbn      tz.mbn
      The files with suffix .img and .img.ext are the actual system files. You don't want them, unless you want to reinstall stock Samsung Android.
      The files NON-HLOS.bin and modem.bin constitute the baseband, all other files with .mbn suffix constitute the bootloader.

    How do I flash these images on Windows with Odin?
    This is only marginally more complex than by using Heimdall (see below). The difference is that Heimdall can immediately flash the extracted .bin and .mbn files, while Odin needs them packed into a tar file. Fortunately you already have 7zip!
    • Select all of the aforementioned .bin and .mbn files. Right click to open the context menu. Select 7zip and choose Add to archive... from the sub menu
      Screenshot_20170125_120950.png

      This opens 7zip's archive dialog. As Archive format choose tar. Append .md5 to the archive filename and press the OK button
      Screenshot_20170125_121840.png

      Congratulations, you're now the happy owner of an Odin file with only bootloader and baseband images.
    • Sidenote: You could also create a tar.md5 file, you just have to append the md5 sum to the just created tar file. It's not really tricky, but you'd need an additional md5sum tool which is not available on Windows by default, so we just skip this here.
    • If you haven't already, download and install Odin.
    • Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
    • Connect your device to your PC's USB port.
    • Start Odin.
    • Select the .tar file you just created.
    • Enable (only) these options: 'Auto Reboot' and 'F. Reset Time'.
    • Flash the images.

    How do I flash these images on Linux/MacOS/Windows with Heimdall?
    • If you haven't already, download and install Heimdall. If you have trouble with the most recent version of Heimdall (the official version 1.4.1 has a few annoying bugs) you have to rebuild heimdall from source by yourself. Instructions for rebuilding can be found here and here.
    • Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
    • Connect your device to your PC's USB port.
    • Check if Heimdall recognizes your device:
      Code:
      $ heimdall detect
      If it doesn't, you have to do some digging:
      • On Windows you might have to install Samsung device drivers.
      • On Linux you might have to create a udev entry for your device. As root, open or create the file /etc/udev/rules.d/51-android.rules and add a line
        Code:
        SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", USER="[insert your non-root username here]"
        , then reboot the machine.
      • On Mac... sorry, I have no idea what to do on a Mac in this case.
    • Flash the bootloader and baseband images:
      Code:
      $ heimdall flash --APNHLOS NON-HLOS.bin \
      --MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn \
      --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn
      This may take a minute or two and then reboot your device automatically. It might reboot into your recovery. That's nothing to worry about. Just reboot from there into system.
    16
    LineageOS 15.1 (Oreo) preview builds

    I made LineageOS 15.1 preview builds available for kccat and lentislte.

    This is very much Work In Progress.
    Only for the experimentally inclined, don't use as daily driver.
    This is only for toying around, I don't take bug reports yet.

    Working:
    • Audio
    • Bluetooth
    • Camera (Photos only)
    • Deep Sleep
    • Display
    • Fingerprint
    • Google Play (with clean install, and a bit bumpy at installation time)
    • GPS
    • Hardware Keys
    • Lights, Torch
    • NFC
    • RIL
    • USB
    • Sensors
    • Wifi
    Not working yet: Everything else. Most notably
    • Camera (Video)
    • Google Play (see above)
    • IR
    • SELinux

    Corinna
    16
    If I delete those files before reboot:
    /data/dalvik-cache/arm/[email protected]@boot-telephony-common...
    the sim card is recognized.

    Thanks, maybe that's a hint for a solution.

    You were really up to something there. @sassmann created a patch to remove these files at startup, and it seems this really makes the RIL startup *much* more reliable. Over 60 reboots with 4 devices with only one fail on one device, and after another small tweak no fail on that device either.

    We need a bit more time for testing so the patch may not make it into the tomorrow's official build, but what's one week, right?

    Edit: I merged the patches so this should be in tomorrow's builds. Thanks again, @Krapotke!
    Edit 2: @Krapotke, I gifted you Ad-free, I'm just so glad we have a workaround.


    Corinna
    16
    Lineage 15.1 goes official for kccat6/lentislte

    Apart from the occasional SIM problem it looks like we're in a pretty good shape now. I triggered the process to make 15.1 the official release for our device. First official builds are going to be built tomorrow or, if the timing isn't quite right, the week after (Monday is lineage-15.1 build day ATM).

    Let's dive in,
    Corinna