yashsingh1/xdaforums huggingface dataset:
[Magisk] Jean_85:
Tried:

- magisk unistaller + wipe cache: still failing

- flash latest LOS weekly + latest Gapps + wipe cache: still failing + vendor mismatch

- flash latest boot/vendor/radio: cannot boot to system, used wrong stock version (too new)

- reflash LOS+GApps + wipe cache:

it's booting, still vendor mismatch BUT BASIC INTEGRITY PASS for SafetyNet, hence PoGo is working again!

- reflash right boot/vendor/radio: still didn't boot

- reflash LOST+GApps+wipe cache: works, afraid of flashing magisk for now!
[Magisk] teddy0209:
Yup, you should ask there... Hope you get your answer there. Perhaps you can switch to global stable for ur device as a last resort...
[Magisk] AXelzero1:
Magiskhide was working earlier today but out of nowhere I'm tripping safetynet. Any help is appreciated
[Magisk] teddy0209:
Did magiskhide start properly? Tey to toggle it off and on...
[Magisk] Jean_85:
Flashed Magisk 12 and SafetyNet is green, great!!

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Magisk] alexdpaul:
I've tried to install Magisk with Google Pixel ROM.

I've followed the installation guide on the Magisk official guide - but Magisk SU doesnt want to be installed.

What did you change/unistall on the ROM, prior to installing Magisk?
[Magisk] Jean_85:
I'm having the same issue on my Nexus 5X with latest Lineage. (see previous posts)

(edit) I re flashed Magisk and wiped cache now I have root and SafetyNet is still green
[Magisk] houston_:
If I install magisk on my CM12.1 rom that passes saftynet...

I get a endless saftynet check instead of failing or passing one :(

Any Ideas about this?
[Magisk] alexdpaul:
What process did you use to:

Flash Magisk, and

Wipe cache?
[Magisk] teddy0209:
Play services crashing... Try force closing it and clear data... Or try reflashing gapps.
[Magisk] houston_:
I will try later this day, thanks! :)
[Magisk] 135Shadowsoul:
hi every1,

short question: if i flash magisk v12 from here and update the manager with playstore, is magisk hide enabled by default? some people told me, its not, but i tried it and it was (and not passing SN...)

thanks for answer.

€dit: now clean flashed rom and it was not enabled... strange

=> question answered :)
[Magisk] houston_:
Okay, tried this now:

Wipe all (excl. internal), flash order: CM12.1 + gapps + unSU -> Restart

SN check green.

Back to recovery: wipe cache/dalvik + flash magisk + gapps again.

