Database Develop

Magisk patched_boot image vs TWRP re setprop

An unusual question;
I have a need to do 'adb shell setprop persist... '
I can do that after flashing TWRP and booting it. Works fine.
I assumed (wrongly) that 'fastboot boot patched_boot.img' would allow me to run the same adb command. I realize that the patched boot images are made to then further install Magisk Manager, systemless root, etc.
My question is there any way to get the patched_boot.img to allow a simple adb setprop command, like twrp does? (without going the full root route).
Thanks very much for taking the time to respond to my obviously not very knowledgeable question about Magisk.

AsItLies said:
An unusual question;
I have a need to do 'adb shell setprop persist... '
I can do that after flashing TWRP and booting it. Works fine.
I assumed (wrongly) that 'fastboot boot patched_boot.img' would allow me to run the same adb command. I realize that the patched boot images are made to then further install Magisk Manager, systemless root, etc.
My question is there any way to get the patched_boot.img to allow a simple adb setprop command, like twrp does? (without going the full root route).
Thanks very much for taking the time to respond to my obviously not very knowledgeable question about Magisk.
Click to expand...
Click to collapse
If you have Magisk working, use a module to do that setprop for you. I believe "MagiskHide Props Config" in the Magisk repo could do that trick.

AsItLies said:
An unusual question;
I have a need to do 'adb shell setprop persist... '
I can do that after flashing TWRP and booting it. Works fine.
I assumed (wrongly) that 'fastboot boot patched_boot.img' would allow me to run the same adb command. I realize that the patched boot images are made to then further install Magisk Manager, systemless root, etc.
My question is there any way to get the patched_boot.img to allow a simple adb setprop command, like twrp does? (without going the full root route).
Thanks very much for taking the time to respond to my obviously not very knowledgeable question about Magisk.
Click to expand...
Click to collapse
You want to patch a boot image, so that it sets the property on boot that you wanted it to, right ??
If that's the case, you can directly use MagiskBoot to unpack the boot image and then ramdisk, then you can create an init.*.rc script to do your custom tasks and import that in init.rc where you need that to be applied.

JayminSuthar said:
You want to patch a boot image, so that it sets the property on boot that you wanted it to, right ??
If that's the case, you can directly use MagiskBoot to unpack the boot image and then ramdisk, then you can create an init.*.rc script to do your custom tasks and import that in init.rc where you need that to be applied.
Click to expand...
Click to collapse
Looking more carefully at doing this right now. Yes, it certainly sounds like it would do what's needed. Will post back with results. Thnx for the pointing out this possibility.

Help. Deleting magisk modules no root.

I was on magisk rooted pixel 3 Android 10, no twrp. After flashing a magisk module, it boot, but couldn't get into desktop, kind of bootloop. So i fastboot stock boot img and boots, but lost root previleage.
I want to remove the said magisk module, with no root and no twrp.
Any suggestions???
Thanks.

evanxyj said:
I was on magisk rooted pixel 3 Android 10, no twrp. After flashing a magisk module, it boot, but couldn't get into desktop, kind of bootloop. So i fastboot stock boot img and boots, but lost root previleage.
I want to remove the said magisk module, with no root and no twrp.
Any suggestions???
Thanks.
Click to expand...
Click to collapse
While the phone is in the bootloop connect the phone to your PC and open cmd, cd to the folder where you have adb drivers and type:
adb wait-for-device shell magisk --remove-modules
This will remove all the modules and you should exit the bootloop

visa91 said:
While the phone is in the bootloop connect the phone to your PC and open cmd, cd to the folder where you have adb drivers and type:
adb wait-for-device shell magisk --remove-modules
This will remove all the modules and you should exit the bootloop
Click to expand...
Click to collapse
Thanks. Actually my phone booted into system, it said "phone is starting"and kept that forever, but it never went into desktop. Wonder whether or not your script will work...

evanxyj said:
Thanks. Actually my phone booted into system, it said "phone is starting"and kept that forever, but it never went into desktop. Wonder whether or not your script will work...
Click to expand...
Click to collapse
It is not necessary to enter the desktop. I have a Huawei and my phone was in a bootloop showing Huawei logo. I put this script in the cmd while the phone was in huawei logo and I was able to exit the bootloop by losing all magisk modules.

visa91 said:
It is not necessary to enter the desktop. I have a Huawei and my phone was in a bootloop showing Huawei logo. I put this script in the cmd while the phone was in huawei logo and I was able to exit the bootloop by losing all magisk modules.
Click to expand...
Click to collapse
I'll try next time I ****ed up my system again. Thsnks.

visa91 said:
It is not necessary to enter the desktop. I have a Huawei and my phone was in a bootloop showing Huawei logo. I put this script in the cmd while the phone was in huawei logo and I was able to exit the bootloop by losing all magisk modules.
Click to expand...
Click to collapse
Delete. Misguide

