Related
Trying to utilise the new method of installing v14.0 of MAGISK.
I've installed Magisk Manager and got a copy of my boot.img, I've patched within the app and flashed the patched_boot.img.tar via ODIN and got the Green PASS.
This however after a couple of vibrations just hangs the phone at the BootAnimation when restarted.
I've reflashed the stock boot.img and my device boots correctly.
Also posted this under the Official Q&A Thread:
Samsung G935F Samsung S7 Edge on Three UK FW
I've tried using the new method to create patched_boot.img.tar to flash with ODIN.
ODIN flashes successfully but device just hangs at boot animation.
Reboot and flashed stock boot.img and boots fine.
Opened up New Issue on @topjohnwu GitHub here: https://github.com/topjohnwu/Magisk/issues/356
I've seen these quotes:
Quote:
Samsung devices are quirky. The normal installation instructions are in the release thread. If you're device requires a special installation process you're probably better off checking in your device's forum.
Quote:
No. You have to unlock the bootloader since you need to be able to fish a modified boot image. Only exception are Samsung devices since these can be flashed with ODIN... Which most likely will exclude the locked down is versions
With v14.0 and this method being so new I can't find anything on a special installation process as I want to install using new method only. Any advice or anything further I can supply to help Troubleshoot.
Click to expand...
Click to collapse
I had the same issue - the only way is to wipe the data and cache in recovery after installing the new boot.img (its because the phone detects the new boot.img and so prevent access)
meddylad said:
I had the same issue - the only way is to wipe the data and cache in recovery after installing the new boot.img (its because the phone detects the new boot.img and so prevent access)
Click to expand...
Click to collapse
Thanks meddylad will try that!
Hi...just a followup - did it work?
any news ?
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?
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!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8
xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?
xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯
xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img
magisk 24 is ****, it's bricking MediaTek powered Samsung phones
Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.
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 !