Trying to patch boot.img with Magisk on March update. I check "select and patch..", select boot.img and it says "lets go". When I click on that Magisk closes and nothing happens. No magisk_patched.img is created. Anyone else have this problem?
March update with Magisk
- Thread starter Daisymae
- Start date
What do you mean when you say you "checked
select and patch'? Do you mean you opened Magisk Manager tapped install (next to Magisk),tapped install, tapped select a boot image to patch. Selected it and tapped the check mark? If yes, try again.
Tried it several times with same result. When I get to "method" I tap "select and patch". It immediately takes me to the download directory where the boot.img is. I tap that and it takes me back to the screen with the methods. I tap next and then "lets go" appears.. I tap that and it closes. Nothing happens.
Update: found the problem. It was a canary magisk manager. DL the stable one and patched image was created.
Last edited:
Had exactly the same thing today. I cleared cache and data on Magisk Manager, uninstalled it and then reinstalled. Worked fine after that. Might be able to skip the uninstall step, I just do things that 2ay to be complete. Make sure you get the APK from a legit source, there are fakes out there.
Ahhh, just saw the post above. Yep I was on Canary and when I reinstalled I went back to stable.
Yes, it is a bug in the latest canary magisk manager. It should be fixed in next canary release.
Stable version roots fine so that's an option until canary builds are fixed.
When I patch the March boot.img with Magisk Manager 7.5.1 stable and Magisk 20.3 I get a boot loop at the "G" screen after the progress bars cycle for a few seconds. I actually got the same result when I did the Magisk method of accepting the March OTA which is why I'm trying this method. I've tried reflashing both slots with factory March and then flashing patched image to both slots, so far no love. If I flash the stock boot.img back to the active slot it boots right up without root. Any ideas? TIA!
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel3xlRemove
-
Code:
fastboot flash boot magisk_patched.img --slot all
Code:
fastfoot boot image-newpixel3xl.img- Remove/Delete all the modules in the folder
- Remove/Delete the hidden file: .disable_magisk in the cache folder
- Reboot
- Thank the OP!
Last edited:
That worked! I actually had to use the image-newpixelxx vs image-newpixelxxRemove as the latter also boot looped for me. Who knows what state I'd gotten myself into to cause that. I also had to manually take Magisk out of core only mode afterwards in the app settings in order to get systemless hosts working again. Anyway - it definitely was a bad module and you put me directly on the right track! Thanks so much!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
32
It could be a bad (outdated) module that is causing the boot loop.
Try this:
- Download: image-newpixel3xlRemove
--Code:fastboot flash boot magisk_patched.img --slot all- Use a root file manager to open data/adb/modules folderCode:fastfoot boot image-newpixel3xl.img
- Remove/Delete all the modules in the folder
- Remove/Delete the hidden file: .disable_magisk in the cache folder
- Reboot
- Thank the OP!1
Had exactly the same thing today. I cleared cache and data on Magisk Manager, uninstalled it and then reinstalled. Worked fine after that. Might be able to skip the uninstall step, I just do things that 2ay to be complete. Make sure you get the APK from a legit source, there are fakes out there.
Ahhh, just saw the post above. Yep I was on Canary and when I reinstalled I went back to stable.
New posts
-
-
-
recent Snapdragon-based headunit, identify, resources, rooting?- Latest: The.Invisible.Man
-
-
Development [KERNEL] KernelSU 11760 - Galaxy Tab A8- Latest: atulnakul121