FORUMS
Remove All Ads from XDA
H10 Turbo

[RECOVERY][ROOT]TWRP 3.2.1-1 Samsung Galaxy Tab S3 SM-T820/T825

12,360 posts
Thanks Meter: 8,064
 
By ashyx, Recognized Contributor on 30th March 2017, 08:22 AM
Post Reply Email Thread
Unofficial release -TWRP recovery for the Samsung Galaxy Tab S3 - SM-T820/T825, Qualcomm MSM8996




TWRP 3.2.1-0 Released
Dec 9, 2017

TWRP 3.2.1-0 is out now for most currently supported devices.

What's new in 3.2.1-0:


What's new in 3.2.1-0:

* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)



Update 18/5/2018
TWRP 3.2.1-1 build released.

Current status: BETA

Features:

[B]MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below) >> to be added
NTFS support
F2FS support >> To be added
Twrp app support


IMPORTANT:
PLEASE READ ALL OF THIS POST BEFORE FLASHING ANYTHING TO YOUR DEVICE.



WHATEVER YOU DO BEFORE FLASHING ANYTHING MAKE A BACKUP OF YOUR DEVICE AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE, DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!




Instructions:


Flash with ODIN using the AP slot.

1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot.
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Failure to implicitly comply with step 4 will result in stock recovery replacing TWRP at first boot


NOTE: Since android 5.1.1 it is necessary to enable OEM Unlock.
Settings -> Developer Options -> OEM unlocking
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.



DOWNLOAD -
Device must be running at least AQD6 or later firmware. Earlier firmware may need the previous builds:


UPDATE: 18/5/2018 TWRP 3.2.1-1

twrp_3.2.1-1_T820_28518

twrp_3.2.1-1_T825_29518


UPDATE: 8/5/2017 TWRP 3.1.0-1

twrp_3.1.0-1_sm-t820_AQD6

twrp_3.1.0-1_sm-t825_AQD6

Previous builds:

SM-T820:
https://www.androidfilehost.com/?fid=745425885120721426

SM-T825:
https://www.androidfilehost.com/?fid=673368273298945058



IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.







Follow the instructions below to disable dmverity, forced encryption and mount internal storage(DATA):

MARSHMALLOW AND NOUGAT ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:

(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot

Boot image patcher
no-verity-no-encrypt_ashyx


OREO ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:


1. Install the relevant boot patch for your device below. This can be installed with ODIN or extract the boot.img and flash with TWRP:

T820XXU1BRE2_dmverity_patched_boot
T825XXU1BRE2_dmverity_patched_boot

2. Boot to TWRP

3. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler

4. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)

5. Reboot and check DATA is mountable

Done.


PLEASE NOTE: The dm-verity patch above for Oreo contains a patched boot image. Any future firmware update could break this patch and cause your device not to boot if flashed. I'm currently looking into a more generic solution to this issue.



To Root:
Flash the latest SuperSU or Magisk(recommended) release with TWRP:

SuperuSu: https://forum.xda-developers.com/app...2-05-t2868133/

Magisk: https://forum.xda-developers.com/app...80cb6-t3618589


INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb...twrp-v3-1-0-0/







DEVICE TREE: soon


PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST













Credits: Me, my testers @suzook, @jonathonalexander, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.

FEEDBACK IS APPRECIATED PLEASE.
THANKS.


DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU



.
The Following 62 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
 
 
30th March 2017, 08:38 AM |#2  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 8,064
 
Donate to Me
More
RESERVED
The Following 3 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
30th March 2017, 10:09 AM |#3  
Senior Member
Thanks Meter: 845
 
More
Delete
30th March 2017, 10:25 AM |#5  
Senior Member
Thanks Meter: 845
 
More
Quote:
Originally Posted by ashyx

How do you mean it bootloops? I thought you said that you were able to mount the partitions and flash supersu?

I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
The Following User Says Thank You to suzook For This Useful Post: [ View ] Gift suzook Ad-Free
30th March 2017, 12:09 PM |#6  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 8,064
 
Donate to Me
More
Quote:
Originally Posted by suzook

I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.

Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA

The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.

.
The Following 2 Users Say Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
30th March 2017, 12:24 PM |#7  
Senior Member
Thanks Meter: 845
 
More
Quote:
Originally Posted by ashyx

Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA

The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.

.

Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
30th March 2017, 01:00 PM |#8  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 8,064
 
Donate to Me
More
Quote:
Originally Posted by suzook

Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.

Its in the first post.
The Following User Says Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
31st March 2017, 12:28 AM |#9  
Senior Member
Thanks Meter: 845
 
More
Quote:
Originally Posted by ashyx

Its in the first post.

, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
31st March 2017, 06:19 AM |#10  
ashyx's Avatar
OP Recognized Contributor
Thanks Meter: 8,064
 
Donate to Me
More
Quote:
Originally Posted by suzook

, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.

I need the recovery log after installing supersu and boot.img patcher.
The Following User Says Thank You to ashyx For This Useful Post: [ View ] Gift ashyx Ad-Free
31st March 2017, 09:25 AM |#11  
Senior Member
Thanks Meter: 845
 
More
Quote:
Originally Posted by ashyx

I need the recovery log after installing supersu and boot.img patcher.


https://drive.google.com/file/d/0BwP...w?usp=drivesdk
Post Reply Subscribe to Thread

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

Advanced Search
Display Modes