I do know it works without the "-d" since I repaired with the .25 script and was able to accept the .31 OTA after.
update 10.0.31.... out
- Thread starter gaww
- Start date
so heres what i think happened. i looked at all the zips and saw that yes you are correct on it not having -d
the problem wherein i needed to change it was because i had to use msm tool. magisk didnt exist period as an app.
i ran scripts without the -d and they did work in the sense the script executed magisk install
but i had flashed my original .25 boot image and no magisk SO when i used original script it had an error and did not install magisk at all.
i was confused for a couple reasons
1. somebody mentioned replacing boot image from x with script folder y
2. previous scrips did not have
echo.
(script following the echo + period)
so when i opened MY slightly modified versions and saw -d......thats what i thought was happening. and it did work for that command.
that said, no way about it is working correctly without msm. wasnt able to update to 27 since ive been busy with fam to mess with any of this and i cant find the kernel everyone keeps talking about needing for the 31 update.
If you have the original kernel that you extracted in TWRP before injecting Magisk, that is the one you need to restore. Uninstalling Magisk should put the correct kernel back for you automatically.
On the other point, if adding the "-d" will work for those without Magisk Manager already installed, I will add it.
i was never able to update to 27. that includes uninstall magisk incorrectly, finding and flashing 25 boot img, redoing the whole thing, and clicking restore images etc etc.
and i guess nobody had reserves or something i kinda gave up for a bit and figured come back to it later (today, now. since i just got tired of notifications and realised new build).
maybe yourself or others may know the answer to this: i used to have issues with commands like --set-active not recognizing -- set until realizing minimal fastboot works best for that sort of thing instead of regular command prompt or whatever new windows powershell either.
however a lot of things ive noticed talking about fastbootd (fastboot reboot fastboot a la "flash" script zip), that command does not work. at least windows 10. for me. and various shells im using. i believe i remeber seeing something about that being (our device) recovery, so wouldnt it be fastboot reboot recovery? been out this a bit to accurately assume certain things. im just tryna update lol. all this was why i was trying to streamline multiple scripts so that way with each update can just pull what i need and have one big folder for each one should anyone not me need.
Im on 25 I tried getting to 31 with no luck with OTA. rooted and unlocked. Tried the reserve25 repair with no luck either. Anyone have any ideas?
I ended up having to use msm tool. Was initially just going to lock bootloader. Either way bye bye certain data. Oh well
I just want to be sure how to update now - after I finally updated .31 without having to use MSN and reserve.img is in its place in Data, do I only have to unroot with stock kernel from Magisk, update, and then reroot with patched boot.img ?
You mean for updates coming after .31? You don't have to do anything right now. Once a new update comes out, just uninstall Magisk, restore stock boot.img, and install the update.
Here we go again - .34 update just appeared.
Been waiting on one to see how my rooted device handles it per the above procedure.
Well, I had Magisk reinstall image, rebooted, and then ran the update. Finished and rebooted OK.
But then had trouble with rebooting. Fastbooted the patched Magisk .img, and it rebooted, looked ok, but couldn't get to the desktop to have Magisk reinstall itself to lock it in.
Had to go through the rerooting procedure a few times, but finally got to Magisk manager and reinstalled Magisk, rebooted and all fine.
Should I be using an updated patched Magisk to avoid the above problem ?
Been waiting on one to see how my rooted device handles it per the above procedure.
Well, I had Magisk reinstall image, rebooted, and then ran the update. Finished and rebooted OK.
But then had trouble with rebooting. Fastbooted the patched Magisk .img, and it rebooted, looked ok, but couldn't get to the desktop to have Magisk reinstall itself to lock it in.
Had to go through the rerooting procedure a few times, but finally got to Magisk manager and reinstalled Magisk, rebooted and all fine.
Should I be using an updated patched Magisk to avoid the above problem ?
Last edited:
I pulled a fresh copy of the kernel and patched it with Magisk again. Everything was smooth, and I was back up and running within 20 minutes.
You have to pull it from your phone after the update. Then you patch it with Magisk, boot from it, and then flash it.
I had problems with pulling it with TWRP/adb pull. I used some one's boot.img.
Try this. Go into magisk and hit uninstall. After that you should be able to take the ota. Don't reboot after it installs. Go back into magisk and hit install and apply to inactive slot and then reboot and you should be good to go without having to patch anything on your PC.
If you rooted with an older kernel, you will need to unroot and restore your boot image, then reboot and make sure the kernel build date shows April, not March. Then you can try the steps again.
When it did the update it rebooted automatically - is there another way to update?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone