yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S7 FE] t0urista2:
Hi

what I can suggest :

+ download the correct firmware from Frija, then repeat the various steps,

+ but skip the steps 9 to 13, so do not patch the boot.img with Magisk on the tablet, you will not be abble to do so anyway.

+ add a step 13b where you tar the genuine boot.img thta you've just extracted with lz4

+ then apply step 14 where you push again the genuine boot.img to the table with Odin. that's the most tricky part, if this fails you're stuck.

if it works you get a new and genuine tablet...

and you can repeat the full process to root it, but this time with the correct firmware !!!;-)
[Samsung Galaxy Tab S7 FE] avemt1:
I got the correct firmware with Frija. Forst time Frija user. I thought auto meant detecting the device, but it doesn't. ¯\_(ツ)_/¯

I just installed the AP file in whole, and restarting the process otherwise.

It worked, and I now have root.

I hope other people get help form this post.
[Samsung Galaxy Tab S7 FE] Pheaa:
Anyone has the boot.img file for THL devices? Because yeah My internet will die if I download something at 5gb
[Samsung Galaxy Tab S7 FE] Blombardo:
public service announcement This thread appears to be for NON US variants.

Tab S7 FE 5g sm-T738U rev .38 -- the US version has no way to unlock bootloader... once again the 'free' country is less free than others in the world...​

Thx to afaneh92. No more US variants for me.. waste of money... lol

If anyone finds a way to do the US one I'd appreciate being tagged!
[Samsung Galaxy Tab S7 FE] Blombardo:
Can someone offer up an exact model number that can have bootloader unlock? As in - likely - an overseas variant?

Or is there any possible trick to changing firmware on a US 5g version to make it an overseas version so it can get the unlock bootloader option?
[Samsung Galaxy Tab S7 FE] Awesomeslayerg:
i have the wifi us version not the 5g version
[Samsung Galaxy Tab S7 FE] Sam9938:
Anyone have any issues with Samsung Care claims with a unlocked bootloader/rooted tablet? Wanted to root it but don't want to compromise my protection plan.

EDIT: NVM, I see clearly on the device after I unlocked the BL that the warranty is void.
[Samsung Galaxy Tab S7 FE] Datblkbro:
You can always flash back the stock firmware using ordin. I wanted android 13 so I Uninstalled Magick and flash original firmware. It lock my bootloader back. Also I was able to Ota update to android 13
[Samsung Galaxy Tab S7 FE] Phoost:
Did you try to root stock Android13 firmware afterwards? I have a rooted A12 and would like to update to 13 but need root again.
[Samsung Galaxy Tab S7 FE] Datblkbro:
No I haven't yet but from what I read it's the same steps as A12
[Samsung Galaxy Tab S7 FE] Tofor:
If you have the SM-T738U that is from T-Mobile then unfortunately no you cannot root your device. the SM-T738U does not have the option to unlock the bootloader in the developers menu. This option is being blocked by T-Mobile. No bootloader unlock means no root. i had a tablet i got from metro pcs a while ago that also did not have this option, but the option appeared after i did the network unlock. maybe try your network unlock and if you succeed with that look again to see if it appeared. this is doubtful but worth a try.
[Samsung Galaxy Tab S7 FE] Arilan:
I purchased a samsung s7 FE 128gb from best buy the other day. Updated it to One ui 5.1 Android 13... went straight to Dev options to see if I can check on OEM unlocking and sure enough it does work :)

can't wait to see what options we have for roms
[Samsung Galaxy Tab S7 FE] hpc305:
if you dont mind me asking,what model # is your tab? thanks
[Samsung Galaxy Tab S7 FE] lewmur:
By "patch AP", do you mean "put the boot.img.tar into the AP slot and click start"?
[Samsung Galaxy Tab S7 FE] lewmur:
I just bought an S7 and it has Android 13. I'm assuming this will still work with 13 but has anyone tried it?
[Samsung Galaxy Tab S7 FE] Typhoon_Master:
I uninstalled Magisk too, but now I am stuck in a bootloop.

