yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] xbt-:
TWRP and root worked perfectly for me in 2022, T713. Couldn't find a better 8" OLED on the market, had to get this old device. It's really really lightweight, perfect ereader. Regret that nothing better exists on the market in this size. Installing Lineage OS 17 now, even though 18 is out, the T713 isn't listed. 17 it is.

Android 10 will have a modern experience on this old but mint good ereader tablet. Using it for reading books and maybe some learning apps. Got the new Galaxy Tab A7 Lite, but I like this older Tab S2 tablet better for reading. Much better display - OLED and higher resolution. The Tab A7 lite isn't bad though, but not as good of a reading experience. Might keep them both, for different uses.
[Galaxy Tab S2 Android Development] StarbuxMcCloud:
This really is the best tablet ever made. It's so disappointing nothing like it has succeeded in over 6 years! It's still as fast as all the newer tablets and has similar PPI.
[Galaxy Tab S2 Android Development] vonDubenshire:
I'm debating trying this on my wife's old Tab S2.

SM-T713

NRD90M.T713XXS2BSG1

Think it'll be successful?
[Galaxy Tab S2 Android Development] bololabich:
It's completely useless. It does install but you can't do anything, the SD card does not get detected, data and system partitions do not mount... what's the point then?
[Galaxy Tab S2 Android Development] Georgie911701:
Hello folks!

What I done to rooting SM-T713...

After this TWRP and custom ROM (Nougat - Stock Lite v8) installed and do nothing else:

1; download Magisk-v25.1.apk from magiskmanager.com to SD-card in the device, then install it,

2; rename Magisk-v25.1.apk to Magisk-v25.1.zip then boot TWRP,

3; install Magisk-v25.1.zip then reboot.

Now for me the root working with fully functional.

G.
[Galaxy Tab S2 Android Development] martytoo:
I found your explanation to be extremely helpful. I couldn't get the recovery installed until I followed the instructions to put in the older TWRP and then like you I put in the 3.5.2-9-2- version.

I tried to use larger gapps than you used but had trouble and eventually used the the pico version. Thank you again for this suggestion.

I do have two issues one minor and one even less than minor. The somewhat annoying but minor issue is that my camera is not working. I do not use it much at all and in fact use a camera blocking app to decrease the chance that someone could spy on me if I was on a website with malware. But I do need it to install the Verizon Messages app which gives me the ability to text from my tablet with the same account I have on my phone. That app uses a QR code that is sent to the phone to verify use in the tablet. I can't verify this because the camera isn't working.

EDIT: I SEE THAT MANY USERS ON MANY DEVICES ARE COMPLANING OF CAMERA TROUBLE.

The even smaller issue is that the app called Craigslist Checker will not run on the tablet. It gives me an error that it lacks permission to run.

I thank you again and again for helping me bring a newer OS to my favorite tablet. I can now run the Amazon app once again. Amazon had recently disabled it when used with the stock Android on the T713.

I used a ROM that is 2 weeks old. (12-6-22). I did not root the tablet as of yet. My question is whether you update your ROM on a regular basis or if you are still using the build that you installed when you made this wonderful post. If I update the ROM should I do a backup before the update and just overwrite the current ROM with the latest version? I am interested in this question regardless of whether it will fix the camera.

Thank you, thank you, thank you!!
[Galaxy Tab S2 Android Development] xbt-:
This week my tablet kept rebooting to recovery. At first it would not connect to the internet, and when I tried to turn on wifi it would reboot. Eventually, it would reboot to recovery immediately. It could be I disabled too many system services, but it was time to update anyway. It also was unable to be seen in windows and connecting with USB, but I don't know if it ever could, I hadn't used it for a few months. It could also be the cable.

So today I downloaded the latest 17.1 and gapps pico (it uses ARM64 and it is version 10, FYI), and proceeded to update.

Dirty flash didn't fix it, but I wiped everything EXCEPT Data partition and I did not do the formatting of Data (because I did not want to lose data on my internal storage, I could not connect it to my computer).

It worked. Of course I have to re-setup everything, but my internal storage is not wiped (like downloads folder), which is helpful.

Only thing is that still it doesn't show up in my computer, but it could be the cable, don't know. I had to copy files over by taking out the micro sd card manually or just downloading what I needed form the internet.

Fortunately I did not have much on there yet, and what Idid have on there (my books), I had a backup for, as well as TitaniumBackup to restore app data. A prime reason to have a rooted device. Another primary reason is to have CF-Lumen in rooted mode.

