Database Users

SM-T590 root/custom recovery?

So i got today the "Samsung Galaxy Tab A 10.5 (gta2xlwifi /SM-T590) with Android 8.1, the first Question i had "Can i root the Tablet?".
Well this is now my Question, i used google for a Hour and the Search function in XDA but apperently i cant find smth about this Device + root/custom recovery, i just found a news article with rumors about the Bixby Button.
so i wanted to ask if someone know already smth about rooting this device or give me some advises where i should begin with workarounds or smth like that.

Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Unpack the lz4 compressed image
Install Magisk and select the Patch boot image method
Flash the patched boot image with ODIN/Heimdall
Cheers, Tom

tomparr said:
Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Install Magisk and select the Patch boot image method
If sucessful, flash the patched boot image with ODIN/Heimdall
Cheers, Tom
Click to expand...
Click to collapse
(That English sounds kinda bad not gonna lie xd im really sorry for this crappy text tried my best)
first of all thanks for your time
so..... i did not found any infos about unlocking bootloader for this tablet... probably i dont search the right terms...
Well i tried it without unlocking it (idk if its maybe already unlocked)
now i created the boot image, install it via odin now yeah...
ive got magisk now and "root" but root do not actually work (apps like titaniumbackup cant find the "su") (probably because the bootloader isnt unlocked?)
so maybe its because of the bootloader not unlocked, just not working because of this "workaround", so i basically just can wait till someone take her/his time with this device or i did something wrong and didnt do it right

tomparr said:
Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Install Magisk and select the Patch boot image method
If sucessful, flash the patched boot image with ODIN/Heimdall
Cheers, Tom
Click to expand...
Click to collapse
Edit: I tried this and the boot.img won't patch, comes back saying it can't patch the stock kernel.

airmaxx23 said:
Edit: I tried this and the boot.img won't patch, comes back saying it can't patch the stock kernel.
Click to expand...
Click to collapse
Hi,
Could you upload the boot.img(.lz4) somewhere? My device should arrive any day now, so I am really interested to get it working.
-- Tom

tomparr said:
Hi,
Could you upload the boot.img(.lz4) somewhere? My device should arrive any day now, so I am really interested to get it working.
-- Tom
Click to expand...
Click to collapse
Here you go, please keep me updated on your progress and let me know if I can help. This is from the December update.
https://drive.google.com/file/d/1hlntpS7hj6zsfuBW6JbPvJoCOEVSDG3i/view?usp=drivesdk

airmaxx23 said:
Here you go, please keep me updated on your progress and let me know if I can help. This is from the December update.
https://drive.google.com/file/d/1hlntpS7hj6zsfuBW6JbPvJoCOEVSDG3i/view?usp=drivesdk
Click to expand...
Click to collapse
Thank you. I ran the above steps (after decompressing the image with lz4) and the patching process went through without any issues. You can find the recompressed image here. No warranty it will work though since I don't have access to the device (yet) but please let me know if it works.

tomparr said:
Thank you. I ran the above steps (after decompressing the image with lz4) and the patching process went through without any issues. You can find the recompressed image here. No warranty it will work though since I don't have access to the device (yet) but please let me know if it works.
Click to expand...
Click to collapse
It's my first time messing with Samsung firmware in a long time so I've pretty much forgotten everything, I've also never messed with the lz4 extension before. How did you go about extracting the boot.img?
I'll probably wait until you try it since you're obviously more experienced with Samsung firmware. Please keep me posted.

airmaxx23 said:
It's my first time messing with Samsung firmware in a long time so I've pretty much forgotten everything, I've also never messed with the lz4 extension before. How did you go about extracting the boot.img?
I'll probably wait until you try it since you're obviously more experienced with Samsung firmware. Please keep me posted.
Click to expand...
Click to collapse
My last Samsung device was a Galaxy S2, so it has been a long time for me too. For now I just did a bit of reading about the new formats. The lz4 compression also seems to be relatively new and replace the old img.tar format. You can simply extract the boot.img from the boot.img.lz4 by using the official lz4 binary with the command
Code:
lz4.exe boot.img.lz4
After Magisk patched the image you can repack it by using
Code:
lz4.exe -B6 --content-size patched_boot.img patched_boot.img.lz4
The new image should be flashable with Odin/Heimdall.

tomparr said:
My last Samsung device was a Galaxy S2, so it has been a long time for me too. For now I just did a bit of reading about the new formats. The lz4 compression also seems to be relatively new and replace the old img.tar format. You can simply extract the boot.img from the boot.img.lz4 by using the official lz4 binary with the command
Code:
lz4.exe boot.img.lz4
After Magisk patched the image you can repack it by using
Code:
lz4.exe -B6 --content-size patched_boot.img patched_boot.img.lz4
The new image should be flashable with Odin/Heimdall.
Click to expand...
Click to collapse
Would I use the AP slot in Odin? If I have issues I'd just flash the stock boot.img.lz4?