I am not able to enter download-mode or recovery-mode, by pressing any Buttons.

It just goes from: "Attention Bootloader is Unlocked, press Powerbutton" --> "Samsunsg Galaxy Secured by Knox, This Tablet is not running official software" --> Black Screen --> Back to first Screen (Bootloader).

Any idea what I could do?

//edit: I just managed it to go into recovery somehow with button pressed after black-screen. (I don't know why it did not work prior) ... where can i find the firmware to flash with odin?

//edit2: damn, i cant boot into download mode... neither from recovery nor with buttonpress

//edit3: ok working now. download mode is "vol up + vol down" keys. i did it wrong as i was used power + vol down from other devices
[Samsung Galaxy Tab S7 FE] lewmur:
I can confirm that this does work with the latest Android 13 ROM. I'm up and running with root access.
[Samsung Galaxy Tab S7 FE] XLQ:
which model do you have? I have the SM-T733 model and wondering if that can be rooted?
[Samsung Galaxy Tab S7 FE] lewmur:
That is the model I have and it is rooted.
[Samsung Galaxy Tab S7 FE] Typhoon_Master:
This is also the model i have and it is rooted with Android 13.

Can we get rid of the warning messages at the beginning of the boot sequence?
[Samsung Galaxy Tab S7 FE] XLQ:
Thank you guys. Time to tinker around 😀
[Samsung Galaxy Tab S7 FE] idowens:
I recently purchased an SM-T733NZKAXAR from BB. I've successfully unlocked the BL, but when I try the Magisk patch and Odin flash, it passes (green mark) but root isn't achieved.

I've rooted dozens of phones in the past, usually via adb CLI, but never a Samsung.

A major concern I have is, my Service Provider software version reads:

SAOMC_SM-T733_OXM_XAR_13_0002
XAR/XAR

When I pop T733 / XAR into BiFrost (I'm a Mac user with WIn 10 & 11 running on VM), it returns a match for:

T733XXS3CWD1/T733OXM3CWD1/T733XXS3CWD1/T733XXS3CWD1

Is this truly a mismatch in my version (Android 13, One UI 5.1, Security Patch May 1, 2023) or is that the correct version and the glitch is between the keyboard and the seat? :) I had no idea this was so notoriously convoluted to root or else I'd have gone in a different direction. I need a simple 13" (ish) tablet for use as a seat-back entertainment system. The ultimate goal is using Tasker to turn the device on & off when the car turns on & off but I need root access to control power that way.) I'm well within the return period so I could always move to a different device.

As always, TIA.
[Samsung Galaxy Tab S7 FE] lewmur:
Did you run Magisk again after rebooting? Root isn't there until you do.
[Samsung Galaxy Tab S7 FE] idowens:
If it had been a snake, it would have bit me.

That's the obvious step that I missed. Not having used Magisk before, I wasn't sure how it worked, essentially, but now I have a much better understanding. Many thanks for reviewing this old thread, @lewmur
[Samsung Galaxy Tab S7 FE] marcadamf:
14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.

this step confuses me.

do i put the patched boot.tar into the AP slot in oden?

then add the BL and CSC or the HOME CSC ? to their slots?

14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.

this step confuses me.

do i put the patched boot.tar into the AP slot in oden?

then add the BL and CSC or the HOME CSC ? to their slots?

i run it like that and it passes but reboots a few times and the into recovery.

i have been factory resetting as stated.

16. Once you setup your tablet again, connect your pc and do all that usb setup agagin and then move that app-release.apk again

also confuses me a bit:

the app-release.apk refers to what?

i am reinstalling magisk apk as the device was reset but there is no indication of root at reboot

root checkers state no root

please tell me where i am messing up.

I really appreciate your time.

thank you :)

Marc
[Samsung Galaxy Tab S7 FE] lewmur:
You have to re-install Magisk and run it again to complete the root process. Use whatever Magisk apk you used the first time. That is what the app-release.apk refers to. When you run Magisk again and click install you should have the added option to load direct instead of select a file to patch. Choose that. During the install, the tablet should re-boot itself. That is the point that root gets installed.
[Samsung Galaxy Tab S7 FE] marcadamf:
finally. maybe after installing magisk again i didnt do something right but magisk was there this time ready to roll.

thank you

respectfully, marc
[Samsung Galaxy Tab S7 FE] laperry1:
hey guys, just got the SM-T733 - 256GB model via Amazon

but I get no bootloader unlock option via Developer Options

my question is, can I flash an older/alternate firmware w/the bootloader option enabled?
[Samsung Galaxy Tab S7 FE] Tofor:
I have come to find that t-mobile / Metro PCS will allow the bootloader on most of their devices to be unlocked once the requirements have been met to carrier unlock the device first. I am not saying that this is a guarantee. But on the Galaxy a02s and the Alcatel Joy Tab 2 the option does not appear in the developers menu to allow OEM Unlock at all until the device is unlocked using the unlock app included in the firmware. Once that is done the option will appear as it should in the developers menu.
[Samsung Galaxy Tab S7 FE] laperry1:
mannnn, i'm about to send this thing back...

wait-whut...

"Samsung allows unlocking the bootloader on the international versions of their phones. But on the Samsung Galaxy S8, Samsung Galaxy S9, and Samsung Galaxy Note 8, the 'OEM unlocking' option only becomes available after 7 days of activating the device and adding a Samsung or Google account to the device."

oh, ok... https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/

oem unlock achieved (long story)...

"How to unlock::

1. Turn on your device and then go to settings --> scroll down to about tablet --> Software Information then tap the Build number 7 or 8 times or until it says you unlocked developer options.

2. Go to developer options and tick OEM UNLOCK and then a warning will pop up and just accept it.

3. Turn off your device, then while holding both volume up and down, connect your device to the pc.

4. A New screen should appear saying stuff about custom roms and stuff, Jut hold and press the up button until it resets. ( THis will erase everything on the tablet)"

https://xdaforums.com/t/howto-unlock-and-root-the-galaxy-tab-s6-lite.4132289/#post-83140805

root achieved (but lost wifi, another long story)...

thanks to the OP!! now i can justify purchasing a case...
[Samsung Galaxy Tab S7 FE] lewmur:
Just rooting shouldn't cause loss of wifi. Did you also install a custom ROM?
[Samsung Galaxy Tab S7 FE] laperry1:
No such luck... The firmware provided by Frija was inappropriate for my device...

Got the right one directly from SAMMOBILE
[Samsung Galaxy Tab S7 FE] Incomtus:
Very noob question, is there an easy way to update tablet after rooting with magisk?
[Samsung Galaxy Tab S7 FE] Incomtus:
This tutorial is very fine!

Worked perfectly

Thanks a lot!!

Edit : I don't know if it's due to root, but samsung Dex system UI had a bug. keep force closing if i don't use the tablet for some times and after rebooting the tablet, no more task bar..

I rebooted a second time, the task bar is there lol.
[Samsung Galaxy Tab S7 FE] Incomtus:
yes
[Samsung Galaxy Tab S7 FE] Village_Idiot:
DeX is tied to Knox. When you root, you break Knox. Anything that needs Knox to work won't work.
[Samsung Galaxy Tab S7 FE] Incomtus:
In fact, Dex is working but it seems to be less stable. I reflashed everything and done rooting again, and now it seemed to be better. But screen does strange things the first minute of boot 🤔🤔 so if it's related to Knox I don't know what can I do 🙄🙄🙄
[Samsung Galaxy Tab S7 FE] Village_Idiot:
A while back (several months), there was a post in the S22 Ultra forums addressing this. People who rooted then later were having problems with DeX.
[Samsung Galaxy Tab S7 FE] Incomtus:
Ok, I ll see, since yesterday after resetting everything and root again, I don't have issue. I ll report if needed,