Anyway, everything is back, and I can resume reading and writing on it, and for a small lightweight OLED tablet as an e-reader, I am very happy with this tablet. I just wish it had USB-C and fast charging, but maybe I will get a micro-USB to USB-C adapter so I can use my existing cables instead of my very old micro-USB cables.
[Galaxy Tab S2 Android Development] xbt-:
As feedback, the latest version of 17.1 feels much more stable than the previous version I had on there from last year.
[Galaxy Tab S2 Android Development] BillTheCat:
Howdy, folks. Sorry for the 'necro-post', but I'm trying to restore my T813 to factory spec. I downloaded the latest ROM from Frija and flashed, but I can't seem to get TWRP to work. I've used 'twrp_3.1.0-1_sm-t813_14417n' and also 'twrp_3.0.2-1_sm-t813' and I just can't boot into TWRP after 'PASS' shows and I change the keypress to VOL+ after the blank screen. Is my timing off? Do I need to release the keys when the blank screen shows? Hoping someone can help!
[Galaxy Tab S2 Android Development] almahix:
I gave up trying to restore my tab s2 after a new ROM install broke it. It is in the recycle bin.
[Galaxy Tab S2 Android Development] solnyshok:
Did you find fresh battery? Where? The new one I got is only good for about 2 hours of browsing.
[Galaxy Tab S2 Android Development] madsquabbles:
The first one worked sm-t813_no_encryptable_boot

here are the recovery logs, multiple again.

Difference this time was that I had a reboot prior to the pulsing SAMSUNG but after that got to main set up, rebooted and can still mount /data.

Gonna do the whole set up and reboot into recover in a few.

EDIT: completed set up, rebooted to recovery and it's still good. You are the man Ashyx!
[Galaxy Tab S2 Android Development] ashyx:
Great we have a winner.

I'm not sure if you will be able to enable encryption in Security settings using this boot image or if you will need to restore the stock boot image.

You could give it a try and report for testing sake?

Anyway thanks for the logs and testing stuff out. We got there in the end.

:thumbup:
[Galaxy Tab S2 Android Development] madsquabbles:
The option for encrypting the device is there in security settings. Gotta let it run overnight since it says it can take an hour or more.

First attempt was a failure. it reboots to a black screen with only the notification drawer. Second I did quick encrypt, same result but did boot after 4 min. TWRP still see /data.

Gonna do full again and let it sit at the black screen a bit longer to check if maybe I jumped the gun n rebooting it the first time.
[Galaxy Tab S2 Android Development] ashyx:
You may have to factory reset in twrp. I had a similar issue with my Tab A.

Would not encrypt until I factory reset.

Using the quick option should be fine as it only takes minutes.
[Galaxy Tab S2 Android Development] madsquabbles:
Doing a titanium back up first. The full encryption failed. I'll test the wipe, set up, then encrypt as soon as it's done.

No go on the factory reset and quick encrypt. Just goes to the black screen with the notification drawer. Reboots fine though.
[Galaxy Tab S2 Android Development] ashyx:
Strange, tbh I wouldn't have expected it to boot at all.

In any case it's just a simple matter of restoring the stock boot image if anyone decides they want encryption.
[Galaxy Tab S2 Android Development] madsquabbles:
You tried to trick me into a softbrick! LOL:laugh:

Work good enough for me as is. Thanks!
[Galaxy Tab S2 Android Development] ashyx:
I meant I expected it either would or it wouldn't boot, not half boot.
[Galaxy Tab S2 Android Development] madsquabbles:
Gotcha, just pulling your leg. If you need more tests I may be able to on Monday if I remember to bring my tablet to work. I got a stock image and titanium back up so restoring won't be a big headache.
[Galaxy Tab S2 Android Development] ashyx:
Tbh I think we're done. I'll build the boot images for the other models so people can have the choice if they want to decrypt.

Aside from that if everything else works, apart from adb and mtp which require kernel mods, then there's not much else needs to be done.
[Galaxy Tab S2 Android Development] madsquabbles:
I'll try flashing the stock boot later to see what happens... if it re-encrypts, softbricks, or does nothing.
[Galaxy Tab S2 Android Development] DeeXii:
What does this do?

Also not to get off topic but I cannot find any Tab A info.

I recall you mentioning it a bit. I got my mom a Tab A 8.0 and want to fix it up. :)
[Galaxy Tab S2 Android Development] ashyx:
Not required any more as I have posted updated images.

They disable dm-verity in the ramdisk.

Dm-verity does a hash check on the system partition. If it's modified it won't boot.

