Related
I've had magisk installed since version 6, I've published some magisk modules already and never had a problem until today.
After a full clean reinstall of Nougat NBD90Z (with wipe) on my Nexus 6 and then flashing Magisk, phh's superuser for magisk, installing phh's superuser apk from play store and magisk manager apk I stumbled upon a previously reported (without details) bug where magisk manager would refuse to install modules from repo claiming they are not magisk modules.
I've struggled trying everything I could including the full wipe (more details here: http://forum.xda-developers.com/apps/magisk/module-app-systemizer-t3477512/69230448#69230448) and bounced some ideas off @pnwsr6 who's had the similar problem on Nexus 6 device.
I've achieved a partially working Magisk Manager (manual installs of ZIP files work, but installs from repo still fail) and here's the list of steps which lead to me having semi-working magisk manager again:
1. I flashed ZIP files of some modules in twrp (I'm attaching App Systemizer and Nexus 6 LED Enabler which I flashed)
2. After the phone booted up I saw the modules active and working
3. Within Magisk Manager I then added the ZIP file of the phh's superuser module from that thread (http://forum.xda-developers.com/attachment.php?attachmentid=3893967&d=1475554052)
4. Now at least manual installation of modules within Magisk Manager are working fine.
@topjohnwu -- I've enabled verbose logging and extra logging for bash commands, but I'm still not seeing anything in the log on top of the regular output.
Created an issue against Magisk Manager so it's easier to track for developers: https://github.com/topjohnwu/MagiskManager/issues/20
Looks like that even after flashing some modules in twrp, Magisk Manager only allows to install from zip only exactly the same ZIP I've already flashed (even a minor change and bump of versionCode results in "This ZIP is not a Magisk Module!"). So it might be an issue of Magisk Manager being unable to write to /magisk despite having storage permission and being granted root access.
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
I've seen this error as well on my Nexus 6 NBD90Z with Magisk v8. Started with v7 after some heavy modification on my part .
I was sometimes able to fix it by simply extracting the zip and then Magisk Manager would somehow recognize it as a module.. Other times I could extract the zip and then re-archive the contents and Magisk Manager would recognize that as a module. Weird, but doable.
stangri said:
Well, it works now (you'll have to wipe again). So here's the sequence of events:
1. Flashed @RatchetPanda's busybox http://forum.xda-developers.com/attachment.php?attachmentid=3850579&d=1471875389 from twrp -- got stuck on a boot animation, rebooted again in twrp, flashed magisk uninstall and it didn't help for some reason.
2. So I force-rebooted into fastboot and flashed nbd90z with wipe.
3. After apps were restored and everything was set up, I booted into twrp (it didn't even ask me if I want to allow /system modifications for some reason), added magisk v8 and phh's r259 root to the list, flashed them both.
4. Once the phone booted I could again install modules from repo/zips.
Maybe something didn't get properly wiped first two times but it's working now @pnwsr6!
Click to expand...
Click to collapse
I probably won't try again until next update, and hope the wipe just wasn't clearing something. I have the zip installed through twrp and working for now so I'm good till then.
just wondering if you're still having this issue with v9? I had modules installed fine under v6, but never really installed any modules under v8 to see if this problem occurred for me. now that I'm on v9, which has been wiped clean to start, I can no longer install any modules via Downloads or in the Modules section... any suggestions?
I have the same issue when trying to install viper with v9 on Nexus 6P DP2
Skickat från min Nexus 6P via Tapatalk
Same here. Find a fix ?
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
stangri said:
From what I hear, ZIP/module management has been reworked in the upcoming magisk v10, so unless you want to go the route I went thru, you can just wait for that.
Click to expand...
Click to collapse
Just an FYI, I do still have this problem, but can install the zip through twrp. Maybe 10 will be the solution.
I had the same problem, I cleared magisk manager data and it works fine now
Didn't help
Sent from my SM-G532F using Tapatalk
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
stangri said:
I've published snapshot builds of magisk v10 and magisk manager v2.6, try these together to see if they'd help.
Click to expand...
Click to collapse
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Meowdib said:
I tried the latest one from the 26th, magisk manager keeps crashing when trying to install the downloaded dialer/contacts on HTC 10.
Click to expand...
Click to collapse
Weird, do you have the same problem with magisk manager 161223?
stangri said:
Weird, do you have the same problem with magisk manager 161223?
Click to expand...
Click to collapse
Same
I need a Help to download modules using magisk
Lastest version, Included phh root, manager is from G. play,
But Modules download function is not working
Say "No modules found" for download to install via magisk.
Hello, some of my apps require busybox to work but it was deleted from Magisk. My question is where I can find working buybox for Magisk 13.2 ? I have found one zip but it was for older version of Magisk causing stuck in TWRP.
Thanks in advance
Search and download osmosis busybox works with magisk flawless
I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu
Somebody help me...
I am sure it has been mentioned many times in other threads and forums too.
Magisk 14+xposed seem to be incompatible.
This bootloop happened to me also. I just returned to TWRP and reflashed 13.3.
Problem solved.
Unleashed by ONEPLUS 3T rooted
Why don't flash system version of Xposed?
caryle said:
I can't use my 3t now, ORZ
ROM:Lineage OS Official 20170908
Kernel: blu_spark r179
Magisk: 14.0
Xposed: Xposed v87.2 by topjohnwu
Click to expand...
Click to collapse
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.
Aneejian said:
1. Reboot to recovery. (Keep pressing power button and volume down key till phone reboots).
2. Connect to a computer and copy latest Magisk Uninstaller and Magisk to storage.
3. From recovery flash the Uninstaller.
4. Click back and flash latest Magisk.
5. Wipe dalvik and cache.
6. Reboot to system.
Click to expand...
Click to collapse
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?
caryle said:
Thanks, I've repaired my phone. Is it because the version of magisk above 13.3 that I can't use xposed systemless
?
Click to expand...
Click to collapse
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
I just explained u a few posts before.
Do u even read the posts?
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
I've read the posts before. I just want to know if it caused by anything else.Now I'm going to flash the xposed system.
There is a better solution:
1 Get this zip file (thanks to @LarappsOfDongle)
2 Flash it by using adb sideload or adb push
3 Go to /magisk in recovery using built-in file manager if using TWRP or use Aroma
4 Delete ONLY folder with or similar name as xposed_framework_25 (be careful in TWRP you need to go into the folder first to delete it)
DON'T DELETE ANY OTHER FOLDER
I had the same issue. Tested with Xposed Framework 25 Magisk 14.0 Oxygen OS Open Beta 14 OnePlus 3T.
FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.
Didgeridoohan said:
FYI: The bootloop was caused by a bug where your device will get stuck at boot if any module Magic Mounts a new file to the root of /system with Magisk v14.0. The Xposed Magisk module has now been updated to not do that... There's also an update to the Material Xposed Installer to match the workaround to the Xposed module.
Edit: Make sure to uninstall any previous Xposed Magisk module before installing v87.3.
Click to expand...
Click to collapse
Which is this 87.3 version?
And which magisk module u need to uninstall before?
Unleashed by ONEPLUS 3T rooted
RASTAVIPER said:
Which is this 87.3 version?
Click to expand...
Click to collapse
The one in the Magisk repo (Downloads section in the Magisk Manager).
And which magisk module u need to uninstall before?
Click to expand...
Click to collapse
Xposed... (@topjohnwu changed the module id with version 87.2, if you don't uninstall any previous version you'll get conflicts)
Hi everyone !
I'm currently running XPosed on my One Plus 3 (Oxygen V4.5.0, Android 7.1.1), but impossible to use Xposed installer. I try to flash from recovery to install Xposed, and also from Xposed Installer. But when the installation is "finish", an my phone reboot, if I go on Xposed Installer to search for modules (better with modules I guess...), impossible to install anyone. The download start and stop a 64Kb, and no install button even if I download manually the apk. I also try to install from apk, but the module "must be activated". I try activae it from XposedInstaller, and also look in root folder for the "disable" file (see this solution on another thread) but none of these worked.
Also, I install Xposed 88.2, and when I open xposedinstaller, it's always saying to me a little notification "Please update Xposed Installer".
I try everythink, wipe my phone twice, reboots, wipe only cache after every step, reboots, reinstall Xposed, reboots, reinstall module manually, reboots, and also some reboots.
Do anyone can help me ?
Thank's a lot, and pardon my English
Solved by installing the unofficial Xposed Installer
So i recently decided to try out some of the different roms that were released for the moto e4. I decided to go back to Resurrection Remix, and when i tried to install the modules I had been using, found that some of them weren't working properly. There are no errors when they install, but seem to have no effect, such as the volume step increase, or the injected youtube background player...
other modules, like the app systemizer seem to be working just fine...
HigherStateD said:
So i recently decided to try out some of the different roms that were released for the moto e4. I decided to go back to Resurrection Remix, and when i tried to install the modules I had been using, found that some of them weren't working properly. There are no errors when they install, but seem to have no effect, such as the volume step increase, or the injected youtube background player...
other modules, like the app systemizer seem to be working just fine...
Click to expand...
Click to collapse
Did you do a clean install? (Completely wipe data and not restore it again in twrp). Some ROMs have trouble with some modules. Get logs and ask in the modules threads (the ones not working).
Clean install, full wipe, same as before, modules worked fine last install on the same rom, restore failed to boot, which is why I needed to reinstall the previously working modules
HigherStateD said:
Clean install, full wipe, same as before, modules worked fine last install on the same rom, restore failed to boot, which is why I needed to reinstall the previously working modules
Click to expand...
Click to collapse
I had a similar-ish problem on Moto g4 plus RRO.... If you still can't get it to work, here's what I did:
Rom, gapps, boot (usual steps)
Download Magisk APK from XDA
Give it storage permissions
From Magisk Manager, select install
It should ask of you want to direct patch (recommended)- select this option
Reboot and try modules again
I think it's something to do with storage permissions etc. When Magisk tries to patch boot IMG. Check your file systems too. Data partition should be fsfs and all others ext4.
If the steps above don't work try the fsfs Magisk loopback module. It's in the repo and mentions some of the Moto devices having issues with with patching boot img etc for Magisk. The module is installed via TWRP.
:good:
Got it working, somewhat similar process, ROM, gapps, MM apk, then uninstalled the magisk that came built into the ROM, and used the manager installer... Then encrypted, and then opt-enceypt... A script in sbin for my fingerprint from the original ROM and got safetynet passing.