[ROM][UNOFFICIAL][10] LineageOS 17.1 [T713][T719][T813][T819]
- Thread starter ripee
- Start date
I'm assuming the problem is with the update itself.
The update may need a newer version
I have tried all ways to install and they are all unsuccessful
Thank you so much for the continued support of this awesome OS, that breathes new life into our aging devices.
In this instance, I've encountered a problem: I've followed the steps for the "FULL WIPE (with external microsd card)" section.
I've installed the modded "twrp-3.5.2_9-2-gts210vewifi" that Ripee made available and was able to both install TWRP using Odin on my SM T813 and clean flash "lineage-17.1-20220311-UNOFFICIAL-gts210vewifi" as well as "open_gapps-arm64-10.0-pico-20220426"
Everything went fine and I wiped cache/Dalvik at the end and rebooted.
Upon reboot, the lineage boot animation shows up and stays like that indefinitely. The original post mentions that we need to force reboot the tablet for it to boot correctly, so I did that.
However, upon rebooting, the Lineage boot logo animation stays on for a minute or so and then the tablet reboots into recovery.
I've tried wiping everything again and reinstalling (same result) and installing LOS 16 as well. It always ends up doing the same thing.
Any help would be appreciated
In this instance, I've encountered a problem: I've followed the steps for the "FULL WIPE (with external microsd card)" section.
I've installed the modded "twrp-3.5.2_9-2-gts210vewifi" that Ripee made available and was able to both install TWRP using Odin on my SM T813 and clean flash "lineage-17.1-20220311-UNOFFICIAL-gts210vewifi" as well as "open_gapps-arm64-10.0-pico-20220426"
Everything went fine and I wiped cache/Dalvik at the end and rebooted.
Upon reboot, the lineage boot animation shows up and stays like that indefinitely. The original post mentions that we need to force reboot the tablet for it to boot correctly, so I did that.
However, upon rebooting, the Lineage boot logo animation stays on for a minute or so and then the tablet reboots into recovery.
I've tried wiping everything again and reinstalling (same result) and installing LOS 16 as well. It always ends up doing the same thing.
Any help would be appreciated
Did you do a system restart from TWRP? That solved this problem for me. I use LOS 16. Good luck
You mean after installing the rom and gapps? I installed Lineage OS 17.1 and gapps arm64 nano and then wiped cache dalvik and them clicked on the boot option in TWRP and it just boot looped. I force restarted just like the instructions and it boot looped again for a bit until going back to TWRP recovery mode.
So the way I got this to work for me was:
Boot into recovery (TWRP 3.6.2) then I advanced wiped everything out including the micro SD card and excluding USB OTG.
After wiping everything down went to WIPE then FORMAT DATA.
After that, I plugged in my USB cable from my computer and moved Lineage OS 17.1 and MindtheGapps ( I used android 10 ARM64 - my device model is T713) to the internal storage.
Installed Lineage and MindtheGapps then wiped cache Dalvik.
Reboot- after a couple of minutes, maybe like 5 min, I pressed Power button and volume down. And the device booted normally.
The camera doesn't work with the default app but I think you can get it to work with other apps.
Hope this helps!
Thank you for the May 5 update (16). My TabS2 works fine on that. For the first time I used the Updater under system settings. So i have to wait and see how that develops 
I also replaced the battery. That's a good investment. I use this tablet for media applications. Many thanks for this fine rom.
I also replaced the battery. That's a good investment. I use this tablet for media applications. Many thanks for this fine rom.
Last edited:
A nice experience but unfortunately it does not work. After a few days, the apps crash. Can restore a backup. A clean installation is required for the future!Thank you for the May 5 update (16). My TabS2 works fine on that. For the first time I used the Updater under system settings. So i have to wait and see how that develops
KeepingItCuttingEdge
Senior Member
I also have a couple S3 T-820 Tabs. Today I was fully wiping one and reinstalling LOS 18.1, so just thought I'd give F2FS a chance and IT WORKS. Seemed to gain a little peppiness with it, so now my question -- How difficult is it to add support for it into this ROM? (Tried to install with it on the S2 T-713 and it didn't work.)
THANKS and enjoying the May update!
THANKS and enjoying the May update!
KeepingItCuttingEdge
Senior Member
Also I've been using TWRP 3.6.0 since it was released and have had zero issues, so would you recommend using your 3.5.2-2 or the official 3.6.1 from them? Does their newer release fix the errors you corrected? Or could you easily rebuild their 3.6.1?
I don't use MTP nor do I need HW encryption.
Last edited:
I would like to give my experience since I was almost about to give up. I am giving the success steps at a high level. Details of these can be found throughout many posts.
1. Download latest TWRP for your device.
2. Download latest ODIN.
3. Download latest lineage for your device.
4. Download latest nano or pico open gapps for your device (ARM-64)
5. Unlock the bootloader in your stock ROM
6. Boot your device into download mode.
7. Flash TWRP with ODIN on the AP portion of the tool. For options, uncheck auto reboot.
8. When flash is complete, reboot to rescue mode. (Hold power and volume down until screen goes black. Immediately switch to holding power, volume up and home) It will boot to recovery. If this fails, you might need to reflash at step 7.
9. From TWRP recovery, swipe to choose to allow modification (if it asks).
10. Choose WIPE and then choose format data. This will wipe out everything including internal storage. And it will prep your partition.
11. With the device plugged into your usb, copy over your lineage and open gapps to your internal storage.
12. Choose reboot to recovery again.
13. Choose WIPE and then factory reset.
14. Choose WIPE and then advanced. Choose dalvik, system, data, and cache. Do not choose internal storage
15. Choose install and then select your lineage ROM
16. Choose install and then select your open gapps
17. Choose reboot
18. Right after the lineage boot animation starts, hold power and volume down to force another (2nd) reboot (this is critical or it will stay in that animation indefinitely)
19. The second boot will take ~ 5 minutes and then you are set.
1. Download latest TWRP for your device.
2. Download latest ODIN.
3. Download latest lineage for your device.
4. Download latest nano or pico open gapps for your device (ARM-64)
5. Unlock the bootloader in your stock ROM
6. Boot your device into download mode.
7. Flash TWRP with ODIN on the AP portion of the tool. For options, uncheck auto reboot.
8. When flash is complete, reboot to rescue mode. (Hold power and volume down until screen goes black. Immediately switch to holding power, volume up and home) It will boot to recovery. If this fails, you might need to reflash at step 7.
9. From TWRP recovery, swipe to choose to allow modification (if it asks).
10. Choose WIPE and then choose format data. This will wipe out everything including internal storage. And it will prep your partition.
11. With the device plugged into your usb, copy over your lineage and open gapps to your internal storage.
12. Choose reboot to recovery again.
13. Choose WIPE and then factory reset.
14. Choose WIPE and then advanced. Choose dalvik, system, data, and cache. Do not choose internal storage
15. Choose install and then select your lineage ROM
16. Choose install and then select your open gapps
17. Choose reboot
18. Right after the lineage boot animation starts, hold power and volume down to force another (2nd) reboot (this is critical or it will stay in that animation indefinitely)
19. The second boot will take ~ 5 minutes and then you are set.
Hi!
I tried this probably 4 times, but I can't get the rom to boot...
I'm on t-819, downloaded twrp, lineage 17.1, gapps.
Anyone have any magic that i can do to get this oldie booted??
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Android 9 is more stable than 10 on T813.
But I still get a reboot every once in a while.1
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? -
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.
