[ROM] [OFFICIAL] LineageOS 16.x ALL VARIANTS

Search This thread

Eklondh

Senior Member
Feb 10, 2015
72
14
FYI the LineageOS S5 klte family maintainer haggertk created a new thread here:

[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
Thx bro!

On a side note, I'm currently on one of these Roms and whenever I install gravitybox I get insane lags. Idk if its xposed or gravitybox whos the culprit but it doesnt seem to be magisk at least. Meh, I will continue the battle for quick unlock!

Otherwise these Roms are the **** when it comes to klte hehe no doubt :D
 
  • Like
Reactions: Ibuprophen

r3actor

Member
Nov 1, 2013
34
1
Flashing TWRP Recovery on S5 with Stock Samsung Firmware




  • Notes:
  • You do not need to root the S5 running stock Samsung Firmware before flashing TWRP if you use Odin3 as described below.
  • The sequence is > Samsung OS > flash TWRP custom recovery > Flash LineageOS + optional packages if you wish.
  • Installing an official Samsung firmware on your S5 is a last resort troubleshooting step when all else fails when using a custom OS (ROM) or to make sure that a problem is not hardware related as the stock Samsung firmware it is the most stable for a given device because Samsung had paid staff working for years on it to fix the problems reported by thousands of users & warranty claims.
  • The Galaxy S5 SM-G900V Verizon LTE is a special case and contrary to most S5 klte + variants it has a locked bootloader out-of-the-box thanks to Verizon. The first thing to do is to check if the bootloader is unlocked if you bought the phone used. To check that boot in Download mode & if you see "Mode: Developer" the bootloader is unlocked. See the attached screenshots in S5 G900V Bootloader Update?. If it's not unlocked see this XDA S5 Verizon thread. If you have the CID 15 variant that can be unlocked, do it then flash TWRP as described below.

1- Charge the S5 to at least 80% & to avoid errors it is better to connect the phone directly to the computer and not via a USB hub when using Odin. Also better to have Odin, Samsung Firmware & TWRP on C drive & not on external drives.

2- Download the most recent (@ the present) Odin3 v3.14.4: https://dl2018.sammobile.com/Odin3-v3.14.4.zip

Unzip or unpack the .zip file & copy the Odin3-v3.14.4 folder to the root of C drive.

3- Optional: you can install the most recent Samsung stock Firmware for your exact S5 model for testing purposes or to update the modem, bootloader & other vendor's firmwares not included in LineageOS. The respective download pages include instructions about how to install it using Odin:
  • Most trusted. May require to register (slow) or paid subscription (fast) depending on the firmware you choose: https://www.sammobile.com
  • Don't be fooled by fake Download ad buttons: https://updato.com. Now requires to be registered.

4- Download the TWRP for Samsung Galaxy S5 Qualcomm (klte family) for your exact model. Get the twrp-3.4.0-0-klte....img.tar version to use with Odin & copy it to your Odin3-v3.14.4 folder. The TWRP app is collecting data, wants to always run in the background & is not recommended.

The most recent TWRP Recovery for S5 is required for the built-in OTA LineageOS Updater to work properly.



5- On the computer Right-click Odin and run as Administrator. Click on the AP button and navigate to the twrp-3.4.0-0-klte....img.tar file. (See attached Odin screenshot)

Turn off the phone & boot in Odin Mode (A.K.A. Download Mode) (press and hold Home + Power + Volume Down buttons and confirm with Volume up to Continue) then connect to the computer and in Odin > Options do not select Auto Reboot and keep only the F. Reset Time option selected and nothing else! Click Start.

When Odin has finished the TWRP Recovery installation you will see a blue bar on the S5 screen and All threads completed. (succeed 1 / failed 0) in the Odin Log window. Disconnect the phone & reboot in TWRP Recovery Mode: (volume up + Home + Power buttons) and release the buttons as soon as you see the Samsung Galaxy S5 logo otherwise by default the stock Samsung firmware will revert to the stock Samsung recovery.

This is a one time thing, afterwards booting in Recovery will always be in TWRP as it will rename the stock Samsung one.

If you have network signal & LTE working with your Samsung stock firmware do this before flashing LineageOS:
  1. Write down and/or screenshot your current APN settings that you can use if you have a network signal, data or LTE problem in LineageOS.
  2. After installing TWRP & before flashing LineageOS do an EFS partition backup that can be use to fix a no SIM or no network problem. See this post which includes TWRP screenshots: No Network, No IMEI, No SIM & EFS Partition Restore Fix

You can then reboot to System, reboot back to TWRP & proceed with the LineageOS super clean install as described above.
***

Magisk Problem



I described exactly how I installed Magisk v18.0 in New S5 LineageOS 16.0 haggertk 2019-01-09 Build! - Report & Bugs & added some screenshots.



I'm getting dizzy reading all the stuff you tried. :eek:

"Zip flashed successfully no error" - Well obviously there is error(s) somewhere because Magisk is not working for you. ;)

From what you wrote it seems that you did it properly so maybe there is a file system error, old TWRP, old bootloader or some hardware problems.

The best place to ask for help would be in the Magisk General Support / Discussion with several local Magisk experts but without logs there is no way to intelligently troubleshoot your problem.

I would suggest a super clean install as described above including a Format Data in TWRP.

