Galaxy Tab S5e (SM-T720) - Root Instructions (Release 1.0)

Search This thread
By:
Advanced…
L

louvass

Senior Member
Sep 24, 2010
931
100
I have been flashing devices for quite a few years now. I have performed these instructions about 20 times. Only once was I able to get the magisk file to flash using different odin versions. I was able to install TWRP(without issues) and custom ROM. I went back to stock to try this again, Magisk patches the stock firmware sucessfully. My problem occurs once I have patched and try to flash, odin just sits there analyzing the patched file the flash process never really begins. I am in d/l mode and connected when Odin is running. I am not sure what I am doing wrong. I feel its a version things between magisk and odin. Has anyone else had these issues. Any help would be appreciated. Thank you for work on the instructional tutorial.
 
TheTofu

TheTofu

Senior Member
Nov 14, 2012
351
129
Los Angeles
Samsung Galaxy Tab S5e
Don't patch twrp with magisk, it doesn't work on s5e regardless of Odin or through magisk app.
Workaround is rename magisk apk to zip and flash that in twrp, see here https://forum.xda-developers.com/t/rom-13-official-crdroid-9-4.4541563/post-88458655

louvass said:
I have been flashing devices for quite a few years now. I have performed these instructions about 20 times. Only once was I able to get the magisk file to flash using different odin versions. I was able to install TWRP(without issues) and custom ROM. I went back to stock to try this again, Magisk patches the stock firmware sucessfully. My problem occurs once I have patched and try to flash, odin just sits there analyzing the patched file the flash process never really begins. I am in d/l mode and connected when Odin is running. I am not sure what I am doing wrong. I feel its a version things between magisk and odin. Has anyone else had these issues. Any help would be appreciated. Thank you for work on the instructional tutorial.
Click to expand...
Click to collapse
 
  • Like
Reactions: eried1 and DHGE
L

louvass

Senior Member
Sep 24, 2010
931
100
I finally used another method together droid ROM installed and working.
 
Last edited:
caolfin

caolfin

Senior Member
Feb 9, 2012
135
16
louvass said:
I finally used another method together droid ROM installed and working.
Click to expand...
Click to collapse
Hey
Can you explain ? I'm having crazy problems with mine
- Boot Looped
- Bootlocker is locked
- I can get to Download screen but Odin can't flash TWRP (I want TWRP on there) cos the bootloader is locked ;(
- no ADB because debugging is not enabled

I've tried the "hack" where you try to flash the recovery without the bootloader unlocked - basically do it quickly after rebooting into Download - doesn't work for me

Any ideas ? Anyone
 
L

louvass

Senior Member
Sep 24, 2010
931
100
caolfin said:
Hey
Can you explain ? I'm having crazy problems with mine
- Boot Looped
- Bootlocker is locked
- I can get to Download screen but Odin can't flash TWRP (I want TWRP on there) cos the bootloader is locked ;(
- no ADB because debugging is not enabled

I've tried the "hack" where you try to flash the recovery without the bootloader unlocked - basically do it quickly after rebooting into Download - doesn't work for me

Any ideas ? Anyone
Click to expand...
Click to collapse
I sent you a messsge
 
eried1

eried1

Senior Member
May 27, 2016
585
106
Stockholm
Just went though the whole rooting process. Puh. Thought I was experienced in flashing but geez, that's a lot of details. One of the best guides I've read for years.

To have Magisk enabled after each reboot, is there yet no workaround for the necessary power + volume up combination?
 
Lord Sithek

Lord Sithek

Senior Member
Dec 19, 2018
1,462
784
Xiaomi Redmi Note 4
Huawei Watch 2
eried1 said:
Just went though the whole rooting process. Puh. Thought I was experienced in flashing but geez, that's a lot of details. One of the best guides I've read for years.

To have Magisk enabled after each reboot, is there yet no workaround for the necessary power + volume up combination?
Click to expand...
Click to collapse
I wonder if recent Magisk versions are able to detect that and boot to rooted system by default, have you checked this? If not, there is an LSPosed module called FireFds Kot, which does have this feature
 
  • Like
Reactions: eried1
ExTall

ExTall

Member
Feb 26, 2020
44
31
eried1 said:
Just went though the whole rooting process. Puh. Thought I was experienced in flashing but geez, that's a lot of details. One of the best guides I've read for years.

To have Magisk enabled after each reboot, is there yet no workaround for the necessary power + volume up combination?
Click to expand...
Click to collapse
The older versions of magisk used to do this. My tablet starts in rooted mode always unless I do restart
 
  • Love
Reactions: eried1
M

mrbonine

Senior Member
Jun 29, 2013
75
15
San Jose
Samsung Galaxy S9
Samsung Galaxy S10e
ExTall said:
The older versions of magisk used to do this. My tablet starts in rooted mode always unless I do restart
Click to expand...
Click to collapse
I have the same experience. When I rebooted the last few times I forgot to hold the buttons and did a standard reboot to working system. After I realized my error, I checked to see if root had taken, since I wasn't getting blocked from file access in Fx and root was up and running, Since config issues may impact (I'm not using any add-ons to Magisk) do a reboot or two and verify root however you normally would.

If that works it would be cool if you queried on Magisk board to confirm what version the change was effective. Of course reporting back to this thread would help us all. Personally, after rooting S9, S10+, S20 X 2 (all Exynos when necessary) and this S5e Samsung has convinced me they mean business, I.e. Samsung will continue to throw $$ at this and they have more than all of us.

My uniformed guess is the amount of $$ and effort in chasing locked bootliaders on Qualcomm processor devices in the US suggests a reason: Qualcomm or Samsung are under injunction to do so. This is something they likely cannot disclose but may have happened in many scenarios, speculation is useless. Assuming injunction is US origin, it could apply to Qualcomm and woukd be stipulated by their contract with any manufacturer whose end product is sold in US. If Samsung, it's still a US injunction on them specifically. Other more unlikely scenarios would be restrictions on any system or bundled software that had a similar restriction and Samsung can't work around or replace (perhaps their UI layer or key part of their firmware).

Just screwing with the users and continuiung to lose knowledgeable customers isn't a good enough reason to keep writing code to prevent rooting, in my view. It would be much more efficient if they fear targeted exploits, for example, to provide unlock tokens at nominal cost, maybe $5 which would simply unlock the bootliader, the critical components like payments are already disabled by root, which to me is an easy trade-off. Should they issue tokens (one per device, not multiple) they would have a record along with a model/serial which is countable and referencible, if needed.

In that way they win with more information and support of influencers (ugh), much higher satisfaction and brand loyalty around here, and the substantial savings in cost could be used to oh let's see, put expandable storage back in flagships, even add the audio jack back in (no breath being held here).

Samsung is a leading memory card vendor, so they would get some of that back and I wouldn't feel so ripped of by my one lost wireless Samsung ear kernal. Even if they were free with purchase, after their service contract with Youbreakwefix or whatever their name is fell apart a lot of folks (me for one) didn't have access to authorized repair services for months. Vindication, no, but even though those buds/kernals/ear cave corns sound really great not worth retail. If Samsung could stop racing Apple to the bottom with taking away function because Apple did it would help differentiate the entire line.

These are simple issues to market around, for example the headphone jack: survey customers and publish the results. All mobile phone users, iPhone and Samsung specifically. State the COGs and how little space used, easily waterproofed etc. And throw in other Android benefits. As long as Samsung made the case of them Vs Apple, even a case about distributed supply lines as well other Android manufacturers would not be threatened.

Sorry for rant, and happy to trim this stuff out if inappropriate or offensive.

My perspective from Motorola Droid days using both Samsung S level and tablets AND iPhones and iPad Android is dramatically more easy to use, much less expensive, especially for apps, a more diverse and informed customer, and with Samsungs multiple lines especially, much lower entry cost and ongoing cost.
 
Last edited:
eried1

eried1

Senior Member
May 27, 2016
585
106
Stockholm
I have never been able to flash TWRP through Odin. Am on LOS right now. Any ideas?

I will reflash stock and try the process from scratch again. This time also with the guide by Luke1337 from the LOS16 thread in mind.
 
Last edited:
eried1

eried1

Senior Member
May 27, 2016
585
106
Stockholm
eried1 said:
I have never been able to flash TWRP through Odin. Am on LOS right now. Any ideas?
Click to expand...
Click to collapse
Back on stock. I have located the error which prevents TWRP flashing: Acc to the log Odin gets stuck at 'SetupConnection'.

Any suggestions?

Edit: Finally solved it. Took most of the evening. The solution is to 1) turn off the device and then 2) turn it on by going into download mode via usb button combination, meaning the USB cable should not be connected until volume done + volume up is pressed.
 
Last edited:
eried1

eried1

Senior Member
May 27, 2016
585
106
Stockholm
louvass said:
I have been flashing devices for quite a few years now. I have performed these instructions about 20 times. Only once was I able to get the magisk file to flash using different odin versions. I was able to install TWRP(without issues) and custom ROM. I went back to stock to try this again, Magisk patches the stock firmware sucessfully. My problem occurs once I have patched and try to flash, odin just sits there analyzing the patched file the flash process never really begins. I am in d/l mode and connected when Odin is running. I am not sure what I am doing wrong. I feel its a version things between magisk and odin. Has anyone else had these issues. Any help would be appreciated. Thank you for work on the instructional tutorial.
Click to expand...
Click to collapse
Mine is analyzing I write this. Prior to ODIN 3.14 I flashed Magisk via TWRP and created the patched file via Magisk using recovery mode.

Had to reflash TWRP afterwards but that went smoothly. Problem is, the patch forces you to reinstall LOS + Gapps.

Still not getting Magisk to work with TWRP.
 
Last edited:
ExTall

ExTall

Member
Feb 26, 2020
44
31
eried1 said:
Mine is analyzing I write this. Prior to ODIN 3.14 I flashed Magisk via TWRP and created the patched file via Magisk using recovery mode.

Had to reflash TWRP afterwards but that went smoothly. Problem is, the patch forces you to reinstall LOS + Gapps.

Still not getting Magisk to work with TWRP.
Click to expand...
Click to collapse
This is what I have working on my s5e

Magisk v20.4(20400).zip
Magisk manager v7.5.1.apk
Twrp 3.4.0-2 gts4lvwifi
Android 10 T720XXU1BTG3 UK Version
 
eried1

eried1

Senior Member
May 27, 2016
585
106
Stockholm
Finally I have a correct setup with TWRP, LOS and Magisk. Samsung multidisabler was the last piece of the puzzle. Now I need a long vacation :D
 
You must log in or register to reply here.

Similar threads

TiTiB
[Guide] Samsung Galaxy Tab S5e Debloat Without Root-Info
Replies
109
Views
55K
Tom2112
Tom2112
DaWeav
NEW Samsung Tab S5e 10.5inch AMOLED with Android 9 Pie
Replies
40
Views
16K
elcidroyale
elcidroyale
ExTall
Instal TWRP without a P.C. for Galaxy Tab S5e (SM-T720) keeping stock ROM.
Replies
7
Views
6K
D
Dragon1996
Viro_Major
Relock bootloader on Samsung Tab S5e
Replies
6
Views
6K
L
lewmur
B
Galaxy Tab S6 Lite (SM-P610)
Replies
0
Views
5K
B
Bigmike74

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    eried1
    eried1
    Zamperl said:
    I'm using always LOS (+MicroG), TWRP and Magisk. Could you please explain how you did?
    Click to expand...
    Click to collapse
    Unfortunately have no particular instructions to give you. I did it like you described it in the other thread. A small detail might be missing but can't come to think of it on top of my head. This device can be difficult to use if having TWRP and Magisk installed - doesn't resemble any other device I've come across during my many years of rooting.
    View
    1
    Zamperl
    Zamperl
    Thanks so much. I know now that SM-T720 is difficult. All of my other devices (S4, S5, S9+) were working fine with TRWP and Magisk.zip flashing.
    View
    1
    Lord Sithek
    Lord Sithek
    Zamperl said:
    Thanks so much. I know now that SM-T720 is difficult. All of my other devices (S4, S5, S9+) were working fine with TRWP and Magisk.zip flashing.
    Click to expand...
    Click to collapse
    On this tab it's actually impossible to get TWRP along with Magisk on STOCK ROM, but if you want to use it with custom ROM like LOS or crDroid, it's easy. You have to flash TWRP in Odin (probably first custom vbmeta file), boot to TWRP, remove the stock ROM, flash custom ROM, flash Magisk and boot to system. Depending on a Magisk version, you may be asked for additonal setup, but that should be it.
    View
    1
    Lord Sithek
    Lord Sithek
    Zamperl said:
    I never used stock rom. Always TWRP and different OS with Magisk. My fault was updating Magisk app from 26.2 -> 26.3. After installing Magisk with patching image and reboot I got bootloop.
    Now I have TWRP, LOS+MicroG and Magisk 26.2 and everything is working. See my help thread here.
    Click to expand...
    Click to collapse
    Ah yea, 26.3 is known for breaking things on many devices. I use Magisk Delta 26.1
    View
  • 40
    A
    AHE_XDA
    Requirements & Instructions

    HARDWARE & SOFTWARE REQUIREMENTS

    • Windows Laptop/PC with more than 25GB of available storage space
    • SM-T720 Tablet (Galaxy Tab S5e)
    • Samsung USB Type-C Cable (as found in the original packaging)
    • WIFI connection (and if necessary, login details)
    SECTION ONE - LOG-OUT & BACK-UP YOUR DATA

    Log out of your Samsung and Google account(s).

    Back-up ANY and ALL data as following this guide will result in COMPLETE data loss.

    SECTION TWO - DOWNLOAD THE RIGHT UTILITIES

    In order to root, you require several utilities.

    They are as followed:

    Samsung USB Drivers - Provides connectivity between Laptop/PC and your device.

    7-Zip - An open-source file archiver.

    Odin 3.13.1 - Used to flash original or custom Samsung firmware.

    Frija - Downloads the latest available Samsung firmware.

    Magisk Manager (APK) - Helps obtain/manage and extend root options. Download the latest .APK (Application Package).

    Click on the UNDERLINED NAME of the above utilities to download them to your local Laptop/PC.

    PRO-TIP: Create sub-directories, like pictured below, and organize your downloads accordingly:

    fv1roGJh.jpg


    PRO-TIP: Consider a donation to Frija, Magisk or your favorite developers as a token of goodwill and to help ensure future development efforts.

    SECTION THREE - DOWNLOAD THE RIGHT FIRMWARE

    In order to root or, at a later time, return to original factory settings; you MUST have a local copy of firmware.

    This requires knowing our CSC; a three letter code that Samsung devices use to comply with local telecommunication standards and determine device-specific features or updates.

    To locate your CSC, perform the following:

    On your device, go to 'Settings'
    From 'Settings', scroll down to 'About Tablet'.
    Press on 'About Tablet' followed by a press on 'Software Information'
    Scroll downwards until you see 'Service Provider SW Ver.'
    There are three lines.
    The third line will read similar to the following:
    TUR//

    8d79Pd8l.jpg


    Those three characters (e.g., TUR) represent the CSC code for your region.

    PRO-TIP: Your CSC may OR may not be the same as the example; that's expected and perfectly normal.

    Open Frija, which you downloaded under 'Section One', and input your model and CSC.

    Make sure 'Auto' is selected and click on 'Check Update'.

    If the right values are inputted, Frija will look similar to the following:

    dQAmwVIl.jpg


    Click on 'Download' and select a location on your Laptop/PC.

    When the download is complete, Frija will verify and decrypt the firmware.

    Once finished, Frija will look similar to this example:

    aHt9ICBl.jpg


    PRO-TIP: If you can't get Frija to open or download, right click and select 'Run as administrator'.

    SECTION FOUR - UNLOCK THE BOOTLOADER
    THIS STEP WILL REMOVE ALL DATA FROM YOUR DEVICE. PLEASE REFER TO 'SECTION ONE' FOR MORE DETAILS.

    Power off the device.

    Power on your Laptop/PC and login into your Windows account.

    Connect the USB cable to your Laptop/PC but NOT to your device.

    On the device, hold the 'Volume Up' and 'Volume Down' keys at the SAME time.

    zaMSLbnl.jpg


    Connect the USB Cable from your Laptop/PC to the device.

    MzWasVRl.jpg


    You MUST hold BOTH keys during AND after inserting the USB Cable to receive the following warning:

    75AN0JDl.jpg


    PRO-TIP: In SOME cases, you may also need to hold 'POWER' as well.

    To continue towards unlocking your bootloader, hold the 'Volume Up' key for approximately 4 to 5 seconds (or until the screen goes black).

    After 4 to 5 seconds have passed (or if the screen went black), release the 'Volume Up' key and you will be presented with one last warning:

    lEQlbhpl.jpg

    4MPwQhQl.jpg


    Press and click on the 'Volume Up' key to finalize your decision.

    The device will factory reset and from now on, until the bootloader is re-locked, you will receive this warning:

    kzR7FOIl.jpg


    Leave the device to reinitialize. This will take approximately three minutes. The device will erase itself and you will notice several reboots. Afterwards the only activity you'll see is a pulsing 'SAMSUNG' logo. Eventually you will be presented with the 'Let's Go!' set-up screen. Set the device aside for now.


    SECTION FIVE - INSTALLING 7-ZIP

    If you correctly followed the first FOUR sections, you now have the required utilities, firmware and an unlocked bootloader.

    In order to proceed, you MUST install 7-Zip to extract and manipulate key files required for root.

    If you have prior experience with 7-Zip or an alternate compression manager, SKIP this step and proceed to 'SECTION SIX'.

    It IS enough to double-click the EXECUTABLE and install it; you need NOT configure anything.

    However, for a visual reference, follow this LINK to see 7-Zip in use.

    Alternately, for technical support and assistance SPECIFIC to 7-Zip, use this LINK. Search thoroughly before posting.

    SECTION SIX - EXTRACTING FIRMWARE

    Like the CSC code, mentioned in 'SECTION THREE', the name of your download will differ slightly but 'SM-T720' and 'AP_T720' will be in the file name:

    ZCh4LUBl.jpg


    Using 7-Zip, you must extract the following file:

    AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5

    From the following ZIP container:

    SM-T720_1_20190603182427_gegcc1ebw1_fac.zip

    Right click on your ZIP container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.

    OtP4MFul.jpg


    7-Zip will begin to decompress the necessary files and will result in the following output:

    2rWKOlyl.jpg


    Delete ALL files except for the following:

    SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
    AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5

    Rename the extension of 'AP_T720XX.....tar.md5' to 'AP_T720XX.....tar' and ignore the warning provided by Windows.

    When finished, your folder contents will look similar to this:

    YFyHhhOl.jpg


    The AP file is required for root.

    PRO-TIP: Keep the ZIP container should you ever want to revert back to original factory settings. If not, delete it and download again later using Frija.

    SECTION SEVEN - ENABLE WIFI, TRANSFER FILES & INSTALL MAGISK MANAGER

    In 'SECTION FOUR', the device was left to reinitialize.

    This means you have a device that requires set-up:

    JugCu1Jl.jpg


    Do NOT log into your Samsung or Google account. The ONLY thing required is WIFI:

    ZkOiEMql.jpg


    PRO-TIP: WIFI and Magisk work together to help achieve root access, provide updates and for module repository access.

    Once you've arrived at the home screen, you need to enable 'Developer Options' to ensure the bootloader is unlocked.

    To verify your bootloader is unlocked, perform the following:

    On your device, go to 'Settings'.
    From 'Settings', scroll down to 'About Tablet'.
    Press on 'Software Information'.
    Scroll downwards until you see 'Build Number'.
    Tap 'Build Number' seven times to enable 'Developer Options'.
    Press the back button on the navigation bar to return to 'Settings'.
    Underneath 'About Tablet', you will now see 'Developer Options'.
    Open this and locate 'OEM Unlocking'.
    If you've followed the outlined steps, your screen should match this example:

    JFcJni6l.jpg


    PRO-TIP: If your screen does NOT match the example, it is possible you are NOT connected to WIFI or you did NOT successfully unlock the bootloader. If all these conditions are true, restart the device and check again. If the issue persists, create a NEW response in the thread.

    Now connect the device to your Laptop/PC and, when prompted, 'Allow access to tablet data'.

    b0NVc8Hl.jpg


    Using Windows Explorer, copy the following files to the 'Download' folder of your device:

    MagiskManager-v7.3.2.apk
    AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar

    Due to the size of the AP file, this may take several minutes on a low-end Laptop/PC.

    HFesKvhl.jpg


    Once the copy is complete, go to your device and double press on 'MagiskManager-v7.3.2.apk' to initiate the install process.

    PRO-TIP: Due to changes introduced in Android Oreo, you MUST allow permission to install applications (APKs) not obtained from the PlayStore.

    0RZaK81l.jpg


    Click on 'Settings' to open the 'Install unknown apps' screen and toggle 'Allow from this source' on.

    qhhBOZEl.jpg


    Press the back button on the navigation bar to allow the installation:

    FS39HfOl.jpg


    NNK0PKTl.jpg

    SECTION EIGHT - PATCH YOUR AP FILE

    Open your app tray by swiping up and open Magisk Manager.

    You will see a RED QUESTION MARK and the following error:

    'Magisk is not installed.'

    bz3mnObl.jpg


    Click on 'Install' and, when prompted by Magisk, select 'Install' again:

    Af4JK48l.jpg


    e7XCwO8l.jpg


    Magisk will provide another prompt:

    DltXSHRl.jpg


    Choose 'Select and Patch a File' to proceed.

    Magisk will now prompt for device access:

    PagsJ8Nl.jpg


    Click on 'Allow' and the internal Device File Explorer will open to the 'Recent' tab:

    4sKo67xl.jpg


    Click on the top app bar and select 'Downloads' to find your AP file:

    pNrgI3ml.jpg


    And then:

    rx2QxBbl.jpg


    Once inside the 'Downloads' folder, select your AP file to begin the flash process.

    KDr51Avl.jpg


    Once the flash process is complete, the status on the top title bar will change from 'Flashing' to 'Done!':

    UoCfg2il.jpg

    SECTION NINE - RETRIEVAL & DISSECTION

    With our AP file patched by Magisk, you must now locate and transfer it back to our Laptop/PC.

    If you have not already done so, reconnect the device to your Laptop/PC:

    MzWasVRl.jpg


    Open Windows Explorer, double-click on 'Tab S5e', double-click again on 'Tablet' and open the 'Downloads' folder:

    9P7j22Hl.jpg


    Under 'Downloads', you will see THREE files:

    AP_T720XXU1ASF1_CL15813856_QB24038915_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
    magisk_patched.tar
    magisk_install_log_2019-07-10T225845Z

    PRO-TIP: 'magisk_install_log' is an output of the AP file patching process. If you encountered ANY errors, keep a copy and raise a question in the thread.

    Delete 'AP_T720XX.....tar' and copy 'magisk_patched.tar' back to your Laptop/PC; preferably to the 'FIRMWARE' sub-directory suggested in 'SECTION TWO'.

    Due to the size of the 'magisk_patched.tar' file, this may take several minutes on a low-end Laptop/PC.

    Once the transfer is complete, let's make room in our 'FIRMWARE' folder by deleting the 'AP_T720XX.....tar' file.

    This should leave you with TWO files:

    SM-T720_1_20190603182427_gegcc1ebw1_fac.zip
    magisk_patched.tar

    Move OR delete the 'SM-T720.....fac.zip' container so you can focus exclusively on 'magisk_patched.tar'.

    With NO files left except for 'magisk_patched.tar', you must now use 7-Zip again to extract its contents.

    PRO-TIP: Refer to 'SECTION FIVE' if you need a refresher on 7-Zip.

    Right-click on the 'magisk_patched.tar' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.

    Once all files are extracted, your output will look similar to, if NOT exactly like, this:

    4glKI6Pl.jpg


    Now DELETE these files:

    dtbo.img.lz4
    magisk_patched.tar
    modem.bin.lz4
    persist.img.ext4.lz4
    system.img.ext4.lz4
    userdata.img.ext4.lz4
    vendor.img.ext4.lz4

    In order to have the following:

    meta-data [FOLDER]
    boot.img
    recovery.img
    vbmeta.img

    If done correctly, your folder output will look like this:

    ExxEzTMl.jpg

    SECTION TEN - CREATE YOUR TAR
    In 'SECTION NINE', you organized the following list of files/folder:

    meta-data [FOLDER]
    boot.img
    recovery.img
    vbmeta.img

    Using Windows Explorer, navigate to your 'Firmware' folder (or whatever location you used).

    Now, using 7-Zip, you need to compress these files into a TAR container.

    This means you must select ALL files.

    This can be achieved by using CRTL + A on your keyboard or simply by highlighting them all with a left-click:

    N9HBwIyl.jpg


    Right-click on the selected files, navigate to '7-Zip' and, from the sub-menu, select 'Add to archive...':

    Rmtlfb6l.jpg


    If done correctly, the following screen will present itself:

    cRVRo3ll.jpg


    Only THREE things MUST be done to complete our TAR:

    Change the filename to 'magisk_patched' WITHOUT quotations
    Change the 'Archive format' to 'TAR'
    Click on 'OK' to confirm your decisions and begin compression:

    ikRStEGl.jpg


    PRO-TIP: If, for ANY reason, you don't want to keep these files, you can select 'Delete files after compression' before clicking on 'OK'.

    With this step complete, you are left with the following output:

    y5EVzEjl.jpg

    SECTION ELEVEN - DOWNLOAD MODE
    Using the 'Power' key on your device , select 'Power off':

    twjJLsYl.jpg


    Disconnect the USB cable or the device will switch to 'Charging Mode':

    BFYCibVl.jpg


    On your device, hold 'Volume Up' and 'Power' together until the 'Android Recovery' screen appears:

    c57zM9pl.jpg


    'VOLUME UP' will navigate upwards, 'VOLUME DOWN' will navigate downwards, and 'POWER' will highlight and confirm your choice.

    PRO-TIP: You may have to press 'POWER' twice.

    Highlight and select 'Reboot to bootloader' to properly put your device into 'Download Mode':

    1QQJ9Yyl.jpg


    Reconnect the device back to your Laptop/PC.

    SECTION TWELVE - ODIN PREPARATION AND FLASH
    Now, because recovery is unavailable, you must use Odin to flash your TAR file to introduce root.

    In 'SECTION TWO', you downloaded Odin and created a folder for it.

    You must now go to that folder, or whatever folder you opted to use, and decompress Odin.

    Right-click on the 'Odin3_v3.13.1.zip' container, navigate to '7-Zip' and, from the sub-menu, select 'Extract Here'.

    This will create a sub-directory called 'Odin3_v3.13.1'.

    Double-click and you will be presented with the following output:

    cxuGaeHl.jpg


    Double-click on 'Odin3 v3.13.1.exe' to launch the application.

    You will receive a prompt written in both English and Korean. Click 'OK' to close the warning.

    With Odin open, locate and click on the second tab called 'Options' and uncheck 'Auto Reboot':

    maMzpwql.jpg


    When you click on the 'AP' button, Windows File Explorer will automatically launch.

    As per 'SECTION NINE', and using Windows File Explorer, navigate to the location you created and saved 'magisk_patched.tar'.

    Double-click 'magisk_patched.tar' (or alternatively, highlight the file and select 'Open') to have it load into the AP slot:

    8pbfzuSl.jpg


    With all these steps completed and your device connected, STOP and read below:

    A green navigation bar on Odin, and a white bar on you device, will appear.
    This indicates that key files are being written to your device.
    Irregardless of how quick or slow the progress bar is, DO NOT disconnect the device.
    The device, no matter if the flash was successful or not, will do NOTHING because you unchecked 'Auto Reboot'.
    Wait for 'PASS!' to appear in Odin before you disconnect your device.

    If everything was done correctly, Odin will look like this:

    NN7SbLpl.jpg


    Your device, on the other hand, will have the following bar across its screen:

    Otm716yl.jpg


    Now disconnect the device, STOP and read below until you feel comfortable enough to execute the instructions:

    Hold 'Volume Down' and 'Power' until the screen goes black (also known as a 'Soft Reset').
    The moment the screen goes black, continue to hold down 'Power' but QUICKLY switch so now only 'Volume Up' is being held.
    Do this until you enter 'Android Recovery'.
    As outlined in 'SECTION ELEVEN', use the 'Volume Keys' & 'Power' to navigate the menu.
    First select 'Wipe Data/Factory Reset' and, upon completion, choose 'Reboot System Now'.
    Your device will reboot several times. This is expected behavior.

    If everything was done correctly, your device will reinitialize and require set-up again:

    JugCu1Jl.jpg

    SECTION THIRTEEN - ROOT VERIFICATION
    Like 'SECTION SEVEN', you need WIFI to complete set-up but mustn't log into ANY accounts.

    Also, like 'SECTION SEVEN', you will need to install Magisk Manager again.

    Once the first two steps are complete, power-off the device:

    twjJLsYl.jpg


    With the device powered off AND disconnected, hold down 'Volume Up' and 'Power' until you see the following warning:

    bjeoycEl.jpg


    WARNING: From now on, on EVERY BOOT or REBOOT, you MUST do this if you want Magisk enabled.

    Release all keys and allow the device to boot.

    Once Android is loaded, launch Magisk from your app drawer.

    If you are prompted to update, do so but select 'Direct Install (Recommended)' and remember the key sequence on reboot:

    qH7RzSGl.jpg


    NjFIzHHl.jpg


    Magisk Manager, if set-up properly AND with root enabled, will look like this:

    ezi9gBOl.jpg


    Magisk Manager, if NOT set-up properly OR with root disabled, will look like this:

    Zq9WJAIl.jpg


    PRO-TIP: To further validate root, you can use an application like 'Root Checker' to verify:

    BFzyiJol.jpg


    You may now log into your accounts and finish configuring the device.
    View
    30
    A
    AHE_XDA
    This guide is based on the original PewPewK post.

    Which, in turn, was inspired by TopJohnWu's 'Samsung (System-as-root)' Magisk Installation Guide

    It is an extended walk through aimed at ALL users, meant specifically for the SM-T720 (Tab S5e) BUT specifically meant to:

    UNLOCK THE BOOTLOADER
    INTRODUCE ROOT
    RESTORE STOCK/RELOCK THE BOOTLOADER

    Because of the community support, the options available to you have become numerous!

    So if you're looking to squeeze EVERY inch out of your tablet, search the thread for suggestions or see the links below:

    Go HERE if you are interested in custom recovery (e.g., TWRP).

    Go HERE if you are interested in custom ROMs or kernels.

    ROOT WARNING

    Introducing root and further tampering may lead to unfavorable performance and/or shortened device lifespan.

    In extreme circumstances, it may render your device OR specific hardware components unstable or non-functioning.

    By following this guide, you ACKNOWLEDGE these risks and release AHE_XDA, XDA and its CONTRIBUTORS of ANY and ALL responsibility.

    WARRANTY WARNING

    In many states, countries, provinces and territories, introducing root voids device warranty (manufacturer's and/or third-party). Please consult your regional Samsung office, place of purchase or third-party warranty company to determine if these terms are applicable to you.

    ALTERNATIVES TO ROOT

    If you are looking to maintain warranty and continue access to Samsung-specific features, consider disabling or uninstalling unwanted applications via the Android Debugging Bridge (ADB).

    TiTiB, a genius in his own right, has a thread dedicated to the Tab S5e and bloat removal without the cost of warranty.

    Visit it HERE and click 'Thanks!' if it helped.
    View
    16
    A
    AHE_XDA
    Recognition & Sharing Policy

    RECOGNITION

    This guide, and the required methods and software, would NOT be possible with the efforts of the following individuals:

    @topjohnwu
    @ianmacd
    @LuK1337
    @invmini
    @CrazyApe
    @eragon5779
    @PewPewK

    A sincere thank you for your time, hard work and, most importantly, determination to explore.

    Praise and tribute is also extended to @TiTiB for his editorial skills, testing and much needed feedback.

    SHARING POLICY
    Do NOT reuse any part of this guide without first asking.
    Do NOT reuse any part of this guide without giving credit to those in the 'RECOGNITION' header.

    ALL photographs, not screenshots, are the property of myself (AHE_XDA). I spent considerable time capturing and editing each posted photograph. Therefore photographs may NOT be downloaded, copied, reproduced or used anyway without consent.

    If there's something you like (styling/format/text/photographs) and want to use, ask.
    View
    11
    A
    AHE_XDA
    Known Issues (January 31, 2020)

    KNOWN ISSUES (January 31, 2020)

    Where's Recovery?

    Explanation: TWRP (custom recovery) is NOW available. Please visit TeamWin for instructions.

    Workaround: Resolved as of August 6, 2019.

    Magisk shows as 'Not Installed.'

    Explanation: Magisk, due to the changes to the recovery partition in Android Pie & above, will not boot automatically. It requires user intervention.

    Workaround: To enable root access, be prepared to hold 'Volume Up' and the 'Power' keys on EVERY BOOT or REBOOT.

    WiFi stopped working after installing 'magisk_patched.tar' with Odin.

    Explanation: Cause unknown as of January 31, 2020.

    Workaround: In some cases, after introducing root ('magisk_patched.tar'), WiFi may stop working. If this happens, do the following:

    From the app drawer, go to Settings > Connections > Wi-Fi.
    Highlight and select your WiFi network.
    Long press the network name and select "Forget Network".
    Wait 3 to 5 seconds.
    Press and click on the network in which you asked Android to forget.
    Re-enter your password.
    If entered correctly, WiFi will resume connectivity.

    "Your phone is locked because the payment service was uninstalled."

    OR

    Only official released binaries are allowed to be flashed (vbmeta).

    Explanation: To protect against various threats (e.g., compromised data, theft or root), Samsung, as of December 2017, introduced a series of low-level initiatives to LOCK the device should ANY part of Knox be compromised. These initiatives are frequently referred to as 'KG' (KnoxGuard) or 'RMM' (Remote Monitoring and Management).

    Further details can be found HERE.

    Workaround: A workaround now exists, thanks to @ianmacd, but requires TWRP to be installed followed by the Samsung multi-disabler file.

    If you do NOT intend to install TWRP, precautions MUST be taken not to freeze, disable or remove the following files:

    'Payment Services' (com.samsung.android.kgclient)
    'KnoxGuard' (knoxguard.apk)

    In most circumstances, the issue will present itself immediately after the application(s) is frozen, disabled or removed. In rare circumstances, only after a device restart.

    PRO-TIP: Do NOT reboot unless absolutely necessary; opt to power down the device.

    Should you encounter EITHER error, you will need to boot into 'Download Mode', revert to original factory settings and verify your Google account to avoid an FRP LOCK.

    To enter 'Download Mode' and recover from the error:

    Connect a USB cable to your Laptop/PC.
    With power-off on the device, hold down BOTH 'Volume Up' and 'Volume Down'.
    Connect the USB cable to the device, while holding down both volume keys, and press 'Power'.
    If done correctly, the device will boot to 'Download Mode'.

    My Streaming Service won't log me in, no longer provides HD viewing or doesn't allow offline downloads.

    Explanation: Widevine is a digital rights management platform used by major streaming companies to prevent piracy.

    Low-level details can be found HERE.

    Workaround:

    Resolved by @ianmacd and his 'liboemcrypto disabler' via Magisk Manager and/or Custom Recovery (e.g, TWRP) as of April 4, 2018.

    NOTE: If you installed TWRP and flashed the Samsung multi-disabler file, this issue is resolved of as December 13, 2019.

    If you do NOT intend to install TWRP, log-out and uninstall your streaming application(s). With root introduced and magisk enabled, download 'liboemcrypto' from 'Modules' within Magisk Manager. You will be asked to restart after installing the module. Do this and re-enable Magisk on boot. Sideload your streaming application(s) from a source OUTSIDE the Playstore. Log in and resume streaming.


    Items are ADDED and UPDATED as they are discovered, solved or a workaround is introduced. Please message me directly if something is missing.
    View
    10
    A
    AHE_XDA
    Return To Stock Instructions

    To return to stock and/or relock the bootloader, these are the best instructions available:

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

    They are originally intended for the Galaxy S10 series but work perfectly for the Tab S5e (SM-T720).

    Full credit to @robbo1947.
    View

New posts