[RECOVERY][UNOFFICIAL][SM-T820][SM-T825][2022-12-11] TWRP 3.7.0_9.0 for Galaxy Tab S3

[Awesometic]

/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/

# Team Win Recovery Project

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.

Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.

A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM

You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/


# Features

• Flashing a ROM
• Factory reset
• Erasing the partitions including system, data, cache, internal storage
• Backup and restore
• Supports F2FS formatting
• USB ADB/MTP/OTG

# Downloads

• Galaxy Tab S3 LTE (gts3llte, SM-T825)
• Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)

# How to install

• You have to unlock your bootloader in advance. Check "OEM Unlock" in the device settings.

## Via Odin/Heimdall

1. Download "twrp-*-gts3l*.img.tar"from the given link.
   • Check the file name to yours, gts3llte or gts3lwifi.
2. Enter the download mode by pressing the volume-down + home + power buttons at the same time.
3. Open Odin or Heimdall and set the AP slot as the downloaded recovery file.
4. Flash.
5. Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
6. Done.

## Via rooted ADB

• This is for those who can get the rooted ADB shell, by the custom ROM or previous TWRP, etc.

1. Download "twrp-*-gts3l*.img"from the given link.
   • Check the file name to yours, gts3llte or gts3lwifi.
   • In this guide, assume that the file is named "twrp.img".
2. Copy the recovery file into somewhere the device can access.
3. Enter the ADB shell with rooted mode.
4. In the shell, go to the directory that the recovery file copied.
5. Enter the command, "dd if=twrp.img of=/dev/block/bootdevice/by-name/recovery"
6. Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
7. Done.

# Notes

• It may slow until formatting data partition when you are from the stock ROM. It tries to mount data partition using ext4 filesystem but it fails repeatedly.

# Sources

• Device Tree
  • gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte-twrp
  • gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi-twrp
• Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996

# Buy me a coffee

• If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
  • https://www.paypal.com/paypalme/awesometic

# Credits / Special thanks to

• Android Open Source Project
• TeamWin Team
• LineageOS Team
• OmniROM Team
• TWRP Minimal Manifests
• @Valera1978 for his amazing previous work including his MSM8996 kernel
• @ashyx for his amazing previous work on his TWRP
• @EonOfBlack for confirming its working on SM-T820

 

[Awesometic]

## Changelogs

• 2021. 11. 30
  • Updated TWRP version to 3.6.0
  • Started to use my custom kernel
    • Set the kernel to "awesometic-kernel-v0.3"
    • Merged CAF tag LA.UM.7.6.r1-07800-89xx.0
    • Now it supports F2FS file system
    • Improved performance
    • And some more but not related to the recovery
• 2021. 7. 9
  • Initial release

 

[Awesometic]

reserved

 

[elchmartin]

Nice to see TWRP for the sm820...
Cannot really test since my tabs3 is needed as a daily, but that might just change soon...

 

[samsuffit]

Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:

 libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault

It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.

 

[XolYnrac]

I have flashed with tweaked ROM https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/ via adb shell. It work right

 

[XolYnrac]

/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/

# Team Win Recovery Project

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.

Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.

A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM

You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/


# Features

• Flashing a ROM
• Factory reset
• Erasing the partitions including system, data, cache, internal storage
• USB ADB/MTP/OTG

## Prepared but not tested

• Backup and restore
• Hardware decryption

# Downloads

• Galaxy Tab S3 LTE (gts3llte, SM-T825)
• Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)

# How to install

• You have to unlock your bootloader in advance. Check "OEM Unlock" in the device settings.

## Via Odin/Heimdall

1. Download "twrp-3.5.2_9-0-gts3l*.img.tar"from the given link.
   • Check the file name to yours, gts3llte or gts3lwifi.
2. Enter the download mode by pressing the volume-down + home + power buttons at the same time.
3. Open Odin or Heimdall and set the AP slot as the downloaded recovery file.
4. Flash.
5. Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
6. Done.

## Via rooted ADB

• This is for those who can get the rooted ADB shell, by the custom ROM or previous TWRP, etc.

1. Download "twrp-3.5.2_9-0-gts3l*.img"from the given link.
   • Check the file name to yours, gts3llte or gts3lwifi.
   • In this guide, assume that the file is named "twrp.img".
2. Copy the recovery file into somewhere the device can access.
3. Enter the ADB shell with rooted mode.
4. In the shell, go to the directory that the recovery file copied.
5. Enter the command, "dd if=twrp.img of=/dev/block/bootdevice/by-name/recovery"
6. Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
7. Done.

