yashsingh1/xdaforums huggingface dataset:
[Magisk] :
Temporarily back to SuperSU just because I need root on multiple user profiles, and greenify, so that the battery doesn't drain quickly, but I will go back to Magisk when you guys add multi-user (To be honest, I don't even think greenify actually makes a real difference). Also, still no fix to the Netflix on the Play Store and Play Store auto-update for me.

I do not understand Samsung's new protection, which makes /data uncountable in TWRP. It forces me to install Magisk first (in TWRP, after "FORMAT DATA", reboot, then a full "WIPE" on all partitions except /System, then I install [MENTION=4899305]ashyx[/MENTION]'s "no-verity-no-encrypt" right after Magisk, and then reboot, so a clean slate of a new Android setup is started. But when going back to TWRP (even right after) and/or flashing Magisk-uninstaller (for testing purposes, like, for when it's time to migrate to a new version of either the Firmware or Magisk, also to test this Samsung security annoyance), then, /data becomes uncountable again, and I can't use TWRP without restarting the whole /data from scratch (granted, TWRP is unofficial and Beta for this device. Stock firmware and SuperSU fail to flash with it. That, and discussions with [MENTION=4899305]ashyx[/MENTION], are how I first heard of and read on Magisk, bringing me to it). All I can rely on, then (after /data is in use) is Flashfire. But SuperSU deeply embeds itself to the system, and not even osmosis's un-su seems to do the trick (not 100% anyway. Even Magisk uninstaller keeps reporting that SuperSU was found, even after the un-su script flashing). I wish I could remove it completely and be able to go back and forth between it and Magisk as I needed/wanted to.

Anyway, in short, this Samsung security puzzles me and is rendering TWRP useless to me pretty quickly. It makes it hard to retain or go back to Magisk for me, without a fresh restart of /data.

In minor news about my last hours with Android today, I uninstalled Pay, Pay Framework, Health, Health Service and Members too, today, since all but Members don't work with root. All are bloatware anyway, but hopefully you guys will figure Pay and Netflix soon, for us all. Maybe even KNOX will be figured out, that'd be awesome Thanks everyone.
[Magisk] Didgeridoohan:
Don't use Magisk built-in busybox, or go with the tip from [MENTION=4729202]jsdecker10[/MENTION]. Busybox is removed for the next version of Magisk.

Also, a tip when having issues with a mod, ROM, kernel, etc, is to see if there's any kind of faq in the release thread/OP. Known issue are sometimes listed there (yes, this is a known issue :p)

If you can play Pokemon you're partially passing SafetyNet. Some apps (like PoGo) only checks basic integrity, not the full API. It's not a false reading.... You can find some more details here:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Samsung puzzles me, period. If you want to tinker with and mod your device I would never recommend getting a Samsung.
[Magisk] Sylverfalcon:
Oh, thanks for your answer !

You mean that Xposed Systemless (even topjohnwu version) isn't compatible anymore with SafetyNet test ?

It's a bug, or it will no longer be compatible (i think it was before, right?) ?

Does this mean it's not possible to use apps like PokemonGo when Xposed is installed? :(
[Magisk] Qefx:
How does the playstore know that magisk is installed and activated? Safetynet says all is good. While the store seems to know somehow that root is on... Anyway to bypass that?

---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------

Anyway to get the apps from play store which hide with activated root? Saftynet says all good. While the play store hides them. Is there a way to show them?
[Magisk] Didgeridoohan:
I believe the mount namespace is quite critical to the process monitoring of Magisk Hide... You'll find it used in several more places in the code. The issue you were seeing is probably from here, line 86:

https://github.com/topjohnwu/Magisk/blob/master/jni/magiskhide/proc_monitor.c

That's were it's looking up the mount namespace for pid 1.

It could very well be that old kernels won't work with Hide.

---------- Post added at 09:42 ---------- Previous post was at 09:33 ----------

Considering the conversation I've had with [MENTION=8271536]TheCech12[/MENTION], what's your Linux kernel version?

---------- Post added at 09:44 ---------- Previous post was at 09:42 ----------

Clear data for the Play store, reboot, make sure SafetyNet passes, open Play store.
[Magisk] TheCech12:
Oh yeah, that is also a interesting position in the code.

I opened an issue on github. I hope there is a solution in the future. :)

Now I will wait, until something happens to the opened issue. :D

So thank you for your help. :good:
[Magisk] Didgeridoohan:
Xposed have not been compatible with SafetyNet for a very, very long time.

If you want to use an app that uses SafetyNet you'll have to disable Xposed before.

There might be some specific workarounds for Pokemon Go... Search here: https://xdaforums.com/apps/magisk/discussion-pokemon-magisk-discussion-t3465722
[Magisk] Qefx:
Thanks, but it didnt work ;(
[Magisk] Didgeridoohan:
There has been reports that it might take a while before they show up again. Wait...

I have another suspicion about this though. Could you provide some details about your device, please?
[Magisk] swa100:
sysdump command does not seem to be working. 'sysdump batterystats --reset' gives error in terminal
[Magisk] skiely666:
Don't bite my head off I know it's simple but have you tried adding the playstore to magisk hide list, clearing playstore data & rebooting?
[Magisk] Qefx:
Redmi note pro / international edition (Kate) with resurrection remix 7.1.2.

Basically hid all apps called "google something"
[Magisk] Sylverfalcon:
I haven't looked at Magisk since very long time, thank you for your answer.

Sorry, i didn't see there were a thread about that :x

Thank you again, and have a good day !
[Magisk] yakie996:
Hello I recently bought a xiaomi mi6 with ofcourse MIUI now the safetynet failed I installed the MIUI fix and still did not work than I did this fix and it worked but only until I reboot than I have to do the whole procedure again. Is this going to be fixed? Thanks
[Magisk] teddy0209:
Don't do that, don't include too many apps in magiskhide... Just keep it as is for passing safety net...
[Magisk] DroidJP:
I was about to root but SafetyNet is keeping me from rooting. As i was getting SuperSU thinking i was ready to go. I was redirected here as there is more to it than just rooting. Just shows i haven't been keeping up with the latest trends. So is rooting not worth it anymore? What gives.
[Magisk] zelendel:
If you have to aks them most likely no, not for you.

With Google new security features I am expecting things like root and custom roms to lose about 60 of normal users. As things like root just wont be worth it to them. It will be more for the tech geeks and devs that will do things like root and custom roms.
[Magisk] Dominicano2:
The room I'm using is using Linux kernel 3.10.x
[Magisk] Qefx:
Why?

Any way, I did that after it didn't work anyway.
[Magisk] Teh_Tech:
Hi all :)

Firstly, Im sorry if my problem has already been discussed, but with over 1,000 posts its a bit of a ball ache and I apologise.

Now for my problem:

I tried to install Magisk on my rooted Samsung Galaxy S5 (SM-G900F), all went well until the SafetyNet check, which failed with CTS profile mismatch, so I then went into SuperSU to unroot, after reboot I went into Magisk, and it said there wasnt root and functionality would be reduced..

Then I wiped all partitions on my phone and flashed a more recent sock rom, when I FINALLY got round to installing bits for Magisk, it wouldnt detect Boot Image Location, and detect was greyed out and the app wouldnt work at all, so then I had to root the image just to get TWRP installed so I could flash the Magisk zip, all went well but the damn thing STILL fails CTS profile...

To me it seems like I need to be rooted to get Magisk installed, but when I unroot it dont work.. also the only app that will work on my rooted phone with Magisk is the Virgin Media WiFi app, Android Pay & My EE both still report rooted device.

I was up until 4am this morning trying to recover my S5 brick to a working phone (eventually I was able to find the previous stock rom and flash that, then root, TWRP and recover the backup from 2 months ago) and I feel I have wasted my time trying everything to get this working but I dont have any luck :(

Can somebody PLEASE HELP me to get this issue sorted..

Huge thanks in advance,

Arty.
[Magisk] Didgeridoohan:
Adding to many apps/processes to the Hide list might make Hide fail (overload).

D'oh! I was hoping for an earlier version... Back to the drawing board.

To install Magisk with the Manager you need to be rooted. If you want MagiskSU, make sure you don't have systemless SuperSU and flash the Magisk zip in TWRP.

Don't post the whole log please. Attach or use pastebin.

I already gave you the answer in my troubleshooting thread.
[Magisk] noneandnonly:
As somebody mentioned on page 1002, the app called "VR-SecureGo" is not working with Magisk, even though I've turned on Hide Root and toggled it on for the app.

It's not even working for once, after booting or anything like that. I've even tried the latest Magisk v13 and it's not working.

Did anyone find a workaround or a way to get it to work or can the dev please look into this app and try to figure out how it detects root because I'm at a real loss here with this :(

Helpful answers would be much appreciated.
[Magisk] diegopirate:
Solution to my problem https://xdaforums.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609

:)
[Magisk] DroidJP:
My apologies if i was sounding discouraged. On the contrary, i don't mind. It's just that i want to use link2sd again (even paid for the plus version and i love what it does when i had my previous phone, rooted) and i use Netflix. Just curious if Netflix behaves like samsung pay. And also i started to use wells fargo wallet. So again my apologies if i came off the wrong way like that.
[Magisk] Teh_Tech:
How do I know if I have systemless SuperSU? iirc i flashed CF-Auto-Root-klte-kltexx-smg900f.tar in odin, then updated the app & binaries in the SuperSU app. I did flash Magisk12.zip in TWRP :confused:
[Magisk] :
I have a galaxy s5 g900w8 (same mods apply)

If you are looking to use magiskhide, as far as i know through reading, trial and error, it will not work on a stock rom.

I am currently use a custom rom called Grom.

The custom rom i used was pre-rooted, so i used the full cleanup option within the pre-installed supersu app.

Then flashed the magisk.zip via twrp.

I am passing SN check.

So i guess in order you would likely:

Flash twrp via odin

Install custom rom

If rooted, load into rom and remove root(supersu full cleanup should restore default boot image)

Boot to twrp and install magisk.zip

Load into rom and open magisk manager and enable magiskhide.

Reboot

Edit: I should add that at one point the other day google play store itself listed my device as uncertified. This is fixed by clearing the play store data within the app manager and rebooting.
[Magisk] sam shaikh:
You dont have to repeat the full method after every reboot, just the Terminal su permission and disable/enable thing, but yeah u have to do on every reboot.

I dont know abot the procedure fix, m not a developer. May be we can requedt any developer here. Just found the solution over net and shared here.
[Magisk] noneandnonly:
Alright, big news for the "VR-SecureGo" app!

I've been able to figure out why it's not working and what it's checking for. Turns out it's checking for the Magisk Manager apk and if that's on your system, it knows that you've got root.

As a workaround I currently have Magisk Manager uninstalled and only install it when I need to change something in the settings.

Currently we're trying to figure out a way to rename the app and see if that has an effect.

This is mostly as an information for the developer, to make him/her aware of the fact that this is something other apps do/can do.

Maybe there's a way to prevent that which could be built in but I'll leave that open to others :)

Glad I figured out a way to get it working for now.
[Magisk] Didgeridoohan:
It's possible to hide MagiskSU from some apps/processes and SafetyNet is currently one of them. It's far from foolproof though and it's most likely a losing game in the long run.

Some recommend reading for you:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

If you flash Magisk with systemless SuperSU already installed it'll use that instead of installing MagiskSU. Easiest thing is to just unroot completely before installing Magisk.
[Magisk] MrBrady:
Anyone know of a wakelock terminator Magisk module or stand alone app? Samsung Heath is out of control and I'd love to be able to limit the amount of wakelocks.
[Magisk] swa100:
Does anyone know why dumpsys command doesn't work on magisk? The following command gives an error in the terminal; dumpsys batterystats--reset

Would love to reset the battery graph when battery reaches 80% again.
[Magisk] Artim_96:
Greenify. Doesn't use Magisk but you can use Magisk to make it a system priv-app. The developer never really told what exactly that held for, but that privileged mode is somewhere between only having root and bring able to use it's XPosed plugin
[Magisk] MrBrady:
Currently using Greenify, but I'd rather use something like Amplify (Xposed module) where you can limit, but not necessarily kill the wakelocks individually. For example, I use a Gear S3 watch which tracks my activity. I don't need the Samsung Health App on my phone to also track my activity, killing my phone battery with pedometer wakelocks.
[Magisk] Artim_96:
Well, if you use Android 6 or higher it is required to obey doze, they aren't allowed to whitelist it by default

So maybe just disable the pedometer. Samsung is known for many years to have by far the worst software and especially sub-par battery life
[Magisk] vsc0705:
Magisk hide doesn't work with this log

proc_monitor: init ns=mnt:[4026531840]

I think its related with namespace something..

i'm using magisk 13 snapshot now But after magisk v9, it didn't work with my device(Xiaomi Redmi Note 4x Nougat)

It works with MM rom but not with Nougat..

Kernel version is 3.18.31

Any idea?
[Magisk] :
Problem is, Didgeridoohan, that I really love Samsung devices. I even like TouchWiz and their new GraceUX. (even though I use Nova Launcher most of the time). I don't think I'd like/love Android if it were not for Samsung. So, getting a Samsung is ok, there are always, and there will always be ways to circumvent these security systems. And for that I thank you, and [MENTION=4899305]ashyx[/MENTION], and [MENTION=4470081]topjohnwu[/MENTION], and [MENTION=631273]Chainfire[/MENTION].

As for what I talked about before on TWRP and /data moutn, it's ok, I think I just figured it out now. I just inverted flashing Magisk 1st to flashing ashy's file first (the no-encypt one) and Magisk 2nd. It seems now, no matter how many times I leave TWRP (boot into Android, turn off device, boot into TWRP) or turn the device off and then on again to recovery mode, TWRP always seems to be able to mount /data now. The instructions on the TWRP thread were to flash SU (SuperSU or Magisk) first, then the no-encrypt file. But inverting this order seems to have fixed /data mount for me, so TWRP is fixed, yay! :) I noticed both zips patch the same file, mmcblk0p10 (or something like that), so by flashing Magisk first, what was being backed up was the file with encryption. So, using Magisk-uninstaller would revert this file to the original one that makes TWRP not being able to mount /data. So, now with installing [MENTION=4899305]ashyx[/MENTION]'s file 1st, Magisk installer backs up the "no-encrypt" mmcblk0p10 file, and all is fixed, no matter how many times I install and uninstall Magisk and SuperSU, go in or out of TWRP, or turn on and off the device, /data is always mountable in TWRP.

I can use Flashfire now just to switch back and forth between Magisk and SuperSU, as I wanted/needed for now (until you guys bring in multi-user, and /data will be ok in TWRP now too, so going back and forth will be no problem) and when we get new firmware updates for the device, which haven't happened yet for this model. My former device used to get firmware updates every few months (security patch level, most of the time, nothing else). So far, nothing for the A7 2017, I guess all Sammy is gonna do is wait for the Nougat update, and then start to update more constantly after that.

Ok, I'm gonna restart the whole device now, after all this testing which I think finally worked for TWRP, so, see you later.
[Magisk] teddy0209:
MIUI is strange, been trying to figure this out myself..., and still trying... ???
[Magisk] GreyLeshy:
Magisk doesn't work with PoC!

After loading the operating system and entering the pin code for the SIM card, the phone reboots.

Is there a way to solve this problem?
[Magisk] hachiroku:
had trouble with v12.0, "magisk rooted but no root permission". tried reflashing in TWRP three times...still same issue.

uninstalled using flashable zip then went back to v11.6. no more issues.

Nexus 6P

PureNexus 7.1.1, 20170215
[Magisk] Didgeridoohan:
The tiny part you've shared of that log shows a fully functioning process monitor finding the mount namespace for something. Nothing wrong there...

Having an actual log file to look at would make things so much easier (attach it to a post or upload somewhere else, like pastebin).

And that's one of the beautiful things about Android, variation. Everyone can find something to fit their likes and needs. With some devices you just have to work a little harder for it... :p :laugh:

Great to hear you got things working.
[Magisk] CM Wave:
I'm having some issues getting Netflix to work and I'm not sure what I'm doing wrong. I have Magisk installed correctly, I'm using Magisk's root, I have the Magisk Hide and systemless hosts options enabled, and I'm passing the SafetyNet check but Netflix refuses to run, it pops up with an error saying it's not compatible with my device and closes itself.

I've also tried uninstalled and reinstalling Netflix, clearing the Play Store data, and even wiping the cache using recovery but nothing's working. I'm not sure what I'm missing.
[Magisk] swa100:
[MENTION=4667597]Didgeridoohan[/MENTION], would you have any clue why the dumpsys command in he terminal doesn't work for some people when magisk is installed? It works when rooted with SuperSU. It's an that comes across all versions of magisk and is not happening to everyone. Really clueless here.
[Magisk] bundysoat:
Hi buddies.

Thanks to developer for this app, mod of root and job, thanks a lot.

Buddies, Netflix come to hide Netflix app in Google Play store for root devices... With magisk the app app was appeared in the store again, but... Not works, the app says:

"This app not compatible with your device.... "

And link to a very very older version of the app in Netflix web.

Somebody with the same problem? I hoped it magisk solved the problem, but not understand that more happen with Netflix ecosystem.
[Magisk] Artim_96:
Magisk now uses Widevine DRM and PlayStore now let's apps exclude rooted devices. You need to add PlayStore and play services framework in Magisk hide, then it should let you download it, but then your device needs to support Widevine. Try the app DRM info which should tell you if it's supported. Go me it shows supported but nothing under the other points so maybe my ROM hasn't added it so the app also links me to their website. Maybe it's because of Widevine or maybe I just would need to add it to Magisk hide, I'm not sure.

Just try around and report back. And maybe make a catlog from starting Netflix. Maybe that shows what's going on.
[Magisk] bundysoat:
Sorry buddy, What is Widevine? Then I put Play store and play services Magisk Hide and try now.
[Magisk] tom0769:
I just switched from SuperSu to magisk. So far all root demanding apps work well. The only let's say issue is, that satetynet check dors not end, neither successful nor failed. I'm sure, I'm missing something.

Adb is turned off.

Magisk hide is activated.
[Magisk] Artim_96:
A DRM system made by Google. It's also built in to (desktop) chrome.

---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------

That means that the play services are crashing. Maybe delete its data and reboot, otherwise try to reinstall
[Magisk] tom0769:
Deleted data from playservices and reinstalled magisk but still the same, safetynet check does not end. Could not find any hint of crashing playservices.

Actually using slim rom with open gapps
[Magisk] teddy0209:
Does your device appeared as certified in Playstore? If it's not, try clearing its data...
[Magisk] TakeiHisa:
UPDATE

after I clear supersu,flash uninstall magisk.zip,reflash ROM,flash magisk. this problem has disappeared.

maybe reason is uninstall magisk step?

before these,I have flashed/upgraded magisk and stock ROM several times from magisk v11, and the problem appeared at March.2017 after Shadowvese new version release.

no idea what's going on,I've used android studio and adb saved logcat copies on Shadowvese working status,now I cant reproduce it.. sorry

---------

I have a strange question about shadowverse,

world ver

play.google.com/store/apps/details?id=com.cygames.Shadowverse

japan ver

play.google.com/store/apps/details?id=jp.co.cygames.Shadowverse

after this game upgrade on March, this game changed file structure,and when I used magiskSU for root,

the game will black splash screen and quit without any hint, even I hided with magisk hide.

But I used Chainfire's SuperSU without any hide,this game works fine.

i've no idea what's wrong with these,looks like this game has none root detecte,but when I flashed magiskSU ,the game will immediately crashed.

The magisk hide is works perfect with all apps which has root detecte in my phone.

I'm using oneplus 3T,OxygenOS 4.1.3 (7.1.1), and I think it maybe not necessary to upload my magiskmanager log,if it necessary I will reflash magiskSU and provide it.
[Magisk] DodoGTA:
Please give me a logcat: https://xdaforums.com/showthread.php?t=1726238
[Magisk] swa100:
Just tried flashing SuperSU again and the command instantly works. Going back to magisk instantly causes dumpsys command to result in unknown error.
[Magisk] CM Wave:
Anyone? I'm really at a loss about what I'm doing wrong.
[Magisk] Dylan Hameleers:
Well... it doesnt work for 2 minutes after boot up... so its quite useless compared to SuperSU... :/ fix that please
[Magisk] dahawthorne:
Then I recommend that you stick to SuperSU. Why exactly are you here...?
[Magisk] Dylan Hameleers:
The modules are cool and magisk allowed me to use snapchat and some other apps that look for root... its somewhat safer
[Magisk] teddy0209:
I don't really get what you mean by that 2 minutes... As compared to supersu, this is open source, we can build, we can fork, we can contribute... Plus we get to enjoy apps that normally doesn't work with rooted phones and mod our systems easily without messing with it... ???
[Magisk] Dylan Hameleers:
You are right by that... but what i mean is that i have some apps that run on boot (like kernel adiuter mod) that cant work cuz of those 2 minutes... its not the end of the world, but it is annoying ??
[Magisk] :
I agree completely, gotta love Android. ;)

I was finally able to remove SuperSU too, through more testing. For some reason, restoring the boot.img with Flashfire restarted the whole thing (data was formatted, even though I didn't wipe it nor added it to Flashfire's queue). Restoring boot.img with TWRP does the trick. So I can finallly master my new A7 '17, just like I did the J7 when I had it. So now I can go back and forth between SU and Magisk, no problem.

Thanks again, Didger.
[Magisk] teddy0209:
I have kernel Adiutor on both my phones... What exactly doesn't work?