[ROM][UNOFFICIAL][gta4xl/gta4xlwifi][11] LineageOS 18.1 for Galaxy Tab S6 Lite

Search This thread
hello. i have the tab s6 lite LTE (sm-p615). I have flashed the gta4xl recovery and gta4xl rom correctly where it says in the build number gta4xl. the problem there is no cellular signal, sim cannot be detected, no gps, imei is blank
. could anybody help to why? i have tried crdroid and there is cellular and gps but for lineage there is none
View attachment 5454461
I got it guys but I had to downgrade to lineage 18.1 2021-09-11 version. I do not know the change logs from the two versions but there should not be any major difference, I guess.
 

sky321

Member
Jan 23, 2014
42
30
This build is now also available on the LineageOS build and download server. Does this mean we get now also builds from https://lineage.microg.org/ after some time ?

Was there a reason that this build was not available on LinageOS servers?
 

Linux4

Recognized Developer
This build is now also available on the LineageOS build and download server. Does this mean we get now also builds from https://lineage.microg.org/ after some time ?

Was there a reason that this build was not available on LinageOS servers?

Yes.

The reason was simply that I did not have the LTE model myself, it probably was ready for a long time already.
Now haggertk got one, so thanks to him it's official now.
 

sky321

Member
Jan 23, 2014
42
30
Thank you and also @haggertk for you effort and work. I‘m just bought this device because there was this LineageOS build by you guys. Thanks a lot!
 
  • Like
Reactions: Linux4

mokuni

Senior Member
Feb 28, 2005
159
10
Perth
Hi OP, ive now updated my wife's tablet from Lineage18.0, to this version lineage-18.1-20211010-UNOFFICIAL-gta4xlwifi.zip. Also managed to update and remove TWRP and install Lineage Recovery.

Obvious question but need to ask it. Now when I go on the tablet to update, it says my version Lineage 18.1, and there is a new version 19.1 (16/04/2022). Can I confirm I am NOT to attempt download this version, as the latest version for unofficial is 18.1 10/10/2021?
 

mu1989

Senior Member
Feb 22, 2020
121
49
Hi OP, ive now updated my wife's tablet from Lineage18.0, to this version lineage-18.1-20211010-UNOFFICIAL-gta4xlwifi.zip. Also managed to update and remove TWRP and install Lineage Recovery.

Obvious question but need to ask it. Now when I go on the tablet to update, it says my version Lineage 18.1, and there is a new version 19.1 (16/04/2022). Can I confirm I am NOT to attempt download this version, as the latest version for unofficial is 18.1 10/10/2021?
Well, I have to say that you haven't updated your wife's device in a long time, I would recommend a clean install to the latest versions You can migrate app data when you are booted with migrate app.


Of course you can also switch from unofficial to the official lineage
 

mokuni

Senior Member
Feb 28, 2005
159
10
Perth
Well, I have to say that you haven't updated your wife's device in a long time, I would recommend a clean install to the latest versions You can migrate app data when you are booted with migrate app.


Of course you can also switch from unofficial to the official lineage
Haha yes, I have been bit slack on updates for her but at the same time it has been working fine for all this time.

From what I understand by OP, its not recommended to dirty flash from Unofficial to Official (hence why I didnt install the official). I wanted to minimise the least amount of disruption i.e. not installing her large apps. And considering i'm going from 18.0 unofficial, to 18.1 unofficial I felt it would have been no major issues with the dirty flash.

I just need some clarification about the 19.1 version, if you got some comment on this. Thank you.
 
  • Like
Reactions: mu1989

mu1989

Senior Member
Feb 22, 2020
121
49
Haha yes, I have been bit slack on updates for her but at the same time it has been working fine for all this time.

From what I understand by OP, its not recommended to dirty flash from Unofficial to Official (hence why I didnt install the official). I wanted to minimise the least amount of disruption i.e. not installing her large apps. And considering i'm going from 18.0 unofficial, to 18.1 unofficial I felt it would have been no major issues with the dirty flash.

I just need some clarification about the 19.1 version, if you got some comment on this. Thank you.
Yes, it's always worth taking a risk
You can check the Telegram group.

You can download the ROM here:

There are currently also weekly updates 😅😉

If your wife wants to use magisk or gapps, I definitely recommend the Telegram group, everything you need is in the #notes
 
  • Like
Reactions: mokuni

mokuni

Senior Member
Feb 28, 2005
159
10
Perth

rebser

Member
Jul 13, 2022
6
0
Hi everyone,

for a customer project we have created a custom build of LineageOS 18.1 for SM-P610 and I have an image that is complete with our signage software.
I used to be able to flash these devices following the official installation instructions from the LineageOS page https://web.archive.org/web/20211002124915/https://wiki.lineageos.org/devices/gta4xlwifi/install

Now this doesn't work anymore. On some devices, I can't even unlock the bootloader. This has been discussed elsewhere and I have tried all the tricks from manipulating the datetime to logging on with a google or even a samsung account.
But even on the devices where I could onlock OEM, I can't seem to install the LineageOS recovery. I always get the error message "Only official released binaries are allowed to be flashed (RECOVERY)". FAP LOCK is OFF and OEM LOCK is OFF(U).

It says in the LineageOS install instructions that I must have the latest official Android 11 firmware installed. Previously, I would simply OTA update to this firmware, but nowadays, OTA goes directly to Android 12. So I tried downloading the only available Android 11 firmware from sammobile and flashing it in Heimdall. But unfortunately, I still get the same error message.

Can anybody please tell me which version of the Samsung bootloader I need exactly to install this version of the LineageOS recovery: lineage-18.1-20220112-recovery-gta4xlwifi.img?
Bonus question: Does anybody still have this firmware version mirrored somewhere?

edit: I have downloaded a newer recovery from the internet archives: lineage-18.1-20220504-recovery-gta4xlwifi.img
Now a get a different error message: "Custom binary(RECOVERY) blocked due to remaining installment balance".
Can somebody tell me what this means?
 

rebser

Member
Jul 13, 2022
6
0
Update: I have found what seems to be the exact Samsung firmware that was the latest one at the time:

I'm currently downloading.
Also, I have been able to bring one of the really old devices to exactly this firmware state by OTA by cycling through 3 consecutive incremental updates. I was pretty excited to bring it into download mode, only to see this strange error "Custom binary(RECOVERY) blocked due to remaining installment balance" yet again.
 

lewmur

Senior Member
Apr 30, 2011
2,332
504
Update: I have found what seems to be the exact Samsung firmware that was the latest one at the time:

I'm currently downloading.
Also, I have been able to bring one of the really old devices to exactly this firmware state by OTA by cycling through 3 consecutive incremental updates. I was pretty excited to bring it into download mode, only to see this strange error "Custom binary(RECOVERY) blocked due to remaining installment balance" yet again.
I don't know if this is the case, but there were Samsung tablets that were sold on installment plans. These devices had special bootloaders that required the seller to unlock once the last installment payment was made.
 

rebser

Member
Jul 13, 2022
6
0
I don't know if this is the case, but there were Samsung tablets that were sold on installment plans. These devices had special bootloaders that required the seller to unlock once the last installment payment was made.
I highly doubt this was the case here. The devices are from a stockpile of retail demo devices. Other devices from suposedly the same sockpile were working just fine earlier this year.
 

lewmur

Senior Member
Apr 30, 2011
2,332
504
I highly doubt this was the case here. The devices are from a stockpile of retail demo devices. Other devices from suposedly the same sockpile were working just fine earlier this year.
Why else would there be a "remaining installment balance"? You don't think a retailer would have some that were demo versions and some returned "installment" ones?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    1607247455067.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, 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:
    Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.

    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:


    Support
    Telegram group

    Contributors
    Linux4
    Source Code: https://github.com/LineageOS
    Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl
    4
    New (testing/beta) builds which will also work on OneUI 3 firmware are up:

    3
    CHANGELOG

    2021-01-23

    2021-01-16
    • Fixed hotspot

    2021-01-15
    • Fixed wifi direct

    2021-01-07
    • Update to Linux 4.14.213
    • 2021-01-05 system securitypatch
    • 2020-12-01 vendor securitypatch
    • Improved BT audio quality (BT audio HAL v2)
    • Improved performance and batterylife


    2020-12-12
    • Update to Linux 4.14.210
    • Add glove mode / high touch sensitivity mode
    • 2020-12-05 system securitypatch

    2020-11-24
    • Enable MAC randomization again
    • Netflix now works without liboemcrypto disabler (L3 only, Samsung doesn't seem to allow L1 with custom ROM installed)
    • Fixed small UI lags
    • 2020-11-01 vendor securitypatch

    2020-11-19
    • Fixed RIL on LTE variant

    2020-11-18
    • Initial release
    3
    Yikes, I installed the latest update when it asked, and it, upon success with no errors resulted in the total wipe of the tablet. Was thankfully able to get back to stock. Think I'm going to pass on ever using lineageOS again after that.

    That's why the instructions tell you to use lineage recovery ...
    It's TWRP's fault, not Lineage's.
    I guess there's no other way than fully taking down TWRP downloads for stopping people from using TWRP on official 17.1 and 18.1 (it initially worked on my unofficial 17.1 because that didn't have FBE enabled, that's the only reason why there's TWRP at all)
    3
    I have uploaded new builds, as Lineage is now based on the new AOSP feature drop it's now 18.1