• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[OFFICIAL] LineageOS 18.1 for the Samsung Galaxy S4 (All QCOM Variants)

Search This thread

npjohnson

Recognized Developer
Seeing several reports about the OTA updates giving issues and it being apparently solved in the 210415 build, I would like to share an observation - and thank the developers for all their work!

On an I9505 (jfltexx) which I upgraded via dirty flash from 17.1 to 18.1, I wasn't able to export the downloaded 210422 update what I tend to do on that device before installing. Wasn´t possible resulting in an error - I checked on permissions and also reset all data of the updater (not settings). After successful OTA update to 210422 (had done the update before on another I9505 without issues and therefore dared to do even with this error), it was possible to export.
Fixed exporting updates. Current build should be able to.
 

Lycon70492

Senior Member
Sep 19, 2016
69
6
Currently running official lineage os 17.1 on the jfltexx (GT I9505) and official twrp 3.4.0.0.

Is there anything in particular I should do before installing lineage os 18.1; for example, version of official twrp to use, twrp format data etc?
 

kurtn

Senior Member
Jan 28, 2017
4,075
1,766
Small town in Bavaria
Currently running official lineage os 17.1 on the jfltexx (GT I9505) and official twrp 3.4.0.0.

Is there anything in particular I should do before installing lineage os 18.1; for example, version of official twrp to use, twrp format data etc?
You are good to go. If you want to format data, do it. If you don't, all your apps and data will survive. Except email.

If you had GApps installed and don't format, you need to flash android 11 GApps immediately after 18.1
 
  • Like
Reactions: pocketrule

karlico

Member
Nov 1, 2017
12
3
Thanks for this great rom! Getting the newest android on this 2013 phone is just amazing.

I installed the newest lineage recovery, from 2021-05-13, and it wouldn't flash the OS succussfully. Tried with the OS versions from 2021-04-22 and 2021-05-13. Outputs from the abd sideloading below(phone). The phone would then reboot back to stock rom. On the computer side the adb output updates stopped at 94%. I believe the first 2 red lines with errors(phone) popped up at 47% and the next identical ones at 94%

Then I installed twrp instead of lineage recovery. ABD sideloading the OS went absolutely fine. And as the instruction says I did get the following error message which is fine: "If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."

s4 version is GT-I9505.

EDIT: Managed to boot into stock recovery instead of lineage recovery. Because I booted stock rom after flashing lineage recovery.

IMG_20210513_224646.jpg
 
Last edited:

rw_on_xda

Senior Member
Jun 24, 2013
306
161
Berlin
...
I installed the newest lineage recovery, from 2021-05-13, and it wouldn't flash the OS succussfully. Tried with the OS versions from 2021-04-22 and 2021-05-13. Outputs from the abd sideloading below(phone). The phone would then reboot back to stock rom. On the computer side the adb output updates stopped at 94%. I believe the first 2 red lines with errors(phone) popped up at 47% and the next identical ones at 94%
...
does the sha256 checksum of the downloaded LOS match ?
 
  • Like
Reactions: pocketrule

x2k13

Senior Member
Thanks for this great rom! Getting the newest android on this 2013 phone is just amazing.

I installed the newest lineage recovery, from 2021-05-13, and it wouldn't flash the OS succussfully. Tried with the OS versions from 2021-04-22 and 2021-05-13. Outputs from the abd sideloading below(phone). The phone would then reboot back to stock rom. On the computer side the adb output updates stopped at 94%. I believe the first 2 red lines with errors(phone) popped up at 47% and the next identical ones at 94%

Then I installed twrp instead of lineage recovery. ABD sideloading the OS went absolutely fine. And as the instruction says I did get the following error message which is fine: "If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."

s4 version is GT-I9505.

View attachment 5308701
from https://wiki.lineageos.org/devices/jfltexx/install