airmaxx23 said:
Would I use the AP slot in Odin? If I have issues I'd just flash the stock boot.img.lz4?
Click to expand...
Click to collapse
Yes and yes

tomparr said:
Yes and yes
Click to expand...
Click to collapse
There's only one problem, the file you patched needs to have a .tar or .md5 extension for Odin, it won't accept an .lz4 extension. When you patched it with Magisk did you select .tar format?

From what I've read, you need at least Odin 3.13.1 to flash a lz4 image.

tomparr said:
From what I've read, you need at least Odin 3.13.1 to flash a lz4 image.
Click to expand...
Click to collapse
I have Odin 3.13.1 and there's no option or way to flash an LZ4 image.

airmaxx23 said:
I have Odin 3.13.1 and there's no option or way to flash an LZ4 image.
Click to expand...
Click to collapse
My bad, I've been away too long from Samsung firmwares. Please try this patched boot image. I've recreated it as an img.tar file.

tomparr said:
My bad, I've been away too long from Samsung firmwares. Please try this patched boot image. I've recreated it as an img.tar file.
Click to expand...
Click to collapse
That worked, we have root. A couple things are acting strange but it may be a Samsung thing. Adaway won't stay enabled after a reboot, when trying to edit the build.prop with Root Explorer the tablet reboots when I hit "save". Root Explorer won't delete anything in system/app or system/priv-app.
I have Magisk installed, V4A, Substratum and OnePlus Gestures.
Could you do me one favor and repackage the stock boot.img.lz4 with a .tar extension so I have it. Or explain to me the steps to do it.

airmaxx23 said:
That worked, we have root. A couple things are acting strange but it may be a Samsung thing. Adaway won't stay enabled after a reboot, when trying to edit the build.prop with Root Explorer the tablet reboots when I hit "save". Root Explorer won't delete anything in system/app or system/priv-app.
I have Magisk installed, V4A, Substratum and OnePlus Gestures.
Could you do me one favor and repackage the stock boot.img.lz4 with a .tar extension so I have it. Or explain to me the steps to do it.
Click to expand...
Click to collapse
Glad to hear it worked, at least to some extend.
I've created a flashable tar from your initial boot image, which you can find here. If you want to try it yourself, here's what I did:
Decompress lz4 image: 'lz4 -d boot.img.lz4'
Create tar archive: ' tar --create --format=gnu -b20 --quoting-style=escape --owner=0 --group=0 --totals --mode=644 -f boot.img.tar boot.img'

tomparr said:
Hi,
As far as I know there is no custom recovery for the SM-T590 yet. You're best bet to root the device is most likely to use Magisk and create a patched boot.img with Magisk Manager. The following steps should do the trick, but no guarantees as I have not tested it with this device:
Download the firmware matching your device firmware version
Unlock your bootloader (this will also trigger the KNOX fuse, so apps like Samsung Pay will no longer work)
Install Magisk Manager
In the settings of Magisk Manager, set the boot image format to img.tar
Unpack the lz4 compressed image
Install Magisk and select the Patch boot image method
Flash the patched boot image with ODIN/Heimdall
Cheers, Tom
Click to expand...
Click to collapse
Thanks for that, worked for me after some glitches. Now rooted with xposed working.

gscollier said:
Thanks for that, worked for me after some glitches. Now rooted with xposed working.
Click to expand...
Click to collapse
Which SDK version did you install?
Also, can you please do me a favor? Go into system/app or system/priv-app and try to rename an apk and see what happens.

So you guys are making some progress. Its been a while for me too. I used to develop ROMs here ages ago but I am so out of the loop. Can't find any repos either. The last time I used Odin (and hated it) was back in the skyrocket days. Is it absolutely mandatory? Would adb work in Linux?
I always tried to avoid magisk or just didn't need it. Is it possible to avoid a recovery with it?

(Method) For everyone who wants to Downgrade Galaxy S8 to Oreo/Nougat

Hey guys!
I recently read many Questions About downgrading the Galaxy S8 to 7.0/8.0 after we got the 5x Bootloader.
Well many of you say NO but What many of you forgot is that there is a way to Downgrade your phone.
I already had that Problem with my S6 back in 2016, where I wanted to Downgrade it to 5.1. All you Need for a Downgrade is a Combination File.
Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices.
Combination ROM Advantages:
Its help you to repair imie number in some models like S8/S8 plus S7/S7 Edge S6/S6 Edge…
Its very useful in bypass samsung account in too many models.
Its very useful in bypass Google account in too many models.
Its very useful for downgrade in some models.
Its help you to enable usb debugging.
its help to remove any security FRP / Reactivation Lock from Samsung like 2016-2019
You can find Combination Files for Galaxy S8 devices here:
G950U with latest Bootloader: http://www.mediafire.com/file/j8xi2n73zhh37q1/COMBINATION_FA70_G950USQU5ARG4.zip
G950F (currently only for 4x Bootloader): http://www.mediafire.com/file/c37zq...QB19841686_REV00_user_mid_noship.tar.rar/file
Here is a Video of Downgrading a Galaxy S6 Edge with Combination File : https://www.youtube.com/watch?v=dOKJcHU1pXM Should work with S8 too

Hello, nice tutorial!
Want to ask:
"Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices. "
So only Samsung releases these files to public? or are leaked?
I`m asking to check if I should wait or not, I had V4 bootloader but recently by accident with the latest update I got V5

rilley said:
Hello, nice tutorial!
Want to ask:
"Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free, before making its final release. These files are created by Samsung company and are found in only their devices. "
So only Samsung releases these files to public? or are leaked?
I`m asking to check if I should wait or not, I had V4 bootloader but recently by accident with the latest update I got V5
Click to expand...
Click to collapse
I would recommend you to wait till the latest Combination File gets public for the G950F/G955F. They do work very good and are also stable. Usually I think Samsung does not public These files online but they get leaked very often. I used the Combination File to Downgrade my S6 from 7.0 with Bootloader 6 to 5.1.1 with Bootloader 2.
Im sorry but I can only explain the function of a Combination Rom along with the Galaxy S6..
Once Cthe latest Combination File is available, do this:
1. Download your Nougat/Oreo Firmware you want to install
2. Download Combination File with the latest Bootloader Version
3. Downlad 7zip, since you Need to edit the firmware you want to install
3b) Extract the firmware you want to install to a new Folder
3c) Delete all files except for boot.img, cache.img, recovery.img and system.img
3d) Open 7zip from your Start Menu and locate the firmware Folder
3e) Mark the remaining files and press the green "Add" Button at the upper left corner and create a tar (Odin Flashable) file
4)Download Odin
5) First uncheck Auto-Reboot
6) Now first Flash the Combination File
7) Afterwards go directly again in Download Mode and Flash the tar- firmware File
8) Reboot your phone and do a wipe
9) Congrats! You now have Stock 7.0/8.0 Back!
Notes: Fingerprintscanner wont work, because it is a part of cm.bin, OTA Updates wont work as well, Dont worry if you see a green text next to the Phone logo while starting it. Thats normal and not an error.
Backup your files before you do that!

I hope it helped you

halloo13 said:
I hope it helped you
Click to expand...
Click to collapse
Yes, many thanks for response!
I guess I will wait until I get the combination of files, but until then I want to switch CSC, found a solution to use THAI sim card, but not sure, if everything goes ok, I guess the new OTA update will be the latest from THAI, there are no changes to get bricked by this method right? ( I will be able to get back to the ROM stock that I have now? )

halloo13 said:
I would recommend you to wait till the latest Combination File gets public for the G950F/G955F. They do work very good and are also stable. Usually I think Samsung does not public These files online but they get leaked very often. I used the Combination File to Downgrade my S6 from 7.0 with Bootloader 6 to 5.1.1 with Bootloader 2.
Im sorry but I can only explain the function of a Combination Rom along with the Galaxy S6..
Once Cthe latest Combination File is available, do this:
1. Download your Nougat/Oreo Firmware you want to install
2. Download Combination File with the latest Bootloader Version
3. Downlad 7zip, since you Need to edit the firmware you want to install
3b) Extract the firmware you want to install to a new Folder
3c) Delete all files except for boot.img, cache.img, recovery.img and system.img
3d) Open 7zip from your Start Menu and locate the firmware Folder
3e) Mark the remaining files and press the green "Add" Button at the upper left corner and create a tar (Odin Flashable) file
4)Download Odin
5) First uncheck Auto-Reboot
6) Now first Flash the Combination File
7) Afterwards go directly again in Download Mode and Flash the tar- firmware File
8) Reboot your phone and do a wipe
9) Congrats! You now have Stock 7.0/8.0 Back!
Notes: Fingerprintscanner wont work, because it is a part of cm.bin, OTA Updates wont work as well, Dont worry if you see a green text next to the Phone logo while starting it. Thats normal and not an error.
Backup your files before you do that!
Click to expand...
Click to collapse
Hi, ok but it means that i cannot use fingerprint or ota update anymore or after dowgrade could i install full stock firmware with odin and recovery functionalities?

Will this trip Knox?