Thanks bro
[Samsung Galaxy Tab S7 FE] XLQ:
Is there anyway to restore back to stock with Knox working?
[Samsung Galaxy Tab S7 FE] Village_Idiot:
No. Once the Knox e-fuse is tripped it's irreversible.
[Samsung Galaxy Tab S7 FE] lewmur:
True, but it shouldn't effect DeX so long as it isn't rooted. If it were me, I'd flash the latest stock ROM with Odin, with CSC instead of HOME. That factory resets the device
[Samsung Galaxy Tab S7 FE] Village_Idiot:
DeX needs Knox. There's a way to trick it using TWRP, check the S22 Ultra forum. But it will need to be rooted to do it. If you're trying to pass your device off as having not been rooted you're SOL.
[Samsung Galaxy Tab S7 FE] lewmur:
There is a BIG difference between "having not been rooted" and "being rooted". I've had Samsung device for about ten years, and currently have four, and I have never heard of anyone have trouble with Samsung apps simple because the knox fuse was blown. The Magisk apps can hide the fact that the device is rooted and what the DRM level is, but not the fact the fuse was blown.
[Samsung Galaxy Tab S7 FE] Village_Idiot:
Then you need to read more in these forums and other places like Android Authority. Like I said, once the Knox fuse is tripped, anything that relies on it will not work properly; or at all.
[Samsung Galaxy Tab S7 FE] lewmur:
I've been reading these forums several time a day for the last ten years.
[Samsung Galaxy Tab S7 FE] lewmur:
That's funny. The Knox fuse is blown on mine a DeX is working fine. Because I have 3 desktop PCs with 2 40" and 1 65" monitors, I've never found the need for DeX. But because it didn't sound logical to me that if Samsung wanted to disable some apps when the Knox fuse was blown, that they wouldn't just not allow them to run. Not make the run flaky. So I dug out an HDMI to C cable and hooked up a monitor to the tablet and DeX ran without any problem. There are many things that can wrong with any HDMI connection. To the Knox is the problem doesn't make sense to me.
[Samsung Galaxy Tab S7 FE] lewmur:
That's funny. I just tried it on my tablet with Knox fuse blown and it works fine. I had never used DeX before because I have no need for it. But just to test this Knox theory, I dug out an HDMI to C cable and hooked up the tablet. Works fine.
[Samsung Galaxy Tab S7 FE] Village_Idiot:
That's funny here is at least one thread of why rooting breaks DeX. I saw another thread in the S20 forums and another in the S22U Forums.

https://xdaforums.com/t/root-and-dex-simple-question.4385671/
[Samsung Galaxy Tab S7 FE] lewmur:
We weren't talking about rooted devices but rather one's that were rooted, blowing the Knox fuse, but which were returned to stock unrooted. But this isn't an S20 anyway. MY SM-T733 S7 FE is working with the FUSE BLOWN. Your claim that Knox was necessary for DeX IS WRONG!!!
[Samsung Galaxy Tab S7 FE] cjscholten:
Thanks for the guide! I was able to root my Tab S7 this way.

Noob question: do I have to redo this every time there's an update from Samsung? (So, basically every month)
[Samsung Galaxy Tab S7 FE] Jsjs jsn:
Gvfvgvvv vv v b
[Samsung Galaxy Tab S7 FE] steev087:
So is it still impossible to root the Galaxy tablet S7 FE SM-T738U VERIZON MODEL?
[Samsung Galaxy Tab S7 FE] lewmur:
The problem with carrier models is that they control unlocking the bootloader. And you can't root with it locked. If you've fulfilled your contract you can get them to unlock it.
[Samsung Galaxy Tab S7 FE] steev087:
If the contract is fulfilled will they unlock it even if it's a Qualcomm snapdragon version?
[Samsung Galaxy Tab S7 FE] lewmur:
Easiest way to find out would be to call their tech support and ask.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
Hi everyone, I am new to this. I have downloaded Frija but for some reason when I start it up it crashes instantly. I have tried running it as admin but that's not working either. Is there something I am doing wrong?

