Database Develop

FE Heroes not working despite safety net check passing

Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!

pqueiro said:
Hey! First off, thank you to the creator of magisk, it's amazing and very useful
However, I can't seem to get Fire Emblem Heroes to work. OP3T on stock rom, TWRP and magisk 11.1, nothing else. Using MagiskSU for greenify and adaway and everything works. Manager says I pass the safety net check (used to give a profile mismatch but that went away after rebooting) and I've enabled magisk hide for the app, to no avail.
For what it's worth PoGo seems to be working fine.
What further info could I give you to help and where do I get it?
Thanks!!!!
Click to expand...
Click to collapse
Trying to update the game e get the message "your device isn't compatible with this version"

Rcpbarba said:
Trying to update the game e get the message "your device isn't compatible with this version"
Click to expand...
Click to collapse
I just updated from 1.0.2 to 1.1.0 and keep getting the same error message as before (the good old 803-3001).
This is supposed to be a connection error message, but it doesn't make sense -- if I hotspot off my magisk'd OP3T to a stock OPO or a stock iPad, the game works fine, so it stands to reason the connection is good.
Hence my suspicion that it's probably a SafetyNet issue (FE:H, like PoGo, uses SafetyNet -- might be a Nintendo thing). Any idea how to get around it?
Thanks!

Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

Didgeridoohan said:
Might be an issue where the app also relies on another app or service to find a rooted device. See this thread, the Hiding root post under "Dependencies": https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.

pqueiro said:
Good idea. I didn't think of that, but alas, the game doesn't ask for any permissions (and none listed in settings) -- so if they do use 3rd party software to check, it doesn't show up in the permission list.
Inspired by Pocket Morty's dependency on Google Play Games, I went and installed that too (I'd removed it as a cruft-reduction exercise) to see if that was it, but it's not. Still doesn't work, same error message.
Click to expand...
Click to collapse
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.

Didgeridoohan said:
Yeah, I don't think it has to be as a result of permissions (note to self: update the text)... It might also be that the app is looking for certain prop values. Both of these are hard to figure out without decompiling the apk.
Click to expand...
Click to collapse
Well now, that's substantially more complicated and probably out of my league I'll have to stick to playing it on the iPad. It's not impossible, just annoying.
Thanks!

you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)

panchovix said:
you could try on nox pc emulator too, it is working on 1.1 (i had to disable root tho)
i will try with magisk on my phone until i install the apps on LineageOS13
EDIT: @pqueiro it works on LineageOS 13 and using Magisk 11.1, without problems, so i guess can be something of the rom (i can pass the net check too, and PoGo without problems)
Click to expand...
Click to collapse
The plot thickens. Let me check on my "playground" phone if I can replicate that.

@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.

Klassikal said:
@pqueiro
did you install the game when the Phone was already rooted?
I can replicate this issue when installing the game on already rooted devices - but if I install the game on a non-rooted device and apply magisk afterwards the game launches proper.
Create a nandroid backup, flash the rom and try to launch the game while non-rooted and see if it makes a difference for you.
Click to expand...
Click to collapse
FYI, tried this (took the opportunity when updating Oxygen OS) and it worked a treat! All is good. Backup > unroot > update > install > magisk all the things and it's working fine.
Thanks!

Banks app detects root after update v18.0 (with Magisk Hide and hidden Manager)

Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.

Adios2nd said:
Hi, thanks for reading.
I've used Magisk 17.3 with all my bank apps perfectly, with Magisk hide and Magisk manager hidden.
After update to 18.0 and update manager to 6.1, the bank apps start detecting root status, and stop working.
So, I've flashed back to 17.3 and old manager 6.0.1, and everything's back to working normally.
My system:
Poco F1
LineageOS 16.0 built 27/11/2018
The apps are from Thai's banks:
SCB EASY: detected root, still working
TMB Touch: detected root, stop working
KTB Next: detected root, working partially
If you'd want any log or anything, please also tell me how to get them.
Click to expand...
Click to collapse
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk

Can confirm that this works, thanks.
For me, it started getting detected on 17.x even before updating to 18, right after the banking app (Sparkasse) was updated.
LG G6.

hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This didn't work for me. I had to downgrade back to 17.1 to get my banking app working again. Appears that the root detection prevention is a regression in this latest version.
-- SSS

hsiehboss said:
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide msgisk manager.
5.rehide app.
6.reboot.
it work for nexus 6p.
Click to expand...
Click to collapse
This doesn't work for me.
Did all of these...still got detected.

I have the same problem. Magisk says: ctsProfile: False and Google Pay don't work. Also my Banking App detects root.

I flashed today the latest Los 15 build and the crt false error is till there after flashing magisk 18. The same error is also with 17.4...

Tell me if I'm wrong but I believe we have two different reports: the original report where root is detected, and the ctsProfile/basicIntegrity failing. The second one is a regression fixed by rebooting device (however, it is annoying to reboot 10 times a day because suddenly SafetyNet fails for no reason).

I am using Magisk Hide Props module, and after 18.0 update Santander App detects root, even with Magisk Manager says I pass safetynet

It's happened with my bank app as it detected root & saftynet false and have to downgrade to ver.17.2
Sent from my SM-C900F using Tapatalk

See in install app delete old magisk manager, after install magisk 18.0 new magisk manager rename to manager.

I have same problem. After install v18 magisk, same bank app can detect the system is rooted. Downgrade to v17.2, all bank app become normal.

Same here since Magisk 18 my BankApp (Intesa Sanpaolo) start and says that there is a safety problem and it close, if I choose Magiskhide it doesn't start at all.
SafetyNet check spin without an end.
With Magisk 17.1 and 17.3 no problem at all.

Same problem here, after upgrading to Magisk 18 claiming to better hide root in the history, apps now suddenly detect root.
This affects also the Safety Net check and Google Pay... so far, Root Hiding in 18.0 seems COMPLETELY broken.
A solution would be great.

