Develop Bugs

[HOW-TO] How to SuperSU the Moto G5 Plus (Rooting Guide)

Hey guys,
Thanks to @vanche for the modified kernel and twrp recovery and @fayiaz for the guide on how to root and @Johny Cipel for the original guide and everyone else like
@topjohnwu
@santhosh
@abdyasar
For the original twrp, root and other stuff.
Now thats out of the way
Requirements:
-Unlocked Bootloader (Moto G5 Plus with offers from Amazon won't have unlockable bootloaders but if you buy the standard model from them then you'll be fine)
-Vanche's Modified TWRP from here (http://cloud.vache-android.com/Moto/potter/TWRP/twrp-3.1.0-0-potter.img)
- Vanche's Modified Boot Kernel from here (http://cloud.vache-android.com/Moto/potter/root/potter_boot_test7.img)
- Vanche's Wifi Patch because wifi will stop working after flashing the modified boot kernel (http://cloud.vache-android.com/Moto/potter/root/wlan_custom.zip)
- Chainfires Root http://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
--- If you already have TWRP on your phone, the one by Santosh, you must flash the one made by Vanche or it wont work and you can just download the recovery image and flash it via twrp by toggling the flash zip button on the twrp recovery install menu.
1.. Download all the three files then boot your phone into bootloader mode by holding Volume Down + Power
2. Connect your phone to your PC and then open the adb terminal wherever adb is located open command prompt at that folder
3. Place the recovery image and boot image where the adb terminal folder is located
4. Fastboot flash recovery first and then boot into recovery at least once then reboot into bootloader fastboot flash boot the modified boot image.
5. Boot into the system (May take a while for the first time after flashing the boot image).
6. Place the wlan_custom.zip into your phones internal storage
7. Boot back into recovery and then flash the zip this time
8. Then download and flash the SR3 Super Su from above using recovery and you should have root!!
Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.

wiping?
do we need to wipe storage in this process?

yourtitan said:
do we need to wipe storage in this process?
Click to expand...
Click to collapse
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once

Awesomeslayerg said:
It shouldnt, But if you cant boot then you need to flash the no-verity crypt zip once
Click to expand...
Click to collapse
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.

wifi not working after supersu root
wifi not working mate.. Flashed custom zip .. No use..

Dhan... said:
wifi not working mate.. Flashed custom zip .. No use..
Click to expand...
Click to collapse
Did you correctly flash vanche TWRP and boot image? Because you're supposed to do that first and then flash the wifi zip..

yourtitan said:
thanks for the reply. but i have several data in my phone. can i just unlock bootloader and root as instructed above without wiping my storage? its a task to take backup of everything. thanks in advance.
Click to expand...
Click to collapse
The phone will wipe as soon as you unlock the bootloader so best to back up first.

Sorry but what's the differences beetwen this method and magisk?

Awesomeslayerg said:
Requirements:
-Unlocked Bootloader (Amazon bought Moto G5 Plus dont have unlockable bootloaders so your out of luck)
Click to expand...
Click to collapse
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.

Dahenjo said:
Only the 'Prime Exclusive - With Offers and Ads' Amazon models don't have an unlockable bootloader, while the 'Standard Version' models can definitely be unlocked. You probably should clarify that or some will think that they can't buy from Amazon and unlock/root the phone.
Click to expand...
Click to collapse
Will do thanks

The "Magisk method" didn't give me privileges on /system, there are some things I can do and others do not, this method gave me full root access like in the other MotoG devices? And the safetynet check fails too?
Anyway thank you very much!!

What's going to be different than magisk root?

Videon Tutorial [SuperSu]
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE

gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to
gr8 work mate.....I'm rooted with Magisk...wanna go with super su........do i need to reflash above said recovery?
will it wipe my current data on both storage?
Pls guide..........How is Moto app working with super su?
Shamith08 said:
Guys I Found This Video Tutorial For This Thread On Roting Moto g5 Plus With Super Su ------- And Worked Great For Me----- link:-
https://www.youtube.com/watch?v=TV78iWxQrRE
Click to expand...
Click to collapse

Thank you so much! This worked! Why would WiFi stop working with this boot image?

I'm
donjuro said:
Thank you so much! This worked! Why would WiFi stop working with this boot image?
Click to expand...
Click to collapse
I don't know why but you have to flash WLAN in order to get it to work

Twrp backup can't worked
I successfully rooted my moto g5 plus mobile. And TWRP INSTALL Latest supersu via. But sdcard card backup can't worked. Why can't work sdcard in twrp? I think this twrp unofficial so not supported sdcard process. Please help me. How to work sdcard backup twrp. I try mount sdcard. But can't mount sdcard. Totally I'm very tired. Please help me.

Does someone have the img file for G5/Cedric?

Awesomeslayerg said:
...Safety net may break so if you wanna use Snapchat or any other apps that use safety net make sure you login first then root. You can't logout or else you'll have to unroot and log back in.
Click to expand...
Click to collapse
Do you think that will be fixed soon with a newer version of SuperSU, or some "root hider" apps? The idea of running a phone without root is absurd/offensive/rediculous IMO, but I don't want to be denied the ability to run certain apps because the developers have the rediculous idea that running without root should be "OK" to ordinary users? This idea is extremely offensive to me!!!

Guys, I wonder why the OP is "Account currently disabled"? I hate running without root, but, it seems a bit early and not all the problems have been worked out yet, such as TWRP not accessing SDCARD yet - I think I was a little premature buying my Moto G5 Plus as we don't really have "stable" release custom ROMs or fully functioniong TWRP and to even root we have to rely on some not well known sources for kluged files to make SU work?

TWRP 3.2.3-1 for Pixel 2 XL

Note: Do not use if you have multiple users (including a guest user)
Lots more information here: https://plus.google.com/u/1/+DeesTroy/posts/i33ygUi7tiu
I strongly recommend that kernel developers start building the touch drivers into the kernel instead of depending on modules to ensure a fully functional TWRP since recovery is now part of the boot partition.
Be careful about what you install on your device as far as kernels and ROMs go. I think there is a high potential for losing the ability to decrypt because of the OS and patch level tags that are included in the boot image and the anti-rollback features that Google has implemented.
MTP does not work in TWRP on the Pixel 2 and will not work until we have time to update the TWRP MTP implementation. You may still use adb to push and pull files.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
Pixel 2:
https://twrp.me/google/googlepixel2.html
https://dl.twrp.me/walleye/
Pixel 2 XL:
https://twrp.me/google/googlepixel2xl.html
https://dl.twrp.me/taimen/

Reserved!

Awesome to see the progress here, thank you for working on it and dealing with all the impatient requests. Will definitely be keeping an eye on this thread ?

Hurray for progress!

fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Edit: The logs are posted here:
https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148/post74363478

This makes me smile. Thanks Troy and TeamWin!

Thanks Dees_Troy and Team for getting this started!

Things are looking up, thanks guys!

Awesome to see action with this phone! Thanks!!

You da man

sharkie405 said:
fastboot boot /path/to/twrp.img reboots into TWRP, but it never goes past the teamwin splash screen. I am able to reboot the phone normally after that, so no biggie.
I don't have time now to mess with figuring out how to get you logs, but I'll do that later this evening. Just wanted to give you a quick "what happened when I tried it."
And THANK YOU for working on this for us so quickly!
Click to expand...
Click to collapse
Here are those logs.

Nice! Great to see the progress

Thanks for the progress guys. Has anyone tried flashing root from TWRP yet? I wonder if this process would work, if we used this modded TWRP... https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324

sharkie405 said:
Here are those logs.
Click to expand...
Click to collapse
Did you try unlocking critical?

cwalker0906 said:
Did you try unlocking critical?
Click to expand...
Click to collapse
Yes, I've already unlocked critical.
Sent from my Pixel 2 XL using XDA Labs

Great to see...this is the start!

I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.

bggold said:
I unlocked the bootloader without critical and was able to bootloader into twrp. No just figuring out a way to get root.
Click to expand...
Click to collapse
From here we should be able to push ADB shell comands to edit build.prop right?

I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!

chazall1 said:
I just fastboot booted your .img. All functioning as expected except for the issues that you indicated.
Rebooted back to system without any issues.
Thank You Great Job!
Click to expand...
Click to collapse
Have you unlocked critical?
Sent from my Pixel 2 XL using XDA Labs

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

Bootloop on Oreo, plus, anyone has stock image of Oreo

So i sideload the Oreo on Nougat. Everything was fine. Then i rooted with magisk and it is no stuck in bootloop. The only way to boot up the device is to go to bootloader screen and hit start. I flashed an image found on this forum and nothing changed. I believe i need a new image ?
Thank you

There is an Oreo .xml.zip, but I don't know for which versions it is:
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/

Gigahyperprime1 said:
So i sideload the Oreo on Nougat. Everything was fine. Then i rooted with magisk and it is no stuck in bootloop. The only way to boot up the device is to go to bootloader screen and hit start. I flashed an image found on this forum and nothing changed. I believe i need a new image ?
Thank you
Click to expand...
Click to collapse
The solution is in this post -- https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
The user Rafikowi give the solution in that post. - "Good Luck" :good:
UPDATE 20.04.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 16.0 or 16.2 (does not matter) AGAIN (yes.).
3. Flash f2fs-loopback-bug-workaround-2018.1.31.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me last night).

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.

Bootloop in logo S9

RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up

Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961

https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me

S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q

viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.

it stucks for me on the samsung logo

aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod

omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it

viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?

Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.