Then after flashing the most recent Magisk & before rebooting > TWRP > Home > Advanced > Copy Log to external SD card then reboot to System. The TWRP Recovery log can be very useful for troubleshooting an installation problem & it takes about 10 seconds to back it up.

In Magisk Manager > hamburger > Log > Magisk > there is a save button on the top (screenshot). That could be useful for troubleshooting besides capturing a logcat.

Because you are not rooted check "setup ADB and then capture a log" in the LineageOS wiki.

Or since the phone is not rooted you can grant this permission to enable the fast & easy to use SysLog using ADB & a computer:
  • adb shell pm grant com.tortel.syslog android.permission.READ_LOGS

Read this post in the Magisk General Support thread by Recognized Contributor @Didgeridoohan.

Please report back if you fix your problem or not. :cool:
***
Thanks for this guide!
Curently I'm trying to get LOS 18.1 by applying your guide to my Stock Samsung firmware SM-G900F (S5) phone.
I downloaded Odin version that you shared 3.14.4.
BUT... I wonder why that package has 2 extra *.dll files (while other ODIN versions, like 3.14.1 only has an *.exe and *.ini file in it)?
The 2 extra *.dll files that came with the 3.14.4 version of ODIN that you shared are:

cpprest141_2_10.dll
SS_DL.dll


Putting 'unknown' *.dll files on C drive is not something that is 'good'. So, can you tell a newb like me, what are those two *.dll files an do I need them?

Thanks!
 

jdrch

Senior Member
Jun 18, 2014
428
189
Quad Cities, IA
Thanks for this guide!
Curently I'm trying to get LOS 18.1 by applying your guide to my Stock Samsung firmware SM-G900F (S5) phone.
I downloaded Odin version that you shared 3.14.4.
BUT... I wonder why that package has 2 extra *.dll files (while other ODIN versions, like 3.14.1 only has an *.exe and *.ini file in it)?
The 2 extra *.dll files that came with the 3.14.4 version of ODIN that you shared are:

cpprest141_2_10.dll
SS_DL.dll


Putting 'unknown' *.dll files on C drive is not something that is 'good'. So, can you tell a newb like me, what are those two *.dll files an do I need them?

Thanks!
Don't recall seeing any such files back in the day when I did this, but:

  1. Check the 18.1 thread as that's the latest version and where all the action is. 16.1 is no longer developed and therefore this thread might not be where the latest info is
  2. When in doubt about any file, upload it to virustotal.com and see what the scans say. Bear in mind you might get false positives for some files from here (not the ODIN ones, I think) because the process of rooting uses certain known exploits
 

r3actor

Member
Nov 1, 2013
34
1
Don't recall seeing any such files back in the day when I did this, but:

  1. Check the 18.1 thread as that's the latest version and where all the action is. 16.1 is no longer developed and therefore this thread might not be where the latest info is
  2. When in doubt about any file, upload it to virustotal.com and see what the scans say. Bear in mind you might get false positives for some files from here (not the ODIN ones, I think) because the process of rooting uses certain known exploits
Thanks for your fast reply.
The reason why I wanted to follow (the part of) curiousrom's guide is because it looks well written. I only need a way to properly install TWRP on my S5 phone which still has official samsung stock ROM (android v5.0). After getting TWRP on my phone, I could then read the steps from LOS 18.1 topic. I only wanted to get to TWRP 'stage' where I can backup things like radio(modem) in case I fckup something.

Btw.... would it be 'ok' to use Odin 3.10.7 just to put latest TWRP on the phone, or I will need newer version of Odin (newer than 3.10.7) ?
 

jdrch

Senior Member
Jun 18, 2014
428
189
Quad Cities, IA
Thanks for your fast reply.
The reason why I wanted to follow (the part of) curiousrom's guide is because it looks well written. I only need a way to properly install TWRP on my S5 phone which still has official samsung stock ROM (android v5.0). After getting TWRP on my phone, I could then read the steps from LOS 18.1 topic. I only wanted to get to TWRP 'stage' where I can backup things like radio(modem) in case I fckup something.

Btw.... would it be 'ok' to use Odin 3.10.7 just to put latest TWRP on the phone, or I will need newer version of Odin (newer than 3.10.7) ?
Just use whichever version is mentioned in this thread. The newer versions don't support older devices very well (if at all.)
 
Thanks for this guide!...

I downloaded Odin version that you shared 3.14.4.
BUT... I wonder why that package has 2 extra *.dll files (while other ODIN versions, like 3.14.1 only has an *.exe and *.ini file in it)?
The 2 extra *.dll files that came with the 3.14.4 version of ODIN that you shared are:

cpprest141_2_10.dll
SS_DL.dll


Putting 'unknown' *.dll files on C drive is not something that is 'good'. So, can you tell a newb like me, what are those two *.dll files an do I need them?

Thanks for the feedback & glad the guide was useful to you.

That Odin3 download link is from sammobile, a trusted source of stock Samsung OS.

I don't know what those two *.dll files do exactly when running Odin3 but I trust them & never had any issues with any downloads from sammobile.
***
...Check the 18.1 thread as that's the latest version and where all the action is. 16.1 is no longer developed and therefore this thread might not be where the latest info is...

This still works regardless of the OS running on the S5: S5 Odin Flashable Modem & Bootloader

I wrote this for Windows PC users & LineageOS 16.0 but the same steps works for 18.1: S5 super clean install except that you need a GApps ARM package for Android 11.

