Hello,i have recently rooted my phone, about 3 months, never had any issues, once bootlooped, nothing too serious until 3 days ago when i executed a module named FDE AI module,when i enter magisk after the reboot the module and superuser section was unavailable,i tried reinstalling magisk, different custom recovery to flash magisk,factory resetting,nothing,and i also noticed that the module didn't appear in the module folder when i tried to uninstall it manually since i didn't have the module section available.If anyone that encountered this problem and could help me solve it i would be grateful.
Related
I am currently using a T mobile Note 4 running firekat V4. After initially flashing Firekat V2, V3 and V4 I successfully installed xposed and was running wanam as well as YouTube adAway. Today I opened the xposed installer to check for updates to my modules and noticed the messages shown in screenshots 1 & 2 that "app version 58 was installed previously but app version "" was installed now" etc.. and "Framework not installed.." I tried to simply download the newer version of the xposed installer, install it, back out and tap framework, hit the install / Update button and reboot but it didn't change anything and I still had the exact same errors.
After multiple unsuccessful attempts the developer of the Firekat ROM tried to help. Over the last few hours he's tried to troubleshoot this with me. He advised me to use root explorer pro to delete all xposed installer files after uninstalling xposed. Redownload and install it and reboot.
Once reinstalled I followed the instructions in the main xposed sticky thread and it is still telling me framework not installed.
One thing i noticed each time I've tried to install the framework since reinstalling is that it asks me for root access even though i hit grant access every time I've been asked. I'm new to all of this but i do not remember being asked multiple times by the same app before.
i have tried to do classical installation mode approximately 10 times throughout the day and 3 times since installing the actual xposed installer app from the link posted here in the xposed forum. I have also tried the other methods of installing through TWRP. On the one method where you install through TWRP from a zip file I was unable to find the zip file to confirm the flash and install. I'm open to try whatever to resolve.
this worked for me
Exact same problem as you and this kernel fixed it
http://forum.xda-developers.com/not...lopment/kernel-kt-note4-nih-ktweaker-t2936809
Good luck.
Works this on N910F too ? I have this Problem too
Hi!
So this is my first post on xda, so please be nice
I rooted my Samsung s8 sm g950f with ambasadii, and running magisk.
When I first flashed the rom everything went ok. The first time I entered the Magisk Manager app there was a note that said that I can update the manager app to v18.1. When opened the app got a message that the app was unsupported by magisk manager. So I flashed the rom again and just didn't updated the manager app. That's one problem, here is the next one.
When I enter my banking they use a 2 step verification system. I have to go to the phone and enter a code that verifies the login. Now since I've rooted the phone I can't use it, is there any solution to this problem? The banking app does not support either a rooted phone. One of the reasons I rooted with magisk is the Magisk Hide. But I don't think it is working for me . The verification goes through the sim card.
Let me know if you need some more info to help me solve this problem!
PS: I am new to rooting
Thanks!
Welcome to XDA, Magisk and root world.
Quick tips:
Every time before trying the problematic app again, under Android settings/app, stop it and clean its cache and data. Even better to unistall it, reboot, install it again from play store. Even better before reboot go to recovery mode and wipe cache, dalvik (only those!).
Hide Magisk Manager (=repack it with a random name). You do that on Magisk Manager settings menu. After that its visible name will be only Manager (on your app drawer).
read everything here, special attention to SafetyNet and hiding other rooting tests apps may use:
https://www.didgeridoohan.com/magisk/HomePage
install MagiskHide Props Config module and use its improve hiding settings: (available for download on the Dowload menu of Magisk Manager)
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Try updating Magisk/Manager to 18.1/7.0 (last stables):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Do backups and try updating to last Canary builds. Read last posts on its thread:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Maybe the module ShellHide works better than standard Magisk Hide on your device, I don't know. Read thread:
https://forum.xda-developers.com/apps/magisk/magisk-shellhide-t3855616
For general Magisk support, usually better search and ask for help on official support thread:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
I noticed something strange, on my phone and I'm trying different ways to solve it, but it just does not "work".
I have 2 x Magisk icons in my phone and I cannot remove them, so that I only have 1 x Magisk.
Here's some background,...
My phone: OnePlus 6 [OP6], with stock Oxygen OS 9.0.9 [OOS 9.0.9] Android and running custom kernel [Omega].
I had been running a ROM [xXx NoLimits] which is a Magisk Module.
For last 11+ months, I have had no issues with my phone, no issues with Magisk, and no issues with root really.
I updated to Magisk v20.0 (but it seems it was the Beta / Canary channel) and also,
I had used the "Hide Magisk Manager" feature, for 1 specific app. to work.
Just this week, I noticed some issues with my phone or that I had 'lost' root
This happens rarely, and I just reinstall Magisk, but it resolves itself.
So, I went looking and saw an odd thing: 2 x Magisk icons.
Since then, I have tried:
- Magisk Uninstaller [Magisk-uninstaller-20191011.zip]
- Flashed unpatched BOOT.img file, Flashed TWRP. Then, rebooted to TWRP.
- Flashed Magisk, flashed the custom kernel.
Still, I saw 2 x Magisk icons.
I could see 1 Magisk was on STABLE channel, while other was on CANARY channel.
This was strange.
So, I changed the CANARY to STABLE, etc. etc...
Anyway, too many combinations of uninstalling and removing root, reinstall Magisk, etc... and I still don't know how to really uninstall Magisk and start from ZERO again.
I have lost Magisk's association to my Magisk modules too.
Can anyone help or advise?
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
I think I resolved my issue now...
I uninstalled Magisk using the official Magisk Uninstaller.
I also uninstalled the 2 x Magisk apps in my launcher, using this .APK ---> "Uninstalled SystemApps" ( https://github.com/nicolaserlonghi/UninstallSystemApps )
Then, I had to go through re-installing the BOOT.img, Magisk and most importantly, the ROM (which itself was a Magisk module).
Slowly, it populated the Magisk module list and 'SuperUser' lists, and I think I got the phone back into how I had it.
Didgeridoohan said:
Sounds like you just have two Managers installed. Uninstall them both (like you would with any other app) and install the apk manually again.
https://didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_Managers
Click to expand...
Click to collapse
Yes, exactly.
Thanks for this tip, but I reached this conclusion anyway...
and used another .apk (Unsinstall SystemApps) to remove the Magisk Manager (which was the result of using "Magisk Manager Hide",
but then I must have mixed up Stable & Canary builds of Magisk on the phone, etc.)
Didgeridoohan said:
Sounds like you just have two Managers installed.
Click to expand...
Click to collapse
One thing weird though is, quite a few modules that were previously installed are missing from the Magisk "modules" section.
When I 're-install' them, they still don't show in the "modules" section.
For Example:
Vanced, Advanced Charging Controller, etc... all have been installed, but not showing up in Magisk.
I just had a weird situation of 2 different Magisk installs (at first it seemed like 2 x Managers), but it could be 2 different Magisk builds:
stable and canary
I don't know how to explain it, but maybe the Magisk Uninstaller doesn't work properly on Canary builds?
Anyway, my issue now is modules don't get listed in the Magisk Manager.
No, you did not have two different Magisk builds installed at the same time. Can't happen...
And without more to go on (logs, etc) it's gonna be real hard to help with the module issue.
I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
You need to enter twrp and select the module causing the card machine to be deleted in the twrp advanced options, file management and data / ADB / modules directory
https://lanzoui.com/b03c2iqbi Password: han
This is the self-help brick rescue module generator made by our domestic great God. After you choose to set it, click OK to automatically brush it into the mask manager! However, you cannot select a language! You can translate screenshots by yourself! The general description of the function is to find that the card machine module regrets trying the boot mode several times. If it still fails to boot after reaching the number set above, all modules will be automatically disabled to achieve the boot effect
ruffpl said:
I need small help. I got bootloop on my Xiaomi mi note 10 lite. Something like year ago I had rooted it (after couple days of trying a lot of metods) and I after that I started to use it. By time I have been using few Magisk modules and now I wanted to try some battery savers. I had install GPU Turbo boost and I reeboted my phone. After that I had install Greenify magisk module and reeboted again. Then my phone hangs on bootloop that always finish with Mi recovery 3.0. I can go into fastboot but I dont have TWRP installed. I had enter safe mode but I dont know can I go into settings/apps/magisk and clear data (or uninstall whole magisk) without causing more problems. Is there a way to remove the module somehow without removing magisk?
Click to expand...
Click to collapse
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
Check from the section "Disabling/uninstalling modules manually". Maybe this will help
Thanks all for help I got it working. I read that all I need to do is just restart phone from safe mode and when phone will boot magisk will be disabled and it worked . I had open magisk app,removed module, flashed magisk boot image and its ok for now. Only problem that still exists is with some modules - when I want to install zip file I got extract error.
Safe mode has side effects. It's better to uninstall and install! After putting on the mask, brush in the automatic brick rescue module provided by me, and you can do it at will
If you don't understand, open the application, click the three vertical bar options on the right and directly click to confirm the default!
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
rf9992003 said:
i no have install LSPosed Zygisk
just install Safetynet Fix module Zygisk,and use Zygisk Black list,and change Magisk app name( i have install stub-release.apk this apk)
my all bank app can't detected Magisk,and work fine
google pay too
Click to expand...
Click to collapse
Exactly this, bank apps can't detect the new zygisk, at least for now, just hide magisk app, delete TWRP folder and use SNF zygisk module and the black list
hi
MisiekDP said:
Hey,
I updated my Magisk v23 do Magisk v24.1 yesterday. I noticed that hiding root from apps doesn't work for me and LSPosed modules don't work either. I looked to see if LSPosed offers a module that works on Zygisk. As it turned out there is such a module, they have been working on such a version of LSPosed for months. Module I uploaded, it worked for some time. After a while I noticed that Google Pay does not want to use my card (it sees root). I installed the Universal Safetynet Fix module in Magisk. I restarted my OnePlus 7 Pro, then cleared the Google Services data, and poriously added the payment card. I was greatly surprised as I did another reboot to make sure all changes were applied. The phone booted, the boot process took a very long time compared to how it has always booted. At the end of the bootation I felt two vibrations and that was it. The boot process ended and there was a black screen. There was no Launcher, status bar or anything else visible. The only thing I noticed was 3 options in the white window after holding down the power button - a white window and 3 options: Lock, Restart and Power off.
I've tried for hours different tricks - uninstalling Magisk, getting rid of TWRP, flashing the official ROM in TWRP (without Magisk) and nothing worked. The effect is the same every time. To sum up, I regret that I updated Magisk to v24.1. I think that Zygisk mode and modules are still very underdeveloped. The whole situation caused me to lose all the data in the application. The only recovery is copying files via TWRP. I personally have no idea how to get out of this situation to keep a working system.
Click to expand...
Click to collapse
Hello, were you able to solve this?
maycomathias93 said:
hi
Hello, were you able to solve this?
Click to expand...
Click to collapse
No. You have this same problem (phone not turning on)?
yes, the only solution in this case is to run uninstall magisk and install again without lsposed. For now use edxposed without safetynet (sorry for my google translate english)
Man, I solved this problem, going from Android 9 (custom ROM where I had the problem) to 10 (also custom ROM). I hope it helps you, greetings.