Problem after update Magisk - Samsung Galaxy S9+ Questions & Answers

Hello,
yesterday I got a notification to update Magisk to v.21.3. I did it directly with Magisk Manager.
Since then I'm having problems with some apps and I notice that a new version of Magisk was release just to fix this problem.
When I try to install the v.21.4 with the Magisk Manager there is an option unchecked but I do not know if I have to check it or no.
Keep AVB 2.0/dm-verity
I do not know what is this. When I update to v.23.1 I did not have that option, was direct but now when I want to update to 21.4 from Magisk Manager I have this option and I do not know what to do.
Thanks

I assume nobody answered you because you could have just googled it.
Disable DM-Verity or Android Verified Boot without TWRP
In this tutorial, we will show you the steps to disable DM-Verity or Android Verified Boot (AVB) without using TWRP Recovery.
www.droidwin.com

Related

Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]

Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]
Hi XDA friends,
After quite investigation I finally have found the way to have our devices Systemless Rooted.
The main advantage? SafetyNet working on our rooted device. That means Google does not notice our device is rooted ...yes, you can play Nintendo games or use Android Pay as well!
View attachment 4371569 View attachment 4371476
Here is the step by step guide:
You Must Have: Unlocked bootloader, ADB Fastboot drivers and Flashtool installed.
- Flash Stock Android 6.0.1 ROM with Flashtool (Wipes checked). I recommend 26.3.A.1.33 for the E2303 model. You can find Stock ROMs in this post.
- Flash TWRP from ADB: "fastboot flash recovery recovery.img" (I tried with v3.0.2.0 and also the new v3.2.1-0 recently published here!)
- Flash custom kernel (SkyMelon 8.1 or 9 without-root) from TWRP. Download v8.1 from this post or v9 directly here: View attachment 9-20171210-no-root.zip. Wipe Dalvik/Cache after install it.
- Flash the latest version of Magisk with TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
- Install the latest version of Magisk Manager.apk. GitHub repo: https://github.com/topjohnwu/MagiskManager/releases
- [Optional] In order to avoid flashing errors with TWRP it is recommended to update directly through Magisk Manager. If you want to install previous versions of Magisk (between v14.6 and v15.2), could be neccesary to check the box "Preserve AVB 2.0/dm-verity" before "Direct Install" it.
Note: Magisk v16.4 and Magisk Manager v5.7.0 was the last version working tested by me. From this version I will discontinue testing new Magisk releases on this device. Feel free to post your experience with the new ones
- This method is compatible with E2303, E2306 (reported by @zputnyq) and E2333 (reported by @Yester_Ko) models.
- Compatibility with Apps2SD reported by @tim_pear
Please if this works for you, thanks are very welcome to my first post! Also ideas or improvements to the post are welcome.
Credits:
- Special thanks to @osmank3 who built SkyMelon v9 without-root and help me with Magisk updates.
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Hi othmane.os,
I cannot provide information about restoring the TA. My warranty expired some time ago and I don´t have a TA backup.
Thanks for comment.
othmane.os said:
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Click to expand...
Click to collapse
Hi osmank3,
I have modified the post with the screenshot request and also with some links to the material used in the guide.
If you have any problem, I will be glad to help you. Thanks for comment.
osmank3 said:
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Click to expand...
Click to collapse
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 9-20171210-no-root.zip
Thanks
Hi osmank3,
I have tested the kernel that you built and it is working perfect. Thank you! This version has been added to the post and of course is menctioned your contribution.
I'm afraid you'll have to install a stock ROM...
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
osmank3 said:
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 4371416
Thanks
Click to expand...
Click to collapse
GameBoy1989 said:
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
Click to expand...
Click to collapse
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
It works
Thank you very much. Post updated!
osmank3 said:
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
Click to expand...
Click to collapse
Hey, i downloaded Magisk v14.5 and tried to flash it with twrp but i got error "invalid zip file format" What should i do now or what did i do wrong?
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Great! Thanks for sharing :good:
Which is the difference between methods? I see that it also works for you by flashing Magisk v14.0.
Artsii said:
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Click to expand...
Click to collapse
GameBoy1989 said:
- Flash Magisk v14.5 from TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
This was only thing i made differently. I didn't find right magisk there what would work when flashing because i had problem with "invalid zip file format" so i downloaded that magisk zip file from another place.
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
If you try to flash directly the last Magisk version (v15.1 in this case) I don´t know why yet but it doesn´t work. For that reason it is neccesary to first flash Magisk v14.5 (last version working with TWRP).
The way that you do it is also a very good one! Thanks for sharing @lordmd.
lordmd said:
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
Click to expand...
Click to collapse
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
osmank3 said:
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Click to expand...
Click to collapse
GameBoy1989 said:
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
Click to expand...
Click to collapse
I must flash system partition from stock Rom, after that safetynet passed.
Ty
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
I´ve tried with Pexo Rom v3 and systemless root works with Magisk but it does not passed Safety Net check.
Sayan Qadri said:
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
Click to expand...
Click to collapse

