yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] tigerpuffs:
Wow, a lot has changed!

Hi!

I recently bought a Tab S3 and haven't rooted anything since doing my Note 2 several years ago, so I'm very out of touch on the issues of rooting. I've spent the last week trying to read up on the current issues, but there's a lot there and I wanted to make sure I wasn't missing anything. I was hoping someone could take a bit of time and give me some updated info about rooting.

I read something about Netflix and Amazon Prime Video problems with encryption?

Is this not an issue with magisk?

Are there other issues I should know about?

Are there pros and cons to android 7 vs android 8? My tablet is bugging me to update to BRE1, but I didn't want to do it if there's big cons to android 8.

I'd love to root my tablet and get a working firewall and ad blocker and all the other wonderful things rooting allows that my phone has, but if it is going to make Netflix or Prime Video break, that might be a deal breaker for me, since that's one of the big reasons I bought a tablet.

Thanks in advance for taking the time to read and hopefully help me! And thanks ashyx for all the help you've given on this forum, it makes rooting much more approachable to noobs like me!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] retikulatus:
Awesome post!

Do do recommand a particular (country) firmware or is it just as you mention, any AQD6 or later ones?

Doesn't a too recent firmware compromise the root and custom rom install?

Do i really need to backup if i have a stock firmware at hand?

if i want to install a rooted lineage rom, do i have to follow all the step on the first post (with the dmverify stuff) or is it is not required anymore?

Thank you for your work and advices, Ashyx.

kind regards from France
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] namitutonka:
Differences between UK and US T820 file size in CSC

United States (XAR) oreo 8.0.0

https://updato.com/firmware-archive-select-model?record=5E5494E9655911E89F15FA163EE8F90B

No signup required

SM-T820_1_20180523135714_8qsl9aro0u_fac.zip (T820XXU1BRE2) 2.6 GB, 6 minute (free) download

AP_T820XXU1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT_meta.tar.md5

5/23/2018 3,064,551 KB

BL_T820XXU1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT.tar.md5

5/23/2018 16,181 KB

CSC_XAR_T820XAR1BRE1_CL13537284_QB17987615_REV00_user_low_ship_MULTI_CERT.tar.md5

5/23/2018 86,401 KB

HOME_CSC_XAR_T820XAR1BRE1_CL13537284_QB17987615_REV00_user_low_ship_MULTI_CERT.tar.md5

5/23/2018 86,391 KB

====================

United Kingdom - oreo 8.0.0

https://www.sammobile.com/firmwares/galaxy-tab-s3/SM-T820/BTU/download/T820XXU1BRE2/218679/

Requires signup

T820XXU1BRE2_T820OXA1BRE2_BTU.zip 2.5 GB, over 2hr. (free) download

AP_T820XXU1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT_meta.tar.md5

5/7/2018 3,064,551 KB

BL_T820XXU1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT.tar.md5

5/7/2018 16,181 KB

CSC_OXA_T820OXA1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT.tar.md5

5/7/2018 51,481 KB

HOME_CSC_OXA_T820OXA1BRE2_CL13482624_QB18016528_REV00_user_low_ship_MULTI_CERT.tar.md5

5/7/2018 51,471 KB
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
[MENTION=4899305]ashyx[/MENTION], if you wouldn't mind, could you explain exactly what has changed from stock in the patched boot image above?

I've unpacked your boot.img and compared with stock, but the only differences I can see are that the file verity_key has been removed from the ramdisk, and the file boot.img-dtb has changed, even though the kernel remains untouched.

Can you please detail exactly what changes you made to the stock boot.img?

The reason I ask is that I have compiled a custom kernel for the T820, but I can't currently get it to boot. I'm using your patched boot.img as the basis, replacing the boot.img-zImage kernel in that, and then repacking (using AIK). This is what I've done on other devices and it works there, but I suspect that I also need to do something with boot.img-dtb, but my kernel build isn't producing a replacement for that.

Thanks in advance.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
The only real change is in the DTB which now has the FSTAB flags for the system partition as per Google's instructions for Oreo.

You'll notice no FSTAB in the Ramdisk any more.

This means to disable dm-verity it must be done in the DTB.

Also as you've noticed the verity key has been removed.

Tbh if all you've done is replaced the zImage it should boot.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] namitutonka:
Yay! My warranty is void. :)

DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

The above is a donate to ashyx! :silly:

Never thought I'd be glad to have a warranty on an almost new device voided, but thanks to you [MENTION=4899305]ashyx[/MENTION], I'm enthused. My SM-T820 is much more mine now than it was. :highfive:
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Yes, I did notice there was no fstab any more, and I couldn't figure out why! I assume you just hacked the DTB with a binary editor.

The last time I did serious Linux kernel work was in the early 2000s, and DTBs didn't exist back then. Clearly, my knowledge is lagging and I need to do some reading.

Yes, all I did was download the Samsung kernel source from Samsung's own site, unpack it, and recompile it with the defaults. It does compile, but isn't yielding a working kernel. I wasn't sure whether the kernel itself wasn't quite right, or whether it was being neutralised by external factors, but with dm-verity gone, I wasn't sure what might be left.

Anyway, thanks for your explanation. I'm going to read up on DTBs now.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
With each OS release kernels seem to get more and more difficult to build successfully.

Especially with all the added security that keeps being added.

If it's not booting then it could be an selinux issue. In my experience Samsung don't always release the exact source used in the stock binary, but some bodged version just to keep the GPL happy.

Try building as permissive.

Might also be worth pulling the last_kmsg to see to see if it gives any clues.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Orbital_Logic:
Is it just me or does the download keep hanging at 77%
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] namitutonka:
N/A
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Orbital_Logic:
In the US, trying one more time..3rd times the charm. It's at 75% saying 2 min left... let's see if it completes...damn... hung at 77% again. I have plenty of space... I'll try a different browser then PM you.

[Edit: downloading from desktop.. using edge browser on my tablet--getting those points racked up lol --which I'm not super familiar with, max download?? I dunno, seems to be working okay on kde desktop firefox...its coming in at 7.8MBps so.. /Edit]

--came in fine on the desktop.. thanks
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Thanks for these tips. It feels like trying to shoot a moving target whilst wearing a blindfold. I'll give it another shot today.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Kosgi:
Hi,

I'm trying to root the SM-T820 following the instructions in the OP but want some clarifications.

I understand the first set

What am I supposed to do once I see TWRP recovery?

More importantly, I want to root so I can try to recover lost data due to a factory reset. Does that mean that I need to follow the next set of instructions to disable verity, encryption and mount data? I presume that 'mount data' is something I'll need in order to connect the tablet to my pc and run data recovery software, correct?

If so, I believe I need to do some things before I start with the TWRP process.

The process to disable verity says:

Does 'boot to TWRP' mean the TWRP recovery screen as per the last step of the 1st set of instructions?

I need to do step 2 through that screen?

As for step 3, do I check it simply by connecting my tablet by usb to my pc and see if it sees the internal storage?

As for steps 4 & 5, install SuperSU and boot image, when do I do those? Do I install SuperSU before I even start the first set of the process or can I install it after? and how?

also, by install boot image, how do I do that?

If anyone can help a bit to explain how I go from the TWRP recovery screen to apply the verity disabling in a bit more detail it'd be helpful.

Thanks in advance.

EDIT: I plan on doing this for Android 7.0. I'm just interested in trying to recover my data.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] pocketrussian:
Hi,

I have an unrooted S3 running Oreo. I would like to temporarily root the tablet in order to de-bloat the firmware and install Nova launcher in the priv-app directory. After that I would like to unroot the tablet and re-enable dm-verity and forced encryption for security reasons. Is this possible and what would be the steps involved to unroot and re-enable dm-verity and forced encrypt?

Thanks in advance!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
If that's all you want to do, my opinion is that the benefits are not in proportion to the hassle of what you propose; assuming that you even complete the operation flawlessly, because it's a delicate one that can easily go awry if you forget a step or misinterpret an instruction.

If I were you, I would use pm uninstall to debloat without root, and simply forget about installing Nova as a privileged app.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Agreed, don't see the point in making Nova a priv app.

As for debloat, this can be accomplished with Samsung package disabler or BK package disabler.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] pocketrussian:
Thanks [MENTION=7187684]ianmacd[/MENTION] and [MENTION=4899305]ashyx[/MENTION] for your reply. You likely saved me a ton of hassle! I didn't realize I could just do a pm uninstall without root (my previous tablet was a Fire HD 10 and Amazon has disabled this feature in later firmware).
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] namitutonka:
TWRP working on T820

