Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
EDIT:
Thanks to @seko85, anyone who had this issue disable all substratum themes and also do this:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Clear Data from Settings - Apps - Magisk Manager.
mobidor said:
Clear Data from Settings - Apps - Magisk Manager.
Click to expand...
Click to collapse
I did that, enabled any permissions required as well.
Are you using v13.1?
If you're on B25, MagiskSU force closes when allowing a "new" app root, so that could be behind the crashes
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Cyb3rzombi3 said:
Make sure that you have the latest version of magisk manager installed. Since the app got removed from the playstore you have to update manually.
Click to expand...
Click to collapse
I did yeah, the latest version is 5.0.4?
Yeah got 5.0.4 as well and latest magisk is running fine.
If that is not the problem then I don't know what else it could be
Which rom do you have installed?
nfsmw_gr said:
I did that, enabled any permissions required as well.
Are you using v13.1?
Click to expand...
Click to collapse
Yes, and no problem. Installed with TWRP.
nfsmw_gr said:
Hello everyone.
So like many I was using Magisk for root purposes on my device, more specifically v12.
It was working flawlessly until now, only thing was that Google updated their safety and safetynet would fail for a couple of weeks but I didn't mind much.
I got a notification last night that v13.1 is out and I tapped on it and tapped download and install now.
I did just that, rebooted the device and to my surprise Magisk had stopped working.
Once I entered the manager app the app would force close, i tried multiple times opening it and the result was the same.
I tried flashing the uninstaller and the un-su zip and flashed v13.1 again but the same thing happened.
I tried clearing cache and dalvik cache but it didn't help.
I even tried going back to v12 but to my surprise again v12 was force closing too!
I ended up flashing the trusted old SuperSU but I really need magisk for some modules I use.
I searched the magisk subforum but couldn't find anything that fixed it for me.
Had anyone had the same experience?
Is magisk v13.1 working for you?
How did you update? (if you were running v12)
Click to expand...
Click to collapse
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
seko85 said:
I had the same situation. The solution was:
1. Wipe dalvik cache, cache and system
2. Install the ROM I was using (RR)
3. Install Magisk 13.1
4. Install Gapps
5. Install kernel
6. Reboot to system
7. Install all modules I was using (deep buffer remover and viper for android by ahrion)
Root is working and passed safety net. Unfortunately I couldn't manage to run Dolby Lee Pro 3 by ahrion and I suppose that also war mod is not working (post data script is not working, using Magisk v12 I saw in Magisk log that war mod was executed now with Magisk v13.1 I don't see such message).
Click to expand...
Click to collapse
Alright that advice step by step was great!
Gonna try this once I get home and post back, thanks man!
Update, thanks to @seko85 and disabling any substratum theme (dunno which made it work, could be both together as well) I managed to fix the issue.
Magisk v13.1 is up and running.
Also thanks to everyone who replied.
Peace, out.
Related
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I think is a good idea to say which rom are we using and how xposed works on it. Its still an alpha, and there are many mods that dont work too. Users as @mrnickel have reported that the phone gets REALLY SLOW, and some issues like low memory.
INSTALL (at your own risk) INSTRUCTIONS:
-Make a nandroid backup
-Install apk from the thread link above
-Flash the framework zip from the same thread (updated version, bridge version 61 or up, if you flash 60 it wont work)
-Wipe dalvik cache and cache
-Reboot
Confirmed "working" on 100% stock rooted. [Thanks @jabskii. @Jhyrachy @thdervenis]
Confirmed "working" on TitanPrime ROM (now even better, the dev implemented full support for xposed)[Thanks @pantu99]
All credits to @rovo89
I tried it. Don't do it. I installed from the recovery and this happens:
1st- My cellphone is now broken. Whatsapp won't work.
2nd- My cellphone now tells that I have almost all storage full when it's not possible (see attached screenshots)
3rd- Xposed won't work
oscillat0r.lfo said:
I tried it. Don't do it. I installed from the recovery and this happens:
1st- My cellphone is now broken. Whatsapp won't work.
2nd- My cellphone now tells that I have almost all storage full when it's not possible (see attached screenshots)
3rd- Xposed won't work
Click to expand...
Click to collapse
What Rom?
Whatsapp works for me. But I have those other two bugs...dat storage and xposed doesnt work
Whatsapp started working with a reset. My system lost its date and time.
I set that up again and it's working.
The OS is titanrom with lollipop 5.0.2. The OS is working really really slow right now. It sucks because I installed it before going to vacation, not so wise move.
GUYS! DON'T INSTALL IT!
oscillat0r.lfo said:
Whatsapp started working with a reset. My system lost its date and time.
I set that up again and it's working.
The OS is titanrom with lollipop 5.0.2. The OS is working really really slow right now. It sucks because I installed it before going to vacation, not so wise move.
GUYS! DON'T INSTALL IT!
Click to expand...
Click to collapse
Keep calm, de dont know how doest it goles con Cm12 or 100% stock
I flashed it a first time:
errors with clock and disk space
Then i reflashed it again and wiped cache.
Now it works !
Jhyrachy said:
I flashed it a first time:
errors with clock and disk space
Then i reflashed it again and wiped cache.
Now it works !
Click to expand...
Click to collapse
Did you wipe dalvik too?
Humm, too late now. I will try tomorrow flashing the zip and then wiping cache and dalvik for the lulz
oscillat0r.lfo said:
Did you wipe dalvik too?
Click to expand...
Click to collapse
yes
I installed it and flashed then wiped dalvik and cache and it worked and said it installed. After boot xposed said it was installed but when I rebooted again it says xposed
Framework not installed is anyone else getting this?
Flashed in stock rom got storage bug
Flashed in cm12 no storage bug but module doesn't work and it's not a problem with module.
Just installed on XT1068, stock 5.02.
Wiped Dalvik/Cache
WORKING
Burned Toast
BlackList Pro
Native Freezer
YouTube AdAway
No Safe Volume Warning
XGEL Settings
App Settings
Network Speed Indicator
Ringer and Notification unlink
YouTube Background Playback
Exchange Bypass for Xposed
NOT WORKING
Complete Action Plus
DoubleTapToSleep
Recent Apps Cleaner
Play Store in App Info
XInstaller
APM+
Very happy with Xposed Lollipop so far!
I will continue testing modules. I am sure that pretty soon module developers will bring them up to date with Xposed Lollipop.
Jhyrachy said:
yes
Click to expand...
Click to collapse
100% stock 5.0.2?
laureano97 said:
100% stock 5.0.2?
Click to expand...
Click to collapse
100% Stock + Root
Clean install 5.0.2 with fastboot flash and root. I use TWRP.
I flashed first time, booted, refleshed and wiped cache (both) and then all worked
A lot of modules are still not compatible :/
Please and step-by-step how to install and how to copy files for 5.0.2 stock rom root
Thanks in advance
half269 said:
Please and step-by-step how to install and how to copy files for 5.0.2 stock rom root
Thanks in advance
Click to expand...
Click to collapse
1-Install a custom recovery
2-Make a nandroid backup from recovery (to sdcard1 is better, more free storage I think)
3-Install the apk from here http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
4-Flash the zip from the same thread
5-Wipe cache and dalvik
6-Reboot
In case of bootloop or something gets wrong, boot into recovery and restore the backup you did before flashing
I think its obvious, but all credits to @rovo89
Its working on my XT1068 titan prime ROM
I downloaded the apk and the zip
Installed the apk
And manually installed zip in twrp
After installing I wiped cache/dalvik cache and rebooted. Working flawlessly
This app CPU temp in status bar works but you cannot enter the app. It shows up on my status bar when I enable it on xposed installer .. Other than that this is awesome ! Thanks @laureano97
Sent from my XT1068/69 using XDA Free mobile app
If you guys are having issues like enough storage space or modules not working
1)Flash the zip into your recovery
2)Wipe Cache and Dalvik Cache
That will get rid of your "enough storage space" error
If some modules won't work its because it hasn't been updated for lollipop to work but some modules can work by changing SELinuxMode to permissive
To do that just search "SELinuxModeChanger" in appstore then once installed open it and change it to permissive then reboot your phone.
App Setting is working on my 5.0.2 Stock Lollipop but I tried Greenify and it wouldn't recognize if I installed greenify so it probably hasn't been updated to work in Lollipop and maybe some modules is also the same
OP updated
It seems like the zip rovo89 fisrt uploaded didnt work fine...An hour later he updated it. That was the problem when I flashed it first time. Bridge must be 60 or up
Hey all!
Those of you monitoring the unofficial LineageOS thread may have seen me talking about this already. I've been having issues with Magisk. I'm running their beta versions for 13.0.
So here's the story...
I have wanted to pass SafetyNet since May, when I got this phone and rooted it. I obviously went to Magisk, and when I realized that 11.6 was not passing SafetyNet, I decided to try the 13 betas. These didn't pass either, but since they were more recent than 11.6, I stuck with them. But when I heard of the Universal SafetyNet Fix Module, I immediately tried it.
Bottom line, these are my issues:
1. Magisk will not install the module. I go to Magisk Manager -> Modules -> + and select the ZIP for the module. Magisk gives me a toast saying "Installation error!" (See screenshot).
2. Okay, so now I want to start fresh and see if it works then. I boot into TWRP, flash the lastest Magisk uninstaller (08 June), and boot. Nope! Stuck on the "device unlocked" screen with ID: bad key.
3. Uhh.. maybe the stock boot image will work? I go to TWRP and flash the stock boot.img taken from the stock firmware. Still ID: bad key and I'm stuck again.
And I can boot successfully if I flash a Magisk 13.0 beta.
So, does anybody have any solutions? I think I may just have to reflash stock firmware.. not my top choice. Thank you for any help and reading through my long post :good: :highfive:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
eskamhl said:
Try to install magisk v12, it always worked for me on every rom with safetynet fix ( try also the previous uninstaller )
Click to expand...
Click to collapse
Will give it a shot and update when I see results.
Edit: Nope. I've a feeling that I'll have to start from scratch by flashing stock firmware.
Try flashing the safetynet fix in trwp.
triggerlord said:
Try flashing the safetynet fix in trwp.
Click to expand...
Click to collapse
Tried already. Still no.
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
smitharro said:
Well, as far as I can see you messed up your installation. Start from scratch:
1. Go to TWRP and wipe system, data, cache and dalvik cache.
2. Install LineageOS, GAPPS, Magisk 12 and the stable version of the safetynet fix
3. Reboot and setup your nice and clean system again.
Bottom-line: don't keep messing with an already messed up system. Start clean again. And really: don't install stock boot.img on LineageOS: that's asking for trouble! To be honest: I'm astonished it even booted!!
Click to expand...
Click to collapse
Lol, was doing this all on the stock ROM. See my original response to triggerlord's post.
Edit: issues fixed with a clean install of the pure Nexus ROM. I'm assuming this would be the case with a clean install of the stock ROM, but I am definitely not switching anytime soon (this ROM is amazing!)
Hello everyone...
I have a problem in here
Today I tried to instal Viper4Android n SeLinux Mode Changer but its say (Root Permission (SU) Required).
Does anyone know how to fix that??
Should I downgrade my supersu to 2.6x or need to reinstal Super Su
My phone LG V20 H990DS (Rooted) with super su v.2.82
Alfanizer said:
Hello everyone...
I have a problem in here
Today I tried to instal Viper4Android n SeLinux Mode Changer but its say (Root Permission (SU) Required).
Does anyone know how to fix that??
Should I downgrade my supersu to 2.6x or need to reinstal Super Su
My phone LG V20 H990DS (Rooted) with super su v.2.82
Click to expand...
Click to collapse
You should probably ask this in the viper or su threads as your problem has nothing to do with the v20
Sent from my LG-H910 using XDA Labs
Alfanizer said:
Hello everyone...
I have a problem in here
Today I tried to instal Viper4Android n SeLinux Mode Changer but its say (Root Permission (SU) Required).
Does anyone know how to fix that??
Should I downgrade my supersu to 2.6x or need to reinstal Super Su
My phone LG V20 H990DS (Rooted) with super su v.2.82
Click to expand...
Click to collapse
As a constant reminder to myself that root likes to be buggy and/or loose itself,
I just use Magisk su v.16 and everything is flawless. Try Magisk instead or if you want this to be done with SuperSU instead, you this (A Uninstaller for SuperSU, use in TWRP)
https://drive.google.com/file/d/16Cs-DjOaG6bPSctB-gHBzUZY3nNGQINH/view?usp=drivesdk
1. Uninstall SuperSU
2. Then Flash the latest zip of SuperSU.
I hope this has helped you out.
ROOT67 said:
As a constant reminder to myself that root likes to be buggy and/or loose itself,
I just use Magisk su v.16 and everything is flawless. Try Magisk instead or if you want this to be done with SuperSU instead, you this (A Uninstaller for SuperSU, use in TWRP)
https://drive.google.com/file/d/16Cs-DjOaG6bPSctB-gHBzUZY3nNGQINH/view?usp=drivesdk
1. Uninstall SuperSU
2. Then Flash the latest zip of SuperSU.
I hope this has helped you out.
Click to expand...
Click to collapse
Bro i tried to instal magisk 16 but error when installing??
Alfanizer said:
Bro i tried to instal magisk 16 but error when installing??
Click to expand...
Click to collapse
What ROM are you using ?, if you're using stock maybe try formatting the Data Partition only and wiping dalvik cache and cache, then reboot to system. Do the setup, make sure to disable the automatic system updates in the setting under the developer options (Go to about phone and tap the build number 7 times, then go to developer options.) Then once done, reboot to TWRP and flash Magisk 16.0 zip and remember to wipe Dalvik cache and cache before rebooting.
If you are using a custom ROM, then just wipe everything in TWRP and flash the ROM zip, wipe dalvik cache and cache, reboot and go through the setup. Once done, go back to TWRP, flash Magisk 16.0 zip and remember to again wipe dalvik cache and cache before rebooting.
Optional: You can use root permissions to let Magisk do a direct install in the Magisk Manager apk.
Hi,I've just installed:
lineage-14.1-20190713-UNOFFICIAL-clark
from androidfilehost. I am stuck In a bootloop but have been able to restore a backup. I'm using hashbang's moddedrecovery TWRP which is the only one I've ever had any luck booting a ROM with.
I've wiped data/system and tried installing it with and without gapps but still only get bootloop.
I notice this latest nightly has magisk 19.3 built-in and wonder if this may be the culprit? I'd really like to update for security updates as my stable build is quite outdated now.
Many thanks if anyone can help
captain sideways said:
Hi,I've just installed:
lineage-14.1-20190713-UNOFFICIAL-clark
from androidfilehost. I am stuck In a bootloop but have been able to restore a backup. I'm using hashbang's moddedrecovery TWRP which is the only one I've ever had any luck booting a ROM with.
I've wiped data/system and tried installing it with and without gapps but still only get bootloop.
I notice this latest nightly has magisk 19.3 built-in and wonder if this may be the culprit? I'd really like to update for security updates as my stable build is quite outdated now.
Many thanks if anyone can help
Click to expand...
Click to collapse
Did you check the md5 checksum?
Sent from my perry_f using XDA Labs
hello, thanks for replying.
checked original and matched. re-downloaded and checked that one as well just in case, also matched. same result
** Edit - Problem Solved - My Fault/Strange Glitch
Soooo, I tried a few more times to install the latest nightly and whenever the rom was finished installing, Magisk 19.3 was also attempting to install. this is not because magisk is included in the rom, because it's not. even after advanced wipe > everything apart from microSD card and clearing my zip queue several times, magisk was still trying to install after the rom.
I went back to stock 7 install using fastboot and the necessary files then reflashed modded TWRP via fastboot, rebooted, and installed the latest nightly and gapps together and rebooted. so far so good thanks again for replying.
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Dirty flash ROM or if 1st step doesn't work factory reset and install everything
Same here. I don't want to do a factory reset.
I tried to:
- uninstall Magisk from twrp
- flash the boot.img of the rom
- flash the previous version 21.2 of magisk
but none of this worked!
I have the same Issue. Havoc 3.9., Magisk 21.4.
I tried to dirty flash the rom, uninstall magisk 21.4 via twrp, and flashing 21.2.
Didn't help. Occassionally I got into the system, but the screen is a bit more white than usually, I can type in my lock password, but after this, System UI fails.
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
[email protected] said:
Yesterday I flashed the fix for safetynet passing after the latest update, which made it work again, and I remember that at the relevant magisk forum, somebody mentioned that would affect System UI somehow. Now I am trying to repair the System UI to see if it works as a solution.
Click to expand...
Click to collapse
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
en_ha87 said:
I'm running Android 10 with EvoX rom and after last update of Magisk to 21.4 the phone is stuck on bootloop. After going to recovery and uninstalling Magisk I have the same problem, it's still in bootloop. What can I do to fix the problem?
Click to expand...
Click to collapse
Same problem occur with me ,i just unistall 21.4 and indtal 20.4 veraion but nothing happens then i just wait for 5-10 min on bootloop screen and it starts processing it's updating my new boot image ... This thing happens when i update my miui after completing the process i finally see my homescreen
Lars0n89 said:
What fix are you talking about? Where can I acquire it?
EDIT: In my case the bootloop was caused by the Systemless Xposed Framework module v90-beta2 by rovo89 (packaged by topjohnwu). Disabling that module allowed me to boot normally.
Click to expand...
Click to collapse
How can you install that Module from TWRP?
That i remember i never installed it, it's automatically loaded with magisk?
To solve this problem i had to format the phone, installing the OS again and also magisk v21.2. But Today i got the same problem... so maybe is not the versione of magisk. But I don't know of to solve it.
I tried also the sotck boot.img, but it stays some seconds on the boot screen of lineage OS and then reboot again stucking on Mi logo.
i also had to install stock rom, lost all the data on the phone. today i have to install custom rom, and will probably pass on the magisk, i don't need sh**t like this happening again.
I had to reinstall the rom from scratch, and needed to format data partition too. After flashing my ROM back, I installed magisk 21.2 and it works great.
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Could you help me i got into a bootloop after doing the magisk direct update from the app. My discord is : SneezeOnYou2#8507
I believe that i have a backup in twrp just dont know how to flash or uninstall or what ever to do i dont want to lose my data. I can record my screen if you add me on discord.
flavioggl said:
I solved:
-go in fastboot mode
-flash twrp recovery
-go in twrp and with mtp insert magisk-uninstaller.zip and last magisk-21.4.zip
-run uninstaller.zip than installer.zip
-reboot in system
Click to expand...
Click to collapse
Thank you, brother. It was a simple solution but I forget to do that. After wasting 2 hours finally able to solve the problem. Thanks again.