yashsingh1/xdaforums huggingface dataset:
[Magisk] bleetx:
For me it was Magisk causing the crashes it seems. I unrooted my Redmi Note 4 and made fake gps a system app through TWRP and looks like everything working fine, even when i switch app in background. Without Magisk my SafetyNetTest fails, but for some reason i still can login on my Pokémon Go accounts... I'll take it i guess
[Magisk] jan.skurski:
For me it is:

setup: Galaxy S6, some light 7.0.1 Android with root (Magisk).

I can get to app (and "play infinitely in the foreground") without problems nearly always (some crashes can occur at boot time, but in 2-3 tries it always lets me in). So tricks with TitaniumBackup are not necessary in my case.

I would happily uninstall Magisk if it would help, but uninstalling via TWRP causes "bootlop to recovery" every time, and uninstalling Magisk via
[Magisk] justj0sh:
I would greatly appreciate someone figuring out why uninstalling magisk creates a bootloop
[Magisk] jan.skurski:
So it's the same for you?

I tried to search for that issue (bootloop), but ended with nothing,
[Magisk] Telperion:
As a former Ingress player, it's trivial for Nia to detect spoofing, but for whatever reason they don't. Compare logged raw NMEA data from a real GPS stream with a spoofed one. There are obvious patterns.

The Ingress community long ago concluded that Nia ultimately doesn't care, they care to the extent that it hits them financially. Spoofing artificially inflates their usage and engagement numbers, which is all they truly care about -- their corporate partnerships.

All that to say, everyone should have the mindset that if Nia wants to detect things like spoofing and reversed API use, they could at any time and may already do so. They turn a blind eye to some things for unknown reasons.
[Magisk] fOmey:
Anyone who is boot looping uninstalling magisk, it's probably because your on a stock rom.. download & flash the latest version of no-verity in recovery straight after you restore your stock boot.img... you can do this straight after either flashing your boot.img in twrp or running the magisk uninstaller.
[Magisk] twinko:
Found this post and it helped:

Just flash

magisk 16.1 beta

*edit:

moreover going back to core mode in magisk helps aswell
[Magisk] hamonmaru:
Just put as above but the game still force close.

My phone with rr nougat though they have oreo above.

Are there any difference?

Anyone test?
[Magisk] tim_pear:
SafetyNet failed but not tripping PoGO

Hi!

