yashsingh1/xdaforums huggingface dataset:
[Magisk] 135Shadowsoul:
Hallo every1,

since magisk v16.4 po/go does work for me... but not stable and safe. I have tested a little bit and i am thinking the problem is magisk hide does not work all the time. after some time, SafetyNet checks fail. i have tried to manually stop and restart magisk hide with

su
magiskhide --disable
magiskhide --enable

after enable i get a error message pointing to logcat error. if i

su
logcat

i get error message "logcat read failure1"

does any1 has an idea how to fix this? as logcat does not work, its hard to post any logs, you know? (if there is a possible way to post helpfull logs, pls tell me)

if this is the wrong thread for the question, pls point me to the better one.

Greetings and thanks for helpfull answers
[Magisk] Didgeridoohan:
It's probably not a Magisk/MagiskHide issue.

You need to figure out why your logcat stops running. It's the central part of what MagiskHide uses to monitor your apps and processes, so if it doesn't work neither does MagiskHide.

You could try running a logcat recording in the background (personally I like MatLog, but there are of course many apps available, and also ADB) until it fails. That might (or might not) show something.
[Magisk] 135Shadowsoul:
MatLog and CatLog (another app) and even a thrid one do not show me any logs. (ofc. i gave them root permission) so... i think i have a problem with logcat... :(

as this is probably the wrong thread for such a question, can you pls point me to the right one? (or maybe PM in order to help me?)

With Magisk v16 (and i am not sure with 16.3) i did not have these problems, but with 16 i was not able to play po/go at all
[Magisk] Didgeridoohan:
Since you say MagiskHide works for a while, that means logcat fails at some point. Logging detection is changed somewhat in Magisk v16.4, so that might be related.

Start by finding some data.

Is there any data in the log in the Manager? If so, upload that.

Is there a magisk_debug.log in /data/adb? If so, upload that.

What's the terminal emulator output of (both when MagiskHide is working and when it isn't):

su
ps | grep log

Does logcat run properly at any point? If so, when does it stop? Reboot and check. You can try grabbing a logcat from boot with ADB and then let it run until something changes.

Does logcat behave the same if you go back to Magisk v16.0 or v16.3?

There's more data to be collected, but that would be a start.
[Magisk] 135Shadowsoul:
the ps | grep log did not return anything in terminal (dont know if it does anything)

i rebootet, and during reboot i can "adb logcat" at some point and get a lot of lines of text. after some time, there is a "read: unexpected EOF!" line.

if i now "adb logcat" there is a "logcat read failure"

looks like logging crashes short time after boot

about v16.0 and 16.3 i dont know at this moment and sadly i cannot flash them currently, mabe later/tomorrow/nextdays

i have attached 4 files in the zip: magisk debug log, magisk manager log, magisk install log and the adb catlog during boot as long as the logging worked.

€dit: i found something: https://sites.google.com/site/zhuoweisite/blog/fixingreadunexpectedeoferrorwhenusinglogcatonandroid80 but "adb logcat -G 1m" and "adb shell" -> "su" -> "logcat -G 1m" both give me error message "failed toset the 'main' log size"

maybe this information can help anyhow? maybe its caust an error cause im on android 7 and not android 8 device
[Magisk] soraxd:
on the latest pokemon go update, I've been getting a lot of failed to log in, takes multiple attempts to log in. anyone else on the latest pokemon go update having this issue as well?
[Magisk] 135Shadowsoul:
sometimes i have this issue, too

for me its works if i set magisk core onlyand (i hope its called that way in english) isolated namespace for root access. reboot after this ofc.

give it a try, i hope it helps
[Magisk] SebaS-DG:
Something is wrong in my xiaomi redmi note 3 special edition, miui 8.4.19.

Im using magisk, with pokemon go marked.

I can play fine, but after 1-2-3-4 hours, it starts to fail, cant log sometimes or while Im playing it says "device or OS not compatible".

To make it work again or prevent this when I need to do a raid/s, I rebot my phone and I play well for a few hours.