I'm running the updated twrp on oreo. I now have a full backup on my SD card.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Zimus:
Please forgive my ignorance but I have been out of the ODIN flashing game a little too long... I'm confused about this step for installing the T820XXU1BRE2_dmverity_patched_boot.tar file via ODIN:

Under which button/section do I load this TAR file in ODIN, is it AP (like for TWRP) or BL since it contains boot.img?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] rorymc928:
Put the file in the AP slot, then go from odin direct to TWRP to flash the no verity no encrypt zip
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
Good question. I understand the confusion.

The boot loader is the thing that bootstraps the device, allowing it to boot to recovery, download mode or the operating system.

In the case of the operating system, the ramdisk from the boot.img that you previously flashed is mounted, control is passed to init, and the system boots from there. Because boot.img is part of the operating system, it goes in the AP slot. The BL slot is reserved for the boot loader itself, which is a lower level piece of code.

To add to the confusion, if you're flashing a boot.img in TWRP, you do need to select the boot partition. That's not the same place as where the boot loader lives, but you could be forgiven for thinking that. The similarity in nomenclature for different concepts across the various environments is lamentable, and has probably caused its fair share of catastrophes over the years.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Tbh it does not matter.

ODIN is savvy enough to flash it to the correct partition whichever is used.

AP can be used for flashing any image.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] rorymc928:
Nice to know, good gen ?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Zimus:
Excellent - good to know. I had always been rather cautious with Odin out of fear of flashing something incorrectly. I'll still continue to be careful of course, but worry a little bit less :good

One last thing, as you can tell from my signature I am woefully behind on updates with my Tab S3 (it's rooted and I've been happy enough with it that I never bothered with updating and re-rooting). Would it be safe to jump directly from Nouget/AQBB to Oreo/BRE2? Or should I flash the intermediate Nouget updates (AQBB -> AQDC -> AQF3 -> AQI2 -> etc) first?

Thanks again!

---------- Post added at 18:41 ---------- Previous post was at 18:38 ----------

Awesome - thank you for the detailed breakdown, I truly appreciate it. You've certainly cleared up some confusion for me!

---------- Post added at 18:43 ---------- Previous post was at 18:41 ----------

Thank you!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
It's fine to go direct.

Samsung firmwares are complete and not consecutive like ota's.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
We're all still learning. I didn't know either that Odin was smart enough to do the right thing if you tried to flash a BL in the AP slot or vice versa, so thanks to [MENTION=4899305]ashyx[/MENTION] for that.

Incidentally, don't assume that TWRP will be just as helpful if you try to flash, for example, vendor.img to the boot partition. Maybe it will, but I suspect it won't. For that reason, I would advise maintaining good habits with Odin, too, just to keep clear in your head where each flash will end up; so that when you use software with no built-in safety net, there's less chance of a mishap there, too.

Also already answered by [MENTION=4899305]ashyx[/MENTION], but I just wanted to add that I did almost exactly what you're doing and everything went fine (other than that I temporarily lost my active CSC, but that is detailed elsewhere in this thread, along with the cause and its ultimate remedy).
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] Zimus:
Awesome - thanks again!

---------- Post added at 23:39 ---------- Previous post was at 23:15 ----------

I'm even more cautious w/in TWRP, if it's not a ZIP (which I assume has some sort of manifest telling TWRP what to do) I try to avoid installing it if at all possible :) There are so many more partitions now (at least compared to Kit Kat & Lollipop or even Marshmallow) that I barely know my way around anymore - I just back them all up and hope I never have to restore anything.

Thanks again for all of the help, I really do appreciate it!
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] OPO13R:
It worked!! Thank you so much for your effort to bring TWRP to the S3, at last.

Btw: I found it a LOT easier to boot to recovery right after flashing TWRP to the AP slot via ODIN, by selecting "Auto-Reboot" and NOT getting overwhelmed by doing 2 key combinations one right after the other one. I always missed the right timing.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DeHAWK:
Hey bro

If you have a device tree problem, you will never get past the bootloader screen. The Bootloader hands over the right dtb to the kernel. The kernel will then take over and boot the device, you will then see the boot animation. Just a minor dtb problem will show up as you describe. As I see it, this seems to be a dtb problem. Personally I was able to boot a Nougat system on the Oreo bootloader, this using an insecure kernel I made for the experiment.

Regards

DeHAWK
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
The stock boot.img contains a boot.img-dtb, but the kernel source as supplied by Samsung doesn't build one. To be honest, I don't know where to go from here. There are some kernel build options concerning the concatenation of the DTB with the kernel, but those don't seem to be relevant here.

Lots of DTBs do get built as part of the build process, but nothing appears to get done with them. No dtb.img gets built.

If it's sounding as if I'm out of my depth, it's because I am. I would love to learn more about this, but am not sure where to go from here.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DeHAWK:
Hey bro

I'll be back with more help for you later. Watching football....:)

Regards

DeHAWK
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
The dtb that gets built as part of the kernel build should be exactly the same as the stock dtb as long as the source and stock kernel share the the same build number.

If you want to build the dtb I can tell you how to do it, but it won't make any difference if it doesn't boot with the stock dtb.

I'm assuming you've tried with the stock dtb?
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] DeHAWK:
Hey bro

Below is two Linux functions I use in my build script:

First is the building of the dtb files, I called it: FUNC_APPEND_DTB

ATTENTION:You MUST make the required changes to make it fit your build script. I've the SM-T825.

#!/bin/bash

DTB_PADDING=0

DTS_FILES="msm8996-sec-gts3llte-eur-kor-r00

msm8996-sec-gts3llte-eur-kor-r02

msm8996-sec-gts3llte-eur-kor-r04

msm8996-sec-gts3llte-eur-kor-r05"

echo ""

echo "================================="

echo "FUNC_APPEND_DTB - START "

echo "================================="

echo ""

if ! [ -d $BUILD_KERNEL_OUT_DIR/dtb_building ] ; then

echo "ERROR no directory : "$BUILD_KERNEL_OUT_DIR/dtb_building found.""

echo "Creating directory : "$BUILD_KERNEL_OUT_DIR/dtb_building""

mkdir $BUILD_KERNEL_OUT_DIR/dtb_building

#exit -1

else

echo "Removing old .dtb & .dts files: $KERNEL_DTB_FILES/*.dtb *.dts"

