yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
If I just flash updated stock firmware, my experience with the S8+ has been that the device re-encrypts (and thus also reformats) /data on boot, and that's a big pain in the neck, even with a good back-up.

I'm expecting the S3 Tab to behave the same way. Is this not the case?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Ch3ck3rM0n:
I tried following steps starting from TWRP:

- install from image: boot.img

- install from image: recovery.img

- install from zip: no-verity-no-encrypt_ashyx.zip

- SHUTDOWN

- boot into download mode

- flash with odin HOME_CSC_DBT_T825DBT1AQH4.....tar

- REBOOT to recovery

-----> then update process starts and shows the attached screen after!

- REBOOT to system

-----> no changes in the menu :( still the same "issue" like I wrote in the post: https://xdaforums.com/showpost.php?p=74130217&postcount=912

By the way:

Is the adoptable storage script from you working on Nougat too? Did you check?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Correct that's why you need to boot into recovery and flash the patch BEFORE it boots.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
And there you have it. No mention at all of FORMATTING /Data after flashing the patch.

HOME_CSC will mess with your /data partition.

You need to be stock first to flash it.

That means no custom recovery, no dm-verity patch, no unencrypted /data partition.

I suggest you flash all partitions with odin.

Some say adoptable storage patch works fine on nougat.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
I understand that, but IIRC, that caused the CSC to be installed and that's when the formatting happened.

I'm going from memory, as the events are a couple of months removed now, but I'm fairly sure that I installed TWRP before booting into recovery for the first time after flashing the new firmware.

On the other hand, if that approach is known to work, then I must have only thought that I had done it correctly.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
If you intend to install a new firmware then the way I would suggest is to back up the data partition and personal stuff to sdcard first.

Then proceed to flash the whole firmware with odin so it can properly upgrade.

You can then proceed to install twrp, flash the boot patch, format data and finally restore your data partition all in one session.

No worries about losing data or encryption troubles with this method.

If you'd rather not have to restore data then you'll have to be smart to prevent the device from booting after the upgrade.

The name of the game here is to catch it when the update finishes and stock recovery auto reboots.

Just be ready with the 3 button combo and reboot to download mode so twrp can be flashed followed by the encryption patch.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
I'd really rather avoid having to restore /data if at all possible.

So if I understand you correctly, I should flash the firmware with Odin after unchecking the auto-reboot box. Then boot to recovery, let the CSC get installed, and then, when the device auto-reboots at the end, catch that and go back into download mode to flash TWRP. Then reboot into TWRP and flash the verity and encryption patches.

Is that the correct order of operations?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] osocooototo:
Any chance this will ever be available for the T827 Verizon model?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
Is this the correct way to flash TWRP ?

.

Hello -

I am finally ready to try and flash TWRP / ROOT (Su) / and firmware if needed.

Currently, I am running the AQ12 on an SM-T820 and I have OEM Unlocked.

This is the procedure I think I should follow Unless anyone sees's an issue

or something I have forgotten. I am just worried of course of screwing this up.

My wife calls it my $600 toy.

First thing, Should I stick with the AQ12 firmware, or switch to the AQF3 ?

This is the plan

......OBJECTIVE: Flash TWRP & Root

Put the tab into DOWNLOAD mode / Uncheck Auto Reboot.

Load ODIN3 v3.12.7

Flash twrp_3.1.0-1_sm-t820_AQD6 in AP slot.

*** QUESTION: If I am on AQ12 do I still flash AQD6 or is there a AQ12 version ?? ***

After flashing, immediately reboot to TWRP recovery.

Choose 'Allow modifications'

Flash 'SU' SR5-SuperSU-v2.82-SR5-20171001224502.zip

......OBJECTIVE: Disable forced encryption

Boot to TWRP

Formate Data partition - FORMAT DATA (found in Wipe options)

Check that DATA is mountable

*** QUESTION:Should I flash SU now or up above at #6 ??

Install boot image patch 'no-verity-no-encrypt_ashyx'

Reboot

--- END

Thank you all for any suggestions or comments on this.

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
Use the newest firmware, AQ12. Twrp and supersu work fine
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DroidIt!:
AQ12 is actually a bit old, relatively speaking. Check here https://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-T825 :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
I checked this page but am confused. For the SM-T820 it shows me this list. It doesnt even show AQ12 .

I see AQD6 I thought that was before AQ12 ? Please could you or someone Help me out and let me

know what the latest firm is for my SM-T820 (USA)

Mobile Phone	SM-T820	T820XXU1AQD6	SM-T820_EUR_NN_Opensource.zip	announcement	Inquiry Link

Mobile Phone	SM-T820	T820XXU1AQF3	SM-T820_EUR_NN_Opensource.zip	announcement	Inquiry Link

Mobile Phone	SM-T820	T820XXU1AQF5	SM-T820_EUR_NN_Opensource.zip	announcement	Inquiry Link

Mobile Phone	SM-T820_CHN	T820ZCU1AQG1	SM-T820_CHN_NN_Opensource.zip

Thank you so much !!

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
AFAIK, AQ12 is the newest firmware for the us. Samsung has always been show updating and it seems the us firmware lags the rest of the world. In any event, twrp and su 2.82 release 5 works for either firmware version
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
Thank you for that !

One

LAST QUESTION

. Probably a stupid question, but just thought I should ask.

Do I flash twrp_3.1.0-1_sm-t820_AQD6.tar ( as per the OP ) or do I flash twrp-3.1.1-0-d2tmo.img.tar ( newest from TWRP site )

I only ask because I am currently using AQ12 BUT the OP offers TWRP3.1.0-1 for the AQD6.

Again I thank you
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Maybe I'm wrong but i don't believe there is a version for our device on twrp. I can't find our device on there. Only the version in this thread is available.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
Twrp from this thread works. I haven't tried the one you mention.

PS, I just looked and there is no official twrp for the tab S3. The twrp you mentioned looks like it's for the s3 phone. DON'T USE THAT.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DroidIt!:
Ahh. There's the confusion. :) In your original post you asked if you should stick with AQ12 or go with AQD6. 12 is for the SM825 and AQD6 for the SM820. If you have an 820, I've been on AQF5. I'd use that one. :good:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
I have an 820 and am on AQ12. It rooted with no issues with the instructions and files in this thread.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] gottahavit:
No here's the confusion. It's not AQ12, it's AQI2, which is the latest us versions from sept for the 820. This is a newer version than any of the AQF* series.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
Ummm ok .. 3 different answers. :confused: - - - I am also on the AQ12 now so I know AQ12 works on the 820. Thank you for the info on the one I posted

being for the PHONE ! I wont use that. I was just confused because the file here in this thread says TWRP.....AQD6.tar and I did not know

if I should flash it onto my AQ12. So it seems like the answer is YES just follow the OP and flash the TWRP.....AQD6.tar onto my AQ12.

.

DroidIt I think AQ12 is for SM820 ? ..

my SM820 has been using it for over a month

?? ... I am not familiar with AQF5 what country is that?

.

Thank you again !!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] gottahavit:
again the confusion is it's not a "1" it's an "I" AQI2 and yes this is the latest for the 820
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
Ok so it is a

I

not a

1

. . . check!

And just flash twrp_3.1.0-1_sm-t820_

AQD6

onto my

AQI2

. ??

### UPDATE

### Just did it all and went just fine. TWRP / ROOT / Dycrypt --- Thank You to all for the help..

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] xpil:
Update t825 lte

I would like to ask the forum a question regarding upgrading my tablet, which is a t825 LTE with a European T825XXU1AQF3. This tablet is rooted, following the OP, and, as such, it has TWRP and magisk 14.0. The question is whether there is a procedure to update to AQI2 without loosing my installed (user) applications and data. Since both firmwares are android 7.0 I do not want to repeat the whole process described in the OP, and start from scratch.

Thanks in advance for your help
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] gerber.chua:
Hi. my firmware is AQE6, is this TWRP (twrp_3.1.0-1_sm-t825_AQD6) compatible for flashing? or do i need a twrp with AQE6?

Thanks in advance.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
I am not 100% sure, but I just flashed the TWRP___AQD6 onto my tab that was running AQI2 and it went just fine. I ended up with 7.0 and the AQI2 firmware,

and I followed the OP exactly as it was posted.

I am not telling you to do that ... but ... it seems like it should be ok. Maybe wait for 1 other person to back this up ?

Good Luck
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] BronzeKnee:
I am confused with these directions, let me get this straight:

I have Odin on my systems I've install new firmwares with it. So after enable OEM unlocking I fire up Odin and install TWRP. Once ODIN reports Pass immediately hold POWER + HOME + VOL DOWN and then change to VOL UP while Holding POWER + HOME when the screen goes blank.

Now I am in TWRP Recovery... and before I do anything else I need to install SuperSU and the boot patcher, right? So I don't reboot or anything, I just format the data partition, check DATA is mountable, then install SuperSU followed by the boot image patcher, then I finally reboot. I don't flash SuperSU and the boot image patcher at the same time, I do SuperSU first then the boot image patcher, right?

But if I wipe the data, won't I lose the SuperSU files and the boot image patcher I have saved on the system? So I'm guessing I need an external SD card, which I don't have, so I can't install this then until I buy one... right?

Thanks for any and all information.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
SD card required or you can use adb sideload.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Thibor69:
Yes you need a sdCard to hold the files. Other than that your steps look fine ..

Oppss

Ashyx

beat me to the reply. ;)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sirscrubsalot:
Hi [MENTION=4899305]ashyx[/MENTION] , thanks so much for this development! I am new to Samsung device modification and just purchased the SM-T820.

The good news: I was able to successfully follow your OP guide and installed TWRP (twrp_3.1.0-1_sm-t820_AQD6)+ SuperSU v2.82 SR5 Beta + no-verity-no-encrypt_ashyx perfectly! :D I did everything in order step by step as you had outlined. (Had to install the Samsung USB drivers on windows 1st). I also flashed AdAway v3.x (systemless enabled in preferences) and that worked and also did flash [MENTION=4873016]schwabe93[/MENTION]'s Flash-Kernel V.1.1 Permissive to just check NTFS OTG Support (doesn't seem to be working as I was hoping but it did flash and shows in the about tablet settings).

My device = SM-T820 (SM-T820NZKAXAR , wifi, 32gb, U.S. Edition) running the latest AQI2 firmware [XAR-T820XXU1AQI2-20170926150246] which I updated + enabled OEM Unlock before your OP instructions.

2 general questions for future reference (Before doing anything I would do the full nandroid backup via TWRP and do have a copy of the latest firmware on both microsd and computer at that given time)

a) If I ever wanted to revert back to stock recovery and stock rom or in case of some other flashing error and I don't want to recover any data (i.e. start from scratch all over), I have the AQI2 firmware in zip format.

Once in "Download Mode" Do I just extract the main firmware zip and just place each of the AP/HOME/CSC/BL files into the corresponding Odin (latest version) slots > uncheck auto-reboot > start > wait for PASS > POWER + HOME + VOLUME DOWN > let it reboot and wait for the process to finish?

b) In the event we ever do receive a new OTA firmware from Samsung, do you have a XDA link handy on the proper way to approach this if we're running stock ROM + TWRP-SuperSU Root? Basically after following your OP in this thread. (I found a few different XDA threads in other samsung device forums, not sure if they apply here).

Thanks again for all the help!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] eos:
Cannot confirm this really works as expected: I have followed your approach to the letter, even managed to catch the stock recovery auto reboot after the CSC installation. When the device (SM-T825) came up with the recent firmware (T825XXU1AQI2) all my data was gone! :rolleyes:

The only thing I did not have to do was format the data partition prior to installing Magisk and the encryption patch. Luckily, I could simply restore my data partition with TWRP.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Of course all your data was gone? :silly:

That's why I stated to back it up before hand and then restore it after the update.

If you mean you didn't wipe it and it was the firmware install that wiped it then you must have used the 4 file repair firmware which DOES wipe the device UNLESS you omit the CSC part.

A stock firmware upgrade should NOT wipe your device..

At least you were prudent enough to have a backup. :svetius:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] eos:
Do not want to sound pedantic, but here is what you said as an option to the backup/restore approach: :D

The firmware package was as stock as they get for all I know. I simply downloaded the most recent one from updato.com for my model, region and provider. I have not the slightest option what the "4 file repair firmware" is or how to get my hands on it. Or are you saying installing CSC always triggers a wipe? If so, why would I ever want to flash it on an upgrade? Should I perhaps stick to HOME_CSC instead? I still do not quite understand the difference between the two.

I also did a full upgrade, i.e. flashed BL, AP, CP and CSC (not HOME_CSC which I perhaps should have tried coming from the same original CSC code). Anyway, doing backups just in case is always a life saver! :good:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
I interpreted the upgrade instructions in the same way you did, and I, too, have been burnt in the past by an unexpected wipe.

One thing I will say is that flashing CSC always causes a wipe, whereas flashing HOME_CSC shouldn't.

That said, I have tried updating the firmware on an S8+ twice in recent months, and even though I stopped the device from booting after the upgrade and instead booted to TWRP, the device was still wiped and re-encrypted upon installation of the csc in the post-flash stage.

I have since given up on upgrading the firmware of any rooted Samsung device in my possession until I can established a guaranteed upgrade path. It's just too costly in terms of time otherwise, even when one can restore from a recent back-up. There is always still plenty of manual configuration to do afterwards.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] eos:
Thanks for your confirmation. That still leaves me with the question whether CSC should be flashed to begin with (unless of course I wanted to migrate to a different CSC). In my opinion, HOME_CSC is the safest option.

That said, I cannot say that my last upgrade was too painful. Always supposing you create a backup of your data partition, you can restore it afterwards and you are good to go! The upgrade itself made a lot of sense because it has fixed some major issues for me, so I can definitely recommend it.

