Yes I'm always careful to d/l the right package and flash it before first boot. 16.0 and 17.1 don't have the issue, there's nothing else I can do differently. As its seems to only be happening to one other person on here I'm going to assume its a DUOS specific issue as he doesn't mention which model he has, but if it were the G900F everyone would be reporting it.
Hi. Thanks for your reply but the 'insufficient space' problem is there before any backups are restored or changes are made. First boot as a new device, login to the Play store and updates immediatley fail with that message.For the insufficent memory issues:
Can be due to Adoptable Storage, despite enough free mem on internal & external storage.
But the S5 is also running out of space due to Los18. Many apps can no longer access sdcard, which some of them previously did w/o notice.
That was the(later discovered) reason that many of my apps would crash after being restored from a Los17 TB backup and had to be removed, reinstalled from Playstore and configured from scratch for some extra hours of fun. After that internal free mem had shrunk by about 2gbytes in my case.
During the days of Kitkat(4.4), Playstore required a minimum of 250mbytes of free internal flash to update or install a single app.
Early this year i ran into the same problem with a bit less than 900mbytes free on my now retired Acer tablet.
And camera may crash and require a reboot or even reformatting of the sdcard, if you set it to save to sd. Especially when switching between picture and movie mode,and orobably when altering flash modes.
If you're going towards 1GB or less of free internal mem now, consider uninstalling apps or use Adoptable Storage, which has its very own quirks and is probably not even possible with Los18(hasn't support for ExtFS on sdcards been removed? AS requires encrypted Ext4, i used it on Cm14 & Co for security reasons, with internal free mem still being plenty. But too many issues.
From the perspective of the ROM itself, all models function the same once you get it installed. The jailbreaking process turns whatever model you have into Google Play Edition(?) developer device, so no worries there. This is why the thread is named klte*.
Yes, the ROM is built weekly. New builds are posted at https://download.lineageos.org/klte
I haven't done that since 2016, so I don't know what the latest method is. I would not be of much help there.
Download Magisk 23 from here. Please flash this ZIP archive in TWRP. The phone will now restart. Go to the Magisk manager app and follow the further steps.
Sorry, there is so much misinformation.
The firmware is for people that did not update stock firmware for a long time. It seems like you did not unlock, yet. So search let your phone update first.
I noticed a bug appearing recently: after expanding the Status bar quick tile curtain if you long press the clock the Trebuchet launcher/U.I. crashes... Same with shortcuts like Wi-Fi, Location, etc. instead of opening the corresponding settings panel.
Thanks a lot! I have now downloaded the two roms listed for my phone, and one is with four binary files (edited). New edit: I couldn't wait until the morning and flashed the four binary file. It passed! Still the phone doesn't boot, but now I see some light in the end of the tunnel. Thanks to all you good people for advice!This is where I got my 4 file set from:
Samsung Galaxy S5 Duos a complete list of...sfirmware.com
My SM-G900F is listed as Duos but I don't think that's correct. Anyway, have fun searching.
|klte||SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8|
|kltechnduo||SM-G9006W, SM-G9008W, SM-G9009W|
|kltekor||SM-G900K, SM-G900L, SM-G900S|
It's (likely) not. I've found an issue in the legacy paths of the recent sdfat (Samsung exfat driver) revision. I haven't been able to recreate the bug/assert after the fix. After getting a second confirmation I'll upload the merge the change.SDcard corruption may be caused by a recent Google security patch. I experienced this once with the "new" unofficial LOS17 for the Samsung P605, coming from unofficial 14.1,where this never happened before. But others started complaining about the same issue, after this antique rom got a recent security patch.