yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Original Android Development] luca020400:
https://github.com/gts210vewifi-dev...mmit/7ccbdb5e6473e498d309a66f6ded4ef11f3c7570

Fixes the adsp crash ( I know you were stuck here )
[Galaxy Tab S2 Original Android Development] DeadPicsel:
Is there anyway of getting LineageOS working on Samsung T819?
[Galaxy Tab S2 Original Android Development] LuK1337:
Well, I am guessing that T813 builds would boot but you wouldn't have any radio capabilities.
[Galaxy Tab S2 Original Android Development] DeadPicsel:
I can live with that, would it brick my device tho
[Galaxy Tab S2 Original Android Development] LuK1337:
I highly doubt. Also I would recommend waiting 1~2h for the next build.
[Galaxy Tab S2 Original Android Development] Lightn1ng:
I messaged [MENTION=5073087]bu44er[/MENTION] with this ROM, but I removed the check in the updater-script to make sure it's a gts210vewifi. I'll let you know if he responds.

On a second note, I am the person [MENTION=4557146]T_I[/MENTION] was talking about earlier. I would like to learn how to port this to the T713, which I have here. Thank you very much in advance.

-Lightn1ng
[Galaxy Tab S2 Original Android Development] LuK1337:
He could just use gts210vewifi TWRP and flash it without modifying the package contents.
[Galaxy Tab S2 Original Android Development] Lightn1ng:
That would be too easy :D
[Galaxy Tab S2 Original Android Development] LuK1337:
It's not like I want people to use some unofficial TWRP builds tho. Oh btw there's newer build available, I uploaded it like 10 mins ago.
[Galaxy Tab S2 Original Android Development] ptfdmedic:
FYI: last root package works. I used 2.78 successfully
[Galaxy Tab S2 Original Android Development] Lupin The Third:
Thanks, downloading it now. :)

No fingerprint sensor yet, right?
[Galaxy Tab S2 Original Android Development] Lupin The Third:
Flashed new build.

Auto brightness = works

Wifi 5ghz connection = works

Flip cover sensor = works

Fingerprint sensor = not there yet.

Testing further. Quick impressions? This looks daily driver.

Curious to see how battery life is :)

Very well done. This tablet now shines brightly! :angel:
[Galaxy Tab S2 Original Android Development] Lupin The Third:
I still see a struggle with auto brightness. It is a hit or miss. Sometimes it works, sometimes after unlocking the device the brightness is max and doesn't adapt to the environment light.

So I set it to manual and looks good at the moment.
[Galaxy Tab S2 Original Android Development] T_I:
In the Tab S2 2015 builds we setup a gts2-common for all devices, with the device specifis parts in gts210wifi, gts210ltexx,... trees. I'd advice to do the same for the 2016 version. Difference between wifi and lte for 2015 were radio and gps (gps on wifi doesn't use lte libs) and differences between 210 and 28 were display/gpu related. (nothing more)

The same was done for vendor (TheMuppets), general blob store for blobs that didn't differ between te devices, specific stores for differences. To get wifi with the most channels working we used the cellular south stock image.

---------- Post added at 10:26 AM ---------- Previous post was at 10:21 AM ----------

Where do you download the root package?

Edit: Never mind, official root package not yet available, the one mentioned was SuperSU 2.79. (and yep, it works)
[Galaxy Tab S2 Original Android Development] luca020400:
Automatic brightness is bad as on stock for me :P

The light sensor isn't what you'd call "fast"
[Galaxy Tab S2 Original Android Development] Lupin The Third:
Manual brightness is fine for me though. Not an issue.

I hope the fingerprint sensor will be fixed. That would be nice to have.

On a positive note the battery life looks great until now. :svetius:

I'm keeping this as a daily driver (for now :))
[Galaxy Tab S2 Original Android Development] T_I:
I've choosen this as daily. Just made the first back-up with TWRP and it's only 4.7G, compared to the 8.7G of the stock image with all my apps in it.

However, my audio setting on stock were stuck on 'concert hall' (or something crappy like that), which it's still on in this image. Any way to kill this setting without having to restore stock to kill it? Found this post, but that doesn't help me much as I can't find the settings I need in L1ghtning image, so I'm now reverting to stock. This setting is very anoying, as I use the tab to listen to music at work. (Had the same issue on stock though, so no reason to switch back permanently)
[Galaxy Tab S2 Original Android Development] LuK1337:
This is not for Tab 2, this is for Tab S2.
[Galaxy Tab S2 Original Android Development] Godapol:
I tried yesterday to install LOS, but failed, I ended in a softloop. Could restore with Odin and an image from Sammobile. I used the guidance in the wiki: https://wiki.lineageos.org/devices/gts210vewifi

