Develop Bugs

December update breaks magisk?

Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.

Works fine for me.

Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions

Working fine for me as well.

I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app

You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.

mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.

RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!

RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.

RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1

Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1

sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.

Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.

RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.

bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018

I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse

Installing Viper4Android

After days of trying numerous different ways I've finally managed to get Viper to work my Oneplus 7T Pro
You will need to have a modded recovery with adb enabled:-
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
First I removed the any previous Viper module in Magisk and rebooted.
I then uninstalled the Viper App and rebooted again.
So I then had a clean starting point.
I installed The SELinux Switch app from XDA to set SELinux mode to Permissive:-
https://forum.xda-developers.com/and...witch-t3656502
I turned off Google Play Protect.
I then installed the version 2.7.1.0 module in Magisk.
Installed driver and it rebooted.
Stuck at Fastboot screen.
Reboot to Recovery
I then did the following in adb to delete the post-fs-data.sh file which is the file that stops the phone booting.
1) adb shell
2)cd to /data/adb/modules/ViPER4AndroidFX
3)rm post-fs-data.sh
4)exit
reboot to Fastboot and then Start
Then it just worked.
Hopefully this method will work for others.

Sounds cool. Congratulations

Wrong thread!

Legend!!!

Wouldn't it be easier to just make a viper zip without postfs data?

f41lbl0g said:
Wouldn't it be easier to just make a viper zip without postfs data?
Click to expand...
Click to collapse
I don't know how to do that.
That would be a question for the people who write Viper.

f41lbl0g said:
Wouldn't it be easier to just make a viper zip without postfs data?
Click to expand...
Click to collapse
We don't have the source of the module, and you can't just take the installed module folder and zip it to a module so I don't think it's possible.
Might be wrong though.
Sent from my OnePlus7TPro using XDA Labs

thanks mate. worked for me too. finally
Edit: it is not processing on Bluetooth devices

Here try this zip I modified, it should work fine on the OP7T and OP7T Pro if this fix does indeed work. Shouldn't need any custom recovery or adb. Can someone report if my modified file works? If it doesn't just use the custom recovery with adb to remove the module.
Note: Selinux will need to be changed to permissive before installing the module using this:
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
All credits to:
- @ahrion
- @zhuhang
- @osm0sis
- Viper's Audio (Official blog)
- @viper520
- @Team_DeWitt

f41lbl0g said:
Here try this zip I modified, it should work fine on the OP7T and OP7T Pro if this fix does indeed work. Shouldn't need any custom recovery or adb. Can someone report if my modified file works? If it doesn't just use the custom recovery with adb to remove the module.
Note: Selinux will need to be changed to permissive before installing the module using this:
https://forum.xda-developers.com/android/apps-games/app-selinux-switch-t3656502
All credits to:
- @ahrion
- @zhuhang
- @osm0sis
- Viper's Audio (Official blog)
- @viper520
- @Team_DeWitt
Click to expand...
Click to collapse
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.

Alexisd1 said:
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Click to expand...
Click to collapse
Did you make selinux permissive?

f41lbl0g said:
Did you make selinux permissive?
Click to expand...
Click to collapse
Yes i turned the selinux permissive from the beginning. I haven't mentioned that because I forgot it by mistake

Alexisd1 said:
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Click to expand...
Click to collapse
I had the same. I had to install and delete the .sh twice until it worked. And it works fine.

Alexisd1 said:
You will have to make this steps to make it work.These steps are from the original thread and for my situation the module It didnt worked properly.
I have flashed your zip with magisk manager,I havent rebooted,I have installed the drivers from Viper and then I rebooted. I got stucked in fastboot. I had to make rm post-fs-data.sh to force the phone get fixed from the loop.Then I have opened Viper and then asked me again to install the drivers.Then I got stucked again and I had to put the same command through adb shell rm post-fs-data.sh. After that It did worked but I dont know why its not working with your module.
Click to expand...
Click to collapse
c0caine_train said:
I had the same. I had to install and delete the .sh twice until it worked. And it works fine.
Click to expand...
Click to collapse
At this point just flash the zip from the original post, don't use my zip. I'll test it out more once my phone arrives.

Do you need to keep selinux permissive to continue to use Viper due to deletion of the .sh? Or can one toggle it back post this process?

Wow, this Viper4android seems to be a pain for our phones. I already tried it approximately 5 times and having to use the MSM tool to be able to boot up again from scratch I'm coming from a different flagship and I never had a problem rooting and installing apps like Viper4android before. I don't know if it would be too much to ask. that once someone has found a proven successful method to please share. I don't want to seem lazy I've been searching all over and so far the methods are not definite and very frustrating. Ive had my phone for a week still adjusting. Anyway any help would be appreciated and please no offensive comments. Thanks

slapman said:
Wow, this Viper4android seems to be a pain for our phones. I already tried it approximately 5 times and having to use the MSM tool to be able to boot up again from scratch I'm coming from a different flagship and I never had a problem rooting and installing apps like Viper4android before. I don't know if it would be too much to ask. that once someone has found a proven successful method to please share. I don't want to seem lazy I've been searching all over and so far the methods are not definite and very frustrating. Ive had my phone for a week still adjusting. Anyway any help would be appreciated and please no offensive comments. Thanks
Click to expand...
Click to collapse
Yeah, read the first post...
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Yeah, read the first post...
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Yes, I did read the post but I just don't want to mess up the phone again. Maybe Ill try again when my mind is fresh had to many mishaps but thanks.

slapman said:
Yes, I did read the post but I just don't want to mess up the phone again. Maybe Ill try again when my mind is fresh had to many mishaps but thanks.
Click to expand...
Click to collapse
Which version do you have? EU or international?
This recovery works fine in EU version, if there's is anything that messes up it's likely a module, which can easily be removed with the modded recovery.
Sent from my OnePlus7TPro using XDA Labs

When I try to cd to /data/adb/modules/ViPER4AndroidFX I get cd: bad substitution
I'm on OOS 10.0.4 (international ver.) with modified recovery for ADB.

Pixel 3a XL Bootloop after enabling modules in Android 11

Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance

scyther3989 said:
Hello!
I installed the new Android 11 stable and everything went well. I installed OTA and was able to flash a modified boot.img for root. I then wanted to re-enable the modules I turned off for the update. That's when I got stuck in a boot loop. I'm not sure the correct procedure for re-enabling the modules but immediately after restarting to let the modules take effect I ran into a boot loop.
To remedy this I tried re-flashing the modified boot image, which always leads to a boot loop.
I have also tried the "adb shell magisk --remove-modules" command during the boot loop but that immediately brings me to the fastboot screen with the reason "Invalid boot slot" and then it stays there until I flash another boot.img.
I've tried unpacking and repacking a magisk_patched.img with both the Pixel 3a XL's "core only" and "remove modules" but those lead to a fastboot error where it doesn't like the image and won't boot from it.
If I flash the stock Android 11 boot.img the phone boots up fine but doesn't have root obviously. I am also using the newest (30.0.4) version of android platform tools.
I was wondering if anyone else had some insight as to what I'm doing wrong or where to go from here?
Thank you in advance
Click to expand...
Click to collapse
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version

adm1jtg said:
Sounds like an incomparable magisk module. You need to isolate which module is the problem and leave it disabled or look for an updated version
Click to expand...
Click to collapse
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.

scyther3989 said:
I would be fine with this but I have no idea how to disable the modules without root. And the adb shell isn't working for me either.
Click to expand...
Click to collapse
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.

adm1jtg said:
I think it's in the themes forum here but they're is a magisk module disabler. They're are also other utilities to do so.
Click to expand...
Click to collapse
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.

scyther3989 said:
The only things I've seen for Module disablers are...
the adb shell magisk module disable
the patched "core only" and "module remover" repacked boot images
magisk uninstaller that requires a recovery to run it
I've tried the first two and I can't find a TWRP that works with a Pixel 3a XL running Android 11.
Click to expand...
Click to collapse
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.

adm1jtg said:
And you won't find one. Twrp only works on Android 9 or older. Starting with 10 the partitions are dynamic and to date twrp can't handle them at all. Since we haven't had a working twrp in over a year i wouldn't get my hopes up.
Click to expand...
Click to collapse
Yeah I'm hoping for some kind of insight on how to disable modules without root or maybe some new patch I haven't tried.

Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app

rifraf1 said:
Try booting into safe mode, this is supposed to disable all modules. When you boot back into regular mode they should still be disabled and you can delete or update the bad one.
Sent from my SM-T860 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Wow this actually worked!!
For anyone having a similiar issue:
I flashed the magisk_patched.img from Android 11 and let it go back into it's bootloop
As soon as the booting animation started I pressed volume UP and volume DOWN and it booted into safe mode
I restarted once I successfully made it into safe mode
The modules causing the bootloop were disabled and I am now able to have root in Android 11
Thank you @rifraf1

