Changing /system folder permissions causes bootloop - Moto G5S Plus Questions & Answers

Changing /system folder permissions causes bootloop - Moto G5S Plus Questions & Answers

Alright, maybe I did something stupid, but I don't think so...
I unlocked the bootloader, used the R2 version to remotely launch TWRP (can't get the phone to do it) and then rooted with Magisk. All as recommended.
Ad Away wouldn't work because the permissions weren't set right for system/etc/host directory. So, I used Solid Explorer to change the system directory permissions (rwxrwxrwx -R). Probably overkill, but just wanted to eliminate the issue of permissions.
Shortly after executing the command, I got an error "couldn't remount" and the phone rebooted into a bootloop, which leads to a recovery that won't launch (TWRP won't launch from the phone).
I can stop the bootloop and get into the bootloader, but can't "see" the phone in PC ADB.
Anyone have advice on how to proceed?

In bootloader or recovery it wont be ADB but Fastboot. Try "fastboot devices" and see if the pc sees it.
Also Magisk is a systemless root and they have in option in their main app to allow host file to be written to system/ect/host/.

Related

Cannot root KFHD 7

Hi everybody,
I've done all the steps from this topic http://forum.xda-developers.com/showthread.php?t=1891939. And it looks like no problems appeared during installation (ADB Interface appeared in Device Manager tree, Device can be found by adb in cmd, no any exepions or errors during cmd installation).
The only problem at the end - device is not rooted. In ES FileManager root access doesn't work. Superuser app doesn't appears in the list (but when I tried to install it for the secon time in cmd, it says that Superuser.apk is already installed).
So I've tried twice, but have't succeed. Could you please assist with the possible reason for the failture?

[Q] Help with multiple KF2 Root/Unremoveable Programs

I don't know what I've done to my KF2. I have successfully rooted the device, and have even been in fastboot for something I tried (can't remember what, just that I was trying to properly root my device). But I have about 14 programs that won't remove off my device (they only show "Add to Favorites" on my device instead of the additional option to remove from device)? I cannot get into ES File Manager and delete them. The .apk's for these files are located in the system folder, and even when I mount root in ES File Manager, I can't delete any of the files in the folder.
I also have a lot of problems with my toolbars randomly flickering on and off. But nothing I've read and tried, except for restoring the device and rerooting it again fixes this problem. I've also looked at a lot of posts that tell me to do a command with the /data/local.prop file. But I don't have this file on my kindle. I've searched for it everywhere using ES File Manager. I do have a /data/default.prop file, however. But I can't use ADB commands on that file either.
So I was advised to get a factory cable so that I can boot into fastboot. But I can use KFFIRSTAIDE to get into that successfully. Can anyone tell me what I've done to my kindle, what programs, and what commands I need in order to fix this problem? I'm not an idiot; I successfully rooted 3 KF2's and a KFHD successfully before this monster of a device came along!

herrenfam said:
I don't know what I've done to my KF2. I have successfully rooted the device, and have even been in fastboot for something I tried (can't remember what, just that I was trying to properly root my device). But I have about 14 programs that won't remove off my device (they only show "Add to Favorites" on my device instead of the additional option to remove from device)? I cannot get into ES File Manager and delete them. The .apk's for these files are located in the system folder, and even when I mount root in ES File Manager, I can't delete any of the files in the folder.
I also have a lot of problems with my toolbars randomly flickering on and off. But nothing I've read and tried, except for restoring the device and rerooting it again fixes this problem. I've also looked at a lot of posts that tell me to do a command with the /data/local.prop file. But I don't have this file on my kindle. I've searched for it everywhere using ES File Manager. I do have a /data/default.prop file, however. But I can't use ADB commands on that file either.
So I was advised to get a factory cable so that I can boot into fastboot. But I can use KFFIRSTAIDE to get into that successfully. Can anyone tell me what I've done to my kindle, what programs, and what commands I need in order to fix this problem? I'm not an idiot; I successfully rooted 3 KF2's and a KFHD successfully before this monster of a device came along!
Click to expand...
Click to collapse
Well, if you can reboot into fastboot via KFFA, than no, you don't necessarily need a fastboot cable. Have you tried removing these programs via ADB? If you ADB shell into the device, does the command "su" work? System apps can't be uninstalled the normal way, you have to manually delete them from "/system/app/" yourself. But that's weird that you can't get ES to work. Which version of ES file explorer are you using? I know the new version requires you to not only turn root explorer on, but you have to tap two radial dials to switch it from "/system" from RO (read only) to RW (read writable).
Hope this helped

Ph0enix_216 said:
Well, if you can reboot into fastboot via KFFA, than no, you don't necessarily need a fastboot cable. Have you tried removing these programs via ADB? If you ADB shell into the device, does the command "su" work? System apps can't be uninstalled the normal way, you have to manually delete them from "/system/app/" yourself. But that's weird that you can't get ES to work. Which version of ES file explorer are you using? I know the new version requires you to not only turn root explorer on, but you have to tap two radial dials to switch it from "/system" from RO (read only) to RW (read writable).
Hope this helped
Click to expand...
Click to collapse
What command(s) would I use to remove these programs? The only command I know is "ADB SHELL su". I am not an idiot at computer software, but I was absent on the day they handed out the intelligence on DOS commands.
And how would I get rid of the associated program files? Or do I just leave them on the drive?
What I would really like to do is unroot the device (which seemed to screw it up last time I tried it), restore to factory defaults as to erase all this gibberish, and restart from fresh, with a clean slate and then a clean root. Can that be done? How would I accomplish that? Like I said, it seemed that I the problems with the programs not uninstalling started with the restoring of the device, be it by unrooting it or by restoring the device to factory defaults on the kindle.
PS: yes, I can get into SU on ADB on my computer. I just don't know where to go from there. And my ES File Explorer is V. 3.0.9.0. I looked in the settings and could not find a option to change file to RW.

herrenfam said:
What command(s) would I use to remove these programs? The only command I know is "ADB SHELL su". I am not an idiot at computer software, but I was absent on the day they handed out the intelligence on DOS commands.
And how would I get rid of the associated program files? Or do I just leave them on the drive?
What I would really like to do is unroot the device (which seemed to screw it up last time I tried it), restore to factory defaults as to erase all this gibberish, and restart from fresh, with a clean slate and then a clean root. Can that be done? How would I accomplish that? Like I said, it seemed that I the problems with the programs not uninstalling started with the restoring of the device, be it by unrooting it or by restoring the device to factory defaults on the kindle.
PS: yes, I can get into SU on ADB on my computer. I just don't know where to go from there. And my ES File Explorer is V. 3.0.9.0. I looked in the settings and could not find a option to change file to RW.
Click to expand...
Click to collapse
The commands to remove bloatware and stuff (in this case, apps) would be:
Code:
adb shell
su
mount /system
rm /system/app/nameofapp1.apk
rm /system/app/nameofapp2.apk
rm /system/app/nameofapp3.apk
reboot
If a clean slate is what you want, then you can use this tool here to flash three stock Kindle partition images (boot.img, recovery.img, and system.img) to your Kindle via fastboot. The images aren't of the latest firmware, but I don't think OTA updates are disabled, so you can just let your Kindle auto update over wi-fi.
If "su" works in the ADB shell, then I guess you are rooted. I don't know what to say from there, except to backup whatever data you can and start fresh.

Ph0enix_216 said:
The commands to remove bloatware and stuff (in this case, apps) would be:
Code:
adb shell
su
mount /system
rm /system/app/nameofapp1.apk
rm /system/app/nameofapp2.apk
rm /system/app/nameofapp3.apk
reboot
If a clean slate is what you want, then you can use this tool here to flash three stock Kindle partition images (boot.img, recovery.img, and system.img) to your Kindle via fastboot. The images aren't of the latest firmware, but I don't think OTA updates are disabled, so you can just let your Kindle auto update over wi-fi.
If "su" works in the ADB shell, then I guess you are rooted. I don't know what to say from there, except to backup whatever data you can and start fresh.
Click to expand...
Click to collapse
Thanks a great deal. Where is the program to flash the three stock .img files so I can have a from-the-beginning kindle? I've already got the only thing I need from the device - a list of the third-party apps and where I downloaded them from.

herrenfam said:
Thanks a great deal. Where is the program to flash the three stock .img files so I can have a from-the-beginning kindle? I've already got the only thing I need from the device - a list of the third-party apps and where I downloaded them from.
Click to expand...
Click to collapse
...I forgot to post the link, didn't I?
Here it is: http://forum.xda-developers.com/showthread.php?t=2096888
>>>Sent from my homebuilt TARDIS running Android 4.0.3... or maybe it's a rooted Kindle Fire HD<<<

Aishon A19--have root, sort of, need to install SuperSU

Problem: I have an Aishon A19 tablet, which it is very hard to find information about. It is an RK3288 tablet running Android 5.1.1.
It is not really rooted in the normal sense. However, "adb root" works; I can get a root shell and mount /system as writeable, I can push any app I want to the device, etc.
Things that will not work:
-- I tried to put on a /system/xbin/su (from SuperSU 2.76), with mode 6755 (rwsr-sr-x) and it didn't work. I also made symbolic links to /system/bin/su and /system/xbin/daemonsu. Running it from a non-root shell in adb prints a 1 and doesn't give me root. Running it from a non-root shell on the tablet does the same thing. Running it from a root shell gives me no error, but that obviously isn't much use.
-- Running SuperSU as an app gives me the error message about "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 5....." I have no idea if it actually can't see the ./system/xbin/su or if the error message just isn't that good.
-- Trying to use "adb reboot bootloader" or getting into the bootloader using buttons doesn't work. It reboots the tablet into a blank screen, with the same vendor ID and a new product ID; however, "fastboot devices" shows nothing. This happens both under Windows and Linux, and even when run as root under Linux (thus not having to worry about udev rules). This means that I cannot install TWRP unless someone can explain to me how to install TWRP without using the bootloader.
I *can* use "adb reboot recovery" and get into the recovery menu. And as I mentioned, I can get root access to the tablet and a root shell using "adb root", and push any file I want to it.
Is it possible to use this root shell and/or recovery to install SuperSU somehow, even if I have to just copy files one at a time?
Edit: Moderators., you can lock this. Someone had the same problem in http://forum.xda-developers.com/apps/supersu/how-to-manually-update-su-supersu-file-t3238991 and I was able to folloow that, manually running the commands in update-binary.

Rooted with kingroot and replaced with SuperSu, TWRP and Xposed

Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot

8. reboot the phone
9. Go to developer options and enable the option - 'Enable OEM Unlock'
CAUTION: The next steps will soft brick your phone.
10. Run adb.exe. check connectivity using command 'adb devices'
11. Run command 'adb reboot bootloader' (this will put the phone in fastboot mode)
12. Make sure the TWRP recovery is in the same folder as the adb.exe file. (get the twrp recovery from here http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601)
13. Run command 'fastboot oem unlock'. At this point, there will be a prompt on the phone to confirm the action. Read it carefully, it clearly says that this process will wipe all data.
14. Press 'volume up' on the phone to confirm. It should take a few seconds. Then the phone will become unresponsive. Pressing volume up/down buttons or power button doesn't do anything.
15. Run command 'fastboot reboot-bootloader'
16. Run command 'fastboot flash recovery recovery.img'
17. Run command 'fastboot reboot'. When the phone is rebooting press volume up. If everything went well, This will put the phone in TWRP recovery mode.
18. When the phone enters TWRP recovery mode, it'll ask for 'write permissions'. I swiped to enable the write permissions.
19. At this point, the phone has no OS.
20. On the PC, extract the files downloaded from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip
21. With the phone connect to the PC and adb running. Run command adb devices. The phone must be listed as 'xxxxxxxxxxxxxxxxx recovery'
22. You will have to push the back up files to twrp backup using adb
23. The general command is 'adb push <local> <remote>'. This is what i did for each of the files. Be patient, this will take time.
adb push "C:\boot.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/boot.emmc.win
adb push "C:\logo.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win
adb push "C:\logo.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/logo.emmc.win.md5
adb push "C:\nvram.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win
adb push "C:\nvram.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/nvram.emmc.win.md5
adb push "C:\secro.emmc.win" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win
adb push "C:\secro.emmc.win.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/secro.emmc.win.md5
adb push "C:\system.ext4.win000" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000
adb push "C:\system.ext4.win000.md5" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win000.md5
adb push "C:\system.ext4.win001" /data/media/TWRP/BACKUPS/BLU_VIVO_XL/2016-03-05/system.ext4.win001
24. Once all the files are copied to the phone. Go to TWRP Restore option and then do a restore from the backup you just uploaded 2016-03-05.
25. After the restore is successfull and complete, TWRP will automatically ask to install 'SuperSu'.
26. Choose 'yes' and install SuperSu
27. TWRP will recover the phone and root the phone with SuperSu
If all of the above worked then install Xposed as per instructions in http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
GOOD LUCK !!! :good::good::good:

Please help me on rooting my Blu vivo XL I upgraded it to Android 6.0 and now it does not root. Please help.

hamilLewiston said:
Hi everyone. My aim here is to present a more clear Tutorial... not sure if i'll succeed, but i want to try. :good: Good Luck. Your results may be different.
A word of Caution: These steps will soft brick the phone and erase all data from your phone. Proceed with caution.
A huge thanks to:
emowing
quyvinh
jemmini
John Hale
kingroot
I refered to these posts when I was rooting:
http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
Download the BLU Vivo XL Backup from https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip . This is required to unbrick the phone.
WARNING: THE METHOD I FOLLOWED WILL ERASE ALL DATA ON THE PHONE. I really didn't care for the data on the phone so I didn't create a backup. You could google for steps to make a backup before continuing.
I did these on a Windows 7 machine. I didn't take any screenshots. This was totally random effort.
1. Ensure ADB Universal Drivers, adb.exe and fastboot.exe are installed. Use google search. I used this one http://rootjunkysdl.com/?device=Amazon Fire 5th gen. Even though it is for Amazon 5th gen Fire tablet, it worked for BLU Vivo XL
2. Enable 'Developer Options'
3. Enable 'USB Debugging'
4. Connect the phone to the computer.
If you are doing this for the first time then...
The phone will show up as a new 'cd' drive
Open that and you should see the software to install official drivers for the phone
Install the drivers using that software.
If you have previously connected the phone then it will show up like a 'USB flash storage' device with 2 partitions - Phone and SD Card5. Run 'adb.exe' in command prompt ( i assume you know how to do this)
6. Run adb devices and make sure that adb is able to communicate with the phone.
At some point, there will be a pop up on the phone with a key to enable the computer to securely connect to the phone. I don't know what this is called , but it is needed. Make sure you choose to remember this key permanently on the phone.
7. Root the phone with 'Kingroot' (Yes, this is odd, but this is required to get the TWRP recovery to load)
The reason i say this is needed is because without the root when I tried to install the TWRP recovery i got the error saying that there is no root access and therefore TWRP recovery file cannot be copied to the phone
[a] go to kingroot (dot) net and get the latest kingroot apk
try to root with kingroot. the first time i did this it didn't work. kingroot app said there is 'root' method available but it couldn't root.
[c] i uninstalled kingroot
[d] then i installed purify from play store
[e] rebooted the phone
[f] installed kingroot again and tried root again and this time it worked. (go figure...)
[g] so YMMV.
if you rooted successfully with Kingroot, then you can continue, otherwise.... try again till you can root with kingroot

Yes
Sent from my chronos_ace using XDA Free mobile app

Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.

Please help ME my phone vivo v 5 plus root How To

Gungho-sd said:
Yes, is it for marshmallow? Or yes, is it for lollipop? Or does it work for both? Please clarify.
Click to expand...
Click to collapse
From what I've read this would only work for Lollipop, as apparently kingroot no longer works on Marshmallow.

How To Guide Delete magisk module from bootlooping phone

This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- rooted phone with magisk installed
- usb data cable
First you have to boot into safe mode which will disable the loading of all magisk modules:
- Turn off the smartphone completely.
- Turn it on normally and when the MIUI logo appears, press and hold the volume down button until the system boots completely, and you see the lock screen, it should also display "safe mode" in the bottom left corner.
Next enable USB debugging on your phone and connect it to a pc, then run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes 'unauthorized' then accept the prompt for authorization on your phone.
Now open an ADB shell from your pc:
adb shell
su
cd /data/adb/modules
ls
This will list all your installed magisk modules. Remove the problematic one with:
rm -r problematic_module
Done, reboot normally!
------------------------- If su command freezes the command line------------------------------
If somehow this does not work, for example you have not granted shell superuser rights before, then you have the following backup options:
run:
adb wait-for-device shell magisk --remove-modules
This should remove all installed modules, and reboot the phone. If it does not work from safe mode, you can try it during the boot animation. (After MIUI logo comes up adb gets enabled (check with 'adb devices' command, if adb is running))
If so far nothing worked you still have a third option to recover you phone/data:
--------------------- Nothing working ---------------------------
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.

Gorg2331 said:
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- usb debugging already enabled and authenticated (preferrably)
- rooted phone with magisk installed
- usb data cable
all you have to do is connect your phone to your PC and when it shows the MIUI logo during normal boot run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes unauthorized then skip to the "Other Method" section below. If you get back nothing try to run it a couple times during boot. I am not sure when adb gets enabled during the boot but should be around the MIUI logo appearing.
next write:
adb wait-for-device shell magisk --remove-modules
This will delete all magisk modules from your phone, and it reboot it automatically. It should boot up just fine, and all your magisk modules will be deleted.
---------------- Other method --------------------------
If you really need access to the phone, but do not have adb enabled:
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Click to expand...
Click to collapse
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.

pjottrr said:
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
Click to expand...
Click to collapse
That is a great suggestion, tho you cannot use any root applications since they will not be loaded. (Even if you install them during safe mode) But it should help sidestep the adb not authorized issue possibly! I incorporated safe mode in the post.

I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone

pjottrr said:
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
Click to expand...
Click to collapse
Oh you are totally right! You can use safe mode to remove the problematic modules with rm -r. But I think this only works if you have previously granted shell superuser rights. (Since in safe mode you will not get prompts to give SU rights)

I confirm, your guide Is correct. Now i have installed a modules called magisk bootloop saver. Works fine. Do the same thing without digit the adb command.

i'd also suggest in case of BOOTLOOP (cause of bad magisk module)
you can still fastboot
Code:
fastboot flash boot boot.img
the ORIGINAL boot.img of your actual ROM ( so everytime you root keep a copy of the original BOOT.IMG)
in that case you'll be able to reboot your phone ( without root ) and without losing any data !

yes, all these suggestions are good and 100% work! great thread

Booting into Safemode, adb shell and deleting the bad module worked great, thank you!

Database Develop

welcome