[KERNEL][PIE/TEN]LuisKERNEL Linux 4.9.215 for GTS4LVWIFI & GTS4LVLTE devices

Search This thread

DarkBuf0n

Member
Dec 11, 2018
7
0
Great kernel.
Thank you for your work.
2 errors on my device:
Volume control from headphones.
Screen rotated in GCAM.

Request / Suggestion
If it is possible to activate the HDR function of the screen?

Thank you
 
Jul 1, 2012
20
6
Networking Filesystem

Does this kernel include any networking file system (cifs/nfs) ?
If not, is it possible to include this, or is there already any existing kernel available ?
 

Zer0Sense

Member
Dec 8, 2013
11
2
Could somebody help.
Installed this from TWRP on my S6 Galaxy Tab into boot partition. Can't start device neither enter the download mode. Could something be done?

Solved: with wire could enter download mode and flash TWRP
 
Last edited:

Lord Sithek

Senior Member
@TiTiB
Hello bro. I know you have great experience in rooting S5e Tab. I still hesitate to do it because I don't have much experience with rooting Samsung devices. Actually, I'm bit scared reading of all people's issues here and there... So I'd like to ask few questions and if you'd be so kind to answer, I'd be very grateful :)
1. Do you use or have used Luis kernel? If yes, does it present any issues interrupting daily use? I know about PC connection issue and I'm not sure if it's been resolved yet. I see this kernel was updated several times (latest update from May), but I didn't find straightforward answer if this issue is resolved. This kernel seems to good way to introduce root, but too many uncertainties :eek:
2. If I'm going to flash TWRP, is it better to do it BEFORE rooting with Magisk (but after flashing VBMeta with Odin), like suggested in the OP here, or should I root the tablet following AHE_XDA's tutorial and only then try to introduce TWRP?
3. Is it necessary/important/helpful to pre-root TWRP image with Magisk before flashing it, like suggested here: https://twrp.me/samsung/samsunggalaxytabs5ewifi.html ? I don't find any other mention of this method on XDA, but it is strongly recommended on the official TWRP site...

Thank you in advance for your patience with noob :cyclops:
 
Last edited:

TiTiB

Senior Member
Jun 19, 2015
852
603
Earth
@TiTiB
Hello bro. I know you have great experience in rooting S5e Tab. I still hesitate to do it because I don't have much experience with rooting Samsung devices. Actually, I'm bit scared reading of all people's issues here and there... So I'd like to ask few questions and if you'd be so kind to answer, I'd be very grateful :)
1. Do you use or have used Luis kernel? If yes, does it present any issues interrupting daily use? I know about PC connection issue and I'm not sure if it's been resolved yet. I see this kernel was updated several times (latest update from May), but I didn't find straightforward answer if this issue is resolved. This kernel seems to good way to introduce root, but too many uncertainties :eek:
2. If I'm going to flash TWRP, is it better to do it BEFORE rooting with Magisk (but after flashing VBMeta with Odin), like suggested in the OP here, or should I root the tablet following AHE_XDA's tutorial and only then try to introduce TWRP?
3. Is it necessary/important/helpful to pre-root TWRP image with Magisk before flashing it, like suggested here: https://twrp.me/samsung/samsunggalaxytabs5ewifi.html ? I don't find any other mention of this method on XDA, but it is strongly recommended on the official TWRP site...