Restart, MagiskHide activated, SN check red ... :(

Updating Google via Playstore -> red...

Can't stop play service, only deactivate it.
[Magisk] 135Shadowsoul:
Hi,

i figured out, adaway but also magisk adblock lets SN fail. is there anything else i could do to block adds?

grettings

€dit: looks like substratum (or time gated???) fails SN, too :(

---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------

as i was confused a bit, sometimes it seems magisk hide is enabled by default, but sometimes not. is it enabled in your case after flashing? and why did you reflash gapps? maybe this could a problem, too
[Magisk] Tesla:
It's a bit strange, but i have found that wiping cache and Dalvik cache and install Magisk again solves many problems.

Sometimes complete reboobs and flashing Magisk is needed more than one/twice.
[Magisk] Edozullo:
i flashed Magisk 12 all is ok, but after a few days i haven't root no more, must to uninstall ed reinstall magisk from recovery and lost all modules downloaded. What is the problem?
[Magisk] Didgeridoohan:
Hide isn't enabled by default. If you haven't removed the Manager between installations, the Manager settings from a previous installation will still be there. Maybe that's why it seems like Hide is already enabled after a clean flash.

There have been some reports about systemless hosts causing SafetyNet to fail. Don't think I've seen any proper troubleshooting about it though and it's probably a ROM specific issue. I've never experienced it...

---------- Post added at 14:16 ---------- Previous post was at 14:14 ----------

On some custom ROMs this can be caused by having Magisk busybox enabled.
[Magisk] Edozullo:
Thank you. I've disabled it now.
[Magisk] 135Shadowsoul:
now its working, but it looks that its timegated SN fails. but this is realy strange...
[Magisk] Pkt_Lnt:
:eek: GF or wife? :cool: :D
[Magisk] Tesla:
You'r mom :p:good:
[Magisk] Pkt_Lnt:
necrophilia!

[/OT]
[Magisk] 135Shadowsoul:
strange... it seems not to be time gated, but i do not know why sometimes it fails (untill reboot) and i am currently not able to reproduce it
[Magisk] rignfool:
Added a flag to build.prop to let Tasker know it's rooted?

What property?
[Magisk] Pkt_Lnt:
# modversion

Keep the hash.

https://tasker.dinglisch.net/userguide/en/faqs/faq-problem.html#root
[Magisk] CrazyCypher:
Because it is very compatible I am using phh's superuser... Are there any drawbacks over SuperSU or I wont see a difference if I only need SuperSU for a few apps?
[Magisk] soder:
OK, but I guess AP isn't in Sweden yet (if ever).

If I want to try the other SuperUser, do I then uninstall SuperSu from inside the app, or do I only have to flash my ROM again from recovery and flash the other SuperUser instead, with Magisk and systemless Xposed?

/Söder
[Magisk] Artim_96:
Well, since it's all in all just a module, it could be enough to put an empty file called "remove" in the directory and reboot
[Magisk] soder:
In what directory?

/Söder
[Magisk] Artim_96:
/magisk/phh
[Magisk] JudgeDread11:
He wants to install phh and uninstall SuperSU.

I haven't used SuperSU so I'm not sure but you should find something recognizable in the /magisk folder.

Most likely the mod folder will be called "SuperSU". :)
[Magisk] soder:
Yes there was.

OK, so, this modded version of SuperSu is installed different then the normal version?

/Söder
[Magisk] Artim_96:
Oh... You're right. It just doesn't happen that often here that someone has SuperSU. But yes, there should be something like /Magisk/SuperSU

---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------

Yes. The normal version patches the boot.img and is standalone. In Magisk, the patching part of file by Magisk, so that SuperSU version shouldn't be patching the image and should be installed like every other module
[Magisk] soder:
This is what I did now:

Wiped /system, flashed ROM, Magisk, phh's SuperUser and systemless Xposed.

After boot I will install the phh's SuperUser apk from Play Store. Since before I got the material version of Xposed apk installed.

I then need to give my apps root access in the new SuperUser app instead, and after that I hope everything is as normal.

But, if I want to use apps like AP or my video streaming apps doesn't like root, shall I then disable root in the Magisk manager and run the apps, or what shall I do?

The reason I ask is cause before all this I was about to try chainfire's hidesu, where I hide specific apps and not disable root.

Can I disable Root-Cloak now with this way to hide root, or is that still something that might work (or is it just old)?

/Söder
[Magisk] Nomelas:
So I am using root check app and see that superuser is installed to /system (see attached)

I thought the system partition wasn't supposed to be touched?
[Magisk] KaMyKaSii:
The app is recognizing the binary mounted on system, not written
[Magisk] soder:
OK. I did all that, and in Magisk manager, and after that I could go further in AP then I ever could. I think the problem now is that I live in Sweden.

Anyhow, I still couldn't get my video streaming apps to work. I will try to both disable Root-Cloak and also to wipe data of the apps.

Edit: Don't I have to reboot after enabling and disabling modules in Xposed now when running systemless?

Edit: Wiped data of the two apps. Same problem as before wipe. One app just loading and loading, and the other app crashes. (C More and TV4 if there are any other from Sweden that might help me.)

/Söder
[Magisk] adrman:
I'm not sure if anyone reported in this thread yet, but over in phusson's SuperUser thread there's a rewrite of his SuperUser app, if anyone wants to give it a try. It seems to be working fine for me.
[Magisk] KaMyKaSii:
The link is down. You could send the apk?
[Magisk] adrman:
Sorry about that. I just made a post to [MENTION=5444464]PunchUp[/MENTION] asking for permission to post it and if there was a reason the link is down.

EDIT: The link should now be active.
[Magisk] daleski75:
Thanks to the developer on this one I have managed the impossible and that is to get Barclays mobile banking working on cm13 whilst the phone is rooted, still cannot get android pay working but it's almost a non-issue as I can do contactless payments through the Barclays app anyway.
[Magisk] izeeqo:
Hello everyone,

I want to ask if SnapPrefs is compatible with Magisk xposed please? Thank you
[Magisk] AndroidGee209:
Yes it's compatible.
[Magisk] izeeqo:
Thanks for your answer. I have an LG G3 D855 with stock Android 6.0 Marshmallow and a custom kernel (Xceed Kernel ) i'm rooted and I have xposed v86 sdk23 arm. I would like to install systemless xposed, magisk and phh's superuser to use Snapchat without uninstalling Xposed, must i uninstall root and xposed and replace by systemless xposed, magisk and phh's superuser ? or what do i do please ? can you help me? Thank you
[Magisk] Fedroid:
Yes, you have to uninstall xposed an root totally, then flash magisk, root and xposed.
[Magisk] rignfool:
Can I put this in a system.prop file for a module... Can I use resetprop? Or do I have to hard edit the build.prop?
[Magisk] Pkt_Lnt:
I dunno. ;)

