yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] bschatzow:
Problem updating one device

I have two Samsung SMT813 that I have been using Lineageos 16.0 on. On one I can not update with any rom newer than 8/4. The other works on all the updates. I thought I set them up the same.

The one that fails gets error 7 Both have the same version of TWRP. Any ideas on how to fix this?

I was able to find the problem and need to update the firmware on the second device. I thought that they were both on the same version.

Thanks.
[Galaxy Tab S2 Original Android Development] OhioYJ:
Sounds like they are not. A new version of firmware was actually released this year. You have a couple options:

Heimdall.

Odin.

The Odin route is probably easier, I have not used it. I went the Heimdall route. I've used Odin before though to restore my tablet in a long time ago though.

This thread mentions where to find the firmware as well.
[Galaxy Tab S2 Original Android Development] tony950:
Not able to flash the latest nightly build

used to be able to install lineageos 16 on my galaxy tab s2 sm-t813. latest twrp is installed on the tablet. latest nightly build of lineageos 16 is on the sd card. i got through all the proper steps to flash the zip file. it does what its supposted with with no errors that show up in twrp during the flashing process. after the flashing process completes i reboot the thing. the lineageos splash screen show ups. does its thing for a few minutes then tablet reboots after and goes right back in to twrp. anyone have any ideas of what might be going on?
[Galaxy Tab S2 Original Android Development] OhioYJ:
I just updated to the 9-19 version. I assume since you got no errors you are on the latest firmware.
[Galaxy Tab S2 Original Android Development] sprocket12:
Samsung Keyboard-- no mouse

Finished installing LineageOS 16 on Galaxy Tab S2 T-813. Had difficulty with TWRP going into recovery boot loop but re-applied TWRP through Odin and all is great. Well, except one thing...

I am using the official Samsung keyboard with trackpad. LineageOS fixed the annoying 'turning off screen' when the keyboard was folded behind to use Tab S2 solely as a tablet, but now I have a new problem. The mouse cursor is not displayed and is not functioning. Is this a bug, feature, or just not implemented? I could have sworn that I saw my mouse at one point during configuration after I had everything installed...

Other than that, my Tab S2 has new life!

-S

---------- Post added at 07:57 AM ---------- Previous post was at 07:47 AM ----------

Ok, I always thought I wasn't crazy...

After posting, I thought of the term 'trackpad'. I went into preferences and did a search. Nothing. However, I ran my finger across the trackpad and it APPEARED! What's up with that??? :eek:
[Galaxy Tab S2 Original Android Development] srt10coupe:
lineageos 17 ?
[Galaxy Tab S2 Original Android Development] nw47978:
1st LOS install not going well. What am I missing?

Apologies up front -- I've never done this before so please be patient with me...

I'm trying to get LOS installed on my T813 but can't seem to get into TWRP. It seems to keep resetting the factory recovery image. Here's what I've done:

1. reset tablet to factory

2. went though the setup wizard (time zone, google/Samsung accounts, etc) skipping most of it where I could

3. enabled developer options (and USB debugging)

4. used Odin v3.13.1 with CF-Auto-Root to (I think) root and install TWRP (said it passed)

If I use the Auto Reboot option in Odin, once the upload is complete, the CF-Auto-Root seems to run, but then it says "restoring stock recovery" and reboots. If I let it finish booting, the system says it's rooted and the SuperSU app is installed and seems to be working.

If I don't select the Auto Reboot option, the screen is stuck on the download page and the only thing I can do is a soft reset (power and volume down). From there I get to the recover mode, but again, it's overwritten with the factory recovery image.

If I use the factory Recovery and whether I try "apply update from SD-Card" or "apply update via ADB", I get errors that say "signature verification failed" and finally "installation aborted."

I've been at this for at least a couple of hours now and I'm running out of things to try (and google hasn't been helpful - probably not searching for the right things). I think (hope) I'm missing a simple step, but I have no idea where to go from here other than back to stock.

Thanks for any help or suggestions you can offer!!
[Galaxy Tab S2 Original Android Development] Atreya1:
When you've flashed twrp you need to power down. If you let it restart it will install stock recovery. From power down start in recovery mode and it should boot into twrp recovery mode.

Hope this is of help
[Galaxy Tab S2 Original Android Development] nw47978:
Thanks Atreya. The problem is, if I do the auto reboot in Odin, then we know the outcome (re-installs stock recovery). If I uncheck the Auto Reboot option, then the flash finishes on the "Downloading..." screen and the only key combination I can find that works from there is power+volume down (which restarts it and re-installs the stock recovery). Is there a different combination to try that I can't find? (It doesn't look like the battery is removable).
[Galaxy Tab S2 Original Android Development] supachris:
You have to press Home and Vol up immediately after the screen goes black to reboot into recovery. This installs twrp permanently.
[Galaxy Tab S2 Original Android Development] nw47978:
I can't believe I'm having this much trouble. I'm not having any luck. Am I supposed to hold down Home and Vol Up? (I've tried both ways - holding down and just pushing once). Should I be using the Auto Reboot option in Odin?

Whatever I do, it just kicks off the CF-Auto-Root, then the SuperSU installer and eventually "Restoring stock recovery". I tried this as well with no luck (from another thread here):

1. BEFORE pressing start on your computer, hold volume up and home button.

2. Now press start on the computer, keep your fingers on the volume button up button and home button. Let the PC and Phone start it's process.

3. The moment the phone screen goes black. Press and hold the power but while keeping your fingers on the volume up and home button.

4. Keep all the buttons held down (volume up, home button and power button) till you see the TWRP screen boot.

---------- Post added at 07:20 PM ---------- Previous post was at 06:39 PM ----------

Is this accurate or outdated? Do I need a custom kernel?

"The S2 has a weird way that it deals with recovery. It technically has a recovery partition but it isn't used and instead the recovery is usually installed with the kernel. What flashing the custom kernel does is the LineageOS kernel contains a thing called IsoRec that redirects the device to the recovery partition (where TWRP is) when recovery is booted. "

(from: https://www.reddit.com/r/LineageOS/comments/603qeq/cannot_boot_into_twrp_on_samsung_galaxy_s2/)
[Galaxy Tab S2 Original Android Development] nw47978:
more info

Ok, it looks like I was missing something. When it first tries to go to recovery mode, there's a message that says "recovery is not seandroid enforcing". Does that add any more info?
[Galaxy Tab S2 Original Android Development] jyotisankar9:
I had similar issues trying to get LOS 16 installed. But instead of using CF Auto root, I was just trying to flash TWRP. This is what I did,

1. Get tar file for TWRP from official website.

2. Put tablet to download mode, connect to PC.

3. Use AP button to flash TWRP, make sure auto reboot unchecked.

4. Once you see success msg, disconnect the tab.

5. This is where the trickiest part, press Vol Down+home+power to initiate reboot, however change to Vol Up when screen goes black.

6. This time TWRP should boot.

7. You can format Data, System and Cache, mount internal storage to copy zip files for LOS, GApps and SU of your choice. And install all of those in sequence and reboot.

Hope it helps.
[Galaxy Tab S2 Original Android Development] nw47978:
Thanks. I think I'm understanding the process more now (plenty of practice!) but I believe the problem is related to something I was missing. I get it to boot to recovery mode after flashing, but there's a brief message that "recovery is not seandroid enforcing". From what I can tell via google, it sounds like I might have the wrong version of something? I just don't know what.
[Galaxy Tab S2 Original Android Development] nw47978:
Thanks for the suggestions. I just wanted to let you know that I either had the wrong twrp file or it was corrupt. I downloaded it again and am moving forward with the LOS install...
[Galaxy Tab S2 Original Android Development] bschatzow:
Did you ever find a solution to this.? I have two devices with the identical problem (except message is in English).
[Galaxy Tab S2 Original Android Development] herbi1966:
Did you format Data when whiping for clean install?
[Galaxy Tab S2 Original Android Development] bschatzow:
I did on both devices.
[Galaxy Tab S2 Original Android Development] Deltadroid:
There could be an issue with magisk.
[Galaxy Tab S2 Original Android Development] bschatzow:
Not using Magisk. I was, but I switch as I was told that may be the problem.
[Galaxy Tab S2 Original Android Development] moloko01:
No really solutions, got two devices SM-T813 and SM-T713. I found out, it is a problem with magisk module Substratum. So if installed you have to go to recovery and clean Dalvík cache. Each time if you need a reboot. Or disable Substratum in magisk.
[Galaxy Tab S2 Original Android Development] rogers11:
Don't know if it matters in this case but you should use the 64 bit version of the add-on.
[Galaxy Tab S2 Original Android Development] bschatzow:
It was. It would not work if it wasn't.
[Galaxy Tab S2 Original Android Development] Atreya1:
Another thought the samsung latest ota update
[Galaxy Tab S2 Original Android Development] srt10coupe:
[MENTION=5075128]LuK1337[/MENTION] are you planning lineageos 17 for t813?
[Galaxy Tab S2 Original Android Development] LuK1337:
I don't even have it anymore. I gave it to my sister ^.^
[Galaxy Tab S2 Original Android Development] ripee:
So that means T713, T719, and T819 won't get 10 from you either? Too bad.
[Galaxy Tab S2 Original Android Development] LuK1337:
Obviously ^.^
[Galaxy Tab S2 Original Android Development] ripee:
Not really. It was easy enough for you to port Pie to all 4. Don't you want your sister to enjoy 10 on her tablet? :)
[Galaxy Tab S2 Original Android Development] LuK1337:
No, I don't care. If you still want to use something maintained by me, feel free to upgrade to Tab S5e ;3
[Galaxy Tab S2 Original Android Development] ripee:
Sorry that you don't care. From what I understand, blind device maintenance is no longer frowned upon. But thank you for all you've done and for being honest.
[Galaxy Tab S2 Original Android Development] 00schneider:
damn, bought me an extra one last week, but thanks for the pie port.
[Galaxy Tab S2 Original Android Development] ripee:
I'm sure someone else will pick up the torch. I will help as much as I can.
[Galaxy Tab S2 Original Android Development] OhioYJ:
That is actually very exciting news, there have been no new Lineage tablets for too long. Sounds like I maybe upgrading soon...
[Galaxy Tab S2 Original Android Development] weinbers:
I'd contribute to you, Ripee, if you pick up the mantle for this and the 713 (I have both).
[Galaxy Tab S2 Original Android Development] moro1964:
Thanks for the great work !!! My tablet got a new life. Do not tell me how to enter the engineering menu on this firmware? I want to slightly increase the volume of the speakers.
[Galaxy Tab S2 Original Android Development] ripee:
If you have both tablets rooted, can you please go to this folder: /sys/class/rtc/rtc0 and tell me if the value in the "time" file matches that of the clock in the status bar? For some reason the tablets aren't registering the proper time, and this is why it's incorrect in TWRP. I am working on a fix in TWRP, but if it can be fixed in Lineage, all the better.
[Galaxy Tab S2 Original Android Development] weinbers:
Both are rooted and that file is empty on both devices. Twrp displays the correct time on the 813 but is off about 8 minutes on the 713.

Let me know if I can help in any other way.
[Galaxy Tab S2 Original Android Development] acme64:
just did a clean wipe and install from stock T813. LineageOS makes it to the boot logo but thats it, it'll reboot back to recovery. i'm on twrp 3310 and lineage-16.0-20191006-nightly-gts210vewifi-signed.zip with MindTheGapps-8.1.0-arm64-20180808_153856.zip. Any clue why i'm looping?
[Galaxy Tab S2 Original Android Development] supachris:
I'm pretty sure you have to use the 9.0 GApps on LOS16. This may cause your bootloop.
[Galaxy Tab S2 Original Android Development] acme64:
that was it, thanks!
[Galaxy Tab S2 Original Android Development] Sickyman678:
There's this random issue when you stream Spotify and listen via Bluetooth the sound lags/cracks a bit.Its hard to explain.Anyone else have this issue?
[Galaxy Tab S2 Original Android Development] Entodoays:
This issue is also annoying when my bluetooth keyboard is connected. Even when cover is closed, the tablet responds to key presses. This is annoying when I'm moving with tablet anf keyboard in hand or in a backpack. The only workaround that I can see is setting the Home button not to wake the device, but that would mean that it would no longer be possible to wake the tablet not even when the cover is open. Is there a chance of getting this fixed?
[Galaxy Tab S2 Original Android Development] peacepipe:
Hi community,

first thanks to Luk for this amazing work.

I haven't used my tablet for a while and wanted to go straight to the latest version. So I first downloaded the latest Samsung firmware with the tool SamFirm and installed it via Download Mode. Then I installed the current version 3.3.1-0 of TWRP, did a factory reset with TWRP and tried to install a nightly build of LOS 16 + opengapps + addonsu. After installing this packages I restart and I see the bootlogo of LOS. After a while the device restarts and I see TWRP again. What happened here? I followed the instructions of this: https://wiki.lineageos.org/devices/gts210vewifi/install

BR

peacepipe
[Galaxy Tab S2 Original Android Development] Deltadroid:
The issue could be with opengapps. You could try MindTheGapps instead.
[Galaxy Tab S2 Original Android Development] peacepipe:
This issue occurs also if I only install the LOS 16 ROM without addonsu or opengapps.
[Galaxy Tab S2 Original Android Development] Deltadroid:
TWRP 3.3.1 also is broken with encryption and perhaps other things. I recommend TWRP 3.2.3 instead. Which means, you would need to format your /data partition over again using TWRP 3.2.3 in order to create a usable encryption footer.
[Galaxy Tab S2 Original Android Development] peacepipe:
Well, I don't know what actually helped. I wiped all partitions except my sd card and install the image from sd card and not via adb sideload. What ever it works now. Thx!
[Galaxy Tab S2 Original Android Development] peter-piranha:
Had same issue with gapps. Alway reboot to TWRP. After installing MindTheGap Apps it worked.

TWRP 3.3.1 with odin.

Gesendet von meinem SM-T813 mit Tapatalk
[Galaxy Tab S2 Original Android Development] herbi1966:
Same issue with Gapps, took an older version and worked again.
[Galaxy Tab S2 Original Android Development] harryrasul:
can someone help me to install netflix or which version of the app apk to install..I tried installing the latest build apk and upon trying to install, I get "app not installed" error. Any help would be appreciated..
[Galaxy Tab S2 Original Android Development] Atreya1:
Why apk???? Why not through play store
[Galaxy Tab S2 Original Android Development] bschatzow:
Can you add the mind the gaps install after you do an update as a dirty install from twrp? I believe my random reboot issues maybe related to the gaps install instead of using of using the recommended mind the gaps for the Google apps.
[Galaxy Tab S2 Original Android Development] BlueCyclone:
AFAIK, gapps need to be flashed clean, or semi clean (wipe system but not data). Gapps needs to setup on first boot of ROM.

I would try:

Wipe system, cache/Dalvik

Flash ROM+gapps

I usually wipe cache/Dalvik again

Boot system, first boot takes long

If you need root, then reboot to TWRP and flash magisk/lineage Su

Reboot back to system

Profit?
[Galaxy Tab S2 Original Android Development] bschatzow:
I did a complete wipe, reformat, etc. I then installed the old Samsung firmware (no issues), I then updated to TWRP, Then Lineage 16, Lineage SU and Mind the gaps. No change. System boots but screen is not useable. It then goes to another screen for about 10 minutes where it says system is loading. It then goes in to recovery mode where I reflash, clear data and it comes back. Not sure what the issue is, but several people have it and it doesn't seem to be related to the Gaps or mind the gaps or how it is rooted. Maybe it is one of the rooted apps that is causing the issue? It has been around for me since February and I have no clue what to try next.
[Galaxy Tab S2 Original Android Development] supachris:
Very strange. I do not have any issues like this. I had some trouble with old firmware and new LOS, but after updating with the stripped down version here the tablet runs smoothly and stable as a rock. I'm rooted with LOS SU.

For long time, I was on TWRP 3.2.3 as the newer versions do not format data correctly (missing crypto footer, but I want to have the tablet encrypted). Now I'm on the TWRP 3.3.1 Beta 3 and it works also. Not tried to format data with this (no need). I assume there is either a hardware defect or an issue with an app in your case. I'm using OpenGapps pico.
[Galaxy Tab S2 Original Android Development] bschatzow:
Have it on 2 devices that were wiped clean. Both started having problems in February. Don't think it is a hardware issue as it works on the stock firmware. Don't know what to try next.

Just saw on Reddit "WARNING: Open GApps Builds 201009, 10, 11 & 12 Fail to Boot to System & Goes to Recovery Instead"

Lots of comments from people with different phones and different gapps version. This is what I see on a clean install on my t813 with the mind the gaps.

I think there is a memory map issue where the os is allowing programs to write to incorrect locations.
[Galaxy Tab S2 Original Android Development] herbi1966:
Has anyone tried Gapps later than 201012?

I had the issue with rebooting to recovery too...

Thanks

Herbi
[Galaxy Tab S2 Original Android Development] BlueCyclone:
I think I saw on opengapps thread that 10/13 is supposed to be fixed. Otherwise use an older one and just let it update in play store
[Galaxy Tab S2 Original Android Development] rodentkj:
Add me to the list of "Thanks"

Appreciate you taking the time explaining this.

Am able to flash the latest builds after doing this.
[Galaxy Tab S2 Original Android Development] Starfiresg1:
Hi,

today I made the switch on my tablet from Samsung firmware to Lineage using lineage-16.0-20191015-nightly-gts210vewifi-signed. Flashing the build on its own worked without any problems. However when I flashed the latest Gapps with it (open_gapps-arm64-9.0-nano-20191016) the first boot is rather long an ends with an automatic reboot into TWRP recovery. Tried it several times with wiping system, cache and data in between.

Due to the reports here I was able to get it working with an older Gapps package (open_gapps-arm64-9.0-nano-20191006) - thanks :)

