[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1

Search This thread
By:
Advanced…
RagingHarry

RagingHarry

Senior Member
Jan 8, 2012
825
328
Havelte
Really like the 31/8 build.
No probs with fingerprint.
---
Upgraded
Flash twrp img in recovery, reboot recovery.
Boot to download, odin mentioned AP and BL, boot system, reboot recovery, flash 31/8
Runnining super smooth.



Sent from my gts4lvwifi using XDA Labs
 
T_I

T_I

Senior Member
Mar 22, 2012
903
1,269
LuK1337 said:
You can use https://build.twrp.me/twrp-3.4.0-0-gts4lvwifi.img until -4 is out.
Click to expand...

Thanks. This TWRP image, combined with info from this issue got my TWRP backup working for main and work profile again. Setting the same pin twice instead of using 1 pin and set option 'use one lock' enabled me to decrypt both main and work profile.

It's still a hassle, but changing to the same lock twice instead of use one lock will do while making backups. This was no image issue, but a TWRP one.
 
L

lewmur

Senior Member
Apr 30, 2011
1,725
364
LuK1337 said:
Unlikely.
Click to expand...
I see from the TWRP site that you are the maintainer for the S5e, so if you say "Unlikely", I'll take it as the "final word".:D I'll just have to wait. With the amount of storage and RAM this tablet has, the "Samsung Bloat" isn't as big a deal as it was on earlier models, so waiting isn't a problem.:)
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,278
16,587
Samsung Galaxy S III I9300
Moto G 2014
lewmur said:
I see from the TWRP site that you are the maintainer for the S5e, so if you say "Unlikely", I'll take it as the "final word".:D I'll just have to wait. With the amount of storage and RAM this tablet has, the "Samsung Bloat" isn't as big a deal as it was on earlier models, so waiting isn't a problem.:)
Click to expand...

Well it'll mostly work but don't expect it to decrypt userdata, also stock rom might hate you for custom recovery.
Also idk what you're going to wait for, I'm not going to invest time into stock rom...
 
L

lewmur

Senior Member
Apr 30, 2011
1,725
364
LuK1337 said:
Well it'll mostly work but don't expect it to decrypt userdata, also stock rom might hate you for custom recovery.
Also idk what you're going to wait for, I'm not going to invest time into stock rom...
Click to expand...
If it will install so that I can then format the data partition and poceed to flash either LOS 17.1 or your cDroid ROM, then that's all I want. :fingers-crossed: The whole point is to get away from stock.
 
N

nsx2brz

Senior Member
Nov 4, 2014
71
33
Another successful update

Updated to latest version from August 31st, no issues to report that haven't been already....

- Flashed updated twrp-3.4.0.0 from twrp-3.3.2.2
- Flashed updated AP and BL from Odin
- Flashed updated lineage-17.1-20200831-nightly-gts4lvwifi-signed.zip from twrp
- Wiped Cache and Dalvik (not sure that it is necessary)
- Rebooted

I have Magisk 20.3 and Viper's Audio installed, it kept the installation of both. Waiting for the fix for the magnetic switch for the book cover which is coming in the next build.

Thx!!!
 
T

truc113

Member
Dec 8, 2010
31
22
Trifouilly-les-Oies
F2FS file system support gone?

Hi all,
first many thanks @LuK1337 for your amazing work maintaining this great tablet!

I'm using it with a F2FS formatted sdcard (better speed than exfat + some other better stuff).
until 24/08 build all was ok, I could read/write my sdcard without issue.

from 24/08 build, with the firmware update etc, there probably are many kernel changes I suppose (according to your github),
now my sdcard is no longer accessible, logcat shows that F2FS is now unsupported...
same happen with your newest twrp, though I can't remember if I could ever read F2FS in it before

indeed in your kernel repo (and in the lineageos one, which is basically the same)
F2FS is not enabled nor even mentioned in the defconfig files.

is it intentional or just some side effect of a big merge? (in that case there might be other things dropped unintentionally)
could it be enabled again please :crying: ?
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,278
16,587
Samsung Galaxy S III I9300
Moto G 2014
truc113 said:
Hi all,
first many thanks @LuK1337 for your amazing work maintaining this great tablet!

I'm using it with a F2FS formatted sdcard (better speed than exfat + some other better stuff).
until 24/08 build all was ok, I could read/write my sdcard without issue.

from 24/08 build, with the firmware update etc, there probably are many kernel changes I suppose (according to your github),
now my sdcard is no longer accessible, logcat shows that F2FS is now unsupported...
same happen with your newest twrp, though I can't remember if I could ever read F2FS in it before

indeed in your kernel repo (and in the lineageos one, which is basically the same)
F2FS is not enabled nor even mentioned in the defconfig files.

is it intentional or just some side effect of a big merge? (in that case there might be other things dropped unintentionally)
could it be enabled again please :crying: ?
Click to expand...

Ehh i don't like f2fs...but i reenabled it. BTW it was Samsung that disabled it.
 
W

wapok147

New member
Sep 2, 2020
3
0
Hi there, after 31 Aug build downloaded and the tablet rebooted, when TWRP asked for the PIN code, I wrongly clicked "cancel", then it still installed the update but the fingerprint reader doesn't work anymore.
What should I do? Should I run the update again using the ADB / Sideload method?
 
V

vafele

Member
Feb 2, 2017
40
16
hi. i bought this tablet for its great display but am dissapointed in general use responsiveness. every swipe feels slow and juddery. will going from stock to lineage rom solve this issue? it is hard to blame the hardware for this since its decent, so my guess is stock rom might be at fault
 