I was using 16.3, updated it to 16.4 and its the same.

Edit: this is xiaomi os related or something like that, because when I was playing and my OS was LineageOS, everything seems fine.

Im using Xiaomi OS since 5 days or 6 daays.

Edit: If I force close pokemon go app, after it fails to log or give "device or OS not compatible" warning, it stops for a few loggins more. Faster than reboot phone, but reboot phone seems better
[Magisk] Fivegates:
i'm also experiencing some "device or OS not compatible" since 0.101.1 (magisk, hide active, oneplus 3, oxygen OS 5.0.1)
[Magisk] hamonmaru:
1. you could try MagiskHide Props Config magisk module

I use this module to make magisk hiding better on miui

2. lock magisk manager application to keep running background
[Magisk] Fivegates:
try to clone magisk manager with a new package (in magisk manager settings). It worked for me
[Magisk] SebaS-DG:
I just made a clean install in my Xiaomi Redmi Note 3 Special Edition Kate. With Twrp and Magisk.

After 2 hours of use, pokemon go starts to fail and fail and fail to log.

So, its Miui System or what? anything I need to know about this?
[Magisk] teddy0209:
It depends on your setup. Do you pass SN?
[Magisk] SebaS-DG:
I'll try, thanks!

---------- Post added at 10:41 PM ---------- Previous post was at 10:34 PM ----------

Yes, I pass it, not ctsProfile, I tried: https://xdaforums.com/apps/magisk/module-magiskhide-props-config-simple-t3765199

It fix that, but dont make any diference with Po Go, after 1 o 2 hours of use and play, pokemon go starts to fail when I try to log or while I'm playing with "device or os not compatible bla bla bla".

Just Reset the phone fix that for 1-2 hours and it starts again.

Im using Miui developer edition 8.4.19 Beta.

Magisk 5.7.0, and with the clean install/format everthing, I have flashed 16.0 (before I was using 16.4, before format).

---------- Post added at 10:46 PM ---------- Previous post was at 10:41 PM ----------

1. U mean this? https://xdaforums.com/apps/magisk/module-magiskhide-props-config-simple-t3765199

ALredy tried, didnt make any diference.

2. I'll try, thx
[Magisk] teddy0209:
Since you are using dev rom, you need the right props. Hide the manager, male sure pogo is checked on the hide list. I suggest you use latest beta of magisk (16.4).
[Magisk] SebaS-DG:
16.4 and "props" I used (following the 2 steps to make ctsProfile: true), didnt make any diference with PoGo the last 4 days I have tried it with magisk 16.4 zip.

Today I'm testing 16.0, no "props" and another tips, from a fresh install, I mean, I wiped and format everything from twrp.

Edit: never mind guys, its seems to be another app that Miui + Pokemon Go dont like, but I dont understand because in LineageOS it works Perfect.
[Magisk] Firedragonweb:
I'm a bit at loss as well. Since a few weeks, Pokemon go shows the "device not compatible" error, sometimes on login, but mostly 0.5-2 minutes after login in game. My phone is a Oneplus 3 with Android 8, rooted with magisk without any further modules, Pogo 0.101.1.

I believe I tried pretty much every solution (safe for completly wiping my phone) in this thread:

Magisk Hide for both Pogo-Processes

Checked the list of files Pogo tries to access from a few pages back - none of which exist

tried strace to generate my own list. Sadly, this leads to an immediate Pogo-Crash, meaning I cannot do it right before the dreaded screen

Safety net fully passes

Reinstalled Pokemon go several times

One interesting thing is that I had a Fake GPS app installed to debug one of my own apps. However, it has been uninstalled since and should, if I'm not mistaken, generate other errors in Pogo.

Does anyone have any idea what's left to try?
[Magisk] 135Shadowsoul:
reflashed magisk v16.0 (stable), but still same problem with logcat... attatched the log during boot as long as possible

i am running out of ideas... does any1 else has one?
[Magisk] SpikyAndroid3:
I too have tried all the steps in this thread to get it to work and I've received errors ranging from "...make sure this account exists", "Failed to Login" and the "Device, OS not compatible" even with Magisk Hide active and passing the Safety Check.

However

, I noticed that I am able to login and 'play' without interruptions when my GPS location is turned off - which seems counter intuitive of course but the game seems to trip ("Device, OS not compatible") when it's turned on.

I have tried MagiskHiding any location-based packages but it still trips. Repackaging Magisk doesn't work for me either.

The only current advice I have is to ensure that you remove any files in your /sdcard which relates to the busybox installer or having the "Xposed" installer in the form of an .apk or archive (/sdcard/MagiskManager). I'm unsure whether PoGo can detect the systemless busybox module somehow, but disabling it doesn't make any difference.
[Magisk] Firedragonweb:
Hey, that's exactly the symptoms I am experiencing. When I set the Location to Power saving (no GPS), I can "play" just fine (except it's rather useless then).

---------- Post added at 02:20 PM ---------- Previous post was at 01:48 PM ----------

Okay, I'm even more confused now. After having backed up my data, I decided to completly wipe my phone. The very first thing I did after that was to install Pokemon Go. Guess what happened? "Device not compatible".

Apparently, the newest (and last) version of OxygenOS for the OP3 really seems to be incompatible to Pogo.
[Magisk] SpikyAndroid3:
Did you wipe back to stock (no root, stock OS)?

Is the "Device not compatible" the in-game PoGo screen, or do you see that in the Play Store. First thing I'd check is whether the Play Store says you're certified or not. If not that may be why it's incompatible since I had that issue before I installed Magisk on my OP2. Clear dalvik-cache and clear data from the Google Play Services / Play Store and check again.
[Magisk] Firedragonweb:
Yep, complete wipe of data, cache, dalvic and internal storage. I left recovery as it is. Play store says it's certified, and the result is: I get the same in-game-screen stating incompatible as before.

Edit, to make the confusion perfect: After another factory reset, it works well.
[Magisk] coolwater22:
Anyon having pogo+ not connecting or connecting for a few mins but then disconnecting in a few mins?
[Magisk] Daimao1984:
But whats ur root method, if ur not using magisk?
[Magisk] origitat:
I don't get it. I did the same (Magisk Uninstaller (new version) uninstall phh su but it still don't work. What are the locations I should check manually for root dirt still laying around? I checked /system/bin and system/xbin and there was nothing.

I also did a cache/davlik wipe to no avail.
[Magisk] pineappleraptor:
[deleted] double post
[Magisk] Daimao1984:
Whats ur ROM? Im starting to think that only stock-based ROMs can login through these steps (in my case, for instance, I did even less steps than u did - only flashed magisk uninstaller and that was it).

If u are on CM, maybe ur out of luck.
[Magisk] pineappleraptor:
Can you please post the steps you took to get yours working? Also which device and ROM are you using?
[Magisk] Tesla:
People got root and pogo working. Thats so cool. :good:

What's not cool is that they just say they got it working... not how and on what rom and bla bla..

Please give us all the details. And i mean all the details. Remember, lots of readers are beginners.
[Magisk] .NetRolller 3D:
Note 4 N910C on stock Marshmallow.

I reflashed my ROM using Odin (no data wipe), then reinstalled custom recovery, and finally installed phh's hidesu zip from recovery. That's all.

Unfortunately when I try to install romracer's 86.0 systemless xposed (the only systemless xposed available that needs neither SuperSU nor Magisk), it appears to install fine, but on boot, no Xposed. For some reason, it's unable to loop-mount xposed.img - I checked this by hand, xposed.img is a valid ext4 file system, but when I try to loop-mount it from an adb shell, it fails with "can't read superblock". Probably some selinux-related issue, but no idea.
[Magisk] oTeMpLo:
Ok and t will only work for 14 days..., But at least It work now..
[Magisk] AkaMM_:
uninstall magisk and phh root and pogo its work... but i miss my root :(
[Magisk] Deities:
Maybe some sort of MultiROM setup can make this work
[Magisk] .NetRolller 3D:
Reinstall phh's su using the link I posted. It can mask itself from SafetyNet.

Still waiting for a working build of Xposed that needs neither Magisk nor SuperSU.
[Magisk] pineappleraptor:
Major thanks to .NetRoller 3D. Here are my steps. DISCLAIMER. Not responsible for any problems. I have a STOCK HTC 10 ROM. Not a custom ROM. These steps could result in problems if you have any non-STOCK ROM because it's a Stock Boot.img that gets flashed. I recommend NOT doing this on a Custom ROM (If anyone knows for sure, please correct me)

My Device: HTC 10 Unlocked :)

Previous Setup:

Magisk V7

PHH SuperUser Magisk version

No Xposed Installed as it never worked for me with PoGo

I used:

PHH Superuser-hideSU (.NetRoller 3D linked to it in his post) Edit: Here's his link

http://xdaforums.com/android/softwa...-superuser-t3216394/post68969947#post68969947

Steps:

1. Reboot into TWRP.

2. Flash LATEST Magisk Uninstall zip in the Magisk Thread.

3. Reboot

4. Wait for Android to Upgrade...

5. Reboot into TWRP

6. Flash boot.img from a non-rooted nandroid backup. I didn't wipe data, I just unchecked everything but "boot"

7. Reboot to System.

8. My PHH Superuser App was uninstalled already, but if yours isn't, wait and then Uninstall it like a Normal App. Check Safetynet, and it should pass at this point. If not Reboot, and check again.

9. Reboot into TWRP

10. Flash PHH-SuperUser-HideSU (NOTE: You shouldn't need a separate SuperUser Zip. This has SU and HideSU in one)

12. Reboot

13. Re-install PHH Superuser from PlayStore. Grant your root priveleges as needed. SafetyNet should pass and you should have full Root AND PoGo/Android Pay
[Magisk] Tesla:
Thanks m8 :)

I wonder if superuser-r266-hidesu.zip and Superuser_2.0_Beta_6.apk works with Pokémon?

Superuser_2.0_Beta_6.apk

It does work with Superuser_2.0_Beta_6.apk :=)

Playing pogo now and root works,

Thanks m8.
[Magisk] hugohthuang:
yes
[Magisk] VoiceGuy:
Thanks for the detailed instructions, [MENTION=4507299]pineappleraptor[/MENTION]. I have a Nexus 6 with the latest PureNexus rom & ElementalX kernel. It was running Magisk V6 & Phh SuperUser Magisk version. No Xposed. Followed the instructions, passed safetynet, PoGo & my root apps working good so far.
[Magisk] giffyy:
So did you follow all the steps provided by pineappleraptor

OR

you just installed superuser-r266-hidesu.zip and Superuser_2.0_Beta_6.apk and it worked with your phone?

I have the same phone N3 as you with same kernel using AryaMod

THanks!
[Magisk] Tesla:
Hi.

More or less.

Had no root and had no magisk or xposed. That was already done. So yes, just installed superuser-r266-hidesu.zip and Superuser_2.0_Beta_6.apk and boom it worked.

No need for Flash boot.img for me.

Edit: Btw.. Recovery always wants to root your phone after you unroot. Don't let it.

Sounds silly? Well, it's an easy thing to miss. ;)
[Magisk] ameel:
Does hidesu pass new SafetyNet update? I just compiled SuperSu for x86, but SafetyNet doesn't pass and I'm not sure whether hidesu isn't working properly for x86 or whether hidesu doesn't pass SafetyNet since last update.

Can anyone please clarify?
[Magisk] Tesla:
superuser-r266-hidesu.zip works.
[Magisk] hugohthuang:
include Xposed? thanks
[Magisk] Didgeridoohan:
I'd keep investigating about increasing the logger buffer size. Check your settings, under "Developer Options" if there is a setting for the logger buffer size.
[Magisk] 135Shadowsoul:
good morning

i increased logger buffer size to 16M (max. possible) and tryed logcat: still read failure

i rebooted with logging during boot and got a lot of line of information (see attachement). but the last line is still a "read: unexpected EOF!"

maybe its a logging problem with my rom and i should ask the rom-dev? (or maybe flash latest update?) but if so, i am wondering why it appears with the latest magisk versions. i did not re-flashed the rom for month.

problems startet to appear with po/go v0.97.2 and v0.99.1 and the magisk updates arround this time. i did not do anything with the rom

any idea?
[Magisk] Didgeridoohan:
Have you tried doing a clean install of v16.0, uninstalling and then reinstalling? If that still doesn't work I would ask your ROM developer...
[Magisk] 135Shadowsoul:
i will try next days.

to uninstall, do i just have to flash uninstaller from magisk main thread? do i have to wipe dalvik/cache? do i have to reboot before flashing magisk again? (do i have to uninstall manager, too?)
[Magisk] SebaS-DG:
With Miui OS, my problem was (yesterday I figurate it) when in gps joystick (clon or not) I used "disable location services", this is working fine in lineageOS and pokemon go, but not with Miui.

Getting deviceor or not compatible, loggin takes for ever, after 1-2 hours of playing fine. Reboot the phone makes the game works fine for 1-2 hours.

With this activated, my gps dont drift or jumps. But now I deactivated it and I need to use some tricks to block gps signal.
[Magisk] n82freak:
I got the same problem since pogo 101.1

On older Version all good .

I tried the hole hiding procedere again but every login i get the message that my os not supported .

I dont know what to do or what can try to fix it. I would generate a log but i cannot generate the access list .

Anyone here who can explain exactly what to do to generate my access log ?
[Magisk] Firedragonweb:
Sure.

Download the strace binary from the post a few pages back

Copy that binary to e.g. /sbin/

Open an adb command line on your pc and execute adb shell

Enter root: "su"

chmod +x /sbin/strace

Now you can follow the steps in the original post

Be aware though, that you might have to be pretty fast to enter the commands: Pokemon go must be running before you can find out the PID with ps, but you have to start strace (with the PID) before the error occurs.

I had the same symptoms; for me, a phone factory reset was neccessary.
[Magisk] n82freak:
I try to explain what happens in post post 3513 i think

It works fine and i get a tracefile.

But if i use

grep access\(* /sdcard/trace.txt.

then pogo crashing .

And in the tracefile are many text but i dont understand the Text.

The file is over 5mb large

Here a little bit of my tracefile:

1913 futex(0xc89e46d4, 0x89 /* FUTEX_??? */, -2 <unfinished ...>
1978 recvfrom(96, <unfinished ...>
1913 <... futex resumed> ) = -1 EAGAIN (Resource temporarily unavailable)
1978 <... recvfrom resumed> "nysv\0\0\0\0\315J\245\3267m\0\0\230\232c\0face", 2400, MSG_DONTWAIT, NULL, NULL) = 24
1913 futex(0xc89e46d4, 0x89 /* FUTEX_??? */, -2 <unfinished ...>
1978 recvfrom(96, <unfinished ...>
1912 futex(0xc89e46d4, 0x89 /* FUTEX_??? */, -2 <unfinished ...>
1978 <... recvfrom resumed> 0xc0e7e868, 2400, 64, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
1911 <... futex resumed> ) = 0
1978 clock_gettime(CLOCK_MONOTONIC, <unfinished ...>
1911 futex(0xc89e46d4, 0x89 /* FUTEX_??? */, -2 <unfinished ...>
1978 <... clock_gettime resumed> {120086, 592462446}) = 0
1910 <... futex resumed> ) = 0
1978 write(83, "\1\0\0\0\0\0\0\0", 8 <unfinished ...>
1910 futex(0xc89e46d4, 0x89 /* FUTEX_??? */, -2 <unfinished ...>

Hope someone can explain what i do wrong with the command and how to read or interprete the trace .

Thx a lot
[Magisk] ~DPD~:
I've tried this several times but without luck. When I enter "strace -f -p XXXXX -o /sdcard/trace.txt", in the command window it first says "Process YYYYY attached with 92 threads" and it repeats the same multiple times but with other PIDs and without the threads part. Then PokemonGO gets slow (at the same moment I press enter), crashes and the final .txt is huge (I've got files from 9 to 24Mb). When I open it, there is a lot of lines and different PIDs.

I haven't been able to get the "device not compatible" warning before the app crashes. Am I doing something wrong?
[Magisk] SpikyAndroid3:
I'm getting the same problem here. Though I'm not sure if it has to do with the PID selected. Once I run

ps |grep nia

It seems to return one package - com.nianticlabs.pokemongo

I've also noticed that the parameter is different with the output, instead of

u0_a731 XXXXX 3294 1887976 307604 [B]do_signal_[/B] 00ef6068a4 T com.nianticlabs.pokemongo
u0_a731 XXXXX 3294 1289420 18344 [B]SyS_epoll_[/B] 00ef6068a4 S com.nianticlabs.pokemongo:pgp

# I get this:

u0_a731 XXXXX 3294 1289420 18344 [B]SyS_epoll_[/B] 00ef6068a4 S com.nianticlabs.pokemongo

This probably making the difference when analysing the PID of that package.
[Magisk] dadnammit:
Using Magisk 16.3 and Magisk Manager 5.7.0 with Pokemon Go 0.101.1 on a Xiaomi Mi A1 running Oreo 8.0.0.

I setup Magisk Hide for Pokemon Go and ran the app. After about a minute, it gave me the notice:

“This device, OS, or software is not compatible with Pokemon GO.”

After that, authentication always fails, even after a reboot.

Looking at this thread, jeez, what a pain this is!
[Magisk] coolwater22:
Try a clean install and use magisk 15.3 and magisk manager 5.6.4..thats what i had earlier and it worked. Now since they updated magisk to 16.4 im using that and that works well with 5.7.0 magisk manager. Try and see if either of those work.
[Magisk] 135Shadowsoul:
tryed to uninstall and re-install magisk, but still after some time, "logcat read failure" :(
[Magisk] Fivegates:
Rollback to magisk 16 and should work
[Magisk] 135Shadowsoul:
new information:

if i "su" and "start logd", it seems logcat is running again. i am able to "magiskhide --disable" and "magiskhide --enable" and i can again pass SN. Po/Go starts. but then it seems the Po/Go root checks are running and find something they should not find imo. => maybe magiskhide does not work 100% with re-startet logcat? any idea? do you want any logs? if yes, wich ones?

i will try to provide as much information as possible :)
[Magisk] Didgeridoohan:
Interesting... So you probably have something that's stopping logging quite late during boot.

If you can pass SafetyNet, MagiskHide is working. No question about it... It's likely one of the other issues described earlier in the thread (having to add sub-processes manually or other apps triggering PoGo).
[Magisk] 135Shadowsoul:
new information again: it seems, with "start logd" i can re-enable logcat logging, but not everytime "magiskhide --enable". even if logcat is running again, it sais "logcat is disabled" :(

edit: magisk hide just needs a bit longer to "not work" anymore (failing SN)
[Magisk] vamprook:
I did this, and it's not working, most of time i can't login and when i can login it gives to me the "not compatible device" error.

I'm using lastest version of magisk and pogo on a Galaxy s6 with Android 6.0.1 :/
[Magisk] 135Shadowsoul:
hi

i am facing similar problems

try and report outputs/results of the following:

reboot phone and directly after reboot start po/go (ofc. hidden) <-- works for me and i can play ~1h until po/go starts next SN check

run "adb logcat" from computer (prefered way imo) or "su" + "logcat" from terminal emulator. <-- after some time of logging i get "read: unexpected EoF" if logging early enough or later a "logcat read failure"

also try "su" + "magiskhide --disable" and try to "magiskhide --enable" <-- getting error message about "logcat is disabled" (even if i restartet it by "su" + "start logd" + "logcat")

if you get similar results/outputs i am not alone and we can try to find out whats borken (im on a Samsung s4 with LOS 14.1 (Android 7.1.2))