Using this version the first boot after flashing LOS and Gapps didn't took as long and booted correctly into the OS and the Google setup screen.

So there seems to be still issues with newer Gapps.
[Galaxy Tab S2 Original Android Development] martijnpeters:
Is there a way to disable the capacitive lights on this rom? The various apps which could turn off the lights that worked with the stock rom don't seem to work with lineageos 16
[Galaxy Tab S2 Original Android Development] Starfiresg1:
If you are refering to the button backlighting: this can be configured under settings - system - buttons - backlight
[Galaxy Tab S2 Original Android Development] OhioYJ:
I had issues with 2 other devices not booting with the 10-10 version. Just got done flashing the 10-16 version to 3 different devices (T813, OP6T, H5X), one of those being my T813, one being a clean flash, no issues at all. They all booted first try without issue.
[Galaxy Tab S2 Original Android Development] Deltadroid:
Make sure you are not installing TWRP's app when setting up recovery.
[Galaxy Tab S2 Original Android Development] Fuzzums:
Following up here with the issue that [MENTION=7714752]bschatzow[/MENTION] and I both experienced:

I re-flashed my T813 back to Lineage OS 16 2019-10-15 build after trying to see if the similar boot issue was fixed...It seems this is related to Lineage OS 16 encryption.

Doing a clean install with

