Hi! so i have an issue, i cannot get any magisk modules installed on the latest B05 Rom. i've tried on both the official system from ZTE aswell as community made roms based on B05. I have also tried like 5 different magisk modules non of which want to be installed. What could the issue be and how can i fix it?
senny22 said:
Hi! so i have an issue, i cannot get any magisk modules installed on the latest B05 Rom. i've tried on both the official system from ZTE aswell as community made roms based on B05. I have also tried like 5 different magisk modules non of which want to be installed. What could the issue be and how can i fix it?
Click to expand...
Click to collapse
If you have an early version of Magisk 13.3 that can be the problem. The Magisk Manager that shipped with 13.3 initially was flawed so that it would fail to install modules, or so I read.
But it has happened to me that it just failed to install any module out of the blue, with version 12.0. If that's the case a full system reinstall seems the only way to fix it. you might as well want to use the magisk uninstaller and then install it again, but I don't think that would fix it.
Related
Hi,
my A2017G (B05 Nougat) doesnt boot with Magisk v13.4 or above. I tried beta versions and also the brandnew v14. The bootanimation is stuttering but thats all.
Im using 13.3 and Manager v5.3.0, which is working so far.
I cant deinstall systemapps. 'reboot disemmcwp' has no effect. I think its because of magisk. With SuperSu i can deinstall systemapps. But i use some modules with magisk so i want stay with magisk, but it seems not working properly. Can someone confirm this issues?
Where's the problem?
Any ideas?
I'm pretty sure stock has issues with Magisk in general. I'm using the latest 14 on RR with no issues.
works fine for me, ive ran 13.6 on B05 and B06
MaxRink said:
works fine for me, ive ran 13.6 on B05 and B06
Click to expand...
Click to collapse
Whats flashed on your phone? Bootstack + System with Magisk 13.6 only?
I dont understand why magisk 13.3 works without any problems, but every version above has this issue on my phone.
Stock B06 with B06 bootstack, 13.3, 13.6 and 14 work just fine
Hi,
i think i found the problem. If i flash xposed (systemless v87 sdk25 by PurifyOS), my phone cant boot up.
So i have to wait and use magisk 13.3, until xposed get an update, to work with magisk 13.4 and versions above.
im new at thisxda stuff but i am 90 percent sure i figured out how to keep magisk from uninstalling after a reboot... YOU MAY NEED TO UNINSTALL MAGISK AND ALL MODULES BEFORE DOING THIS USING MAGISK UNINSTALLER basically you have to also install an older version of supersu and it has to be an aroma installer and install as SYSTEM also make a backup of the boot.img just incase you get bricked if you install the supersu app it will say su binary occupied but install should stay install supersu aroma (2.78v2) from https://forum.xda-developers.com/attachment.php?attachmentid=3879523&d=1474248173 before and possibly after magisk install...only tested with magisk 16.2 beta channel and regular install not patched boot on Axon 7 with RR 8.1 weekly 6.0.0 20180225 (us variant) but should work on others probably...let me know how this goes for you
TRY AT OWN RISK I AM NOT RESPONSIBLE FOR DEVICE BOOTLOOPS OR BRICKS
If anyone has a better way to get magisk to hold after a few restarts please let me know
sidenote:this supersu does work with magisk not installed and definately keeps root
(stock boot.img is in initial zip for custom rom) select intall imgs in twrp and flash the boot partition as needed)
ALSO YOU CAN ALWAYS DIRTY FLASH CUSTOM ROM same build or higher IF ALL GOES TO **** AND WONT LOOSE APPS OR DATA AT LEAST ON RR
works for me without problems after last 2 years on any Rom.
dont know what you doing wrong?!
I cant get to bypass safetynet V: other than that root works fine
J0nhy said:
I cant get to bypass safetynet V: other than that root works fine
Click to expand...
Click to collapse
this actually fixed sn for me without the fix installed
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
desu1337 said:
Ever tried magisk v15.3? I never had problems with uninstalling, but everything above 15.3 won't pass safety net,at least for me/on stock nougat b10 rom.
Click to expand...
Click to collapse
Maybe on stock roms...it should work on l8r versions tho...
try this already https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
also cant have xposed installed with the sn fix
Hi guys!
First of all, please do not send me to somwhere on forum because I have tried dozen of ways do deal with problem. My phone is LG G6 running on android pie. TWRP installed, Magisk installed. Im trying to instal viper4droid. I have tried download module from Magisk itself, I have tried to download .apk file from different sources, I have tried to download .zip file, I have tried to installed as apk itself and grant root accesss, tried by TWRP, tried unify installers and **** knows what else. Trouble is, First few times it was installed but status was "not running", Today after many attempts to deal with that viper4droid installing drivers and.......after each reboot its doing it again. Moreover i have found that sometimes Magisk did not show up the newest version of v4a as a module to download. So......is somebody for the love of god know what the **** is wrong? thank you.
marcin3595p said:
Hi guys!
First of all, please do not send me to somwhere on forum because I have tried dozen of ways do deal with problem. My phone is LG G6 running on android pie. TWRP installed, Magisk installed. Im trying to instal viper4droid. I have tried download module from Magisk itself, I have tried to download .apk file from different sources, I have tried to download .zip file, I have tried to installed as apk itself and grant root accesss, tried by TWRP, tried unify installers and **** knows what else. Trouble is, First few times it was installed but status was "not running", Today after many attempts to deal with that viper4droid installing drivers and.......after each reboot its doing it again. Moreover i have found that sometimes Magisk did not show up the newest version of v4a as a module to download. So......is somebody for the love of god know what the **** is wrong? thank you.
Click to expand...
Click to collapse
Hi man, there are three versions of viper4ndroid on magisk, try the viper4android fx legacy materialized as normal app after disabling play protect on google playstore. hope this helps
I will try that in a minute mate.
didnt work.
I have the same problem. I switched to viper hifi and now after reboot it is working but after some time it stops till i reboot it again. I think it is because of the pie version, on oreo everything works fine. After every reboot every mofule in magisk reinstalls. For example youtube vanced instals like new and i have to set it up after the reboot.
IIRC it required me to install viperfx (the new version, not legacy or xhifi), audio modification library and audio compatibility patch, have you done that?
I have tried all three version of viper. I have isntalled it as a apk and modules in Magisk. All possible audio patches and compatibilies mods from magisk are intalled as well.
marcin3595p said:
I have tried all three version of viper. I have isntalled it as a apk and modules in Magisk. All possible audio patches and compatibilies mods from magisk are intalled as well.
Click to expand...
Click to collapse
if you still have this problem, try installing viper4android 2.7 as apk from xda lab, I was downgrading back to pie sometimes ago and couldn't get viper to work, besides the 2.7
Hi all, i just rooted my phone (mi9t) and installed Xiaomi.eu and magisk and i was researching for modules to download. And i stumbled upon a wall. Every single module that i tried to install has failed because it need Magisk version 17-19. What's happening ? Have the devs stopped updating their modules for newer Magisk versions or am I super catched up with Magisk and everyone else is still trying to bring the updates? For reference some of the modules that i tried:
Universal GMS Doze
Riru - Core
FDE.AI (from zip it doesn't work and there is no result after searching it at all)
Can you please elaborate what's happening?
panostheodorakis7 said:
Hi all, i just rooted my phone (mi9t) and installed Xiaomi.eu and magisk and i was researching for modules to download. And i stumbled upon a wall. Every single module that i tried to install has failed because it need Magisk version 17-19. What's happening ? Have the devs stopped updating their modules for newer Magisk versions or am I super catched up with Magisk and everyone else is still trying to bring the updates? For reference some of the modules that i tried:
Universal GMS Doze
Riru - Core
FDE.AI (from zip it doesn't work and there is no result after searching it at all)
Can you please elaborate what's happening?
Click to expand...
Click to collapse
Maybe you flashed canary magisk version, flash the stable one, or even 20.3...
Sent from my Mi 9T using XDA Labs
In order to be able to run Charter Spectrum, (and other television streaming applications) I've been looking to use some of the more sophisticated root-hiding technologies made available by newer versions of Magisk. I'm currently on version 23 of Magisk itself, and 24.1 of the app, but afraid to go any higher with either due to reports of non-boot conditions or incompatibility with newer versions of the Magisk app itself.
Has anyone been brave enough to try current versions of Magisk with Alpha/Omega Rom and MK2000 kernel (or other comparable custom kernels)? If so, did you have a similar problems, (no-boot, Magisk app ceasing to function, etc.) did it work perfectly, or was there some other outcome?
Your input is very much welcomed!
Bill720 said:
In order to be able to run Charter Spectrum, (and other television streaming applications) I've been looking to use some of the more sophisticated root-hiding technologies made available by newer versions of Magisk. I'm currently on version 23 of Magisk itself, and 24.1 of the app, but afraid to go any higher with either due to reports of non-boot conditions or incompatibility with newer versions of the Magisk app itself.
Has anyone been brave enough to try current versions of Magisk with Alpha/Omega Rom and MK2000 kernel (or other comparable custom kernels)? If so, did you have a similar problems, (no-boot, Magisk app ceasing to function, etc.) did it work perfectly, or was there some other outcome?
Your input is very much welcomed!
Click to expand...
Click to collapse
Hello, your on the latest version that works with Oreo 8.0 at this time. Magisk 25.2 does not work. When I installed Magisk 25.2 app, it would not open. So I just uninstalled the Magisk app and reinstalled a lower version and that fixed it. I am also running Stock Oreo 8.0 ezV2020 kernel.
Darnrain1 said:
Hello, your on the latest version that works with Oreo 8.0 at this time. Magisk 25.2 does not work. When I installed Magisk 25.2 app, it would not open. So I just uninstalled the Magisk app and reinstalled a lower version and that fixed it. I am also running Stock Oreo 8.0 ezV2020 kernel.
Click to expand...
Click to collapse
Thanks for the datapoint. Can a newer version of Magisk itself be used with version 24.1 of the app?
Bill720 said:
Thanks for the datapoint. Can a newer version of Magisk itself be used with version 24.1 of the app?
Click to expand...
Click to collapse
I was mistaken, version Magisk-v24.3.apk is the latest version that will work with the Lgv20 Stock Oreo. And Magisk 24.3 would be the latest version. Just install the apk file from GitHub. Do direct install. I just updated my Lgv20 and it works.
Darnrain1 said:
I was mistaken, version Magisk-v24.3.apk is the latest version that will work with the Lgv20 Stock Oreo. And Magisk 24.3 would be the latest version. Just install the apk file from GitHub. Do direct install. I just updated my Lgv20 and it works.
Click to expand...
Click to collapse
Indeed. The version 24.3 apk installed beautifully, and version 24.3 of Magisk did the trick as well. Unfortunately, after enabling Zygisk and restarting, the device now hangs indefinitely on the boot animation .
Bill720 said:
Indeed. The version 24.3 apk installed beautifully, and version 24.3 of Magisk did the trick as well. Unfortunately, after enabling Zygisk and restarting, the device now hangs indefinitely on the boot animation .
Click to expand...
Click to collapse
I never enabled Zygisk, Do you have a backup of your boot image in twrp? I would re flash the boot image. Or you can try to boot into twrp and run Magisk-uninstaller-20210117.zip Then install the Magisk apk again to get Magisk installed.
Darnrain1 said:
I never enabled Zygisk, Do you have a backup of your boot image in twrp? I would re flash the boot image. Or you can try to boot into twrp and run Magisk-uninstaller-20210117.zip Then install the Magisk apk again to get Magisk installed.
Click to expand...
Click to collapse
I followed a bunch of rabbit trails on this one. Tried disabling Xposed Framework because someone said that it might interfere with Zygisk. No change. Tried disabling all of the Magisk modules, but it still hung. Finally, I did the rename-magisk-apk-file-to-uninstaller.zip trick and uninstalled it through TWRP. The device still hangs on boot. I'm thoroughly regretting this experience right about now. The V20 might just be toast.
Update: it did boot up eventually after uninstalling Magisk completely. I'll have to revisit this later in the day.
Phew! It's back in service. Enabling Zygisk is definitely the thing that causes it to incompletely boot, however.
Update: And it's gone again. I tried enabling Zygisk a second time, but now, I cannot uninstall Magisk from within TWRP any longer because it can't mount /data. It can't mount data because device encryption is enabled. I tried using the "locksettings clear --old xxxx" adb shell command, but it is not accepted:
java.lang.NullPointerException: Attempt to invoke interface method 'android.os.IBinder com.android.internal.widget.ILockSettings.asBinder()' on a null object reference
at com.android.commands.locksettings.LockSettingsCmd.onRun(LockSettingsCmd.java:62)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:54)
at com.android.commands.locksettings.LockSettingsCmd.main(LockSettingsCmd.java:50)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:284)
Click to expand...
Click to collapse
Any ideas here, anybody, or am I totally screwed?
Bill720 said:
Phew! It's back in service. Enabling Zygisk is definitely the thing that causes it to incompletely boot, however.
Update: And it's gone again. I tried enabling Zygisk a second time, but now, I cannot uninstall Magisk from within TWRP any longer because it can't mount /data. It can't mount data because device encryption is enabled. I tried using the "locksettings clear --old xxxx" adb shell command, but it is not accepted:
Any ideas here, anybody, or am I totally screwed?
Click to expand...
Click to collapse
That's so odd because I enabled Zygisk on my phone and it booted but I did not have xposed installed. If the data partition is encrypted the only way I know of getting rid of that is to do a format in twrp. That will erase everything on the phone. I don't have any ideas maybe some one will chime in.