[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017]

Search This thread

Michi_BS

Member
Aug 25, 2016
20
6
Basel
Build contains latest wpa_supplicant patches.
Link see signature.

Edit: Probably has some probs, my phone calls are muted, no mic, no speaker. Anybody else?
Edit2: Works now, new image uploaded.
https://www.androidfilehost.com/?fid=889964283620759082

Thank you for your builds. :good: I have running 20171009 at present and seems to be stable for me. The only thing that bothered me was that sometimes the phone showed a "bluescreen" with time and date, but no way to log in again (had to remove battery to reboot). Finally I found that this was caused by the activated "Flip cover" (dt. Klapphülle) which does not make sense to me as I don't have a flip cover with the built in magnet. After turning this option to OFF there were no more blocked sessions like this .

BTW: How do you recommend to flash your latest build without loosing my app settings? Is it enough to flash over the existing build with TWRP and only to wipe dalvik/cache before rebooting?
 

Peregr1ne

Member
Jan 4, 2014
37
5
somewhere in Drenthe :)
Hi, you should better have posted a logcat for all your issues ;)

I've made my first few logcats - not sure how best to share them, posting full text will not be appreciated or even possible I think, in the album section I can only upload images (doh! ;))
Let me know if I can should look for some specific info in there, or if I should share them (happy to do so!)