I just want to check in to figure out how safe my configuration on an old phone is until I get my primary device back from service. I have two systemless devices, one on stock Marshmallow (Xperia M4 Aqua) the other on AOSP Nougat (Xperia Z1). The first one is passing both SafetyNet checks just fine, but the other one is failing the CTS profile check (probably due to the Linux kernel, tried enforcing but didn't help). Anyway, I am not looking to fix it, as I can play PoGO just fine on both. I just wonder how safe it is to do it on the one with a CTS Profile mismatch. Thanks in advance!
[Magisk] Didgeridoohan:
As far as I know, PoGo only checks basic integrity. Shouldn't be any worries... If you want to fix the CTS failure, try this:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-simple-t3765199
[Magisk] Haxorleet:
True but i meant the "OS not compatible" message that can occur during gameplay without warning.
[Magisk] DrSeussFreak:
[MENTION=4667597]Didgeridoohan[/MENTION] is there any works being done to find a fix for the issues we are seeing with Magisk and PoGo? I uninstalled Magisk, and my issues went away, reinstalled and they came back, so I am not running free of root. I know all PoGo discussions are shunted to this thread to keep the main thread clear, but I haven't seen any comments on a fix in the works, etc. Just wondering if you knew if anything was going to happen?
[Magisk] Didgeridoohan:
The work being done is going on right here in this thread... [MENTION=4470081]topjohnwu[/MENTION] is quite busy with his military duty. If you all can figure this out and pinpoint what's going on, there's a possibility of a fix.

Some posts seem to suggest that there's some background process running that can detect root. Could be that when moving from having PoGo in the foreground (MagiskHide active), to the background (MagiskHide not active, background process sees Magisk), and then back to the foreground again, it triggers. DISCLAIMER: This is a highly speculative theory by me and me only. I'm very likely to be completely wrong.
[Magisk] DrSeussFreak:
Any thoughts on what we can do to help find the issue? I think it is safe to say that removing Magisk resolves the issue, so we can say with some certainty that Magisk is the culprit.

Using a PoGo+ also seems to make the situation worse, so not sure what process(es) are added outside of leveraging my phones Bluetooth connection. Do we need more logcats, what would help?
[Magisk] Telperion:
Just because the existence of Magisk trips the detection, doesn't mean Magisk can fix it. Nobody knows what specifically Niantic is detecting, just that it appears to be related to app switching.
[Magisk] DrSeussFreak:
If you completely remove Magisk though, I and did this, and ran it for 15 hours, the issue went away completely. Immediately after installing Magisk, with no modules or any other root apps, the issue comes back, and yes, it happens if I run it in the background or switch, not if I keep it in the open. It seems like Magisk is the cause, but I understand that without know what is PoGo is detecting, Magisk may not be able to be patched to fix it.
[Magisk] aNGERY:
it's pretty alarming to me that Niantic can shut down Magisk for Pokemon, but Google can't shut down Magisk for Android Pay, etc.
[Magisk] osm0sis:
Guys, this thread is going in circles.

It's important to recognize that it's not just Magisk + MagiskHide, it's also SuperSU and suhide-lite (and even old-school, badass suhide). I know this is a "Magisk thread", but it's useful to determine whether similar methods of hiding also do not work, because it's not that "Magisk is the cause", it's that any root hiding ability is now exposing some nasty bugs in Pokemon GO's updated detection code.

It's also important to remember that it still works. You keep restarting the game after the "incompatible" screen or pressing "Open app again" after the FCs and eventually it'll work. This pretty much proves it's only a timing issue with the root hiding methods vs. the root detection methods, and certainly would be resolved by speeding up the root hiding, though [MENTION=3694505]Telperion[/MENTION]'s playing with Pokemon GO's services is also a useful avenue to explore.
[Magisk] DrSeussFreak:
So what would you recommend we do to help? I am more than happy to dedicate my time to give developers any data they may need.
[Magisk] osm0sis:
If you can code and compile APKs then Magisk and MagiskHide are open source and you can experiment, otherwise it's likely a waiting game for [MENTION=4470081]topjohnwu[/MENTION] to have time to tinker with it and attempt to make it faster to hide. As I said, [MENTION=3694505]Telperion[/MENTION]'s efforts with Pokemon GO's services could also help with a workaround for the time being.

In the mean time either downgrade to the last working Pokemon GO version (0.91.2 I think), or just deal with restarting the app multiple times until the timing lines up for the root hiding to pass the detections. Running root apps at the same time as Pokemon GO's startup does make the timing lining up harder currently, e.g. I had been using [MENTION=3292224]franciscofranco[/MENTION]'s PokeBatterySaver and disabling it improved the chances of passing significantly.
[Magisk] DrSeussFreak:
I haven't coded in 10 years, not sure I can add value there. If any testing/feedback is needed, I would be happy to help.
[Magisk] SebaS-DG:
Magisk COre only, do nothing, pokemon go keep crashing, device no compatible, and logs you out sometimes.

Magisk 16.2 is the same.
[Magisk] justj0sh:
There is no latest version that works. 0.95.3 was forced earlier.
[Magisk] soraxd:
so when you guys say uninstall Magisk, do you mean uninstall the Magisk Manager app, or uninstall the whole Magisk framework from your rom?

Would apps that already have root privilege be able to retain it? if no, would converting all of them to system apps solve that?
[Magisk] osm0sis:
I don't say that. I say keep restarting the game until it passes, because it will, and wait for a MagiskHide update to hopefully improve the hide speed which will fix it.
[Magisk] DrSeussFreak:
If you convert using Titanium, you can do it, but any app converted via Magisk modules will be reverted. You do lose root when you remove magisk (and I am referring to complete uninstall)
[Magisk] soraxd:
thanks is is exactly what I was looking for.

I'm curious, has anyone experimented with just uninstalling Magisk Manager and seeing if pkgo behaves any better?
[Magisk] Telperion:
Perhaps alter this and build to test:

Not being topjohnwu I can't speak to what would be the best places to speed up the rate at which MagiskHide works, but that doesn't look like a bad place to start. I imagine that it may be rather resource-intensive so a faster polling rate wouldn't be well-suited to general use. Perhaps a future build can provide a user-facing setting if altering it proves to be useful?
[Magisk] Haxorleet:
I have an idea... but I don't know how to do it.

Hello,

I was thinking about an idea how to fix this Pokemon crash issue.

I don't know if it's possible but, if it's possible It might solve our problems.

However, it requires to remove root, with some previous benefits of having a rooted device.

1) Install TWRP + Root your device with Magisk.