So... are the instructions wrong or is it better to wait? I read a lot of flashing single files the last few pages. I read somewhere else that I should deactivate OEM... is this true?

Thx for answers!
[Galaxy Tab S2 Original Android Development] alex1301:
Hey Guys, gonna get a T819 version tomorrow. Now I want to ask if there's any chance to get this version of Lineage up and running on the 819 version. I can live without LTE and GPS.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] pastorbob62:
Your post is worthless for getting help. What version TWRP? Coming from stock or another custom ROM? If stock, MM or Nougat? If custom clean or dirty flash? I realize you posted a link to the instructions you followed but they are outdated. e.g. the version TWRP it says to use is wrong for Nougat and Nougat based ROMs. It also does not mention formatting the /data partition which is necessary when coming from MM to Nougat.

That is just a few of the problems with your post.

@ LuK1337 - The instructions on the OP really need to be updated. There is no mention of the changes that came into play when coming from MM -> Nougat -> Lineage. The correct version TWRP should be mentioned and also the need to be on the latest baseband before flashing. Not trying to tell you what to do, but expecting noobs to come in and read 39 pages of postings to get extremely basic but pertinent info before flashing is asking quite a lot. I have even seen some veterans screw it up. Again, just a suggestion. ;)
[Galaxy Tab S2 Original Android Development] Godapol:
Bought a new T813 with Nougat, flashed directly twrp-3.1.0-1-gts210vewifi.img (i saw now that there is a new version out) with Heimdall. Then I was stuck. Went back to Stock with Odin, tried an other way:

https://xdaforums.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627

With this I was able to get TWRP, SU installed and was able to work in stock. Then I installed LOS and was stuck in the beginning with the "Setup wizard".
[Galaxy Tab S2 Original Android Development] pastorbob62:
Did you do a backup from TWRP before flashing anything? Did you clean or dirty flash? When you say stuck in the setup wizard, is it repeatedly crashing? If so, did you flash open gapps at the same time as the ROM? It would really help if you would provide a step by step description of what you did from the point you had rooted/stock Nougat working, (assuming that is the case).. Then I would know how to advise you.
[Galaxy Tab S2 Original Android Development] Godapol:
Nope, no backup at all, directly out of the box, plugged to my PC and started Heimdall. I flashed TWRP and tried to reboot and the tablet was stuck, only download-mode worked. Then I flashed stock with Odin.

Next day I installed TWRP again with Odin (as descripted in the other thread, with the Boot Patch and SuperSu), this worked. Then I started the tablet and played a bit with stock. After that I put in a SD-Card with LOS and OpenGAPPS nano (arm64) and installed LOS, OpenGAPPS and SuperSu (zip) and made a Wipe. After that LOS started but was stuck while "setup wizard has stopped...". Tried this trick with permission and so on but they where already on allowed.

https://www.youtube.com/watch?v=l4nJPPE11XA

So this evening I will reflash stock and then TWRP plus SuperSu and will wait a few weeks.
[Galaxy Tab S2 Original Android Development] Deltadroid:
The setupwizard issue is most likely caused by opengapps. You can try the Nougat Base gapps package for arm64 that I posted here
[Galaxy Tab S2 Original Android Development] pastorbob62:
If you flash Lineage first, boot into system, set up then reboot into TWRP and flash open gapps it is no problem. Been there, done that. Actually did it this morning and my tablet is working great.
[Galaxy Tab S2 Original Android Development] Deltadroid:
You must flash gapps and lineage before booting into the system for the first time or the correct permissions will not be given to gapps. Permissions are given upon first boot only.
[Galaxy Tab S2 Original Android Development] Godapol:
so, this is now interesting. :D
[Galaxy Tab S2 Original Android Development] pastorbob62:
Huh? It hasn't been a problem for me, but then I may not run any apps that can cause an issue. Although I seriously doubt that is the case. The only thing is I have to setup google play and my google account upon first use. Be that as it may I have flashed open gapps this way on both my phone and tablet more than once and all apps work well. Not to mention that opengapps pico is 40 Mb smaller than the minimalist package you are pushing. Just sayin'. ;)
[Galaxy Tab S2 Original Android Development] Godapol:
My problems are definitely based on OpenGapps. Tried several scenarios, but the only thing what worked where the modified Gapps from this thread: https://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
[Galaxy Tab S2 Original Android Development] pastorbob62:
Don't know what to tell you man. I'm using opengapps without any issues. I am also using them on my phone. But if flashing minimal gapps works for you more power to ya. :good:
[Galaxy Tab S2 Original Android Development] Godapol:
I did everytime a clean install as recommended here:

https://github.com/opengapps/opengapps/wiki/FAQ

TWRP => Flashing LOS, Gapps and SU => Setup Wizards hangs

TWRP => Flashing LOS => Setup Wizards runs through => TWRP => Flashing Gapps => No booting

TWRP => Flashing LOS, DeltaGapps and SU => Setup Wizards runs through.
[Galaxy Tab S2 Original Android Development] pastorbob62:
The second method worked for me. :confused: Beats me.
[Galaxy Tab S2 Original Android Development] alex1301:
Really nobody?
[Galaxy Tab S2 Original Android Development] caprihome:
I also would like a version for the t819.
[Galaxy Tab S2 Original Android Development] zeroyoo:
I guess I had a similar problem and found a solution on another thread for the hanging Setup Wizard: once the wizard started, pull down the quick settings bar and enable WIFI. I could then complete the wizard without problems.
[Galaxy Tab S2 Original Android Development] Zacharee1:
Wow I've really been out of it for a while. We have an official LOS build and TWRP! I'm a little confused though. My 813 is on a Marshmallow base still. Do I need to ODIN the new Nougat stuff that I hear has been released before flashing TWRP 3.1 and this ROM?
[Galaxy Tab S2 Original Android Development] Zacharee1:
Alright. Nevermind to that. I dove in head first, and tried to flash LOS after upgrading TWRP. Told me I needed Nougat, so I downloaded the image, flashed with ODIN, flashed TWRP again, rebooted to recovery, and all went well.
[Galaxy Tab S2 Original Android Development] Modest Mind:
Dear friends

Recently I got my GT S2, T813 runing on firmware T813XXU2BQD1 (Germany). I flashed twrp, reformated data to remove encryption, flashed Super SU, flashed no-verity, reboted, switched off again, entered recovery, advance wiped, flashed LOS 14.1 (versions 20170523, 20170516, 20170509 separatelly in this order), gapps, addonSU. Notice says flashing was successfull. I rebooted the system but LOS setup would not display (would not go past "set up as new"). I tried flashing all 3 versions also without gapps and without addonSU. No success. I installed (via odin) the follow up firmware T813XXU2BQD3 (Open Austria), and tried the same procedure as above, but here again LOS setup would not go past "set up as new".

Anyone any idea how to solve this problem?

P.S.: Funny thing though, only one time I could manage to install omni rom (version 20170521) without gapps and superSU. Obviously I wanted gapps and rooted phone so I wiped it and reflashed rom + gapps + superSU but this too would not display past "set up as new"!
[Galaxy Tab S2 Original Android Development] Zacharee1:
When you tap "set up as new" and Setup Wizard crashes, dismiss the crash dialog and instantly start swiping from the top of the screen to get the notification center to show. Go into settings from there and connect to WiFi. Back out into the setup and it'll work. It's an actual LineageOS problem.
[Galaxy Tab S2 Original Android Development] Modest Mind:
That actually did the trick with the firmware T813XXU2BQD1. Now I have LOS 14.1 running on my Tab S2. Thanks a lot!!!

Flashing LOS 14.1 from firmware T813XXU2BQD3 was always “fail”!
[Galaxy Tab S2 Original Android Development] dapat:
Same here. I tried it on T813XXU2BQD3 (nougat) and it won't install.
[Galaxy Tab S2 Original Android Development] Deltadroid:
The next nightly build will support installing with both T813XXU2BQD1 and T813XXU2BQD3 firmwares.
[Galaxy Tab S2 Original Android Development] alex1301:
It's amazing that nobody, not even the dev, is able and kind to answer that easy question...

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] Deltadroid:
The problem with using firmware that is designed for a different device is that the lineage installation checks the version of the bootloader you have. A different model device will not have the correct version of the bootloader and will probably not even install.
[Galaxy Tab S2 Original Android Development] alex1301:
Yeah, but since these two tablets are besides the radio the same, wouldn't it be enough to delete the model check in the installer script?

I don't even get why it's that hard to get Lineage on the 2016 LTE Version of the Tab S2...

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] LuK1337:
T819 / T719 would require some changes to get it supported properly. I only own a T813 and I won't be working on LTE variants.
[Galaxy Tab S2 Original Android Development] alex1301:
Ok, that's not good to hear, but thanks

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] LuK1337:
You probably could boot T813 builds with just removing the assert but don't report any bugs if you do so.
[Galaxy Tab S2 Original Android Development] alex1301:
Maybe I will try it this weekend :D

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] Zacharee1:
You saw how long it took to get any form of AOSP on even just the WiFi variants of the Snapdragon S2. This device, I hear, was troublesome because of the chipset. Since it's also Samsung, and not really a flagship device, that means a smaller dev scene.

You should definitely try flashing this. If it works, you've confirmed that just the radio and such need to be worked on, instead of an entire new build.
[Galaxy Tab S2 Original Android Development] alex1301:
I don't really know how long it take since I got the S2 only some days ago, but I know from other devices how sh**** it could be without proper source.

If something messes up, I can completely revive it via Odin, right?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] LuK1337:
No, it wasn't troublesome because of chipset lol. Just no one was working on it.
[Galaxy Tab S2 Original Android Development] Zacharee1:
Hmm. The person who built RR was complaining about the lack of a device tree for the 652.
[Galaxy Tab S2 Original Android Development] LuK1337:
It's not my fault he's unable to do more than `brunch gts210vewifi`. We made the device tree ourselves lol.
[Galaxy Tab S2 Original Android Development] Zacharee1:
Oh, nice! Honestly, you don't know how glad I am to see more development for this tablet, especially an official ROM with nighties. It's great.
[Galaxy Tab S2 Original Android Development] alex1301:
Ok, tried to flash it. Flashing works fine after deleting the lines in the updater script. But booting is the problem. The tab only boots to recovery. I know this problem from the OnePlus 3, where this happened due to incompatible firmware and/or bootloader. So if nobody is willing to add these things to the source, LOS will not happen...

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy Tab S2 Original Android Development] FitzWM:
I can't get the latest nightly to install on my tablet. I installed one of the first builds of the official LineageOS a while back, and I just haven't bothered to update the ROM since. Now, the TWRP installer is telling me, "This package supports bootloader(s): T813XXU2BQD1, T813XXU2BQD3; this device has bootloader T813XXU2APK6." And then the installer exits with Error 7. Any ideas for how to proceed?
[Galaxy Tab S2 Original Android Development] LuK1337:
You need to flash nougat firmware.
[Galaxy Tab S2 Original Android Development] FitzWM:
Hey, thanks! Everything's working swimmingly now. Best ROM I've ever used, bar none - and they've even ported it to my phone now!

Thanks again.
[Galaxy Tab S2 Original Android Development] c_valentine:
I had a interesting time setting up the May-30 nightlies. Setup did not crash on me, instead when I clicked restore from cloud it would tell me, I'm not connected to the Internet (true) and should chose different network. Problem was WiFi selection slide was only available AFTER I chose set up as new. Could it be that the slide order is somewhat messed up? Otherwise everything works great here! Thanks a lot to the devs!
[Galaxy Tab S2 Original Android Development] FitzWM:
Okay, so I've run into another problem. Ever since updating, I can't get either Netflix or Amazon Underground to connect to the Internet. Everything else works fine, and I can access the sites through Rocket Browser and through other devices / apps on my network. It's just the app that's broken. The only connection I can find between the two is that they're both third-party apps - Amazon because it isn't listed on the Play Store, and Netflix because the Play Store now claims that my device "is not supported," and I had to get it off APK Mirror. I mainly use the tablet as a media device, so this is cramping my style a little bit. Any ideas?

I've already tried uninstalling and reinstalling the apps, wiping and reinstalling LineageOS, wiping my external SD card, and changing DNS settings on the tablet. I'm using the Mini version of Open Gapps, but I had the same issue with the Stock version. I'm rooted using the su addon.
[Galaxy Tab S2 Original Android Development] TanayPoddar56:
It's due to the recent update that Google did to prevent root users from accessing such apps. Root breaks safetynet hence, those apps won't work
[Galaxy Tab S2 Original Android Development] FitzWM:
EDIT: Fixed it. For anyone running into the same issues, here's what I did to get root + Play Store certification, Netflix, etc.:

1. Wipe everything. Not sure if this is necessary, but you definitely need to remove LineageOS's su addon.

2. Download the latest version of Magisk.

3. Flash LineageOS, then GApps (optional), then Magisk with TWRP.

4. Boot into Android and go through initial setup.

5. Download Magisk Manager APK from APK Mirror and install. Apparently, it's been removed from the Play Store. Imagine my shock.

6. Go to Magisk Manager -> Settings and enable Busybox, Magisk Hide, and Systemless hosts.

7. Go to Android Settings -> Apps -> Google Play Store. Force stop the app and then Storage -> Clear Data.

8. Reboot.

9. Open Play Store and agree to terms. Go to Play Store -> Settings and check that "Device certification" reads "Certified".

10. Download Netflix APK from APK Mirror and install. Login and enjoy!

Fantastic. So, do I just have to choose between root and Netflix / Amazon? Or is there some sort of workaround?

Ugh, this is just the kind of proprietary crap that made me leave iOS back in the day.
[Galaxy Tab S2 Original Android Development] FitzWM:
EDIT 2: Nevermind, disregard, I'm an idiot. After a whole day of increasingly complicated troubleshooting procedures, I tried changing the DNS on my router from OpenDNS to Google DNS. And whaddya know, everything connects now. God, it sucks to be in IT and still do things this stupid.

Thanks for the ROM and the help.

EDIT: Welp, it looks like I can no longer access Netflix, Amazon, Prime Video, Audible, or Kindle - even when certified, even when non-rooted.....

I may have spoken too soon, but it seems to be a network issue, not a root issue. Netflix works fine on my work network or when I'm tethered to my phone, but fails even to sign in on my home network. Everything else on the network can connect to Netflix just fine.

Blegh.
[Galaxy Tab S2 Original Android Development] Alessandro999:
anyone can create a resurrection remix with lineage os/ stock android code?

please resurrrection is more faster and battery is much better
[Galaxy Tab S2 Original Android Development] dosludwig:
Would you please explain in detail how to do this?

I am an Android/LineageOS beginner with the same bootloader-problem, and so I am a little bit confused about "flashing (nougat) firmware" (I thought I would exactly do this when trying to install the latest Lineage OS with TWRP).

Thanks for any hint!
[Galaxy Tab S2 Original Android Development] LuK1337:
Download latest nougat from updato.com / sammobile (if you want to spend 10h downloading it at 50KB/s) and flash it with odin or heimdall.
[Galaxy Tab S2 Original Android Development] dosludwig:
Flashing with odin works very well - and now I have got the latest LineageOS - thank you!

Unfortunately, the updater of the system does not work yet (download end with the message 'update failed' or something like that).

Well in the end installing by hand works fine. Thank you again!
[Galaxy Tab S2 Original Android Development] rumrunner4000:
Anyone having issues with the Camera not working? Seems to open but no picture visible (black screen with shutter button and camera reverse button) and shutter button will not take pic, if you try the camera crashes. Camera has stopped error message.

Does not work on last week or this weeks build on my device, i haven't noticed anything else.
[Galaxy Tab S2 Original Android Development] LuK1337:
Camera seems to work just fine here. What firmware are you on?
[Galaxy Tab S2 Original Android Development] rumrunner4000:
I found the problem, there were duplicate Camera, Calendar and Clock Apps. I disabled the oldest version of each and now everything is working fine.

Tks for the response.
[Galaxy Tab S2 Original Android Development] :
Does encryption work properly with this build?
[Galaxy Tab S2 Original Android Development] LuK1337:
Yes.
[Galaxy Tab S2 Original Android Development] Chris56:
twrp says: this device has bootloader T813XXU2APK6

I do not understand your answer.

I'm stuck with twrp complaining and therfore cannot install LOS 14.1 on my Galaxy Tab S2 (2016) (gts210vewifi).

How can I proceed?

Thanks in advance

Chris

Is the bootloader too old? Is the bootloader too recent ?

How can I replace the bootloader wth an apt one? Up to now I only have heimdall and the flashed twrp recovery.

I'm using (not neccessarily) linux.
[Galaxy Tab S2 Original Android Development] LuK1337:
Download latest nougat build from updato.com or sammobile, extract it and flash the firmware with this command.

~ heimdall flash --APNHLOS NON-HLOS.bin --MODEM modem.bin --TZ tz.mbn --SBL1 sbl1.mbn --RPM rpm.mbn --HYP hyp.mbn --ABOOT aboot.mbn ~

NOTE: On Linux you will have to build heimdall from source, although it's really easy. Just follow their instructions ~ https://raw.githubusercontent.com/Benjamin-Dobell/Heimdall/master/Linux/README