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

ashyx · Mar 30, 2017

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:

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 Magisk 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:

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 Magisk
5. Reboot

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

1. Boot to TWRP

2. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler

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

4. Install Magisk

5. Reboot and check DATA is mountable

Done.

Magisk: https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-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

.

ashyx · Mar 30, 2017

RESERVED

suzook · Mar 30, 2017

Delete

ashyx · Mar 30, 2017

Deleted.

suzook · Mar 30, 2017

ashyx said:
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.

ashyx · Mar 30, 2017

suzook said:
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.

.

suzook · Mar 30, 2017

ashyx said:
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.

ashyx · Mar 30, 2017

suzook said:
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.

suzook · Mar 31, 2017

ashyx said:
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.

ashyx · Mar 31, 2017

suzook said:
, 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.

suzook · Mar 31, 2017

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

https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk

ashyx · Mar 31, 2017

suzook said:
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk

Looks like Chainfires script can't find partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.

Try this, recovery log if possible please after installing.

https://www.androidfilehost.com/?fid=529152257862715887

If there is still an issue I will patch the boot image manually.

.

suzook · Mar 31, 2017

ashyx said:
Looks like Chainfires script can't mount partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.

Try this, recovery log if possible please after installing.

https://www.androidfilehost.com/?fid=529152257862715887

If there is still an issue I will patch the boot image manually.

.

Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?

ashyx · Mar 31, 2017

suzook said:
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?

Yes apply the patch after supersu to be on the safe side.

whitedragon33 · Mar 31, 2017

Wow, I haven't got the tab in my hands yet, and there's already recovery & root!
Have some beer: Confirmation number: 49581192XS319942M

suzook · Mar 31, 2017

ashyx said:
Yes apply the patch after supersu to be on the safe side.

Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?

ashyx · Mar 31, 2017

suzook said:
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?

Yep. Just extract it from the tar archive and then select install in twrp.

suzook · Mar 31, 2017

ashyx said:
Yep. Just extract it from the tar archive and then select install in twrp.

Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log

ashyx · Mar 31, 2017

suzook said:
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log

Damn, even defining the boot device in the command line doesn't allow named partitions to mount.

Back to the previous twrp then.

Looks like manual patching of the boot image is going to be required.

suzook · Mar 31, 2017

ashyx said:
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.

Back to the previous twrp then.

Looks like manual patching of the boot image is going to be required.

Ok, sounds good. Ready to test whenever you need. I'm available rest of day, and all weekend. Thanks.

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

Inactive Recognized Contributor

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Similar threads

Top Liked Posts