Database Users

How to update Magisk?

I have fullmics rom (not sure if that matters) with Magisk installed.
Magisk needs updating, but I just can't figure out how to do it and feel like an idiot now.
In Magisk manager, I press install, go through the confirmation dialogue and then choose "patch boot image file" (I've already downloaded the zip).
I then need to choose a file from that zip to patch the boot image, but I don't have a clue which one to choose. I've tried a few that I guessed could work but no luck and the update process is not self explanatory unfortunately....
The strange thing is that the Magisk manager now also says that Magisk is not installed an the phone is not rooted. Did this break because of the failed update, or is the update failing because I somehow lost root? How can I get Magisk back on my phone, it was part of the installation process with fullmics. Should I dirty flash fullmics again to get magisk reinstalled?

I ended up making a back up in twrp as a precaution before moving on to re-flashing magisk. Strangely enough after rebooting (but before re-flashing magisk) magisk was fine again and also had root back.
No idea what had broken but obviously a simple reboot fixed it.

"Installation Failed" MI A1 OTA UPDATE

Ok, why the f. did I get "installation failed" when installing OTA following this guide?
I followed the guide, I hit uninstall and "restore images" in magisk, it restored the stock image and when I tried running feb ota, I got "installation failed", why?
Also, why did my device get in a bootloop by just fully uninstalling magisk?
I had unlocked bootloader with systemless root, with no TWRP, never booted it, never flashed it, only fastboot commands I ran were oem unlock and boot patched_boot.img. I never touched system partition (on purpose), never installed anything other than a bunch of magisk modules, safetynet was always working, if it matters.
PSA FOR GOOGLE VISITORS:
Do not fully uninstall magisk after you get "installation failed", I got a bootloop and had to flash flash_all_except_storage.bat from mi a1 stock rom using miFlash (bottom right to select it, don't flash_all if you want your data).

Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....

Azeemkwow said:
Same thing happened with me... what exactly i done was...booted into patched boot.img using fastboot and after that used magisk manager and installed camera2api and just substratum.....but when i got notification of feb update... I tried to uninstall magisk manager using complete uninstall option....then restarted manually then it booted up and then suddenly shuts down and started showing a black screen with Android logo with (No command) written below it......to recover from this condition i again tried to use the same fastboot method for booting into patched boot... after which i was able to use my mobile.... normally but I'm not able to install feb update.... I'm downloading the complete stock rom.....but if there's any other method which can be efficient so plz inform....
Click to expand...
Click to collapse
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.

Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.

Alanjameson99 said:
Just like he said, yeah using Magisk means waving bye to OTA updates. This was the exact problem I faced where I installed Magisk module without TWRP for the joys of using substratum. Installating magisk won't taper your system, they said, you would still get the update, they said. Well NEWS FLASH for those, installing magisk tampers your system partitions and you are in a dreadlock situation where you can't do ****. People claim there are work arounds like you linked but no one has actually confirmed using it. And the worst part is that if you try to install the update even after uninstalling Magisk , it will still give you the error. How do I know? tried it, doesn't work. The only option which was left to me was to download the official Oreo ROM from MiUI global and flash it using MiFlash.
Click to expand...
Click to collapse
Thanks...now that's what I'm planning to do...install official rom through miflashtool

RavinduSha said:
Flashing the boot.img from stock rom might solve the problem. If not, flash the stock rom using MiFlash with save user data option.
Click to expand...
Click to collapse
Does the 'save user data'-option also preserve the apps installed?
Thanks!

Tiemichael said:
Does the 'save user data'-option also preserve the apps installed?
Thanks!
Click to expand...
Click to collapse
Yes it saves all user data including settings, apps and app data

I had the same issue. I used the tool linked below and the steps:
- Unlock Bootloader
- Flash Stock ROM
- Download ROM (and wait for that to happen)
- Keep UserData (and wait again)
- Lock Bootloader
After that I was able to install the update, then re-install Magisk and camera tweaks.
https://forum.xda-developers.com/mi-a1/how-to/tool-xiaomi-mi-a1-tool-drivers-unlock-t3742857

The guide mention in OP had worked for me for at least 3 updates including the major one from nougat to oreo with any issue. Be aware that mounting system partition as read AND WRITE brakes OTA. You don't even need to change anything just mounting it will brake it. That could easily happen using a root file explorer or a hosts file based add blocker if Magisk is not properly set (systemless hosts support toggle in Magisk settings).

Cant root after April update

After updating to the latest software I found that with the exception of the first time I tried it which weirdly enough worked, I can't for the life of me successfully boot after rooting.
I rooted once and had to uninstall magisk because of a conflicting module but now no matter what I try I always get stuck on essential's splash screen.
Does anyone else have this problem? If I flash the stock boot image I can boot just fine.

have you try flashing update, then boot image then magisk consecutively before any reboot? I'm out of the country at the moment w/o access to my PC, and I can't even risk a soft brick while traveling.

Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.

Ibanez33 said:
Are you getting as far as installing magisk again? cause from what you've written it sounds like it is working but the module that caused the original issue is still there. you can remove magisk by flashing the stock boot image but the magisk image with all installed modules is still there.
If that is the case then there are a few tool out there to mount the magisk image and remove the module.
I tried a few when I had a similar issue and the only one that worked was this one.
https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165
what you would need to do is flash twrp. boot into recovery. (decryption never works for me so would recomend either sideload or adb push to /data/media)
flash the stock boot image back.
then reinstall magisk
flash the magisk recovery manager
once loaded go to the advanced section of twrp select terminal and type mm and follow the on screen instruction to remove the afflicted module then reboot and you should be sorted.
Although that being said if that isn't the issue you're having then can you explain how far you get with trying to reinstall and whats going wrong.
Click to expand...
Click to collapse
I can't believe I hadn't thought of that. The conflicting modules were still there and I just had to remove them. Thanks so much man, I was about to wipe my phone out of frustration!

Lost root access and can't get it back via Magisk. Help!

Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!

bigbraintime said:
Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!
Click to expand...
Click to collapse
Check out this guide. It may be of some use
https://www.didgeridoohan.com/magisk/HomePage

spawnlives said:
Check out this guide. It may be of some use]
Click to expand...
Click to collapse
Thanks. I tried the methods listed in the "Lost root randomly" section and unfortunately they didnt work. Do you have any other ideas? Maybe I could "Select and Patch a File" in Magisk's Install but afaik Magisk doesnt have its img./tar. file.
I should probably just flash a fresh stock and redo the root process, but then my data will be wiped and I dont really want that lol

bigbraintime said:
Thanks. I tried the methods listed in the "Lost root randomly" section and unfortunately they didnt work. Do you have any other ideas? Maybe I could "Select and Patch a File" in Magisk's Install but afaik Magisk doesnt have its img./tar. file.
I should probably just flash a fresh stock and redo the root process, but then my data will be wiped and I dont really want that lol
Click to expand...
Click to collapse
Have you tried the uninstaller through magisk or twrp then try again with magisk.
When trying to re-install magisk do you get any errors.
https://github.com/topjohnwu/Magisk/releases
Also if worried about losing apps/data do a backup before trying anything.
The easiest way is to flash firmware and start from scratch again but backup first.

bootloop after magisk update

after uptade magisk my phone stuck in fastboot . i cant go to recovery . what i can do ?
phone is over or i can fix it ?

Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk

zgfg said:
Open Magisk Github, and try to find a solution in the Magisk Troubleshooting
You say you "updated Magisk". Since you didn't describe how, supposidely you did by flashing Magisk through TWRP or by Direct method from Magisk app/mngr
Unfortunately, those two ways are most risky. If anything goes wrong (if you don't have TWRP backup) you cannot go back to the previous working configuration
It takes just few minutes more to extract and patch the boot.img and to flash it. If anything goes wrong, you flash the original unpatched boot.img or boot.img that was patched by your older Magisk and you are back in business.
To fix the bootlop now, it will take more than few extra minutes for extracting, patching and flashing the image every time when installing and updating Magisk
Click to expand...
Click to collapse
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Add me on discord for live support :
SneezeOnYou2#8507

AC420 said:
I did update magisk by direct method from the app. Now i am in a bootloop. I always had and still have the teamwin recovery project. Can you help me how to get out of this bootloop without losing my data?
Click to expand...
Click to collapse
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well

zgfg said:
You should better have updated Magisk by patching the boot.img, then flashing (from Fastboot or TWRP) - in that case, if you have bootloop you simply flash back your previously patched img that used to work
I cannot know what went wrong. Maybe, there is a module that is no more compatible and causing the bootlop:
- Reboot to TWRP, Advanced, File Manager and navigate to /data/adb/modules
Each folder corresponds to one module.
Add an empty file named: disable (exactly as that) to each folder/module (or only to those modules you suspect they might be causing the bootloop).
Once you disabled the critical module, you can boot to system and from Magisk app further manage your modules.
Or, from TWRP flash to Boot the original boot.img extracted from your OTA zip file.
When you reboot to system, there will be no Magisk but next time you install Magisk it will find and activate old modules, probably causing again the bootloop
Or, download Magisk apk, rename to uninstall.zip and flash from TWRP to fully uninstall Magisk (and all its modules, everything)
Recommending first method, but you see the other two options as well
Click to expand...
Click to collapse
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.

AC420 said:
Connect me pls on discord fkr me its like chinese now it would be easy if you tell me live what to press on the teamwin mode. The reason i update magisk was because i had a module to block ads but suddenly it didnt work so i opened magisk and i saw the update and did the direct update like how i always updated my magisk before.
Click to expand...
Click to collapse
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time

zgfg said:
I don't use discord and I have work and private life
I gave you directions that if you knew just basic things about flashing and File mngr in TWRP, about using Magisk, etc, would be nite than enough to follow directions
Most annoying users are those who install'nuclear bomb' like Magisk, do updates, etc, but never spent their time to learn (when things work and it's easier) how to use, read the Instructions (available by one click to Github from Magisk app), etc, and then when (sooner or later) get a brick, cry for somebody to guide them to click here, there, etc.
You can still use PC and google and fill the gaps from my instructions to what/how you must click here and there
Sorry to be brutal but I really don't have time
Click to expand...
Click to collapse
Its not that i didnt look up on youtube about flashing in revovery mode. When i did search for more information i get those videos of people in india talking their own language. Np if you dont have time and on other topic someone said that they wint use discord because it wont be public for someone else with the same problem but i was gonna make photos with the steps i did for fixing it. The thing is i cant find the uninstall. File or the older version of twrp. Skip i wont takr your time good luck with your private life

And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you

AC420 said:
And about the installing nuclear bomb thing... magisk has the direct install option which is the nuclear bomb button (sometimes) the reason why my phone got into bootloop is a module which isnt working anymore its called energized its for blocking ads. I saw that it didnt work... before it worked fine i thought maybe i need to update magisk but thats why it went into the bootloop. I managed to delete the module through twrp mode and here this is for you
Click to expand...
Click to collapse
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc

zgfg said:
You don't need to delete modules (some of them, like V4A might be complicated to install again) - just disable them through still the working Magisk app before you go for updating
Or patch and flash the image instead of taking Direct install. There might be other reasons to cause bootloop, not just incompatible modules.
If it bootloops when you flash the newly patched img, just flash your old img, previously patched by the older Magisk version, that used to work for you
As simple as that - and no bootloops, no emergency help needed, etc
Click to expand...
Click to collapse
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.

AC420 said:
I am surei have the older backup in my internal storage of my phone but i dont know from where to recover that and on the internet they say everything and i am scared to make it worse than it is. I didnt use the phone for a long time because my lcd got a short circuit and i replacet it. On internet they say this bootloop problem can occure when you skip some updates some say to install a program on pc then go in download mode and fix with the program but i unpluggrd my pc and tv because me and they got too old for eachother.
Now i am just trying different things what i see on youtube and twrp says this: check picture.
Click to expand...
Click to collapse
I've had this ****, i just used abd to flash a new twrp img and dirty flashed the ROM after it flashed magisk back on again, only problem I got was safety new which idk how I solved but I think was using lsposed