When your last functioning build is/was > 0.5 years: did you notice there have been some essential changes in the device tree over the last months? BIG Kernel change to enforcing etc. ...
my question: what was your last stock rom you had installed? - MM? if not you'll surely run into the well known SIM issue, nearly everybody had it the time the kernel was changed. in your place i'd start from the beginning and wipe the cache and dalvik cache, flash the MM stock rom with Odin (let it fully boot into system!), and then TWRP + Lineage once again. :)
at my side i never had any of your described issues :cowboy:
we all never had to ASSERT lines removed from updater script in any way
:cowboy::D
To be perfectly honest, no did not notice anything like that, that is over and above my limited understanding of Android :confused::(

UPDATE: I noticed I'd not really answered your question wrt which version I had before flashing Lineage, to be perfectly honest I'm not sure, I pretty much flashed it right after I got the phone and never really used it before.
The shop where I bought it still has it for sale and lists it as running KitKat (Dutch webshop). Can I (easily) tell from the backup (e.g. recovery.log or one of the data or system files I made before starting the first flash) which version it was?

I think I may have done something that comes close to what you described but that resulted in the current situation :(
I flashed SamMobile firmware which I think was MM (the site lists it as 6.01 sammobile for sure it was stock recovery again - then I flashed TWRP, eventually the 3.1.1-1 and from there the Panzerknakker build, gapps and SU.
Before every major flash I wipe all but the external sd card, the only time when I did not wipe is in between flashing 14.1 and gapps.

Could you please confirm my understanding of your "recipe" ;) to be:
  1. flash back to MM (presumably by installing SamMobile firmware - or sould I go for one of my initial backups?)
  2. install TWRP (both this and previous steps via odin)
  3. make sure TWRP version 3.1.1-1 is flashed, not sure if I can do this in one step, if needed flash via TWRP while wiping all before
  4. after reboot into TWRP 3.1.1-1, wipe all but SD and flash 14.1 (e.g. Panzerknakker build, or more recent build posted recently)
  5. in same session/batch flash gapps
  6. wipe cache & dalvik, reboot
  7. install from google cloud all apps
  8. flash SU
  9. update SU binary &c
  10. from Titanium backup install old app data for some apps (requires SU/root

I've tried to line out the sequence as I think you are suggesting it - please let me know if somewhere I should do something differently or not at all :)

Cheers!
 
Last edited:

Andi46

Senior Member
Feb 7, 2016
238
131
Vechta
I've tried to line out the sequence as I think you are suggesting it - please let me know if somewhere I should do something differently or not at all :)

Cheers!
1. take the last stock FW for your country/eventually provider, no backup - before that go into TWRP and delete all partitions except external SD, in Odin maybe you have to flash a pit file too when flashing stock MM - let the phone fully boot and do the initial setup
4. i'm wiping cache,dalvik,system,data only
6. you just have to wipe cache & dalvik when you're updating an existing Lineage build - in your case don't do it when starting completely new with Lineage - just flash OS,GApps and SU (Magisk 14) in one rush - after that reboot without wiping anything more - the app Root Essentials automatically wipes cache and dalvik cache every time you're flashing a LOS update with it - attached pic...
10. I'm always using Titanium too, but in there just use the recovery of user apps, system things will break something...
to post your logs: i'm using Minimal ADB and fastboot from XDA https://forum.xda-developers.com/showthread.php?t=2317790 - just .rar or .zip the logs and upload them and eventually @hennymcc or someone else with more knowledge can tell you what's the reason
https://wiki.lineageos.org/logcat.html
 

Attachments

  • KMINILTE_EUR_OPEN_HIDDEN50M.rar
    963 bytes · Views: 24
  • Screenshot_20171023-154655.png
    Screenshot_20171023-154655.png
    96 KB · Views: 192
Last edited:

Panzerknakker

Senior Member
Jan 17, 2017
121
270
@Panzerknakker - could you please do a new build when Lineage fought the new vulneraty ,,KRACK'' ? I had read a Twitter post where they mentioned that it's defeated with ongoing builds :fingers-crossed:
or contains the new one already the fix? - lineage-14.1-20171023_071801-UNOFFICIAL-kminilte.zip - https://androidfilehost.com/?w=profile&uid=961840155545583234

wpa_supplicant has been fixed since 17.10.2017: https://forum.xda-developers.com/showpost.php?p=74189033&postcount=1445
Don't know if kernel fixes are necessary, too. Have no changes seen there.

---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------

What is the main obstacle for this ROM to become official?
 
  • Like
Reactions: Tek_No and Andi46

Andi46

Senior Member
Feb 7, 2016
238
131
Vechta
Last edited:

Panzerknakker

Senior Member
Jan 17, 2017
121
270
lineage-14.1-20171023_071801-UNOFFICIAL-kminilte.zip.md5su mwhy this file that it gives
You can copy the .zip and the .md5sum file into the same directory. TWRP then automatically calculates the hash value of the .zip and compares it with the one in .md5sum. This avoids installation of a corrupted .zip.
 

Panzerknakker

Senior Member
Jan 17, 2017
121
270
patch/hardware_samsung_ril/0001-add-support-for-ss222.patch
does not apply since 24.10.17.
Needs changes:
Code:
  ifeq ($(BOARD_MODEM_TYPE),xmm6260)
- LOCAL_CFLAGS := -DMODEM_TYPE_XMM6260
+ LOCAL_CFLAGS += -DMODEM_TYPE_XMM6260
  endif
 -ifneq ($(filter m7450 mdm9x35 ss333 tss310 xmm7260,$(BOARD_MODEM_TYPE)),)
 +ifneq ($(filter m7450 mdm9x35 ss222 ss333 tss310 xmm7260,$(BOARD_MODEM_TYPE)),)
- LOCAL_CFLAGS := -DSAMSUNG_NEXT_GEN_MODEM
+ LOCAL_CFLAGS += -DSAMSUNG_NEXT_GEN_MODEM
  endif
 
Last edited:

mense75

Member
Oct 29, 2017
9
0
hey guys :),
iam new to this forum but iam already following it since february... so first of all thanks to the people who dedicated their time and efforts to make this mod..

(iam not here to just commend)
so to get to my problem:
i flashed my phone to version 14.1 of 28/05/2017.. and since the update function in the actual system isnt working i check the forum from time to time to update my system...
so yesterday i decided to just flash over to ( lineage-14.1-20171022-UNOFFICIAL-kminilte) version, since flashing over the already exsisting mod worked just fine for me at previous updates...
but now my goolge apps wont work properly. the moment i reboot my phone , the error message " google services framework is not working" pops up over and over again and no google app is working..
and
also my file manager is gone, if i remember correctly their was one in the previous version so thats a problem too, since i can see the file manager app in the system setting under apps, but the icon is gone from the menu.
and
the phone got a bit juddery just as an example, when i use the left navigation button where usually the last opened apps show up it takes like 5 seconds to load the apps, which wasnt the case before.

so yeah that was all i noticed.. i googled some issues and checked the last 10 pages of the forum but i thought maybe someone experienced the same proplems as me..

thanks, your help is appreciated :good:
 

Jelsie

Member
Oct 6, 2017
30
3
hey guys :),
iam new to this forum but iam already following it since february... so first of all thanks to the people who dedicated their time and efforts to make this mod..

(iam not here to just commend)
so to get to my problem:
i flashed my phone to version 14.1 of 28/05/2017.. and since the update function in the actual system isnt working i check the forum from time to time to update my system...
so yesterday i decided to just flash over to ( lineage-14.1-20171022-UNOFFICIAL-kminilte) version, since flashing over the already exsisting mod worked just fine for me at previous updates...
but now my goolge apps wont work properly. the moment i reboot my phone , the error message " google services framework is not working" pops up over and over again and no google app is working..
and
also my file manager is gone, if i remember correctly their was one in the previous version so thats a problem too, since i can see the file manager app in the system setting under apps, but the icon is gone from the menu.
and
the phone got a bit juddery just as an example, when i use the left navigation button where usually the last opened apps show up it takes like 5 seconds to load the apps, which wasnt the case before.

so yeah that was all i noticed.. i googled some issues and checked the last 10 pages of the forum but i thought maybe someone experienced the same proplems as me..

thanks, your help is appreciated :good:


I would say: Did you wipe the Dalvik cache, the Cache, system and Data?
Most often this could be the case of your problem...
If you are going to wipe those 'partitions', it would be useful to make a backup with titanium backup (if your phone is rooted of course).
 

mense75

Member
Oct 29, 2017
9
0
I would say: Did you wipe the Dalvik cache, the Cache, system and Data?
Most often this could be the case of your problem...
If you are going to wipe those 'partitions', it would be useful to make a backup with titanium backup (if your phone is rooted of course).

well i wiped the dalvik cache after flashing but i didnt wipe cache, system and data..
i thought if i wipe dalvik cache it would be enough cause then i dont have leftover data from the previous version..
if i wipe the cache + system and data do i have to reflash something? and does it have that much of a risks that i need to make a back up ?
 

Jelsie

Member
Oct 6, 2017
30
3
well i wiped the dalvik cache after flashing but i didnt wipe cache, system and data..
i thought if i wipe dalvik cache it would be enough cause then i dont have leftover data from the previous version..
if i wipe the cache + system and data do i have to reflash something? and does it have that much of a risks that i need to make a back up ?

If you won't make a backup your in-app data will be lost unless it is online, your internal storage will not be touched if you don't wipe it either.
If i were you I would wipe the system too, to be sure erverything should be working fine.
 
  • Like
Reactions: mense75

mense75

Member
Oct 29, 2017
9
0
If you won't make a backup your in-app data will be lost unless it is online, your internal storage will not be touched if you don't wipe it either.
If i were you I would wipe the system too, to be sure erverything should be working fine.

so i wiped dalvik cache, cache, system, data afterwards i flashed lineageos 14.1 and open gapps and now nothing works..
when i start my phone i get endless error messages..
i think i will wipe internal storage now too since there is no other option..
 

Top Liked Posts

  • 2
    Security Patch Level April, plz try
  • 2
    Security Patch Level April, plz try
  • 59
    This is a LineageOS 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).

    DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE

    Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
    Hence please do not ask for support or ROMs for the G800H.

    Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.

    Working features
    • HW accelerated GUI
    • Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
    • MTP storage
    • Flash Light
    • Bluetooth (A2DP, HFP, HID)
    • IR
    • Sound
    • SMS
    • Initiate and receive calls
    • Wifi
    • Mobile Data
    • USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
    • NFC
    • Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
    • Light sensor (needed for auto-brightness)
    • Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
    • SD-Card as internal storage (new Android M feature)
    • GPS
    • Fingerprint scanner
    • SELinux

    Non-working features:

    Known issues:
    • Camera crashes when switching from camera to video. Use Google camera or Open camera to solve camera issues.
    • See the Bug Report section of this thread.

    Disclaimer:
    • You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
    • Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
    • Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
    • The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
    • It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
    • Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
    • Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
    Before you start:
    • Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.

    Download:

    Install recovery:
    • Reboot your device into Download mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
    • Confirm the following warning message with the Volume-Up button.
    • Connect your device to your PC via USB
    • Make sure the device driver's are installed on your PC
    • Start Odin
    • In Odin select "PDA" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
    • Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
    • Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
    • After the recovery flashing process was successful, power of your device, wait a few seconds and reboot into recovery mode (see instructions below).
    • Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.

    Before you flash:
    • You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
    • Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.

    Flash ROM:
    • Reboot into recovery mode (Press Volume-Up + Home + Power button)
    • If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
    • If you haven't copied the installation files yet, you can now copy the GApps and the ROM zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
    • Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
    • Install the CM ROM zip-package
    • Install the GApps zip-package

    How to root:
    LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
    After that root access is still disabled by default. If you want to activate root access for apps, do the following:
    • Open the Settings menu, select "About Phone"
    • Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
    • Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.

    In case you want to go back to the stock ROM:
    • lf you do not have the latest ROM for the G800F you can download it from SamMobile
    • Reboot your phone into Odin mode
    • Open Odin on your PC and connect your smartphone with your PC via USB
    • If you have a zip-file unzip it so that you have a .tar.md5 file
    • In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
    • Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
    • Reboot

    Changelog
    Code:
    Changelog:
    19/08/2017:
    * SELinux policy update
    * Update to newest LineageOS sources
    02/06/2017:
    * Firefox crash&reboot fixed (thanks to Spookcity)
    * Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
    * Ambient display option added (disabled by default)
    28/05/2017:
    * [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
    * Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
    * Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
    * Updated kernel to 3.4.107
    * Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
    * Updated LineageOS sources
    * FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
    * Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
    * Replaced the buggy Snap camera with the LineageOS default camera app
    * Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
    
    20/02/2017:
    * Fixed Youtube scaling issue on window resizing
    * Compass fixed (thanks to mirhciulica for figuring out what's wrong)
    * cpufreq config added
    * Charge mode fixed (starts when plugging USB into a powered-off phone)
    * USB-Tethering and Wifi SoftAP (Hotspot) fixed
    * Camera doesn't crash when switching between camera and video (but might still crash sometimes)
    * Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
    
    01/02/2017:
    * conversion to LineageOS
    * updated some libs with stock MM versions
    * fixed robotic voice problem
    * fixed silence on first call
    
    07/11/2016:
    * Initial test build

    This section is for developers:
    A README file with build instructions can be found here:
    Code:
    https://github.com/cm-3470/android_device_samsung_kminilte

    Sources:
    Code:
    https://github.com/cm-3470/android_device_samsung_kminilte
    https://github.com/cm-3470/android_vendor_samsung_kminilte
    https://github.com/cm-3470/android_kernel_samsung_kminilte
    https://github.com/cm-3470/android_device_samsung_smdk3470-common

    Developers welcome
    • At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
    • Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
    • Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.

    Thanks to CTXz, Psyafter, spookcity138, ayke and mirhciulica for working on this ROM.

    XDA:DevDB Information
    [G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017], ROM for the Samsung Galaxy S5 Mini

    Contributors
    hennymcc, Panzerknakker, spookcity138, psyafter, ayke
    Source Code: https://github.com/cm-3470

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
    Based On: LineageOS

    Version Information
    Status: Beta

    Created 2017-02-01
    Last Updated 2018-08-18
    21
    Hi there is a new build:
    https://www.androidfilehost.com/?fid=529152257862704787

    Changelog:
    • Fixed Youtube scaling issue on window resizing
    • Compass fixed (thanks to mirhciulica for figuring out what's wrong)
    • cpufreq config added
    • Charge mode fixed (starts when plugging USB into a powered-off phone)
    • USB-Tethering and Wifi SoftAP (Hotspot) fixed
    • Camera doesn't crash when switching between camera and video (but might still crash sometimes)
    • Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
    21
    Official TWRP 3.1.1

    I've worked together with the TWRP maintainers to make TWRP official, and it's finally here :D
    https://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-1-1-exynos-t3626646

    You can download it from here:
    https://twrp.me/devices/samsunggalaxys5miniexynos.html
    21
    A new build is available:
    https://www.androidfilehost.com/?fid=961840155545570720

    It turned out that the patch found by Spookcity not only fixes Firefox but also the fingerprint bootloop. So the new build should be usable again.
    As the initial bootloops probably were also caused by the fingerprints it should not be necessary anymore to wipe everything (although still recommended).

    Changes:
    • Firefox crash&reboot fixed
    • Enabling the fingerprint reader does not cause bootloops anymore
    • Ambient display option added (disabled by default)
    17
    A new build is available.
    https://www.androidfilehost.com/?fid=889764386195902448

    Changelog:
    Code:
    * Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
    * Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
    * Updated kernel to 3.4.107
    * Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
    * Updated LineageOS sources
    * FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
    * Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
    * Replaced the buggy Snap camera with the LineageOS default camera app
    * Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone