yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Could someone test this build of TWRP: https://androidfilehost.com/?fid=962339331458993585

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] JWnSC:
Downloading now. Will report back

Sweet! It boots

I'm going to try to get Oreo working without encryption. I'll report back. Thanks
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Just to be clear, you booted this new TWRP on the Oreo bootloader, right?

I just want to check before I try it myself.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] JWnSC:
I'm going to try a fresh install. I'll report back soon. Flashing now.

Ok same as before. I don't think it has to do with recovery tho. Some kind of security Samsung implemented. I can boot with root with encrypted data but won't decrypt for some reason.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Is data mountable directly after FORMATTING?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] JWnSC:
Yes. But after booting it isn't.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Didn't do a clean install. Flashed new twrp and same story. Stuck at rebooting to recovery. Flashed back the old twrp and device boots normal. Could try a clean install but I need my tablet for work at the moment. T825.

Verstuurd vanaf mijn SM-T825 met Tapatalk
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Are you sure you're up to date? It seems you're running an older bootloader.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Can you grab the boot image with twrp and post it.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
i dont have my tab with me right now but i have access to firmware files.. so will it be enough if i upload boot.img.lz4 from the AP files||?

link for boot.img.lz4

https://drive.google.com/open?id=1SJ0Z4o7V63_3CUnbtw9VgWUqj8TF8fcP
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] JWnSC:
Here is the one patched with super su https://drive.google.com/file/d/1pJlpkH_bvE0EEptCy51_8orqtInDZsrY/view?usp=drivesdk

The only way I can seem to get the Oreo build working is to back up system and boot then restore it..wierd

I've tried with magisk and your boot patch but all the same. Without performing the steps above ends in a bootloop
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Is this not just this issue rearing its head again?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
No. Newest bootloader. View attachment 4506893

Verstuurd vanaf mijn SM-T825 met Tapatalk
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
OK will check this out later. Thanks.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] dmokiring:
Gone back to the more reliable Nougat!! Will wait for Oreo to be easily modifiable. [emoji22] [emoji22] [emoji22]
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I wouldn't call it more reliable. Oreo is much better on this tab. I'm sure ashyx will figure all this out.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] whitedragon33:
Shouldn't it be put in the BL slot, not the AP?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
No. The BL slot is for the bootloader, which is the thing that loads and boots either the recovery program or the system. The file that contains the recovery image itself goes in the AP slot.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Can anyone else report the updated TWRP working on Oreo?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
Well it works - it boots into TWRP but we have to do a back up and restore before we can boot to system and after it boots up, TWRP can't read SD card.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
At the moment all I'm concerned with is TWRP actually booting. That's a separate issue to deal with.

Do you have a T820 or T825 as someone earlier said it didn't boot on the T825.

The problem is Samsung have changed the image format and have used lz4 compression it seems.

This is causing issues all round with booting and with boot image patching.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
I've a T825..
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Odd, previous poster said no. I'm currently updating the kernel to Oreo(something I'd rather not do as it will likely break compatibility for earlier OS versions)

If that boots then I'm going look a bit more into the encryption issue.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I have a couple hours today free if you would like to test for t820.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
If I get the chance I'll whip up a build tonight. However I'm still confused as to whether the latest build is booting or not as there are conflicting reports?

I'd rather not waste time on something I don't need to.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
Let me flash latest build, and report back.

---------- Post added at 10:28 AM ---------- Previous post was at 10:20 AM ----------

Latest test build boots. WHat you need now?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Ah right, good.

OK, will concentrate on this other issue with the encryption. I'm guessing it's related to the new lz4 format Samsung are using.

I may post up the new build with latest kernel at some point too.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
OK so it seems OREO brings some major changes to how things are handled at boot time. One of them being the move of the FSTAB from the ramdisk to the vendor directory. This explains why no boot patchers work as there is basically nothing to patch in the ramdisk.

Also it seems the system flags have moved from the FSTAB to the DTB. This is a big PIA as it breaks everything as far as patching goes. It affects anything that needs to modify the system partition as dm-verity is no longer easily disabled.

To disable DM-verity we must decompile the DTB, patch it then recompile. Then on top of that modify the FSTAB in the vendor directory.

However it MAY be possible to override the DTB system flags by adding the system flags to the FSTAB in the vendor directory or maybe we can put the FSTAB back in the ramdisk.

Below is a flashable zip which should overwrite the FSTAB in the vendor directory. If it flashes succesfully then FORMAT the data partion to remove encryption and then reboot back to recovery to see if /data is still mountable.

Also if possible could you copy the newly updated FSTAB from system/vendor/etc/fstab.qcom to the /sdcard then post it, so i can check it out?

https://androidfilehost.com/?fid=746163614322267143

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
You want that file before, or after I flash this. BTW, can't try anything for a few hours.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
After, so I can check the FSTAB changed.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
I have created a patch to patch the FSTAB in system and replace the boot image with a patched DTB version.

This both disables DM-verity and forced encryption.

After flashing this you will need to Format the DATA partition.

SM-T820_forced_encryption_disabler_and_patched_boot

SM-T825_forced_encryption_disabler_and_patched_boot

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I flashed the earlier file. It booted, I formatted data, and was able to mount data. Should I reflash this latest one?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Where you able to still mount data after rebooting to system?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
Nope...lol. Ok, guess I will give latest a shot.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I can't boot to system now. I formatted data, just bootloops. I can boot to twrp though
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Any chance you could post the recovery.log (in file format not copy and paste) after flashing the patch?

Also could you post the stock boot.img you are using?

We can do this another way to work out what causes the boot loop.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
This is just the patched T820 boot image to disable dm-verity.

This can be flashed with TWRP(extract boot.img first) or ODIN.

Ensure the system is booting then flash this without formatting data. This is just to ascertain that the patch works and boots ok without any other mods.

https://androidfilehost.com/?fid=962339331458994891

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I can get log in a little while. I have to Odin back to stock. Nothing I do boots after flashing that 1st test file.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
OK no worries.

If you do get around to flashing the boot image use this link not the previous one.

https://androidfilehost.com/?fid=962339331458994891
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
Heres log
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Everything looks like it flashed OK, so cannot see an issue.

Also according to the log /data is mountable.

Guess we'll just see how things are with the patched boot image.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
It was mountable, but it bootloops. Whats next??
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] lisboapcs:
I own a SM-T825 and updated to Oreo and after some trials and boot loops this is how I got Root and so far everything is OK.

Backup all your personal folders to a MicroSD card or to your PC because all the Internal Card will be erased.

Put in the External Card Magisk 16.4 , no-verity-no-encrypt_ashyx.zip and SM-T825 forced encryption disabler and patched boot - Thanks to ashyx.zip

Magisk 16.4 - https://github.com/topjohnwu/Magisk/...gisk-v16.4.zip

no-verity-no-encrypt_ashyx.zip - https://drive.google.com/file/d/19TD...ew?usp=sharing

SM-T825 forced encryption disabler and patched boot - https://androidfilehost.com/?fid=962339331458994779

Flash with Odin 3.13.1 schwabe93 TWRP 3.2.1-0: (for T825) (I used 7zip to archive to .TAR)

https://drive.google.com/file/d/1Ts6...ew?usp=sharing

Boot in TWRP and use the backup option (only system) to the external card (very important)

Flash - SM-T825_forced_encryption_disabler_and_patched_boot.zip and after go to WIPE and Format DATA ( all internal storage will be erased)

Reboot in TWRP and restore backup from External Card

Flash Magisk 16.4 and after no-verity-no-encrypt_ashyx.zip

Reboot to system (It will take a while, be patience)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I flashed. It boots. but data is not mountable
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] lisboapcs:
You have to flash SM-T825_forced_encryption_disabler_and_patched_boot - and Format DATA ( all internal storage will be erased)

Reboot in TWRP and data will be mountable, but before that use TWRP backup (system only) to an external storage (microsd card)

Restore backup and flash Magisk 16.4 and no-verity-no-encrypt_ashyx.zip
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
Im completely confused now. What a cluster F!

I give up. Another bootloop
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
That's good. It was merely to ensure that it boots not to enable mounting data.

That's was the first step, to disable dm-verity.

Second step is to disable forced encryption so data can be permanently mounted.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Tbh you're confusing things here. There's no point in flashing no-verity-no-encrypt_ashyx.zip as it won't do anything.

Also as far as I'm aware T825_forced_encryption_disabler_and_patched_boot doesn't work either as it doesn't boot after flashing this according to [MENTION=2313936]suzook[/MENTION]? Though I'm not sure why it wouldn't work after formatting data.

All that is required now is to patch the FSTAB and both dm-verity and encryption should be disabled.

Also updated TWRP is available in this thread: https://androidfilehost.com/?fid=962339331458993585

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Ok, this patch should disable forced encryption.

Obviously the previous dm-verity patch should be flashed first and device booted at least once to ensure the device boots.

Then boot to TWRP and flash the encryption patch, next format data and check data is mountable reboot and hopefully data should remain mountable.

I will put both patches here for completeness:

T820XXU1BRE2_dm-verity_patched_boot

Tabs3_forced encryption_disabler

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
data is mountable and system is bootable. Restoring the rest of the device.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Thanks, so it remained mountable after reboot?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
After rebooting to recovery? Yes
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Also after booting to system?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
yes
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Great. Thanks for confirming.

So just to be clear everything is good as far as TWRP, dm-verity and encryption disabled for the T820 and I can post this method to the OP?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
OK, here is what I did to root and restore my T820 on BRE2. But first thank [MENTION=4899305]ashyx[/MENTION] for all his work.

1. Flash ashyx's twrp 3.2.1-1 test tar in odin

2. Directly boot to TWRP, don't boot into system

3. format data in TWRP

4. flash ashyx's dm-verity boot patch

5. re-boot to TWRP, data is mountable

6. flash magisk 16.4

7. flash ashyx's Tab3_forced+encryption

8. restore data from ARA2 twrp backup, this took about 30 minutes

9.. boot to system
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
30 mins to restore data, really? :eek:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
Yeah, it was stupid slow.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
You're telling me. Need to look into that.

However just need to confirm if it does the same when restoring an Oreo backup?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
I'll give it a try. It'll take a little while.

Edit, based on how slow the backup is going I'm going to guess the restore will take a long time. But, I have over 11 gigs of apps and data. Opps, that was files, it's 6.7 gigs. Backup took 884 seconds. Restoring now.

2050 seconds to restore.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
TWRP has always been slow as $hit on this tab. Thought it was the crappy internal storage.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Ah right, thought it was a new thing.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
Just to confirm, all of this works on T825 as well?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] lisboapcs:
YES! just follow jd1639 steps and it will work

1. Flash ashyx's twrp 3.2.1-1 test tar in odin

2. Directly boot to TWRP, don't boot into system

3. format data in TWRP

4. flash ashyx's dm-verity boot patch

5. re-boot to TWRP, data is mountable

6. flash magisk 16.4

7. flash ashyx's Tab3_forced+encryption

8. boot to system
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
The patches are actually T820 specific. T825 versions will be available today along with proper instructions.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
Thank you very much :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] rainman74:
Also from my side confirmation, it works on a Tab S3 SM-T820 with Android 8.0 :)

Flash ashyx's twrp 3.2.1-1 test.tar in odin

Directly boot to TWRP

Flash image boot.img to boot (T820XXU1BRE2_dm-verity_patched_boot)

Boot to TWRP again

Format data in TWRP

Flash Tabs3_forced encryption_disabler.zip

Flash magisk 16.4.zip

Boot to system
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Yeah, if your /data is encrypted now, you'll have to back up from system, not recovery. Best to tar everything up and store on the SD, as you said. You could also use something like Titanium, but that's a bit of a hassle for a full /data back-up.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
Interesting, didn't think about the issue of encrypted data. How can I tell?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Update: TWRP updated links and instructions posted.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Settings → Lock Screen and Security (or Biometrics as it may now be called). Directly above Encrypt SD, you'll see an option to Encrypt device if it is not already encrypted. If you do not see that option, /data is already encrypted. Sadly, there's no option to decrypt it in that case.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
Yup I'm encrypted:rolleyes:. Ugh, here we go again.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Your device will be encrypted as you cannot mount DATA.

Flashfire can back up encrypted data partitions however your mileage may vary on Oreo.

See the OP for new intructions for Oreo.

By the way thanks for all the help in testing and anyone else that helped out. :good:

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] lisboapcs:
Thanks ashyx! I followed the instructions on the first page for (OREO ONLY) and now my SM-T825 is data mountable.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] suzook:
I wasn't much help this time. Lol. Thanks for all you do. Your a true asset to the community!:good:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
It's a 2 way thing. Without willing testers such as yourself nothing would get done.

And thanks to all the others that help out too.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
im bit confused.. whats the difference between

UPDATE: 18/5/2018 TWRP 3.2.1-1

twrp_3.2.1-1_T820_28518

and

T820XXU1BRE2_dmverity_patched_boot

sorry , im a noob in this ..

do i need to flash both??

