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

[solemgar]

Managed to flash it finally. Had to flash via ODIN Oreo stock binary 3 and the prenormal state disappeared right off the bat. I also had enabled OEM unlock option from the moment I booted the stock rom.

 

[theastroboy]

I encountered a bootloop after flashing TWRP 3.2.1-1 by ashx on my Oreo smt820. I found it was due to dm-verify and patches needed to be flashed. It was a scary moment as I never had such an issue with my smt71x/smt81x. Luckily, I was able to recover by flashing an Oreo stock rom.

I have updated my smt820 to Pie stock rom. Can I just flash this TWRP without any patches applied?

Thanks.

 

[theastroboy]

I encountered a bootloop after flashing TWRP 3.2.1-1 by ashx on my Oreo smt820. I found it was due to dm-verify and patches needed to be flashed. It was a scary moment as I never had such an issue with my smt71x/smt81x. Luckily, I was able to recover by flashing an Oreo stock rom.

I have updated my smt820 to Pie stock rom. Can I just flash this TWRP without any patches applied? I will be enabling "allow modification" to keep TWRP obviously, but don't want to get into a bootloop like before.

Thanks.

 

[bmwdroid]

I encountered a bootloop after flashing TWRP 3.2.1-1 by ashx on my Oreo smt820. I found it was due to dm-verify and patches needed to be flashed. It was a scary moment as I never had such an issue with my smt71x/smt81x. Luckily, I was able to recover by flashing an Oreo stock rom.

I have updated my smt820 to Pie stock rom. Can I just flash this TWRP without any patches applied?

Thanks.

Afai remember when coming from Oreo needed 2 files when on Pie already TWRP only should work.
Did for me.

 

[solemgar]

Managed to flash it finally. Had to flash via ODIN Oreo stock binary 3 and the prenormal state disappeared right off the bat. I also had enabled OEM unlock option from the moment I booted the stock rom.

More welp. Flashing Oreo bootloader binary 3 (for the 825) allows me to flash TWRP fine. The moment I install back bootloader from pie, back to kg prenormal again, even with the bootloader locked. Will have to wait the 7 days and see if it make a difference. From what I read, some roms do not work fine with Oreo bootloader (fingerprint reader)

 

[KeepingItCuttingEdge]

Just saw TWRP has gone to 3.7.0 with official Android 12/12L support. Will you be building this for our S3 units?

www.xda-developers.com/twrp-3-7-0-release-android-12-support/

I already have your Android 13 version installed on my two T820 units and it's working GREAT.

THANKS

 

[Awesometic]

Just saw TWRP has gone to 3.7.0 with official Android 12/12L support. Will you be building this for our S3 units?

www.xda-developers.com/twrp-3-7-0-release-android-12-support/

I already have your Android 13 version installed on my two T820 units and it's working GREAT.

THANKS

Thank you for the info

I have been trying to build a new TWRP on android-12.1 branch with FBE support, but it doesn't work at all because of its image size I guess.
If I implement some basic FBE support on the device tree, it always reaches about 36 MB, so I tried to compress the ramdisk with XZ compression, which needs some patches to the TWRP Android source tree, it can be shrunk to 28 MB but it still not work.
But without FBE, with XZ compression, it can be 26 MB, and it finally works but has no merit to use.
So the plan is to build TWRP on android-9 branch like before, but with support LOS 18.1, LOS 19.1 with FDE encryption and LOS 20.0 with no encryption for now.
Another post of this thing..
- https://forum.xda-developers.com/t/...or-galaxy-tab-s3.4510785/page-4#post-87786447

Sad that there are not many options to choose. I don't know why the recovery image size can be a matter on our device, but it apparently is.

Will share all of the progress and the build instruction for LOS and TWRP, so I hope someone will help us in the future

 

[bmwdroid]

.....
Sad that there are not many options to choose. I don't know why the recovery image size can be a matter on our device, but it apparently is. ......

No idea if that can help to determine the cause but I've took the pit file from stock CSC and made it into txt.
Wasn't (yet?) able to calculate the MB size as Idk the byte size of one block but perhaps you know.

On S5=G900F I know for sure that recovery partition is only 30MB big so perhaps it's the same problem here.
Tried DiskInfo as well but that even didn't show the recovery partition.

 