LuK1337

LuK1337

Recognized Developer
Jan 18, 2013
8,278
16,587
Samsung Galaxy S III I9300
Moto G 2014
vafele said:
hi. i bought this tablet for its great display but am dissapointed in general use responsiveness. every swipe feels slow and juddery. will going from stock to lineage rom solve this issue? it is hard to blame the hardware for this since its decent, so my guess is stock rom might be at fault
Click to expand...
Just try it out. If anything you can always go back to stock and relock the bootloader.
 
You must log in or register to reply here.

Similar threads

LuK1337
[ROM][OFFICIAL][gts4lvwifi][11] LineageOS 18.1
Replies
183
Views
27K
_nKo_
_nKo_
LuK1337
[ROM][UNOFFICIAL][gts4lvwifi][9] LineageOS 16.0
Replies
257
Views
32K
T
tek3195
8
[ROM][GTS4LVWIFI][10]LuisROM Android 10 based on crDroid V6.x
Replies
232
Views
19K
M
metaxda
bgcngm
[ROM][DISCONTINUED] LineageOS 17.1 for Samsung Galaxy Tab S5e (LTE)
Replies
85
Views
7K
S
starbright_
8
[KERNEL][PIE/TEN]LuisKERNEL Linux 4.9.215 for GTS4LVWIFI & GTS4LVLTE devices
Replies
117
Views
17K
M
mrdark5555

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    D
    denisovich
    D4rkAn9el said:
    Well… It was working. After a few reboots and installing among other things Magisk, afwall and EdXposed, I'm again with no sound and no screen rotation… full logcat from boot until unlock here https://paste.ubuntu.com/p/Cmmbf7kxqp/
    looks like /system/bin/audioserver crashes this may explains the sound problem but not the rotation one.

    Any one knows how to solve those issues?
    Click to expand...
    Uninstall EdXposed has to be the very first thing any sane person would do. It is known to be the source of endless headaches and badness.

    LineageOS does not just do random things and stop working without any reason. You need to reverse whatever you did that made things not work, and then figure out how to live without them.

    I would estimate that around 75% of all complaints about "this ROM has stopped working" are self-inflicted wounds. And it is quite frankly just pollution in the forums.
    View
    1
    LuK1337
    LuK1337
    ghnue said:
    On my end flashing CTK1 did end up with :
    - no sound (volume rocker was fine though)
    - no rotation
    - no video decoding
    - long boot time
    was still on 17.1.
    Flashed 18.1, behavior did not change.
    Flashed CTI1, problems aforementioned disappeared. (while keeping 18.1, no userdata format)
    Was previously on what seems to be a mix of ATE3 and BTG3.
    Now I guess I'm ATE3/CTI1.
    Might be because of me flashing manually with TWRP (BTG3 and later) so not everything may be writable.
    Click to expand...
    You can't flash firmware with twrp.
    View
  • 37
    LuK1337
    LuK1337
    2okPze5.png


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

    Instructions :
    • Download the latest build and gapps
    • Reboot to recovery
    • Flash the latest build and gapps
    • Reboot
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code: 
    What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
 
Did you--
wipe:
 restore with titanium backup:
reboot after having the issue:
 
Are you using--
a task killer:
a non-stock kernel:
other modifications:
 
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

    XDA:DevDB Information
    [ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1, ROM for the Samsung Galaxy Tab S5e

    Contributors
    LuK1337
    Source Code: https://github.com/LineageOS

    ROM OS Version: Windows 8 Mobile

    Version Information
    Status: Testing

    Created 2019-09-24
    Last Updated 2020-04-01
    View
    18
    LuK1337
    LuK1337
    -- bit more friendly stock -> lineage instructions --

    1. Unlock the bootloader
    - Connect to WiFi network
    - Enable OEM Unlock in developer options
    - Turn off the tablet
    - Boot to download mode manually by plugging in USB and holding all the buttons for few seconds
    - Follow instructions on the screen
    2. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
    3. Flash custom VBMeta image ( https://dl.twrp.me/gts4lvwifi/vbmeta.tar.html ) in Odin ( use AP slot )
    4. After flashing VBMeta, boot to stock. It'll likely ask you to wipe data, if so do that
    5. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
    6. Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it's flashed
    7. Install Lineage × whatever else you need ( gapps, addon-su, ... )
    8. Format data
    9. Reboot ( make sure to not install TWRP app when TWRP asks you to )

    ---

    Also Odin download for those who can't find it on their own https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip
    ( sha1sum 1057496afa34bfdf7e77caf0b99207dca77fcb2d )
    View
    7
    LuK1337
    LuK1337
    Builds 20200824+ depend on Android 10 firmware, and thus from now on the recovery will abort the installation if you're still on Android 9 one.

    You can update the firmware by flashing following Odin package: https://github.com/luk1337/gts4lv-fw/releases/tag/T720XXS2CUA3.

    After the firmware update you should be able to flash newer builds.
    View
    6
    LuK1337
    LuK1337
    Hi, 20190928+ OpenGapps builds should work just fine without doing anything special. B-but there's a catch, you'll need to update to TWRP 3.3.1-4 or newer ^.^
    Have fun~!

    ---

    Also OpenGapps apparently moved their builds there ~ https://sourceforge.net/projects/opengapps/files/arm64/beta
    View
    5
    LuK1337
    LuK1337
    EugenStanis said:
    Do you think there is chance lineage based on android 11 will support this tab?
    Click to expand...
    No comment.
    View

New posts

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