How to root Galaxy Tab S7(+). (GUIDE)
- Thread starter Nightmare0
- Start date
I'm not convinced that it's EUX. It doesn't say that anywhere in the name. And it has the same build version as the Korean one listed at:
Galaxy Firmware SM-T970
Search again but replace EUX with KOO. See if the download URL and file name/size are exactly the same as what's in your screenshot.
Its good to go. I just updated didn't do a clean install didn't install any bloat ware
Last edited:
I noticed that it says OXM XAR. OXM is a multi CSC designation, I've seen it on other Samsung devices I've used. So you're good, I guess. Have you rooted it yet?Its good to go. I just updated didn't do a clean install didn't install any bloat ware
As long as its still getting updates not in any rush to root the time will come down the road
Last edited:
Apparently applying the patch using the latest magisk release on github did not work on my device with android 12. T875 CUCL. The tablet booted normally, but there was no preinstalled magisk manager. There are a few threads that suggest using magisk canary will work, so Ill try that. Also I think you can just patch the whole AP file, Ill try that too just to be sure. Pretty sure I did the same steps as I did before..
Last edited:
I just flashed Android 12, rooted with Magisk, and installed TWRP. All seems to be working as intended, I just need to install my apps again and configure them.
Here's what to do. Unzip your firmware file if it isn't already. Open the AP tar.md5 file with ZArchiver. Extract the boot.img.lz4 file. Next, extract that file, you will end up with boot.img, not compressed. Install Magisk manager, patch that boot.img. Copy the resulting patched boot.img back to PC, flash with Odin. Bam, you should be rooted after rebooting back into Android, and you don't need to flash a huge modded AP file while doing so. It's that simple, that's the process I've followed every time I root my tab, works every time.
Edit: I almost forgot to say this, but after you have copied the patched img to PC, be sure to rename it to boot.img. then use a program like 7-Zip/WinRAR to create a tar file. So, it should be a boot.img file contained within a boot.tar file. The tar file can be named whatever you want, but the image within it MUST be called boot.img or it won't flash.
Yeah, you need canary for Android 12, I think. And no, you don't need to patch the entire AP file, that's overkill just to root.
Here's what to do. Unzip your firmware file if it isn't already. Open the AP tar.md5 file with ZArchiver. Extract the boot.img.lz4 file. Next, extract that file, you will end up with boot.img, not compressed. Install Magisk manager, patch that boot.img. Copy the resulting patched boot.img back to PC, flash with Odin. Bam, you should be rooted after rebooting back into Android, and you don't need to flash a huge modded AP file while doing so. It's that simple, that's the process I've followed every time I root my tab, works every time.
Edit: I almost forgot to say this, but after you have copied the patched img to PC, be sure to rename it to boot.img. then use a program like 7-Zip/WinRAR to create a tar file. So, it should be a boot.img file contained within a boot.tar file. The tar file can be named whatever you want, but the image within it MUST be called boot.img or it won't flash.
Last edited:
Hey, thanks for confirming. Indeed canary did work, I kinda freaked out a few times when it flashed twice without the preinstalled magisk.
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
Welp, I tripped Knox trying to root my S7+. I got it unlocked and rooted but tried to undo the root and screwed up my warranty. Good luck to all.
After testing Android 12 for the past week, I'm mostly liking what I see. However, when playing Call Of Duty Mobile, my PS4 DualShock controller (genuine, not 3rd party) randomly disconnects. This happens even after I've fully charged it. It's getting really annoying, especially when it happens in the middle of a round. I've died more than a few times because of this. It was never a problem on Android 11 either.
Sometimes it will stay connected for an hour with no disconnects, other times it will disconnect several times within the span of 5-10 mins. I can always press the PS button and it will reconnect, but it's still annoying AF.
As I see it, the issue is one of 3 things:
1. Android 12
2. Faulty controller (I don't have any others to test with)
3. CODM (perhaps an update or whatever)
I've tested with other BT devices that I use frequently (earbuds, speaker, etc), they are fine and never disconnect unless they need to be charged.
I'm just wondering if anyone else is having Bluetooth issues with A12. I'm going to try downgrading to see if the issue persists.
Thanks!
Sometimes it will stay connected for an hour with no disconnects, other times it will disconnect several times within the span of 5-10 mins. I can always press the PS button and it will reconnect, but it's still annoying AF.
As I see it, the issue is one of 3 things:
1. Android 12
2. Faulty controller (I don't have any others to test with)
3. CODM (perhaps an update or whatever)
I've tested with other BT devices that I use frequently (earbuds, speaker, etc), they are fine and never disconnect unless they need to be charged.
I'm just wondering if anyone else is having Bluetooth issues with A12. I'm going to try downgrading to see if the issue persists.
Thanks!
Last edited:
thatruth132
Senior Member
Will this twrp work for t870TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
Almost certainly, no. That's a different device. I'm guessing that TWRP for Tab S7+ won't be compatible with Tab S7 (non-plus). However, I think that someone has been trying to build a working TWRP for the Tab S7. To me, TWRP is as important as root, which is why I went with the plus model.
Bought a new PS4 controller, no more disconnects. So, the old controller was aging and faulty. Looks like I'll be keeping Android 12 after all.
Are you kidding? My instructions are very clear. And I can't make a video for the PC side of the instructions, since my PC recently stopped powering on. I'm pretty sure it's a hardware issue. Just follow what I posted, you'll be fine.
It's easier to just patch it yourself. You shouldn't use someone else's patched file, because it needs to match the version code of the firmware you currently have installed.
Download your firmware, extract using the instructions I posted on this page, patch with Magisk.
I don't know if you all noticed but there's another EUX update CVA5 out showing up on Frija
I flashed it works fine
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Damn, that sucks. Nothing at all? Are you sure? Because Samsung devices are almost impossible to hardbrick. 99% of the time%, anything you've messed up, software-related, can be fixed by flashing official stock firmware with Odin. I personally have never bricked any of my Samsungs, and I dont know anyone else that has.
It sounds like you unlocked the bootloader, but didnt yet do the step of connecting to Internet and going to Developer Options to ensure that the bootloader unlock option is toggled on and grayed out. Once it says there that you're unlocked, you should be good to proceed with root.ing, TWRP, etc.
Try holding Volume Up and Volume Down, but not Power, while plugging the device into a PC USB port. It must be a PC, not a charger. If you're lucky, that might get you into download mode so you can at least flash the stock ROM. Trying leaving the tab plugged in overnight charging before doing so. Even if you cant see that it's charging.
If that fails, I'd suggest contacting Samsung support and seeing if they can get you to bring it in to an authorized service center for repair. -
10Download the firmware, and extract "boot.img.lz4" from AP.
Use 7-zip or something else to compress the boot file and choose TAR format.
Use Magisk to patch the "boot.img.tar", and you will get "magisk_patched.tar" in /Download folder.
Flash it as AP and wipe user data. (You should unlock the bootloader.)
Then you have successfully rooted your device.
How to download the firmware.
Use Samfirm to search device model and CSC code.
It seems that Sammobile has not released the firmware of the new Galaxy Tab S7 series.10
Knox is 100% tripped. Samsung Pass cannot use. Netflix widevine, Dex and Spen are not affected.
Unlock Bootloader: turn on "OEM unlocking" in "Developer options"
connect to the PC, reboot the tablet and hold both volume up and down. Then hold volume up to unlock it. (The method may be different now)
Download the firmware from Frija and unzip it.
Unzip the AP file, you will get "boot.img.lz4" and tar this file, get a tar file.
Copy it to your phone and use magisk to patch it, get "magisk_patched.tar" in "/Download". Copy it to the PC.
Whether your phone is rooted or not is not important.
Boot into Download Mode, and use Odin flash AP, BL, CSC, (CP). Then use AP slot flash "magisk_patched.tar".
Install magisk manager on your tablet.
Done.
When updating your tablet, you should reflash it, including the new patched file, but use the "HOME_CSC" file instead of "CSC" file.
Data will not be lost.
Why patch the boot file?
When patching it, magisk is written into it. When you boot your tablet, magisk will run. Another way is to patch the recovery file. When boot into recovery, magisk will run.
When updating, why flash "HOME_CSC"?
Flash "HOME_CSC" you will keep all your data, if you flash "CSC", you will lose all your data. It is the easiest way to update it.
Any way to fix the Knox?
No.
Frija: https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
Odin: https://odindownloader.com
Magisk: https://magiskmanager.com6
I have rooted my Tab S7+ what i gained is the ability to add a system wide ad block with adguard doh + firewall with the ability to use a vpn at the same time.
Also bouncer now works seamlessly with a rooted device. I also use warden which blocks in app trackers and loggers from system apps and debloat easily from the device without using adb.
I am able to use tasker to seamlessly adjust apps that are not optimized for tablets in landscape mode so that they work properly on my device.
All of that is only possible with a rooted device and im discovering new tweaks every single day.33@Markeee: I figured out how to relock, after several hours of digging and trying different things. I'm posting a short tutorial in the Tab S7(+) bootloader unlock thread for anyone who is interested.
Bootloader relock instructions