Solved: The program was crashing so fast I couldn't see what the error was, turns out I needed to update some stuff below:

microsoft visual c++ 2008 redistributable package (x86)

microsoft visual c++ 2010 redistributable package (x86)

NEW Problem though. Step 14. Open up odin , put your device to download mode and then patch the AP using the boot.tar you just created.

I'm using the boot.tar I just created and patching the "ap" part with that file. and it keeps giving me the following:

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

<ID:0/003> Removed!!

<ID:0/003> Added!!

<ID:0/003> Removed!!

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1401)..

<ID:0/004> File analysis..

<ID:0/004> Total Binary size: 96 M

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> NAND Write Start!!

<ID:0/004> SingleDownload.

<ID:0/004> boot.img.img

<ID:0/004> Complete(Write) operation failed.

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Can someone tell me why? Or what other information I can provide?
[Samsung Galaxy Tab S7 FE] lewmur:
The thing that gets confusing with using Magisk is that some Samsung tablets need to also modify the vbmeta file as well as boot.img. This tablet is one of them. So, instead of extracting the boot.img from the AP file, copy the ENTIRE AP md5 file to the tablet and then use Magisk to modify it and not the boot.img. Copy the modified AP back to the PC and use Odin to flash it in the AP slot along with the BL and CSC.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
Thank you so much for answering. I believe I've gotten to the point of copying the modified AP back to PC and have Odin ready to go but I am a bit confused about the BL and CSC portion.

Am I using the modified AP in the AP slot AND the BL and CSC slot using the same file? for all 3 essentially?
[Samsung Galaxy Tab S7 FE] lewmur:
No. You use the BL and CSC files from the stock ROM in the BL and CSC slots and the modified file in the AP slot instead of the original AP.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
Okay, so I used the stock BL and CSC files from the same location I got the AP file before it got modified. I have my tablet in download mode. But I'm pretty sure it failed after using Odin. the log is below:

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1401)..

<ID:0/004> File analysis..

<ID:0/004> Total Binary size: 8613 M

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> NAND Write Start!!

<ID:0/004> SingleDownload.

<ID:0/004> abl.elf

<ID:0/004> xbl.elf

<ID:0/004> xbl_config.elf

<ID:0/004> tz.mbn

<ID:0/004> hypvm.mbn

<ID:0/004> devcfg.mbn

<ID:0/004> tz_iccc.mbn

<ID:0/004> aop.mbn

<ID:0/004> km41.mbn

<ID:0/004> qupv3fw.elf

<ID:0/004> storsec.mbn

<ID:0/004> NON-HLOS.bin

<ID:0/004> dspso.bin

<ID:0/004> shrm.elf

<ID:0/004> cpucp.elf

<ID:0/004> uefi_sec.mbn

<ID:0/004> imagefv.elf

<ID:0/004> sec.elf

<ID:0/004> quest.fv

<ID:0/004> testvector.fv

<ID:0/004> bksecapp.mbn

<ID:0/004> apdp.mbn

<ID:0/004> vbmeta.img

<ID:0/004> vaultkeeper.mbn

<ID:0/004> tz_kg.mbn

<ID:0/004> tz_hdm.mbn

<ID:0/004> recovery.img

<ID:0/004> vendor_boot.img

<ID:0/004> dtbo.img

<ID:0/004> super.img

<ID:0/004> vbmeta.img

<ID:0/004> vbmeta_system.img

<ID:0/004> FAIL! (Auth)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Link to image of Odin fail as well.