And yes the current official thread for the S5 is [ROM][OFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*) ;-)
***
 
Last edited:

frone0

Member
Sep 21, 2022
22
5
S5 LineageOS Super Clean Install - Magisk Problem

For the official LineageOS installation or upgrading instructions see https://wiki.lineageos.org/devices/ > {your device}. Note that the wiki does not mention TWRP & uses Heimdall instead of Odin.

On a Windows computer Odin is much faster & easier to use to install TWRP compared to the finicky Heimdall that requires drivers that in turn breaks Odin & that's why I wrote this tutorial.

If you are running the stock Samsung OS (or want to install it to rule out a possible hardware problem) see the chapter below: Flashing TWRP Recovery on S5 with Stock Samsung Firmware. The sequence is > Samsung OS > flash TWRP custom recovery > backup the EFS partition > Flash LineageOS + optional packages if you wish.

If you are running unofficial LineageOS 16.0 on your S5 klte + variants or official LineageOS 14.1 or 15.1 see Official 16.0 for S5 2019-03-01 - Dirty Flash Report and you can install official 16.0 with the proper Open GApps ARM 9.0 & just a System + caches wipe.

If you are running a custom ROM (OS) & custom recovery and you want to start from the ground up & do a really S5 LineageOS super clean install:
  1. Make sure you have the most recent TWRP if you want the built-in LineageOS OTA Updater to work properly (see How to Update TWRP Using TWRP Itself) and the most recent bootloader & modem (how-to update).


  2. Optional: Then after backing up your external Micro SD Card to computer, format it as Portable storage using the phone itself: usually the default file explorer has this function. Stock Files explorer formats the Micro SD card to the FAT32 file system so it you use a computer to format your card that's what the S5 likes by default but you can also use exFAT. Adoptable storage is not recommended on the S5 as explained here: Micro SD Card as Internal Storage - Adoptable Storage.
  3. Copy to external Micro SD Card the Official LineageOS 16.0 ROM for the S5 klte & variants for your exact phone model:
    • klte - SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
    • klteactivexx - SM-G870F
    • kltechn - SM-G9006V, SM-G9008V
    • kltechnduo - SM-G9006W, SM-G9008W
    • klteduos - SM-G900FD, SM-G900MD
    • kltedv - SM-G900I, SM-G900P
    • kltekdi - SCL23 & SC-04F
    • kltekor - SM-G900K, SM-G900L, SM-G900S

    And if you wish Open GApps ARM 9.0.

    Note: if you are installing LineageOS 17.1 you need Open GApps ARM 10.0.

    I prefer the smaller Pico package & just add the extra apps I need from the Play Store or https://f-droid.org/ . See Open GApps Package Comparison.

    Rule of thumb: the larger the GApps package the more chance of installation errors.

    For root you can chose either the LineageOS 16.0 addonsu ARM and the addonsu-remove-16.0-arm-signed.zip from the same page which should be copied to your external SD card just in case you need it in the future to solve a root problem or if you want to switch to Magisk. Note: the addonsu does NOT work on LineageOS 17.1. Only Magisk workes on that version.

    Or the Latest Stable Magisk (Release thread), Latest Magisk Manager.apk & Latest Magisk uninstaller. Beta is not recommended.

    Note: in TWRP MTP file transfer is enabled by default. So you can boot in TWRP, connect to computer & transfer the files to be flashed to the external Micro SD card.
    *
  4. Sync all your > Settings > Accounts one by one. To avoid some restoring Google Backup problems reported by some users set Screen lock to None, remove SIM lock if you have one & force a fresh > Settings > System > Advanced > Backup or > System > Google > Backup + a Chat backup in WhatsApp's Settings if you use that app.
  5. You can also screenshot or write down your working APN settings before flashing 16.0 so you can use that info in case of a problem connecting to your network provider.
  6. In TWRP backup to the external Micro SD Card the very important EFS partition as described in No Network, No EMEI & EFS Partition Restore Fix
  7. Then after backing up the internal sdcard, in TWRP use Format Data which rebuilds the entire file system of the Data partition including the internal sdcard instead of using wipe that only deletes files of Data without affecting the internal sdcard (screenshot).
    See TWRP FAQ: What is a data/media device? for detailed explanations:


    Format Data adds an empty section after the Data partition for some future encryption related data which is required if you decide later to encrypt your S5: A.K.A. encryption footer.
  8. In TWRP after Format Data > Advanced wipe of Cache, Dalvik / Art Cache, System like in the last attached screenshot below and reboot to Recovery before installing the LineageOS ROM + Open GApps in one go without rebooting in between then reboot to System.

    You can root later at anytime so it is not necessary to do it at this stage. I prefer to install only LineageOS + GApps to keep it simple & avoid errors, boot to system, setup the device, reboot to recovery & make a full TWRP backup of that clean install then root the device.
    ***
  9. Optional but not recommended: In TWRP instead of Format Data, you could > Advanced wipe of Cache, Dalvik / Art Cache, System & Data and reboot to Recovery then install the LineageOS ROM + Open GApps but you may carry some problematic leftovers from internal sdcard & some Data file system problems. You could also have some encryption problems if you decide to do it at a later stage as Format Data reserves some space at the end of the Data partition for the encryption footer which the simple wipe Data does not do.