5. Sideload the LineageOS .zip package:
  • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
  • On the host machine, sideload the package using: adb sideload filename.zip.

    Tip: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success.
The output on your display, Manual Mode...I've never seen that during sideloading. 🤔
 

karlico

Member
Nov 1, 2017
12
3
does the sha256 checksum of the downloaded LOS match ?
I'm pretty sure I checked the checksum for OS zip files. I am trying to recheck now. The 05-13 version is fine. However the os version I flashed secondly, yesterday, was not 04-22, but 04-15 according to my local file. I am not able to find the checksum of that version anymore as it is not listed on the official download site. Weird I guess.

I did not check the checksum for lineageos recovery file.
from https://wiki.lineageos.org/devices/jfltexx/install

5. Sideload the LineageOS .zip package:
  • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
  • On the host machine, sideload the package using: adb sideload filename.zip.

    Tip: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success.
The output on your display, Manual Mode...I've never seen that during sideloading. 🤔

I used those installation instructions step by step. But had to use another computer after I'd installed lineage recovery as I was not able to get adb to work on the first computer.
The menu on lineage recovery did not match the instructions 100% . I had an option directly from the main menu that said "Apply update from ADB" which I used.
 

x2k13

Senior Member
I'm pretty sure I checked the checksum for OS zip files. I am trying to recheck now. The 05-13 version is fine. However the os version I flashed secondly, yesterday, was not 04-22, but 04-15 according to my local file. I am not able to find the checksum of that version anymore as it is not listed on the official download site. Weird I guess.

I did not check the checksum for lineageos recovery file.


I used those installation instructions step by step. But had to use another computer after I'd installed lineage recovery as I was not able to get adb to work on the first computer.
The menu on lineage recovery did not match the instructions 100% . I had an option directly from the main menu that said "Apply update from ADB" which I used.
Are you running Windows or Linux on the computer you use to connect to the phone via adb? Asking bacause on Linux using adb is really stable and easy to setup, it's in the package repos of all major distros.

I used to do it on Windows but that drove me nuts, always something that didn't work as it should.
 
  • Like
Reactions: pocketrule

karlico

Member
Nov 1, 2017
12
3
Are you running Windows or Linux on the computer you use to connect to the phone via adb? Asking bacause on Linux using adb is really stable and easy to setup, it's in the package repos of all major distros.

I used to do it on Windows but that drove me nuts, always something that didn't work as it should.
I'm using windows on the computer I first tried to sideload the OS. Was not able to get that to work out.

Then I switched to a linux computer. And yeah a flawless ADB experience.
 

rw_on_xda

Senior Member
Jun 24, 2013
306
161
Berlin
I'm pretty sure I checked the checksum for OS zip files. I am trying to recheck now. The 05-13 version is fine. However the os version I flashed secondly, yesterday, was not 04-22, but 04-15 according to my local file. I am not able to find the checksum of that version anymore as it is not listed on the official download site. Weird I guess.
...
yup, checked that by just exchanging the numbers of another checksum link.