Simply even mounting the system partition with twrp can cause this.

What do you mean fix up?
[Galaxy Tab S2 Android Development] DeeXii:
Images? You mean the TWRP downloads for these models?

I see that the TWRP for the T713 has an upload date of June 1st. Where are the updated images? Slightly confused.

Regarding "fix up" I meant root, TWRP, etc. :)
[Galaxy Tab S2 Android Development] ashyx:
This is only needed if you wish to remove encryption to enable mounting DATA in TWRP.

https://www.androidfilehost.com/?fid=24591000424940488

Which model Tab A does she have ?
[Galaxy Tab S2 Android Development] DeeXii:
I have a T713 S2 btw.

Which TWRP do I download for that one.

As far as the Tab A, it is the T350.

Thanks
[Galaxy Tab S2 Android Development] debbinkm:
Thanks for all the work, ashyx. I successfully rooted my T713, but am running into the same issue with being able to un-encrypt as others I think. I thought your link above (115) was the fix, but I flashed before I noticed the file name was "sm-t813_no_encryptable_boot.tar", not t713... wouldn't boot. Any chance of building a boot file for the T713?

Possibly unrelated, but thought I'd throw it out there: after flashing the above file, then re-flashing the stock image to get the tablet booting again, the light behind the "app-switch" soft key doesn't work and the two soft key functions (app-switch and back) are completely swapped. Mildly annoying, but since I'm going to edit the build.prop file to show on-screen keys I'm not too worried about it.

Thanks again for the work, I've been following this thread since it started.
[Galaxy Tab S2 Android Development] ashyx:
Right yeh, sorry meant to get around to that.

I will do that at some point later on today. I'll be out all day today, my little boy is taking me out for Father's day.

It's unlikely the issues with the soft keys are related as the modifications don't touch anything system related.

Maybe have a look in the display settings?
[Galaxy Tab S2 Android Development] ashyx:
You can find links to cf-autoroot and twrp here for the Tab A :

http://xdaforums.com/showthread.php?t=3126827
[Galaxy Tab S2 Android Development] debbinkm:
Awesome, thank you. Enjoy your time with your boy and happy father's day.

I'll take a look at the display settings but there seems to be much fewer options in there than in past (non-marshmallow) Samsung builds.
[Galaxy Tab S2 Android Development] jpfx:
I have a T713 and followed the instructions in the first post. all went without issue except the device is stuck on pulsating 'samsung'.

no errors were displayed in twrp at all (data has been wiped and reformatted at this point). I've gone back to the stock recovery linked in the first post and as others have noted, if it's going to boot , it's taking a long time on the pulsating 'samsung'.

nevertheless have a great fathers day with your family. I'll be watching this thread for developments but if anyone has had the same experience and found a solution to get the T713 running again; please post.

thanks all

---------- Post added at 16:17 ---------- Previous post was at 16:07 ----------

ok to fix my own problem(T713 stuck on pulsating 'samsung'):

use odin the install the recovery image linked in the first post.

boot into stock recovery and wipe data/factory reset (this is important, doing this in twrp won't get it going again).

restart, T713 should boot into initial welcome screens in short order (a minute or so)
[Galaxy Tab S2 Android Development] ashyx:
Boot image must be flashed before or immediately after formatting DATA and before booting to system.

sm-t713_no_encryptable_boot
[Galaxy Tab S2 Android Development] jpfx:
thanks ashyx

I installed twrp again but fat-fingered rebooting into twrp so the tablet rebooted instead. BUT... it kept on booting and started clean!

so I rebooted into twrp and installed super-su from your original post. it rebooted twice and came up with super-su installed!

I'm not entirely sure what exactly caused this but I assume the formatted and wiped data partition (first by twrp and then by stock recovery) is not encrypted so re-installing twrp and super-su was plain sailing.

so I didn't need anything other than your original files and stock recovery.

thanks so much though :)
[Galaxy Tab S2 Android Development] ashyx:
See if you can mount data in recovery, you may find you've been re-encrypted.
[Galaxy Tab S2 Android Development] DeeXii:
Im confused...

A couple weeks ago I flashed your original TWRP and just formatted data with out flashing this no encryptable and its been fine for weeks.

What exactly does this do?
[Galaxy Tab S2 Android Development] ashyx:
It prevents the data partition from being auto encrypted at boot.
[Galaxy Tab S2 Android Development] DeeXii:
Well I understood that part. The part I am confused with is why my T713 doesnt auto encrypt at boot.