Question Stuck boot loop

Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance

Hunter_87 said:
Hi guys,
just updated my op9p to the newer oos 11.2.5.5LE15BA and repatched with magisk, everything gone fine.
I re-deleted some google system app with sdmaid that i had debloated yet before this oos update.
Once i re-install vanced apps i detached it using magisk module from termux, rebooted and now i'm in stuck with boot loop.
Tried to clear cache from recovery but still keep in stuck.
What can i have corrupted?
Can i solve it reflashing stk boot.img?
Thanks in advance
Click to expand...
Click to collapse
you can try booting in safe mode, this will disable all magisk modules

Same issue tring to boot into safe mode

I just posted a tutorial to use adb to remove magisk modules for a situation just like this. worth to check it out if you can't get it done via safemode
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
there might be the same tutorial on xda but i had this copied to my clipboard

Scary that a detach module could cause bootloop...

Hunter_87 said:
Same issue tring to boot into safe mode
Click to expand...
Click to collapse
Did you able to make it work?

Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Nothing.. i had to do an hard reset!! Thanks to all anyway..

Hunter_87 said:
Nope, same result tring to follow thirtythr33 tips..
Really don't undestand what i did it wrong to get this problem.
Click to expand...
Click to collapse
Have you removed all modules via abd?

netgar said:
Have you removed all modules via abd?
Click to expand...
Click to collapse
Nope, i tried with adb command as reported on linked guide but nothing happen and i receive just an error on cmd for too waitings.

Question Viper4android on any android 12 custom rom

i've been trying for 2 whole days now to install viper4android on my oneplus 9 pro, i just can't get it to install. I'm basically stuck in an install loop and i've tried almost everything (permissive, AML, clean install, v4a repackaged, android 12 fix) but none of them work.
I wonder if anyone got viper working on their device running a custom android 12 rom

Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com

Hammerhand.17 said:
Take a look:
Viper4Android
Hi guys i used V4A on all of my 1+ devices. Started from the 1+1, 5, 7Pro and now i own the 9 Pro. The phone is rooted with a patched img, Magisk 24.3 installed, stock recovery. OOS Version is 11.12.10.10 Somehow i cant get V4A get to work...
forum.xda-developers.com
Click to expand...
Click to collapse
tried that too and just now tried it on just stock lineage os on A11 but still no luck nstalling v4a

This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).

Hammerhand.17 said:
This method worked for me in several custom ROMs in A12 and A12, bit just following the steps exactly and rebooting in every step (and you have to activate legacy mode).
Click to expand...
Click to collapse
i did follow every step with the reboots after each module but i'm still stuck in an install loop so i cant even get to the settings unfortunately... i've never had so much trouble with a device

Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.

Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
Awesome, i'll try as soon as a custom rom is up and running

Hammerhand.17 said:
Uninstall all the modules, try the procedure again with these files. I tried with other and got driver loop as you did, but it worked with these.
Click to expand...
Click to collapse
So install magisk, reboot, AML, reboot, JamesDSP, reboot, V4A, install drivers and let it reboot? kernel can stay in enforcing?

After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.

Hammerhand.17 said:
After last reboot, you have to substitute the fs file as stated in the other thread, reboot again and set legacy mode.
I am in enforced kernel, yes.
Click to expand...
Click to collapse
Got it working finally!! Could you supply me with the modification i need to make in the post fs file? So i follow you exactly? Also can i remive jamesdsp now or does it need to stay installed?

You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot

Hammerhand.17 said:
You have to replace this file in /data/adb/modules/Viper4AndroidFX and reboot. About JamesDSP I don't really use it so I disabled the app, although I have to do it in every reboot
Click to expand...
Click to collapse
But can i remive jamesdsp from magisk or does it need to be installed in order to keep viper working? Like the moment you remove it viper just stops working?

Don't know, never tried. If you try, tell me, but I didn't want to do more tests.

Hammerhand.17 said:
Don't know, never tried. If you try, tell me, but I didn't want to do more tests.
Click to expand...
Click to collapse
If you uninstall it viper is once again stuck in an install loop so you do need jamesdsp to stay installed

Ok. Good to know. Will left it installed, then.