I edited my build prop since on PN my /system is already modified and OTA is irrelevant.

Try it.
[Magisk] rignfool:
Well... It didn't work when I put it in an already working system.prop

Could I just 'resetprop #modversion' in post-fs-data.d?

I am perpetually attempting to set my device up with Tasker and such to be ready for when everyone gives up on custom ROMs since Google is closing source for all their toys...

*shakes fist*
[Magisk] Pkt_Lnt:
I hear ya. Putting this in the build.prop solved not only Tasker but the old Secure Settings which still does a ton for me as long as I can get it root, since it has not been updated in 3 years and has no clue what "systemless" root is. :rolleyes:

This worked for me, I have not played with the post-fs-data.d stuff, so I'm no help. Maybe someone else will chime in?
[Magisk] rignfool:
I am getting this feeling it has to be a hard edit...

Pent specifically says it has to be the top line of the build.prop... is that where you have placed it?
[Magisk] Pkt_Lnt:
yes
[Magisk] jhedfors:
Magisk Core Only Mode

[MENTION=4470081]topjohnwu[/MENTION] - I am a little confused as to the purpose of this setting. Is there any difference between having this checked, or simply not having any modules?

If this is simply disabling the Magisk Modules function, why not take it a step further and hide the "Modules " and "Downloads" sections, along with renaming the toggle to "Disable Magisk Modules"?
[Magisk] karthik km:
Hello guys can any one tell me why this happening in my device (miui)

Please look at the attachment once

You will understand my question
[Magisk] Didgeridoohan:
If you want to do this systemlessly you'll have to make a module that replaces the build.prop file with one that you've edited.

It's not a prop you can edit with resetprop, but a comment line in the file.

You could probably set up a module that copies your build.prop and then inserts the required line and mounts the edited file.
[Magisk] rignfool:
Magisk loads before the actual build.prop?

So I can just make a new build.prop... Put it into a module with proper path and it will load that instead of the actual build.prop?
[Magisk] Didgeridoohan:
Yes.

---------- Post added at 16:20 ---------- Previous post was at 16:17 ----------