Any idea if I can downgrade from pie on a S8+ on bootloader 6?

I've tried this method on my S7 edge but I've stucked on step - deleting files.
After extracting the firmware I get 5 files- Ap, Bl ect.
When i extract the AP file (previously deleting "md5" from the name, and becoming rar file) there are only 3 new files (nothing for delete if i remembering correctly)
Files i need to delete are on other files from extracted firmware.
At the end I finished on unsuccessful flash.
I want to go back to nougat on my S8+ (955f), but i dont want to take risks, so I did flashing on old device with corect firmware.
I'm really mad at Samsung. Battery life become horrible at pie. Thats why I want to go back to nougat or at least oreo.
I will post some videos after day or two how is possible to downgrade android version on some Samsung devices with higher bootloader version. These methods didn't worked for me but may be they will encourage some of you to make possible the downgrade.

As I promised:
1. Interesting way to downgrade Samsung Device (J series) when touchscreen does not working:
https://www.youtube.com/watch?v=SmfgxoUhflA&feature=emb_title
2. Second method:
https://www.youtube.com/watch?v=ZKg1DC4ul_g&feature=emb_title
As I remember oreo and nougat have pro mode on video recording and faster charging speed. I hope someone to explain is it possible to downgrade S8 and whats are the steps with this method.

so if i want to downgrade to firmware with bootloader v4 but my phone has now v6, will i download combination file with bootloader 6 or 4? I didn't get that part, sorry. i have s8+
edit: ok, 4 didn't work, so i guess need to get 6

Does anyone know the password for the linked Combination file?

Thanks for this thread.
I want to downgrade from Oreo to nougat too, I'm on "U1" security patch, but I don't understand the order of bootloader version... Can you try to explained how to ?
I found this if it can help : https://combinationfirmware.com/combination-samsung-galaxy-s8/

Scylla.bx said:
Thanks for this thread.
I want to downgrade from Oreo to nougat too, I'm on "U1" security patch, but I don't understand the order of bootloader version... Can you try to explained how to ?
I found this if it can help : https://combinationfirmware.com/combination-samsung-galaxy-s8/
Click to expand...
Click to collapse
Since you are on bootloader version 1, you don't need the combination files. If you were past version 2 they would be needed.
Once you update to a new bootloader you can't go back to software on the older bootloader without the combination files.

Kaloob said:
Since you are on bootloader version 1, you don't need the combination files. If you were past version 2 they would be needed.
Once you update to a new bootloader you can't go back to software on the older bootloader without the combination files.
Click to expand...
Click to collapse
Thank you for your reply.
Ok so if im on the right bootloader for Nougat, why can i install this rom ?
[S8/S8+][Nougat][01-Jan-2020][v30] LightROM
In fact i can install it, all seem to be fine, no error in twrp, but at reboot it freeze at bootloader
Thanks for your help bro

Scylla.bx said:
Thank you for your reply.
Ok so if im on the right bootloader for Nougat, why can i install this rom ?
[S8/S8+][Nougat][01-Jan-2020][v30] LightROM
In fact i can install it, all seem to be fine, no error in twrp, but at reboot it freeze at bootloader
Thanks for your help bro
Click to expand...
Click to collapse
If you have an Exynos version, maybe ask around on that thread.
If you have a Snapdragon variant, you can't flash that ROM.

Kaloob said:
If you have an Exynos version, maybe ask around on that thread.
If you have a Snapdragon variant, you can't flash that ROM.
Click to expand...
Click to collapse
I have exynos. Anyway thank for your help, i try to post on that thread and hope someone could figure it out.
Peace

Did anyone find the password for the file?

necklickhia said:
Does anyone know the password for the linked Combination file?
Click to expand...
Click to collapse
Password I had to find it elsewhere: "www.samkey.org/forum" without the quotes

(Root Guide) Samsung Galaxy J7 Prime J727t1 (U4 Only)

Finally, a method to root the Galaxy J7 Prime!!!!
Do note, this root isnt perfect. Root has to be manually started every reboot via ADB or the included bat script.
By installing this, you will not loose any data. I still would be wise to backup your devices regadless.
This root package only supports firmware U4. Odin will not flash these files if your build is above U4.
If you are on a build lower that U4, do not flash this, you will softbrick your device.
I can provide the U4 update if people need it. TBA
J727t1 U4 Odin Firmware
The Steps
1. Download and Extract the zip package to your desktop. --------> J727t1 Root.zip
2. Go into J727t1 Root\Odin Firmware and run odin.
3. Click BL and select "Put in BL Slot ENGSboot.tar" (Its in the Odin_Firmware folder)
4. Click AP and select "Put in AP slot ENGRoot.tar" (Its in the Odin_Firmware folder)
5. Power off you device, and then by pressing and holding "Power Vol_Down and Home" boot into download mode. (Dont forget to press Volume Up when prompted)
6. Connect your phone and then click start. Let your phone reboot.
7. Once booted, go into Go into J727t1 Root and run Install_Root.bat . Let your phone reboot again.
8. Now finally, in the J727t1 Root folder run 00activate_root.bat
You are now rooted and SuperSu should work until you reboot your phone.
Additional notes:
NO OEM UNLOCK NEEDED
The Install_Root.bat puts the bat file to activate root on your device.
That way, if your out and about while your phone reboots, you just need
a computer to reactivate root. lol lol

