Hi everyone,
I followed this guide to install Magisk v14 on my Huawei P10:
https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
Root is working fine. However, MagiskHide doesn't seem to be working. Firstly, I am unable to pass Safetynet. Also, when I try to hide root by using Magisk Hide to select the app (for example, Root Checker), root is still detected by Root Checker.
Lastly, when I enable/disable the option "Magisk Hide" from settings, the logs don't show any response. I tried enabling/disabling using a Terminal, but there is still no response.
I've run out of ideas, and any suggestions would be greatly appreciated.
Many thanks.
What worked for me (after many tries) was:
- install Magisk 12 (not Magisk 14)
- install Magisk Manager
- within Magisk Manager, update to Magisk 14, checking the two boxes as on the tutorial you linked do.
Hey, thanks for the reply. I did try to do what you did, but for me Magisk Hide wasn't working. No logs were generated when I tried enabling / disabling MagiskHide in Settings. Does yours work?
Yes, the checks worked. But I had another issue (Sound and Settings stopped working). I ended up doing a factory restore and decided that root is not for me on the P10. It just doesn't seem stable enough. Will wait a few years for my next phone, I can live without it.
Hope you have better luck that I did.
Related
Hi everyone,
I am using the application Raiffeisen Twint (version 1.2.16.0, https://play.google.com/store/apps/details?id=ch.raiffeisen.twint) on my Magisk's rooted Google Pixel (Android 8.0, Nov. 2017) without problems for a while, but since Magisk 14 versions, the application stopped working and the application reports that root is detected.
I have successfully updated to Magisk 14.5 (from 14.2), but root is still detected by the application, even with Magisk Hide activated for the application and the Magisk Manager package moved to a random name (could also be related to the updated application).
I have cleared the data of the application several times and it doesn't help and root is still detected by the application...
Anyone has a idea?
Thanks for your answers!
Like I said in the Magisk support thread, I can hide Magisk from that app just fine (on Magisk v14.5 beta)...
You don't happen to have any other mods that might trigger an app looking for root (like Xposed)? Can your device pass SafetyNet? Have you previously been rooted with any other root method and do you have any remnants of that left (root management apps, etc)? Do you have any apps that are known to be used for questionable purposes. By "questionable purposes" I mean getting access to paid features without paying, etc. Not necessarily that you use the app for this, but that the app might be used in such a manner... Etc, etc, etc. Every little detail might count.
Hi Didgeridoohan,
Thanks for helping me!
I do not have any mods installed in Magisk and also no Xposed. My device is passing SafetyNet!
I have performed a factory reset last week and since that I only rooted my device with Magisk 14.2, so no other rooting applications used. For details, I have unlocked bootloader, TWRP recovery installed and developer options and USB debugging activated.
My settings in Magisk are:
I have following applications installed on my device:
https://pastebin.com/pmt4jBMV
Do you see any applications with "questionable purpose"?
I get this message in the application:
Thanks a lot!
At a quick glance everything looks ok...
I did some experimenting with the other Raiffeisen apps you have installed, in case they also detect root and "tell" on you. At least one of them did detect root, but from what I could see it didn't make any difference for Twint.
I also tested installing a few of the root apps you had installed (in case the app looks for certain known apps), but that didn't make any difference either. I could still successfully hide root.
My guess is that it's something along these lines tough. That it's using another app or detecting a root app. You could start experimenting with that. Clearing data for the other Raiffeisen apps and adding them to MagiskHide and also removing root apps. Try disabling USB debugging and developer options as well (didn't make difference for me, but worth a shot).
Simple. Change name of package from settings in Magisk Manager, then MAKE SURE you add twint app to magisk hide list, then ERASE DATA of twint app, change package name once again and run twint. Working with Magisk 14.5. Screens if u want available. Or video.
Hi Didgeridoohan, Hi Mamama07,
Thanks for your help, but sadly none of your suggestions did worked... until the update of the application released yesterday, to fix problem related to rooted devices! [emoji3]
Thanks anyway again for your help! [emoji106]
I had the same problem (with BCV Twint) and after a few tries, changing Magisk Package Name worked!
Magisk Hide (Masking Magisk SuperUser) - 2 Problems w/ Magisk Hide being disabled after reboot or closing Magisk Manager.
If you are using Magisk Manager and Magisk Root and are experiencing difficulty with Magisk Hide (Masking Magisk's SU) not showing in the Manager's side-menu or remembering its status in settings, it occurs when a file is not automatically deleted and removed.
PROBLEM:
Open Magisk Manager, Settings >> Enable Magisk Hide, close Manager, re-open and Magisk Hide is disabled and not visible (hidden) in the left side-menu. i.e. Exit, Close, Stop, Re-Open & Reboot Reset's Magisk Hide's State to Disabled.
SOLUTION 1.
Force stopped Magisk Manager.
Backup then Delete file /data/property/persist.magisk.hide (0600).
Launch Magisk Manager.
Go to Settings >> Enable Magisk Hide.
Go back to Manager home screen. Swipe to reveal side-menu and check Magisk Hide menu is visible.
Close Magisk Manager or Force stop.
Reopen and Swipe side-menu and confirm Magisk Hide is still visible!
I hope this helps others also experiencing issues with Hiding Super User SU. Thanks Shak!
SOLUTION 2.
Another Fix someone else has also posted Dec 2017 was in regards to an error "fopen: /magisk/.core/magiskhide/hidelist failed with 2: No such file or directory"
The issue is due to Magisk Manager being unable to save the list of ticked Apps to hide from SU to /magisk/.core/hidelist.
Check the existence of the "/magisk/.core/hidelist" path.
Create the "/hidelist" directory.
CHMOD "/magisk/.core/hidelist" to 0644.
Thanks to Dunderball. :highfive:
.
Thanks a lot! I have been looking this issue up for almost a week now.
Solution 1 worked for me.
No worries mate. Appreciate the feedback.
Someone else had a similar issue for a few weeks and was unable to resolve it until upgrading to 16.4 beta. But this isn't viable for everyone due to issues w/ 16.4+.
Thanks!
monsterkrusher said:
Thanks a lot! I have been looking this issue up for almost a week now.
Solution 1 worked for me.
Click to expand...
Click to collapse
I would like to add to this thread that this doesn't work anymore with the newer versions of magisk. Eget did work for me though was to delete (and backup of course) /data/adb/magisk.db and then restart
tgcGlaDius said:
I would like to add to this thread that this doesn't work anymore with the newer versions of magisk. Eget did work for me though was to delete (and backup of course) /data/adb/magisk.db and then restart
Click to expand...
Click to collapse
which version you use ?
I use version 19.4, wont work if delete magisk.db.
LineageOs 17 on a Nexus 2013 Flo
Magisk 19.3
Magisk Manager 7.3.2
safetynet always fails after a reboot.
I tried renaming magisk.db and while magisk kept working generally, m-hide still fails the safetynet test after a reboot until I toggle hide.
kevin mitnick said:
which version you use ?
I use version 19.4, wont work if delete magisk.db.
Click to expand...
Click to collapse
michaelh99 said:
LineageOs 17 on a Nexus 2013 Flo
Magisk 19.3
Magisk Manager 7.3.2
safetynet always fails after a reboot.
I tried renaming magisk.db and while magisk kept working generally, m-hide still fails the safetynet test after a reboot until I toggle hide.
Click to expand...
Click to collapse
Download The Module Of MultiFunctions From This Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386 For Getting The Ability To Use Either The Sub-Function Of Hide Keeper Or Hide Enabler.
Dreamer(3MF) said:
Download The Module Of MultiFunctions From This Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386 For Getting The Ability To Use Either The Sub-Function Of Hide Keeper Or Hide Enabler.
Click to expand...
Click to collapse
I'll have to try that sometime in the future when I've got more time to experiment. I ended up going back to stock just to have a working tablet. I only use it for maps and streaming and since Netflix wouldn't work...
How to make a bakup?
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'm running, on a Huawei Mate 10 PRO, an official Huawei ROM BLA-L29 8.0.0.157 (C432) with no custom kernel or script installed via TWRP. I only have Magisk 18 running with a couple of modules such as Android Pie Fonts, Busybox, DNSCrypt-Proxy 2, Pixel Experience, Youtube Vanced. Root works perfectly on the device with many applications. Now I'm struggling with two things that don't work at all:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
FYI: On Magisk I have the "Keep forced encryption" set and "Keep AVB 2.0/dm-verity" unchecked. I tried with "Keep AVB 2.0/dm-verity" set and re-installed Magisk but problem is still there.
I looked at Magisk's log but can't see any outstanding issue or error message.
Can someone help me to solve this issue since some banking applications are now blocking me? Thanks a lot.
PS: I tried to use an alternativel fingerprint via the MagiskHide Props Config module but that didn't help.
SafetyNet with Magisk 18.0
alphazo said:
- SafetyNet check: it takes many minutes to complete and at the end I get an "Invalid answer"
- Magisk Hide: as soon as I register an application in Magisk Hide I can no longer launch it. Clicking on the icon doesn't do anything.
Click to expand...
Click to collapse
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Thanks a lot for your pointers. I finally got it working and thus even with Magisk 18
It was a combination of many factors.
Here is what I did first:
Fully uninstalled Magisk 18
Installed Magisk 17..3
Selected applications lilke a simple Safetynet checket app under Magisk Hide
Started the Safetynet checker app and it worked.
Then I started to re-install my Magisk modules including Pix3lify (former Pixel Experience module) for an alternate launcher and found out that this was causing the issue.
I uninstalled this module and then decided to upgrade to Magisk 18. Magisk Hide didn't work at first since a simple Safetynet checker app wouldn't pass.
I had to go back to Magisk Hide panel and unselect all the apps that were previously registered before selecting them again and this time it worked.
Thanks again for your pointers and I hope the above will help other people.
PhilippeSX4 said:
Hi alphazo,
I had the same problem with my Huawei Mate 10 Pro since I went from 17.3 to 18.0.
I tried several solutions like you, but nothing worked. The only thing that worked was to downgrade to version 17.3, there, everything was functional.
For my part, I completely uninstalled Magisk from my phone and then reinstalled it. After that, everything works perfectly and I have no problems with SafetyNet.
You just have to reconfigure the Magisk Manager application and choose which applications you want to hide.
I hope it will work for you too ! :good:
Click to expand...
Click to collapse
Hi, can someone please help? I can't get SafetyNet check to pass in Magisk Manager, not even basicIntegrity.
I have tried everything here:
https://www.didgeridoohan.com/magisk/MagiskHideSafetyNet
... and here (in addition to digging around XDA forums)
https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
I have a oneplus One running LineageOS 16 with microG pre-installed (https://lineage.microg.org/)
Specific troubleshooting steps taken, each step taken with TWO device restarts after:
1) Magisk Manager is hidden (via Magisk Hide in the Manager)
2) I am only using Magisk modules i.e. no BusyBox, xposed, etc.
3) After having issues I tried disabling all Magisk modules and rebooting twice
4) I tried the osm0sis unSU script, I flashed it in TWRP then deleted Dalvik/cache and rebooted twice, only Magisk was found
5) Developer options/USB debugging are both disabled
6) I froze in Titanium Backup any app needing root then hid Titanium Backup in Magisk (do I need to fully uninstall Titanium Backup and/or other apps with root?)
7) I tested magiskHide with a root checker app - it works, the root checker reports successful root then I hide the root checker with MagiskHide and when re-checking root then fails as expected.
8) I tried to reset fingerprint props but I reverted the settings back when this didn't help. Does anyone have any more info about this please? Unfortunately I already altered the props on my OPO and I don't have stock Cyanogen ROM available to me (it's spyware anyway!!)
A few related question please:
1) I don't need to use Systemizer plugin anymore, correct? As MagiskHide can handle this now? Or do I?
2) I tried a few SafetyNet fixes/modules but none worked... should I try more i.e. PetNoire's SafetyNet Spoofer? https://forum.xda-developers.com/apps/magisk/universal-safetynet-fix-magisk-17-t3840680/page5
Unfortunately I am not sure that I can attach a logcat output file as I am brand-new to XDA and have <10 posts.
Thank you all so much!
ertrink3n said:
I have a oneplus One running LineageOS 16 with microG pre-installed (https://lineage.microg.org/)
Click to expand...
Click to collapse
I believe this might be the key to your problem. I'm not entirely sure, but I think there might be issues passing SafetyNet on MicroG.
Try looking through MicroG threads/forums for info and help rather than Magisk.
Didgeridoohan said:
I believe this might be the key to your problem. I'm not entirely sure, but I think there might be issues passing SafetyNet on MicroG.
Try looking through MicroG threads/forums for info and help rather than Magisk.
Click to expand...
Click to collapse
Micro G can't pass safety net no more cause the Droid helper hasn't been updated....
([emoji3590]09-09-18[emoji3590])
Thank you for the confirmation @PoochyX, that's what I thought, but since I don't use or keep track of MicroG I wasn't sure.
@ertrink3n That's your answer.