Thank you in advance for your patience with noob :cyclops:
1. I've only used LOS 15.1 and its default everything. FWIW, I've used, and, loved Luis's ROMs on other devices in the past.
2. I followed AHE_XDA's tutorial exactly (I helped him write/test it), so I added TWRP *after* Magisk root.
3. iirc, and that is definitely questionable, I used the TWRP app (the only time I've used it, I think) to test it so we could then recommend an easy TWRP install method to others. Not sure if this made it to the thread though.

All in all, if you follow the guide *exactly* you shouldn't have any problems. But if you do, there are also instructions to go back to stock; which I had to do 3 or 4 times during the testing phase.

I've rooted 5 different Samsung devices and am of the opinion that it's *very* unlikely that you'll brick your S5e. And I use the term "brick" in the way it is meant to be used; render your device completely unrecoverable/dead "As useful as a brick". BTW, there is no such a thing as "soft brick". It's like someone being "kinda dead"; you either are, or are not.
 

Lord Sithek

Senior Member
1. I've only used LOS 15.1 and its default everything. FWIW, I've used, and, loved Luis's ROMs on other devices in the past.
2. I followed AHE_XDA's tutorial exactly (I helped him write/test it), so I added TWRP *after* Magisk root.
3. iirc, and that is definitely questionable, I used the TWRP app (the only time I've used it, I think) to test it so we could then recommend an easy TWRP install method to others. Not sure if this made it to the thread though.

All in all, if you follow the guide *exactly* you shouldn't have any problems. But if you do, there are also instructions to go back to stock; which I had to do 3 or 4 times during the testing phase.

I've rooted 5 different Samsung devices and am of the opinion that it's *very* unlikely that you'll brick your S5e. And I use the term "brick" in the way it is meant to be used; render your device completely unrecoverable/dead "As useful as a brick". BTW, there is no such a thing as "soft brick". It's like someone being "kinda dead"; you either are, or are not.
Thanks a lot for your answer. Yea, I think I'll just follow the main root instruction and will give a thought to TWRP only then - if it is really necessary in my case... Yesterday I've read all the "Root instructions" thread and I encountered Extall's method with TWRP App (I think this is what you meant) and sounds promising.

If you don't mind, I would have just two more minor questions, just to make sure :)
1. Assuming I'm rooted without TWRP, if ever something goes wrong and I'm stuck on bootloop, what should I do to recover without loosing all data? Should I flash in Odin magisk_patched.tar prepared during the rooting process and that's all?
2. Have you ever tried to update the stock rom after rooting without erasing user data? I saw somewhere brief instruction on how to do it, but I want to make sure if it is safe and you seems to me competent guy to ask this question :D

Thanks again!

Sent from my mido using XDA Labs
 
Last edited:

MikyMuch

Member
Feb 9, 2019
8
0
The performance is beter compared to the stock kernel, but I found this bugs:
1. The tablet screen does not turn off when closing the cover.
2. Sometimes the system ui process stops working.

One sugestion, adding the possibility to overclock would be great for gaming I know the tablet is not designed for gaming but the temperatures are great.
Anyways, excelent work and thank you.

Edit: I use magisk 20.4 with busybox and fde.ai app, without fde.ai the system ui doesn't almost crash.
 
Last edited:

masad8

Member
Jun 6, 2019
8
0
While building the kernel source using linaro 4.9 toolchain, I am getting the following error:

CC crypto/memneq.o
security/selinux/hooks.c: In function 'selinux_inode_copy_up':
security/selinux/hooks.c:3812:19: warning: 'sid' may be used uninitialized in this function [-Wmaybe-uninitialized]
error, forbidden warning: hooks.c:3812
scripts/Makefile.build:339: recipe for target 'security/selinux/hooks.o' failed
make[2]: *** [security/selinux/hooks.o] Error 1
scripts/Makefile.build:653: recipe for target 'security/selinux' failed
make[1]: *** [security/selinux] Error 2
Makefile:1094: recipe for target 'security' failed
make: *** [security] Error 2
make: *** Waiting for unfinished jobs....


---------- Post added at 05:05 PM ---------- Previous post was at 04:48 PM ----------

With Linaro 7.5, I get the following error:

CC fs/xattr.o
fs/namespace.c: In function ‘vfs_kern_mount’:
fs/namespace.c:1223:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
error, forbidden warning: namespace.c:1223
scripts/Makefile.build:339: recipe for target 'fs/namespace.o' failed
make[1]: *** [fs/namespace.o] Error 1
make[1]: *** Waiting for unfinished jobs....
CC mm/compaction.o
CC kernel/bpf/percpu_freelist.o
CC kernel/bpf/stackmap.o
CC mm/vmacache.o
CC mm/interval_tree.o
Makefile:1094: recipe for target 'fs' failed
make: *** [fs] Error 2
make: *** Waiting for unfinished jobs....
 

Essentrix

Senior Member
Apr 4, 2013
870
176
Hi,
Been using this kernel since day one... Only thing I miss is further CPU governor options... Any chance they can be added in further version? Cheers

Sent from my SM-T720 using Tapatalk
 

Beninjam9

Member
Jan 4, 2015
5
1
1. I've only used LOS 15.1 and its default everything. FWIW, I've used, and, loved Luis's ROMs on other devices in the past.
2. I followed AHE_XDA's tutorial exactly (I helped him write/test it), so I added TWRP *after* Magisk root.
3. iirc, and that is definitely questionable, I used the TWRP app (the only time I've used it, I think) to test it so we could then recommend an easy TWRP install method to others. Not sure if this made it to the thread though.

All in all, if you follow the guide *exactly* you shouldn't have any problems. But if you do, there are also instructions to go back to stock; which I had to do 3 or 4 times during the testing phase.

I've rooted 5 different Samsung devices and am of the opinion that it's *very* unlikely that you'll brick your S5e. And I use the term "brick" in the way it is meant to be used; render your device completely unrecoverable/dead "As useful as a brick". BTW, there is no such a thing as "soft brick". It's like someone being "kinda dead"; you either are, or are not.

I followed AHE_XDA's tutorial to the letter with no issues, but after installing TWRP, I can no longer boot my device into a rooted state as TWRP boots instead as it uses the same key combo. Was this an issue for you?

Thanks in advance for your help :eek:
 

jckelsall

Member
Jan 22, 2014
6
0
I have the LTE version of the tablet (SM-T725 running android 10 (fully up to date), UK). The device is (so far) unmodified. It was bought through Vodafone, but has never had a network lock.

To give a general overview of my experience, I have rooted the majority of my android devices in the past, but this is my first Samsung device for a several years.

I have a few questions, I hope someone can answer them.

1 - Will unlocking the bootloader and installing this kernel/twrp/magisk, result in any features being lost? (Dex, HDMI, USB storage [plugging storage devices into the tablet], HD netflix, anything relating to knox, good lock, etc.)

1A - If any features will be lost, is it possible to restore them through, for example, a magisk module, and if so, which ones?

2 - Are there any apps I should expect to stop working completely?

3 - Is it possible to backup the tablet's data prior to unlocking the bootloader in a way that allows it all to be restored after installing this kernel/twrp/magisk?

4 - Is there anything else I should know before unlocking the bootloader and installing this kernel/twrp/magisk?

Thanks in advance to anyone who can offer any help in answering these questions.

Edit to add:

5 - How will future system updates work? Obviously OTA is out of the question, but what other methods are available?
 
Last edited:

guhvanoh

Senior Member
I have the LTE version of the tablet (SM-T725 running android 10 (fully up to date), UK). The device is (so far) unmodified. It was bought through Vodafone, but has never had a network lock.

To give a general overview of my experience, I have rooted the majority of my android devices in the past, but this is my first Samsung device for a several years.

I have a few questions, I hope someone can answer them.

1 - Will unlocking the bootloader and installing this kernel/twrp/magisk, result in any features being lost? (Dex, HDMI, USB storage [plugging storage devices into the tablet], HD netflix, anything relating to knox, good lock, etc.)

1A - If any features will be lost, is it possible to restore them through, for example, a magisk module, and if so, which ones?

2 - Are there any apps I should expect to stop working completely?

3 - Is it possible to backup the tablet's data prior to unlocking the bootloader in a way that allows it all to be restored after installing this kernel/twrp/magisk?

4 - Is there anything else I should know before unlocking the bootloader and installing this kernel/twrp/magisk?

Thanks in advance to anyone who can offer any help in answering these questions.

Edit to add:

5 - How will future system updates work? Obviously OTA is out of the question, but what other methods are available?
Most of your questions should really be asked in the Q & A section. Then head over to the Guides, News, & Discussion section to learn about rooting and stuff. Finally, return here for stuff on this kernel.

Sent from my SM-T720 using XDA Labs
 

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    My LuisKERNEL (PIE/TEN) for Samsung Galaxy Tab S5e (gts4lvwifi/gts4lvlte)
    device.png

    Code:
    *** Disclamer
    /*
     * Your warranty is now void.
     *
     * We are 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 us for messing up your device, we will laugh at you.
     *
     */

    Notice
    I like to share my work for my Samsung Galaxy Tab S5e (LTE). I have compiled this kernel so that my Galaxy Tab performs better and rooting with Magisk works better.
    I'm testing this kernel on my Samsung Galaxy Tab S5e (gts4lvwifi) device and I think it should work on the Samsung Galaxy Tab S5e LTE (gts4lvlte) too.
    The kernel I use on the latest Samsung Stock ROM with Magisk 20.3 and Magisk Manager App + Ex Kernel Manager.
    The source code is a fork from the official LineageOS 17.1 sources.

    The kernel runs for me with LineageOS and Stock Samsung ROM.

    Sometimes I get a lot of help or feature requests from users of my LuisROMs and LuisKERNELs. My dog Luis and I try to fulfill most of the wishes, but that is not always possible. I do that as a little hobby and Luis does not always want to build ROMs :). Please understand if I can not always answer directly.

    Kernel: I have pached up the Kernel to Linux 4.9.217 with many mods other devs (thanks to @LuK1337 for the base an incredible work!)
    • Pached from 4.9.112 up to 4.9.217 from caf
    • Removed lots of excessive bloat (improves security and performance)
    • Improved stability (several bugs not listed here have been fixed)
    • Boeffla Wakelock blocker driver V1.1.0
    • More I/O-Schedulers (fiops, sio, zen, maple)
    • Added fsync on/off support.
    • Disabled crc check
    • Optimized for performance and battery life
    • Compatible with EX Kernel Manager
    • Compatible with systemless root (recommend Magisk 20.x or higher !!!)
    • Wireguard kernel support
    • Many other misc. improvements not listed here

    First time installation:

    Update:

    Downlads:

    Kernel source:

    Enjoy!
    Frank
    7
    LuisKERNEL Update to Linux 4.9.217 + Wireguard 0.0.20200318 kernel driver

    Hello Friends,

    i have updated my LuisKERNEL up to Linux 4.9.217 from caf sources and wireguard kernel driver up to 0.0.20200318.

    Downloads:
    TWRP: http://luis-builds.de/downloads/lin...s4lvlte)/LuisKERNEL-4.9.217-twrp-20200322.img
    Odin: http://luis-builds.de/downloads/lin...s4lvlte)/LuisKERNEL-4.9.217-odin-20200322.tar

    if you have a rooted device then after flash my kernel reflash magisk or other SU for root your device!

    Cu Frank

    Changelog:
    * kernel/samsung/sdm670/
    0923934ff053 Merge branch 'upstream-korg-linux-4.9.y' into 10.0-luis-los
    11254e5c2d36 net: update wireguard 0.0.20200318
    10a20903d7ac Linux 4.9.217
    0bde22da659c ipv4: ensure rcu_read_lock() in cipso_v4_error()
    ff58bb340c43 mm: slub: add missing TID bump in kmem_cache_alloc_bulk()
    ed14ef08c55a ARM: 8958/1: rename missed uaccess .fixup section
    3a4c51d02e70 ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_functional()
    e06aeb9f3da6 jbd2: fix data races at struct journal_head
    4306259ff6b8 signal: avoid double atomic counter increments for user accounting
    d2a49017c249 mac80211: rx: avoid RCU list traversal under mutex
    4f1547a774dd net: ks8851-ml: Fix IRQ handling and locking
    c0d470e3ec3b cfg80211: check reg_rule for NULL in handle_channel_custom()
    5e953295a8d9 HID: i2c-hid: add Trekstor Surfbook E11B to descriptor override
    479912f78ffc HID: apple: Add support for recent firmware on Magic Keyboards
    f2a18533a69e ACPI: watchdog: Allow disabling WDAT at boot
    22333af249bc perf/amd/uncore: Replace manual sampling check with CAP_NO_INTERRUPT flag
    135075ae4eaf batman-adv: Use explicit tvlv padding for ELP packets
    34673c28f43d batman-adv: Avoid probe ELP information leak
    3c6ed319b82f batman-adv: update data pointers after skb_cow()
    baed34edb061 batman-adv: Don't schedule OGM for disabled interface
    1f9fd18c2025 batman-adv: Avoid free/alloc race when handling OGM buffer
    5841c1bb484f batman-adv: Avoid free/alloc race when handling OGM2 buffer
    5f6dd57c7b50 batman-adv: Fix duplicated OGMs on NETDEV_UP
    3c3e542a40ad batman-adv: Prevent duplicated gateway_node entry
    b081203732b8 batman-adv: Fix multicast TT issues with bogus ROAM flags
    292ddcd9d68e batman-adv: Avoid storing non-TT-sync flags on singular entries too
    9bcfdf4f8fa1 batman-adv: Fix debugfs path for renamed softif
    f7e13c96077a batman-adv: Fix debugfs path for renamed hardif
    0b81edc88189 batman-adv: prevent TT request storms by not sending inconsistent TT TLVLs
    24443bf39b9b batman-adv: Fix TT sync flags for intermediate TT responses
    f4d59337e0b8 batman-adv: Avoid race in TT TVLV allocator helper
    8142ea6bab53 batman-adv: Fix internal interface indices types
    13e6a853099e batman-adv: Fix lock for ogm cnt access in batadv_iv_ogm_calc_tq
    8c69c09f5ede batman-adv: Fix check of retrieved orig_gw in batadv_v_gw_is_eligible
    ea40bc532c52 batman-adv: Always initialize fragment header priority
    0478b59311ab batman-adv: Avoid spurious warnings from bat_v neigh_cmp implementation
    805596e6a807 batman-adv: fix TT sync flag inconsistencies
    f357813e20ff batman-adv: Accept only filled wifi station info
    1c5a456ac64a batman-adv: Use default throughput value on cfg80211 error
    65927b335012 batman-adv: Fix rx packet/bytes stats on local ARP reply
    4ae2c0625ecb batman-adv: Initialize gw sel_class via batadv_algo
    e1244b876d77 batman-adv: Fix transmission of final, 16th fragment
    351f7cbfff97 batman-adv: Fix double free during fragment merge error
    af83aa2e1f27 efi: Add a sanity check to efivar_store_raw()
    11ac2ba035f4 ipv6: restrict IPV6_ADDRFORM operation
    159ba99817a8 iommu/vt-d: Ignore devices with out-of-spec domain number
    1d66a5502feb iommu/vt-d: Fix the wrong printing in RHSA parsing
    cb87b895f146 mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame()
    a2ecb2d17b70 netfilter: cthelper: add missing attribute validation for cthelper
    85a7e73aacda nl80211: add missing attribute validation for channel switch
    0a626cd0438c nl80211: add missing attribute validation for beacon report scanning
    d4ffeafda724 nl80211: add missing attribute validation for critical protocol indication
    045bf0978374 iommu/vt-d: Fix a bug in intel_iommu_iova_to_phys() for huge page
    5145afc851ad iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint
    16d8f5dec5a6 efi: Fix a race and a buffer overflow while reading efivars via sysfs
    b5badebc9e3c ARC: define __ALIGN_STR and __ALIGN symbols for ARC
    3a91d55c921d KVM: x86: clear stale x86_emulate_ctxt->intercept value
    c919b9a14829 gfs2_atomic_open(): fix O_EXCL|O_CREAT handling on cold dcache
    ca9a513b0110 cifs_atomic_open(): fix double-put on late allocation failure
    346ff2f614e5 drm/amd/display: remove duplicated assignment to grph_obj_type
    3772b93dc3bc workqueue: don't use wq_select_unbound_cpu() for bound works
    412c17e2ddd7 iommu/vt-d: quirk_ioat_snb_local_iommu: replace WARN_TAINT with pr_warn + add_taint
    64007a74ac01 virtio-blk: fix hw_queue stopped on arbitrary error
    e9ed467f390d net: phy: fix MDIO bus PM PHY resuming
    529f4b7ad397 cgroup: memcg: net: do not associate sock with unrelated cgroup
    9fc9ba073f67 bonding/alb: make sure arp header is pulled before accessing it
    7a7c8ba58283 slip: make slhc_compress() more robust against malicious packets
    a01b5e507c99 net: fec: validate the new settings in fec_enet_set_coalesce()
    3bd2095b8058 macvlan: add cond_resched() during multicast processing
    2ad8246c4dbe ipvlan: don't deref eth hdr before checking it's set
    8621153cb6c8 ipvlan: do not use cond_resched_rcu() in ipvlan_process_multicast()
    276a875f7124 ipvlan: egress mcast packets are not exceptional
    96ce4520f395 ipvlan: do not add hardware address of master to its unicast filter list
    8079db5d729a ipvlan: add cond_resched_rcu() while processing muticast backlog
    65ff45dfdc63 nfc: add missing attribute validation for vendor subcommand
    0ba5c3ddb59c nfc: add missing attribute validation for SE API
    26623ec1fcd6 team: add missing attribute validation for array index
    c8571e0c2b68 team: add missing attribute validation for port ifindex
    65c9a7a213e4 net: fq: add missing attribute validation for orphan mask
    1abae2c50c67 macsec: add missing attribute validation for port
    76de44ee4d7b nl802154: add missing attribute validation for dev_type
    5869a748587a nl802154: add missing attribute validation
    0b21c9cbf647 fib: add missing attribute validation for tun_id
    285112d5a481 bnxt_en: reinitialize IRQs when MTU is modified
    f120a4000223 r8152: check disconnect status after long sleep
    e5660ee1a35b net: nfc: fix bounds checking bugs on "pipe"
    fc094dab7eb9 net: macsec: update SCI upon MAC address change.
    6d80c781790e ipv6/addrconf: call ipv6_mc_up() for non-Ethernet interface
    6f1aea70c1f8 gre: fix uninit-value in __iptunnel_pull_header
    78604444fb87 cgroup, netclassid: periodically release file_lock on classid updating
    da933d989ff5 net: phy: Avoid multiple suspends
    4ffa65aa2bc5 phy: Revert toggling reset changes.
    dbfc9e987856 NFS: Remove superfluous kmap in nfs_readdir_xdr_to_array
    5
    LuisKERNEL Update

    Hi Friends,

    new kernel update is out :)

    Download:
    LuisKERNEL-4.9.112-191208-twrp-boot.img
    LuisKERNEL-4.9.112-191208-odin.tar

    Link: http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_Tab_S5e_(gts4lvwifi)(gts4lvlte)/LuisKERNEL/

    Flash with odin (.tar) or twrp (.img) to boot partition.

    Changelog:
    • Merge branch 'upstream-los-lineage-17.0' into pie-luis-los
    • msm: vidc: Add NV12_512 support for encoder
    • uapi: Add COLOR_FMT_NV12_512
    • Revert "Android.bp: Initial header export bp for Android (qseecom only)"
    • msm: kgsl: run kgsl-workqueue as a high prio wq
    Cu Frank
    3
    update - Tried the kernel on sm-T720 , worked without issues. No kcal support.
    - please consider adding kcal/color/saturation options if possible.

    Thanks
    Kcal will merged in the next days if stable ;) Testing today ;)))

    Cu Frank
    2
    I bought a used tab s5e from a local electronics store for less than half of the msrp. I then discovered that it wouldnt charge past 70%. Later I peeled off the sticker on the back and the tablet said 'not for sale'. It turns out that this was a display unit and these are configured to not charge past 70% to protect the battery. I didn't want to return it because it was a really good deal even if it doesn't fully charge. My question is will flashing this kernel allow my tablet to charge to 100%? Or this kernel will not be compatible with it? Thanks in advance.

    There's an option in the battery settings that limits the tablet from charging beyond 85% to extend the battery life, you can take a look at that first. If that doesn't help, you can try a custom ROM and Kernel. Start with the kernel, as it is less intrusive. but to be honest, I have no idea if that would help. You can also try a factory reset.
    If I was a betting man, I'd bet on Samsung limiting that device's charging capacity though the ROM.
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