I am on msgisk rooted and patched Android 9 ASF3 based on the guide jn this thread.
Can somebody list the steps to flash Android 10 magisk root?
The bootloader on the North America snapdragon variants (SM-G973U/W) are not unlockable. This is only for the exynos and the Hong Kong snapdragon variant (SM-G9730)WilI this method work on the Sm-G975u? Has anyone tried it
It's definitely a much more involved process than any other phone I've ever rooted. If you want to root yours, I suggest reading the guide thoroughly multiple times as well as reading through this thread to see the issues and solutions others have already dealt with.Can people with experience with Magisk on S10 tell me how much of a burden the Samsung flashing process is? I can follow the steps, but I'm a bit afraid of all the hurdles you need to go through and the bricking risks.
Great info, thanks a lot for taking the time to share. I still have a few basic questions.It's definitely a much more involved process than any other phone I've ever rooted. If you want to root yours, I suggest reading the guide thoroughly multiple times as well as reading through this thread to see the issues and solutions others have already dealt with.
There is little to no risk of bricking as you should always be able to get back into download mode, but plan on losing everything on your phone until you're completely finished rooting and everything is working properly.
When I first got mine, it took me about 6 hours and 4 times re-flashing stock through Odin before I finally got it and I'm very experienced with Android and rooting. The process and instructions have definitely improved, but it's still a bit painful the first time. Once you get it rooted though and you understand the process, things such as updating while keeping root are pretty straightforward.
The biggest thing I would say from my own experience is to use a high quality USB cable and verify the firmware files at each step of the process. Files can get corrupted during transfer and banging your head against a wall trying to flash a file you didn't know got currupted is frustrating and exhausting.
In case it helps once you get to the AP patching part of the guide, here's my process for patching the AP file:
1. Get SHA1 checksum for newly downloaded AP file on your computer (I use 7-zip)
2. Transfer the AP file to your phone using ADB push (you can transfer through any means but ADB push is much more reliable to avoid corruption)
3. Get SHA1 checksum for AP file on phone and ensure it matches the checksum from your computer (I use solid explorer)
4. Patch the AP file with Magisk manager
5. Get the SHA1 checksum for the new magisk_patched.tar file (again, I use solid explorer)
6. Transfer to PC using ADB pull (as above, you can use any means to transfer but ADB is more reliable)
7. Get SHA1 checksum of magisk_patched.tar on PC and ensure it matches the checksum from the phone (again, I use 7-zip)
8. Follow the rest of the flashing process
Great info, thanks a lot for taking the time to share. I still have a few basic questions.
Thanks. I think I'll go down the TWRP route, maybe after having just the Magisk scenario clear. I can't really live without TWRP backups and also I can use TWRP to recover from Magisk fu*kups using Magisk Manager for Recovery Mode (mm). The reason I want to root is actually my current stock setup being messed up after the update to 10, freezing all the time.1. You will need to do the key combo each time you reboot to keep root as Magisk resides in recovery so it will not be loaded unless the system is booted to recovery. There are a few other options though. One is to use an app that can reboot straight to recovery. Magisk manager has a reboot to recovery option in the three dot menu on the modules page. If you have Xposed, you can use Firefds to customize the power menu and replace reboot with a reboot to recovery button. If you are on One UI 2.0 (Android 10), I don't believe Firefds is working yet.
Another thing to note on this, bluetooth pairings will not persist after reboots with Magisk unless you install the libsecure_storage Magisk module.
2. Multidisabler is only necessary if you will be using TWRP. On that note, you should decide at the beginning if you want to use TWRP or not because adding TWRP into the mix requires a data wipe the first time. It adds another layer of complexity and will most likely cause you some more confusion and headache so be aware of that. Adding TWRP into the mix probably doubled my first setup time due to the lack of good information at the time but there is a lot more info out there now.
Thanks. I think I'll go down the TWRP route, maybe after having just the Magisk scenario clear. I can't really live without TWRP backups and also I can use TWRP to recover from Magisk fu*kups using Magisk Manager for Recovery Mode (mm). The reason I want to root is actually my current stock setup being messed up after the update to 10, freezing all the time.
It's going to be interesting to learn how both Magisk and TWRP can live alongside in the recovery partition...
Those are the exact same reasons I went the TWRP route. Definitely read all the documentation multiple times but here's a basic rundown of the steps for TWRP. Keep in mind what I said before about checksumming every file before and after transferring.
1. Transfer AP and TWRP img file to phone (ensure TWRP kernel base matches firmware version eg. latest TWRP v3.3.1-100 is based on BSKO so that should only be flashed with BSKO firmware)
2. Patch both files with Magisk
3. Transfer back to PC
4. Rename magisk_patched.img (TWRP) to recovery.img
5. Open magisk_patched.tar in 7-zip
6. Drag and drop the TWRP recovery.img that you renamed into the 7-zip window to overwrite the stock recovery.img in the AP tar file
7. Open Odin and uncheck the auto-reboot setting
8. Flash CSC, CP, BL, and patched AP all together
9. Once flash is successful, boot into TWRP by pressing and holding power+vol up to get out of download mode then as soon as the screen turns black, hold power+vol up+bixby and keep holding them until you're booted into TWRP
10. Flash multidisabler (per the multidisabler post, you can rename it to add _btfix to the end to fix bluetooth pairings without needing the Magisk module)
11. Factory reset in TWRP to wipe data which will finalize removing FBE (encrypted /data)
12. Reboot to recovery using the option in TWRP and just let it boot up
Keep in mind that's a very rough overview and there's a chance I misspoke about something.
Does this this Root and TWRP work on G973N?
I don't know. I have not problems with last firmware. Last firmware I have updated, not installed.yes i can use magisk and select reboot in recovery but in case i want to shut off my phone or if it shutting down, i should reflashing firmware, instead before it was enought turning on phone with something plugged in usb
Got a S10, rooted with magisk, no TWRP installed.
I want to update to the latest Firmware with magisk, but without wipe everything , is it possible?
What are the steps please?
# dd if=/dev/block/sda15 of=recovery.img
$ tar f magisk_patched.tar --delete recovery.img $ tar rf magisk_patched.tar recovery.img