rm -f $KERNEL_DTB_FILES/*.dt*

echo "Removing old dtb.img: $INSTALLED_DTIMAGE_TARGET"

rm -f $INSTALLED_DTIMAGE_TARGET

fi

for DTSFILE in $DTS_FILES; do

echo "=> Processing: ${DTSFILE}.dts"

"${CROSS_COMPILE}cpp" -nostdinc -undef -x assembler-with-cpp -I "$BUILD_TOP_DIR/include" "$DTS_DIR/${DTSFILE}.dts" > "$KERNEL_DTB_FILES/${DTSFILE}.dts"

echo "=> Generating: ${DTSFILE}.dtb"

$OUTPUT/scripts/dtc/dtc -p $DTB_PADDING -i "$KERNEL_DTB_FILES" -O dtb -o "$KERNEL_DTB_FILES/${DTSFILE}.dtb" "$KERNEL_DTB_FILES/${DTSFILE}.dts" #> /dev/null 2> /dev/null

done

echo "================================="

echo "FUNC_APPEND_DTB - START "

echo "================================="

echo ""

-----------------------------------------------------------------------------------------

Next we must make a dt.img file, using the above compiled files.

I called the function: FUNC_BUILD_DTIMAGE_TARGET

#!/bin/bash

echo "================================="

echo "FUNC_BUILD_DTIMAGE_TARGET - START"

echo "================================="

echo ""

echo "Building the DT-image file..."

echo ""

echo "Target DT-image will be in: $INSTALLED_DTIMAGE_TARGET"

rm -f $INSTALLED_DTIMAGE_TARGET

$DTBTOOL -o $INSTALLED_DTIMAGE_TARGET -s $BOOT_IMAGE_PAGESIZE \

-p $DTC $KERNEL_DTB_FILES/

chmod a+r $INSTALLED_DTIMAGE_TARGET

echo ""

echo "================================="

echo "FUNC_BUILD_DTIMAGE_TARGET - END"

echo "================================="

echo ""

The above will then build the dt.img file.

Later in your build, your must use the mkbootimg as follows:

mkbootimg --kernel "$KERNEL_IMAGE_NAME" --ramdisk "$BUILD_KERNEL_OUT_DIR/ramdisk.cpio.$compext" --cmdline "$BOOT_IMAGE_CMDLINE" --board "$BOOT_IMAGE_BOARD_NAME" --base $BOOT_IMAGE_BASE --pagesize $BOOT_IMAGE_PAGESIZE --dt "$INSTALLED_DTIMAGE_TARGET" --kernel_offset $BOOT_IMAGE_KERNEL_OFFSET --ramdisk_offset $BOOT_IMAGE_RAMDISK_OFFSET --second_offset "$BOOT_IMAGE_SECOND_OFFSET" --tags_offset "$BOOT_IMAGE_TAGS_OFFSET" --os_version $BOOT_IMAGE_OSVERSION --os_patch_level "$BOOT_IMAGE_OSLEVEL" --hash $BOOT_IMAGE_HASH --output $BUILD_KERNEL_OUT_DIR/boot.img

Hope it gives you a hint....

Regards DeHAWK
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
I actually hadn't tried with the stock DTB, because I knew you'd patched it, so I knew I'd need your patched version to avoid grief from dm-verity.

However, if the stock DTB were to work, that would be worth knowing and help localise the problem, so I just tried it. Sadly, my kernel won't boot with that version, either.

At this point, the only difference between my boot.img and the stock one is the kernel binary itself. I suppose there's just something really not right about what I've built. My binary is about 630 Kb smaller than the one that Samsung purport to have produced from these sources, so that's close enough to be explained away by differences in the tool chain. Other than that, I see no difference.

Oh well, none of this has anything to do with TWRP, so I apologise for taking up time and space here. I was keen on cautiously starting a custom kernel for this device and adding a couple of extra features to it, but I can't even get to stage one with it. Back to the drawing board for me. Maybe I should just start from scratch again and double-check every step along the way. I don't think I did anything wrong, and the fact that the kernel does build using Samsung's instructions reinforces that belief, but, well, if it don't boot, it ain't no good.

Thanks for the patience and hand-holding, [MENTION=4899305]ashyx[/MENTION]. I do appreciate it. And I especially appreciate having rooted Oreo on my T820. This is the config this device has always deserved, and thanks to your perseverance, we all have it now.

---------- Post added at 21:37 ---------- Previous post was at 21:29 ----------

Thanks for these, mate. These scripts will be of use to me when I trace the source of my problems, which I'm now thinking isn't DTB-related at all.

I think it's time for me to start from scratch again and scrutinise every step of the process.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
Just looking at the kernel log you posted. Are you sure this is from the custom kernel boot? It doesn't seem so.

See the error below it states booting to Recovery. Also the kernel version is AQF3.

[926:bootstrap2] <LP> RECOVERY BOOTING..... [1032: idle] Return value from recv_data: 14 [1033: idle] Return value from recv_data: 14 [1034: idle] Return value from recv_data: 14 [1160:bootstrap2] ERROR: Image Invalid! signature check failed

You need to boot with your kernel, leave it alone for a minute then reboot to recovery and save the last_kmsg.

You can also use this one liner run from the kernel build directory to build the DTB after compiling the kernel:

tools/dtbTool -s 2048 -o arch/arm64/boot/dt.img -p /$(pwd)/scripts/dtc/ arch/arm64/boot/dts/samsung/

Compiled DTB will be in /arch/arm64/boot/dt.img

I don't use MKBOOTIMG directly to build the boot image I use AIK. Much easier to unpack the boot image replace the zImage and DTB then repack.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ianmacd:
I booted to my kernel, waited about 45 seconds at the stuck bootloader (i.e. the screen with the device name, not the flashing Samsung logo that would follow if control had successfully been passed to the kernel). then rebooted to TWRP and ran

adb shell cat /proc/last_kmsg > kmsg.txt

on my laptop. The output is what you saw here.

I, too, noted the reference to AQF3. It raised my eyebrow, but I thought that was probably due to something you'd done with the boot.img (remember I was using your dm-verity hacked image as my base), or coming from some code that had been compiled into TWRP itself. This was the first time I'd ever dumped last_kmsg on an Android device, so I assumed that anything that appeared odd to me almost certainly had a logical explanation.

Thanks for the one-liner. I will try it.

Yes, I also use AIK, because it borders on the foolproof. Unpack, copy a file or two into place, repack, adb push, flash and reboot. It really doesn't get any simpler.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] ashyx:
So that means that maybe the kernel isn't booting at all as it's only pulling the last_kmsg from recovery.
[Samsung Galaxy Tab S3 ROMs, Kernels, Recoveries, &] QuattroPower66:
Hello,

I want to root my Samsung Galaxy Tab S3, SM-T825, Android 8.0.

R16nw.t825xxu1bre2

Can i root on this Stock version?