FORUMS
Remove All Ads from XDA

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

691 posts
Thanks Meter: 132
 
By mistermojorizin, Senior Member on 13th September 2018, 06:29 AM
Post Reply Email Thread
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/app...mless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/sho...0&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/gal...1arh1-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?
The Following 4 Users Say Thank You to mistermojorizin For This Useful Post: [ View ] Gift mistermojorizin Ad-Free
 
 
13th September 2018, 02:41 PM |#2  
ScottBroker's Avatar
Senior Member
Thanks Meter: 223
 
More
Quote:
Originally Posted by mistermojorizin

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/app...mless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/sho...0&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/gal...1arh1-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????
The Following User Says Thank You to ScottBroker For This Useful Post: [ View ] Gift ScottBroker Ad-Free
13th September 2018, 03:02 PM |#3  
Senior Member
Thanks Meter: 658
 
More
Quote:
Originally Posted by ScottBroker

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-se...-installation/
The Following 2 Users Say Thank You to Stupifier For This Useful Post: [ View ] Gift Stupifier Ad-Free
13th September 2018, 03:32 PM |#4  
OP Senior Member
Thanks Meter: 132
 
More
Quote:
Originally Posted by ScottBroker

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.
14th September 2018, 05:40 AM |#5  
Senior Member
Flag Phoenix
Thanks Meter: 150
 
More
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.
The Following User Says Thank You to tomiga For This Useful Post: [ View ] Gift tomiga Ad-Free
14th September 2018, 08:05 AM |#6  
ianmacd's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 2,556
 
More
Quote:
Originally Posted by mistermojorizin

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/app...mless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/sho...0&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/gal...1arh1-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.
14th September 2018, 08:25 PM |#7  
ScottBroker's Avatar
Senior Member
Thanks Meter: 223
 
More
Quote:
Originally Posted by tomiga

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?????
15th September 2018, 11:33 AM |#8  
ianmacd's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 2,556
 
More
Quote:
Originally Posted by ScottBroker

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.
The Following User Says Thank You to ianmacd For This Useful Post: [ View ] Gift ianmacd Ad-Free
15th September 2018, 01:49 PM |#9  
ScottBroker's Avatar
Senior Member
Thanks Meter: 223
 
More
Quote:
Originally Posted by ianmacd

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
15th September 2018, 02:31 PM |#10  
ianmacd's Avatar
Senior Member
Flag Amsterdam
Thanks Meter: 2,556
 
More
Quote:
Originally Posted by ScottBroker

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

Which will also align your camera firmware with your kernel again, but now you don't have root, right?
15th September 2018, 03:21 PM |#11  
ScottBroker's Avatar
Senior Member
Thanks Meter: 223
 
More
Quote:
Originally Posted by ianmacd

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
Attached Thumbnails
Click image for larger version

Name:	tempFileForShare_20180915-101644.jpg
Views:	1108
Size:	236.7 KB
ID:	4596793  
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes