Related
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?
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.
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
Hi guys,
Sorry if it is a silly question but I have been trying to get the information with no results.
I have a Samsung galaxy s10+ SM G975F... It is binary 15 and when I use Odin, I can get a newer binary than 14... I want to downgrade from Android 12 to 11... The Batery drain is insane now...
Odin always said that the Binary is incorrect and can't flash any diferent rom
Any ideas or suggestions? Can I install a custom Rom at least?
Thanks and I hope you can help me.
Downgrading Samsung phones is pretty much impossible without unlocking bootloader some funky playing around (manually flashing system, boot, and probably way more) and a TON of luck. I could help you better with an older android Version as i dont have much experience with android 9 or newer.
Arash2803 said:
Hi guys,
Sorry if it is a silly question but I have been trying to get the information with no results.
I have a Samsung galaxy s10+ SM G975F... It is binary 15 and when I use Odin, I can get a newer binary than 14... I want to downgrade from Android 12 to 11... The Batery drain is insane now...
Odin always said that the Binary is incorrect and can't flash any diferent rom
Any ideas or suggestions? Can I install a custom Rom at least?
Thanks and I hope you can help me.
Click to expand...
Click to collapse
Bump same question my device is 16 and binary i want to install is 14? help
no, you CANT downgrade the binary but you can try make a rom with older version of android but expect bugs and a lot of issues due the bootloader
i got s10+ "G975FXXUFHVE1" i cant downgrade also im new to this whole stuff i really need help
🥹
Ch_ali134 said:
i got s10+ "G975FXXUFHVE1" i cant downgrade also im new to this whole stuff i really need help
Click to expand...
Click to collapse
Same boat here... S10+
i'm on G975FXXUGHVJ5 (android 12), so locked to bin 16. Wanted to go back to G975FXXSEFUL1 (android 11) So I could use my GearVR again, but that is bin 14... Backporting GearVR is out of the question... So i'm left with a feature downgraded p.o.s.. and this was the last moddel to support GearVR...
Pandoriaantje said:
Same boat here... S10+
i'm on G975FXXUGHVJ5 (android 12), so locked to bin 16. Wanted to go back to G975FXXSEFUL1 (android 11) So I could use my GearVR again, but that is bin 14... Backporting GearVR is out of the question... So i'm left with a feature downgraded p.o.s.. and this was the last moddel to support GearVR...
Click to expand...
Click to collapse
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Pandoriaantje said:
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Click to expand...
Click to collapse
Pandoriaantje said:
From what i've read, its mainly dowload mode/odin that does the check and blocks the downgrade. But what about converting an official samsung update to a flashable twrp/recovery zip? I already have a fully magisk rooted stock android 12 rom, i just want do downgrade the system to stock android 11 (rooted) for GearVR. I don't think actually loading the kernel/system is blocked at the bootloader lvl right?
Maybe with a rom kitchen it could be possible to convert to a flashable zip?
Click to expand...
Click to collapse
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
NigrumTredecim said:
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
Click to expand...
Click to collapse
NigrumTredecim said:
its only blocked when the bootloader is locked, you can just slap the files into an unsigned tar and it will flash fine with odin (bootloader cant be downgraded tho), but you will have to unlock bootloader and the binary version wont be downgraded just ignored
Click to expand...
Click to collapse
My bootloader is already unlocked. haven't tried downgrading through ODIN, as this is my Daily driver Phone, but i'dd love to get GearVR back. The phone is fully unlocked, with custom kernel, as per my Signature ... So (according to you) I should be able to downgrade to G975FXXSEFUL1 without error through ODIN? despite everyone claiming it can't be done? (I realise that the bootloader binary can't be downgraded, but ODIN/Download mode checks everything. Bootloader, kernel, etc.. no?)
What do you mean with "unsigned tar"?
side question: What about kernel? could I reuse/reflash (from TWRP) my current kernel (Ambasadii HVJ5, android 12) as it is pre-patched with latest magisk, on an older android 11 rom?
Pandoriaantje said:
My bootloader is already unlocked. haven't tried downgrading through ODIN, as this is my Daily driver Phone, but i'dd love to get GearVR back. The phone is fully unlocked, with custom kernel, as per my Signature ... So (according to you) I should be able to downgrade to G975FXXSEFUL1 without error through ODIN? despite everyone claiming it can't be done? (I realise that the bootloader binary can't be downgraded, but ODIN/Download mode checks everything. Bootloader, kernel, etc.. no?)
What do you mean with "unsigned tar"?
side question: What about kernel? could I reuse/reflash (from TWRP) my current kernel (Ambasadii HVJ5, android 12) as it is pre-patched with latest magisk, on an older android 11 rom?
Click to expand...
Click to collapse
unpack the stock tar.md5 using 7zip or some tool and repack it into a normal .tar, to my knowledge odin only checks the binary of original unmodified tar.md5 files like they come from samsung (my newest samsung is from 2017 so that may not be true anymore but it should still be)
for the kernel question i dont really know as i run android 8 with a modded stock kernel
NigrumTredecim said:
unpack the stock tar.md5 using 7zip or some tool and repack it into a normal .tar, to my knowledge odin only checks the binary of original unmodified tar.md5 files like they come from samsung (my newest samsung is from 2017 so that may not be true anymore but it should still be)
for the kernel question i dont really know as i run android 8 with a modded stock kernel
Click to expand...
Click to collapse
Any updates on this process, i would also give it a try if it works out.
crucknova said:
Any updates on this process, i would also give it a try if it works out.
Click to expand...
Click to collapse
not really, my newest samsung is an a5 2017 (where this process works fine)
but it should work, downside is that your bootloader needs to be unlocked as you build you own unsigned flashfile
EDIT: i cant get it to work anymore even tho thats how i did it the first time, flashing using a custom recovery will work tho if thats an option for you
QUICK TUTORIAL
1: download your desired stock firmware
2: extract AP****.tar.md5 (basically just a normal tar with signatures at the end use 7zip or any other program you know)
3: repack boot.img system.img vendor.img (vendor.img may not be there depending on the android version) into an uncompressed tar (using 7zip or any other program)
4: flash said tar using odin
you could also manually flash the image files using heimdall without repacking into an tar
NigrumTredecim said:
not really, my newest samsung is an a5 2017 (where this process works fine)
but it should work, downside is that your bootloader needs to be unlocked as you build you own unsigned flashfile
QUICK TUTORIAL
1: download your desired stock firmware
2: extract AP****.tar.md5 (basically just a normal tar with signatures at the end use 7zip or any other program you know)
3: repack boot.img system.img vendor.img (vendor.img may not be there depending on the android version) into an uncompressed tar (using 7zip or any other program)
4: flash said tar using odin
you could also manually flash the image files using heimdall without repacking into an tar
Click to expand...
Click to collapse
Thanks for the reply and a quick tutorial
NigrumTredecimi have an s10 plus and a m30, im a bit hesirtant on trying it on s10 plus, but i will try the process on m30, as i need to downgrade it as well!
can you give me an more detailed tutorial on the 3rd step which includes repacking the boot.img system.img vendor.img, should i delete everything except these 3 and repack or what!
Thank you
download lz4 https://github.com/lz4/lz4/releases and drag and drop your .img.lz4 files onto the exe to get the img files
AAAAAAAAAAAAAAA i cant get it to work even though thats how i did it before already, using a custom recovery to flash the images will definitely work, so thats an option for you thats easier just unpack the .img.lz4 and skip the rest and flash using a custom recovery
just leaving the rest here in case somebody wants to find where i made the oopsie here
select your files in 7zip and then click the green plus in the top left corner
then pick tar in the format dropdown menu and then click ok to create the archive
then open said tar with odin
NigrumTredecim said:
download lz4 https://github.com/lz4/lz4/releases and drag and drop your .img.lz4 files onto the exe to get the img files
AAAAAAAAAAAAAAA i cant get it to work even though thats how i did it before already, using a custom recovery to flash the images will definitely work, so thats an option for you thats easier just unpack the .img.lz4 and skip the rest and flash using a custom recovery
just leaving the rest here in case somebody wants to find where i made the oopsie here
select your files in 7zip and then click the green plus in the top left corner
then pick tar in the format dropdown menu and then click ok to create the archive
then open said tar with odin
Click to expand...
Click to collapse
if i do a custom recovery the knox would trip and i wont be able to use the samsung pay. which i use a lot for payments. And thanks for your support dude.
Hello all !
I followed this tutorial on how to root my Galaxy S10+ : https://www.thecustomdroid.com/samsung-galaxy-s10-root-guide/ but there are 2 problem:
1st: At the Step6, the file name isn't exactly magisk_patched.tar but magisk_patched-25200_xLm0q.tar. Is this a problem ?
2nd: at Step 10, when I want to exit the Download Mode (Volume Down and Power button for over 7s), the phone get in a boot-loop (which I found online that it means the phone can't find a proper OS to boot on)
How can I know what I'm doing wrong ? I have a doubt on the stock firmware I found on Frija:
my phone is a G975F-DS and there is no "G975F-DS" but only "G975F"
I can't use Phone Info Sam because the link is broken/the app doesn't exist anymore ? When I type *#1234# the CSC code is G975FOXMGHWA3. I searched OXM but couldn't find anything on Frija so I search and I've read that OXM is not the correct CSC Code so I went to Software INFO and in the Service provider software version it's written ...SM-G975F_OXM_XSP... so I chose the XSP firmware and did the root with it until the phone boot-looped.
My service provider now in KT in Korea, does it make a difference ?
Thank you for reading me
Edit: I found Phone INFO ★SAM★ 3.8.5 By vndnguyen on APK Mirror and it says " Firmare's CSC Code: XEF" and "Active CSC Codes: XSP". Which one is correct ?
Reflash the stock firmware, then flash TWRP and flash Magisk in TWRP.
First Flash Offical firmware (BL,AP,CP,CSC)
Then Patch AP file by magisk
windows4droid said:
First Flash Offical firmware (BL,AP,CP,CSC)
Then Patch AP file by magisk
Click to expand...
Click to collapse
Isn't it the same as Step 6 from the tutorial ?
V0latyle said:
Reflash the stock firmware, then flash TWRP and flash Magisk in TWRP.
Click to expand...
Click to collapse
May I ask a trustful tutorial on how to do it please ?
Constantine1711 said:
Isn't it the same as Step 6 from the tutorial ?
May I ask a trustful tutorial on how to do it please ?
Click to expand...
Click to collapse
The firmware must be flashed first
Then you make a patch from the AP file
The baseband of the device must be identical to the firmware from which the root file is made
windows4droid said:
The firmware must be flashed first
Then you make a patch from the AP file
The baseband of the device must be identical to the firmware from which the root file is made
Click to expand...
Click to collapse
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
V0latyle said:
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
Click to expand...
Click to collapse
Yes, you can try twrp
[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S10/e/+/5G Exynos
Official TWRP 3.6.1-* For Galaxy S10/e/+/5G Only for exynos variants - G970F / G973F / G975F / G977B (Europe - Global, Single/Dual-SIM), G970N / G973N / G975N / G977N (South Korea) Disclaimer I am not responsible for bricked devices, dead SD...
forum.xda-developers.com
Edit: see below
V0latyle said:
Patching the AP.tar doesn't always work.
@Constantine1711 just flash the original firmware in Odin, then follow the guide in the TWRP thread for this device to install TWRP. Once you have TWRP installed, flash Magisk in TWRP. No need to rename it to .zip, just install it like you would any other zip
Click to expand...
Click to collapse
I did that and now my Phone Status is Custom but Root Checker says Root access is not properly installed.
Constantine1711 said:
I did that and now my Phone Status is Custom but Root Checker says Root access is not properly installed.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?
V0latyle said:
What version of Magisk are you using and where did you download it from?
Click to expand...
Click to collapse
I got the v25.2 from magiskmanager.com/
Constantine1711 said:
I got the v25.2 from magiskmanager.com/
Click to expand...
Click to collapse
NEVER download Magisk from anywhere but the official Magisk repo. That is the ONLY trustworthy source; any other source is not affiliated with the project and may be malware.
V0latyle said:
NEVER download Magisk from anywhere but the official Magisk repo. That is the ONLY trustworthy source; any other source is not affiliated with the project and may be malware.
Click to expand...
Click to collapse
Oops ... what's the risk ? Should I reset my phone again ?
Constantine1711 said:
Oops ... what's the risk ? Should I reset my phone again ?
Click to expand...
Click to collapse
The risk is malware, like a virus. If you've had questionable apps with root access, I would absolutely recommend you perform a clean factory flash.
V0latyle said:
The risk is malware, like a virus. If you've had questionable apps with root access, I would absolutely recommend you perform a clean factory flash.
Click to expand...
Click to collapse
Is it possible to check if an apk is different from the github one ? Like a code checker or something. I'm so tired of reseting my phone it's been a week I try to root it ...
Otherwise, maybe I'll try with an other tutorial.
The Proper Way to root your S10 (10+,10e) Device and get it Right! Tipps & Tricks
Hi Guys :cowboy: Today I want to bring some simple and effektive Insights on proper Device & Software Management and also about Mistakes on the Way and Solutions! :good: ;) So make yourself comfortable and check this out! It will really help...
forum.xda-developers.com
Is this one a good one ?
Is it just me getting older or rooting a device got much more complicated than before ? (I use to root PSP/playstation2 and 3 in the past)
I missed having full control of my device so I thought to root my phone but it's seems so complicated for so little reward
Edit: I tried to follow the official Magisk tutorial but I failed so I'm just gonna stop trying here. Sorry for wasting your time guys !