[Awesometic]

No idea if that can help to determine the cause but I've took the pit file from stock CSC and made it into txt.
Wasn't (yet?) able to calculate the MB size as Idk the byte size of one block but perhaps you know.

On S5=G900F I know for sure that recovery partition is only 30MB big so perhaps it's the same problem here.
Tried DiskInfo as well but that even didn't show the recovery partition.

Didn't think that we can analyze devices' PIT information. Actually, I don't know the size of each block

From your file, the recovery size part is this.

----------------------------------------------------------
Entry Memory Address: 0xE8C
----------------------------------------------------------

Binary Type:                0            (UNKNOWN)
Device Type:                2                (MMC)
Identifier:                 29
Attribute:                  5       (READ / WRITE)
Update Attribute:           1               (FOTA)
Block Size:                 391.168
Block Count:                155.648
File Offset (Obsolete):     0
File Size (Obsolete):       0
Partition Name:             RECOVERY
Flash FileName:             recovery.img
FOTA FileName:

Maybe you did use this PIT Magic tool?
In the screenshot the author posted, block size and the block both has '(KB)' unit next to their label.
Hmm, but don't know yet how to determine the actual size. But it is definitely one of the exact factors we can refer to for the recovery partition.

 

[bmwdroid]

........ Maybe you did use this PIT Magic tool?

Indeed I used that

In the screenshot the author posted, block size and the block both has '(KB)' unit next to their label.

Didn't know the screenshot.

Hmm, but don't know yet how to determine the actual size. But it is definitely one of the exact factors we can refer to for the recovery partition.

So acc to the block count=kb the recovery partition size would be 152MB (155648/1024 kB).
So that should be way enough for a >30MB TWRP.
Diskinfo (Kuder Apps) said 30MB for G900F while its pit file names 30720 blocks.
So that matches.
"Block size" I figured out is where the partition starts.

 

[Awesometic]

Indeed I used that

Didn't know the screenshot.

So acc to the block count=kb the recovery partition size would be 152MB (155648/1024 kB).
So that should be way enough for a >30MB TWRP.
Diskinfo (Kuder Apps) said 30MB for G900F while its pit file names 30720 blocks.
So that matches.
"Block size" I figured out is where the partition starts.

Then, it is peculiar.
After doing my job, I will share the source codes with instructions. Looks like it need to be checked by other developers

 

[gukovsem]

Thank you for twrp, used 3.7.0_9 to install from Odin, because 3.5.0_9 stuck on running.
With this 3.7.0_9 could install Rom with Android 13 instead previous Android 12.

 

[Awesometic]

I uploaded the new TWRP 3.7.0_9.0 recovery.
Actually, this hasn't noticeable change except that syncing with the latest source tree.
If you don't have any issues with the previous version, you don't need to update the recovery image.

 

[KeepingItCuttingEdge]

I installed this via Odin because it would not install as an image file in TWRP 3.6.0.

Today I tried to update your first alpha build of Android 13 to the your 2nd release on Jan. 2nd and 3.7.0 could not mount storage. I formatted Data and restarted to TWRP and it did more but still would just bootloop. Could not mount Cache. I tried repairing the file system and still nothing.

Have you tested this?

I have a 2nd T820 that I had not updated to 3.7.0 and the Jan 2nd build updated fine.


I appreciate your work and just letting you know.

 

[Awesometic]

I installed this via Odin because it would not install as an image file in TWRP 3.6.0.

Today I tried to update your first alpha build of Android 13 to the your 2nd release on Jan. 2nd and 3.7.0 could not mount storage. I formatted Data and restarted to TWRP and it did more but still would just bootloop. Could not mount Cache. I tried repairing the file system and still nothing.

Have you tested this?

I have a 2nd T820 that I had not updated to 3.7.0 and the Jan 2nd build updated fine.


I appreciate your work and just letting you know.

Yes, I'm using this version now. Boot-loop on LineageOS 20 is not fixed yet, you should avoid formatting data partition on the TWRP menu for now.

Please refer to this post: https://forum.xda-developers.com/t/...or-galaxy-tab-s3.4510785/page-5#post-87936447