why weird ?
I guess nobody will download an month old file, even when in newer one's security patches went in.
It would just waste storage (summing all devices over time with each ~0.5 GB in size per week)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    in my experience the early versions of 18.1 seemed better.
    in the last 5 or 6 versions the phone often has slowdowns and blocks that were not there before. It is well known that microsd used as an external space with android 11 (you can't save data like offline maps or other as other have said) has problems unfortunately.
    I would like to believe you but in my situation it is the opposite...sorry for my english...
    I`m with @vip5912.
    18.1 runs very smooth for me. No slowdown etc. Just a single reboot while due to a very RAM-intensive app.
    I put a 128gb-sdcard in but didnt adopt it and apps like OpenCamera or osmand (Navigation-app) are able to use the external sdcard as storage for Images or offlinemaps. (the only downer is my provider which STILL doesnt use AGPS on 4g and swithes down to 2g while on assisted gps. So no Onlinemaps "on the go").

    I hope this device will be supported longer. great work. If @arco has a support channel, i.e paypal or whatever, i would be willing to support it.

    Again, great work! Thank you!
    2
    I think lineage 17.1 is better than 18.1 at the moment
    sdcard is supported in 17.1, not here.
    for me 18.1 seems a downgrade respect 17.1....camera is very unstable and drain battery when remain blocked with the small icon in the upper bar.
    probably, android 10, is the last usable android version for our old s4
    I like 18.1.
    I use sdcard 32GB as Adopted Storage and I have many space in phone for new apps.
    I have no problems with camera and my (not new) battery is enough for one day of daily apps (phone, mails, messengers, news etc).
    18.1 is more stable as 17.1 in my opinion.
    I hope we will have support for this ROM as minimum 1 year (security updates) because new Android 12 is only for 64 bit phone (not for our 32 bit phone).
    2
    Would be nice to update OP with the hint that /G is still good for noGApps setup.
    Done.
    2
    currently can't install microg on lineage 18.1 jfltexx and ks01ltexx
    so I use microg lineage 17.1 with patched services.jar
    Just tried. Signature spoofing works with magisk modules "riru" and "riru lsposed" and that xposed module

    .. and it survives dirty lineageOS update
    1
    Hello guys,
    Does anyone else experiencing cracky-laggy-delay sounds in videos? Mostly in videos at browsers outside youtube.
    I have same problem

    *update from LOS 2021-07-08
    Fixed this issue!
    Also fixed Open apps strange closing Problem, good job people :)
  • 21
    lineage-os-logo.png

    Samsung Galaxy S4

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for all Galaxy S4 variants.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    • jactivelte (GT-I9295)
    • jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
    • jfltespr (SCH-R970/C/X, SPH-L720)
    • jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
    • jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
    • jfvelte (GT-I9515/L)

    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • MHL doesn't work after LineageOS 14.1, and likely never will again, as Google dropped support for it platform-wide in AOSP.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
    Kernel Source: https://github.com/LineageOS/android_kernel_samsung_jf
    6
    thanks for response and support
    This issue is now fixed. You will need to sideload the upcoming build by hand to get back on track though.

    Sorry for the inconveniences.
    5
    Good news, my GT-I9505 is updating automatically at this moment ("Update recovery" option disabled).
    Next step, activate the option to update the recovery and see if this works well.
    Thanks @npjohnson for your incredible work
    the recovery image updates the second you check the box.

    after you update OS, it updates the recovery on the next boot during boot animation.

    Have fun! Good to hear.
    5
    USB otg is unfortunately broken at the moment. But you can get access to your external storage by installing MiXplorer (which I recommend in any case) and "enable otg" in settings -> more settings
    Should be fixed in next build.
    4
    many thanks all developers - great work.

    i had dirty flashed from official 17.1 with 65 installed apps yesterday
    (SAMSUNG_I9505)

    rebooted to TWRP (twrp-3.5.1_9-0-jflte)
    0. wiped only system/dalvic/cache:
    1. flashed LOS (lineage-18.1-20210401-nightly-jfltexx-signed.zip)
    2. MindTheGapps-11.0.0-arm-20210328_143701
    3. magisk 22.0

    everything works well.


    but there was to much google-apps.

    i had unzipped MindTheGapps-11.0.0-arm-20210328_143701
    and reduced apps like "open_gapps-arm-pico"

    deleted:
    system/product/app/GoogleTTS
    system/product/app/talkback
    system/product/priv-app/AndroidAutoStubPrebuilt
    system/product/priv-app/Velvet

    and zipped again "MindTheGapps-11.0.0-arm-20210328_reduced"

    also once again

    0. wiped only system/dalvic/cache - rebooted to TWRP:
    1. flashed LOS 18.1
    2. MindTheGapps-11.0.0-arm-20210328_reduced
    3. magisk

    everything works well for now.