I have rebooted several times since you initially informed me to format my data / storage partitions and there has been no issues.
[Galaxy Tab S2 Android Development] ashyx:
This is just what I've understood from other users.

In that case you dont need it.

Possibly because you rooted straight after or before formatting DATA.

As far I'm aware supersu should also patch the boot.img to prevent encryption and remove dm-verity.
[Galaxy Tab S2 Android Development] jpfx:
[MENTION=4899305]ashyx[/MENTION]. just to confirm the data partition cannot be mounted in twrp. everything I hoped to achieve has been so your help has been much appreciated.
[Galaxy Tab S2 Android Development] dtsjunk:
When I root my tab s2 the t819 and I do the final step sm-t813_no_encryptable_boot in odin everything boots up fine but I don't get wifi or data ...... if I root and follow all the steps except sm-t813_no_encryptable_boot in doing it works just fine is thereally a file for my 819 or this should work? Am I missing something? Thanks in advance
[Galaxy Tab S2 Android Development] ashyx:
Sorry, I haven't built a suitable boot image for the T819 yet.

If you send me your boot.img from the stock firmware I will sort it.
[Galaxy Tab S2 Android Development] DionWhite33:
What version did you flash?
[Galaxy Tab S2 Android Development] madsquabbles:
[MENTION=2996598]DeeXii[/MENTION]

Have you checked in twrp for /data as mountable or see if "encrypt this device" is available in security settings?

Re encrypting didnt affect much of anything and the device performed as normal. Without encryption you can recover you data via twrp if needed.

Mine would reencrpt after flashing twrp, formatting, flash su then reboot. The pulsing Samsung logo shows then freezes and reboots and upon going directly to twrp on the reboot it's encrypted itself. This is on a T813.

Still haven't gotten to flash stock boot to see what happens. Hoping it encrypts without losing data.
[Galaxy Tab S2 Android Development] dtsjunk:
I took this from the firmware i backed up before, (T819XXU1APD8_T819PHN1APD2_T819XXU1APD5_HOME.tar.md5) had to split in 3 archives because XDA only allowe 8mb files.

is this okay? or do i really need to dump the boot.img from my t819?

Thanks in advanced
[Galaxy Tab S2 Android Development] DeeXii:
I bought another T713 and gave the first one to my daughter.

I will see the process when I do it again.
[Galaxy Tab S2 Android Development] ashyx:
Should be fine as long as the archives unpack correctly.
[Galaxy Tab S2 Android Development] ashyx:
Just wanna say thanks to Jean-Paul, Matthew and madsquabbles for their donation support.

Cheers.
[Galaxy Tab S2 Android Development] dtsjunk:
Looking forward for the working root :D

Thanks for the efford.

:cowboy:
[Galaxy Tab S2 Android Development] ashyx:
You can still root without the boot.img, but you won't be able to mount data in twrp.
[Galaxy Tab S2 Android Development] dtsjunk:
I know but I think it's more handy if I can also mount the data because I can't see the stuff in the internal sdcard .. rooting went fine

Did that also on my s7
[Galaxy Tab S2 Android Development] Lightn1ng:
Is there a reason there is absolutely no rom development for the T713 and T813? Is it because nobody has them? Because I'm thinking about buying one and making Supernova for it (ashyx knows). Anything holding me back?
[Galaxy Tab S2 Android Development] dtsjunk:
any luck on the boot.img?:victory: :fingers-crossed:
[Galaxy Tab S2 Android Development] DeeXii:
The T713 and T813 just came out not too long ago. So yes I would say that would be part of it.

However with that said I would get this ASAP. The performance and batt life is way better for me on my T713 then my T710.

Do it! :)
[Galaxy Tab S2 Android Development] djgade:
That would be awesome!
[Galaxy Tab S2 Android Development] ashyx:
Will look at this later, didn't get chance last night.
[Galaxy Tab S2 Android Development] ashyx:
Here you go: sm-t819_no_encryptable_boot

.
[Galaxy Tab S2 Android Development] ashyx:
If anyone has the T719 boot image, could they post it here?

.
[Galaxy Tab S2 Android Development] Lightn1ng:
YouFirmware has it I believe
[Galaxy Tab S2 Android Development] ashyx:
I actually only want the boot.img not the whole firmware.
[Galaxy Tab S2 Android Development] Lightn1ng:
Oh :sigh:
[Galaxy Tab S2 Android Development] DionWhite33:
I flashed this and got Root. Then put Xposed. For 2 days things were great then all of a sudden tonight Google Play Services Updated and the PlayStore wont open. I tried everything to fix the issue. Also none of the apps linked to the store like app keys etc would work anymore duemto playstore not only not coming on but its lkke its not working. I get a message that Play Services is updating but lasts forever and never does. I put my TWRP backup on and was fine for an hour. Then poof? It happned again. Half of my stuff is useless without the PlayStore. I also noticed in Link2Sd...that on Google Playstore it says on that app that services and playstore are UPDATED....does anyone know why this is happening? And is it just me?

