[TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17

Search This thread

Uliaoth

Member
Jul 9, 2020
12
2
Hello,

I'm getting an error in TWRP while flashing the Boot image patch on my smt-813

It says "Error : Unable to find boot block location!
Aborting
Failed to patch boot image.

I flashed TWRP (the last version from twrp.me "twrp-3.4.0-0-gts210vewifi" ) with odin. I've done everything like in the OP. What should i do in order to flash the patch boot image ?
 
Last edited:
Bumping up the post

So I did not format the Data prior to root.

Now when in the format data I am unable to type YES as i cant see the keyboard, i connected a wired mouse but still no response.

Any ideas how to proceed further

Thanks for the help

EDIT: Reflashed TWRP now able to type YES
 
Last edited:

xbt-

Senior Member
Aug 8, 2013
159
57
Moscow
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.
 

xbt-

Senior Member
Aug 8, 2013
159
57
Moscow
FYI I tried to upgrade to the latest TWRP (twrp-3.6.0_9-0-gts28wifi.img.tar) on my T713, but it failed. I used latest Odin (Odin3 v3.14.1_3B_PatcheD).

However, I reflashed the original TWRP from this thread (twrp_3.1.0-1_sm-t713_14417n.tar) and it worked again.

I also then tried downloading the img file (twrp-3.6.0_9-0-gts28wifi.img) and flashed inside TWRP (to Recovery). Still no luck, still went to download mode after failing recovery.

Next I tried the next one, except that @ripee modded it to fix a bug on hw
Post with download links here

The one I used was twrp-3.5.2_9-2-gts28vewifi and I flashed it in Odin. It worked! Now I'm on the latest version of TWRP that's working as of today.

So if you want the latest TWRP, use that one.

p.s. now apparently my CPU is not over 30,000 degrees C (55,000 deg F)! lol. It was obviously a bug with the previous version that excluded the decimal point, since now it's 30 deg C.


Next I installed Lineage OS 17.1
and also Open gApps Pico (this version is just the Play store and Play Services)

Attempts to install Supersu directly after Lineage OS failed, I will have to reboot first I suppose. It's booting! I'll be able to see then if it's still rooted after the whole format and wipe of the whole system to install LineageOS. I have a feeling I'll have to root again separately after it boots.

Update: Had to install magisk.apk and then rename magisk.apk to magisk.zip, then reboot into twrp and flash the zip. It worked!


Instructions from my other post:

Flashed Lineage OS 17.1 and open gapps pico on my T713, clean install, and it took over 30 minutes at the curved line logo with the circle moving right to left (loading screen at boot).

Then found another thread that said it should take only like 15 mins (edit: after my own experience, it takes only like 5 mins or so - if it gets stuck by 10 mins, then force reboot and wait a min and it will go to welcome page).

Since this is an OLED screen, I'm worried about screen burn in, so I don't want to leave it with that bright blue line fixed in the middle overnight. Going to try a couple things. I shut off and back in recovery now.

This time I did this:

  1. Wipe all like in wipe instructions
  2. Reboot back to recovery
  3. Mount System too so the following are mounted (for me System was not mounted, not sure if it matters)
    - System, Data, Cache, MicroSD
  4. Install LineageOS only (will install gApps later, this is to isolate is lineage is the problem)
  5. Click the Wipe Cache/Dalvik
  6. Reboot
After about 5-10 mins I decided to search the thread. Someone said they just forced reboot (hold power and voldown in my case until it reboots),

  • It worked! After a minute or two when it reboot, it just went straight into the welcome page (white screen with blue LineageOS logo). Success!

  • Now I turned it off (hold power and press power off) without setting up and installed gapps, and wiped Cache/Dalvik and reboot, and after another minute back into welcome screen - this time the gapps welcome screen!

  • Pressing the yellow Start button lagged a little. But after a few seconds (I clicked a few times) it went to the next screen!

  • Then after skipping wifi setup, it asked forone of three options with fingerprint+pin, etc, well just pick one, on the next screen there will be a skip option if you don't want to set it up.

First courses of action:
  • Enable dark theme! It's under Display. Search didn't work for some reason.
  • Disable Play Protect (I don't want it)
  • Security > Find My Device > Off
  • Turn off Bluetooth
  • About > tab on Build Number a few times at the bottom to enable Developer
  • System > Advanced > Developer Options > Automatic System Updates > Off
  • System > Advanced > Developer Options > Advanced Restart > On
  • System > Advanced > Developer Options > Override Force Dark (always on)
  • System > Buttons > Backlight > Disabled
Next
  • Root
  • Add Xposed (LSPosed)
  • Add LSPosed modules
Flashing SuperSu like the root guide says, doesn't work. Instead, install Magisk. Then reboot.

Had some trouble. Then I came across this:

Installing Magisk is extremely easy on this ROM:
  1. Download the Magisk app from github (link updated to github)
  2. Install the APK file
  3. Rename magisk.apk to magisk.zip
  4. Install magisk.zip from TWRP.
It worked! I'm rooted! That was not intuitive, but easy!
 
Last edited:
Apr 8, 2011
20
1
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.
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.
 

vonDubenshire

Senior Member
Feb 10, 2018
496
104
USA
Samsung Galaxy Tab S2
LG Nexus 5X
I'm debating trying this on my wife's old Tab S2.

SM-T713

NRD90M.T713XXS2BSG1

Think it'll be successful?
 

Attachments

  • PXL_20220510_172314683.MP.jpg
    PXL_20220510_172314683.MP.jpg
    5.5 MB · Views: 81

bololabich

Member
Jan 26, 2012
26
5
Bydgoszcz
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?
 

Georgie911701

New member
May 24, 2015
2
0
46
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.
 

martytoo

Senior Member
Oct 12, 2010
235
49
FYI I tried to upgrade to the latest TWRP (twrp-3.6.0_9-0-gts28wifi.img.tar) on my T713, but it failed. I used latest Odin (Odin3 v3.14.1_3B_PatcheD).

However, I reflashed the original TWRP from this thread (twrp_3.1.0-1_sm-t713_14417n.tar) and it worked again.

I also then tried downloading the img file (twrp-3.6.0_9-0-gts28wifi.img) and flashed inside TWRP (to Recovery). Still no luck, still went to download mode after failing recovery.

Next I tried the next one, except that @ripee modded it to fix a bug on hw
Post with download links here

The one I used was twrp-3.5.2_9-2-gts28vewifi and I flashed it in Odin. It worked! Now I'm on the latest version of TWRP that's working as of today.

So if you want the latest TWRP, use that one.

p.s. now apparently my CPU is not over 30,000 degrees C (55,000 deg F)! lol. It was obviously a bug with the previous version that excluded the decimal point, since now it's 30 deg C.


Next I installed Lineage OS 17.1
and also Open gApps Pico (this version is just the Play store and Play Services)

Attempts to install Supersu directly after Lineage OS failed, I will have to reboot first I suppose. It's booting! I'll be able to see then if it's still rooted after the whole format and wipe of the whole system to install LineageOS. I have a feeling I'll have to root again separately after it boots.

Update: Had to install magisk.apk and then rename magisk.apk to magisk.zip, then reboot into twrp and flash the zip. It worked!


Instructions from my other post:

Flashed Lineage OS 17.1 and open gapps pico on my T713, clean install, and it took over 30 minutes at the curved line logo with the circle moving right to left (loading screen at boot).

Then found another thread that said it should take only like 15 mins (edit: after my own experience, it takes only like 5 mins or so - if it gets stuck by 10 mins, then force reboot and wait a min and it will go to welcome page).

Since this is an OLED screen, I'm worried about screen burn in, so I don't want to leave it with that bright blue line fixed in the middle overnight. Going to try a couple things. I shut off and back in recovery now.

This time I did this:

  1. Wipe all like in wipe instructions
  2. Reboot back to recovery
  3. Mount System too so the following are mounted (for me System was not mounted, not sure if it matters)
    - System, Data, Cache, MicroSD
  4. Install LineageOS only (will install gApps later, this is to isolate is lineage is the problem)
  5. Click the Wipe Cache/Dalvik
  6. Reboot
After about 5-10 mins I decided to search the thread. Someone said they just forced reboot (hold power and voldown in my case until it reboots),

  • It worked! After a minute or two when it reboot, it just went straight into the welcome page (white screen with blue LineageOS logo). Success!

  • Now I turned it off (hold power and press power off) without setting up and installed gapps, and wiped Cache/Dalvik and reboot, and after another minute back into welcome screen - this time the gapps welcome screen!

  • Pressing the yellow Start button lagged a little. But after a few seconds (I clicked a few times) it went to the next screen!

  • Then after skipping wifi setup, it asked forone of three options with fingerprint+pin, etc, well just pick one, on the next screen there will be a skip option if you don't want to set it up.

First courses of action:
  • Enable dark theme! It's under Display. Search didn't work for some reason.
  • Disable Play Protect (I don't want it)
  • Security > Find My Device > Off
  • Turn off Bluetooth
  • About > tab on Build Number a few times at the bottom to enable Developer
  • System > Advanced > Developer Options > Automatic System Updates > Off
  • System > Advanced > Developer Options > Advanced Restart > On
  • System > Advanced > Developer Options > Override Force Dark (always on)
  • System > Buttons > Backlight > Disabled
Next
  • Root
  • Add Xposed (LSPosed)
  • Add LSPosed modules
Flashing SuperSu like the root guide says, doesn't work. Instead, install Magisk. Then reboot.

Had some trouble. Then I came across this:

Installing Magisk is extremely easy on this ROM:
  1. Download the Magisk app from github (link updated to github)
  2. Install the APK file
  3. Rename magisk.apk to magisk.zip
  4. Install magisk.zip from TWRP.
It worked! I'm rooted! That was not intuitive, but easy!
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!!
 
Last edited:

xbt-

Senior Member
Aug 8, 2013
159
57
Moscow
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.
 

xbt-

Senior Member
Aug 8, 2013
159
57
Moscow
As feedback, the latest version of 17.1 feels much more stable than the previous version I had on there from last year.
 

BillTheCat

Senior Member
Jun 17, 2008
1,873
673
Milford, PA
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!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 89
    Unofficial release -TWRP recovery for the Galaxy Tab S2 - SM-T713/719/813/819, Qualcomm MSM8976

    teamwin-recovery-project-twrp-logo.jpg


    TWRP 3.1.0-0 Released
    Mar 10, 2017

    TWRP 3.1.0-0 is out now for all currently supported devices.

    What's new in 3.1.0-0:


    vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
    adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
    tweak MTP startup routines (mdmower)
    support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
    support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
    better indicate to users that internal storage is not backed up (Dees_Troy)
    improve automatic determination of TW_THEME (mdmower)
    minimal getcap and setcap support (_that)
    try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
    shut off backlight with power key (mdmower)
    timeout during FDE decrypt (Dees_Troy and nkk71)
    support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
    boot slot support (Dees_Troy)
    TWRP app install prompt during reboot (Dees_Troy)
    support for AB OTA zips (Dees_Troy)
    support new Android 7.x log command (Dees_Troy)
    update recovery sources to AOSP 7.1 (Dees_Troy)
    numerous bugfixes and improvements by too many people to mention

    Official TWRP App
    Mar 11, 2017

    Official TWRP App
    The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
    Download Links:
    We recommend downloading the app from the Play Store.

    If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
    How do I use the app?
    When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).

    Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.

    If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.



    Update 1/4/2017
    TWRP 3.1.0-1 MM/NN build released.

    Current status: BETA

    Features:

    MTP working
    ADB working
    SEANDROID warning fix
    TWRP and Kernel built from source
    System image backup
    F2FS support >> To be added
    Twrp app support

    Bugs:
    Reboot to recovery loop when using reboot utilities. Use hardkeys combo only to boot to recovery POWER + HOME + VOL UP
    If you get stuck in a recovery loop reflash TWRP with auto-reboot enabled.




    You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.


    Instructions:


    Flash with ODIN 3.10.7 in the AP slot.
    Put your device in DOWNLOAD mode.
    Uncheck Auto reboot.
    Load the respective file below into the AP slot and hit start.
    After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
    As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
    You should now see TWRP recovery.


    NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
    Settings -> Developer Options -> OEM unlocking
    AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.


    DOWNLOAD:

    TWRP 3.1.0-1 - Nougat
    twrp_3.1.0-1_sm-t713_14417n
    twrp_3.1.0-1_sm-t719_13417n
    twrp_3.1.0-1_sm-t813_14417n
    twrp_3.1.0-1_sm-t819_14417n

    TWRP 3.1.0-1 - Lollipop/Marshmallow
    twrp_3.1.0-1_sm-t713_1417
    twrp_3.1.0-1_sm-t719_1417
    twrp_3.1.0-1_sm-t813_1417
    twrp_3.1.0-1_sm-t819_1417

    TWRP 3.0.2-1

    SM-T713/719
    twrp_3.0.2-1_sm-t713

    SM-T813
    twrp_3.0.2-1_sm-t813

    SM-T819
    twrp_3.0.2-1_sm-t819_31816



    To Root:
    Flash the latest SuperSU release with TWRP:
    https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/

    To disable forced encryption and mount internal storage:
    (Note this MUST be flashed after SuperSU if you intend to root)

    1. Boot to Twrp
    2. Format Data partition using FORMAT DATA button under Wipe options.
    (Note: This will wipe the internal storage)
    3. Check DATA is mountable.
    4. Install SuperSU (if root is required)
    5. Install boot image patch below.
    6. Reboot

    Boot image patch
    no-verity-no-encrypt_ashyx




    DEVICE TREE: soon


    PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST


    Screenshot_2016_03_05_08_13_44_1.png


    DnoCrqh.png


    VAm49c4.png


    ytBFf13.png


    ONLSkMi.png



    Credits: Me, my testers, Teamwin
    Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.

    FEEDBACK IS APPRECIATED PLEASE.
    THANKS.


    DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU



    .
    4
    Thanks for the correction and your patience, must be looking at things in a daze[emoji14]I have an edited version:

    For Galaxy Tab S2 9.7 SM-T813

    1Settings -> Developer Options -> OEM unlocking ENABLE OEM UNLOCK
    2Put in download mode: turn on by pressing and holding Volume DOWN + Home + Power Key
    3Run Odin, connect USB to PC and Tab. ID-Com Box turns blue.
    4Click "AP" Button in Odin, Select "twrp_3.0.2-1_sm-t813.tar" on PC.
    5Unselect all "Options" except "F. Reset Time".
    6Press Start in Odin.
    7Wait for ID-COM Box to turn Green; Uncheck Auto-reboot. turn OFF your Tab.
    8Boot into TWRP Recovery mode: turn it on by pressing and holding Volume UP + Home + Power Key.
    9In TWRP: "Wipe > Format Data" to remove encryption, destroys all user data!
    10 Shut Down Tab.
    11Copy no-verity-no-encrypt_ashyx.zip to SD card in Tab.
    12Boot into TWRP Recovery mode: turn it on by pressing and holding Volume UP + Home + Power Key.
    13Flash no-verity-no-encrypt_ashyx.zip (NOT Image file as in Techbeasts Guide!)
    14To Root: Flash "SuperSU.zip" with TWRP as in 11-12.
    #10
    There's no real reason to shutdown, it can all be done in one fell swoop.
    If you do want to reboot then it's sufficient to just use the reboot to recovery option in twrp.

    Everything else is good.
    4
    UPDATE 14/4/2017: Fixed Nougat builds added to the OP.
    4
    Update: TWRP 3.1.0.-1 released.
    4
    Hello ashyx...
    I do exactly your séquence :
    - Unlock OEM
    - Install twrp_3.1.0-1_sm-t813_14417 Nougat Mode .
    - Format Data ... (with a lot of red warning (prob with Data )
    - Install SR3-SuperSU-v2.79-SR3-20170114223742 (no warning)
    - Install no-verity-no-encrypt_ashyx (no warning)
    - Reboot immédiately with Power On + Vol Down + Home...

    On screen "Galaxy Tab S2" / Powered by samsung 10 sec after logo samsung blinking 10 mins and after Boot OK ... Root work correclty ....

    *** Root work on Galaxy Tab S 2 VE Nougat (T813XXU2BQD1 DBT)

    Great Thanks ashyx for you help ...

    Bye ...