Magisk 17.1

Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
clouds5 said:
Hi guys,
Just got notified that new magisk is available for install. Is it stable and working with the v30 (running Oreo v21a)?
I had a magisk update soft brick some phones before that's why I'm asking...
Cheers
Click to expand...
Click to collapse
See the last few pages of WTF thread. 17.0 boot loops. 17.1 fixes boot loops, but best to uninstall 16 Magisk in TWRP before installing 17.1. Run the uninstaller.
However, there's problems with Magisk Hide on 17.x right now. It crashes for a lot of people.
Thx, I'll stick with 16.0 for the moment. No issues with it and I'm not missing anything so...
17.0 made my stock rom bootloop.
17.1 works fine for me.
It probably makes no difference how you install it, but I used the patch boot image option then flashed the patched boot.img using fastboot.
use dd to get an image of your currently working boot partition
patch that boot.img with magisk manager to 17.1 and copy to PC
use fastboot to flash that patched_boot.img and then reboot (or fastboot boot TWRP.img then reboot from there to be extra safe)
I'm on 21B and that works for me. I have not tried a different way so I can't confirm/deny any other method yet
Sent from my LGE V30 using XDA Labs
21a here i just clean flashed with 17.1 ._.
I'm getting issues with 17.1 and magisk hide.. Is there any fixes? Thanks in advance
So just want to make sure.. can I run the magisk Uninstaller by flashing the zip in TWRP and the flashing 17.1 in TWRP to reinstall magisk?
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
silver311 said:
Hi All,
Just to let people know. I believe the issue is with the Magisk Manager App. I'm currently still using Magisk 17.1. However, I've uninstalled the Magisk Manager and re-installed Magisk Manager 5.8.3 instead. I can now use Magisk Hide without crashing. Maybe others can give this a try as well.
Click to expand...
Click to collapse
This worked for me as well.
1. Uninstall Magisk 16 in TWRP using the latest MagiskUninstaller.
2. Flash Magisk 17.1
3. Boot up and un-install MagiskManager 5.9.1
4. Install MagiskManager 5.8.3.
As expected, the SafetyNet check doesn't work but some of the modules I use are being updated to the new template which prevents them from running on Magisk 16.0.
Anyone know how to get rid of the pop-up to update MagiskManager every time the app is opened?
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
trekminal said:
The lastest pop-up on MagiskManager shows the 6.0 version and the changelog shows that it is designed for Magisk 17.2
Anyone has tried with these new modules?
Click to expand...
Click to collapse
Yes, discussed over in WTF thread.
https://forum.xda-developers.com/showpost.php?p=77687418&postcount=1798
Thanks.
I updated to MagiskManager 6.0 but it shows me the option to update to Magisk 17.1, not the 17.2
I will wait some days until 17.2 will be available through the main app.
Any else have magisk manager crashing when using selecting #magisk hide from the magisk manager menu?
running 20d us998
with magisk 17.1
magisk manager 6 (although 5.9.1 did the same thing)
and root checker remover
someone on the magisk support thread recommended deleting the hidelist file which didn't really do anything. Problem is still occuring even with the new hidelist.

What steps are needed to deal with Magisk and OTAs for the S9/S9+, specifically?