Is there something I am missing?
[Samsung Galaxy Tab S7 FE] lewmur:
Try this. Use 7zip to open the modified file and delete the vbmeta.img file from the archive. Then try again.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
I have gone into the modified file and deleted that vbmeta.img you said from the archive, unfortunately it did not work again.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
I was wondering what that beeping noise was. I see on my tablet's download mode screen say,

"Custom Binary(vbmeta) Blocked By OEM Lock"

What does this mean exactly? I have gone into the developer settings already and enabled OEM unlocking option.
[Samsung Galaxy Tab S7 FE] lewmur:
I'm assuming you did enable both Dev mode and OEM enable in dev options on the tablet?
[Samsung Galaxy Tab S7 FE] arcanglepk1:
Yeah. I just exited download mode to double check. Developer options are enabled. OEM unlocking is enabled. USB debugging is also enabled. Is there anything else I should have set in here?
[Samsung Galaxy Tab S7 FE] lewmur:
Let's start at the beginning. What version of stock did you download and did you flash it to your tablet? What version of Magisk?
[Samsung Galaxy Tab S7 FE] arcanglepk1:
Okay.

SM-T733

Android version: 13

AP_T733XXU5CWI4_T733XXU5CWI4_MQB71451738_REV00_user_low_ship_MULTI_CERT_meta_OS13.tar (I think this is the file I flashed with)

Magisk - 26.4

OEM unlocking - Enabled

I may be a bit confused on your question of which version of stock I downloaded. I used Bifrost, someone else posted it in this thread and entered in my SM-T733 and downloaded the firmware from that using XAR for the CSC portion. Since Frija wasn't downloading it completely for me, and kept failing.
[Samsung Galaxy Tab S7 FE] lewmur:
Did you unlock the bootloader? If you did you should be getting a nag screen when you turn the tablet with a yellow warning sign saying it is unlocked.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
I'm an idiot. You were spot on about unlocking the bootloader. I just assumed that enabling the OEM unlocking meant the bootloader was unlocked. I went through the steps to unlock the bootloader, it wiped the tablet. I quickly set up the tablet, went to download mode, and tried Odin again, and it succeeded!

The tablet asked to factory reset, which I did. What do I have left to do in order to root?
[Samsung Galaxy Tab S7 FE] lewmur:
If you succeeded flashing the modified AP, then just run magisk from the tablet and when you click install, you should now have the additional option for "Direct" install rather than "choose a file". Do that and when Magisk finishes it will reboot and you should have root.
[Samsung Galaxy Tab S7 FE] arcanglepk1:
Bless. Successfully rooted. Thank you so much Lewmur, truly appreciate the help!
[Samsung Galaxy Tab S7 FE] charter3554:
First off, lewmur, thanks for the consistent help you provide to users. I'm still learning here, how can I find out if my S7 FE has an unlockable bootloader? Is there a menu to go to?

I have MDM that comes up, it doesn't specifically say Knox Cloud, but on a boot screen it says DEVICE STATE - locked

I wonder if this software could help?

ALL Samsung FRP Bypass Free Tool || Remove Samsung FRP one click - GSM Experts Official

Main function:

gsmexpertsofficial.com
[Samsung Galaxy Tab S7 FE] Nahked:
I followed all the steps multiple times, bricked once but got it back... I lost wifi so I have to Bluetooth tether... I downloaded the proper firmware from fraija I have a fe A12 SM-T733. OEM unlock, bootloader unlocked, I tried 7zip to tar on original AP boot image to try and get wifi back but it did not work. The first attempt was successful, I took the extracted boot img to the tab used magisk to patch it sent it back renamed it and .tar it. It worked but no wifi... any ideas? Used several versions of magisk now, no luck.

Edit: I managed to get root but no wifi...
[Samsung Galaxy Tab S7 FE] lewmur:
You say you dl the "proper firmware" from Frija and yet indicate "A12 SM-T733". Does that mean you still have Android 12 on the tablet? If so, that is your problem. You need to flash the latest stock A13 ROM before doing anything else. And the version you modify with Magisk must be the same one installed on the device.