Don't know what that could be about. Try another app as well. SafetyNet Playground works well...
[Magisk] biggdevon:
Do you have that root checker app selected in Magisk Hide?
[Magisk] Didgeridoohan:
It's not a root checker, but a SafetyNet tester. And adding it to the Hide list shouldn't make a difference...
[Magisk] Citizen_Snips:
He's failing SafetyNet, not root check. I use the same app and I pass it all. If I hide root from root checker pro, I still pass SafetyNet. Doesn't matter.

More info on his setup would be useful. Phone, ROM version, etc. Those pictures don't tell anything at all.
[Magisk] biggdevon:
Thanks, I used a very similar looking app that had different screens for root check and SafetyNet. But after reading your reply I realized my current root checker (not hidden) sees root and passes SafetyNet so my previous question is indeed useless.
[Magisk] maelfilk:
Not the first time happended to me. I flashed clean rom and magisk. Root was working fine. Than suddenly after 3-4 reboots it dissapeared for no reason. Is this considered normal?
[Magisk] Rush94:
Pokémon go is saying failed to detect location have magisk installed used to work earlier after updating os it fails now i downgraded back 2 old version can some1 help i known its not the right thread but magisk was design for Pokémon go to work with root access help help me asap i think i need loc zip to flash or something else ?
[Magisk] joelh:
If you updated your ROM, assuming you are on nougat and need microg in your system partition, you need to reinstall microg to /system. It still works.
[Magisk] Rush94:
Can you provide the link that i can directly flash in the twrp
[Magisk] joelh:
I don't have it on me, but you can search for [MENTION=5627087]ale5000[/MENTION]'s Unofficial microG Installer thread and find it there.
[Magisk] karthik km:
I've tested SafetyNet with some other app

It says CTS profile match true

But basic integrity false

So the Magisk will check only CTS profile Mismatch Error but not all

And other SafetyNet apps will check all required things to pass SafetyNet

Screenshot attached

Am I correct?

Any idea how to fix basic integrity failure

And thanks for the previous Reply
[Magisk] Artim_96:
You are the first one managing that afaik...

For those things there is a thread giving hints on what you can try to pass, mostly it's stuff like SELinux set to enforce (or Magisk's pseudo-enforce) and some props
[Magisk] 135Shadowsoul:
Hi every1,

on my GT-I9505 (Samsung Galaxy S4) with Opt. LOS 14 (Stable2, lates build) i have some strange problems with magisk. sometimes, at the moment i can not reproduce it by will, but sometimes SNcheck fails, after a time of passing it. does any1 has an idea why this happenz? and how to solve it? maybe rom-related?

the second thing i want to ask/tell: "magisk adblock", "adaway", "substratum" and "secure settings" (at least as system+) cause SN fail, too. is there any chance to fix it? if you need a link to any of the mentioned apps, just tell me :)
[Magisk] yochananmarqos:
With Adaway or similar you need to enable systemless hosts. You can use App Systemizer to systemize Secure Settings. Substratum should not make a difference.
[Magisk] Rush94:
My device is Motorola and i flashed for the same and guess what lost all my contact and now i cant login to google acc

Now i have to clean flash everything :(
[Magisk] 135Shadowsoul:
i will try, "enable systemless hosts" is what i was talking about with "magisk adblock".

i will give it a new try tomorrow. thanks for fast reply. i will report what happens.

secure settings has its own system+ conversion, to enable some more features. i need it in 2 cases: 1. enable/disable NFC (if there would be any shell command i could run with tasker it would be ok, too) and 2. monitor if mobile network is enabled to disable Wifi (unless there is no other idea, how to :) )
[Magisk] android404:
Hey. I hope this is the place for stupid questions.