evanxyj said:
U can try this one
https://forum.xda-developers.com/pixel-3/themes/magisk-modules-disabler-booting-magisk-t3967433
Click to expand...
Click to collapse
No. Boot images are device specific, and that's a Pixel 3 boot image that won't work on @visa91's Huawei.

Didgeridoohan said:
No. Boot images are device specific, and that's a Pixel 3 boot image that won't work on @visa91's Huawei.
Click to expand...
Click to collapse
My mistake.

Uninstall magisk (+modules) without TWRP (and without root)?

I have a OnePlus 7T, which I rooted by booting to magisk_patched_boot.img (since there is no TWRP for OnePlus 7T yet).
I installed some module which caused bootloop. I recovered from bootloop by dirty flashing stock rom (just the boot.img).
Bootloop resolved. Root gone.
Now if I boot into magisk_patched_boot.img, it gets stuck on bootloop again. So I am assuming the magisk module files are still present.
How do I get rid of those modules?

Try here:
https://didgeridoohan.com/magisk/Ma...agisk_functionality_bootloop_loss_of_root_etc

Didgeridoohan said:
Try here:
https://didgeridoohan.com/magisk/Ma...agisk_functionality_bootloop_loss_of_root_etc
Click to expand...
Click to collapse
Worked like a charm, thank you so much!!
If anyone else is suffering through the same issue, while in bootloop, enter the following command in command prompt (in adb directory)
Code:
adb wait-for-device shell magisk --remove-modules

mihir24 said:
Worked like a charm, thank you so much!!
If anyone else is suffering through the same issue, while in bootloop, enter the following command in command prompt (in adb directory)
Code:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
I have the same problem. I dirty flashed the stock rom and now i reflashed the patched rom in order to enter the command.
nothing happens for me. i just copy and pasted that command. is that wrong?
thanks

so yea i need to uninstall modules so i can root and not format wipe the phone. i have tried the whole adb wait-for-device shell magisk --remove-modules when its sitting on the g with the line under it. it reboots but then just goes back to the g with a line under it. i have read up on other ways to do it one involving twrp but unfortunately twrp isn't out for 3xl. any help would be appreciated thanks in advance.

DrUnkeN_TiGeR said:
so yea i need to uninstall modules so i can root and not format wipe the phone. i have tried the whole adb wait-for-device shell magisk --remove-modules when its sitting on the g with the line under it. it reboots but then just goes back to the g with a line under it. i have read up on other ways to do it one involving twrp but unfortunately twrp isn't out for 3xl. any help would be appreciated thanks in advance.
Click to expand...
Click to collapse
were u able to find any solution? I'm in the same boat as u

mihir24 said:
Worked like a charm, thank you so much!!
If anyone else is suffering through the same issue, while in bootloop, enter the following command in command prompt (in adb directory)
Code:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
thank you :good::good::good::good:

Hi, I would like to run adb on my Galaxy S10+ but if I plug any usb cable on my phone, it starts. How to disable this behavior please?

I tried the same for my Pixel 3a. I can't get adb to recognize it. Fastboot does and if I boot to stock bootloader it at least boots and recognizes it but of course it doesn't snow magisk installed..

mihir24 said:
Worked like a charm, thank you so much!!
If anyone else is suffering through the same issue, while in bootloop, enter the following command in command prompt (in adb directory)
Code:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
Holy crap, thanks for the clarification!! I found the original instructions but could not get it to work, this got it working!
You have to be in the bootloop and then enter the command above!
This worked on my Huawei P20 Pro.

Doesn't work for me, adb Devices doesn't show anything. I can boot to rescue mode or into adb sideload and it finds it. Really want to get this working

GrandMstrBud said:
Doesn't work for me, adb Devices doesn't show anything. I can boot to rescue mode or into adb sideload and it finds it. Really want to get this working
Click to expand...
Click to collapse
You can try this. It is for the Pixel 3a only.
fastboot boot image-new.img
image-new.img
https://www.androidfilehost.com/?fid=8889791610682920432
You should boot up with root but modules disabled. Remove your modules with root explorer located here (data/adb/modules) then remove the .disable_magisk file that is in the cache/ folder. It is a hidden file (starts with a dot) so your root file explorer will need to be set to show hidden files.
This all should be done while in bootloop after flashing your magisk_patched.img
Just boot to fastboot and boot the image.
https://forum.xda-developers.com/pixel-3a/how-to/magisk-modules-disabler-booting-magisk-t3976621

Tulsadiver said:
You can try this. It is for the Pixel 3a only.
fastboot boot image-new.img
image-new.img
https://www.androidfilehost.com/?fid=8889791610682920432
You should boot up with root but modules disabled. Remove your modules with root explorer located here (data/adb/modules) then remove the .disable_magisk file that is in the cache/ folder. It is a hidden file (starts with a dot) so your root file explorer will need to be set to show hidden files.
This all should be done while in bootloop after flashing your magisk_patched.img
Just boot to fastboot and boot the image.
https://forum.xda-developers.com/pixel-3a/how-to/magisk-modules-disabler-booting-magisk-t3976621
Click to expand...
Click to collapse
Hey there, I'm using a Pixel 4a and I've run into the exact same issue unfortunately. While in the boot loop I ran the adb command but it just keeps on waiting to detect my device. There seems to be no modified magisk_patched.img defaulting to Magisk core-only mode on XDA for the Pixel 4a (only for older devices), and I've also tried your other tutorial using the AIK to build a custom one for myself, which did not work unfortunately. What should I do to restore root while preventing the problematic module from loading? Thank you!!!:crying:

mihir24 said:
Worked like a charm, thank you so much!!
If anyone else is suffering through the same issue, while in bootloop, enter the following command in command prompt (in adb directory)
Code:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
just replying to say this helped me!!
With magisk, after flashing the patched boot.img (generated from magisk) via fastboot and receiving a bootloop, i ran this code, which then restarted my phone and got me to my homescreen
using oneplus7 and android 11, thanks, now i have root with magisk (rip twrp?)

tThank you so much this saved my device from getting flashing the ROM again

For future readers, you should boot into safe mode (Google to find the key press combination for safe mode) and then reboot again. This will disable all magisk modules so you can go into the manager and remove the module/s causing the bootloop

CerealKiiller said:
For future readers, you should boot into safe mode (Google to find the key press combination for safe mode) and then reboot again. This will disable all magisk modules so you can go into the manager and remove the module/s causing the bootloop
Click to expand...
Click to collapse
Thank You So So Much. I already thought i'd have completely re set up every module and setting.

[GUID] Solution MIUI 11 or other Bootloop with lastest Magisk (with Google Pay)

Hello Guys
Got issues with my 2 mi phones after the Stable Global MIUI 11
I assume that you can try to use this theory to resolve your boot loop with Magisk as well.
Requirement:
Unlocked the bootloader
Step 1. You need TWRP recovery.
And the phone can go to fastboot mode and use CMD
Code:
fastboot flash recovery twrp(whatever your twrp name).img
Some stock boot recovery the recovery img when you try to boot the phone
So in CMD
Code:
fastboot boot twrp(whatever your twrp name).img
Step 2 Install Magisk by putting it thro TWRP
Install Zip, after installation don't restart your phone yet (it will boot loop)
Use the File Manager in TWRP
Go to /data/adb/magisk/chromeos find "futility" file and chmod 644
Go to /data/adb/magisk find "BusyBox" file and chmod 664
Click to expand...
Click to collapse
Then you can restart the phone to system
Step 3 Edit google service database
Download SQL editor. Navigate to /data/data/com.google.android.gms/databases and open dg.db
Change any value contains "attest" the column C to from "10(most the case)" to "0"
Click to expand...
Click to collapse
If you see too many of them, you can clear cache and data for Play store, google service and google pay.
Step 4 Change permission to DB
Many ways of doing it, I still use the file manager in TWRP
Go to /data/data/com.google.android.gms/databases find "dg.db" file and chmod 440
Click to expand...
Click to collapse
Restart
Step 5 in Magisk Hide google Service and Google Pay
Then enjoy open your Google pay and add your card.
Hope this can help you.
Best
Zhu

Why to complicate that much, there is much easier way
Sent from my Redmi Note 8 Pro using Tapatalk

I would just like to point out that this isn't a solution per se, more of a dirty workaround. By using chmod 644 on those files you're crippling Magisk and a whole bunch of stuff will break...
This sounds like a better workaround, since it won't break Magisk functionality (untested by me, since I don't have any MIUI devices, so I can't confirm if it actually works):
https://forum.xda-developers.com/showpost.php?p=80995509&postcount=4

goulaobangzi said:
Hello Guys
Got issues with my 2 mi phones after the Stable Global MIUI 11
I assume that you can try to use this theory to resolve your boot loop with Magisk as well.
Requirement:
Unlocked the bootloader
Step 1. You need TWRP recovery.
And the phone can go to fastboot mode and use CMD
Code:
fastboot flash recovery twrp(whatever your twrp name).img
Some stock boot recovery the recovery img when you try to boot the phone
So in CMD
Code:
fastboot boot twrp(whatever your twrp name).img
Click to expand...
Click to collapse
After this, when you boot to TWRP, you can do factory reset, but you loose data...

bootloop edxposed

Hello, on my pixel 3XL android 11 i have install edxposed sandhook and magisk riru.
Since then, I have a bootloop. Cannot delete because no TWRP. I have flashed the non-root image and can boot without root. If I remake a boot image via magisk and flash, I have the bootloop again.
How to uninstall old modules please?
I tried the following command during the bootloop :
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
the phone goes back to the fastboot and cannot restart as if it removes the boot.img
I just figured out how to do it.
I flashed the original boot.img and restart
I downloaded the recovery image and flash with magisk
https://androidfilehost.com/?w=files&flid=313291
Click to expand...
Click to collapse
fastboot flash boot image-newpixel3xl.img
adb wait-for-device shell magisk --remove-modules
fastboot flash boot magisk_patched.img
all done