2) Install any app remover to remove all the bloatwares and useless features from your device.

3) Move your flygps app from local to system app.

4) Remove Magisk and root and TWRP by flashing back the minimum necessary to have your device booting and running. (i don't know, maybe boot.img and recover.img that you previously extracted from the stock rom?

5) Enjoy Pokemon GO without crash with flygps running as system app.

What do you think?

Anyone up to the challenge to make it work?

I tried this by flashing boot.img and recovery.img with an app called flashify after fully uninstall Magisk but my phone is stuck at the flashing samsung logo.

I have access to the original android recovery though... but the OS is not launching.

Something I miss?

Thanks if any specialist may help.

Best Regards.

ONE LAST THING BUT IT REQUIRES SOMEONE ELSE'S CONFIRMATION:

I have noticed that if you install Pokemon GO on your unrooted device, launch it, it works perfectly (obviously) THEN after it acquires all the necessary data, you can root your device, the game will still work properly as long as you don't clean the app data from the system app list.

It also works the other way around: I root my phone, launch successfully the game, then, unroot my phone by flashing the rom with odin, phone getting unroot, the game won't launch like it still thinks the phone is rooted...

Clear up all the app data + cache, everything goes back to normal.
[Magisk] twinko:
Bro, i didnt rooted because of cheating at pokemon. This is no solution. We all need to wait until [MENTION=4470081]topjohnwu[/MENTION] is fixing the problem. If you use root only for spoofing, just unroot and get your lazy ass movn.
[Magisk] Sippi4x4man:
Yea me too. That was an awful lot of work just for one game to work.
[Magisk] royaLred:
on my iphone with Pokemon Go++ all **** works.
[Magisk] 309041291a:
I thought te purpose of SuHide and all of this was to stop this...?
[Magisk] Sippi4x4man:
Safetynet was updated by Google at 1030am and SuHide no longer works.....
[Magisk] bezeek:
My V10 is giving me the same sort of run-around with SuperSU. I just finished my third head-scratching attempt. :silly:

I rolled back to a clean boot partition, flashed the Magisk uninstaller, and rebooted; then installed Magisk v7, rebooted, and installed SuperSU V2.78 SR1 in systemless mode.

Magisk Manager complains about lack of root and crashes, I can't find a su binary anywhere, SuperSU claims to be installed in systemless mode but also claims I need to update the binary (which fails because it can't get root to run its commands), and SafetyNet checks fail anyway.

Maybe the fourth time's the charm... :cool:

Or maybe I'll just go back to what works for now. :rolleyes:
[Magisk] Sippi4x4man:
That's the same problem that I had over and over. Once I typed in that command in TWRP and then flashed Supersu it worked fine.
[Magisk] ghenxx:
What's the backup plan to play games, uninstalling superuser and flashing the magisk uninstaller?
[Magisk] Sippi4x4man:
Not sure. There are several users on Reddit who are reporting that even after completely un-rooting their devices and removing Magisk, Pokemon Go still doesn't work....

https://www.reddit.com/r/pokemongodev/comments/560o9a/safetynet_updated_again/
[Magisk] Tesla:
Are there a way to play Pokémon and have root now?

Magisk v6 and v7 is a no go.

If you know how, please tell me/us in a very specific way with links to what i need.

//

Tesla
[Magisk] Sippi4x4man:
At this time NO. Google has updated SafetyNet and there's no way around it at this time.
[Magisk] Tesla:
Thanks for answer m8.

But i have to ask, why did you tell me this? :confused:

I asked for a solution.

Again, thanks for answering but..;)
[Magisk] ghenxx:
for ****s sake google...

Anyway, my experience:

I uninstalled superuser app

I left magisk manager installed

I rebooted to recovery