edit: now i understood ...
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
You need to flash twrp_3.2.1-1_T820_28518 with odin, AP slot. See ashyx's process in the OP and make sure you have auto-reboot NOT checked. Then boot directly to twrp (recovery)

You flash the dmverity_patched in twrp.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
thank you very much for explaining :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
When I flash twrp_3.2.1-1_sm-t825_18518 and manual reboot to launch into TWRP, it just gets stuck at "RECOVERY BOOTING...."

No amount of flashing/reflashing gets me passed this step.

Any ideas?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Which firmware build are you running? Try the T820 build and let me know if that boots.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
BRE2. schwabe93 TWRP 3.2.1-0: (for T825) version did work, however.

Here it is: https://drive.google.com/file/d/1Ts6oFj0BXrZr6bpMbrA1IRY9azAwxONJ/view
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
i too have the same problem :(

struck in this screen when i try to do first boot to recovery on my T 825 after flashing twrp_3.2.1-1_sm-t825_18518.tar
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
link is dead :(
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
Try this one: https://drive.google.com/file/d/1Ts6oFj0BXrZr6bpMbrA1IRY9azAwxONJ/view
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] dmokiring:
This file is all I needed to all on those provided in the OP & all is fine now. Flashed Xposed too & everything is smooth. Thanks to the great works of [MENTION=4899305]ashyx[/MENTION]
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
this one worked, i followed the steps in OP and was able to mount data.. it went into bootloop after i flashed magisk :(
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
Is anyone able to flash the disable encryption zip with that TWRP version? I cannot.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
i was able to, using the TWRP link which u provided and i was able to mount data..
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
I'd appreciate if people would stop posting links in this thread to other recoveries NOT built by me. This IS the original TWRP thread for the Tab S3! :rolleyes:

I will fix whatever needs to be fixed to ensure TWRP boots. However I can't do that without feedback.

Can anyone who has the T825 try the T820 version and let me know if it boots?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Mischka20:
Ist because of root.

There are 2 options:

- remove root

- rename a File liboemcrypto.so toll .bak like described here https://xdaforums.com/showpost.php?p=62539622&postcount=72

The 2nd one worked for me. Found the file in system/vendor/lib

No issues so far.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Zimus:
I can confirm that renaming the liboemcrypto.so file in system/vendor/lib will fix the connectivity problem with Netflix. It's a DRM issue with certain rooted devices. VUDU does something similar, it restricts your VUDU downloads to standard-def if your device is rooted..
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DJBhardwaj:
Wouldn't SuperSU automatically patch the boot image and remove forced-encryption?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Not until the new version gets released.

I have been in talks with Chainfire and he is going to implement my patch into future releases of SuperSU as a user definable option.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DJBhardwaj:
Thanks for the heads up :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] esgie:
Bought the device yesterday.

I don't really get why are you guys dealing with SuperSu when flashing Magisk (with MagiskSU) works like a flaw, and enabling MagiskHide makes su undetectable and tablet passes the SafetyNet (tested) and also OTAs shall be still available (not tested).
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Because I tried it and it had issues. Some apps seemed to think the device wasn't rooted. Maybe that's changed lately.

SuperSU has been around a long time and is super stable. Trusted and works.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sp4r3h:
I updated to latest firmware (April 1st safety fixes) and when I try to push recovery with Odin I get custom binary error and Odin fails. Is this expected or is it likely I've done something wrong?

Second question: I'm new to Samsung / Odin (as you can probably tell) how to I simply load the recovery.IMG rather than pushing from Odin. I just want to load twrp temporarily and not make any permanent changes to recovery or system.

On my nexus' I'd boot to bootloader, fastboot boot recovery.IMG. can this be done with Samsung?

Thanks in advance.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
You need to enable OEM unlock as advised in the OP.

You cannot temporarily flash an image on Samsung devices.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sp4r3h:
Thanks for the quick reply. Yeah for some reason my OEM lock reset so was a bit of a duh moment when you told me.

Can you think of any reason I'm hanging when booting recovery, Odin is passing. Holding the buttons in sequence stated. Twrp never loads.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Which firmware build are you running?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sp4r3h:
I updated to T820XXU1AQD6 which is the new one with April 1st security patches.

I have the downgrade downloading as we speak, I figured it could be this.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
If it works with your downgrade let me know and I'll look at fixing things up.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sp4r3h:
Downgraded to AQBB and it booted. Let me know if there's someway I can help and thanks again for replying.