If you want to restore a Google Backup, do it as soon as you boot to System the first time when asked if you want to do that. My Google backup was huge @ 1.3 GB so make sure you have a quick wifi connection if you do that.

It restored 90% of my LineageOS settings, all apps & my data but did not include the apps that I installed manually from other sources than Google Play obviously.

And/or use an other apps backup method like Titanium Backup for example (requires root to create the backups) but it's hit or miss depending on the apps and their required libraries which are not always backed up by Titanium Backup.
***

Rooting Galaxy S5 LineageOS 16.0

These 2 methods were tested successfully on my S5 running LineageOS with the files downloaded from the links above.

LineageOS own su root solution:

  • In TWRP flash the LineageOS 16.0 addonsu ARM.zip package.
  • Boot to System.
  • Enable Developer options: Settings > About phone > keep tapping on Build number until a pop up saying "Developer options enabled" appears.
  • Go back to Settings > System > Advanced > Developer options > Root access > enable Apps. Note the enable Apps and ADB options in case you need root while using ADB & connected to a computer.
  • You can disable root at any time on the fly with that Root access setting.
  • Or remove it permanently by flashing in TWRP addonsu-remove-16.0-arm-signed.zip

Or Magisk if you wish. On my S5 G900M running LineageOS 16.0, Magisk Manager was no showing up after flashing the Magisk installer & rebooting but installing manually Magisk Manager.apk showed that Magisk was installed correctly & enabled.
***

See some S5 LineageOS optimization tips here: Remove Animations UI Speedup Test - Taming Google & Apps
***

I described how I updated my S5's modem & bootloader here & included Odin screenshots: S5 Odin Flashable Modem & Bootloader

As seen in the screenshot you can use DevCheck > System where you can see Bootloader & Radio which is the same as modem or baseband.

You can also see your current bootloader & modem using adb. See this XDA portal article What is ADB? How to Install ADB, Common Uses, and Advanced Tutorials for more info.

adb shell getprop > getprop_Properties.txt

And search file with bootloader & modem. Or to see it on your screen:

adb shell getprop gsm.version.baseband

adb shell getprop ro.bootloader
***

Flashing TWRP Recovery on S5 with Stock Samsung Firmware




  • Notes:
  • You do not need to root the S5 running stock Samsung Firmware before flashing TWRP if you use Odin3 as described below.
  • The sequence is > Samsung OS > flash TWRP custom recovery > Flash LineageOS + optional packages if you wish.
  • Installing an official Samsung firmware on your S5 is a last resort troubleshooting step when all else fails when using a custom OS (ROM) or to make sure that a problem is not hardware related as the stock Samsung firmware it is the most stable for a given device because Samsung had paid staff working for years on it to fix the problems reported by thousands of users & warranty claims.
  • The Galaxy S5 SM-G900V Verizon LTE is a special case and contrary to most S5 klte + variants it has a locked bootloader out-of-the-box thanks to Verizon. The first thing to do is to check if the bootloader is unlocked if you bought the phone used. To check that boot in Download mode & if you see "Mode: Developer" the bootloader is unlocked. See the attached screenshots in S5 G900V Bootloader Update?. If it's not unlocked see this XDA S5 Verizon thread. If you have the CID 15 variant that can be unlocked, do it then flash TWRP as described below.

1- Charge the S5 to at least 80% & to avoid errors it is better to connect the phone directly to the computer and not via a USB hub when using Odin. Also better to have Odin, Samsung Firmware & TWRP on C drive & not on external drives.

2- Download the most recent (@ the present) Odin3 v3.14.4: https://dl2018.sammobile.com/Odin3-v3.14.4.zip

Unzip or unpack the .zip file & copy the Odin3-v3.14.4 folder to the root of C drive.

3- Optional: you can install the most recent Samsung stock Firmware for your exact S5 model for testing purposes or to update the modem, bootloader & other vendor's firmwares not included in LineageOS. The respective download pages include instructions about how to install it using Odin:
  • Most trusted. May require to register (slow) or paid subscription (fast) depending on the firmware you choose: https://www.sammobile.com
  • Don't be fooled by fake Download ad buttons: https://updato.com. Now requires to be registered.

4- Download the TWRP for Samsung Galaxy S5 Qualcomm (klte family) for your exact model. Get the twrp-3.4.0-0-klte....img.tar version to use with Odin & copy it to your Odin3-v3.14.4 folder. The TWRP app is collecting data, wants to always run in the background & is not recommended.

The most recent TWRP Recovery for S5 is required for the built-in OTA LineageOS Updater to work properly.



5- On the computer Right-click Odin and run as Administrator. Click on the AP button and navigate to the twrp-3.4.0-0-klte....img.tar file. (See attached Odin screenshot)

Turn off the phone & boot in Odin Mode (A.K.A. Download Mode) (press and hold Home + Power + Volume Down buttons and confirm with Volume up to Continue) then connect to the computer and in Odin > Options do not select Auto Reboot and keep only the F. Reset Time option selected and nothing else! Click Start.

When Odin has finished the TWRP Recovery installation you will see a blue bar on the S5 screen and All threads completed. (succeed 1 / failed 0) in the Odin Log window. Disconnect the phone & reboot in TWRP Recovery Mode: (volume up + Home + Power buttons) and release the buttons as soon as you see the Samsung Galaxy S5 logo otherwise by default the stock Samsung firmware will revert to the stock Samsung recovery.

This is a one time thing, afterwards booting in Recovery will always be in TWRP as it will rename the stock Samsung one.

If you have network signal & LTE working with your Samsung stock firmware do this before flashing LineageOS:
  1. Write down and/or screenshot your current APN settings that you can use if you have a network signal, data or LTE problem in LineageOS.
  2. After installing TWRP & before flashing LineageOS do an EFS partition backup that can be use to fix a no SIM or no network problem. See this post which includes TWRP screenshots: No Network, No IMEI, No SIM & EFS Partition Restore Fix

You can then reboot to System, reboot back to TWRP & proceed with the LineageOS super clean install as described above.
***

Magisk Problem



I described exactly how I installed Magisk v18.0 in New S5 LineageOS 16.0 haggertk 2019-01-09 Build! - Report & Bugs & added some screenshots.



I'm getting dizzy reading all the stuff you tried. :eek:

"Zip flashed successfully no error" - Well obviously there is error(s) somewhere because Magisk is not working for you. ;)

From what you wrote it seems that you did it properly so maybe there is a file system error, old TWRP, old bootloader or some hardware problems.

The best place to ask for help would be in the Magisk General Support / Discussion with several local Magisk experts but without logs there is no way to intelligently troubleshoot your problem.

I would suggest a super clean install as described above including a Format Data in TWRP.

Then after flashing the most recent Magisk & before rebooting > TWRP > Home > Advanced > Copy Log to external SD card then reboot to System. The TWRP Recovery log can be very useful for troubleshooting an installation problem & it takes about 10 seconds to back it up.

In Magisk Manager > hamburger > Log > Magisk > there is a save button on the top (screenshot). That could be useful for troubleshooting besides capturing a logcat.

Because you are not rooted check "setup ADB and then capture a log" in the LineageOS wiki.

Or since the phone is not rooted you can grant this permission to enable the fast & easy to use SysLog using ADB & a computer:
  • adb shell pm grant com.tortel.syslog android.permission.READ_LOGS

Read this post in the Magisk General Support thread by Recognized Contributor @Didgeridoohan.

Please report back if you fix your problem or not. :cool:
***
Thanks for a super detailed set of steps for getting this process done. I've upgraded a couple g900v phones using this and have had great success.

Unfortunately, I've run into a problem with one of the LineageOS over air upgrades and am now trying to get a g900v back to stock to troubleshoot. The issue with the update crippled all mobile data. To troubleshoot, I used your steps above to install the Samsung Stock Firmware. Surprisingly, after rolling back to stock firmware, the mobile data was still broken. To further troubleshoot, I purchased another g900v and tested the mobile data successfully, then upgraded to the latest LineageOS, which broke mobile data again. I rolled this second phone back to the Samsung Stock Firmware as well and the mobile data issue persists.

Is there a chance I am missing something here in returning these phones to complete 'factory defaults' or have I likely gone past the point of no return with them.

Another point of information - After rolling back to Samsung Stock Firmware, the phones still automatically connect back up to my wireless network. They are saving the password through the rollback process. I figure this hints that I might be doing something wrong.

Thanks!
 

kurtn

Senior Member
Jan 28, 2017
4,709
2,105
Small town in Bavaria
Thanks for a super detailed set of steps for getting this process done. I've upgraded a couple g900v phones using this and have had great success.

Unfortunately, I've run into a problem with one of the LineageOS over air upgrades and am now trying to get a g900v back to stock to troubleshoot. The issue with the update crippled all mobile data. To troubleshoot, I used your steps above to install the Samsung Stock Firmware. Surprisingly, after rolling back to stock firmware, the mobile data was still broken. To further troubleshoot, I purchased another g900v and tested the mobile data successfully, then upgraded to the latest LineageOS, which broke mobile data again. I rolled this second phone back to the Samsung Stock Firmware as well and the mobile data issue persists.

Is there a chance I am missing something here in returning these phones to complete 'factory defaults' or have I likely gone past the point of no return with them.

Another point of information - After rolling back to Samsung Stock Firmware, the phones still automatically connect back up to my wireless network. They are saving the password through the rollback process. I figure this hints that I might be doing something wrong.

Thanks!
What procedure do you follow for roll back?
Mobile data should be fixed by backup of efs partition
 
  • Like
Reactions: frone0

frone0

Member
Sep 21, 2022
22
5
What procedure do you follow for roll back?
Mobile data should be fixed by backup of efs partition
Hello Kurtn -

To roll the phone back to stock, I tried two separate routes. Both are from Curiousrom's 'Super Clean' install instructions above. The section I followed for this rollback is entitled "Flashing TWRP Recovery on S5 with Stock Samsung Firmware". I tried both methods of installing the "twrp-3.4.0-0-klte....img.tar" using Odin and also downloading the "Samsung stock Firmware" as mentioned as an option. For the Samsung stock firmware, I followed the steps mentioned at the download site (updato.io) which also used Odin.

After completing both rollbacks, the phone still cannot use mobile data. Also, it has retained my wifi password through both rollbacks. Seemed odd to me, so I thought I should mention it.

Is this the best method for repairing my efs partition?

I'm looking at the section entitled "CHAPTER 3: AKA "YEAH ABOUT THAT MY EFS IS ALREADY CORRUPTED, PLS HELP"

Thanks for the help troubleshooting!
 
Last edited:
...g900v phones using this and have had great success.

Unfortunately, I've run into a problem with one of the LineageOS over air upgrades and am now trying to get a g900v back to stock to troubleshoot. The issue with the update crippled all mobile data. To troubleshoot, I used your steps above to install the Samsung Stock Firmware. Surprisingly, after rolling back to stock firmware, the mobile data was still broken...

What is your network provider?

FYI LineageOS does no support VoLTE on any Samsung devices @ the present because the devs could not reverse engineer Samsung's proprietary VoLTE implementation so far.

That could be a deal breaker if your network provider drops 2G & 3G as only VoLTE will work for voice calls after that and it may explain your calls issues.

Try > Settings > Network & internet > Mobile network > Advanced > Access Point Names > APN > and make 100% sure that they are identical to your network provider's current recommended settings then turn off the device, wait a few seconds, turn back on, then send an SMS before receiving one.
***
 
  • Like
Reactions: frone0 and pmduper

frone0

Member
Sep 21, 2022
22
5
What is your network provider?

FYI LineageOS does no support VoLTE on any Samsung devices @ the present because the devs could not reverse engineer Samsung's proprietary VoLTE implementation so far.

That could be a deal breaker if your network provider drops 2G & 3G as only VoLTE will work for voice calls after that and it may explain your calls issues.

Try > Settings > Network & internet > Mobile network > Advanced > Access Point Names > APN > and make 100% sure that they are identical to your network provider's current recommended settings then turn off the device, wait a few seconds, turn back on, then send an SMS before receiving one.
***
Thanks for the info! I'm certain that a previous version was working, but still troubleshooting. Are you telling me that 4G data will not be supported in any way on this phone using LineageOS? That would likely be a bummer.

My network provider is Verizon.

I went through the steps you posted for me. I am swapping my SIMM card between a working stock g900v and the failing one that had been flashed. Here are the results:

I first turned off the wifi, to make sure it was only using the mobile data.

1. Swapped the SIMM into the failing phone and turned it on.
2. Went through similar steps (stock phone steps are different) to locate AP Names.
3. Phone popped up a message saying it was switching to Global Mode.
4. Found the AP names, which did not match that of the working phone.
5. Found that I could not add an AP Name, nor edit the existing ones. Could only delete them.
6. Powered off the phone and waited a minute.
7. Powered on the phone and immediately sent a SMS text, which worked.
8. Sent and received a test MMS message with picture attachment successfully.
9. Found Chrome and all other Internet apps to still report no network connection.

I'm pretty sure the MMS messaging was failing before as well. I was also unable to add or edit existing AP names on either phone. Both are running Samsung default at this point. The failing one was upgrade to LineageOS previously.

Thanks again for the help - please let me know what other info I can provide or what I should try!
 
Are you telling me that 4G data will not be supported in any way on this phone using LineageOS?

No. 4G data is working fine on my S5 G900M running LineageOS 18.1.

My network provider is Verizon.

It's very possible that Verizon is blocking data on your S5 running LineageOS because it's not supporting VoLTE.

See this & their other support pages: https://www.verizon.com/support/prepaid-3g-to-4g-lte-upgrade-faqs/

Try with a SIM from an other provider.

5. Found that I could not add an AP Name, nor edit the existing ones. Could only delete them.

Try this app to work around Verizon's APN editing restriction: AddAPN - Access the Add APN settings page directly.

If you are running LineageOS 18.1. then please post in that thread so everybody could benefit & contribute: https://forum.xda-developers.com/t/...geos-18-1-for-samsung-galaxy-s5-klte.4267517/
***
 
  • Like
Reactions: frone0 and pmduper

frone0

Member
Sep 21, 2022
22
5
No. 4G data is working fine on my S5 G900M running LineageOS 18.1.



It's very possible that Verizon is blocking data on your S5 running LineageOS because it's not supporting VoLTE.

See this & their other support pages: https://www.verizon.com/support/prepaid-3g-to-4g-lte-upgrade-faqs/

Try with a SIM from an other provider.



Try this app to work around Verizon's APN editing restriction: AddAPN - Access the Add APN settings page directly.

If you are running LineageOS 18.1. then please post in that thread so everybody could benefit & contribute: https://forum.xda-developers.com/t/...geos-18-1-for-samsung-galaxy-s5-klte.4267517/
***
Thanks again for all of the info.

I am unable to try another SIM as I only have the one. I am currently trying to get it back to working under stock (not LineageOS) before further testing however. I'm wondering what I am doing wrong in getting it back to stock as it worked before the LineageOS install, but now fails even after flashing the stock firmware. I have to be doing something wrong.

If I am running stock firmware, should I still need to use the AddAPN app to add an APN?

I feel like something is 'left over' still from the LineageOS install. Wondering if it might be the modem, etc.

Not sure how to quote it, but above this kurtn suggests that I might need to repair my EFS partition. Is this guide the best way to get started on doing this?

Thanks again!!
 
........ I'm wondering what I am doing wrong in getting it back to stock as it worked before the LineageOS install, but now fails even after flashing the stock firmware. I have to be doing something wrong.
Did you flash multiple part stock ROM and if yes CSC and not HOME_CSC file chosen?
If I am running stock firmware, should I still need to use the AddAPN app to add an APN?
Was never necessary for me. Worked automatically.
I feel like something is 'left over' still from the LineageOS install. Wondering if it might be the modem, etc.
Shouldn't be after flashing stock.
In the past I sometimes had to flash stock twice bit can't remember it it was on this device.
Not sure how to quote it, but above this kurtn suggests that I might need to repair my EFS partition....
Imho only when IMEI is missing.
 
Last edited:
  • Like
Reactions: frone0

frone0

Member
Sep 21, 2022
22
5
No. 4G data is working fine on my S5 G900M running LineageOS 18.1.



It's very possible that Verizon is blocking data on your S5 running LineageOS because it's not supporting VoLTE.

See this & their other support pages: https://www.verizon.com/support/prepaid-3g-to-4g-lte-upgrade-faqs/

Try with a SIM from an other provider.



Try this app to work around Verizon's APN editing restriction: AddAPN - Access the Add APN settings page directly.

If you are running LineageOS 18.1. then please post in that thread so everybody could benefit & contribute: https://forum.xda-developers.com/t/...geos-18-1-for-samsung-galaxy-s5-klte.4267517/
***

No. 4G data is working fine on my S5 G900M running LineageOS 18.1.



It's very possible that Verizon is blocking data on your S5 running LineageOS because it's not supporting VoLTE.

See this & their other support pages: https://www.verizon.com/support/prepaid-3g-to-4g-lte-upgrade-faqs/

Try with a SIM from an other provider.



Try this app to work around Verizon's APN editing restriction: AddAPN - Access the Add APN settings page directly.

If you are running LineageOS 18.1. then please post in that thread so everybody could benefit & contribute: https://forum.xda-developers.com/t/...geos-18-1-for-samsung-galaxy-s5-klte.4267517/
***
I'd also love to post my findings in the thread you mentioned. Just not sure what I should put there or if I have enough info yet to help. Please let me know what I can do here.

Thanks again!
 

frone0

Member
Sep 21, 2022
22
5
Did ylu flash multiple part stock ROM and if yes CSC and not HOME_CSC file chosen?

Was never necessary for me. Worked automatically.

Shouldn't be after flashing stock.
In the past I sometimes had to flash stock twice bit can't remember it it was on this device.

Imho only when IMEI is missing.
Thanks for the info!

I'm not sure how to answer your first question. The stock firmware I downloaded was from this link at updato.com:


The download extracted to this file, which I used to flash it to stock:

ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5

That file was about 4.2GB in size.

I also do not think that I flashed it twice with this firmware yet. I have flashed it with a few different ones in trying to revert to stock though.

I'll leave my EFS partition alone for now if you think I should.

Thanks again!
 
  • Like
Reactions: vlad3647
....
The download extracted to this file, which I used to flash it to stock:

ALL_VZW_G900VVRU2DQL1_G900VVZW2DQL1_CL8025411_QB16020535_REV00_user_low_ship_MULTI_CERT.tar.md5

That file was about 4.2GB in size.

I also do not think that I flashed it twice with this firmware yet. I have flashed it with a few different ones in trying to revert to stock though.

I'll leave my EFS partition alone for now if you think I should....
So it was a one part file and then there's no chance for choosing different CSC files.

