[Guide]Rooting Wifi Version of Galaxy Tab s4 (T830)

Search This thread

mistermojorizin

Senior Member
  • Dec 21, 2011
    816
    174
    So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.

    Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.

    1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
    2. Settings>about tablet>tap on build number to get into developer settings.
    3. Check OEM unlock, tablet resets and erases everything
    4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
    5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
    6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
    7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
    8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
    9. Connected tab to PC, opened command prompt, adb reboot bootloader
    10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
    11. Hit “start” in Odin
    12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
    13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
    14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
    15. Open Magisk Manager, it says tablet isn’t rooted.
    16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
    17. Tab rebooted fine
    18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
    19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
    20. Reboot.
    21. ???
    22. Profit?
     

    ScottBroker

    Senior Member
    Jul 12, 2011
    1,828
    224
    So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.

    Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.

    1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
    2. Settings>about tablet>tap on build number to get into developer settings.
    3. Check OEM unlock, tablet resets and erases everything
    4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
    5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
    6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
    7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
    8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
    9. Connected tab to PC, opened command prompt, adb reboot bootloader
    10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
    11. Hit “start” in Odin
    12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
    13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
    14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
    15. Open Magisk Manager, it says tablet isn’t rooted.
    16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
    17. Tab rebooted fine
    18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
    19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
    20. Reboot.
    21. ???
    22. Profit?



    What directory is fastboot and ADB in????
     
    • Like
    Reactions: ianmacd

    Stupifier

    Senior Member
    Jun 8, 2010
    1,906
    680

    mistermojorizin

    Senior Member
  • Dec 21, 2011
    816
    174
    What directory is fastboot and ADB in????

    I already had adb/fastboot setup on my PC for my other phones, but didn't have the Samsung drivers. I installed the android SDK at some point to get the adb and fastboot drivers. Note, that unlike all of my other android devices, the tab S4 didn't respond to fastboot commands (for example, "fastboot devices" command in bootloader/download mode didn't return anything, which was unexpected). But Odin recognized it in that mode. So this doesn't rely on using any fastboot commands, just ADB.
     

    ianmacd

    Senior Member
    Jan 5, 2016
    2,331
    3,723
    Amsterdam
    localhost
    1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
    2. Settings>about tablet>tap on build number to get into developer settings.
    3. Check OEM unlock, tablet resets and erases everything
    4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
    5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
    6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
    7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
    8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
    9. Connected tab to PC, opened command prompt, adb reboot bootloader
    10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
    11. Hit “start” in Odin
    12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
    13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
    14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
    15. Open Magisk Manager, it says tablet isn’t rooted.
    16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
    17. Tab rebooted fine
    18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
    19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
    20. Reboot.
    21. ???
    22. Profit?

    It should be possible to avoid the second system reset in step 12 by flashing a modified system.img with the offending package(s) removed.
     

    ScottBroker

    Senior Member
    Jul 12, 2011
    1,828
    224
    Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.

    I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????
     

    ianmacd

    Senior Member
    Jan 5, 2016
    2,331
    3,723
    Amsterdam
    localhost
    I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????

    It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.

    The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.

    If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.

    This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.
     
    • Like
    Reactions: Stupifier

    ScottBroker

    Senior Member
    Jul 12, 2011
    1,828
    224
    It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.

    The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.

    If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.

    This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.

    I just reflashed the stock image and I am back to normal :(
     

    ScottBroker

    Senior Member
    Jul 12, 2011
    1,828
    224
    Which will also align your camera firmware with your kernel again, but now you don't have root, right?

    No, and I have the wifi version
     

    Attachments

    • tempFileForShare_20180915-101644.jpg
      tempFileForShare_20180915-101644.jpg
      236.7 KB · Views: 1,538

    ianmacd

    Senior Member
    Jan 5, 2016
    2,331
    3,723
    Amsterdam
    localhost
    I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.

    His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.

    After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.

    Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.

    Sent from my SM-G965F using XDA Labs
     

    ScottBroker

    Senior Member
    Jul 12, 2011
    1,828
    224
    His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.

    After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.

    Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.

    Sent from my SM-G965F using XDA Labs

    Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
     

    mistermojorizin

    Senior Member
  • Dec 21, 2011
    816
    174
    Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....

    flashfire won't open. i went through something like this on my fire hd 10, had to install an xposed module to trick flashfire into thinking we're back in an older time and install a really old version of flashfire. Otherwise, the newer version of flashfire would just close/won't open.
     

    machx1111

    Senior Member
    Oct 8, 2013
    193
    39
    Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?
     
    Last edited:

    Top Liked Posts

    • There are no posts matching your filters.
    • 5
      So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.

      Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.

      1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
      2. Settings>about tablet>tap on build number to get into developer settings.
      3. Check OEM unlock, tablet resets and erases everything
      4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
      5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
      6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
      7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
      8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
      9. Connected tab to PC, opened command prompt, adb reboot bootloader
      10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
      11. Hit “start” in Odin
      12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
      13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
      14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
      15. Open Magisk Manager, it says tablet isn’t rooted.
      16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
      17. Tab rebooted fine
      18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
      19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
      20. Reboot.
      21. ???
      22. Profit?
      2
      What directory is fastboot and ADB in????

      Honestly, I don't think the directory should matter as long as adb and fastboot are in your environmental variables. And if they aren't, then just open a terminal in the directory you DO have adb and fastboot in....and run the commands from there.
      https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
      2
      I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.

      His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.

      After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.

      Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.

      Sent from my SM-G965F using XDA Labs
      1
      So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.

      Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.

      1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
      2. Settings>about tablet>tap on build number to get into developer settings.
      3. Check OEM unlock, tablet resets and erases everything
      4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
      5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
      6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
      7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
      8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
      9. Connected tab to PC, opened command prompt, adb reboot bootloader
      10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
      11. Hit “start” in Odin
      12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
      13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
      14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
      15. Open Magisk Manager, it says tablet isn’t rooted.
      16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
      17. Tab rebooted fine
      18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
      19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
      20. Reboot.
      21. ???
      22. Profit?



      What directory is fastboot and ADB in????
      1
      Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone