yashsingh1/xdaforums huggingface dataset:
[Magisk] DrSeussFreak:
It's being looked into, progress isn't what we would all like, but speaking as someone who can't contribute to the coding process, all I can do is wait patiently and thank those people who are working on the resolution.

Like you, I do not root for pogo, rather I have a call blocker, etc, but nothing to cheat with, so the fact Niantic has a problem with my use case drives me nuts.
[Magisk] osm0sis:
Still working fine for me here.. Restarted the game through the usual 3-4 FCs, then just caught a Pidgey. No idea what's up with your devices.. as I said, you're the only one who's reported any kind of issue with catching.
[Magisk] Karls0:
Maybe I'm the one who writes so detailed. Most reports looks like "It's not working, do something".
[Magisk] osm0sis:
Haha perhaps.. but the fact is that mine still works for catching, and those people who have reported in detail have reported a similar experience to mine. I guess we'll have to wait and see if whatever MagiskHide fix comes down the pipes resolves your issue as well.
[Magisk] manthes:
For me just once today i had the message for incompatible device while i am trying to catch pokemon.
[Magisk] Petikas:
Just to add my experience. Once the game starts and as long as I don't switch to another task it's working fine. As soon as i switch to a call, or to an incoming message or if the phone locks then as soon as i return to PoGo it crashes giving the incompatible device message. After 2-3 tries it starts up again normally and works until the next time i switch away from it.

Applications that draw over the screen such as facebook messenger and pokegenie overlay work without triggering the crash.
[Magisk] Karls0:
I would agree with you, but I tested on second phone and don't see a big difference. It is very unlikely that on two independent phones, have similar conflict. The only thing that this two phones has in common with, is the same Magisk v.16 stable..
[Magisk] Lobster$:
+1
[Magisk] fOmey:
I'm curious.. do you think Niantic have purposely manufactured this crash to combat root user's ? Or the crash is just a by product of the technique they are using to detect root.. or perhaps it's not related to either one and would be considered a bug ?

Honestly it seems really crude and I have my doubts it was done on purpose... if anything I would have guessed they would use their generic "device not compatible" screen.

In my experience the crash occurs when the view is reinitialized/resumed.. Samsung's implementation of multitasking is kinda sucky and freezes/pauses any processes that are not in the foreground even if your using "multi window"...

Very odd.. not sure what to think of it.
[Magisk] jcmm11:
[MENTION=1620550]fOmey[/MENTION]

Yes. Before removing Magisk run, from either a terminal emulator or from the terminal in TWRP

cp -lf /data/adb/magisk.* /data/media/

this will create a copy, via hard link, of both magisk.db (contains apps granted root privileges) and magisk.img (containing all your modules etc).

Since it's a hard link you can create this at any time and any changes you make will automatically be kept in both locations (it's actually only 1 file but linked from 2 directories). If you delete either file you only delete the link so the other location is still there.

After removing Magisk the files in /data/adb will be gone. The ones in /data/media will still be there. These will even survive a data wipe (not format) in TWRP. Once you restore Magisk, and booted the system again (so Magisk recreates the files in /data/adb) you can restore these files by running

cp -lf /data/media/magisk.* /data/adb/

I suggest rebooting into TWRP to do that. If you do it from a terminal emulator just make sure you reboot immediately afterwards.

EDIT: you should be able to use "ln -f" in place of "cp -lf", although I haven't tried this variation.
[Magisk] fOmey:
Adb works in TWRP also, if you don't want to use that horrible onscreen keyboard. Nothing worse then typing in terminal commands with a onscreen keyboard..
[Magisk] EViollet:
Hi.

For what it's worth, I managed to stabilize Pogo when switching apps. I no longer have any crashes when switching from one app to another. Your mileage may vary.

I achieved this by using the "app ops" app forbidding Pogo from running in the background.

I still have crashes upon startup, but this seems to be a totally different issue, probably linked to timing issues as previously mentioned.

I hope this helps.

Regards
[Magisk] osm0sis:
I just think their root check now occurs earlier in the startup, and now occurs any time the app is switched back to during multi-tasking where it didn't before. Apparently they switched some classes around and that likely introduced the crashes in conjunction with root checking. Obviously their intent would be for it not to crash and it to display the incompatible message every time.
[Magisk] teddy0209:
It's still playable here for me. Random crashes at startup, but it loads most of the time and when it does, no problems at all during play...
[Magisk] DrSeussFreak:
I occasionally get the incompatible error while trying to catch a pokemon, but usually only if it is the first thing I try to do. I have played all day today without any issues, so long as I don't switch apps
[Magisk] 420SYN:
Same problem here with Magisk + Pixel 2 XL. As soon as I click on a Pokemon I get device not compatible crap. Uninstalled magisk and it works again.
[Magisk] osm0sis:
I still have a strong hunch it has to do with what root apps and/or Magisk modules you 2 guys are using. I got through all of Community Day today without any issues catching anything.
[Magisk] 420SYN:
Wasn't running any, fresh install of both os and magisk. Besides all I use to for us to block ads and get ad free YouTube so I can live without for now. Ads suck though
[Magisk] osm0sis:
Weird. I'm out of ideas then. I have AdAway and a few other utilities mostly (aLogcat ROOT, BBS, FX, FKU, Terminal Emulator and TiBU) and for modules I've got my ADB, AIK, Busybox, Flashlt, Nano, and the Google Dialer, Lens and Pixel 2 Launcher ones as well.

As I've said before, I used to use PokeBatterySaver, but found it requesting root at the same time the game was loading led to more frequent crashes and incompatible messages, so I disabled it and it's been liveable beyond hitting "Open app again" a few times until the MagiskHide timing lines up right.
[Magisk] Lef1337:
for me crashes in every different way black screen and app restart stop work message and the compatibility message i tried remove the magisk clear dalvik cache but still crash i get the crash when multitasking galaxy note 3
[Magisk] inggaro:
I tried this but no changes for me. Did you just set those 2 options? Tnx
[Magisk] EViollet:
Yes, I tried several other things but didn't notice any improvement. Those 2 options are the only ones that seem to have really changed something.

From time to time, I still get FCs when switching apps, but, much less than before. And, to me, it's once again linked to Magisk not hiding quickly enough.
[Magisk] euclanville:
I don't think magisk only is targeted my setup is normal root system. Then I installed xposed then killed it root switch. Then I uninstalled root with su app settings "Full unroot" and viola i have some xposed module working while passing safetynet. Although i have constantly su force closed message but it will gone after 2-3 popped up. But even with this I have still problem with pokemon go crashed and incompatible similar to that with magisk. Because I have my samsung with magisk and my lenovo with this kind of setup
[Magisk] Dineshfika:
Pokemon Go 0.95.3 without magisk

I made my own working Root toggle with ES File Manager (switching root and SafetyNet Passed without using Magisk). Lets wait for sometime Magisk update untill that i will use my own method.

Requirements and Info:-

1. Fresh ROM with SafetyNet Passed and without Magisk root hide. Like Stock ROM, CM ROM, LOS ROM (LineageOS).

2. Any Root Material except Magisk. Like SuperSu, CM-root, etc.

3. TWRP Recovery Mode. (If already skip or not than don't do it before known fully).

4. Some knowledge about System Partiton before doing process.

5. To hide Superuser icon from notification bar, need terminal (local or download from play store or from anywhere) with some knowledge, how to give commands in terminal like small thing.

APK Required:-

1. EX File Manager

2. SafetyNet Helper (or another apk to check status of SafetyNet). You can use magisk apk also to check SafetyNet status.

3. Pokemon Go version 0.95.3.

4. Root Checker Apk (any) to check root everytime in each steps.
[Magisk] Dineshfika:
Ok, i made only small root toggle which ON/off root without rebooting and its Pass SafrtyNet and play pokemon go v0.95.3. Easy to understand all steps. But made only for me, i don't known others would like this or not, so i request to all before doing that don't blame me for any fake info, or something report.

My bad and sorry my English is little weak (only in written and talk :eek:).
[Magisk] oTeMpLo:
Ok.. just tell us what to do..

I hate having unrooted phone for more than a 14 days already :)

Soo.. we or at least i are waiting nervously.
[Magisk] xanthrax:
ohh guys ... let`s stop playing Nostradamus shall we ? I there is something which you think it violates our Forum Rules just report , otherwise ... but you know that already

I`m pretty sure that [MENTION=8980557]Dineshfika[/MENTION] will eventually share and properly explain in detail his workaround if he wants to

I have cleaned the thread a bit

Thanks for understanding

Dan - forum moderator
[Magisk] euclanville:
Anybody has issues with crashed or incompatible even the magisk is uninstalled? But I do have my xposed inactive due to rootswitch disabled. I Passed the safetynet now but still crashing on me. I reboot many times after the magisk uninstalled but still same issues. I will try tomorrow if uninstalled xposed will complete solve the issue. Niantic is getting smarter than safetynet the next API update will be terrifying to rooted users?
[Magisk] osm0sis:
topjohnwu mentioned it crashes even unrooted on Pixel with Android P DP. Pokemon GO is pretty buggy software; they're not getting smarter, we just exposed a bug. :p
[Magisk] rawika:
I was able to fix the issue with the "hardware software/incompatble" message of pokemon go by clearing all the data from playstore and doing an update to latest playstore version by tapping the version number which you can find inside the playstore settings.

I figured this out because my google playstore showed that my device is not certified which I was able to fix by clearing the playstore cache and data. So I think the playstore update is not necessary?

Maybe the problem is a missmatch between the uncertified device message in google playstore while still passing safety net?
[Magisk] Alucard:
So is there going to be a way to play pogo with root,if niantic doesnt want spoofing they must find another way not just ban root damn,ive been rooting since lg p970.
[Magisk] fOmey:
Can someone with magisk installed please do me a favour, disable root in magisk settings.. disable magisk hide and let me know if you pass safetynet ?

If you are indeed passing safetynet with root + magisk hide disabled.. launch pokemon go and see if you still crash.

The less module's installed the better.
[Magisk] Dineshfika:
Same thinks me bro and discuss same topic with my friend about Niandic freaking ban tricks.

---------- Post added at 12:18 AM ---------- Previous post was at 12:16 AM ----------

Can u tell me your rom and all in deep detail? You mean after uninstalled magisk your SafetyNet CTS failed! ?

---------- Post added at 12:21 AM ---------- Previous post was at 12:18 AM ----------

Thats mean Pogo able to detect some root cache or any files in system. I will suggest u to try one app. Wait i will give the app download link. Its also available on play store.
[Magisk] fOmey:
I don't have magisk installed at the moment and I'm at work so I can't test what I posted above.

I'm just curious if pokemon go will still indeed crash with root + magiskhide disabled.. might provide some more insight and allow us to narrow down what is causing the crashes.
[Magisk] Dineshfika:
That is bcoz Pokemon Go new patch were not ready yet for Android P. Pokemon Go 0.95.3 crashing and incompatible device only in rooted device. Try once to play on stock ROM. Game play very smoothly.

---------- Post added at 12:27 AM ---------- Previous post was at 12:24 AM ----------

Hmm interesting... But my play store was show me certified in RR N rom with magisk. There is only magisk reason of pogo app crashing and incompatible device. By after doing 3-4 days research.
[Magisk] kevinm2738:
For what it is worth, whatever is causing the crash started with version 0.93.4. I installed the update to hopefully fix a few bugs that I was experiencing and this is when the crash started. I didn't get the issue when trying to click on a pokemon though, I usually got the issue when connecting to a peripheral device. (Bluetooth, charger, headphones, etc.)

It was working fine with Magisk 16.0 and 0.93.1 and below. I tried another custom ROM without rooting the phone, but then I couldn't login to POGO. Turns out, depending on your device, they can see even when you've unlocked your bootloader.
[Magisk] Stban0626:
I don't think that POGO can see if your bootloader is unlocked or not. Maybe the problem is the rom you tried, because many roms nowadays don't pass safetynet even after a clean install. In many threads devs says that the way to go to fix "the safetynet problem" is flashing magisk. So if you wanna play POGO or use Snapchat or any app with safetynet restriction you are forced to use magisk
[Magisk] hamonmaru:
Yes...

I just uninstall magisk and pogo is playable without any issue

Eventhough after magisk unistalled safetynet check only pass basic integrity.
[Magisk] osm0sis:
A wild Magisk Manager release appears and will fix this issue once you add Pokemon GO to the MagiskHide list again. Stay tuned! ;)
[Magisk] euclanville:
Confirm still crashing on me when switching only between app. "But if i remain on POGO window stable". I did disable root via settings from "app + ADB" to "Disabled".

My setup: Galaxy s7, Android 6.0.1, Xposed disabled through rootswitch, Safetynet passed, - Still getting FC, I dont have issues on my REdmi note 4 without root and the bootloader is untouched.
[Magisk] Silkeyway:
Teasing us hard there, even with a wink smiley and all ... give us some more ?
[Magisk] oTeMpLo:
No.. wont pass.
[Magisk] dfs_:
tons of golden raspberries are thrown at you to make sure that this fix has no chance to flee!
[Magisk] oTeMpLo:
:confused:

Are you waiting for new Unofficial build.. with changes from that weekend ?

https://github.com/kantjer/MagiskFiles ?
[Magisk] DrKillerZA:
I was wondering if you can give me some advice. I clicked your link to check the versions and then it spawned a (wild) question.

I installed Magisk last night. I have Version 16.0 (of something), and 5.6.3 of Magisk Manager.

When this update comes out, what do I need to do to update? Go download the new version manually and go into recovery to install? Or will this manager take care of everything?
[Magisk] Karls0:
But PoGO is added by default and you can't switch it. Will it be changed in next update?
[Magisk] mjemec:
Can you give us an ETA on the update?
[Magisk] Karls0:
Please don't ask for ETA, it is impolite.
[Magisk] DrKillerZA:
Can we ask advice on how to update it? ;)

(Check my previous post a few posts up)
[Magisk] Karls0:
Do you want to test this MagiskManager unofficjal build (2h old)?

https://github.com/kantjer/MagiskFiles/blob/master/MagiskManager-v5.6.3-180327.apk just press download on the top, and install apk manually.
[Magisk] Nataku90:
I activated magisk-hide for all apps on my phone except titaniumbackup and greenify (the only two root apps i use - no spoofing) - is that allright for the upcoming update or should i set it back to default (so deactivate all magisk-hide and keep it only active for pokemongo).
[Magisk] mjemec:
Testing...

Crashing less often on first boot and can switch apps sometimes. But after a while it crashes on switch or shows "device incompatible" warning (especially when locking and unlocking phone) in PoGO.
[Magisk] Karls0:
So we can say that almost nothing changed? I hope it is not this update and we will see correct version soon.
[Magisk] mjemec:
We shall see. A new update for PoGO is expected this week to enable upcoming quests. Maybe that version will not be as buggy.
[Magisk] SebaS-DG:
Same results here, not bad at all.

---------- Post added at 10:55 AM ---------- Previous post was at 10:47 AM ----------

I think the opposite, 93.4 and 95.3 was the same "buggy" thing, while they read it make root users cry, I think they will not change anything about this because is what they always wanted...
[Magisk] nemesishaven:
Yes, exactly. "Less buggy" in this context means it handles root detection/errors more smoothly, which would just mean we'd always get the "This device is unsupported" message instead of getting crashes.
[Magisk] Karls0:
Yes, I think that PoGO update will not help us, we need to wait for Magisk update. If PoGO can bypass MagiskHide, other apps would soon do the same.
[Magisk] Didgeridoohan:
The issue is most likely just that PoGo for the moment isn't in itself added to the Hide list (not allowed by design). So far it has solely relied on SafetyNet, but that seems to have changed somewhat. Being able to add it to the Hide list in a future release of the Manager should take care of everything. Simple...
[Magisk] osm0sis:
After you add Pokemon GO to the MagiskHide list again, you still need to stop using any root apps at those times (startup/switching) because they of course complicate the hide process. Once I did that (PokeBatterySaver was my only offender) I haven't had a single FC or incompatible notice. :good:

Next Magisk zip release will likely improve that a bit further.
[Magisk] oTeMpLo:
Which phone? Maybe your phone is slow enough...? ;)
[Magisk] osm0sis:
Yeah, my OP5T is reaaaallly sluggish. :p
[Magisk] oTeMpLo:
:) my 3t crashes like hell... :)
[Magisk] SebaS-DG:
I dont understand, what we need to do with this "update", I just flashed it, and installed the new apk (180327).

Anything else I need to do?
[Magisk] osm0sis:
Go into MagiskHide and add Pokemon GO to the list again. It was previously grayed out because it was known to use only SafetyNet, but now it seems to help to hide root from the entire app, so topjohnwu unlocked it and you need to add it.
[Magisk] SebaS-DG:
Mmmm, I did something wrong then, pokemon go is grayed and "managed by default" by magisk.

I will uninstall it a re install.

Edit: Im missing something, still grayed by default.
[Magisk] mjemec:
I wasn't switching between root apps when I experienced crashing. I went from PoGO to FB Messenger to Viber and back to PoGO. Sometimes it's enough to lock the screen with the app in foreground and it crashes on unlock or it gives "OS not compatible error".
[Magisk] Didgeridoohan:
I don't think the code to add PoGo to the Hide list is on GitHub yet, so the feature won't be in the unofficial snapshot.
[Magisk] DrSeussFreak:
Anyone else get "App not installed"?

::Edit:

I had to uninstall the existing magisk manager (just the app, not root) and then it worked, but PoGo is greyed out...
[Magisk] osm0sis:
Ah sh*t, well that explains it. Sorry all, soon enough.
[Magisk] Karls0:
So we have to wait :). Let's hope it will be released until new quest system in PoGO is out.
[Magisk] SebaS-DG:
Just unistalled magisk, and most of root advantajes for fly gps, and disable location services, are working for me without make pokemon go crash or something. Island and double pokemon go window is working too!

Im happy now.

Edit: tested in my lg g3, and xiaomi redmi note 3 SE.
[Magisk] Soakil:
Don't

Disabling the location service will trigger the red warning, don't do it!
[Magisk] SebaS-DG:
Using it since 2017, no red warning, no shadow ban.

And I have 4 accounts.
[Magisk] Soakil:
When I use it with legit gameplay I had no problem for month, but recently my local groups stopped to play and I made 100% spoofing, and got 2 red warnings, I disabled it after the second warning an play the same way but no more red warning. (had to patch services.jar for the mocks)
[Magisk] -Happy Feet-:
With Magisk Pogo works fine for me on my Pixel with android 8.1.0
[Magisk] fOmey:
Anyone who would like to test adding pokemon go to magiskhide early.. you can do this without a updated manager.

This seems to have fixed the crashing for me.

Open a terminal emulator and punch in the following:

su magiskhide --add com.nianticlabs.pokemongo

EDIT: Some users reporting issues with the one line, if this includes you try the following:

su
magiskhide --add com.nianticlabs.pokemongo
[Magisk] inggaro:
Thank you so much, it's working!!! :good::good::good:
[Magisk] Silkeyway:
Working indeed! Awesome!

Now why on earth is this necessary, and why does a greyed-out check mark in Magisk Manager mean "force disabled"? I always thought these mean the exact opposite...

Also, is this persistent?
[Magisk] fOmey:
I don't completely understand why pokemon go was disabled from the list in the first place tho, I was under the impression it was automatically enabled in magiskhide.. which is why it was disabled in the list. Not exempt from it?!

Anyone know the reasoning behind this ? Or was the logic somewhere along the lines of XYZ uses safetynet to determine root, therefore magisk hide is not nessisary ? I honestly think it should be the opposite of this, XYZ uses safetynet therefore we should automatically add to magiskhide to prevent a potential future issue. Everything is obvious in hindsight tho right..

You beat me to it!

Yes, it is persistent.
[Magisk] xGarro:
I can't believe the solution was so simple. In the meanwhile I was using Proximity Service to avoid having to leave Pokemon Go.

Tested and working. I wonder what was Magisk doing to prevent Pokemon Go to pass up until recently that wasn't MagiskHide (As AFAIK it's MagiskHide what makes SafetyNet pass).
[Magisk] manthes:
I paste the command but it gave me an error. Unrecognized option --add.

Which versions are you using? I have magisk manager 5.6.3
[Magisk] mjemec:
I get the following error:

OnePlus3T:/ $ su magiskhide --add com.nianticlabs.pokemongo
magisk_daemon: unrecognized option `--add'

MagiskSU v16.2 (180327)(180327)

Usage: su [options] [-] [user [argument...]]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment preserve the entire environment
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
-mm, -M,
--mount-master run in the global mount namespace,
use if you need to publicly apply mounts
2|OnePlus3T:/ $
[Magisk] fOmey:
Running latest version of magisk.
[Magisk] manthes:
It is not 5.6.3 the latest?
[Magisk] Seagorilla2:
First type 'su' + enter

Then the rest + enter
[Magisk] kos4all:
Remove su from the code line and it works
[Magisk] Soakil:
:/

I can add it in the list, confirmed with --ls switch but it's still grayed in the GUI and the game still crash
[Magisk] mjemec:
Thanks!
[Magisk] Stban0626:
It works perfectly, thanks for the solution. I can't believe it is so easy to fix.
[Magisk] dfs_:
works great with the magiskhide adding, anyone managed to have xposed in the setup too?
[Magisk] DrSeussFreak:
I'm getting

sh: magiskhide: not found

Edit:

Termux didn't like it, installed a different terminal emulator and I'm set
[Magisk] Bcl2:
Do you mean that I've spent half of the day flashing roms on my old phone in the hope of passing safetynet, and the solution was simply a line in terminal emulator? F**K

Oh by the way, it's working :D
[Magisk] Lef1337:
where i need to type the command at recovery terminal command ? need to go in specific folder or?
[Magisk] 420SYN:
I'm pumped to try this. I miss root
[Magisk] iamelton:
thx a lot! it works very well..