yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Can you send me the recovery image from the new firmware?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sp4r3h:
https://drive.google.com/file/d/0B5MRHtQPq3qvZjUtX0RXZW5nRGc
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] samtran0331:
I'm an idiot...

I tried to follow the directions exactly, but now my S3 will only go into download mode.

I can't get into recovery nor Android.

I think my mistake is that instead of getting the latest SuperSU, I used one I already had...I think it is the latest stable release. (<-- This is the idiot part)

Since I can get into download mode, I've tried to use Odin to reinstall twrp, but I still can't get into twrp.

Any suggestions?

Thanks all!!!!!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
From download mode hit cancel then quickly hold POWER + HOME + VOL UP
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] acc3d:
Checking for updates manually and I'm stuck on the March security patch; no April patch is available for me. I'm located in USA. What country are you in?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] gpsrookie:
Hi,

thanks a lot for this work! Everythings works fine, but I have a question concerning "SE for Android". The status remain "Enforcing". Shouldn't it be "Permissive"? For example I have installed the app Linux Deploy (it needs root). Everytime when the app starts mounting partitions it hangs and then my tablet reboots. I assume that this has something to do with SE. Is there a possibility to change SE to permissive?

Thanks in advance!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
I keep receiving a "Failed to map file" with the forced+encryption ZIP :(

EDIT: Nevermind, this was due to a corrupt zip.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
sec.. trying
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
My apologies. Will try the T820 version now.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
nope, its not booting into TWRP ..
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kev1000000:
Yep, no boot with the T820.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Strange how it boots for others? :confused:

Will be back shortly.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Near-perfect upgrade to Oreo

Many thanks to [MENTION=4899305]ashyx[/MENTION] for his ongoing work on TWRP for this device.

With today's progress and updates to this thread, I finally reached the level of confidence I required to undertake the upgrade to Oreo on my T820.

My S3 Tab was still running AQF7 Nougat from way back when. I hadn't wanted to mess with it after successfully rooting it with SuperSU, because it was working perfectly, and I didn't want to do the upgrade to Oreo until I was certain that the no-encryption patch was functional on the new build. I really didn't want my unencrypted /data to inadvertently get encrypted in the course of the upgrade.

Anyway, after flashing the full T820XXU1BRE2_T820OXA1BRE2_BTU build with Odin and rebooting back to download mode to flash the new TWRP, it was basically just a case of following the updated instructions in the OP.

I rebooted to download mode a third time to flash the new DM verity patch, then booted TWRP and flashed the new forced encryption disabler package, followed by Magisk 16.4.

At this point, the device had been subjected to no fewer than 5 separate flashes after shutting it down in its Nougat state. /data was still mountable, so that looked good.

The device was now ready to boot to system, so I gave the command, and away it went.

It took a little while to come up, during which time I was afraid that /data was being re-encrypted, but it was just the initial boot on Oreo that was slow. When the device came up, I quickly verified that /data was still unencrypted, and that Magisk had properly been applied.

The one weird thing I have since the upgrade is that I now have T Roaming and Service Provider entries under Settings. Of course, this is a T820, so neither option should appear, but apart from that, Service Provider lists a KT Twophone Service submenu. I don't know where KT Twophone Service is from, but it has nothing to do with my device's CSC, which is the generic Dutch PHN. All of the options under T Roaming and Service Provider crash the Settings app if I tap them. I flashed the BL, AP and HOME_CSC files in Odin, so I'm not sure how this little oddity crept in, but there you go.

Apart from that little anomaly (which, in any case, has nothing to do with TWRP or the extra patches from this thread), the upgrade was as smooth as silk. You just have to make sure to read the OP, read it again to make sure you understand every step of the process, and then carefully proceed, one step at a time, verifying the successful completion of each stage as you go.

Thanks once again to Ashyx for all of his patience and hard work, and to the testers, who sacrificed the short-term usability of their devices to allow all of us to be able to enjoy rooted Oreo on these devices.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jd1639:
If you flash the CSC, not home you won't have all that extra stuff in settings. You'll, of course, have to reinstall all your apps. But that's the only way I know to avoid the stuff in settings.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
But the whole point of flashing with HOME_CSC is to preserve the CSC you already have. That's what I did and there was no error. And these new XXU firmware files (like T820XXU1BRE2_T820OXA1BRE2_BTU.zip) are all multi-CSC, aren't they?

The popular Phone Info app reports that my device no longer has an active CSC. Hmm. Maybe I'll try reflashing HOME_CSC later this evening, although I can feel that desire not to want to mess with a working device kicking in again. Still, flashing the HOME_CSC again is low risk, so I'll probably give it a go.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Didn't you have it working previously as you reported it booting in a previous post? :confused:

https://xdaforums.com/showpost.php?p=76604674&postcount=1307

Can either of you try this build with an updated Oreo kernel:

https://androidfilehost.com/?fid=890278863836288342

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
no its not booting

edit: whats an updated Oreo kernel? im on stock BRE2
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
it wont boot into system after i tried to boot into TWRP, now ODIN flashing stock rom
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Now I'm well confused. :confused:

Didn't you say in a previous post you had TWRP 3.2.1-1 booting?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Jsilver73:
well I'm up and running on t820 with oreo by flashing the stock system in odin (ensuring the reboot was unticked) and then flashing patched boot.img and encryption patch as per the op - I flashed magisk 16.4 after setup, however despite magisk showing up properly root apps can't seem to access root from magisk. too tired now, will have another look in the morning and if anyone knows anything here that would be great :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] lisboapcs:
I own a SM-T825 and I just would like to confirm the TWRP 3.2.1-1 (twrp_3.2.1-1_T825_28518.tar) in my tablet is working with no problem and with data mountable. I just followed the instructions in the OP.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ww100100101:
[MENTION=4899305]ashyx[/MENTION] i really don't know what different i did this time around :(
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Is your current firmware BRE2?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
It seems only some T825 owners are having an issue.

Do any of the builds in the OP boot?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] fates13:
I followed instructions and it's working fine on 820. Thanks!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Jsilver73:
Update - I got root by reflashing the patched boot.img in recovery then flashing magisk 16.4 straight afterwards.

Previously I had flashed the boot.tar in Odin so I'm thinking maybe this is where something went wrong, I noticed when I first flashed magisk it reported 'stock boot.img' detected, when I reflashed the patched boot.img from twrp just now and then flashed magisk it reported 'found boot.img'

IDK -and I was stupid tired last night, just sharing my experience in case it might help someone else.

Many thanks [MENTION=4899305]ashyx[/MENTION] for your brilliant work in helping us to free our devices from the shackles of the evil overlord 'samsuck' ;):D
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
I just wanted to follow up on this, just in case anyone else runs into the same issue.

I'm still not sure what has happened here, to be honest.

The T820XXU1BRE2_T820OXA1BRE2_BTU.zip firmware I flashed is a multi-CSC package, but the OXA bundle doesn't include PHN (generic Netherlands). What I thought I knew about multi-CSC packages dictates that this should have had the effect of changing my active CSC to the package default of BTU. Instead, however, it left me without any active CSC. And this, in turn, seems to have had the odd side-effect of enabling by default a couple of Korean options in my Settings menu, plus a duplicate entry for Battery.

I tried to remedy the situation by reflashing the OXA HOME_CSC file with Odin, but to no avail. Still no active CSC.

Checking SamMobile, I saw that the actual Oreo firmware for PHN (T820XXU1BRE2_T820PHN1BRD7_PHN.zip) was now also available. Sigh. I should have checked that before flashing anything yesterday, and avoided the OXA firmware entirely. Oh well.

So, I downloaded the PHN firmware and flashed the HOME_CSC file from that. Still no dice, probably because HOME_CSC_PHN_T820PHN1BRD7_CL13486246_QB17886296_REV00_user_low_ship_MULTI_CERT.tar.md5 has a lower version number (BRD7) than HOME_CSC_OXA_T820OXA1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT.tar.md5 (BRE2).

I thought I might be able to force application of the BRD7 PHN CSC by extracting sec_csc.zip from it and flashing that directly with TWRP. Alas, no such luck. Still no active CSC.

With all other options exhausted, I bit the bullet, made a TWRP back-up of /data, and then went back to Odin to flash the full PHN firmware, making sure to use the CSC file instead of the HOME_CSC. As expected, this caused a full reset of the device, which I reasoned was now necessary in order to downgrade the CSC from BRE2 to BRD7.

I then reflashed TWRP and T820XXU1BRE2_dmverity_patched_boot.tar (after verifying that the boot.img inside the PHN firmware was identical to the one in the OXA firmware, so would work with Ashyx's patch), rebooted to TWRP, reformatted the now encrypted /data file system, rebooted back to TWRP, reflashed Tabs3_oreo_forced+encryption_disabler.zip, reflashed Magisk, and then finally restored /data from my back-up.

Half an hour later, I rebooted to system and... drum roll... still no active CSC! And so still the bogus menu entries in Settings!

I've spent a fair amount of time on this problem now and I'm not sure what else I can try, or whether it's even worth the bother. Perhaps when a future PHN firmware update becomes available that includes a CSC with a later version number than BRE2, it'll stick when I apply it. Who knows?

Unless anyone has a golden tip, I think I'll have to resign myself to living with this small issue for now. As far as I can tell, it's more or less cosmetic and there's no practical disadvantage.

I just wish I understood why flashing that OXA firmware yesterday left me without any active CSC instead of the package default of BTU.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Sorry to follow up on myself again, but I've finally fixed this problem.

I was really close when I carried out the above step, but I had failed to understand a small implementation detail that turned out to make a world of difference.

The META-INF/com/google/android/updater-script installation script from sec_csc.zip inside the HOME_CSC file installs its payload of files in /system, but doesn't actually mount /system first.

In TWRP, at least, this has the effect of installing the files onto TWRP's ramdisk. After a reboot, they're gone, of course. Presumably, /system gets automatically mounted when Odin is used, and so no explicit mount is required in the installer script. Although, if you've read my previous epistle, you'll know that Odin didn't work for me, either; but that's possibly because Odin doesn't even get as far as extracting sec_csc.zip from the HOME_CSC file if it determines that the HOME_CSC staged for flashing has a lower version number than the one already installed.

Anyway, as is so often the case, the solution is simple once you actually know what the problem is: Just manually mount /system in TWRP prior to flashing sec_csc.zip. Then the files will actually make it onto the device and stick around after a reboot.

Sure enough, after booting back to Android, the device reports Finishing Android installation and then finally comes up with PHN as its active CSC, specifically T820PHN1BRD7. The bogus Korean entries are gone from Settings now, too, along with the duplicate Battery entries.

This has been quite the learning experience. I thought I knew a little bit about Android devices and flashing, but my understanding is much improved now.

If I could give other non-pro users a tip, it would be to unpack the stock firmware files some time and go browsing through them to see exactly what's in there, and how it all gets installed when you flash it.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Sec_csc.zip boots the device to stock recovery which mounts system to finish the update. That's what the updating message is about when ODIN reboots to recovery after installing a full firmware package.

If you didn't have stock recovery installed at the time this is why it initially failed.

Just to note, its appreciated that you take the time to post details and the fix.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Tried again with a clean install. But recovery doesn't boot on T825.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Did you use the same build or download the one in the OP?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Yes, downloaded the build from the OP. TWRP never boots. Stuck on booting in recovery.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Very interesting. Thanks.

Yes, I flashed Oreo, TWRP and the forced encryption disabler one after the other in Odin, rebooting to download mode each time. I didn't realise that the CSC component of the firmware flash doesn't actually occur until the device is allowed to properly reboot, by which time I had rendered this stage impossible to complete by throwing TWRP over the top of stock recovery.

That's valuable information. So, you must allow a reboot after flashing new firmware (at least when it includes a [HOME_]CSC file) and before installing TWRP. Or you must make arrangements to flash the embedded ZIP yourself later on. Otherwise, you'll end up with a device that experiences an identity crisis, as I did.

Someone, I've managed to get this far without learning that. You can be sure I shan't forget it now, though. Thanks very much for this vital insight. Whenever I've seen that post-flash Updating message after installing a new device, I've always believed it was coming from a post-boot script left somewhere on /data, and then deleted afterwards. I didn't realise that the device is actually in recovery at that point, and busy flashing a file I had thought already flashed in Odin.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Ok, could you try both of these builds?

https://androidfilehost.com/?fid=674106145207490150

https://androidfilehost.com/?fid=890278863836288534

.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Will do later today. But now off to work.

Verstuurd vanaf mijn SM-T825 met Tapatalk
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Well I didn't do a clean install but for me both versions now boot to recovery. So they both work. Really don't know the difference between both.

:highfive::highfive::highfive:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Ah good stuff.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] vogemic:
Also did a clean install. Used test version 1. Recovery is up and running and device is decrypted.

Verstuurd vanaf mijn SM-G955F met Tapatalk
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] lisboapcs:
Yes I am on BRE2
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
[MENTION=4899305]ashyx[/MENTION] i was able to root my T825 , thank you very much for all your help and support..

there's this one thing i would like to point out, the link in Firt post for Recovery of T825 is for twrp_3.2.1-1_T825_29518 .. that file has no extension, i had to rename it to twrp_3.2.1-1_T825_29518.tar .. .tar extension is missing in the downloaded file ... its not a biggie but just lettin u know...
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Whoops, corrected thanks for pointing it out.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
[MENTION=4899305]ashyx[/MENTION] will it be possible for you to make a dm-verity patch for BRE3 firmware? BRE3 supports VOLTE calls natively while BRE2 doesn't.. Most of the cellular operators in my country (INDIA) uses VOLTE.. Since I'm on BRE2, I've to install 3rd party apps for making VOLTE calls and these apps asks for all sorts of permissions.. I don't know how difficult it is to make a dm-verity patch, so pls excuse me if am asking for too much..

I've the BRE3 firmware downloaded, so I will be able to give you any files you might require..

Once again Thank you very much for all the help and support you are giving us..
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
It might be (and probably is) just a question of editing the relevant CSC XML file in your existing firmware to enable native VoLTE, in the same way that many root users have had native Samsung call recording for years, whilst not-root users in many regions are only getting it now (or not at all).
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Why not just flash the CSC from the latest firmware and see if it enables it or just flash the whole firmware then the BRE2 kernel?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
I flashed indian CSC over BRE2 but it always reverted back to BRE2 CSC :confused:

I'll try flashing BRE2 kernel over Full Indian firmware and report back...

[MENTION=7187684]ianmacd[/MENTION] I couldn't find the relevant csc modification command for enabling VOLTE.. I'll search more.. Thanks :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
It would usually be this:

<EnableVoLTE>true</EnableVoLTE>

and it usually goes in customer.xml under the stanza for your particular provider. Search your device for it.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
Unfortunately my carrier "Jio" is not there under that list.. Its the CSC for Britain, maybe that's why.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
You should be able to make the same modification for the active CSC that you're currently using.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
sent u a direct message.. hope its ok
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
Is kernel and boot.img the same? If it is, then I should be able to flash it using twrp, don't I?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
The kernel is part of the boot.img.

You can flash with odin or twrp.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
i worked.. thank you so very much.. now i have root and VOLTE :)

Just in-case if anyone else wants to do it

1)flash BRE2 firmware, install TWRP by following the steps mentioned by [MENTION=4899305]ashyx[/MENTION] and extract boot.img and save it to ur ext card

2) Flash BRE3 firmware, install twrp , twrp install flash boot.img which we extracted previously and then flash T825XXU1BRE2_dmverity_patched_boot.tar provided by Ashyx in the first post and continue to follow the steps in First post .. :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Step 1 isn't necessary, just go straight to BRE3 firmware.

No need of extracting and saving boot.img.

Just flash the T825XXU1BRE2_dmverity_patched_boot.tar after installing BRE3 firmware.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] sadebash:
where can I find BRE3 firmware please? All I can find is BRE2.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] TheGoD:
Does Xposed work with this root method? What about Xposed and Magisk together?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] jaidev.s:
Wow, never knew. Now its way more easier. Thanks for the information [MENTION=4899305]ashyx[/MENTION]

---------- Post added at 20:36 ---------- Previous post was at 20:34 ----------

It's available only for T825 version..

here's the link

https://updato.com/firmware-archive-select-model?record=9D40BB535BE911E89F15FA163EE8F90B

---------- Post added at 20:37 ---------- Previous post was at 20:36 ----------

Yes and yes :)
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Magisk has its own systemless xposed. Just install from the manager.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bonanza123:
Sorry if that has alredy been asked:

I'm flashed your TWRP including the T825XXU1BRE2_dmverity_patched_boot and Tabs3_oreo_forced encryption_disabler patches. All worked fine, in the sense that I flashed Lineage 15 and booted without problems.

I then wanted to encrypt the data partition (from within the system settings of lineage). Since then, the tablet is boot looping. I suspect that this has something to do with the above mentioned patches. Is that possible? What do I have to do to get android/lineage encryption working again?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
I'm surprised it even booted after flashing the patched boot as it's the stock kernel.

You probably need to flash lineage again.

You don't need any of the patches, lineage doesn't have any of this dm-verity and encryption nonsense so they are not needed.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bonanza123:
Thanks for your fast reply. I actually applied the patches before flashing lineage (because flashing failed due to missing access to DATA partition).

Can I consider last two patches to be reverted after flashing lineage again?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Boot twrp, format data, flash lineage.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] bonanza123:
Thanks, the point I don't understand: How does that differ from the state I had before enabling encryption in lineage?

Or do you think the boot looping is not related to the two patches (because I flashed lineage after these patches)?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
If you flashed lineage after the patches this should in theory remove the patches.

However it's important to format data prior to flashing lineage.