That is not possible for this ROM, i think. It needs a clean install! However, if you know where these specific files are stored, maybe you can make a backup. And then put them back?
Last edited:
[ROM][UNOFFICIAL][10] LineageOS 17.1 [T713][T719][T813][T819]
- Thread starter ripee
- Start date
Hello, i got a gts210vewifi.
I recognized some things:
There are links for anything with sha256 - but there are the builds linked, not checksums.
I installed lineage-16.0-20220616-UNOFFICIAL-gts210vewifi.zip.
The level of securitypatch is 5. January 2022 - should it not be May?
I installed lineage-17.1-20220617-UNOFFICIAL-gts210vewifi.zip without Gapps.
I downloaded f-droid to install apps, no problem.
I added a second user. Option: User, has own apps and content.
I downloaded f-droid.apk again.
I tapped on it at the filemanager.
There should be be a dialog, something like "give permissions to install unknown apps" (had been before as Administrator).
But there is not. It is asked "Do you want to install this app?", yes.
"App was not installed".
How can i install f-droid on a second user?
It was possible in LOS 16.
Greets,
wowi63
I recognized some things:
There are links for anything with sha256 - but there are the builds linked, not checksums.
I installed lineage-16.0-20220616-UNOFFICIAL-gts210vewifi.zip.
The level of securitypatch is 5. January 2022 - should it not be May?
I installed lineage-17.1-20220617-UNOFFICIAL-gts210vewifi.zip without Gapps.
I downloaded f-droid to install apps, no problem.
I added a second user. Option: User, has own apps and content.
I downloaded f-droid.apk again.
I tapped on it at the filemanager.
There should be be a dialog, something like "give permissions to install unknown apps" (had been before as Administrator).
But there is not. It is asked "Do you want to install this app?", yes.
"App was not installed".
How can i install f-droid on a second user?
It was possible in LOS 16.
Greets,
wowi63
Last edited:
I got an update-error.
Installed: lineage-17.1-20220617-UNOFFICIAL-gts210vewifi.zip
The updater-app anounced a new build:
lineage-17.1-20220624-UNOFFICIAL-gts210vewifi.zip
No problem downloading.
When i want to install it, installation does not start, a triangel-icon appears in the system bar, it just says "installation error", nothing more.
Greets,
wowi63
Installed: lineage-17.1-20220617-UNOFFICIAL-gts210vewifi.zip
The updater-app anounced a new build:
lineage-17.1-20220624-UNOFFICIAL-gts210vewifi.zip
No problem downloading.
When i want to install it, installation does not start, a triangel-icon appears in the system bar, it just says "installation error", nothing more.
Greets,
wowi63
Hello,
I have a SM-T819, I have to update it to Android 9.0 minimum. This ROMs can do the job, but I also need some of the GAPPS.
According to the FAQ of said GAPPS, this patches ¹ may be a good thing to add in the ROM, which is something I cannot do, it is the work of the developers.
So question : are these patches added in your ROMs ? I guess they are, but I want to be sure.
¹ (yes it is written for Android 7.0. The FAQ for Android 9.0 redirected to this page because these are the same patches to add)
I have a SM-T819, I have to update it to Android 9.0 minimum. This ROMs can do the job, but I also need some of the GAPPS.
According to the FAQ of said GAPPS, this patches ¹ may be a good thing to add in the ROM, which is something I cannot do, it is the work of the developers.
So question : are these patches added in your ROMs ? I guess they are, but I want to be sure.
¹ (yes it is written for Android 7.0. The FAQ for Android 9.0 redirected to this page because these are the same patches to add)
Problems with SM-T813 (gts210vewifi), updated to 17.1-20220708 via ota.
The device boot succesfully, then starts rebooting infinitely.
Edit: The device reboots and go into infinite boot animation until you don't put the charger and force restart. When the os starts, you can remove the charger and everything is ok, but if you want to reboot or shutdown and boot later, you have to put in the charger!
The device boot succesfully, then starts rebooting infinitely.
Edit: The device reboots and go into infinite boot animation until you don't put the charger and force restart. When the os starts, you can remove the charger and everything is ok, but if you want to reboot or shutdown and boot later, you have to put in the charger!
Last edited:
Has anyone tried to login to the American Airlines app with this ROM? Trying to figure out if it is a ROM, Magisk, or adblocking problem.
I have a T813 German model, what would be the best firmware you can put on it? I still use the Samsung firmware of Android 7. Is it still this one? Or shouldnt you advice to use custom roms on the T813 because of some bugs making it a nogo.
Last edited:
I'm using a self-built LineageOS 16.0 (Android 9) on a Dutch T813. Google no longer actively provides security patches for Android 9, so LineageOS can't implement them, and I can't bake them into the ROM. Sadly, it's stuck at 2022-01-05.
I have tried LineageOS 17.1 from this thread, but wasn't happy without a working camera. That was a show-stopper for me.
For the moment, I can make no definite recommendation as to which ROM is 'better'; stock Android is perfectly fitted to the device, but stuck in the proverbial stone age. LineageOS 16.0 is newer and 100% working, but also stuck at it's current level of security. LineageOS 17.1 should be buildable, but has no working camera.
Take your pick
Sorry.Kind regards,
FWieP
Few days ago I a notification about available update and as usual I clicked download clicked install and next thing the tablet (T819) is dead. Black screen, no vibrations and buttons do nothing, tab is completely numb. I tried to get in to download or recovery mode, but no cigar. Charger indicates that tablet is taking charge, but no charging icon on the screen. Is this just simple coincidence of tablet giving up or are there similar experiences after the latest update? I also have a second Tab S2 (T813) and now it's offering the update (21 July). Don't know where to go from here... is this now a paper weight. I would appreciate any help.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
2
I'm using a self-built LineageOS 16.0 (Android 9) on a Dutch T813. Google no longer actively provides security patches for Android 9, so LineageOS can't implement them, and I can't bake them into the ROM. Sadly, it's stuck at 2022-01-05.
I have tried LineageOS 17.1 from this thread, but wasn't happy without a working camera. That was a show-stopper for me.
For the moment, I can make no definite recommendation as to which ROM is 'better'; stock Android is perfectly fitted to the device, but stuck in the proverbial stone age. LineageOS 16.0 is newer and 100% working, but also stuck at it's current level of security. LineageOS 17.1 should be buildable, but has no working camera.
Take your pick Sorry.
Kind regards,
FWieP -
68
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:* [B][U]Your warranty is now void.[/U][/B] I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or your 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, I will laugh at you.
FREQUENTLY ASKED QUESTIONSQ: The room is bootlooping the first time I attempt to boot into it after clean flashing. What should I do?[/COLOR]
(Please read them BEFORE posting anything in the thread!)
A: Force reboot using the Power and Volume Down buttons. The rom will boot properly the second time around. This is a known bug and it affects clean flashes only.
Q: Whenever I try flashing any lineage-17.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.4. Simply flash the linked below version 3.4 or higher, reboot back into recovery, and flash the rom zip again.
Q: Will any of the variants ever receive official builds from LineageOS?
A: No.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
ROMs
pitrus-
- SM-T713: gts28vewifi
- SM-T719: gts28velte
- SM-T813: gts210vewifi
- SM-T819: gts210velte
Open GApps
Magisk
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 17.1 variant, which corresponds to the model of your tablet!FULL WIPE (with external microsd card)
How to flash LineageOS and Open GApps
FULL WIPE (without external microsd card with NO Home PC access)
FULL WIPE (without external microsd card with Home PC access)
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your tablet and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the tablet.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- The rom bootloops only after clean flashing. Force rebooting allows it to boot properly the second time and every time afterwards. See the FAQ's above.
- The cameras work, but with a delayed response, so they are impractical to use.
- T719 & T819: RIL does not work at all.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developer in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Luk1337 and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the gts28velte, gts28vewifi, gts210velte, and gts210vewifi.
Sources
- LineageOS
- team-infusion-developers
XDA:DevDB Information
LineageOS 17.1, ROM for the Samsung Galaxy Tab S2
Contributors
pitrus-
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2020-03-25
Created 2020-03-21
Last Updated 2021-11-1027Reserved
TWRP 3.5.2_9-2
The official TWRP for all four variants is built by TeamWin's servers from the outdated android-6.0 branch. A major bug in this branch is that mtp is broken, so I ran my own builds from the android-7.1 branch. I fixed hw encryption, which is why I bumped the version number up to "-2":
twrp-3.5.2_9-2-gts210velte
twrp-3.5.2_9-2-gts210vewifi
twrp-3.5.2_9-2-gts28velte
twrp-3.5.2_9-2-gts28vewifi17Since all ROMs got deleted and it looks like there won't be any new ones I decided to do something about this.
My T719 is still in perfectly good shape and it would be a shame to dump it to the landfill.
So I spend the last two days digging through Repositories and recreated the build processes originating from ripee's original post, giving these devices a second life.
Download from my GDrive.13
Yes, I'm almost done reviewing my commits so far. Real life is busy lately.
New posts
-
-
Question Is it a good time to download the Android 13 beta or wait?- Latest: cyberdionisio
-
-