xxMoon said:
Finally, a method to root the Galaxy J7 Prime!!!!
Do note, this root isnt perfect. Root has to be manually started every reboot via ADB or the included bat script.
By installing this, you will not loose any data. I still would be wise to backup your devices regadless.
This root package only supports firmware U4. Odin will not flash these files if your build is above U4.
If you are on a build lower that U4, do not flash this, you will softbrick your device.
I can provide the U4 update if people need it. TBA
The Steps
1. Download and Extract the zip package to your desktop. --------> J727t1 Root.zip
2. Go into J727t1 Root\Odin Firmware and run odin.
3. Click BL and select "Put in BL Slot ENGSboot.tar" (Its in the Odin_Firmware folder)
4. Click AP and select "Put in AP slot ENGRoot.tar" (Its in the Odin_Firmware folder)
5. Power off you device, and then by pressing and holding "Power Vol_Down and Home" boot into download mode. (Dont forget to press Volume Up when prompted)
6. Connect your phone and then click start. Let your phone reboot.
7. Once booted, go into Go into J727t1 Root and run Install_Root.bat . Let your phone reboot again.
8. Now finally, in the J727t1 Root folder run 00activate_root.bat
You are now rooted and SuperSu should work until you reboot your phone.
Additional notes:
NO OEM UNLOCK NEEDED
The Install_Root.bat puts the bat file to activate root on your device.
That way, if your out and about while your phone reboots, you just need
a computer to reactivate root. lol lol
Click to expand...
Click to collapse
Maybe, if you tried incorporating flashing Magisk or using Magisk to patch a boot.img and flashing that into this process, somehow, you might be able to keep persistent root.
Sent from my SM-S767VL using Tapatalk

You cant, the bootloader is locked. Any changes to boot, recovery or sboot trigger no boot.

xxMoon said:
You cant, the bootloader is locked. Any changes to boot, recovery or sboot trigger no boot.
Click to expand...
Click to collapse
Ah, I thought this method might have involved using an engineering(factory test) firmware that had a bootloader that would allow modification even with a locked bootloader or even allow the bootloader to be unlocked. I've seen similar steps and method used with that type of firmware. My mistake.
Sent from my SM-S767VL using Tapatalk

As for making it persistent, the only sh files the boot.img .rc's load are install-recovery.sh and init.sec.boot.sh . Patching them to load the su daemon does nothing. Gotta be a permission thing preventing them from running. Maybe its just a exynos oreo thing... Any ideas people?

xxMoon said:
As for making it persistent, the only sh files the boot.img .rc's load are install-recovery.sh and init.sec.boot.sh . Patching them to load the su daemon does nothing. Gotta be a permission thing preventing them from running. Maybe its just a exynos oreo thing... Any ideas people?
Click to expand...
Click to collapse
Your device doesn't have the OEM unlock setting? Factory test/Engineering firmware typically do.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Your device doesn't have the OEM unlock setting? Factory test/Engineering firmware typically do.
Click to expand...
Click to collapse
They dont, ive tested every build, they dont have it baked in. I looked throug, the decompiled secsettings.apk oem unlock is there, but something is disabling it.

xxMoon said:
They dont, ive tested every build, they dont have it baked in. I looked throug, the decompiled secsettings.apk oem unlock is there, but something is disabling it.
Click to expand...
Click to collapse
You mean the setting is there but it is greyed out? Have you tried the trick involving changing the date in system settings to a month or so ago? It bypasses the block that some carriers use that involves a set amount of time having to pass before the setting can be altered, once the time limit expires, the setting is available. Changing the date can trick this into thinking that the proper amount of time has passed.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
You mean the setting is there but it is greyed out? Have you tried the trick involving changing the date in system settings to a month or so ago? It bypasses the block that some carriers use that involves a set amount of time having to pass before the setting can be altered, once the time limit expires, the setting is available. Changing the date can trick this into thinking that the proper amount of time has passed.
Click to expand...
Click to collapse
No, oem unlock doesnt show period, no matter what is done. As for init.d support, after looking through the kmsg, I discover defex was blocking it. I did find one gem though, after looking through the init.rc file, it looks for an rc file that doesnt exist. I can make an rc file with the name its looking for and put it in the directory where it should be, init will run it. But still anything that involves running sec-sh or su gets blocked by defex during init.

