Related
Again I face a problem, now if I hide any application the application doesn't work or open, every time it crashed.
My device: Honor 8
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Logs?
Aid777 said:
This is happening with me on LG G6. Hide is enabled in options and when I want to enter Magisk Hide to enable it then Magisk crashes.
Click to expand...
Click to collapse
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
MechanicaIMan said:
I had that problem on LG V30. I reverted to 16.0 with Manager 5.9.1, and the problem persisted. I then downgraded Manager to 5.8.3, and it's working fine again with the older version of Manager.
Click to expand...
Click to collapse
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
I'm getting this exact same issue, I've attached logcat and magisk logs after hiding the Play Store with Magisk Hide, then attempting to open it (and having it immediately crash). Magisk 17.1, latest Magisk Manager app, Pixel 2XL, Oreo 8.1 (July patch). Apps open again after deselecting them from Magisk Hide. Was working fine on 16.4, stopped working after 17.1, and a complete Magisk uninstall/reinstall did not fix it.
Magisk Log, Logcat.
Aid777 said:
5.9.1 seems to be 17.0 zip. I assume you meant that
5.8.3 is 16.7
When you downgrade do you just flash the zip or do you need to uninstall the 17.1 Magisk then flash this downgraded one?
Click to expand...
Click to collapse
I had the problem after updating from 16.0 with 5.8.3 to 17.1 with 5.9.1, but I also tried using the newest manager with 16.0, and that didn't work either. So there must be some kind of issue with the newest version(s) of the manager. I completely uninstalled 17.1, flashed 16.0, updated manager to 5.9.1 (crashing returned), then uninstalled 5.9.1 and installed the 5.8.3 apk without changing Magisk. If you have 17.1 installed now, then you might want to try just replacing manager with an older version before you bother with completely uninstalling/downgrading Magisk. You can simply uninstall the manager app without uninstalling Magisk, but I don't know if Magisk 17 will work okay with the older versions of manager, since I haven't tried that myself and don't really know anything about Magisk.
It is the same with me
Google Play Store crashed
Same here guys with LG g6, I installed the 17.1 by direct installation (within the app) and then when I go to magisk hide, it keeps crashing!
I've had the exact same experience as @mechanicalman on my V30+ (US998).
Any solution guys.
same with me, would appreciate somebody to have a look.
Magisk Hide tickboxes in Magisk Manager make Oreo crash
Hi, same with me: Oneplus3 with stock OOS 5.0.5 (oreo), dm-verity warning at boot since when I was a superSU user.
Everything was fine with Magisk 16. Since update to 17.1 and MagiskManager 5.9.1, the Magisk Hide menu keeps crashing. I've reflashed the stock ROM, reinstalled magisk 16 and 17.1, used the magisk deinstaller. The problem seems tied with MagiskManager 5.9.1
- In the MagiskHide menu, sometimes I can check 5 to 10 apps before it crashes.
- In the MagiskHide menu, sometimes only 1 check or 1 uncheck makes the phone crash.
When MagiskHide crashes it:
- blacks out the screen for a few seconds
- then starts a reboot (a soft reboot where I am not asked my device password, which I have set to be asked during boot)
- then it eventually launches Android after a very long time (usually OOS 5.0.5 opens after 20 cycles of the animation, but after a MagiskHide crash, it can take 200 cycles (from which I stop counting))
I attached the Magisk log immediately after reboot, which doesn't say much (some lines similar to previous and following ones removed).
MagiskManager: "Preserve force encryption" is on (default), "Preserve AVB 2.0/dm-verity" is off (default), Modulues are Busybox, MM for recovery, Xposed, YouTube Vanced, rest of settings are default.
I hope that helps narrowing down the problem.
I'm coming here with this issue occurring on my LG V30+ and Magisk 17.1
Hi, I'm having the same problem as a couple of people, magisk 17.1, newest Magisk Manager, then when I try to go into the magisk hide menu, the app crashes to home screen.
I enabled core only mode to see if it was any of my modules but the problem persists.
lenovo p2 same problem of manager crashing when entering hide menu
Same problem on my Nexus 5, Dirty Unicorn with Oreo 8.1
Same problem here on the V30+. Anyone able to confirm downgrading works?
Also, what do most of y'all use hide for? I was gonna try to use it to set up chase pay for that 5% rewards. lol
Didgeridoohan said:
Logs?
Click to expand...
Click to collapse
Magisk Manager v6.0.0, OOS9.0 OnePlus 6. App crashes while opening Magisk hide menu. Thanks
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS
hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.
I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.
I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...
Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).
I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet
It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk
See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.
I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.
Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.
Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.
Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.
@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.
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.
Hi. I recently updated my Moto G5s Plus(Sanders) from Android 10 to Android 11(PixelExperience). I used Magisk v21 while installation and everything worked fine. Then I installed the the v22 update through the app. However after downloading and opening the new Magisk, it shows that Magisk isn't installed and that there are updates for both Magisk and Magisk manager. Upon clicking install for manager, nothing happens, no downloading or anything. But on clicking for Magisk, it shows a select and patch method, which I don't know what to do with .
Attaching screenshot below.
Did you by any chance have the Magisk app repackaged with a random name before updating? When moving to v22+ from older releases you need to do that with the app unhidden.
If you did have the app hidden before updating you might now have two apps installed, but you should be able to fix that by uninstalling both and installing the v22.1 apk again manually.
Didgeridoohan said:
Did you by any chance have the Magisk app repackaged with a random name before updating? When moving to v22+ from older releases you need to do that with the app unhidden.
If you did have the app hidden before updating you might now have two apps installed, but you should be able to fix that by uninstalling both and installing the v22.1 apk again manually.
Click to expand...
Click to collapse
Oh my, I actually did have it hidden. I just noticed the dual apps( I think I didn't notice it before because the second one had the default android logo icon) l. Much thanks for the help
Hi there,
i used Magisk with a hidden Magisk Manager (As "Settings" in the app drawer) and i got a update notification about a new Magisk version. I updated and afterwards i read Magisk Manager is dead and isn't used anymore. When i now click on "Settings" it force closes and i can't open Magisk. What can i do now?
Device is a Oneplus 7t Pro with Stock rom.
Thanks
Try reinstalling magisk through recovery. Works for me on my Pixel 3 running LOS18. 1. Just flash the magisk zip through twrp or whatever you have.
Shouldn't be necessary to hide the magisk app. I have Gpay etc working nicely with the magisk app not hidden. Unless of course there's some other app you're running that won't work without magisk being hidden?
Okay i try to reinstall it but i think i'll wait for Android 12 to come and then start from scratch. Magisk Hide or at least hiding root is necessary for my banking app.
Same happened to me. Oneplus 8T with Android 11.