MOD EDIT: PLEASE MIGRATE TO THE OFFICIAL CANARY BUILDS
THIS THREAD IS ABOUT UNOFFICIAL COMMUNITY BUILDS. OFFICIAL BETAS THREAD IS HERE: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589.
This thread is dedicated to the community-built next versions of Magisk and MagiskManager using latest source files posted by @topjohnwu. If you want to contribute in any way -- create a PR/issue on github.
These might be very unstable builds, especially in the early stages of development. You're highly advised to read the rest of this post and at least a few last pages of the discussion.
Downloads are here: https://github.com/TheComputerGuy96/MagiskFiles. Keep reading if this is your first visit to this thread or for the updates at the bottom of this post.
Current builds are courtesy of @kantjer. This project wouldn't have happened without @Deic's module to track the snapshot updates (which may be hindered by recent @topjohnwu changes in versioning) and his contributions to the build script, as well as major contributions in supporting fellow community members by @Captain_Throwback, @Didgeridoohan and @DodoGTA.
Installation:
Magisk: flash magisk snapshot from recovery, it should install over any previous version just fine.
Magisk Manager: The snapshot APK is signed with a different key than the release APK so you can't install snapshot magisk manager over magisk manager from Play Store. You will need to uninstall existing Magisk Manager and install the snapshot APK afterwards.
Commits Logs:
Magisk (master branch)
Magisk Manager (master branch)
IF SOMETHING DOESN'T WORK AND/OR CRASHING:
No support of any kind is implied, however it's a community forum so some users (including local experts) might be willing to help your and/or your report might be helpful to @topjohnwu, but please make sure to follow the below:
Magisk Manager crashing? Problem with Magisk module? Post installed versions of magisk, magisk manager, versions of all installed modules and the magisk log + logcat.
Downloads: https://github.com/TheComputerGuy96/MagiskFiles
Source code: https://github.com/TheComputerGuy96/Magisk (branch travisci-dev)
Travis-CI link: https://travis-ci.org/TheComputerGuy96/Magisk
That's nice of you. What is the change log?
Cool! I'm gonna give this a try and see if some of my issues are resolved.
Filip013 said:
That's nice of you. What is the change log?
Click to expand...
Click to collapse
We can check the commits log for now: https://github.com/topjohnwu/Magisk/commits/master and https://github.com/topjohnwu/MagiskManager/commits/master.
@topjohnwu, what's the reasoning for disabling MagiskHide when SuperSu is installed?
gamer765 said:
@topjohnwu, what's the reasoning for disabling MagiskHide when SuperSu is installed?
Click to expand...
Click to collapse
Because Magisk Hide don't work with SuperSU? Maybe...
Viper4android is working well S7 nougat
Verstuurd vanaf mijn SM-G930F met Tapatalk
Didgeridoohan said:
Because Magisk Hide don't work with SuperSU? Maybe...
Click to expand...
Click to collapse
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
Ok, cool... Did not know that was possible. Since topjohnwu himself have stated that Magisk Hide can NOT hide SuperSU, I assume he has a good reason to do what he does.
Think about saying stupid things, you should have respect for the guy. Just turn on magisk hide, do not tick supersu in gui
Verstuurd vanaf mijn SM-G930F met Tapatalk
afcaajax said:
Think about saying stupid things, you should have respect for the guy. Just turn on magisk hide, do not tick supersu in gui
Verstuurd vanaf mijn SM-G930F met Tapatalk
Click to expand...
Click to collapse
Not sure if you're directing that at me, but no one here is saying stupid things, except maybe you. Plus, I'm a dev/hacker myself so it doesn't really bother me, since I can always fix it myself.
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
If you haven't yet, please consider creating an issue for that on github and let @topjohnwu know.
AFAIK you can checkout the code one commit before the problematic one and build your own v10.
PS. Please don't feed the trolls.
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
That's unexpected, it never worked previously, I just added the detection I should have done in ages.
I'll try it myself when I got time, once confirmed working I'll revert this change
gamer765 said:
I have MagiskHide working perfectly with SuperSu 2.79 on Nougat. I can use PoGo and AP. The latest Github commit breaks it.
Click to expand...
Click to collapse
I'm not sure how you're accomplishing this, but it shouldn't be possible, unless you're also using some other hiding method (suhide, RootSwitch). Magisk Hide cannot hide SuperSU. I just installed it and tried it to confirm, since your post piqued my curiosity, but not surprisingly, SafetyNet came up all red, and my AirWatch app shows compromised.
Can you explain in detail what your setup is and confirm you're ONLY using SuperSU and Magisk Hide, and pass with green for SafetyNet?
Ah, well I am using suhide and rootswitch as well and everything works perfectly fine for me.
I've attached screenshots of SafetyNet passing for me. By all means, it's your project, you may do whatever you wish with it, I'll just fork it and make my own private builds where SuperSU does not disable MagiskHide..
gamer765 said:
Ah, well I am using suhide and rootswitch as well and everything works perfectly fine for me.
I've attached screenshots of SafetyNet passing for me. By all means, it's your project, you may do whatever you wish with it, I'll just fork it and make my own private builds where SuperSU does not disable MagiskHide..
Click to expand...
Click to collapse
Let me take a moment and just lay my palm against my forehead...
I'm gonna go out on a limb and guess what you're really using Magisk Hide for is hiding your unlocked bootloader with resetprop. There are other ways of doing that, you don't need Magisk Hide.
No, I do not. I use it for other stuff as well. All my mods are systemless. I'm on completely stock system with a custom kernel that does not pass bootloader unlock flags. I'm not a dumb person, but I see I'm being treated that way. I do things the way I do them for a reason. I will no longer partake in this conversation, I have better things to do. Maybe it's better to just stick to stock because ignorance is bliss. I need a break anyways from my work. Bye and thank you.
gamer765 said:
No, I do not. I use it for other stuff as well. All my mods are systemless. I'm on completely stock system with a custom kernel that does not pass bootloader unlock flags. I'm not a dumb person, but I see I'm being treated that way. I do things the way I do them for a reason. I will no longer partake in this conversation, I have better things to do. Maybe it's better to just stick to stock because ignorance is bliss. I need a break anyways from my work. Bye and thank you.
Click to expand...
Click to collapse
Well if you want to use SuperSU with Magisk Hide, just manually revert the change that disallowed it. That takes 10 seconds to do.
Captain_Throwback said:
Well if you want to use SuperSU with Magisk Hide, just manually revert the change that disallowed it. That takes 10 seconds to do.
Click to expand...
Click to collapse
His question still stands, if MagiskHide does work with SuperSu installed and there're viable use cases for that, why disable it?
stangri said:
His question still stands, if MagiskHide does work with SuperSu installed and there're viable use cases for that, why disable it?
Click to expand...
Click to collapse
I don't think @topjohnwu was considering those extended use cases when he disabled it. Maybe now that he knows, he'll revert that change. I think he was thinking that Magisk Hide can't directly hide it so it would always be detected. With several other tools, it's apparently possible to hide it, which is good to know. Personally, I'll just be sticking with the open-source solution anyway, so it doesn't really affect me.
EDIT: Besides the fact that there are many people who will enable it, not knowing that Magisk Hide can't hide SuperSU. I think the change was in an effort to prevent those types of questions.
Related
As many of you know Nintendo's first mobile app Miitomo crashes on most custom kernels and ROMs. Since version 1.2.0 Miitomo does no longer check for root, but it checks the value of 'ro.debuggable'. If 'ro.debuggable' is set to '1' by the kernel (in /default.prop), Miitomo will crash.
So what this Module does, is to set 'ro.debuggable' to '0', using the shiny new resetprop introduced in Magisk v9. This Magisk Module is meant for people who can't use Xposed or don't want to.
For Xposed users, check my SecurityBypasser Xposed Module.
Tested on Lux (Moto X Play).
Download and Code over at github.
Can you make another module that sets ro.build.type=user in build.props?
Link_of_Hyrule said:
Can you make another module that sets ro.build.type=user in build.props?
Click to expand...
Click to collapse
Should not be a problem. Any particular reason?
Setialpha said:
Should not be a problem. Any particular reason?
Click to expand...
Click to collapse
Because Android Wear won't work if it's userdebug.
EDIT: I was able to make a script based on an existing script for something else thanks for your reply. This is the script I made if anyone needs it.
@Setialpha This still works great and you should get it put on the Magisk module repo.
Link_of_Hyrule said:
@Setialpha This still works great and you should get it put on the Magisk module repo.
Click to expand...
Click to collapse
+1
I can't install this on magisk with the install module feature. Does it work through twrp?
Brentboy said:
I can't install this on magisk with the install module feature. Does it work through twrp?
Click to expand...
Click to collapse
That's likely an issue with MagiskManager, flashing through TWRP will work.
Setialpha said:
That's likely an issue with MagiskManager, flashing through TWRP will work.
Click to expand...
Click to collapse
Thanks, and is there away to make this work for puzzle and dragons jp? I'm in nougat so can't use your xposed module :/
Just FYI it also helps with Super Mario Run.
This actually allows me to play Mario on my Oneplus One with resurrection remix ROM.
Thank you very much
So I do need to run that script of I don't want to have Android Wear issues?
well it helped in playing Mario Run but it made Yugioh duel links stop working so i uninstalled it
going to give this a try for mario. thanks very much!
WORKS!
Guys... Since v11.5 Magisk changes this prop value by default. If you're keeping up to date, there's really no need to flash the module, just enable Hide...
That is not working in resurrection remix (redmi note 3)
---------- Post added at 03:40 PM ---------- Previous post was at 03:36 PM ----------
Didgeridoohan said:
Guys... Since v11.5 Magisk changes this prop value by default. If you're keeping up to date, there's really no need to flash the module, just enable Hide...
Click to expand...
Click to collapse
That is not working in resurrection remix (redmi note 3)
I still think it would be great if this was added to the magisk module repo I know a lot of people probably use it.
Sent from my Nexus 7 using Tapatalk
Link_of_Hyrule said:
I still think it would be great if this was added to the magisk module repo I know a lot of people probably use it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It won't be added...
1 - Magisk Hide changes this prop by default. If someone has issues with Hide, there's always modules like this and you could also very easily make a boot script utilising resetprop.
2 - @topjohnwu have clearly stated he won't add modules that only changes a prop value to the repo. This is an upcoming feature in the Manager.
Didgeridoohan said:
It won't be added...
1 - Magisk Hide changes this prop by default. If someone has issues with Hide, there's always modules like this and you could also very easily make a boot script utilising resetprop.
2 - @topjohnwu have clearly stated he won't add modules that only changes a prop value to the repo. This is an upcoming feature in the Manager.
Click to expand...
Click to collapse
Oh ok so basically I don't even need this module any more?
Sent from my A0001 using Tapatalk
Link_of_Hyrule said:
Oh ok so basically I don't even need this module any more?
Click to expand...
Click to collapse
U don't need it, because magisk already does what this module does since months.
I'm using ResurrectionRemix Rom on my LG G3 Beat and Pokemon GO v. 0.67.2 and as soon as I install Magisk (used MagiskHide and tried many things) v. 12 or v. 13 beta it stops working. My device passes SafetyNet so it should not be a issue. Someone having this issue too? How can I fix that?
Edit: I finally found the issue. It's KernelAdiutor.
Thinkofname said:
I'm using ResurrectionRemix Rom on my LG G3 Beat and Pokemon GO v. 0.67.2 and as soon as I install Magisk (used MagiskHide and tried many things) v. 12 or v. 13 beta it stops working. My device passes SafetyNet so it should not be a issue. Someone having this issue too? How can I fix that?
Click to expand...
Click to collapse
Why do you use a pogo version that isn't forced yet? 0.67.1 works totally fine.
No need to update, especially not, if you don't know what the update contains and what it is doing.
Go to magisk settings and then to tick the "core only mode" checkbox. Reboot and you are done.
Google has strenghten SN policies and now Magisk modules functionality makes you fail SN check. The temporary solution is to disble all modules related functionality following the steps above.
Sent from my SM-G930F using Tapatalk
I've created a Pokemon Trainer Club account, just for these occasions, when once in a while someone comes in and have issues with PoGo not starting. Anyway...
Tried both 0.67.1 and 0.67.2 and they start up just fine on Magisk v13.0 (54e6a79) beta, OnePlus 3T, OxygenOS 4.1.6, Franco Kernel r24 and nothing else done except having enabled Magisk Hide. Does Resurrection Remix have ro.build.tags set to "release-keys" (and so on)?
DaSoul said:
Why do you use a pogo version that isn't forced yet? 0.67.1 works totally fine.
No need to update, especially not, if you don't know what the update contains and what it is doing.
Click to expand...
Click to collapse
On 0.67.1 I had the same issues
coto39 said:
Go to magisk settings and then to tick the "core only mode" checkbox. Reboot and you are done.
Google has strenghten SN policies and now Magisk modules functionality makes you fail SN check. The temporary solution is to disble all modules related functionality following the steps above.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Tried it, but it won't work, I'm using this module to fix my safetynet bypass but it still don't work with it.
Didgeridoohan said:
I've created a Pokemon Trainer Club account, just for these occasions, when once in a while someone comes in and have issues with PoGo not starting. Anyway...
Tried both 0.67.1 and 0.67.2 and they start up just fine on Magisk v13.0 (54e6a79) beta, OnePlus 3T, OxygenOS 4.1.6, Franco Kernel r24 and nothing else done except having enabled Magisk Hide. Does Resurrection Remix have ro.build.tags set to "release-keys" (and so on)?
Click to expand...
Click to collapse
Checking that, I'll edit this comment when I've done that
Edit: Universal SafetyNet Fix edits them already
Are you able to pass safetynet check?
Sent from my SM-G930F using Tapatalk
coto39 said:
Are you able to pass safetynet check?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
That's what it says in the OP...
Didgeridoohan said:
That's what it says in the OP...
Click to expand...
Click to collapse
Ups. My bad.. I forgot about that.
Sent from my SM-G930F using Tapatalk
Btw. I found out using Magisk v. 13 beta with Core Modules Only does not pass SafetyNet, not even Basic Integrity. Seems a bit strange.
Found something in the magisk logs, there is a entry for every app that is listened in my Magisk hide List but not for pokemon go
Thinkofname said:
Found something in the magisk logs, there is a entry for every app that is listened in my Magisk hide List but not for pokemon go
Click to expand...
Click to collapse
It doesn't have to be on the list. It's using SafetyNet that is on there by default.
Didgeridoohan said:
It doesn't have to be on the list. It's using SafetyNet that is on there by default.
Click to expand...
Click to collapse
But what exactly makes it don't run?
Rootbeer sample in hide-list does not detect root at all...
Thinkofname said:
But what exactly makes it don't run?
Rootbeer sample in hide-list does not detect root at all...
Click to expand...
Click to collapse
No idea... If you're passing SafetyNet you've got some other issue than it detecting root.
Thinkofname said:
Btw. I found out using Magisk v. 13 beta with Core Modules Only does not pass SafetyNet, not even Basic Integrity. Seems a bit strange.
Click to expand...
Click to collapse
Try Using Universal SafetyNet Fix v2 Beta 3 with Magisk v12
and, what did you mean when says doesn't work? I guess you may have mock locations in dev settings enabled or Xposed installed.
I think I found the issue! I completly reinstalled RR, Magisk etc. with my apps but don't configured my other apps. Pokemon GO worked fine. After configuring Kernel Adiutor it doesn't let me in.
Edit: Yep, uninstalled it, reboot and started PoGo, it's working.
Thinkofname said:
I think I found the issue! I completly reinstalled RR, Magisk etc. with my apps but don't configured my other apps. Pokemon GO worked fine. After configuring Kernel Adiutor it doesn't let me in.
Edit: Yep, uninstalled it, reboot and started PoGo, it's working.
Click to expand...
Click to collapse
Would interesting know what configuration you did in Kernel Adiutor, it can helps others.
Edit: @Didgeridoohan how many times did occurs this to we? xd
Thinkofname said:
I think I found the issue! I completly reinstalled RR, Magisk etc. with my apps but don't configured my other apps. Pokemon GO worked fine. After configuring Kernel Adiutor it doesn't let me in.
Edit: Yep, uninstalled it, reboot and started PoGo, it's working.
Click to expand...
Click to collapse
Great. I'm curious as to what you're doing with Kernel Adiutor to cause this issue?
Edit: Ninja'd!
Didgeridoohan said:
Great. I'm curious as to what you're doing with Kernel Adiutor to cause this issue?
Edit: Ninja'd!
Click to expand...
Click to collapse
Just lowered my max. cpu freq, max. gpu freq, edited some cpu governor settings and edited my lmk settings.
Guys, I wonder, is anyone able to run Pokemon Go with other modules enabled in Magisk or is it still not possible ? With Viper4Android to be precise.
MartinMGS said:
Guys, I wonder, is anyone able to run Pokemon Go with other modules enabled in Magisk or is it still not possible ? With Viper4Android to be precise.
Click to expand...
Click to collapse
Did you try Universal SafetyNet Fix v2 Beta 4? Is in the first page of this sub-forum
Hello everyone !
I will develop a new app like Magisk but very easy to install and manage.
Opened this thread because i am tired of bootloops and rom installs i had and also i am curious how many people are happy with Magisk.
Feek free to post your thoughts here.
I also need a name for this app so please suggesting one will be a good thing.
reserved
reserved 2
Magisk is a pretty amazing app. One stop shopping for many of my Superuser needs. I use it for audio mods anti G-spy stuff and much more. Magisk works great for me but I love having options. Good luck, interested to see were you go with this.
Regards
Sent from my SM-G900V using XDA Labs
Hmm... Interesting. Magisk is beast honestly. I was a tried and true SuperSU user and nothing else for years and it took me awhile to make the complete switch to magisk but it's amazing. Not onyl is root reliable, I always pass safety net, and there are tons and tons of modules for magisk which makes it that much better. Development is booming for Magisk and the modules.
1. Are two reserved posts necessary?
2. Magisk is pretty easy to install and manage already. Especially with the number of supported devices.
I'm all for options/competition but why not contribute to Magisk?
loserskater said:
1. Are two reserved posts necessary?
2. Magisk is pretty easy to install and manage already. Especially with the number of supported devices.
I'm all for options/competition but why not contribute to Magisk?
Click to expand...
Click to collapse
1. Yes. These post are necessary.
2. I do not think magisk is easy to install ( especially when updating )
3. :highfive:
AndrOmega said:
2. I do not think magisk is easy to install ( especially when updating )
Click to expand...
Click to collapse
For my own curiosity and in the interest of possibly helping to improve Magisk, what kind of issues do you have when updating?
Didgeridoohan said:
For my own curiosity and in the interest of possibly helping to improve Magisk, what kind of issues do you have when updating?
Click to expand...
Click to collapse
i wanted to update from 14 to 16 from manager= bootloop
installed with twrp= bootloop
uninstalled from twrp with magisk uninstaller=bootloop
reflashed clean rom=cannot install magisk anymore
quited and building a better app :highfive:
AndrOmega said:
i wanted to update from 14 to 16 from manager= bootloop
installed with twrp= bootloop
uninstalled from twrp with magisk uninstaller=bootloop
reflashed clean rom=cannot install magisk anymore
quited and building a better app :highfive:
Click to expand...
Click to collapse
While you're building your app, the recovery log and boot image from from that clean install could be very useful and possibly help make Magisk more robust and compatible with more devices. :good:
AndrOmega said:
i wanted to update from 14 to 16 from manager= bootloop
installed with twrp= bootloop
uninstalled from twrp with magisk uninstaller=bootloop
reflashed clean rom=cannot install magisk anymore
quited and building a better app :highfive:
Click to expand...
Click to collapse
I've never had any of these scenarios happen. When I dirty flash ROM with Magisk already installed, I flash over top and everything is same as before dirty flash. If I uninstall, then reinstall, obviously it's a clean setup. I've never had bootloop 9nce I don't think. Your most likely not dirty flashing, thus it is compressing imag over image essentially when trying to uodate. Mgisk says restore stock boot I'm going before updating, which is what dirty flash does. If you would either dirty flash or just flash stock boot image before doing any of the things you've attempted you most likely won't bootloop
Yes. I have encountered alot of situation -bootloop and softbricks- where the culprit is magisk. I eventually thought not to use it but I'm obliged to use it for its quite awesome module mechanism. Thefore, every possiblity that involves magisk with no bootloop is appreciated.
Magisk 16 and Samsung Galaxy S5=Safety Net failed
All is ok only on Magisk stable 15.3
AndrOmega said:
i wanted to update from 14 to 16 from manager= bootloop
installed with twrp= bootloop
uninstalled from twrp with magisk uninstaller=bootloop
reflashed clean rom=cannot install magisk anymore
quited and building a better app :highfive:
Click to expand...
Click to collapse
Didgeridoohan said:
While you're building your app, the recovery log and boot image from from that clean install could be very useful and possibly help make Magisk more robust and compatible with more devices. :good:
Click to expand...
Click to collapse
Why build your own app when you can build upon a great foundation that is magisk ? Working as a community.. nothing beats it.
Many minds is better than one!
fOmey said:
Why build your own app when you can build upon a great foundation that is magisk ? Working as a community.. nothing beats it.
Many minds is better than one!
Click to expand...
Click to collapse
@fOmey magisk development is now halted and i predict that will be stopped by google in the near future (android p)
my new project is based on CYDIA SUBSTRATUM ENGINE and will be a great root and xposed tool !
:highfive:
AndrOmega said:
@fOmey magisk development is now halted and i predict that will be stopped by google in the near future (android p)
my new project is based on CYDIA SUBSTRATUM ENGINE and will be a great root and xposed tool !
:highfive:
Click to expand...
Click to collapse
Not really ("halted") and possible but unlikely ("android p"). I appreciate the hubris but think such positive energy would be better invested in collaboration with the Magisk team/community which brings considerable expertise and experience to the table.
AndrOmega said:
@fOmey magisk development is now halted and i predict that will be stopped by google in the near future (android p)
my new project is based on CYDIA SUBSTRATUM ENGINE and will be a great root and xposed tool !
:highfive:
Click to expand...
Click to collapse
Well if your apps can stop Xposed from triggering Safetynet then yes you will have a lot of support from user including me...
Sent from my A0001 using Tapatalk
iPusak Gaoq™ said:
Well if your apps can stop Xposed from triggering Safetynet then yes you will have a lot of support from user including me...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
i am focusing on xposed implementation with passing safety net test :good:
AndrOmega said:
@fOmey magisk development is now halted and i predict that will be stopped by google in the near future (android p)
my new project is based on CYDIA SUBSTRATUM ENGINE and will be a great root and xposed tool !
:highfive:
Click to expand...
Click to collapse
Doesn't Cydia Substrate require root? So people would need Magisk anyway? And hasn't Cydia been dead for a long time?
No offense but you seem to like to get people hyped with nothing to show for it so there's going to be some scepticism.
Davey126 said:
Not really ("halted") and possible but unlikely ("android p"). I appreciate the hubris but think such positive energy would be better invested in collaboration with the Magisk team/community which brings considerable expertise and experience to the table.
Click to expand...
Click to collapse
Completely agree
Hello everyone!
Since Snapchat is one of my most used social app and unfortunately i use a rooted device with custom ROM.
I've seemed to try all the hiding methods on the forums inuding, Playstore Visa, Magisk HideProps and all.
Tried Magisk Hide, but that fails to. Enabling core only module messes up my Magisk Completely, i dont know how
So i need to to know what factors trigger Safetynet.
My Device -
Samsung galaxy core prime
CrDroid 7.1.2
Magisk 16.2 Beta
Kernel SElinux permissive (if it matters)
Thanks!
If you scroll down here, you'll find a table with examples over the different things that'll trigger SafetyNet:
https://developer.android.com/training/safetynet/attestation#compat-check-response
But, are you passing SafetyNet or not? You're only talking about Snapchat, and if I remember correctly you can pass SafetyNet and Snapchat will still complain.
Didgeridoohan said:
If you scroll down here, you'll find a table with examples over the different things that'll trigger SafetyNet:
https://developer.android.com/training/safetynet/attestation#compat-check-response
But, are you passing SafetyNet or not? You're only talking about Snapchat, and if I remember correctly you can pass SafetyNet and Snapchat will still complain.
Click to expand...
Click to collapse
No i do not pass Safetynet.
SnapDrag910 said:
No i do not pass Safetynet.
Click to expand...
Click to collapse
I'm going to assume you've checked here (if not, here's a great link):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
And you can always take a look at the basics (what Magisk can't hide, as an example):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Magisk_can_not_hide
And if nothing else, here's some info on what to provide when having problems:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Asking_for_help
Didgeridoohan said:
I'm going to assume you've checked here (if not, here's a great link):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_SafetyNet
And you can always take a look at the basics (what Magisk can't hide, as an example):
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Magisk_can_not_hide
And if nothing else, here's some info on what to provide when having problems:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Asking_for_help
Click to expand...
Click to collapse
Whoa! thanks alot @Didgeridoohan
Sometimes rooted phones , and custom ROMs
Also kernel in rare cases and Xposed
Cherifiali said:
Sometimes rooted phones , and custom ROMs
Also kernel in rare cases and Xposed
Click to expand...
Click to collapse
Ok. Thanks to all for helping me. Ill give my phone one more shot.
Also @Cherifiali my phone has -
Rooted -
Custom Kernel -
Xposed -
Custom ROM -
SnapDrag910 said:
Ok. Thanks to all for helping me. Ill give my phone one more shot.
Also @Cherifiali my phone has -
Rooted -
Custom Kernel -
Xposed -
Custom ROM -
Click to expand...
Click to collapse
Maybe you ROM so
Try saftynet modules for Magisk
Lately I upgraded to Magisk 24.1 from 23 and lost the usual stealth features then reverted back to 23 again. Everything works fine except for hiding the app. Now some apps detect root and don't work. When I use the feature an extra icon for Magisk named "Settings" is created that does not open the app. The original icon is not removed and opens the app like usual. If I leave it like that, I eventually lose root, then I have to uninstall the Settings app for Magisk to work again. I tried to uninstall and reinstall Magisk many times but still experience the same behavior. Something is clearly broken but I don't know how to fix it. Anyone faced the same problem or has any idea what to try?
if the feature doesn't work please try to contact me later thank you!
koryonp10 said:
if the feature doesn't work please try to contact me later thank you!
Click to expand...
Click to collapse
It does not work. I've been fighting with it for a couple days now.
ok so you need to try to restart your phone and if that doesn't work please try to email me at [email protected] i know a lot more than people think
also send me a video
The solution to your issue has been posted here: https://forum.xda-developers.com/t/rename-hide-magisk-not-working-for-v23.4396841/
Why do you want to downgrade though? v24.1 has denylist which works similar to magisk hide. All you need to do is install Universal Safetynet Fix (Magisk modules) and everything should work.
simplydat said:
The solution to your issue has been posted here: https://forum.xda-developers.com/t/rename-hide-magisk-not-working-for-v23.4396841/
Why do you want to downgrade though? v24.1 has denylist which works similar to magisk hide. All you need to do is install Universal Safetynet Fix (Magisk modules) and everything should work.
Click to expand...
Click to collapse
Worked a treat, thank you very much! Basically I downgraded because everything worked fine with the old version of Magisk and I didn't bother to search for a different solution. Is that the best module to pass Safetynet? I think I saw there's a few solutions available.
ser848 said:
Worked a treat, thank you very much! Basically I downgraded because everything worked fine with the old version of Magisk and I didn't bother to search for a different solution. Is that the best module to pass Safetynet? I think I saw there's a few solutions available.
Click to expand...
Click to collapse
Magisk 23 + Magisk Hide was detected by many bank apps I have and I was tired of dealing with it, so I decided to upgrade.
Magisk 24 + Universal Safetynet Fix + Shamiko worked like a charm and everything has been hidden and I have a feeling I won't have to deal with root hiding for a long time.
simplydat said:
Magisk 23 + Magisk Hide was detected by many bank apps I have and I was tired of dealing with it, so I decided to upgrade.
Magisk 24 + Universal Safetynet Fix + Shamiko worked like a charm and everything has been hidden and I have a feeling I won't have to deal with root hiding for a long time.
Click to expand...
Click to collapse
Thanks a lot again, I will give it a try.
koryonp10 said:
if the feature doesn't work please try to contact me later thank you!
Click to expand...
Click to collapse
koryonp10 said:
ok so you need to try to restart your phone and if that doesn't work please try to email me at [email protected] i know a lot more than people think
also send me a video
Click to expand...
Click to collapse
Hello and a very warm welcome to XDA, @koryonp10. I hope you'll always get the assistance you require, and much more we appreciate your intentions to provide your knowledge and expertise to other members. Thanks very much for that!
Please allow me to share with you the principle of this website:
XDA Developers was founded on the simple principle that SHARING IS GOOD and when many people SHARE what they know, EVERYONE benefits. We exist upon this ethos. We RESPECT each other, we SHARE with each other, we do not judge one another, and we HELP all who ask.
Click to expand...
Click to collapse
In order to live this spirit, I suggest to consider to publicly share your knowledge in the threads and not to drag the XDA members to your email, private messages or outside of XDA. Only from what you publicly posts, all can learn and are able to ask corresponding questions. Thanks very much for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
I have Magisk 24 + Universal Safetynet Fix + Shamiko installed on Android 11. It warns me that Shamiko not active as "denylist is enforced'. Regardless, I still get a warning message when I start my HSBC banking app.
simplydat said:
Magisk 24 + Universal Safetynet Fix + Shamiko worked like a charm and everything has been hidden and I have a feeling I won't have to deal with root hiding for a long time.
Click to expand...
Click to collapse
Hi, have read the changelog from magisk 24 that hide not included.
Saftynet Fix i think i have read this in past, i hope i find it. I have find this thread, but how get Shamiko?? And is Zygisk also needed?
At Moment i have HTC U11 with magisk 23 + riru lsexposed, because i need xprivacy.
richardmace said:
I have Magisk 24 + Universal Safetynet Fix + Shamiko installed on Android 11. It warns me that Shamiko not active as "denylist is enforced'. Regardless, I still get a warning message when I start my HSBC banking app.
Click to expand...
Click to collapse
Same issue here not on android 11 though.
richardmace said:
I have Magisk 24 + Universal Safetynet Fix + Shamiko installed on Android 11. It warns me that Shamiko not active as "denylist is enforced'. Regardless, I still get a warning message when I start my HSBC banking app.
Click to expand...
Click to collapse
Hi @richardmace have you fixed for HSBC Banking App? I had same issue
No, not fixed but not a major issue as app still works. I am now not enforcing the deny list and Shamiko is now active.
I am new to the subject but have similar issue. There is an medical application for diabetes in Google Play. It is called Freestyle Libre 3. "3" is important as there are "1" and "2" versions of this app. This app is used to monitor glucose with the help of external device that is placed on the body via bluetooth. The application has two "features" so far:
1) it is available only on a few smartphones (a few Apple's and a few Samsung's)
2) it is available only in few countries (GB, DE, NL, SE and just a few more)
All my bank apps work with zygisk but this medical app doesn't. I added this app and all google play services on deny list. YASNAC shows passed for basic integrity and cts profile. I tried Shamiko and Universal Safety Fix too. Hiding Magisk doesn't help. still no success. But once Magisk is uninstalled the app starts and works.
Could it be somehow an unusual case when application devs made up some one trick more than Magisk is assuming for apps that check for root? Is there any hope to have this app working on LineageOS with Magisk installed?
The working solution is to allow "USB Debugging" in "Developer options", and additionally by Xiaomi, turn off "MIUI Optimization".