On a side note, having rooted several Samsung devices including your portable TV set a.k.a. S8+ :D can you confirm that when rooting with Magisk rather than with SuperSU Knox does not get tripped? I have seen numerous user reports here indicating this may be the case.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
When I tried this, it wasn't just a question of restoring /data. It turned out that TWRP couldn't even restore its own back-up of /data, so I lost everything from that recent back-up and had to resort to a one month old back-up of an S7 to salvage anything at all. And then I had to reconfigure all of the settings and launcher desktops from scratch. It took a full day of very tedious work.

In fact, I have still never successfully restored a back-up to that S8+ using TWRP. The problem is documented on that device's own TWRP thread, but AFAIK, the issue still isn't fixed.

I can't, I'm afraid. I use SuperSU, not Magisk, but I have been intrigued by the same reports that you refer to.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] eos:
Very unfortunate and frustrating, so much is certain. I have been using TWRP for years now on all sorts of devices and never once had trouble with restore (or backup for that matter). Are you saying this issue only applies to S8(+)? Only I have not seen it yet on SM-T825 which is why I stand by my recommendation to do upgrades.

As for Magisk vs. SuperSU, it is a one way street I am afraid: once you have installed SuperSU subsequent rooting with Magisk will not restore Knox (which makes sense given it is an eFuse hardware flag). In other words, you must never root your device with SuperSU in the first place. Not that I care much about Samsung's warranty policy here in the EU (may those buggers who came up with this stupid idea rot in hell for all I care), but in hindsight it would have been nice to know anyway.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sirscrubsalot:
My current device info: (kernel version: 3.18.31 Flash-KernelV1.1+) / Android Version : 7.0 / build number: NRD90M.T820XXU1AQI2, Android Security Patch: August 1, 2017, SE for Android Status: Permissive / twrp_3.1.0-1_sm-t820_AQD6 + no-verity-no-encrypt_ashyx + SuperSU v2.82 SR5 Beta

General questions for future reference for those familiar with Samsung devices - hopefully this will help other newcomers to Samsung devices and this Galaxy Tab S3

a) If I want to go back to Stock kernel only: do I just extract the BOOT.IMG from the latest AP-Samsung firmware and flash with TWRP + wipe cache + reboot? I saw a few threads about other components in the BOOT.IMG file (like ramdisk, not sure if that will affect anything different).

b) If I ever wanted to revert back to stock recovery and stock rom or in case of some other flashing error and I don't want to recover any data (i.e. start from scratch all over), I have the full Samsung AQI2 firmware in zip format on computer + internal microSD card.

Once in "Download Mode" Do I just extract the main firmware zip and just place the AP tar file or each of the AP/HOME/CSC/BL files into the corresponding Odin (latest Odin version) slots > uncheck auto-reboot > start > wait for PASS > POWER + HOME + VOLUME DOWN > let it reboot and wait for the process to finish?

c) In the event we ever do receive a new OTA firmware from Samsung, do you have a XDA link handy on the proper way to approach this to keep our existing DATA if we're running stock ROM + TWRP-SuperSU Root (or Magisk)? Basically after following your OP in this thread. (I found a few different XDA threads in other samsung device forums, not sure if they apply here). - Do we just backup the DATA partition in TWRP + flash the AP file like we did from the OP through ODIN?

d) Switching from SuperSU to Magisk 14.X+: Let's say we already have SuperSU + no-verity-no-encrypt_ashyx already flashed. What is the proper way now (so many outdated threads all over here) to remove SuperSU and install Magisk? Do we just now flash the latest Magisk 14 in TWRP and it will automatically remove SuperSU?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Where have you read such nonsense?

It doesn't matter what the root method. Anything that modifies the boot or recovery partition causes knox to be tripped. Even simply unpacking and repacking the stock boot image will trip knox.

The bootloader does integrity checks on both, if the signature is missing or doesn't match what it expects knox is tripped at first boot.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
All of my S8+ back-ups completed without error. It wasn't until I actually attempted to restore a back-up that things went awry.

That was actually the first time I had ever needed to call on a TWRP back-up. Prior to that, I had used FlashFire.

I'm familiar with the workings of the KNOX bit, but like you, I live in the EU and enjoy better consumer law than in many parts of the world.

That said, I would always root regardless of my consumer rights protection, because running without root means that one cannot fully utilise the power of the device, and that's unacceptable for a device of this price. For that reason, I couldn't care less about KNOX.

I've followed Magisk's development since its inception, but its development model is too haphazard for my taste and it puts down too many roots into the system. I find SuperSU to be a much cleaner, more robust piece of code.

Anyway, none of this directly relates to the Tab S3, so we should probably discontinue our little aside.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bjcamp95:
Has anyone created a build that includes TW_INCLUDE_CRYPTO i would like to have device encryption as well as recovery images