xxMoon said:
No, oem unlock doesnt show period, no matter what is done. As for init.d support, after looking through the kmsg, I discover defex was blocking it. I did find one gem though, after looking through the init.rc file, it looks for an rc file that doesnt exist. I can make an rc file with the name its looking for and put it in the directory where it should be, init will run it. But still anything that involves running sec-sh or su gets blocked by defex during init.
Click to expand...
Click to collapse
There is a .zip that can be flashed to bypass defex. If you have root, you can try flashing that .zip via Flashify or similar app.
There is a zip for disabling dm-verity also.
There is also a RMM fix that can be flashed via Odin.
Where did you get the files that you used to gain root? Where they specific to your device? Did you create them yourself? If you made them yourself, what did you use to make them, did you modify them yourself, if so, what about them did you modify?
I'm asking all this because I'm trying to root a SM-J737A and a SM-S767VL. I've tried all kinds of tricks trying to flash TWRP or Magisk. I don't think I can make it work so I wanted to try your method if nothing else. I just want to know if I need to modify your method to be compatible with my devices. If so, what do I need to modify or at least, where can I find information to make those modifications, if needed?
I see that your files are ENG files, did you get these from the engineering firmware for your device? I have the engineering firmware for both of the devices I listed, they are both U4, the full cstock firmware for both are S4. The J737A has the OEM unlock setting and it is enabled but in download mode it still says KG State: prenormal. The S767VL does not have the OEM unlock setting but in download mode it says KG State: checking. It's confusing and contradictory.
What do I need to adapt files from these firmware to use on these devices?
Sent from my SM-S767VL using Tapatalk

Yeah any zip that modifies the ramdisk wont work. My suggestion for you is to scour the web for an eng root boot img. They give you a rooted adb which means you can do root stuff in the shell. They are signed by Samsung so they can flash via odin no problem.

https://gsm-firmware.com/index.php?a=downloads&b=folder&id=14315
If you contact this place, they offer eng root boot.imgs, i think they charge for em though.

Droidriven said:
I see that your files are ENG files, did you get these from the engineering firmware for your device? I have the engineering firmware for both of the devices I listed, they are both U4, the full cstock firmware for both are S4. The J737A has the OEM unlock setting and it is enabled but in download mode it still says KG State: prenormal. The S767VL does not have the OEM unlock setting but in download mode it says KG State: checking. It's confusing and contradictory.
What do I need to adapt files from these firmware to use on these devices?
Click to expand...
Click to collapse
Most of the newer factory combination roms are pretty secure. I think engroot files are made specifically for official firmwares, just have to match the builds. The sboot from my package is from a combination rom, had to use it to allow for system modifications. If you use just the engroot, all the files you push to /system dissappear after a reboot.

xxMoon said:
Yeah any zip that modifies the ramdisk wont work. My suggestion for you is to scour the web for an eng root boot img. They give you a rooted adb which means you can do root stuff in the shell. They are signed by Samsung so they can flash via odin no problem.
Click to expand...
Click to collapse
As in eng root boot.img specific to my model number and U4 binary? Or any eng boot.img from any 7870 J7 variant with U4?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
As in eng root boot.img specific to my model number and U4 binary? Or any eng boot.img from any 7870 J7 variant with U4?
Click to expand...
Click to collapse
They are specific to your model number. They are also specific to your build, preferably you want it to match yours. If its a lower build they wont flash.

xxMoon said:
They are specific to your model number. They are also specific to your build, preferably you want it to match yours. If its a lower build they wont flash.
Click to expand...
Click to collapse
not specific to build, but specific to Binary, you cant write U4 stuff on U3 firmware.

yurais said:
not specific to build, but specific to Binary, you cant write U4 stuff on U3 firmware.
Click to expand...
Click to collapse
I could be mistaken, but, the U3 engineering firmware can be flashed over U4 full stock firmware, but the U3 full stock firmware can not be flashed over U4 full stock firmware.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
I could be mistaken, but, the U3 engineering firmware can be flashed over U4 full stock firmware, but the U3 full stock firmware can not be flashed over U4 full stock firmware.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
As far as I know , you can't downgrade any thing from U4 to U3, not stock and not ENG.
Enviado desde mi SM-G960U mediante Tapatalk