---------- Post added at 04:11 AM ---------- Previous post was at 04:10 AM ----------

Sorry for the typos in advance
[Galaxy Tab S2 Android Development] djgade:
Also a custom kernel with improved performance would be so great!

---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------

Playstore and Play Services are fine here on T813. Rooted and xposed 85.0
[Galaxy Tab S2 Android Development] madsquabbles:
Kinda had something like this on my nexus 9 (joker loved locking up!). It had locked up on an app update on the google services and had constant crashing after a forced reboot. I had to time my taps right just to be able to clear data and force stop google play svc. Nothing worked but a factory restore for me.
[Galaxy Tab S2 Android Development] Lightn1ng:
I'll see what I can do, but I'm going away soon so it will have to wait
[Galaxy Tab S2 Android Development] DionWhite33:


---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------

Mine works fine for the last two days and then just all of a sudden it happened. I had a backup of when I first rooted it and I just redid my backup reflashed exposed and it's working fine now I have no idea what happened. It apparently got stuck on updating Google Play services. Which then in turn made all my Google Apps not work. Anyways I got it working fine now I didn't know if anybody's ever run across an issue like this just figured I'd ask.
[Galaxy Tab S2 Android Development] djgade:
Yeah thank you for reporting this. On which Build are you?
[Galaxy Tab S2 Android Development] debbinkm:
ashyx - Still having an issue with the soft keys. There are no applicable display settings and even when the tablet boots, only the right soft key is back-lit, so I think it may be deeper than system related. I was able to swap them back (BACK and APP_SWITCH) by switching the key mapping in the .prop file, but the back light still does not work. If it was just the back-light on the app-switch key that wasn't working, I would think hardware failure, but since the key functions swapped AND the backlight stopped working, it makes me think software. I'm not an expert, though. Just wanted to see if you (or anybody else on this thread!) had any other ideas for me to check. Other than that, root and un-encrypted is still working great on the SM-T713.

On another note, adding "qemu.hw.mainkeys=0" to the build.prop file seems to not do anything in Android M :(
[Galaxy Tab S2 Android Development] dtsjunk:
Thanks a million :victory:

Will test it out later, bought you a few beers 2 days ago :D
[Galaxy Tab S2 Android Development] ashyx:
Many thanks for the support. :beer: :thumbup:
[Galaxy Tab S2 Android Development] Lightn1ng:
Alright, I'm going to sleep, somebody wake me up when the T713 kernel source is released (it'll be a long nap!)
[Galaxy Tab S2 Android Development] Dan_FFM:
can we build a cm kernel?

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t819
[Galaxy Tab S2 Android Development] Lightn1ng:
[MENTION=4899305]ashyx[/MENTION]

What are the /dev/block paths for the system and boot partitions on the T713? (aka, how do I mount them in an updater-script)?
[Galaxy Tab S2 Android Development] ashyx:
I take it youve got this now?
[Galaxy Tab S2 Android Development] Lightn1ng:
Yes :D

mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");

and

package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");

I haven't tested it because I don't have a T713 (YET... :)) but I don't see why it wouldn't work
[Galaxy Tab S2 Android Development] Lightn1ng:
TO ANYONE WITH A T713:

I've created a (very alpha) ROM over the past few hours for the T713. I don't have a T713. Could anyone with a T713 please PM me to test it? Thanks very much.
[Galaxy Tab S2 Android Development] ashyx:
I take it the boot.img will be a choice install via aroma?
[Galaxy Tab S2 Android Development] Lightn1ng:
There will be aroma but no boot.img choice. I just included your no-forceencrypt boot.img into it. Why would I want the boot.img as a choice?

It's right here if you want to see:

https://github.com/Nandr0idC0nsumer/LionROM

(I might rename it to something different, LionROM seems a bit feminine to me)
[Galaxy Tab S2 Android Development] ashyx:
Just not really a fan of forced boot.img installs.

Imo should be a choice.

Edit : rom looks like a good start.
[Galaxy Tab S2 Android Development] Lightn1ng:
Ok will do xD

This would mark my first ever aroma rom so hopefully this doesn't end as a disaster...