If it was mine I'd do:
Download multiple part stock using GitHub - ivanmeler/SamFirm_Reborn.
Fill in device name and region (look them up here: https://samfrew.com/)
Check "binary nature" and "decryption".
Results in one zip file containing at least AP, BL, CSC, CP.
Unzip it and flash them with Odin.

Regarding EFS you don't tell if IMEI is present.
 
Last edited:
  • Like
Reactions: frone0 and vlad3647

frone0

Member
Sep 21, 2022
22
5
So it was a one part file and then there's no chance for choosing different CSC files.

If it was mine I'd do:
Download multiple part stock using GitHub - ivanmeler/SamFirm_Reborn.
Fill in device name and region (look them up here: https://samfrew.com/)
Check "binary nature" and "decryption".
Results in one zip file containing at least AP, BL, CSC, CP.
Unzip them and flash with Odin.

Regarding EFS you don't tell if IMEI is present.
It took some doing, but I was able to download both .ZIP files. I have Odin ready to go and have used it in the past by populating the AP with a file and then flashing, but I'm not sure what I need to do with these two .ZIP files.

Please let me know what to put where in Odin for the test flash.

How can I check if IMEI is present so I can report back?

Thanks for all of the help!
 

kurtn

Senior Member
Jan 28, 2017
4,709
2,105
Small town in Bavaria
It took some doing, but I was able to download both .ZIP files. I have Odin ready to go and have used it in the past by populating the AP with a file and then flashing, but I'm not sure what I need to do with these two .ZIP files.

Please let me know what to put where in Odin for the test flash.

How can I check if IMEI is present so I can report back?

Thanks for all of the help!
There should be tar files in those zip archives
 
  • Like
Reactions: frone0

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    This time I would try Heimdall with all the files necessary you extracted.
    It took some doing, but I was finally able to flash with Heimdall and have the phone boot up. After successfully flashing the phone, I went through the initial setup, connecting to wifi, Google account, etc. Everything seemed to work great until I turned off the WiFi. The mobile data (Internet browsing, etc.) again failed with wifi off, but I was able to successfully send and receive MMS messages. Voice phone calls work fine as well.

    There were some files that were listed when I ran the print.pit on the phone that were not included in the files that were extracted, so I obviously did not flash them. Not sure if there is a better 'source' for a complete firmware release with more files? Any ideas of what I might be doing wrong here?

    Just an FYI, I used the following post to help with flashing under Heimdall:


    Thanks again for the help!
    1
    ....
    There were some files that were listed when I ran the print.pit on the phone that were not included in the files that were extracted, so I obviously did not flash them. Not sure if there is a better 'source' for a complete firmware release with more files? Any ideas of what I might be doing wrong here?....
    Glad I could help a bit.
    Can you name the partitions you had no files for?

    As imho all stock ROM files should contain all necessary parts I strongly doubt that there are versions which include more than you got.
    Of course you can have a look at samfrew.com, youmobile.org, sammobile.com and maybe more.

    I once had the necessity to flash the same stock at least twice to be successful.
    Perhaps it helps here as well.
    1
    Glad I could help a bit.
    Can you name the partitions you had no files for?

    As imho all stock ROM files should contain all necessary parts I strongly doubt that there are versions which include more than you got.
    Of course you can have a look at samfrew.com, youmobile.org, sammobile.com and maybe more.

    I once had the necessity to flash the same stock at least twice to be successful.
    Perhaps it helps here as well.
    Sorry about the slow reply - had to step away for a bit.

    I've attached two files. The 'print-pit-partitions.txt' is the list of partitions on the phone when I run the print-pit command included. The other text file is a list of the stock files that I get when extracting the stock ROM download. Just guessing by what I am seeing, it looks like there are a few partitions without flash files on the phone and there are partitions with flash files that are not included in the stock ROM download. I don't know if these are unimportant or not, just trying to help with the info here.

    I am not 100% sure that I have flashed the same stock twice before testing or reflashing. When you did not do this and it failed, was it that it would not boot up, or that something like the mobile data only failed? Mine seems to boot up fine every time after flashing a new stock rom, with only the mobile data failing.

    Sure hope this helps - thanks for all of your help in it!
  • 105
    20170102T093800.jpg

    Code:
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.

    LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), 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.


    Galaxy S5 Supported Models/Variants & Download Links
    klte - SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
    klteactivexx - SM-G870F
    kltechn - SM-G9006V, SM-G9008V
    kltechnduo - SM-G9006W, SM-G9008W
    klteduos - SM-G900FD, SM-G900MD
    kltedv - SM-G900I, SM-G900P
    kltekdi - SCL-23
    kltekor - SM-G900K, SM-G900L, SM-G900S

    Use version 3.2.1-0 or newer of TWRP

    How to install?
    • Download the latest TWRP version
    • Download the latest build
    • Reboot to recovery
    • Flash the latest build
    • Reboot

    Download Links
    ROM: https://download.lineageos.org/
    GApps: https://wiki.lineageos.org/gapps.html
    TWRP: https://twrp.me/samsung/samsunggalaxys5qualcomm.html

    Credits
    Many thanks to the LineageOS team and all the contributors out there in the community
    @haggertk Official Maintainer

    Source Code :
    Github: https://github.com/LineageOS
    Code Review: https://review.lineageos.org/

    Android Version: 9.x Pie
    29
    when testing for mobile data wifi can't be turned on it does not make it credible to other devs that are trying to figure out why this is happening on only one variant , so what you have displayed there is not credible to us . Wifi needs to be completely off and you must show and app or a page or a file being downloaded only from mobile data . Because I work with bruno ( im on the kernel side of things ) and we keep seeing reports like this ) but I also have a vzw and i cannot reproduce this at all . so we need to figure out is it SIM data or CDMA data or is it certain Provider's data that are working , is it different bands that are somehow allowing data to slip by into the device ect.... do understand we are hoping to help all oher variants to gain data as well so we def need your help .

    And the actual klte* maintainer cannot reproduce non-working mobile data. On both a G900F with GSM service and a G900V with actual VZW service. CDMA data is the same as SIM data. Bands don't let data "slip by".

    Now, I got an email that indicated that it seemed that IPv6 mobile data is working and IPv4 isn't. That's a curious, and plausible, finding. Maybe those with non-working mobile data want to report status related to that. Note that if people want to relay things to me then I only care about results on builds that I create (read: I know what went into them).

    Edit -- OK, pretty sure I got it. I'll upload a build in a bit.

    Edit 2 -- Uploaded
    26
    Ok guys, pretty sure we figured out what's causing the boot issues on a whole variety of devices (op2, op3, klte* that isn't klte). Should be fixed in tomorrow's build.
    21
    Could you guys running haggertk's 16.0 beta build 2018-11-08 check under About phone & tell me the SELinux status please?

    haggertk is a lazy moron and hasn't worked out sepolicy for P yet, so it's still permissive as forced by https://review.lineageos.org/#/c/224917

    More seriously, I hope to finally iron out policy this week. Been busy and wanted to do it right.

    Regarding how important is it - I do not run devices as daily drivers without being enforcing. Quite a few security vulnerabilities are mitigated by selinux and legacy devices with legacy blobs can use belts and suspenders.

    Sent from my PH-1 using Tapatalk
    19
    No, hotspot is not working...
    Yeah, I forgot to go back and re-test after setting selinux to enforcing. I'll re-spin builds today to fix that.

    Sent from my SM-N900T using Tapatalk