• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

ROOT Samsung Galaxy Tab S5e SM-T725

Status
Not open for further replies.
Search This thread

jimger

Senior Member
Dec 13, 2012
183
16
Cambridge,UK
OnePlus 8 Pro

ElsaReyes

Senior Member
Apr 25, 2016
353
37
Small update, the crashing hasn't happened in several days now. For some reason it seems it was the screenshot app I used causing it, or so I assume as after I stopped the crashes stopped. It's weird though as I've used it for so long and it's only now that it caused problems, and it hasn't updated since November so, -shrugs- Guess something about the newest Magisk didn't agree with it or something, I dunno.
 
  • Like
Reactions: TiTiB

DRAGON_poop

Member
Jun 26, 2014
45
4
You might want read this in advance to understand the procedure a bit better.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
The other files in the docs folder also contain good info to read, better know to much than being sorry.

In Step 8 of the instructions for Samsung it reads:
"Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do."

But PewPewK's instruction (#10) only mentions to flash AP. Should I only put the tar file in AP, and leave the BL, CP and CSC boxes untouched?

Can anyone please help me? @PewPewK


Edit: I found the solution
 
Last edited:

RagingHarry

Senior Member
Jan 8, 2012
826
328
Havelte
Google Pixel 5
In Step 8 of the instructions for Samsung it reads:
"Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do."

But PewPewK's instruction (#10) only mentions to flash AP. Should I only put the tar file in AP, and leave the BL, CP and CSC boxes untouched?

Can anyone please help me? @PewPewK
For me the @topjohnsw aka magisk worked better including that odin version, resulted in a no error flash.
The Patched D version of odin was any time of 8 fail end on modem.
Also adb pulling the magisk patched ap file seems a must, for me that tutorial was tye first full successfull flash, that's why I was redirecting there.
 

AHE_XDA

Senior Member
Mar 20, 2019
129
182
If you unlock bootloader to this and root it, do u lose the drm l1 so netflix hd?
+ do u void warranty and hit knox counter?

Yes, after root, Netflix is only presented in HD AND you'll need to sideline the APK OR use Magisk Manager to install a workaround (liboemcrypto).

And, finally, adding root will increment the Knox counter and, depending on your region/territory/country, you may also lose warranty eligibility.
 
  • Like
Reactions: TiTiB and jimger

DRAGON_poop

Member
Jun 26, 2014
45
4
Can anyone pls help me?
I am not succeeding using odin. It keeping failing at modem.bin
I've got the right firmware version for the June update, using oding 3.13.1_3B_PatcheD (tried the latest odin, and that failed too)
In Odin i keep the CP slot empty, while adding the patched tar file in AP, and the BL and CSC files that come with the firmware for my device (canada).


<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 6055 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> abl.elf
<ID:0/005> xbl.elf
<ID:0/005> xbl_config.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> aop.mbn
<ID:0/005> cmnlib.mbn
<ID:0/005> cmnlib64.mbn
<ID:0/005> keymaster64.mbn
<ID:0/005> vaultkeeper.mbn
<ID:0/005> qupv3fw.elf
<ID:0/005> sec.dat
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> bksecapp.mbn
<ID:0/005> storsec.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> dspso.bin
<ID:0/005> vbmeta.img
<ID:0/005> system.img.ext4
<ID:0/005> dtbo.img
<ID:0/005> vendor.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<ID:0/005> vbmeta.img
<ID:0/005> modem.bin
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)


I will try pulling from adb, and will report the result soon
 
Last edited:

DRAGON_poop

Member
Jun 26, 2014
45
4
You want to flash patch or stock?
Try just AP to flash, no modem

i want to flash the patch created by magisk when I load the AP in it.

https://github.com/topjohnwu/Magisk/blob/master/docs/install.md

in # 7 method for samsung, topjohnwu writes "Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do." That is why i loaded BL AP and CSC files. I haven't gotten a chance to use the tablet but I feel as if pulling the patched tar file through adb might work. That is the only thing I didn't do exactly.
 
  • Like
Reactions: RagingHarry

RagingHarry

Senior Member
Jan 8, 2012
826
328
Havelte
Google Pixel 5
i want to flash the patch created by magisk when I load the AP in it.

https://github.com/topjohnwu/Magisk/blob/master/docs/install.md

in # 7 method for samsung, topjohnwu writes "Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do." That is why i loaded BL AP and CSC files. I haven't gotten a chance to use the tablet but I feel as if pulling the patched tar file through adb might work. That is the only thing I didn't do exactly.
Above is the post before.

