I once used to have Magisk and Xposed worked perfectly on my Xperia XZ. However today I reflashed the system firmware, flashed Magisk installer zip as usual and after everything's done flashed the Xposed installer zip, the XPERIA logo becomes REALLY SLOW (the animation lags and it takes a lot of time to boot). After that,either it reboots and get into bootloop directly, or I'm able to get in desktop. If I luckily reached the desktop and don't install Xposed Installer, I can reboot for any times I want. However if I install the Installer (if open it right after installation, it says framework is installed but not active) and reboots -- Boom! Bootloop again! The XPERIA logo just shows for about 3-5 secs and then reboots. Obviously I need the Installer to manage modules. I also tried the Systemless Module in Magisk Manager and the result is the same. I tried for a whole day attempting different conditions including changing the version of firmware and uninstalling Magisk, but the problem still exists. As I mentioned it worked before, so what the problem might be? Thanks!
whc2001 said:
I once used to have Magisk and Xposed worked perfectly on my Xperia XZ. However today I reflashed the system firmware, flashed Magisk installer zip as usual and after everything's done flashed the Xposed installer zip, the XPERIA logo becomes REALLY SLOW (the animation lags and it takes a lot of time to boot). After that,either it reboots and get into bootloop directly, or I'm able to get in desktop. If I luckily reached the desktop and don't install Xposed Installer, I can reboot for any times I want. However if I install the Installer (if open it right after installation, it says framework is installed but not active) and reboots -- Boom! Bootloop again! The XPERIA logo just shows for about 3-5 secs and then reboots. Obviously I need the Installer to manage modules. I also tried the Systemless Module in Magisk Manager and the result is the same. I tried for a whole day attempting different conditions including changing the version of firmware and uninstalling Magisk, but the problem still exists. As I mentioned it worked before, so what the problem might be? Thanks!
Click to expand...
Click to collapse
it is said xposed wont work after March security patch
BloodEdge said:
it is said xposed wont work after March security patch
Click to expand...
Click to collapse
Thanks, after tons of searching I finally found that.
BloodEdge said:
it is said xposed wont work after March security patch
Click to expand...
Click to collapse
It happened the same to me on an XZ Premium
Will that mismatch be permanent? Please can you link the statement for me?
Aerocap said:
It happened the same to me on an XZ Premium
Will that mismatch be permanent? Please can you link the statement for me?
Click to expand...
Click to collapse
try beta2, seems it's working
Related
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Boot to recovery and flash Xposed uninstaller. If you try to install Xposed again make sure you choose correct version. You need "xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530".
yiftach said:
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Click to expand...
Click to collapse
I bought this phone yesterday. I could never start using a device unless I unlock bootloader, root and install xposed. I managed to unlock bootloader, flashed TWRP and also flashed systemless SuperSu (2.74-2). Also, I installed systemless xposed (i have shared link below). Phone took sometime and making me to think it is stuck in bootloader. I switched off and start in TWRP. Wiped art/dalvik and cache. Restarted normally. Everything worked fine.
Someone suggested here how to install official xposed (http://newesc.com/es/instalar-xposed-huawei-p9/).
But I installed systemless xposed (see here: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) which works fine without the need of any changes in /system/emui/base/prop/local.pro with this line "ro.config.hwtheme=1" as mentioned in the link I shared above.
Thank you guys!
Hey,
I've been getting constant Magisk Manager crashes every time I try to run it even after multiple "full wipes" (except internal sdcard data) and I can't even get the logs because it doesn't let me access them and there's no folder with logs in them. What am I supposed to do? I already flashed the stock kernel and it didn't fix it. My ROM is the XtreStoLite and I'm using a Galaxy S6 920F. What could be causing it to crash even after "full" wipes?
Thanks
EDIT: Additionally, I can install Magisk without any problem in recovery but whenever I try to run an app that requires root rights, it shows the "Magisk Manager stopped working" error
I just did a complete wipe of literally everything I had on my phone, internal storage included and installed the rom back and magisk manager still crashes... what the hell?
Edit: Installed a logcat app to look at the logs when it crashes and here is the important part, I think:
E/AndroidRuntime(13780): Process: com.topjohnwu.magisk, PID:13780
E/AndroidRuntime(13780): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
Click to expand...
Click to collapse
Edit 2: Alright I've no idea what's wrong but v4.1 works fine, v4.2 crashes all the time even though it was working literally yesterday. Welp, whatever
Im on Resurrection Remix and when I install a Rom update, the managers "loses the root" too, I download the zip (and flash it) again and its a lucky strike if when the phone reboots, the magisk returns to normal and regain the root.
GolpeadorMágico said:
Im on Resurrection Remix and when I install a Rom update, the managers "loses the root" too, I download the zip (and flash it) again and its a lucky strike if when the phone reboots, the magisk returns to normal and regain the root.
Click to expand...
Click to collapse
That does not sound like the issue in the OP...
After a ROM update you'll have to flash the Magisk zip again, since the ROM most likely also updates the boot image, thus removing the Magisk modifications (including MagiskSU).
Didgeridoohan said:
That does not sound like the issue in the OP...
After a ROM update you'll always (well, almost) have to flash the Magisk zip again, since the ROM most likely also updates the boot image, thus removing the Magisk modifications (including MagiskSU).
Click to expand...
Click to collapse
So you are saying that I have to flash it in the same process, all together*, not flash, reboot and later flash the magisk zip?
*(Flash> mount rom zip+gapps+magisk)
GolpeadorMágico said:
So you are saying that I have to flash it in the same process, all together*, not flash, reboot and later flash the magisk zip?
*(Flash> mount rom zip+gapps+magisk)
Click to expand...
Click to collapse
You can boot up after updating, to make sure it's working and then flash Magisk. Doesn't really matter...
I usually flash the update, custom kernel and lastly Magisk zip, all in one go.
Didgeridoohan said:
You can boot up after updating, to make sure it's working and then flash Magisk. Doesn't really matter...
I usually flash the update, custom kernel and lastly Magisk zip, all in one go.
Click to expand...
Click to collapse
Oks. that´s is how I usually do it. I´m going to try again.
Guys, I´m sorry for the double post but I reinstaled it and nothing, the magisk managers says that the phone is not rooted.
***NEW: The problem is busybox. Uninstall it, reinstall magisk and problem solved.
Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....
Try installing it in recovery
I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.
Yes. It's happening to me too. Does it work if I flash this update with twrp?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.
Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.
I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?
madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )
I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.
I've been having zero luck getting this to work. Does anyone have any ideas?
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.
Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.
I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.
I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!
Laugh this is just getting worse. I uninstalled Magisk and now the phone boots straight into recovery whenever I restart it. I'd flash a stock rom but I can't find one. I think I'm in trouble...
Reinstalled Magisk and it at least tries to boot up again but it just loops.
Arsenal420 said:
I've just gotten my new fi Motorola x4 running Android 8.1.0 today. I've unlocked the boot loader via Motorola and I've rooted the device via Magisk. Since I had the Xposed framework on my old phone and loved some of the modules I wanted it on my new phone. Downloaded the Xposed Installed from the playstore, gave it root access with Magisk and attempted to install the framework. Phone is now stuck in a bootloop and it's been alternating between the androidone and motorola screens for about 45 minutes.
I tried to flash xposed-uninstaller-20180117-arm64.zip but got an error that it couldn't mount /system. Another page on the net had me holding down the power button and then spamming it ten times to tell Xposed no to load but that didn't seem to do anything at all. I created a disabled file as suggested on some sites but that did nothing to stop the bootloop:
touch /data/data/de.robv.android.xposed.installer/conf/disabled
I actually had to make the /conf directory manually since it wasn't there. Wiped the cache with no better results. Factory reset did nothing to improve the situation and I was unsuccessful with sideloading the Xposed disabler found here:
https://android.gadgethacks.com/how-to/xposed-101-temporarily-disable-xposed-fix-bootloop-0179446/
It's hard for me to grasp how a completely empty barebones android phone which has only been rooted using Magisk with no other actions taken or software installed can be be stuck in a bootloop trying to perform a standard install using the Xposed installer. Not sure you can find a cleaner environment than the one on my phone.
Anyway if anyone has thought I'd love to hear them. I can boot to TWRP without issue and my phone is visible to both fastboot and adb.
Thank you!
Click to expand...
Click to collapse
https://magiskroot.net/uninstall-magisk-module-twrp/
https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
In summary:
Step 1: Download the flasheable zip file from the Magisk module uninstaller from the following link to the PC
Step 2: Send the zip file to the SD card of the phones or to the internal memory using MTP (most of the recovery of TWRP is compatible with this method)
Step 3: Now, touch the Install button and choose the Zip file of the uninstaller of the Magisk module that you want to update.
Step 4: After the completion of the installation. Go back to the TWRP home page.
Step 5: Tap the advanced option from the TWRP homepage. Choose the terminal option now.
Step 6: Type uninmod in the terminal box and touch the input button.
Step 7: Now, you can see the list of Modules and you have to type the Number you want to uninstall (Check the screenshot below)
Step 8: Finally, the magisk module will be completely uninstalled.
Arsenal420 said:
. Downloaded the Xposed Installed from the playstore,
Click to expand...
Click to collapse
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.
Nergal di Cuthah said:
What xposed installer in playstore, playstore is not where xposed is gotten from...at all. The closest thing to it that I found is an asian trick your friends app.
Click to expand...
Click to collapse
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?
Arsenal420 said:
You are right I got the apk from here:
https://forum.xda-developers.com/showthread.php?t=3034811
Do you have anything additional to offer?
Click to expand...
Click to collapse
Ok good, I got scared for you a bit there, my post was not meant to be mean spirited but maybe you read it as such. As far as the bootloop i'm afraid i'll be no help.