So, there are a few different methods to deal with Magisk when you want an OTA - but the question is, just how far do we have to go when it comes to the S9/S9+?
Will OTAs fail if you have TWRP installed? Will OTA's fail if you've ever done anything to your system partition? (I've installed an app and converted it to a system app)
If they're really not that sensitive, then my understanding of the procedure is this:
1. Uninstall the Magisk Manager app as well as any apps you installed and converted to system apps.
2. Boot to TWRP and flash the Magisk Uninstaller.
3. Boot normally.
4. Re-enable updates in Developer Options and check for the OTA update.
5. Let the OTA finish updating.
6. Boot to TWRP and flash the Magisk Installer.
Can someone tell me if my procedure is correct, or if not, what I'm missing?
Thanks!

How I fixed Magisk 19 constant reboots on my phone

Just some quick instructions that helped me with issues with Magisk 19 most recently.
Problem: you updated the ROM, flashed Magisk and now the phone always reboots to recovery within a few seconds of unlocking it.
Solution:
- Flash Magisk 17.3. this should get you back to a stable system with root, but without working modules.
- Install Magisk Manager 6 to use with 17.3
- Use Root Explorer and go to /data/adb
- Delete all files called Magisk and the modules folder
Reboot and reflash Magisk 19
- update Magisk Manager
I almost gave up and would have started from scratch. I don't know why Magisk 19 corrupted after the update but even after deleting only the modules folder it wouldn't work. The phone finally worked normal again after just deleting all things Magisk in the /data/adb folder.
Unfortunately TWRP doesn't mount the encrypted /data partition yet so you can't use Magisk Recovery or Magisk uninstaller from TWRP. I found this workaround finally fixed my issues and I hope it is helpful to someone else on the forum.
Best of luck!
mrchrister said:
Just some quick instructions that helped me with issues with Magisk 19 most recently.
Problem: you updated the ROM, flashed Magisk and now the phone always reboots to recovery within a few seconds of unlocking it.
Solution:
- Flash Magisk 17.3. this should get you back to a stable system with root, but without working modules.
- Install Magisk Manager 6 to use with 17.3
- Use Root Explorer and go to /data/adb
- Delete all files called Magisk and the modules folder
Reboot and reflash Magisk 19
- update Magisk Manager
I almost gave up and would have started from scratch. I don't know why Magisk 19 corrupted after the update but even after deleting only the modules folder it wouldn't work. The phone finally worked normal again after just deleting all things Magisk in the /data/adb folder.
Unfortunately TWRP doesn't mount the encrypted /data partition yet so you can't use Magisk Recovery or Magisk uninstaller from TWRP. I found this workaround finally fixed my issues and I hope it is helpful to someone else on the forum.
Best of luck!
Click to expand...
Click to collapse
Had this issue a while back and ended up starting with a clean install. Nice that you found a fix, should come in handy if I ever face the same problem again...
Hi,
I have similar issue as you but slightly different. Whatever I tried to flash (e.g: twrp (multiple version) or patched magisk boot img). It always reboot to mi official recovery.
Do you face this issue before and how you fixed it?
Info:
Mi 9 EEA rom
cutesniper22 said:
Hi,
I have similar issue as you but slightly different. Whatever I tried to flash (e.g: twrp (multiple version) or patched magisk boot img). It always reboot to mi official recovery.
Do you face this issue before and how you fixed it?
Info:
Mi 9 EEA rom
Click to expand...
Click to collapse
Take a look, if your bootloader is unlock!
Maybe it is relocked.
I had the same issue today, what I did is quickly opened up Magisk manager, and clicked uninstall. It still rebooted in the middle of the process, but after I flashed 19.1, it never rebooted again!
bombername said:
Take a look, if your bootloader is unlock!
Maybe it is relocked.
Click to expand...
Click to collapse
No, I can confirmed it's unlocked because I'm able to flash global rom into mi 9 china phone.

convert SuperSU to Magisk

Hi,
I'm using a T820 with Stock Android v8.0.0, TWRP installed and SuperSU. Everything is working fine, but I can't use Samsung's security updates ("Failed - unauthorized changes") and thus am rather behind in "Android Security Level" (April 1st, 2018).
I'd like to change from SuperSU to Magisk, but when I try to install via Magisk Manager it says "boot image patched by unsupported program" and aborts installation. This "unsupported program" could either be SuperSU or the "no-verity-no-encrypt_ashyx.zip" I used in rooting.
Is there a way to change to Magisk without reformatting Data? Can I just reflash a stock boot image and then install Magisk, or would that mess with this encryption thingy? Would I need to flash anything else on the stock image, like the "Tabs3_oreo_forced+encryption_disabler.zip" I read about? What would be the correct sequence?
Regards

Categories

Resources