[ROM][OFFICIAL][gts4lvwifi][11] LineageOS 18.1

[Siggyceline]

Is there a new firmware release for our tablet like almost a month ago? Because I'm on the May 19th release.

New firmware release on github for T-720: T720XXU2DUJ1

Maybe it's just me, but I always thought this thread was linked to this page:

Info about gts4lvwifi | LineageOS Wiki

wiki.lineageos.org

Also, pretty much every Monday my S5e let's me know there is an Update...

 

[D.E.A.T.H.]

Hey @LuK1337
Are we waiting for Android 12L release?
Will there be any 12L development in custom roms by you?

 

[LuK1337]

Hey @LuK1337
Are we waiting for Android 12L release?
Will there be any 12L integration in custom roms by you?

It's kinda creepy when death mentions my name.

 

[EugenStanis]

Hey @LuK1337
Are we waiting for Android 12L release?
Will there be any 12L integration in custom roms by you?

It's kinda creepy when death mentions my name.

Kinda interesting IF there will be standard android bump or separated version like Lineage 19L

 

[D.E.A.T.H.]

It's kinda creepy when death mentions my name.

Sorry to creep you out..... lol
I was very naive when I had created this account.

 

[XRed_CubeX]

Sorry to creep you out..... lol
I was very naive when I had created this account.

In fact I'm curious to know how the two android versions (12 standard and 12L) are handled.
Right now we should probably wait for an official release from google but seeing how lineage os will handle these two versions will be interesting (always if there is some sort of Lineage Os 19L).

 

[ProfHastings]

Hi everyone!

First of all, thank you very much for providing such a phantastic custom ROM for our device! I can't stress this enough!

I do have a slight problem though: In Skype there doesn't seem to be any volume control whatsoever. The speakers are always blasting at full volume, no matter how the system's various volume sliders are set----either manually or through the volume rocker. Any suggestens would be very much appreciated!

Thank you very much!

 

[topaza]

Hey guys,

I just tried to get LOS running on my new S5e. Getting to the unlock menu was a pain but it shows the following in the download mode now:

FRP LOCK : OFF
OEM LOCK : OFF (U)
KG STATUS : PRENORMAL
WARRANTY VOID : 0x0
QUALCOMM SECUREBOOT : ENABLE
SECURE DOWNLOAD : ENABLE

However, when I to flash vbmeta.tar with Odin this fails with "<ID:0/003> FAIL! (Auth)"

On the Tablet I get the message: "Only official released binaries are allowed to be flashed(vbmeta)"

Guess this might be related to QUALCOMM SECUREBOOT : ENABLE or SECURE DOWNLOAD : ENABLE

Did I miss something or was it a bad idea to update to latest stock rom before did the flashing attempt and samsung changed something to prevent flashing in the latest update?

//EDIT: In developer options it also shows the the boot loader as unlocked and the option is grayed out (because it cannot be changed back until the boot loader is relocked I guess)

/EDIT2:
Flashing vbmeta worked after some more tries. I have no idea why however....
Also there seem to be download modes that behave different. If I use "adb reboot bootloader" I am in a green download mode without any details. This one failed completely on my first attempts. If I use vol-up + vol-down + power and usb cable connected(!) I get the download mode with additional details on locking state. And this one behaved totally different. Flashing seemed to work but ended in the error mentioned above. Another try in "normal" boot loader however worked for whatever reason.
Can anyone explain where is the difference in the two download modes and which is supposed to do what?

But still I am stuck. I also can flash the new recovery in "normal" download mode but after flashing it instantly reboots to Android which seems to overwrite Recovery again. At least it still looks the same after reboot and ADB sideload fails...
Never ever had such an annoying device before. oO
Any Ideas on how to get to LOS recovery before stock rom boots again?

//EDIT3: After endless tries it finally worked somehow and I am on LOS now.

 

[topaza]

I would like to root the device and I did some research and found that Magisk can only be installed to recovery on this device and there is a "patch file" option in magisk app. However I have no experience with this way of installing Magisk and before I break something, I would like to ask some questions:
1) Can I just use the app to patch the LOS recovery.tar that I used for installing LOS and then flash the patched file with Odin to AP Partition?
2) Is it the same with TWRP? Can I just patch the latest TWRP tar file and flash it to AP partition?
3) Is there any advantage in choosing LOS recovery instead of TWRP?
4) Will Magisk survive LOS update if I uncheck "update recovery" in LOS updater settings?

 

[JJ2017]

I would like to root the device and I did some research and found that Magisk can only be installed to recovery on this device and there is a "patch file" option in magisk app. However I have no experience with this way of installing Magisk and before I break something, I would like to ask,...........

Having just upgraded to Magisk v24 this was how I did it:
1) extract boot.img for the ROM you are using i.e. from the installation package (.zip)
2) install Magisk Manager (download from github if you don't already have it)
3) use Manager to patch the boot.img file - it will save to your device somewhere
4) boot into recovery, flash the patched boot.img using TWRP

Hope that helps

 

[topaza]

Thanks for the guide. In the meantime I also found out that installing Magisk on LOS is much easier than on stock rom.
I did it a little different than you and just flashed the magisk.zip from TWRP. This also works fine for now.
Do you know if patching the image has any advantage over just installing the zip file?

 

[JJ2017]

did it a little different than you and just flashed the magisk.zip from TWRP. This also works fine for now.

That's good to know - I just followed methods on this thread - like you, I was wary about just flashing it and hoping!

Do you know if patching the image has any advantage over just installing the zip file?

If it works, it works - can't see why patching boot would be advantageous but happy to be corrected, if someone knows better

 

[Lupin The Third]

FYI

[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19

LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project, with...

forum.xda-developers.com

 

[Lord Sithek]

FYI

[ROM][OFFICIAL][gts4lv|gts4lvwifi][12] LineageOS 19

LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project, with...

forum.xda-developers.com

Woooow, how exciting!

 

[liontari1977]

how to fix guys?what safetynet fix file need?
and somthing for fix bootloader warning mesagge?
it's a little ugly....

 

[bobemoe]

I have a USB-C hub (BL10V), which has a RTL8152 Ethernet port on it, along with audio, video, USB A, SD, PD. Everything else works apart from the Ethernet. When I connect it no Ethernet item appears under Networking. No mention of 8152 or Ethernet in dmesg or lsusb.

When I connect it to my laptop I see it appear in dmesg and lsusb.

I have tested on my mates Galaxy S9, stock ROM, where it works perfectly.

I did try it on my s5e stock ROM briefly before flashing LineageOS where it also did NOT work. Ethernet was present under Networking, but greyed out, and stayed greyed out.

I see CONFIG_USB_RTL8152 and CONFIG_USB_USBNET are both enabled in defconf.

I don't understand why it is not being recognized. Any ideas?

I bought a USB-C -> Ethernet adapter to use with my tablet. It doesn't work...

Did you ever get anything working?

 

[austinalex23]

I have a USB-C hub (BL10V), which has a RTL8152 Ethernet port on it, along with audio, video, USB A, SD, PD. Everything else works apart from the Ethernet. When I connect it no Ethernet item appears under Networking. No mention of 8152 or Ethernet in dmesg or lsusb.

When I connect it to my laptop I see it appear in dmesg and lsusb.

I have tested on my mates Galaxy S9, stock ROM, where it works perfectly.

I did try it on my s5e stock ROM briefly before flashing LineageOS where it also did NOT work. Ethernet was present under Networking, but greyed out, and stayed greyed out.

I see CONFIG_USB_RTL8152 and CONFIG_USB_USBNET are both enabled in defconf.

I don't understand why it is not being recognized. Any ideas?


Did you ever get anything working?

Unfortunately I have not gotten it working

 

[bobemoe]

So, has anyone actually had Ethernet working on this device? Stock or otherwise? I'm thinking of trying some other ROM's or Kernels. But could this be fundamentally impossible on a hardware level?

Unfortunately I have not gotten it working

Thanks for confirming

 

[Orginator]

How's the performance vs stock android 11? Sadly I can't find any benchmarks or youtube comparison.
Is it worth trying to root and change rom just for that?

 

[androandruts]

I can't find if it is a well-known bug but Lineage OS 18.1 and 19 for gts4lvwifi cannot see wifi networks which operates on channels higher than 11. Please fix it if you can. Greetings