I rooted stock nougat on my moto g4 plus using phh's superuser. Can I simply install magisk through the installer now? Is the automagic boot image detection reliable? Other things I really should think about before proceeding (whilst at the cabin
[Magisk] Pkt_Lnt:
Another possibility, maybe. Too tired to read it or try it now, long night, no sleep. :(

https://xdaforums.com/apps/magisk/module-app-systemizer-t3477512
[Magisk] ale5000:
It is in my signature.
[Magisk] Artim_96:
Don't think you should, would only cause problems. Remove it, probably flash stock boot.img and then Magisk.

But I don't know if your device uses F2FS for cache and data like other motorolas and if so if they fixed the big preventing Magisk to run. You probably should ask in your devices forum
[Magisk] tag68:
For Moto Z Play f2fs loopback device was said to be fixed with Patchlevel march 2017. Don't know if it is true and if it is, if the same applies to G4 plus.

For Magisk hide to work, you need to remove other root solutions before flashing Magisk. If f2fs is broken and data partition is f2fs, you need to flash a kernel with the fix before flashing Magisk.
[Magisk] rsd2000:
Samsung Galaxy Note 4 (6.0.1) on v12 fails on SafetyNet and gives installation error on any module.

AFAIS, there are mixed info about stability on Samsung devices. V12 seems to correct a lot of errors and other people seems to be downgrading. However, I cannot find any solid information yet.

Can somoene, please, point me, if this is a known issue?

-rsd
[Magisk] Didgeridoohan:
Update 2017-12-28: Updated to Magisk module template 1500, just in case someone actually still uses this and wants the latest and greatest. Module version v1.05.

Update 2017-11-24: Updated to Magisk module template 1410. Cleanup of old scripts added. Module version v1.04.

Since it seems like Tasker uses the presence of the Magisk Manager to know if your device is rooted or not, the new Hiding Manager feature breakers Tasker's root detection. Looks like this module still has a use... :) Nope... That doesn't work. If you hide the Magisk Manager Tasker can't detect root, even with this module. If you're using shell commands, add "su -c" to the beginning of the command.

Update 2017-09-06: Just in case there's still someone out there not wanting to update to Tasker v5+, v1.03 for this module is compatible with Magisk v14.0+.

Update 2017-07-20: Tasker v5.0 has been released and this Magisk module is no longer necessary. I'll keep it here though, for anyone who doesn't want to move with the times... :laugh:

Edit: And for any users of Secure Settings.

Update 2017-07-15: Ha ha ha! When migrating to the v4 template I accidentally forgot to include the actual script in the zip! :laugh: If you've previously downloaded v1.02 and haven't been able to get it to work, download it again.

Update 2017-07-11: Update to Magisk module template v4. Version 1.02 of this module is only compatible with Magisk v13.1+. Users with older versions of Magisk must use version 1.01.

Update 2017-07-02: Small update to the module to work around a boot script bug with the new boot script implementation in Magisk v13.0 beta.

Update 2017-05-05: Apparently Secure Settings works the same way Tasker does and will recognise MagiskSU with this module installed.

What does this module do?

It adds the following line to build.prop:

# modversion this line enables Tasker root support

Source: http://tasker.dinglisch.net/userguide/en/faqs/faq-problem.html#root

[MENTION=4403217]Pkt_Lnt[/MENTION] [MENTION=3290808]rignfool[/MENTION]

Just for fun I tried making a module like the one I talked about earlier. One that copies the stock build.prop to the module and edits in the comment line for Tasker root support. Have been wondering for a while how it would be done. Now I know...

Tested on my Nexus 6 and OnePlus 3T. It's just a proof of concept for myself, but I thought I'd share it if anyone else wants to try it out.

The next version of Tasker will have support for MagiskSU, but until then we'll need workarounds like this.
[Magisk] Tesla:
Samsung Galaxy Note 4 (6.0.1) on v12 works with SafetyNet for me. (Stock ROM and twrp-3.0.2-0-trltexx)
[Magisk] rignfool:
My hero!
[Magisk] metrize:
Does anyone know if resetprop can change the buildprop to original buildprop when magisk hide is enabled? doesn't seem to work for me
[Magisk] rsd2000:
SM-N910C. I will try to reinstall it.
[Magisk] Artim_96:
It's not made to change to original one, is to change the original one
[Magisk] joelh:
You can't use microG with Play Services installed. You need a ROM without Gapps. You should also be smart enough to learn how something works before flashing it to your system partition.
[Magisk] ale5000:
My flashable zip is somehow compatible (in the sense that it automagically remove the conflicting part of GApps) but obviously since there are infinite configurations I cannot handle all possible conditions; a clean ROM is always preferred.
[Magisk] Rush94:
OK thanks I will clean flash it right away
[Magisk] ariefcfa:
Hi, i have check magisk is istalled properly in my device. Magisk hide also working.

Buy, thiz app https://play.google.com/store/apps/details?id=com.telkom.mwallet keep notice rooted device although i did try to unrooted using magisk uninstaller.

I face this issue in android 7.1.2 , not happened before in android 7.1.1

Please help
[Magisk] 135Shadowsoul:
Good Morning,

i can "conform" but still not reproduce by will, magisk hide fails SN after some time!

i woke up this night, and checked, SN fails while it was OK for most time in the late afternoon/evening. so i rebooted and it was ok. ~5h later (at morning), it was again failing.

is there anything i can do to get no fails? any logs i could provide you to have a look at this?

thanks for answer

---------- Post added at 07:34 AM ---------- Previous post was at 07:15 AM ----------

Now i tested, "Substratum" + themes does not fail SN, but Adaway still, even with systemless hosts enabled. any1 any idea? did not try "Secure settings" atm...

even it is a bit off topic: does any1 know a shell command, for example executed by "Tasker" to enable/disable NFC on android 7? may need root

thanks and greetings
[Magisk] Didgeridoohan:
Are you using a custom ROM? If so, try changing ro.build.tags to release-keys rather than test-keys. That's the most usual suspect in these cases. Check the link in my signature for more possible prop values and other things that might trigger an apps root detection.
[Magisk] ariefcfa:
Thank you. Yes i use unofficial cusrom based on android 7.1.2 with lot of improvements.

The buildprop values is exactly as "dangerous props" so i changed it to

ro.build.type=user

ro.build.tags=release-keys

ro.build.flavor=xxxx-user

xxx is my device (falcon)

(Manually with root file explorer of /system/build.prop)

Still the app detected a rooted device. I think i must read and follow the tutorial carefully. I will report later. Thank you
[Magisk] Didgeridoohan:
Some apps can be hopeless... Good luck.
[Magisk] tag68:
Although I like adaway very much and it would be my preferred way if I'd want adblock while using a vpn, I don't see why to modify hosts if you can have a locally running dns server using the same lists. Especially if it makes any troubles running adaway. Did you have a look at dns66?
[Magisk] 135Shadowsoul:
yes, did, but i also noticed the notice for Android 7. As long this is not fixed this is not a realy good solution. i read, there is a workarround, but i think i will wait. but thanks for the hint. i will keep an eye on it.
[Magisk] houston_:
I reflashed gapps, because the check took endless before. Returning no result.
[Magisk] 135Shadowsoul:
idk how magisk works, maybe you have to flash magisk after flashing gapps again, too?

what i sometimes have: did you firewall/interblock magisk/SN-checkapp/playservices? this could cause problems, too :)
[Magisk] Sc4ryB3ar:
Hello, I am using an Axon 7, newest 3.1.0.0 twrp for our device, running a 7.1.1 LOS based Rom.

I used Updated-UnSu.zip by Osmosis to remove SuperSu. In this order. Wipe Dalvik & cache, flash kernel, flash UnSu, flash magisk12 (it failed, Error 1). Reboot system. Installed Magisk Manager , redownloaded magisk 12 (just to make sure I have the most recent) reboot recovery, flash kernel, flash magisk 12 again, and again it failed at the very end of the script wit error 1. What am I doing wrong? Or what can I try to make this work? I have no root now, I'm lost in a large black void ;)~