•	TWRP 3.3.1-Beta03

•	open_gapps-arm64-9.0-nano-20191006.zip

•	MindTheGapps-9.0.0-arm64-20190615_031441.zip

•	lineage-16.0-20191015-nightly-gts210vewifi-signed.zip

•	addonsu-16.0-arm64-signed.zip

There was no long boot issue (taking over 20 minutes to boot) and I was able to get into the OS rather quickly. However, as soon as I enabled encryption on the tablet, that's when the same issue with the long boot time began again. Not only that, but all my 3rd party apps were completely broken and require that I perform a restore to get them functioning again. The other difference this time was there was no period of time when the screen would go entirely black and be unresponsive then reboot into TWRP recovery. I think this is related to switching from TWRP 3.2.3.0 to TWRP 3.3.1-BETA03

I wiped my tablet again, to remove encryption and restore from a backup prior to encryption, and the boot issues disappeared. At this point I'm pretty certain this is tied to encryption with Lineage OS 16. I never had this encryption problem with Lineage OS 14.1 deltas that I came from; using either TWRP 3.2.3.0 or TWRP 3.3.1-BETA03.

If anyone has experience with Lineage OS 16 encryption I'd be curious to know what others have experienced.
[Galaxy Tab S2 Original Android Development] supachris:
Hi. I have my T813 encrypted. At the very beginning I tried with TWRP 3.3.0 but this version does not preserve the needed space for crypto footer while format data.