I ran magisk uninstaller 20161004 (yesterday's release version)

rebooted to system

ran pogo

Seems to work. I caught a krabby.
[Magisk] Sippi4x4man:
You can ask for a solution all you want but there isn't one.
[Magisk] royaLred:
The only way is Flygps.
[Magisk] .NetRolller 3D:
Confirmed - even after fully unrooting, removing Magisk & everything, SafetyNet still fails. Haven't tried reflashing stock rom using Odin (could be some SuperSU residue in the boot image), but it's looking like Google switched to an "ever rooted before" policy.
[Magisk] ghenxx:
make sure you use the latest version of uninstaller 20161004 version
[Magisk] NWTSCL:
I'm receiving the GPS error when using a device that has always been stock. So maybe they're having problems on their end.
[Magisk] bezeek:
This alienation of root users is just pitiful. Funny how Google suddenly got all aggressive when a Nintendo property came into play. I firmly believe Nintendo and Niantic have a right to try to prevent cheating, but now it's like Google has entirely forgotten that openness is what made their platform so great in the first place.

I took a detour (about an hour ago) between fiddling around with SuperSU and reverting to phh's SuperUser to ensure my device passed SafetyNet, and it did. Try unrooting again from the SuperSU app (to clean system), give 'er a good full reboot or two, flash the latest Magisk uninstaller (to clean data), flash a clean copy of your ROM's boot partition (to clean boot), and see what you get.
[Magisk] 309041291a:
Figures... The day I finally decide to try all of this stuff and play PoGo again it stops working... :laugh:
[Magisk] .NetRolller 3D:
Tried the new Magisk uninstaller, as well as the Full unroot option in the SuperSU app. Didn't help, in fact it made matters worse; I now get "response validation failed" (previously it was just "CTS profile match: false").

On a sidenote, this proves that the malformed SafetyNet response that causes "response validation failed" is not an Xposed bug, but an intentional "super-fail" by Google, in an attempt to punish users who try to subvert SafetyNet.
[Magisk] dfs_:
just for collecting info: same behaviour here on oldschoolcool 6.0.1 with 2016/11 security patch, systemless xposed and suhide: on task switch and random in between crashes and incompatible messages...
[Magisk] bleetx:
I read on one of the channel on Telegram that im into, the last pokemon go update changed its security system from "wolfSSL" to "RakNet" and that should be why it crashes. Idk if that's helpful since I don't even know what are those, but that's all I got :)
[Magisk] soraxd:
so im going to convert all my root apps to system apps, and uninstall Magisk. how might I preserve my 2 Magisk modules tho, like you did?

[MENTION=4344364]DrSeussFreak[/MENTION] [MENTION=1620550]fOmey[/MENTION]
[Magisk] fOmey:
This really isn't a solution.. I was just figuring out what might be causing these crashes. The process of elimination.

We need to either address pokemon go or magisk hide.. removing magisk isnt the solution as your going to loose root.
[Magisk] DrSeussFreak:
Let me know how it goes, I'm running the latest magisk(6.20), and titanium won't load, constant crash on load.

Agreed, but a potential workaround if you have apps that don't require root, and can run as a system app.
[Magisk] soraxd:
thanks, I will. so far my titanium backup is working as I've moved it to system and currently delaying su to it via Magisk Manager.

as for my Magisk Modules tho, is there a way I can stop them from being wiped when I uninstall Magisk?
[Magisk] DrSeussFreak:
[/COLOR]

As it was pointed out to be earlier today, by design magisk cleans up after itself
[Magisk] fOmey:
No unfortunately.. keep a backup of the magisk module zips, will make reinstalling them easier.
[Magisk] soraxd:
I didn't realize the name til I saw the package name.... the only Magisk module I care to save is yours LOL, huge props for your work
[Magisk] marcorua:
I do not know if I will help but tried on my old smartphone (motorola moto g 2013), rom LineageOS 14.1-20170704, security patch June 5, 2017, magisk (16.0). Pokemon go works 100%, do not crash .....
[Magisk] justj0sh:
I'd like to remind you guys that it is very possible that niantic is logging every magisk detection. I'm not sure how many times you get to trigger the device incompatible warning before you get banned.
[Magisk] osm0sis:
Upside being when it crashes it's before it ever shows the incompatible screen so more than likely not phoning home at that point (if it does at all). Thank their buggy code. :p

Nobody has ever been banned from the rooting itself that I've seen, just spoofing.
[Magisk] shoey63:
Root or no root. There will be no bans.

Spoofers have been playing with red warnings and shadow bans for months on end. Niantic won't ban them because they buy items to help them bypass the restrictions (eg: raid passes and insence etc).

It's all about revenue. Appearing to crack down on spoofers appeases legitimate players, and stops them leaving the game.

And then there's IOS users. They spoof with impunity, due to Apple's more strict security regarding apps detecting system operations. Can't see them getting banned either.
[Magisk] justj0sh:
Tell that to my failed to get game data account that I just got :D
[Magisk] shoey63:
You bought it from a botted account. That's the only sure fire ban.
[Magisk] justj0sh:
Lol no it's my own account and I have been playing this acc pure spoof only for more than a year. Zero warning zero shadow ban just randomly got perm ban after 0.95.3. If you'd like to suggest another reason why I got banned other than forcing it to login I'm all ears.
[Magisk] SebaS-DG:
That was so funny to read :eek:
[Magisk] justj0sh:
The fact is I've got one more banned account, which previously had survived a full year, just because of 0.95.3. It had a 100IV Lugia in it from Go Fest in Chicago so I was always very careful with it. Believe it or not it's not my problem :)
[Magisk] SebaS-DG:
I'm usign two smarthphones, with island to play 2 accounts per phone, most of ppl ask me to setup the same config to their phones, and no one of them get an account banned at the moment, only ppl who bot or use maps (poketrack,pokemesh, or iv calcs with logging) is getting banned.
[Magisk] marcorua:
What configuration do you use?
[Magisk] euclanville:
when i install twrp pokemon go crash but rare. then when i install magisk i got the device incompatible message. confirm magisk is triggering on pokemon go detection. bad english :D I am on lollipop with xposed with rootswitched. Next API update we are all doomed :(
[Magisk] DrSeussFreak:
I'm getting the incompatible error as soon as I try to catch a pokemon, I click on one and boom, either it crashes or I get the error
[Magisk] osm0sis:
No such problems here. You're probably running an IV calc root app? Make sure you have no root apps running.
[Magisk] DrSeussFreak:
Calcy iv, it is not root based, but I do have a root call blocker going, you think that is it?
[Magisk] soraxd:
that message doesn't mean you're banned. if you tried on say, a different device, or reinstalled the app, it would likely log in. that failed to log in message is also what root users see, it doesn't mean you're banned, just failed to pass login check.
[Magisk] justj0sh:
Like I said, I do have a new banned account that survived for a full year because I was very careful. It's up to you to make your own conclusions but the only change I can think of is trying to repeatedly make 0.95.3 work :)
[Magisk] Karls0:
It seems that current version of Magisk is unable to bypass PoGO 0.95.3 verification - a lot of FC, tested on two different phones. It log sometimes after several dozen of tries, it is possible to spin pokestop, but when you try to catch a pokemon it is FC or device incompatible message. So game is unplayable so far.
[Magisk] hamonmaru:
[/COLOR]

Yeah.. I have to uninstall magisk to make this game working and just make new problem because all installed magisk modules gone.

It's dilemma to choose magisk or pogo but i choose not playing this game until solution come.

Do not care community day event and obtained expass 2603 gone.
[Magisk] osm0sis:
It's far from unplayable. It FCs once in awhile and there's the odd incompatible complaint but otherwise works fine here.
[Magisk] Karls0:
In my case this incompatible complaint is here every time when the catching screen is on, and it is not possible to close - I can only close the app. So yes, without possibility to catch anything I can assume it is unplayable. I don't use any kind of gps spoof, cheats etc. Root is totally unrelated with PoGO, I use it for thinks like firewall, backup etc.
[Magisk] osm0sis:
You think a root-based firewall is unrelated? Pokemon GO uses the internet. Disable your firewall and I'm sure it'll work fine.

My only root app that was active during Pokemon GO usage was PokeBatterySaver, so I disabled it and now (when it doesn't FC first) it signs in fine most of the time, I can switch tasks, and play without issue.
[Magisk] Karls0:
PoGO has full internet access, it worked all fine until forced updated to 0.95.3 version. I even tested it on second phone, with different system, different manufacturer, without any firewall. It is not device- or configuration-specific issue. I think that new version can detect Magisk or at least comes in conflict with him, which can cause FC and others bugs. However to be honest - I've read about few cases with similar errors without Magisk/root but it is far more frequent for Magisk users. That lets me think, Magisk needs update.
[Magisk] osm0sis:
Yes, a MagiskHide update could definitely fix it by making the hiding process faster. That still doesn't explain your catch issue. Even fully allowed in your firewall, your firewall is still using root to intercept and decide that. Try disabling your firewall and see if your catch issue resolves. You're the only one who's reported that particular issue. Everyone else is just having issues (FCs + incompatible message) at startup and when switching tasks.
[Magisk] Karls0:
Did you read carefully my previous post? I can't play also on second phone that doesn't have firewall at all. I was not even able to login, because of constantly FC. Two days ago it was highly unstable, like you described above, but playable. Today something changed and I can't play on both phones. Maybe some server-update for Niantic - maybe this extra check on compatibility when you start to catch is enabled now, I don't know.