Following the post before yours worked for me perfectly, did That a few weeks before today (read all the md"s to be sure what I was doing)
Your linked guide does not mention corruption problems using mtp for copying files, where as topjohnwu writes about in the github .md
I did use mtp the first and ran into trouble with patched files, later I tried to adb pull them and flashed with other "mentioned" files, worked perfect. (note used latest official odin, the patchedD didn't work properly, again the Auth modem failure, even on full stock June firmware)
The other needed mentioned key combos to do so are well described in this thread in the tutorials.

For me the #7 was a must, and topjohnwu doesn't say stuff for nothing..
He's the W(s)u master..

So actually all the needed info could've be found here, and your link is confusing others, cause it is missing up to date info.
Please don't take it hard, but I rather follow a guide by topjohnwu then any other on rooting..
 
Last edited:

DRAGON_poop

Member
Jun 26, 2014
45
4
I have pulled the patched ap file created by magisk through adb, but the odin for mac (jOdin) fails to retrieve a PIT file. For the Odin on windows there isn't any prompt for a PIT file, and after searching through previous threads regarding it, people say it is not needed. However, jodin does not seem to want to start flashing without it. Would anyone here have the PIT file of Model number SM-T720? How i wish I had easy access to windows right now. I will try to get access to another machine in the meantime.
 

NSD

Senior Member
May 9, 2006
143
6

For the life of me I can't get Odin 3.13.1 to recognize the device in download mode, not sure how to proceed. Different cables, different ports (2.0 and 3.0), different computers (Win 8.1, 10) I just keep getting Code 43 (Device Descriptor Request Failed).
 
Last edited:

AHE_XDA

Senior Member
Mar 20, 2019
129
182
For the life of me I can't get Odin 3.13.1 to recognize the device in download mode, not sure how to proceed. Different cables, different ports (2.0 and 3.0), different computers (Win 8.1, 10) I just keep getting Code 43 (Device Descriptor Request Failed).

Does Windows recognize the Tablet?
 

NSD

Senior Member
May 9, 2006
143
6
Does Windows recognize the Tablet?

Turns out all I had to do was just wait a few hours and it would magically start working... But now I have a new issue. Odin fails due to missing modem file since the Canadian version is wifi only and I'm scared to flash the AUS modem.
 

AHE_XDA

Senior Member
Mar 20, 2019
129
182
Turns out all I had to do was just wait a few hours and it would magically start working... But now I have a new issue. Odin fails due to missing modem file since the Canadian version is wifi only and I'm scared to flash the AUS modem.

This is exactly how your 'magisk_patched.tar' should look.

Don't put anything else in there.

Aldo it doesn't matter what version of software you use; all versions of SM-T720 use the exact same hardware.
 

Attachments

  • Example.jpg
    Example.jpg
    160.4 KB · Views: 111
Last edited:

NSD

Senior Member
May 9, 2006
143
6
This is exactly how your 'magisk_patched.tar' should look.

Don't put anything else in there.

John Wu's instructions from here say you have to add files for BL, AP, CP and CSC right? Also my tar doesn't look like your screenshot. Did you manually remove the .lz4 files that were in it, and are flashing it by itself (so only AP checked in Odin)?
 

AHE_XDA

Senior Member
Mar 20, 2019
129
182
John Wu's instructions from here say you have to add files for BL, AP, CP and CSC right? Also my tar doesn't look like your screenshot. Did you manually remove the .lz4 files that were in it, and are flashing it by itself (so only AP checked in Odin)?

I understand the instructions you're referring to but see the following post:

https://forum.xda-developers.com/showpost.php?p=79547905&postcount=18

This is what many of us have been using as a template.

And yes, you are correct. I removed several files and only flashed the requisite files via Odin using the AP slot.

I'm including a before and after screenshot to elaborate.
 
  • Like
Reactions: NSD
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.

    Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:

    Because my installation process was hardly linear (I ran into many problems along the way), I can't guarantee that these are exclusively the exact steps you would need to take to get it working. But I think this should be a compilation of all the final (working-ish) steps I took.

    (1) Setup tablet for first time, go to settings, enable developer mode, and flick the OEM Unlocking switch.
    (2) Turn off the Tab S5e and boot into Download Mode by holding Power and Vol Up + Vol Down. Then hold up on the Vol Up button (not just a quick press) as it says to enter Bootloader Unlocking Mode. Follow the instructions there to fully unlock the bootloader.
    (3) The tablet will be formatted at this step. After the bootloader is fully unlocked, make sure you boot back into the Tab S5e and perform the set up again. Enable developer options and make sure that the OEM Unlocking switch is turned on. Yes, again. This step is necessary apparently due to some changes Samsung made with their new VaultKeeper service? If you don't you may soft brick the device.
    (4) Install @ianmacd's Magisk Manager application on your Tab S5e. Download is here. [Update: TopJonWu's official Magisk build should now work fine.]
    (5) Download the latest Tab S5e firmware build. I found my copy here. Extract from it the AP file. Transfer this file to your Tab S5e.
    (6) Back in Magisk Manager, go to settings and look for "Update Channel." Here's where I'm a little uncertain of what I did that finally got it to work, so I'll recommend two steps...
    (7a) Select the ianmacd update channel and return to the home screen of Magisk. [Update: This shouldn't be necessary anymore, especially if you installed the official Magisk Manager earlier.] Click install, then choose the patch file option. Locate the AP file you transferred earlier and wait for it to finish creating a "magisk_patched.tar" file. Transfer this file to your computer and rename it "magisk_patched_ianmacd.tar," then delete the old magisk_patched on your device.
    (7b) Do the same for the Canary (debug) update channel. Patch the AP again, and locate the patched file, copy it to your computer, and rename it to something clear.
    (8) This is an odd step I had to follow to avoid errors flashing. It turns out of the several times I tried making the patched images, I almost always inevitably had some file in the archives getting corrupted. So open up both magisk_patched.tar's and test them for errors. I did this in 7-Zip, but there's probably ways to do it in WinRAR, too. If it gives you any error, take a note of which file it failed on because that guarantees your flashing will fail in later steps. In fact, the reason I recommended doing two different methods for patching magisk above was because the first ianmacd patch I tried had a corrupt recovery.img. What I ended up doing to fix it was extracting a working (non-error checking) recovery.img, vbmeta.img, and boot.img from the two different patched Magisks and then recombined them myself into my own Magisk tar. I also kept the meta-inf folder in there for good measure, though I don't think it's necessary? So in the end, I had what I called a "magisk_patched_lite.tar" that contained exactly three images: recovery.img, vbmeta.img, and boot.img, along with the meta-inf folder and ensured 7-Zip did not return any errors on the archive.
    (9) Reboot the tablet to Download Mode. Press Vol Up to start. Attach the Tab S5e to your computer, and start Odin (I used v3.13.1_3B_PatcheD).
    (10) Put some working archive of the patched magisk in the AP slot and uncheck "Auto Reboot." I don't know if the 'lite' version is sufficient for your first flash, but I suspect that it is (it would not be sufficient if you're pre-patching an updated firmware for the Tab S5e). Let Odin rip and see if you get any errors.
    (11) Assuming Odin was successful, hold Power and Vol Down to exit Download Mode, then immediately switch to Power and Vol Up once the screen shuts off. Continue holding these until you are greeted with Recovery mode.
    (12) Use the volume keys to select Factory Reset/Wipe Data. Execute that to make sure the tablet is properly formatted.
    (13) Use the reboot into system option at the top of recovery. Hold Power and Vol Up until the "Bootloader is Unlocked" warning screen shows up, then release.
    (14) If you're lucky, you should eventually see a red warning message about not having Samsung software installed. That's a good sign. My tablet fumbled around these steps and looked like it was gonna bootloop for a while? But eventually, it ran its course and booted.
    (15) You hopefully have root installed now. Set up the tablet one last time, install the ianmacd Magisk Manager again and open it up. If it says Magisk is installed, great job, otherwise... I don't know where the issue is because this rooting sequence is way more complicated than for other devices! At some point, I think after a reboot, Magisk Manager asked if it could do some additional setup stuff. Obviously let it do that.

    I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.

    Also important! Fundmentally, this version of root works very differently from what you may be used to. See here for detailed information. Normally root is installed onto the boot partition, but Samsung did some ****y stuff this generation to be "compliant" with Google's new rules, but still do things in their own special way, so now to achieve root Magisk has to live on the recovery partition.

    Magisk living on the recovery partition means that in order to boot with Magisk enabled, you have to boot into recovery. So to boot with root, hold power and vol up until you see the "bootloader is unlocked" warning screen, then release. If you hold Vol Up, you will be taken to recovery, which will boot the system partition with root enabled. Otherwise, your tablet will boot the system partition without root. So if you do not do this step, root will not work (i.e. you'll boot into system without Magisk).

    Hope this helps you achieve root.
    8
    The first release of my guide is NOW available here:

    Galaxy Tab S5e (SM-T720) - Root Instructions (Release 0.1)
    https://forum.xda-developers.com/an...-t720-root-t3947806/post79892274#post79892274

    If you are having difficulties, this guide is user-friendly and quite comprehensive. I will take questions there.
    @MikeChannon - Can we close this thread please and thank you?
    4
    You da man! Appreciate your help.

    My pleasure. Just finalizing a guide to make this a bit easier for other users. Enjoy!
    4
    @AHE_XDA, boss will you publish guide, with collected all knowledge and experiences?
    Thanks

    Yes Sir. Need 48 hours.
    4
    I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.