Install TWRP Recovery and Root Galaxy Tab S4 (SM-T830/T835)

How to Install TWRP Recovery and Root Galaxy Tab S4

In this tutorial, I will show you how to install TWRP recovery and root Galaxy Tab S4 running Android 10, Pie or Oreo, easily. This guide supports both the SM-T830 (WiFi) and SM-T835 (LTE) variants.

Advertisement

In 2018, we barely saw any Android-based tablets being released, except Samsung’s own Galaxy Tab S4. The 10.5-inches tablet aims at achieving a near-desktop experience with a magnetic keyboard, an S-Pen, and improved multi-tasking through Samsung DeX. The Tab S4 is powered by the Qualcomm Snapdragon 835 SoC and comes with Android 8.1 Oreo out-of-the-box.

Despite all the powerful hardware and software with extended features, users might often want to root Samsung Galaxy Tab S4. Well, one might simply want to use root-enabled apps or install mods for additional features. Whatever the reason might be, you can now easily install TWRP recovery and root Galaxy Tab S4 using Magisk 20.0.

Thanks to XDA Recognized Contributor mentalmuso, we now have official TWRP recovery for the Galaxy Tab S4. According to the developer, the latest TWRP 3.4 recovery provided by him is completely stable for usage and supports everything including OTG and MTP. And as mentioned earlier, both the WiFi (SM-T830) and LTE (SM-T835) variants of the Tab S4 are supported.

Our appreciations also go to XDA member ianmacd who helped the developers with continuous testing that resulted in a working TWRP, as well as root.

Now, before you follow the instructions, take a look at the information provided right below.

Important Thing to Note

  • Flashing TWRP and rooting your tablet will trip the KNOX counter and thus, will break the official warranty. This cannot be undone.
Table of Contents

Prerequisites

  • Although installing TWRP recovery will not wipe anything off your tablet, but rooting it will require a complete wipe of all the data. So, make sure that you take a complete backup of all the data beforehand. You can also follow our detailed tutorial on how to backup Android devices completely.
  • Install latest Samsung USB drivers on the PC.
  • Download Odin 3.13.1 on the PC and extract the zip to an easily accessible location.
  • It is strongly advised to use a USB 2.0 port of your PC for the flashing process.
  • Enable ‘OEM unlock’ option in Settings -> Developer options. If the OEM unlock toggle is missing, then you can also try fixing it using our tutorial.

Make sure to fulfill all the requirements stated above before you head over to the instructions to install TWRP recovery and root Galaxy Tab S4.

Downloads

Download all the files to the PC before you follow the instructions. The files provided below are the latest as of 29 October 2019 and support both Android Pie and Oreo firmware. Please visit the original XDA threads (1 & 2) and make sure that you download and use the latest ones for the procedure.

Advertisement

TWRP Recovery Image

WETA Kernel

Note: Flashing the WETA kernel is mandatory on Android Pie, but not required for Android 10.

Forced-encryption Disabler

Latest Magisk flashable ZIP

Install TWRP Recovery on Galaxy Tab S4

The first step in order to root Galaxy Tab S4 is to install TWRP recovery on it. Further, to ensure that DM-Verity is not triggered and your Tab S4 doesn’t enter a bootloop it is crucial to boot your tablet directly into TWRP recovery mode after the flashing process finishes. The process may sound a bit confusing, but it’s quite easy instead. Simply follow the steps laid below to install TWRP recovery on Galaxy Tab S4.

  1. Boot your Galaxy Tab S4 into Download Mode.
  2. To do so, power off the tablet first. Then hold the Volume Down and Power buttons until the tab vibrates. Then quickly release the Volume Down button and hold the Volume Up + Power button. Your tablet should now enter the stock recovery mode. To boot into Download Mode, select ‘Reboot to bootloader’.
  3. Connect the tablet to the PC using the USB cable.
  4. Launch Odin tool by double-clicking on the ‘Odin3 3.13.1.exe’ file.
  5. The ID:COM port on the Odin window should light up blue.
    Install TWRP Recovery on Galaxy Tab S4 - Odin ID COM Port
  6. In the Odin tool window, uncheck ‘Auto Reboot‘ in the Options menu.
  7. Click on the ‘AP‘ button and select the TWRP recovery image file (e.g. TWRP_T830_3.3.1-4.tar).
  8. Finally, click on the ‘Start’ button to flash the file and install TWRP recovery on Galaxy Tab S4.

Now here goes the important bit: After the flashing is complete, it is necessary to boot into TWRP mode directly. Hold the Volume Down and Power buttons until the phone powers off. As soon as it powers off, hold the Volume Up and Power buttons to enter TWRP recovery mode on your Galaxy Tab S4.

Install TWRP Recovery on Galaxy Tab S4 - Screenshot
Image courtesy: [email protected]

How to Root Galaxy Tab S4

  1. Select ‘Keep Read Only’ when TWRP prompts to keep the system read-only.
    Root Galaxy Tab S4 - Keep System Ready Only message in TWRP
    Image courtesy: [email protected]
  2. Go to ‘Wipe’ -> ‘Format Data’ in TWRP and enter ‘yes’ in the provided field. This will wipe the tablet completely, including internal storage. It is important to perform this step in order to disable encryption completely and have access to the storage in TWRP recovery.
  3. Once formatted, reboot your Tab S4 into TWRP recovery mode. To do so, go to the “Reboot” menu in TWRP and tap on “Recovery”.
  4. Connect the tablet to the PC and turn on the “Enable MTP” button in the TWRP’s “Mount” menu.
  5. Transfer the WETA kernel, Forced-encryption Disabler, Magisk Flashable ZIP files to the tablet’s internal storage or microSD card.
  6. Once the files have been transferred go back to the TWRP main screen and tap on the ‘Install’ button.
  7. Select the WETA kernel ZIP file (Optional for Android 10) and press the ‘Add more Zips’ button. Then select the ‘TabS4_oreo_forced_encryption_disabler.zip‘ file (Android Oreo) or ‘Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip‘ file (Android 10 & Pie).
  8. Then tap on ‘Add more Zips’ again and select the ‘Magisk-v21.2.zip‘ file.
  9. Once the files have been added to TWRP’s flashing queue, swipe the button on the bottom of the screen to flash the files and root Samsung Galaxy Tab S4.

After the flashing process finishes, you can boot your tablet back into the OS by pressing ‘Reboot System’. The first boot might take some time.

Your Galaxy Tab S4 should now be rooted with Magisk and you should see the Magisk Manager application among the installed apps in the app drawer. To verify if your tablet has been successfully rooted, launch the Magisk Manager app and check its status

Now that you have successfully rooted your tablet, you can install root-enabled apps, or install Magisk modules to add more features to the software. You can also install an audio mod and the infamous Xposed Framework.

So, this was our tutorial on how to root Galaxy Tab S4 and install TWRP recovery on it. We hope that it proved useful to you and was easy to follow. If you have any questions, please leave a comment below. We will try to help you to the best of our knowledge.

Comments

  1. Hi! The Weta kernel is nowhere to be seen. Where can I get it? Thanks for your help

    1. Hi. I too verified this and suppose the developer removed the WETA kernel from the download folder.

      If you’re running Android 10, you will not need WETA at all.

  2. Hey, I rooted my Tab S4 with the Weta Kernal with aNdroid 9. Everything is ok, but Bluetooth is bugged. My bluetooth randomly finds devices, most of the time it wont find any. And it also does not remember the devices after some few hours. E.g. I paired my headset and my sound speakers yesterday, even renamed them individually. Today, they werent in the list of known devices. I dont know if this is something that only occurs on a rooted device, since googling for a solution didnt help, because no one seems to have this issue.

    So I decided I ll upgrade to Android 10 to solve my problem, well it was solved I guess, but in android 10, I couldnt create a screen lock patterm pin or password, because the system will alsways promt me to secure the pattern via Findymymobile. There was no option to allow me to disagree, only accept, and because I dont have a Findmymobile account, it wouldt save the patterm pin or password.

    So now I am back on Android 9 root and stuck with the bluetooth issue. Any help or anyone who has found a work around?

    Thanks

    1. Hi, that’s a known issue with rooted Samsung Galaxy devices. To fix this issue (once you have rooted the tablet), go to Magisk Manager > Modules and install the ‘Bluetooth Library Patcher’ module by ‘3arthur6’. After the installation, reboot your Tab S4 and check if the Bluetooth issue is fixed or not.

  3. Hi, thank you very much. it works
    i flashed TWRP first and,
    and inside twrp i flashed

    1- Weta kernel.
    2- Disable_Dm-Verity_ForceEncrypt_03.04.2020( Android pie )
    3- Magisk-v20.3
    4- RMM_Bypass_v3_corsicanu

    1. Hi. I am glad it did work out for you! Thanks a lot for taking the time and confirming it.

    2. omg please someone helpi have no knowledge of any of this i just want my tablet back :C i am stuck on set warranty bit kernel and i have the twrp thing omgi thinkmy tablet is broken help

    3. Hello. This error is caused due to tripped DM-verity. After flashing TWRP, it’s extremely important to boot straight into it.

      For restoring, simply download the latest Odin firmware for your Tab S4 using the Frija tool. And then flash the firmware to your tablet using the Odin Flash Tool. For instructions, you can refer to this page.

    4. It’s basically installing the firmware that came pre-installed from Samsung (the firmware files are pulled from their servers). We generally use the “flashing” term because it indicates writing to the flash memory of the phone (where the OS resides).

      I suggest you go through the guide I linked for more explanation.

    5. Anyways, i did the whole thing again that I have more experience, and now its rooted. ;0 thanks for your help

    6. Turns out i didnt root my tabs4 and now im stuck on set warranty bit recovery please help i cant access downloads
      no ignore pls

    7. Have you tried holding the Power key for 10-15 seconds to forcefully power off the tablet? Once it turns off, you can use the buttons combination to get back into Download Mode and flash the stock firmware to recover the tablet.

  4. Hi Dhana,

    Thanks for your tutorial. But I got problem with samsung galaxy tab s4. After instal TWRP I cannot enter TWRP Recovery mode.

    “Now here goes the important bit: After the flashing is complete, it is necessary to boot into TWRP mode directly. Hold the Volume Down and Power buttons until the phone powers off. As soon as it powers off, hold the Volume Up and Power buttons to enter TWRP recovery mode on your Galaxy Tab S4.”

    My tab doesn’t have any response and cannot enter to download mode. its write ” set warranty bit : recovery” with the yellow colour in the top right corner. and I cannot do anything about it. do you have any idea, what happen to my tabs.

    Thank you

    1. Hi Andrew. After you flashed TWRP, were you able to boot it into TWRP mode? You can ignore that screen until the complete TWRP and rooting process is finished.

      Did you also uncheck the “auto reboot” option in Odin before flashing TWRP?

  5. Will this work on the tab s4 AT&T variant, sm-t837a? Or is there a way to flash that model with generic firmware, and then do it? There’s no OEM unlock option in developer options. Any advice?

    Thanks,

    Brian

    1. Hi Brian. I am afraid that it won’t work on the SM-T837 because the variant comes with a non-unlockable bootloader. That’s why the ‘OEM unlock’ toggle is missing in your tablet’s settings.

      With an unlocked bootloader, it is not possible to install TWRP or root.

  6. Hello Dhananjay, and thank you for this guide.

    I followed all the steps on my Tab S4 running Android 9, but at the end when I try to reboot into system, all I get is the initial screen with “Set Warranty Bit : Kernel” in yellow at the top left, and an open padlock symbol with the word “Custom” below it. This screen remains for about 15 seconds, then goes black briefly, and then returns. This continues until I shut down the tablet.

    Any help you could give would be greatly appreciated.

    Arthur

    1. Hi Arthur, exactly at what point did this happen?

      Also, what software build version was your Tab S4 running before you started performing the instruction? If you can’t remember it, just let me know which month’s update it was running.

    2. It happened at the very end after I had done all the flashing and was ready to boot into system. As far as I remember, TWRP showed an error message at some point, possibly when flashing Disable_Dm-Verity…, but I’m not 100% sure.

      I was on T835XXU4BSJ6, Kernel version 4.4.153-17096871, date 31 October 2019. I have since re-flashed this ROM with Odin and the tablet is working fine again, but I would still like to be able to root it. I have rooted all the Samsung devices I have ever had, and this is the first one I have had any problem with.

    3. Hi Arthur. I think I know what was missing. A custom kernel is required to patch some of Samsung’s security features stored in the kernel.

      Do one thing, repeat the whole procedure. This time, along with flashing the Encryption Disabler and Magisk files, also flash the WETA kernel (Download here).

      Flash it in the following order: WETA kernel > Encryption Disabler > Magisk

      As for the error you mentioned, it would have stated ‘Could not mount /odm’ or somthing similar. That’s perfectly normal, you can ignore it.

    4. Success! I followed your instructions to flash WETA kernel, then the Encryption Disabler, then Magisk, and rebooted into System. After an anxious wait of about 8 minutes, I was delighted to see the Let’s Go welcome screen, and even more delighted to see Magisk in my apps drawer!

      Many thanks, Dhananjay, for your help and your easy-to-follow, clear instructions. I greatly appreciate it!

    5. Hi Dhananjay,
      Thank you for the Guidance.
      I have successfully installed all the things. but in Magisk manager it always says checking for updates and even in modules it is empty. can you please help me out?

    6. Hi again, Arthur. That’s great! And thank you so much for the kind words. I hope to see you around the blog more often.

      I will update the post with WETA kernel and related instructions.

    7. Hi Dhananjay,
      After performing magisk.zip and RMM flashing and rebooting into the system, This is the initial screen with “Set Warranty Bit : Kernel” in yellow at the top left, and an open padlock symbol with the word “Custom” below it. This screen remains for about 15 seconds, then goes black briefly, and then returns. This continues until I shut down the tablet.how to go head please guide.

    8. Hi Kishore. I have just updated the post recently with an additional file (WETA Kernel) that needs to be flashed along Encryption Disabler, RMM, and Magisk ZIP files.

      Please re-check the download link and follow the updated instructions. Do let me know how it goes.

    9. Hi again, Kishore. I am glad it worked!

      As for the issue you’re facing, please first uninstall the Magisk Manager application from your phone. Then download the latest version of the app from here and re-install it.

      Once that is done, reboot your tablet and try again. It shouldn’t show just ‘Checking for updates’, a few seconds in and you should see ‘Magisk is up-to-date’.

      The ‘Modules’ section only shows the modules that have been installed on your device. To download them, go to the ‘Downloads’ section of the Magisk Manager app.

    10. Hi Dhananjay,
      I have reinstalled the Magisk and when the device is not connected to internet,Magisk manager is up to date. But if I connect the device to the internet through wifi it simply says checking for updates.and the downloads section of Magisk manager is empty.

    11. Hi Kishore. It seems like the application is not properly able to communicate with the servers.

      Do one thing, go to the settings and delete the Magisk Manager app’s data and cache. Then uninstall the app and reboot your tablet. Finally, download the latest version of the app from here, install it, and run it to check if the issue resolves.

  7. I did the first few steps but I didn’t even get to the TWRP recovery mode, all it did was show me the samsung logo and wipe all my data.

    When I went back to booting the TWRP thing again, all I got is a red-colored message ‘only official binaries can be flashed(recovery)’

    Now my OEM unlock toggle is gone and I can’t make it show itself again

    1. Hi John. You will have to start over with the procedure again.

      Well, before we get there, you first need to install the stock firmware on your Tab S4. You can easily download the latest firmware package using the Frija Tool and then flash it using Odin.

      Once done, you will have to wait for 7 days for KG/RMM State to turn normal again and OEM unlocking will then be visible.

      After that, please ping me so that I can guide you further.

  8. Hi, I am trying to root my Tab S4 and the link to T83x_PIE_Encrytption_Disabler_V2.zip is dead.
    Is there a new link?
    My tablet is running Android 9 and all variation I have found of the encryption disabler seem to trip knox.
    Thank you
    AB

    1. Hi AB. I have updated the link with the newer version of the disabler.

      As for KNOX, it will be tripped as soon as you flash TWRP.

  9. Hi,

    I’m trying to download the encryption disabler file, but the site isn’t working?

    Thanks.

    1. Hi Taylor. I have updated the links. Please check again.

      One more thing, I have also added a newer version of TWRP (unofficial), which is recommended.

    1. Hi mr. lee. I have updated the link with the latest version of the disabler. Kindly check again.

  10. Hi,the link:
    For Android Oreo: TabS4_oreo_forced_encryption_disabler.zip
    do not work any more. Are there any other download links?

    Mat

  11. Hi thanks for the tutorial. I am doing this so i can flash kali nethunter 2019.3 to my device. All goes well with your tutorial but when i go back to flash nethunter in twrp it says Updater process ended with ERROR: 1

    Error installing the zip file

    failed to mount ‘/data

    unable to mount storage

    What am i doing wrong can you help?

    Thanks

    1. Hi Will. Thanks for the appreciation.

      After finishing the rooting process, did you reboot your Tab into the OS first? Also, you did follow the whole process, right? Didn’t just stop after installing TWRP?

  12. I tried your guide on a new Tab S4 which came with Android PIE preloaded. After doing everything the tablet won’t boot and it will start a bootloop while showing the “set warranty booloader” flag. KG Status is CHECKING, OEM is unlocked and TWRP will load but system will not….

    is there something I can do?

    1. Hi Antonio. “KG State: Checking” is a sign that prenormal KG State has kicked in, thus preventing you to flash custom binaries or boot your phone. You will have to flash the stock firmware via Odin first.

      After that, you will have to wait for a 7-day period to get KG state to normal. Upon doing this, you will again be able to flash TWRP and follow the procedure further to root your Tab S4.

      I have a question for you: Did you instantly boot your Tab S4 into TWRP mode after flashing it? Or did the tablet accidentally tried and enter the OS? It is very important to boot your phone into TWRP recovery mode right after flashing it to avoid this situation.

  13. I followed the guide exactly as it went and all went as it said it would up intil the last part..
    When all was flashed and done i tried to boot the tab s4 but it kept loading to the samsung logo screen then restarting over and over.. never past the samsung logo screen.
    Im avle to get to the twrp thing and the download mode again but whatever i do i cannot get it to boot to system.

    1. Hi Samuel. Were you successfully able to boot your Tab directly into TWRP mode after flashing it via Odin? Even if it mistakenly tries to enter the OS, the prenormal KG/RMM state will kick in and prevent the device from booting.

      Could you please boot your S4 into Download Mode, and see what the status of “KG State” or “RMM State” is shown as?

  14. Last time I rebooted Into the bootloader there was no visuals telling to how to get out of it. It only says downloading… do not turn off target. I assume there is a way of leaving the bootloader so please can you state how?

    1. Hi, Subl. Have you tried holding the Volume Down and Power buttons together for about 10-15 seconds? That should allow you to force-exit Download Mode on your Tab S4.

      P.S. Are you trying this out on your S4 running Pie?

  15. Hi, I tryed your advises, but in Odin 3.1301 it hangs in SetupConnection. The tablet is unable to reboot or to power off. So I am unable to do anything.

    1. I have the Odin part done. Now I don’t come into the TWRP Tool. I am in the boot loop. Nothing seems to help. What now?

    1. Hi. I just got to know that TWRP for the Tab S4 is now official, I will be updating the instructions and files and ping you back via the comments.

    2. Great tutorial! I got mine to work, but now wondering if you have found out yet if it will work with Pie update. Thanks!

    3. Hi Tom, I have updated the download links. TWRP now officially supports Tab S4, even on Pie. However, decryption in TWRP will still not work. So, you will still need to format /data partition and flash the Encryption Disabler zip file, before you flash Magisk or RMM Bypass zip.

      Not to forget: After flashing TWRP recovery, make sure to boot your tablet directly into TWRP recovery mode. Or else, KG/RMM state will be triggered.

  16. Hi master. After step 8 I cannot boot into TWRP even if I am pressing the combo of buttons. I got loop of reboots and on the screen I can see “set waranty bit recovery”
    Could you please tell me what I did wrong? Thank you in advance

  17. Hi, thank you very much for the article. I followed your instructions but after point 12 I didn`t get the menu that you show in the picture below.
    And what is ment with the tablet`s storage: the sc-card oder the flash-card of the tablet?
    Thank you for any help

    1. Hi, this is an important bit: “After the flashing is complete, it is necessary to boot into TWRP mode directly. Hold the Volume Down and Power buttons until the phone powers off. As soon as it powers off, hold the Volume Up and Power buttons to boot into TWRP recovery on your Galaxy Tab S4.”

      After TWRP is flashed, you must boot directly into TWRP. If by chance you enter the OS, it will go into a bootloop.

      One more thing, after going through the original XDA thread again, I can see that it is not required to flash the “T830XXU1ARH8_dmverity_patched_boot_permissive.tar” anymore. So, in TWRP installation section, you can skip from Step 6 to Step 9.

      Here’s a brief:
      1) Make sure OEM unlock is enabled
      2) Download Forced Encryption Disabler and Magisk 18.0 zip
      3) Copy these files to a micro SD card (Not the tablet’s internal storage)
      4) Flash TWRP via ODIN
      5) After flashing TWRP, boot directly into it
      6) Flash Forced Encryption Disabler and then Magisk

      Reboot at last! Let me know how it goes. In the meantime, I will update this post with the latest files and instructions.

    2. So, I have updated the instructions and files. Before anything else, just download and copy the forced-encryption disabler and Magisk zip files to the micro SD card.

  18. Hello ,
    How flashing the tablet with the version T830XXU2ARK4 ? Because it’s impossible for me . You propose T830XXU1ARH8_dmverity_patched_boot_permissive.tar . do you have a solution please ? thank you

  19. Hello ,
    it does not work at home. The problem comes for me from the android version. You suggest to install T830XXU1ARH8_dmverity_patched_boot_permissive.tar then the android version form my tablet is: T830XXU2ARK4. I have error messages in red. Is there a new version of dmverity_patched_boot_permissive.tar. Thank you in advance .
    @ +

  20. Your Tutorial is no longer working. Newer S4 Tabs have T830OXM2ARJ3 Firmware. After Step 7 the TAB reboots and makes a Factory Reset. I think a newer patched boot file is needed…

  21. I cant seem to find a way to put my files into the internal storage and find them later could you please help me i am stuck on step 5.

  22. Could you please help me.I cannot find out hot to jnstall force encryption and magiska. I can put them on my device but i cant fjnd this with team program twrp.

  23. Hello, after root of Galaxy Tab S4 T835 according to your instructions can I use build-in encryption or can I encrypt this rooted tablet in some other way please? Thanks.

    1. Hi Mato. Encrypting the rooted Tab S4 will prevent it from mounting the /data partition (Internal storage) in TWRP. And you will not be able to flash any files then since ADB is also not working in this case.

    2. Hello Dhananjay. Thanks for the reply. It is a big pity 🙁 Unencrypted tablet is very risky… Do you know any other solution for encryption for this case without built-in encryption, please?

    3. Hi Dhananjay, thanks. I also trust the native encryption the most, but I am thinking about buy of this tablet (mainly like a personal assistant for writing my notes etc) and I need root (for iptables etc) and encrypt this device too… It is the first time (during of my Android use) when I see the device which can be rooted, but not native encrypted at the same time 🙁 Samsung provides the great stylus, but the impossibility of native encryption and root in the same time is a big problem for me. Do you know any other similar tablet where is possible to use native encryption and root it at the same time, please? Thanks.

    4. Hi. Tab S4 is the only Android tablet I’d recommend investing in, especially because of the stylus. Oh, and by the way, as I went again through the procedure, I think you can simply try flashing Magisk while skipping the forced encryption disabler and data formatting part.

    5. Hi, many thanks. So when I understand correctly, first I common native encrypt the tablet and after I only will skip steps 5-7 in “How to Root Galaxy Tab S4” and boots into the OS, transfer the Magisk 17.2 to storage and after I will install Magisk-v17.2.zip in recovery mode and the tablet would be rooted…

    6. @Dhananjay thanks and one more question: Did you try this modified procedure personally or do you know about someone who tested it? Thanks.

    7. I did get the chance to try, but my friend was scared of doing it. Anyhow, there are several other users on the XDA thread, who have successfully tested the procedure on their Tab S4.

    8. Yes. Make sure to transfer the Magisk 17.3 zip to the storage (Preferably SD card) before beginning with the TWRP part.

  24. Hey man, I have followed the instructions and I have hit a wall. I’m on the rooting the S4 part, step 5. I have already installed the TWRP but when I go to try and install the TabS4_oreo_forced_encryption_disabler.zip, my PC doesn’t see the tablet anymore, and I have gone to the device manager and it’s not in there either to update the drivers. What should I do at this point?

    1. Hello, while your tablet is connected to the PC, is it in TWRP mode or in the OS?

Leave a Reply

Your email address will not be published. Required fields are marked *