So I downgraded to 3.2.3 and formatted again. Since this point, the LOS16 encryption is working until now. After it was available I updated to TWRP 3.3.1 Beta 3 and updates are still working. I also flashed new Samsung firmware, so LOS works flawless.

I did not yet try the broken gapps version, the LOS is quite new, I keep it updated once a week or so. I can try new versions and make backup first. I'm always using Open Gapps pico.

Edit: Currently I'm using 2019/10/05 version of both LOS16 and OpenGapps pico.
[Galaxy Tab S2 Original Android Development] supachris:
Just updated to recent LOS 2019-10-16 and OpenGapps Pico 2019-10-17. No issues so far. Normal "after update" boot time, decryption is working and system running normal.
[Galaxy Tab S2 Original Android Development] fred0r:
Why did you install both ?

You need to install open_gapps OR MindTheGapps.
[Galaxy Tab S2 Original Android Development] Fuzzums:
I initially had boot loop issue with open_gapps, so I was using MindTheGapps, but it was a very old copy. Then I switched to the non-broken open_gapps since they were up to date binaries. So I technically used both, and they each worked.

That said I'm still having issues encryption breaking core google applications on reboot with the recent October 15, 16, and 17th builds. Note, when I was first using the early July builds, LineageOS 16 was working fine with encryption. Maybe I should just revert back since the old build didn't have these issues I'm seeing today. That or I just live without using encryption, which seems like the more likely option I'll use.