xxMoon said:
Finally, a method to root the Galaxy J7 Prime!!!!
Do note, this root isnt perfect. Root has to be manually started every reboot via ADB or the included bat script.
By installing this, you will not loose any data. I still would be wise to backup your devices regadless.
This root package only supports firmware U4. Odin will not flash these files if your build is above U4.
If you are on a build lower that U4, do not flash this, you will softbrick your device.
I can provide the U4 update if people need it. TBA
The Steps
1. Download and Extract the zip package to your desktop. --------> J727t1 Root.zip
2. Go into J727t1 Root\Odin Firmware and run odin.
3. Click BL and select "Put in BL Slot ENGSboot.tar" (Its in the Odin_Firmware folder)
4. Click AP and select "Put in AP slot ENGRoot.tar" (Its in the Odin_Firmware folder)
5. Power off you device, and then by pressing and holding "Power Vol_Down and Home" boot into download mode. (Dont forget to press Volume Up when prompted)
6. Connect your phone and then click start. Let your phone reboot.
7. Once booted, go into Go into J727t1 Root and run Install_Root.bat . Let your phone reboot again.
8. Now finally, in the J727t1 Root folder run 00activate_root.bat
You are now rooted and SuperSu should work until you reboot your phone.
Additional notes:
NO OEM UNLOCK NEEDED
The Install_Root.bat puts the bat file to activate root on your device.
That way, if your out and about while your phone reboots, you just need
a computer to reactivate root. lol lol
Click to expand...
Click to collapse
Got a bootloop after flashing files , but it is because battery was drained
Replaced battery and all is well.
Is it engRoot boot.img file the same than extracting boot.img from combination firmware ?

yurais said:
delete it
Click to expand...
Click to collapse
No

TWRP, Rooting and Custom Rom HELP SM-T510 Tablet Tab A 10.1

Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)

You don’t unzip the .tar files. Keep them as is.

secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5

My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.

fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.

is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse

fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!

framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?

framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.

lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.

framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.

lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY

framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.

lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!

framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.

Did anybody unlock the bootloader and root the unit?

As topic asked.
It looks like OEM unlock (in developers settings) is hidden on US phone models
The last Samsung I made root was S5e and I am wondering is S6L possible

sadly no
Nope, Samsung hasn't even released the stock firmware yet so any development is currently halted

Can the user unlock the bootloader then?

Haven't tried it, but it should be possible

I don't know about unlocking the bootloader. This page (updated in Apr 2020) showed a way https://www.getdroidtips.com/root-samsung-galaxy-tab-s6-lite/ to root it. I haven't tried it yet. If anybody tries, please leave some comments.
Edit: how to unlock the bootloader https://gearallnews.com/how-to-unlock-bootloader-of-samsung-galaxy-tab-s6-lite-guide-2020-2/

I managed to unlock the bootloader with the tutorial on http://androidbiits.com/root-samsung-galaxy-tab-s6-lite-sm-p610-sm-p610x-easily/, but rooting with the Magisk file failed.
I think i will try it later.
The bootlader is now unlocked, so it gives me a warning on the screen every time i boot the tablet.
I have the P610 version, only WiFi, no LTE

I tried it for the second time and now succeeded.
Installed Titanium Backup and removed some useless system apps.

Iceman66 said:
I tried it for the second time and now succeeded.
Installed Titanium Backup and removed some useless system apps.
Click to expand...
Click to collapse
Has Samsung released the firmware tho? I wanted to root but scared if the process failed I cant flash the old ROM

StuKaGel said:
Has Samsung released the firmware tho? I wanted to root but scared if the process failed I cant flash the old ROM
Click to expand...
Click to collapse
You can find it here: https://samfrew.com/model/SM-P610/ I found the link in the turorial.
Be aware that this is for P610 (only Wifi), but you can find the firmware for the other versions off the S6 Lite as well on this website.

Iceman66 said:
I tried it for the second time and now succeeded.
Installed Titanium Backup and removed some useless system apps.
Click to expand...
Click to collapse
Hi, thank you very much for reporting it. Do you know if Netflix still works after the unlocking and rooting?

dxxvi said:
Hi, thank you very much for reporting it. Do you know if Netflix still works after the unlocking and rooting?
Click to expand...
Click to collapse
Yes, Netflix works after installing Magisk module liboemcrypto disabler :good:

Iceman66 said:
dxxvi said:
Hi, thank you very much for reporting it. Do you know if Netflix still works after the unlocking and rooting?
Click to expand...
Click to collapse
Netflix works after installing Magisk module liboemcrypto disabler :good:
Click to expand...
Click to collapse
I just read about that module. I post the info here for lazy people like me "Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type"
https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393

dxxvi said:
I just read about that module. I post the info here for lazy people like me "Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type"
https://forum.xda-developers.com/apps/magisk/magisk-liboemcrypto-disabler-drm-t3794393
Click to expand...
Click to collapse
The strange thing is, that after removing the module and rebooting tablet, Netflix is still working