# Notes [2021. 7. 9]

• I started roughly, so the recovery has some files for dealing with hardware encrypted file system, but I couldn't test yet because I need the stock ROM to test but I should keep the workflow with my LineageOS. If anyone can test this then please let me know it works or not.

# Sources

• Device Tree
  • gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte-twrp
  • gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi-twrp
• Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996

# Buy me a coffee

• If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
  • https://www.paypal.com/paypalme/awesometic

# Credits / Special thanks to

• Android Open Source Project
• TeamWin Team
• LineageOS Team
• OmniROM Team
• TWRP Minimal Manifests
• @Valera1978 for his amazing previous work including his MSM8996 kernel
• @ashyx for his amazing previous work on his TWRP
• @EonOfBlack for confirming its working on SM-T820

I would like to help to add dualboot for sm-t820, is there some project in this direction ?

Thanks, Good job!!

 

[Awesometic]

Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:

 libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault

It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.

Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..
If there's no problem when you use another TWRP, can you tell me which one?

I would like to help to add dualboot for sm-t820, is there some project in this direction ?

Thanks, Good job!!

There's no plan for something related to the dual-boot.

 

[samsuffit]

Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..
If there's no problem when you use another TWRP, can you tell me which one?

I tried again, before I messed it up https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.

I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.

---

Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!

From Stock Rom:
- Flash with Heimdall/Odin -> NOT OK
- Flash with TWRP -> OK

Still, I have the error.

[email protected] $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault

 

[Awesometic]

I tried again, before I messed it up https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.

I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.

---

Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!

From Stock Rom:
- Flash with Heimdall/Odin -> NOT OK
- Flash with TWRP -> OK

Still, I have the error.

[email protected] $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault

I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.
Could you attach the logcat when the error occurs?

 

[samsuffit]

I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.
Could you attach the logcat when the error occurs?

Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.

Reading the logs, I've found where the date and time are, for my other problem in the other thread.

I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25

 

[Awesometic]

Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.

Reading the logs, I've found where the date and time are, for my other problem in the other thread.

I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25

Oh okay, thank you for the report anyway.

And the date/time issue, I didn't know that the time data is stored into the /persist directory.

 

[LedgendaryEpics]

twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.

 

[Awesometic]

twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.

Yeah I'm using my TWRP and I agree that there's a performance issue. Will look into this problem.

 

[bmwdroid]

Yeah I'm using my TWRP and I agree that there's a performance issue. Will look into this problem.

I'd love to see camera first, cause that's what I need much more, than a fast booting TWRP.
That I'm using only once a month or less and if it needs 40"' or 5' to start doesn't bother me.

 

[hinghing1113]

I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??
Second, do i need to uncheck auto reboot after install this twrp version?

 

[bmwdroid]

I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??
Second, do i need to uncheck auto reboot after install this twrp version?

1. Well I never installed so it seems not necessary
2. If you mean Odin flashing the TWRP, surely.
Otherwise the old stock recovery gets revived when auto rebooting and not into TWRP directly.

 

[fulleden]

Does this require root?

I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware

 

[Awesometic]

Does this require root?

I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware

Hello.

Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.
Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..

 

[fulleden]

Hello.

Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.
Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..

I agree. I didn't realize the stock recover could overwrite TWRP once you were able to boot into it. Yes, I did have the bootloader unlocked (by OEM unlock in Dev Options, not sure there's another way). I was using Odin to flash and even tried a few different versions. The tablet originally had the latest Oreo Rom. I tried downgrading it to an older Oreo and also tried a Nougant rom. I had to do a "Format Data", otherwise I would get a boot loop and it seems to me that this then forced a "factory reset" on the next restart where it would sit on the Samsung logo for a very long time. I tried several different angles. I could reboot from TWRP back into TWRP. I even tried flashing TWRP on top of TWRP. Every time I went to boot into Android, it would take forever while it was apparently performing a rebuild of something. I was trying to avoid root to avoid tripping Knox. My ultimate goal was to systemize an app using TWRP which I've done on several older Samsung tablets.

In the end, I flashed Magisk then everything worked on the first try. Booting into Android went quick and I still had TWRP. I tripped Knox but in the end I was able to get what I needed onto the tablet. All is fine now.

Thanks for your work on this TWRP recovery and for sticking around to help support it.