ROOT Samsung Galaxy Tab S5e SM-T725

[DerZero]

i search a Root for the Samsung Galaxy Tab S5e SM-T725 , for install a Mod PlayStore .....

 

[A.Priori]

Are you asking if there is root for the Tab 5se yet?

 

[DerZero]

yes ... is there a root for the tab S5e?

 

[nsx2brz]

Yes, there is root for the S5e, it is complicated atm...

https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-series-t3918699

yes ... is there a root for the tab S5e?

 

[DerZero]

I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?

 

[nsx2brz]

I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?

I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:

https://topjohnwu.github.io/Magisk/samsung

More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.

 

[AHE_XDA]

I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:

https://topjohnwu.github.io/Magisk/samsung

More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.

I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.

 

[AHE_XDA]

I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.

A few caveats with XAA:

For 'OEM Unlock' to show, you must be connected to WiFi to unlock the Bootloader.

And if you 'Factory Reset' after unlocking it, it disappears completely.

If you change the date, time or year, it doesn't return until you reconnect to WiFi.

 

[A.Priori]

Interesting, just got mine today tempted to try this.

---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------

I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.

Please let us know how it went!

 

[AHE_XDA]

I've managed to unlock the bootloader.

I'll post a few pictures in a moment.

Note: This is for the SM-T720.

 

[AHE_XDA]

I've managed to unlock the bootloader.

I'll post a few pictures in a moment.

Note: This is for the SM-T720.

-----

I've patched the AP file but keeps failing when Odin attempts to write 'Modem':

<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)

For those curious; I'm on the latest version of Odin and running stock XAC firmware.

That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.

But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.

 

[nsx2brz]

Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...

-----

I've patched the AP file but keeps failing when Odin attempts to write 'Modem':

<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)

For those curious; I'm on the latest version of Odin and running stock XAC firmware.

That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.

But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.

 

[AHE_XDA]

Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...

Do you happen to have the URL for the thread?

I'm apt to try this again in a week or two.

 

[DerZero]

best would be a root of CF-AUTOROOT or a TWR and a ROOT.ZIP -.-

 

[nsx2brz]

https://forum.xda-developers.com/ga...ragon-root-waiting-discussion-t3919024/page24

Post #235 is where is says what worked. Good luck! I probably won't have time to try mine until next month.

Do you happen to have the URL for the thread?

I'm apt to try this again in a week or two.

 

[PewPewK]

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.

 

[btonetbone]

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.

Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.

 

[PewPewK]

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.

 

[netjetman]

Great Instructions.

The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.

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:



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.

Hope this helps you achieve root.

 

[PewPewK]

Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.

The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.

Yep, good point. I forgot to include that because in the original e-mail thread, it was already known and implied. But I'll add it to the post here so folks will catch that. Annoying for sure, but at least it works.