Iceman66 said:
I managed to unlock the bootloader with the tutorial on http://androidbiits.com/root-samsung-galaxy-tab-s6-lite-sm-p610-sm-p610x-easily/, but rooting with the Magisk file failed.
I think i will try it later.
The bootlader is now unlocked, so it gives me a warning on the screen every time i boot the tablet.
I have the P610 version, only WiFi, no LTE
Click to expand...
Click to collapse
I tried using this guide and am getting a vbmeta signature failure upon flashing with odin. Did you run into any issues like that when you got your device rooted? I'm also using the P610

Same here. Not a noob despite being long time lurker and not posting. I have been rooting devices forever but this one is escaping me.
Using the guide and getting a vbmeta signature failure as well. I tries 3 various firmware versions to Magisk patch the required 4 files, but get the same error every time.
So close yet so far...
Thanks
Eric

Iceman66 said:
The strange thing is, that after removing the module and rebooting tablet, Netflix is still working
Click to expand...
Click to collapse
Yes, it does work but won't go above SD.
I bought the S6 Lite as a replacement for a Tab Pro 10.1 (SM-T520) which was running LOS 14.1. Netflix was working, but looked like crap. Downloading prior to watching improves the quality a bit, but you could see it is SD instead of HD.
I have rooted every Android devices I have had, but this time I do not want to lose the Widevine L1 certification. The SM-T520, which was in 2014 Samsung's high end tablet (>$600), only had one update from 4.4.2 to 4.4.4....rooting was the only way to move up. I hope Samsung will support this device a little better.

b0bness said:
I tried using this guide and am getting a vbmeta signature failure upon flashing with odin. Did you run into any issues like that when you got your device rooted? I'm also using the P610
Click to expand...
Click to collapse
Here is what ik did:
Starting from the step when the firmware is downloaded
Unpack the firmware with Winrar
Select the boot.img l4 file and use 7-Zip to transform it to boot.img
Transfer the boot.img file to tablet and patch the file with Magisk manager
Transfer the patched-boot.img to computer
Rename the file to boot.img
Put tablet in Bootloader-mode
Flash the boot.img with Odin 3.14
The first Block in Odin will turn green if flashing is succesfull
Now start up the tablet
In my case, a got a message that the software is damaged, i choose the option to restore to factor settings
After a few minutes the tablet booted and i installed Root-checker, rooting was succesfull

Iceman66 said:
Here is what ik did:
Starting from the step when the firmware is downloaded
Unpack the firmware with Winrar
Select the boot.img l4 file and use 7-Zip to transform it to boot.img
Transfer the boot.img file to tablet and patch the file with Magisk manager
Transfer the patched-boot.img to computer
Rename the file to boot.img
Put tablet in Bootloader-mode
Flash the boot.img with Odin 3.14
The first Block in Odin will turn green if flashing is succesfull
Now start up the tablet
In my case, a got a message that the software is damaged, i choose the option to restore to factor settings
After a few minutes the tablet booted and i installed Root-checker, rooting was succesfull
Click to expand...
Click to collapse
Thanks for the steps, got it working! To add a note for those reading the above comment. After renaming the file to boot.img, use 7z and 'add to archive' the boot.img to make it a boot.tar for Odin to be able to flash it.
Another thing that might help folks: The boot.img.l4z wasn't working with 7z to decompress the l4z. I installed l4z and moved the boot.img.l4z into the folder with l4z.exe. Then I ran the command 'l4z boot.img.l4z boot.img' in the folder where l4z.exe was located to get the boot.img.

Сan some one to upload a ready-made installation ROM file for direct flashing into Odin please? Cause I can not understand how to transfer and patch all this different parts together. I don't understand which files I need to marry each other
Please help to root with MAgisk tab6 lite (wifi only SM-P610).

Iceman66 said:
Here is what ik did:
Starting from the step when the firmware is downloaded
Unpack the firmware with Winrar
Select the boot.img l4 file and use 7-Zip to transform it to boot.img
Transfer the boot.img file to tablet and patch the file with Magisk manager
Transfer the patched-boot.img to computer
Rename the file to boot.img
Put tablet in Bootloader-mode
Flash the boot.img with Odin 3.14
The first Block in Odin will turn green if flashing is succesfull
Now start up the tablet
In my case, a got a message that the software is damaged, i choose the option to restore to factor settings
After a few minutes the tablet booted and i installed Root-checker, rooting was succesfull
Click to expand...
Click to collapse
[i followed your steps but now i get the [BLOCKED BY OEM LOCK] when using odin to flash boot.
i unlocked bootloader in developer settings. no idea what step i missed.
am using Firmware U1ATF2