LineageOS 19.1 for SM-T580 (gtaxlwifi), SM-T585 (gtaxllte), SM-P580 (gtanotexlwifi), and SM-P585 (gtanotexllte)
- Thread starter K9100ii
- Start date
Just came across this post and this quoted procedure helped me out. I did make one goofup though which was easily fixed. Having wiped the system partition before enabling USB debugging caused me to lose the ability to ADB (shows as unauthorized and unable to authorize it without a working OS). And I had not copied over the images to the internal storage. HOWEVER the Lineage recovery can just as easily pull from an SD card which I was able to use no issue. Just in case anyone does this boneheaded move like me.
Just recently upgraded my mother's SM-T580 using this rom and method and it's working beautifully. Last OEM update and security level was all the way back in 2019.
Sorry, I have no good alternative in mind but I think the ease of donating is crucial. Speaking for myself, I don't want to have to create an account first before being able to donate. I agree to the dislike of PayPal but it is pretty easy using credit card or bank transfer. The above requirements are conflicting e. g. with GitHub sponsor program as I don't have an account there.
Hi all,
First of all thank you for your great work with the lineage OS, everything worked like a charm. I’ve tried to install Netflix from Play Store which is not available there.
I can install an APK but would just like to know if Netflix works in 1080p or is it only in 720p?
Thank you!
KR
Rok
First of all thank you for your great work with the lineage OS, everything worked like a charm. I’ve tried to install Netflix from Play Store which is not available there.
I can install an APK but would just like to know if Netflix works in 1080p or is it only in 720p?
Thank you!
KR
Rok
Hmm, it isn't perfect, but looks decent.
Allows payment via Stripe, therefore allowing card payments, as well as PayPal. Certainly has accessibility.
I might look at getting it setup sometime over the next few days. Thanks for the suggestion.
PUBG mobile? On this hardware that's low end for today? Seriously? I'm not interested in that game, but is that playable at all? Legitimately interested, and have my doubts.
Anyway, no idea, but weird. Will only check logcats later.
Okay, this is helpful. Only checked that log; SELinux denials, as I expected.
Might be able to address them in one go, I'll have to see.
By the way, on audio issues: There's likely something with the audio HAL that means modifications are needed for the 7th revision. I'll probably not have any clue; You'll likely be on your own unfortunately.
Indeed, fully agree, specifically why I'm mentioned accessibility.
:)And yeah, fair enough on not wanting to create a new account.
Bank transfers aren't an option, since I can't put up the details for my personal account. That would mean my identity being extremely directly exposed. But yeah, I agree it would be best if not for that.
GitHub's sponsor program could actually be an okay additional option. Maybe overkill. Thanks for mentioning it.
Meanwhile, for everyone: I'll be getting a username change, on both my XDA account and GitHub account. It's already complete on my GitHub account.
The "9100" in "K9100ii" is part of the model number of the Galaxy S2, on which without getting into custom firmware, way back in 2017, I wouldn't be at the point I'm at(!). (Oh, it's good seeing it run mainline Linux at all nowadays, wish the same for other devices like these tablets.)
For those building own builds: You should update your manifest with device-specific repositories (although this won't be urgent since GitHub should redirect from my old username to my new one).
Last edited:
My mistake, I meant direct debit but also in relation to PayPal. At least in Europe, PayPal offers this option. Same as with credit card, both is possible without having an own account as donor.
And yes, I would also not want to make my personal bank account details public. ;-)
Looking forward to whatever option you choose.
Ah, okay. I thought that wasn't an option for donations. I knew PayPal offers that option for commercial transactions, but (somehow) thought donations worked completely differently.
I'll most likely go for having only PayPal then. I was planning to have it anyway despite my dislike as the common option, but in that case, if I go with something like Ko-Fi, on my end, it'll be going through 3 different services (with 3 different accounts) which isn't nice.
Thanks for bringing that up.
Sorry for yet another post on this matter: I checked today and see that the form for PayPal donation both via credit card and via direct debit as alternative to log in to an existing account include (besides all personal data) now also a password box (was not the case some time ago). No clue whether it is a box that can be omitted or not. I found also information online that PayPal accepts only up to three times payments (not specific to donations) via direct debit per bank account without a PayPal account and to a maximum of 1.500 EUR.
I guess anti-money laundering legislation is making things more and more complicated ... and data gathering interest of companies like PayPal are not going to oppose this.
For some reason, after LOS boots up for the first time, the device immediately shows "Factory data reset" and throws me back into TWRP.
The strange thing is that I initially had issues with installing Gapps (MindTheGapps refused to install), so I checked if LOS works or not. I went halfway through the initial setup before rebooting and trying to install some other Gapps versions.
After that, I went through several Gapps versions because I started receiving this message and reboot.
So, once again, I tried with no Gapps and the reboot persists without Gapps as well!
Then I tried an older LOS and the reboot still happens.
At this point, I went through like 10 combinations and reboots/wipes and it never works.
I always fully wipe everything on the device (system, cache, data) and install from SDcard (I mean, the real SD card in the slot).
What could have triggered this and how could I solve it?
Yes, the OEM Unlock was enabled before flashing TWRP. Although that other mentioned software refused to run.
Is that important?
I don't think so because I had a vanilla LOS going through half-way of the initial setup process once. This reboot thing started after I managed to install a Gapps package as well (but now vanilla won't work either).
The strange thing is that I initially had issues with installing Gapps (MindTheGapps refused to install), so I checked if LOS works or not. I went halfway through the initial setup before rebooting and trying to install some other Gapps versions.
After that, I went through several Gapps versions because I started receiving this message and reboot.
So, once again, I tried with no Gapps and the reboot persists without Gapps as well!
Then I tried an older LOS and the reboot still happens.
At this point, I went through like 10 combinations and reboots/wipes and it never works.
I always fully wipe everything on the device (system, cache, data) and install from SDcard (I mean, the real SD card in the slot).
What could have triggered this and how could I solve it?
Yes, the OEM Unlock was enabled before flashing TWRP. Although that other mentioned software refused to run.
Is that important?
I don't think so because I had a vanilla LOS going through half-way of the initial setup process once. This reboot thing started after I managed to install a Gapps package as well (but now vanilla won't work either).
In TWRP, Format -> Format Data (there's a specific button) -> Type yes to confirm. Should be fine after that.
Edit: Misread/mistook your problem from tiredness, but try that anyway. Can't imagine anything going wrong with properly formatted data.
Edit 2: Also, MindTheGapps can't install using TWRP. You need to use another google apps package, or use Lineage recovery packaged in builds as "recovery.img" with a micro SD card to install MTG.
Last edited:
Nah, it's fine. Such information is interesting and useful to know.
I've taken a look at a PayPal donation form for payment via a debit card, and here (I'm in the UK), it doesn't show a password box. So that's interesting. Seems like it would be region-based. It does seemingly also allow for entering really high amounts of money, and only requires a phone number and email, asides from card and address details, as expected.
Would be interesting if it's non-transparently actually making an account if you submit info, doesn't seem right to ask for a password otherwise.
With the additional information online, could you link it? I'm struggling to find anything like that here.
And yeah, no doubt, unfortunately.
Last edited:
I even tried changing the filesystem on all writable partitions (system, data, cache) from ETX4 to EXT3 and back to EXT4 just to make sure they are indeed getting formatted and not just rm-f wiped.
I guess K9100ii knows better which of what follows can be relevant but I will ask a few (silly) questions from my own experience - no need to answer everything but maybe something will lead you the right way:
- Which model do you have?
- Which TWRP are you using? Matching the model as listed in OP? (Low chance being relevant since you seem to have no troubles with TWRP itself.)
- Are you using the matching build as listed in OP?
- Did you check the integrity of the package with the provided checksums in "Folders for builds" in the OP for LOS? (For checksums of TWRP packages, you might want to ask K9100ii whether he can provide. I haven't found any for TWRP so far.)
- Device was running without issues on stock before you started the whole activity?
- Most interesting: What do you mean with "I had a vanilla LOS going through half-way of the initial setup process once"? Do you mean it succeeded to install (not meaning a lot) or to boot into system without the mentioned issue (more relevant info)?
- Whenever you flashed GApps, did you format your data partition before booting system?
- Worst case, you can try to check the partition with
fsckvia TWRP - shell is available in advanced or so. (Don't have device with TWRP at hand right now.)
Just for sake of completeness: Did you format data as mentioned by K9100ii followed by a reboot to recovery and then flashing just the plain LOS build without GApps?
Just to confirm... the latest LineageOs avaiable for the old T580 is this 19.1 version, right?
To get my Tablet to a more updated state i need to go with:
- twrp-3.7.0_9-0-gtaxlwifi-unofficial-newsources.tar
- lineage-19.1-20230603-UNOFFICIAL-gtaxlwifi.zip
- open_gapps-arm64-12L-pico-20220705-UNOFFICIAL_MOD.zip
Is this correct?
To get my Tablet to a more updated state i need to go with:
- twrp-3.7.0_9-0-gtaxlwifi-unofficial-newsources.tar
- lineage-19.1-20230603-UNOFFICIAL-gtaxlwifi.zip
- open_gapps-arm64-12L-pico-20220705-UNOFFICIAL_MOD.zip
Is this correct?
i have revision 7 gtaxllte device
i just want the stock rom without fully unlock for normal use
now i have lineage os
where do i get the stock rom
i just want the stock rom without fully unlock for normal use
now i have lineage os
where do i get the stock rom
SM-T585 gtaxllte.
I downloaded TWRP from the first post.
Yes, I double-checked.
No, but ZIP files always have internal checksums.
Yes, stock is running fine (even after going back from LOS).
I succeeded to boot once. Then I abandoned the setup process after a first steps and went back to wipe and install some other Gapps package.
I always wiped everything.
Indeed, I could. But it should make no difference since wipe uses mkfs by default (it recreates the filesystem).
Last edited:
from firmware bro
just search "SM-T585 firmware" and select your country
unzip the firmware file and flash this files with odin3 from PC
that's it
Can't I load it in the TWRB recovery with ADB SIDEloader
And where do I get the Stock ROM (the operating system)
without knox
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4
I did have two mentions of google app packages, some custom opengapps packages and nikgapps. A while ago, I saw posts from someone related to issues with those packages, implying that the mentions were seen as recommendations, rather than just useful mentions in a specific context. All the while it seemed like I might've got partial blame for the issues, just with the mere mentions since I've been taken to having recommended packages.
Meanwhile, I don't use google apps and so can't support them, and google app package-related issues seem to be common.
So I simply gave up and removed the mentions. So IDK.3
Of course? I haven't disappeared.
Updated forked repos again.
In the future, use these commands to update forks from Lineage's repositories locally:
Git:cd frameworks/base git remote add lineage https://github.com/LineageOS/android_frameworks_base git fetch lineage lineage-19.1 git rebase lineage/lineage-19.1 cd frameworks/native git remote add lineage https://github.com/LineageOS/android_frameworks_native git fetch lineage lineage-19.1 git rebase lineage/lineage-19.1 cd packages/modules/Permission git remote add lineage https://github.com/LineageOS/android_packages_modules_Permission git fetch lineage lineage-19.1 git rebase lineage/lineage-19.1
Shouldn't be trying to make updated builds without pulling in all the updates while intending to get the latest security patches anyway.3Well folks...
for me this discussion with *Gapps looks like with the flys, who dont want to move from the candy (I dont wanted to write "sh*t").
And to be honest: at the beginning of my "career" with LineageOS I also was a user, who thought, that *Gapps always must be.
But since a year now I run my to Samsung Galaxy S7 and my Samsung Galaxy Tablet SM-580 WITHOUT *Gapps, what means, that I do not have that Google mess (GSF, Pay and more) on my units.
Here at XDA there were good people who convinced me, that any *Gapps and so all that Google Systems Framework mess is really not neccessary.
Reason: over 90% of all the apps, and especially neary 99% of all that games in Google Play Store are not only just crap, they are also fullfilled with all kind of spyware, trackers and other mess, nobody needs. Google has lost the control of its play store, and the coders of bad apps, of viruses, spyware and other mess to rule there now...
I still use the Google Playstore to download just a few apps with Aurora, I got from there and use since years. But by rethinking I got convinced to use Fdroid store, where very good apps are, and none of them has trackers or other mess.
And, most important: mostly a direct contact with the coders of these apps allows me to pay them without fee for Google, and the coders like that.
So folks: forget *Gapps. Forget Google. Use your units without that mess. Its better, believe me!3As the questions "where can I find XYZ GApps" or "which GApps should I use" are popping up lately every other day, I tried to summarize and to gather options from this thread. If anyone has practical experience with additional options, please share here or send a PM - I will try to keep the post up to date.
Do I need GApps?
- Well, it depends ... consider also that you can run the tablet without GApps (freeing up resources) by using e. g. F-Droid (https://f-droid.org/) and accessing Google Play Store e. g. thru Aurora Store available thru F-Droid.
- As it depends on many variables, there can't be a clear statement for what you need GApps or not. Don't ask - try yourself!
- Credits to @netra3441 for the reminder on this general consideration.
- Consider as alternative also microG (https://microg.org/) as indicated in the OP.
- Remember, you need GApps for Android 12L (sometimes also referred to as Android SL; base of LineageOS 19(.1)) and ARM64 as indicated in the OP.
- As stated in the OP, use as light as possible since the hardware is old and was never cutting edge!
- OpenGApps (https://opengapps.org/)
- NikGApps (https://nikgapps.com/)
- Files can be found here - you need to go for "releases" and "NikGapps-SL". "Core" is the lightest flavor - matching the "as light as possible" recommendation.
- My personal preference lately as they are light and well maintained.
- Point of attention: There are several reports of Play Store having no connection - activate data usage in the app properties to resolve (e. g. here>here>here).
- LiteGapps (https://litegapps.site/)
- No own experience and not mentioned in this thread but mentioned here and there in context of light GApps for older hardware.
- MindTheGapps (https://mindthegapps.com/)
- The only "officially" recommended (not supported!) GApps by LineageOS - linked on the official wiki page related to GApps.
- Apparently, there is an issue installing MindTheGapps via TWRP - multiple mentions can be found.
- As there is only one flavor incl. a few more apps, they don't match the "as light as possible" recommendation.
Disclaimer: This overview post is not implying support for any of the referenced GApps or other solutions. Everything is on your own risk.3
Yes, thats it. In German we say "jedem Tierchen sein Plaesierchen", what nearly means the same ;-)
But myself I got angry a year before, after I understood, how bad this Google mess alltogether is: spying and slowing down the smartphone or tablet.
It is a clever marketing strategy of Google, that they have achieved, that the most users believe, a smartphone or tablet will not work without Google Systems Framework, so the *Gapps.
I am glad, that I got help and information here on XDA, to learn to free myself and my smartphones and tablet from this believe... -
72This is LineageOS 19.1, which is based on Android 12L, for variants of the Samsung Galaxy Tab A 10.1" (2016), which have models and codenames as follows:
- SM-T580, with codename gtaxlwifi
- SM-T585, with codename gtaxllte, along with SM-T585N0, SM-T585C, and SM-T587 (not SM-T587P)
- SM-P580, with codename gtanotexlwifi, along with SM-P583
- SM-P585, with codename gtanotexllte, along with SM-P585M, SM-P585Y, SM-P585N0, and SM-P588C
Some useful information for devices from China (SM-P583, SM-T585C, SM-P588C, and SM-T580 on the CHN CSC) - For unlocking the bootloader before installation, an app, "CROM Service", would need to be opened and the prompt from it accepted so that it can be unlocked, after enabling the "OEM unlock" setting in developer options. It should be available from the Galaxy Store, although I can't be 100% sure about it. In any case, an APK of it should be easy to find.
As was the case with LineageOS 18.1, I've taken over maintaining 19.1 for gtaxlwifi from @followmsi, and my 19.1 builds continue on from his 19.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of an existing install from his builds without doing anything further (or "dirty flashed").
For those running 18.1 or 17.1, upgrading to 19.1 is possible through the procedure I've explained before here and here (except with 19.1/Android 12 and 18.1 rather than 18.1/Android 11 and 17.1 for that second post). I highly suggest backing up any important data before trying to upgrade. In the unlikely case the upgrade fails, and it doesn't boot, data would need to be formatted.
For those who used WiFi-only variant builds on an LTE variant device, installation of a proper LTE variant build on top of an installation from a WiFi-only variant build is possible, except for a small issue you may encounter after doing so. See issue 3 in the "known workarounds and issues" section below for it.
LineageOS 19.1/Android 12 usability fixes
For those wanting to disable the widely disliked taskbar (the grey bar at the bottom with the 3 navigation buttons and shortcuts for apps docked at the launcher): Instructions for doing so are in the first section of my post here.
For enabling lockscreen rotation: Instructions for doing so are in my post here.
For those needing Google apps: Do not use heavy Google apps packages, as otherwise, you WILL have severe performance issues. Instead, use the most minimal variant of your chosen package (core, pico...). Also, while mentioning that, make sure the package is 64-bit ARM (ARM64) and specifically, and only, for Android 12L.
You may look for Google app packages that others have had success using by searching the thread. Also worth considering is microG, which - if you can use and don't have anything depending strictly on having Google's own play services - will allow you to have additional resources (RAM mainly) that would otherwise be taken up by Google play services.
Build downloads - From 20230824, all with security patch level 20230805
For gtaxlwifi: https://drive.google.com/file/d/1zY_6gJFjpcqbW2Upo8ZcFCpOIebcmlQh/
For gtaxllte: https://drive.google.com/file/d/1tlUO_x1MdIqUw_IMck6U6kU1WZEX6T7b/
For gtanotexlwifi: https://drive.google.com/file/d/1N34dR5QtcuPVbJQ88o2XIXhTdL1nR6Ju/
For gtanotexllte: https://drive.google.com/file/d/1AiP5P8855PWPtSCRybyDNJrQTP8dlNG-/
Recoveries to use
Use my unofficial TWRP builds:
For gtaxlwifi: Image here, tar for Odin for AP slot is here.
For gtaxllte: Image here, tar for Odin here.
For gtanotexlwifi: Image here, tar for Odin here.
For gtanotexllte: Image here, tar for Odin here.
Folders for builds
Along with current builds, these contain text files with SHA256 checksums for builds, and folders containing few previous builds.
For gtaxlwifi: https://drive.google.com/drive/folders/1S3NRiTP2jr9gRtSMKoKoaoMu75g_FJM4
For gtaxllte: https://drive.google.com/drive/folders/1ZFkGkVkIohsNFDi0jNF2-Yhz7Sbg5GT4
For gtanotexlwifi: https://drive.google.com/drive/folders/11pcp9NZf0ovelvT7oxfhoem6-utpSao8
For gtanotexllte: https://drive.google.com/drive/folders/1AICJ1UcnZ5a-slcgd-iGQ9mpk9J8Evmd
Changelogs
Known issues and workarounds/fixes (if any)
Sources
A manifest containing all of the necessary repositories to make builds for all of the variants is in the repository here on branch lineage-19.1.
Thanks to:
- @Valera1978 - for all of the previous work for the T580 and T585 long ago.
- @followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
- Anyone who has previously tested anything new I've put up for testing, reported results, and provided information needed for me to get it working if it was necessary.
- The Lineage team - for the Android distribution itself.
- ...and everyone else who has worked on anything that is in use.
27New builds for 20230419
Downloads:
For gtaxlwifi: https://drive.google.com/file/d/1HYynOu6aGNBjYQ4Xa2PgV3bfFV_MNkfX/
For gtaxllte: https://drive.google.com/file/d/1KgsUF_S2mUKAz7_vlHc8-EriN0MeGIlT/
For gtanotexlwifi: https://drive.google.com/file/d/1i-Ixj9H0CXqFOmgL4pArds2c2DtliDEI/
For gtanotexllte: https://drive.google.com/file/d/1_JC0PrPNPWSjzuAbZHPYwBfQwNmm_G19/
Changelog:
- Latest changes from LineageOS, including the 20230405 Android security updates.
- Linaro's new SLSI BSP (Board Support Package, containing sources for HWC and some other stuff) sources are now used - Much more up-to-date than the previously used sources, and there's possibly a small improvement in performance.
- The OMX hardware video decoder and encoder libs are now built from the new Linaro BSP sources - With that, playback of HEVC videos is fixed in Chrome and other Chromium-based browsers.
- Some updates from the 4.14 Android common kernel as of March have been applied to the kernel.
- The wireguard kernel module has been added back - I silently removed it in the previous builds since it was unusable due to a now fixed device lockup bug that caused almost total unresponsiveness after enabling a wireguard VPN.
Anyway, some nice improvements in these builds.
The kernel updates are behind by a month due to... yep, a lack of time and other previously mentioned reasons. As always, I'll try getting them in at some point later. I'm really hoping these don't become unsustainable, keeping up and trying to defy that the 3.18 kernel is no longer maintained upstream since a really long while is certainly becoming more difficult.
In any case, enjoy.23Since I haven't posted anything for weeks now, I thought I'd give an update.
With me being yet more busy, and things constantly changing, and health issues on top (though don't worry about me), I haven't had much time to work on this stuff much.
Within my sources, I've fixed a bug, and applied kernel updates, but haven't had any real opportunities to release any new builds. I should be able to get around to getting new builds out in the next week or so.
I don't really have time to reply to much of anything at the moment, so if there is anything to reply to, I'll be leaving replies for later.20New builds for 20221127
Downloads:
For SM-T580/gtaxlwifi: https://drive.google.com/file/d/1jd9kC8SoJH3Jba2YT_7K3qEB7QG27MMR/
For SM-P580/gtanotexlwifi: https://drive.google.com/file/d/1V_lE-ehNIvD2q-B6bbz119pjwFq92fOk/
Changelog:
- Latest changes from LineageOS, including the 20221105 Android security updates.
As for LineageOS 20.0, I've still yet to get around to working on it.
While it certainly is possible, sadly, there most likely won't ever be any possibilities for getting network traffic monitoring (used specifically for data usage statistics, network download/upload speed monitoring...) working under Android 13. (For 12.1, support for the old, non-eBPF method for it was removed, however, we have changes to revert the removal and bring it back since our old 3.18 kernel only supports it and doesn't support eBPF. It certainly seems like we won't have changes to bring it back on 13, and unfortunately, it doesn't look like there will ever be eBPF backports for 3.18.)
Nevertheless, for the meantime, enjoy.20New builds for 20230720
Downloads:
For gtaxlwifi: https://drive.google.com/file/d/1lrTWHdZc8N3_QU5z9unqzdf8vwHfTs0r/
For gtaxllte: https://drive.google.com/file/d/1vI87QfvD4SiYZILrscebKzakM_eYbYlM/
For gtanotexlwifi: https://drive.google.com/file/d/19qlw6psNakFs2CQOXJvGwT1yrNhB9Vg7/
For gtanotexllte: https://drive.google.com/file/d/1usokOmctg3-OrXLjQvzhDJLwOaqXW_3f/
Changelog:
- Latest changes from LineageOS, including the 20230705 Android security updates.
- Call audio over Bluetooth has been fixed.
- On tablets with different models for different regions, the correct model number should now be set and displayed in "About tablet" in settings.
- [LTE variants only] RIL blobs have been updated from Samsung's A305GUBU8CWE3 firmware.
- Booting and sensors issues fixed for revision 7 gtaxllte devices (exclusive to 2020 students in Egypt) - Audio issues remain.
- Many updates from the 4.14 Android common kernel, up to v4.14.320, and a few other small updates, have been applied to the kernel.
Since the correct model numbers on devices with different ones for different regions should now be set, in case that doesn't happen for anyone, do report that.
Enjoy.