Later... after downgrading to Magisk 17.2, MagiskHide is working for me again and Safetynet checks succeed. The dev is aware of the problem, an issue is open on the Magisk Github (#907)

After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide

I can confirm the v18 update breaks something and BOTH safety net checks fail. So all apps detect you are rooted, especially bank apps and Get Pay. Downgrading back to v17 restored everything to normal.
The only thing I could think of is the installation method. I did the direct install rather than installing the zip via recovery. Not sure if it makes a difference but I will wait for next release.
I am on a Pixel 2 with Android Pie updated to the Aug 2018 release.
---------- Post added at 12:47 PM ---------- Previous post was at 12:43 PM ----------
Harlock1978 said:
After uninstalling and reinstalling my bankapp now works without any problem and doesn't detect root even if is not under Magisk hide
Click to expand...
Click to collapse
I did not uninstall but tried clearing bank app data and cache and the problem persisted. Magisk still showing all red for safetyNet. Just sharing testing feedback.

@Djtrip83 Did you try just toggling MagiskHide off and on once after updating to v18? Sometimes MagiskHide simply needs a restart after an update...

I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.

Djtrip83 said:
I did that too. Toggled Hide on and off for all apps. Repackaged Magisk. Turned off USB debugging. Removed modules installed. Tried everything I thought would work. Even restored hosts in case Ad Away affected something on /system.
The only thing I did not do was remove root apps and re-install them to re-grant permissions after the Magisk update. And I wonder now if uninstalling Magisk completely and make a brand new clean install with v18 would work rather than upgrading.
I was at a loss so I downgraded. Sorry I don't have a log to share. However, v17 works fine.
Click to expand...
Click to collapse
We might be misunderstanding each other, but what I'm talking about is simply to go to the Manager settings and change the toggle for MagiskHide to off and then on. No need to do anything to the Hide list or anything else... Did you do that? As I said, that's sometimes something you the to do after an update, but it's rare.

Magisk has silly bug request rejected

@topjohnwu
Its been long i have been experiencing this same problem since magisk v15 and i am not the one who is getting this issue.
When you flash magisk everything is fine and you get su prompt without any issue.
But if you see after sometime maybe like 10 or15days its not sure it comes random and new app you install yoj never get prompt of su request.
Issue in magisk log is same as others
04-26 07:54:08.656 26879 26879 E Magisk : write failed with 32: Broken pipe
04-26 07:54:23.254 27099 27099 W Magisk : su: request rejected (10240->0)
04-26 07:54:57.742 27473 27473 W Magisk : su: request rejected (10230->0)
04-26 07:55:06.003 27527 27527 E Magisk : write failed with 32: Broken pipe
04-26 07:55:12.932 27541 27541 W Magisk : su: request rejected (10262->0)
04-26 07:55:18.934 27571 27571 W Magisk : su: request rejected (10211->0)
04-26 07:55:26.091 27612 27612 W Magisk : su: request rejected (10217->0)
04-26 07:55:26.093 27613 27613 W Magisk : su: request rejected (10217->0)
04-26 07:58:20.432 27670 27670 W Magisk : su: request rejected (10211->0)
Click to expand...
Click to collapse
that 10412 is random number maybe uid
But saved su request apps keeps working as fine they can execute su commands which are saved in magisk manager but new apps never get the prompt.
So i think this issue is somewhat related to magisk manager app which doesnot repond, even though i have made sure magisk manager is in my recent app not killed still no prompts.
Now i am fed up with this so posted this issue.
The only thing which works for me i have taken data backup of magisk manager and restore it so my apps stays working fine.
Temp fix whivh always work for me is i have tk flash system image in twrp backup restore and then after sometime after reboot magisk shows prompt, dont know whats this.
My devices are s7 and s9+ exynos same issue on both since v15 i started using magisk.
Full logs attached.

I think I faced the same issue (or at least something similar) two or three times, I will try to get some logs for the next time.

This needs to be analyzed properly every user gets this but we ignore wven for me it is not working even after jninstalling and installing magisk

Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.

Didgeridoohan said:
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Click to expand...
Click to collapse
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached

BytesReverser said:
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
Click to expand...
Click to collapse
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.

Didgeridoohan said:
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Click to expand...
Click to collapse
I have already added magisk manager to unoptimized apps in battery, dont know what is wrong only @topjohnwu can help.
Right now i didnot flashed system because i want to figure jt out whh this is happening, i can test if topjohnwu guides what he needs

hope topjohnwu will fix it soon

I managed to get it work again. Sharing what i did in sequence:
1. Delete all module in magisk. Trash can icon. Reboot.
2. In magisk manager, uninstall > clear images. Reboot.
3. In magisk manager, uninstall > complete uninstall. Reboot automatically.
4. Reboot to recovery. Flash magisk uninstaller .zip. clear dalvik/cache. Reboot to system.
5. Install magisk manager apk. Reboot.
6. Reboot to recovery. Flash magisk 19.1 zip. Clear dalvik/cache. Reboot to system.
Try su at terminal trigger magisksu prompt after step 6.
Hope this helps.

I have a blu dash l 4.4.2 with twrp and I'm also facing this or similiar issue with su request rejected in log, permission denied in terminal, modules flash but magiskhide and superuser do not. I have tried many things with no luck.
No display over other apps, battery, or any other permission settings included. Only 20.4 flashes on my devices others say unsupported image format. 7.1.1 magisk manager seems to be only one which says additional update but then goes to setup failed. Magisk app settings others ok, tried toggling root access, canary settings crash. Have tried to copy and chmod rw 600 to libdirect file from another device to vendor and lib folders because my device does not appear to have it included. Minimal adb fastboot module tip no luck as well as reflashing stock.
Would like to try to add "(sleep) 1 to early_mount " as I read somewhere but not sure how exactly. No luck yet manually updating magisk.db but I am hoping there is someway to have it fully functioning automatically somehow. Any help much appreciated

i have the same issue ,i was rooting my huawei with magisk ..
To resolve this you need to go to magisk manager press install (the first one) ,recovery mode (if needed) and then direct install ,this worked for me

[Discussion]Harry Potter: Wizards Unite Discussion Thread

Niantic, well know for creating Pokemon Go, released their new AR game, Harry Potter: Wizards Unite. Supposedly, the approach to this game was to build upon what made PoGo great. Right now there is a new root check for this game which is completely different from Pogo. Anyone have any clue on how to run the app with a root device?

Huh, I thought I was going crazy. I've tried Hide, renaming package, removing all root-named apps... anything we can do?

I've been playing since the beta and have had no issues running the game. Just make sure you do all the normal steps. If you receive the "Device not supported" error then root or Magisk is being detected.
Hide Magisk Manager (rename)
Magisk Hide Wizards Unite
Ensure Safety net passes
Rename any and all files with "Magisk" in the name on your internal storage to something else i.e Magic.zip

Mildly said:
I've been playing since the beta and have had no issues running the game. Just make sure you do all the normal steps. If you receive the "Device not supported" error then root or Magisk is being detected.
Hide Magisk Manager (rename)
Magisk Hide Wizards Unite
Ensure Safety net passes
Rename any and all files with "Magisk" in the name on your internal storage to something else i.e Magic.zip
Click to expand...
Click to collapse
Renaming the Magisk app/files doesn't affect their function?

ragnarokx said:
Renaming the Magisk app/files doesn't affect their function?
Click to expand...
Click to collapse
Sorry meant to say rename all .zip files so if you have a Magisk.zip for flashing make sure to rename the file to something else. Magisk will download a new .zip when updating it so make sure to check your downloads folder.

I have the same issue, playing the version that was released last Friday.
Magisk Hide seems to work, but it only allows me to play for maybe 5-15 minutes and then the "device not supported" error still pops up.
Edit: Turns out I never used the option to hide Magisk Manager before Going to check if that helps.

MrMagic said:
I have the same issue, playing the version that was released last Friday.
Magisk Hide seems to work, but it only allows me to play for maybe 5-15 minutes and then the "device not supported" error still pops up.
Edit: Turns out I never used the option to hide Magisk Manager before Going to check if that helps.
Click to expand...
Click to collapse
Pretty sure you also have to do that because without magisk manager hidden they can easily detect the original package name. The fact you can play 5-15 minutes it's when they start checking for root. Also happens in pogo. If the error still happens try to clear the data of the app and the root detection should be gone for good

Magisk hide+rename magisk+no magisk related file on my device+safety net pass
Getting the error every 2-10min. I also reinstalled the game but nothing does change. PoGo has no problem.

I am also getting the same error even after magisk hide and everything else.
After a reboot it works for Quite a while but after a while it reports incompatible device again.

Same here, nothing named "magisk" on my device anymore, hide is on, still get the message every few minutes
Edit: I forgot to "Hide Magisk Manager (rename)" in the Magisk settings. Played for about an hour today and no incompatibility message! I think that fixed it.
What I did was
1) used Root Explorer and searched my system for "magisk" and renamed or deleted all results
2) hide wizards unite in Magisk Manager
3) go to Magisk Manager settings and click the option that renames the Magisk apk to a random filename

ragnarokx said:
Same here, nothing named "magisk" on my device anymore, hide is on, still get the message every few minutes
Edit: I forgot to "Hide Magisk Manager (rename)" in the Magisk settings. Played for about an hour today and no incompatibility message! I think that fixed it.
What I did was
1) used Root Explorer and searched my system for "magisk" and renamed or deleted all results
2) hide wizards unite in Magisk Manager
3) go to Magisk Manager settings and click the option that renames the Magisk apk to a random filename
Click to expand...
Click to collapse
In addition to these steps, I needed to clear the magisk log in magisk manager.
I did this through the following steps,
Tap the menu icon in magisk manager,
Tap log,
Tap the magisk tab (superuser tab may be shown, it doesn't need to be cleared)
Tap the trashcan icon in the top right corner
This is on magisk manager 7.3.2 (224).

All I did was use Magisk hide to hide it from the app and then renamed Magisk in the settings

The OP should update the original post with these so others after us don't have to search for it or ask the same crap over and over.
I can play this game just fine with root and Xposed framework installed and SafetyNet passing. So long as you don't give the game permission to access storage then there isn't much of a chance that the game is scanning for anything named Magisk but I did it anyway. After following what I've quoted below I still wasn't able to play so I cleared game cache and game storage and then uninstalled the game and reinstalled. Before opening the game I made sure to hide it from Magisk.
In addition, LP is installed on my device and only with its Xposed module was I able to hide LP (package rename). I've read or been told at some point that LP can be detected as a GPS hack or similar so I took the extra step. You don't have to have Xposed at all to run WU on a rooted device but it is required to be able to hide LP.
Mildly said:
I've been playing since the beta and have had no issues running the game. Just make sure you do all the normal steps. If you receive the "Device not supported" error then root or Magisk is being detected.
Hide Magisk Manager (rename)
Magisk Hide Wizards Unite
Ensure Safety net passes
Rename any and all files with "Magisk" in the name on your internal storage to something else i.e Magic.zip
Click to expand...
Click to collapse
lpfansether said:
In addition to these steps, I needed to clear the magisk log in magisk manager.
I did this through the following steps,
Tap the menu icon in magisk manager,
Tap log,
Tap the magisk tab (superuser tab may be shown, it doesn't need to be cleared)
Tap the trashcan icon in the top right corner
This is on magisk manager 7.3.2 (224).
Click to expand...
Click to collapse

lpfansether said:
In addition to these steps, I needed to clear the magisk log in magisk manager.
I did this through the following steps,
Tap the menu icon in magisk manager,
Tap log,
Tap the magisk tab (superuser tab may be shown, it doesn't need to be cleared)
Tap the trashcan icon in the top right corner
This is on magisk manager 7.3.2 (224).
Click to expand...
Click to collapse
Sadly that also doesn't work on my device.
Are you using other modules? I'm thinking right now that Youtube vanced could be a problem.

Impact7 said:
Sadly that also doesn't work on my device.
Are you using other modules? I'm thinking right now that Youtube vanced could be a problem.
Click to expand...
Click to collapse
YTV would not make WU throw a device incompatibility error. Root in some way or another is being detected by WU or you may have a device that is confirmed not supported. No extra Magisk modules, no extra tricks required.
I can play this game just fine with root and Xposed framework installed and SafetyNet passing. So long as you don't give the game permission to access storage then there isn't much of a chance that the game is scanning for anything named Magisk but I did it anyway. After following what I've quoted below I still wasn't able to play so I cleared game cache and game storage and then uninstalled the game and reinstalled. Before opening the game I made sure to hide it from Magisk.
Mildly said:
I've been playing since the beta and have had no issues running the game. Just make sure you do all the normal steps. If you receive the "Device not supported" error then root or Magisk is being detected.
Hide Magisk Manager (rename)
Magisk Hide Wizards Unite
Ensure Safety net passes
Rename any and all files with "Magisk" in the name on your internal storage to something else i.e Magic.zip
Click to expand...
Click to collapse
lpfansether said:
In addition to these steps, I needed to clear the magisk log in magisk manager.
I did this through the following steps,
Tap the menu icon in magisk manager,
Tap log,
Tap the magisk tab (superuser tab may be shown, it doesn't need to be cleared)
Tap the trashcan icon in the top right corner
This is on magisk manager 7.3.2 (224).
Click to expand...
Click to collapse

Are the files located at "root" also needed to be removed/renamed? Or only those located at the internal storage? Thanks..

Hello,
I’m not sure its the right thread as I don’t have a rooted phone but I didn’t found a lot of threads about the game.
But here is my question:
Do you think the google apps are absolutly necessary ?
I have a lineageOS 16 installed without gapps and can’t pass the login with facebook screen (login with google don’t work, nothing happen)

after following these exact steps it instantly gives me incompatible device:
uninstalling wizards unit
rebooting to make sure minimal data is preserved
making sure magisk is renamed to some random string
making sure nothing named "*magisk*" exists on internal storage(and I never gave permission anyways)
install wizards unite
magisk hide wizards unite
start wizards unite and log in with my account etc
Could there be anything that wizards unite checks besides this?
I have tried many times making sure I followed everything exactly, but it still doesnt work.

On my Oneplus 3 with LineageOS 16, Magisk 19.3, and GPS Joystick by The App Ninjas, I keep getting "Device Incompatible" error intermittently, i.e., every 5 to 10 minutes. I tried the following:
1. Pokemon Go works perfectly
2. Passed Safety Net (two ticks)
3. Hid the GPS Joystick app
4. Deleted whatever "magisk" named files
5. Confirmed that the game doesn't have file storage access
6. Cleared whatever logs left by Magisk
7. Removed Magisk Manager (didn't hide it)
8. Confirmed that when searching for "magisk" or "gps" in /sdcard/* there is nothing found.
9. Cleared the cache of the game
10. Did not run GPS Joystick (but it is still in /system/priv-app since it was installed via App Systemizer, and hidden by Magisk).
Any ideas?
Update: I fixed it! I have to Magisk hide both the game and the GPS Joystick app.

Linuxfornoobs said:
after following these exact steps it instantly gives me incompatible device:
uninstalling wizards unit
rebooting to make sure minimal data is preserved
making sure magisk is renamed to some random string
making sure nothing named "*magisk*" exists on internal storage(and I never gave permission anyways)
install wizards unite
magisk hide wizards unite
start wizards unite and log in with my account etc
Could there be anything that wizards unite checks besides this?
I have tried many times making sure I followed everything exactly, but it still doesnt work.
Click to expand...
Click to collapse
Tried the same over and over again. If I got time I will full wipe (also internal) and flash my ROM to see if anything from the years before is causing the problem. I'll write here if anything does change.

[HELP] Hide Magisk Manager (Repackage) upgrades the version over the internet

I have my Samsung A30 (SM-A305F) rooted with magisk canery (87de0e7a) by flashing patched boot img via odin. Now, If i try to hide magisk with random package , it demands internet connection and install the latest version (9348c5ba). BUT i don't want to upgrade as the updated version has weird bug of rejecting SU automatically (with a very brief pop-up). I then need to ---> uninstall the repackaged app ---> Reboot ---> install 87de0e7a version ---> then it become functional again. I don't have TWRP installed. Re-flashing new patched boot requires wiping data. i don't want to do factory reset
Now I want to hide magisk as PUBG MOBILE might be crashing due to root detection. Please help me achieve solution:
(1) hide magisk manager without updating
(2) update magisk manager without that BUG of rejecting SU automatically

1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions and owner).
Edit: replace the package name above with the one your Manager uses.
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.

Note: i previously managed to hide it successfully when there was no newer version. It would just download the same version from the internet and repackage itself with random package name. But some days ago, i restored original manager and now i can't get it to hide.

Didgeridoohan said:
1 - Hide the Manager and let it update fully, no way around that. Then replace /data/user_de/0/com.H3.nuhw6UY.GoCgl/dyn/current.apk with the apk of whatever Manager version it is you want to use (and don't forget to set the same permissions).
2 - Seems to be a similar issue reported here: https://github.com/topjohnwu/Magisk/issues/2944
If there's anything to be done about it, it will be eventually.
If you can get some proper logs showing the su rejection and add to the above linked issue that would be great.
Click to expand...
Click to collapse
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again

Shihabus Sakib Rad said:
Thanks for replying. I followed our steps (com.mkhirsnpiw.z.kkt was used instead of com.H3.nuhw6UY.GoCgl). But it again says the same thing, "Upgrade to full magisk to finish the setup. Download and install?". Clicking ok upgrades it again
Click to expand...
Click to collapse
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.

Didgeridoohan said:
Did you place the new current.apk file in the same directory and give it the proper permissions (same owner and permission 600)? I just tested and had no issues downgrading the hidden Manager to 285 this way.
Click to expand...
Click to collapse
yes with MiXplorer.
When Manager updated itself , i tried to update the magisk ( not the manager). But it bricked my phone as it won't start. i had to flash stock firmware via odin. It happened what i feared about. Now, i will try to patch boot img with new version.

UPDATE: I patched and flashed boot img using canary 290. after rebooting , this time there was not that Bug of rejecting SU automatically. Root was functional. But when it asked to do additional setups, it was stuck on setup operation forever and when i tried to hide manager, it showed "hiding magisk manager failed". so i uninstalled canary 290 and installed 7.5.1 (267) . This time additional setup was completed and rebooted automatically. But there was some problem with su access. so i uninstalled 7.5.1 (267) and installed canary 290. Root is now functional and it does not ask for additional setup anymore. (meaning setup was complete?). But still shows "hiding magisk manager failed" when try to hide manager. I don't know what is the problem . I was using canary 284 without any problem. PUBG mobile was runnig without problem. Now I am tired......

About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager

Didgeridoohan said:
About hiding the Manager failing:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_hide_the_Magisk_Manager
Click to expand...
Click to collapse
Disabling Play Protect Worked !!!! Thank you Sir :angel: