Just wanted to create a thread similar to the Pokémon Go one because i've seen the only one having problems with this app and magisk despite the John announncement made in September...
Anyway, back to the main topic, in this thread i would like to gather all users with some requirements:
- Fate GO istantly closes, opens the default mail app and prompts the "Error 61" in the mail, other errors have nothing to do with magisk.
- Latest version of Magisk Dev
- Magisk Hide enabled and Fate GO ticked in the list
- Magisk Manager hidden
- Check if other apps (Like GPay for example) find Magisk/Root or not
- Safetynet "full" passes
- No Xposed
- Running the uninstaller of magisk makes Fate GO working normally
- Always write: ROM, Kernel, Magisk Version, Fate GO version and region (NA, CN, JP ecc...)
Thanks in advance to everyone that will help with this problem or share their experiences or thoughts, and if someone else would like to test itself you can find the apk on APKPure if it's no present on play store.
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Sent from my Pixel using Tapatalk
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Chocobubba said:
Make sure USB debugging is disabled, then if that doesn't work, clear the data for the app
Click to expand...
Click to collapse
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Niiya said:
Hello, I'm sorry for you, but I'm the same, and the worst is that I recently installed magisk, just yesterday, because I thought it would work with Fate G / O but apparently I happen the same as you, it was supposed to be fixed, right?
By the way, just to complete other apps I can't find magisk.
-StockRom Android 6.
-Kernel 3.18.19+
-Last Magisk Dev
-Last ver JP and NA
Click to expand...
Click to collapse
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Killua96 said:
Debug usb has nothing to do with error 61, which is magisk, that's why I specified it in the list xD
Yep, it was supposed to bi fixed since September, but the majority of the players here and on reddit reported the opposite, I've tried anything suggested and to ask it many times in many threads and for now I'm stuck with a not-rooted OP6...
Btw I got it "barely working" with the app "Island" but I say "barely" because sometimes it didn't work.
Click to expand...
Click to collapse
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Niiya said:
I tried flashing the reddit hide zip and several more until I surrendered, after all I gave him delete without remembering to save the save code.
It's weird, because I installed magisk believing that go would work, if a bank app works because it wouldn't work fate GO?
It seems that I was wrong.
Click to expand...
Click to collapse
Btw my bank app doesn't work with and without magisk, anyway the problem is that FGO was advised as playable since September and it's not...
Hello, i get some problems like this. My device - Asus me302kl with Nitrogen os 8. I install magisk (canary), hide fate app, and rebuilt magisk with new package name. After killing process in app settings i can play, but after some time (i think when magisk has autolaunch) fate found magisk and i recieve error 61. After this I need restore and rebuild package again, for normal fgo launch.
Now i try something for stable result.
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Killua96 said:
This could be interesting: https://twitter.com/topjohnwu/status/1064941972375392257?s=19
Let's see if he can do something about it...
Click to expand...
Click to collapse
And in fact now magisk is not detected at all by FGO, finally...!
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Niiya said:
For a moment I got error 43 so I deactivated the USB debug, but then I went back to error 61, is it still possible that it is an error of my device?
The developer options are activated permanently because oem unlock is activated.
Click to expand...
Click to collapse
If you have added fgo to the magisk hidelist, and have hidden MagiskManager trough the option in the settings then you could try to use the ProcGate apk and see if the proc bug is the issue.
FGO works well now, no errors or anything. This is great because I use root regularly, but wasn't willing to let go of it.
:victory:
I have android 6, well I can always use an emulator.
Just tried this game and can't open just white screen and there some gmail option
-AEX N 7.1
-latest mgisk cannary
-3.10.108
-latest NA
I can play dragalia lost just fine with magisk hide,this game sure annoyingxD
Edit: Oookay its weird,I just reboot my device and it work like a charmxD
Niiya said:
I have android 6, well I can always use an emulator.
Click to expand...
Click to collapse
Check with procgate app if you have leaks, if there are unfortunately there aren't solutions atm on Android versions bellow nougat...
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
AsakuraVN said:
I can't seem to get it working. Keep getting error 61 & 60
Running on 7.1 LineageOS with latest canary build
Both Fate GO & MM are hidden
All safetynet checks passed
Freshly flashed ROM, no Xposed or anything
No leaks detected in Procgate
Running magisk uninstaller makes Fate GO working normally
Click to expand...
Click to collapse
What error code you have last? 61?
Try hide MM from framework+google apps
Lordische said:
What error code you have last? 61?
Try hide MM from framework+google apps
Click to expand...
Click to collapse
Already tried. Right now it's 60.
Guilhermex12 said:
Well looks like this topic is a bit dead. Is Fate GO still working with Magisk?
Click to expand...
Click to collapse
Yes. Poke GO and FGO work with Magisk - at least with 17.4 and 18.1. i played Fate a few days ago, no problem on Pie.
Related
At least 2 of my Apps refuse to start. One is my banking app and they do not offer any other way of interaction.
The problem is that the phone in fact is not rooted! It's just "OEM unlocked" to be prepared for root (which I need for E.g. titanium backup, but only maybe once a month).
Please give me a way out of this vicious circle!
I cannot remove the OEM unlock because it requires full wipe every time. Or is there a way?
Or what can I possibly tell the App Provider to improved their Code so that Oneplus phone state is being recognized (more) correctly?
Any help would be greatly appreciated.
Use Magisk I guess? Use it to hide root from that app.
Reeb_Lam said:
Use Magisk I guess? Use it to hide root from that app.
Click to expand...
Click to collapse
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
ako673de said:
In fact I already flashed an official image and still (with no zip installed via TWRP) I'm getting refusals from these apps.
So for sure some apps decide from something else then simply an installed "root" manager or the installed "su" binaries.
What else could they decide from? "OEM unlock" was my first guess (and it would also be the worst, because as far as I know it can't be "hidden" temporarily, or can it?), but maybe there are other settings. Does anybody know more?
Click to expand...
Click to collapse
You need to do some reading about Safetynet. If you're OEM unlocked you fail Verified Boot checks. Most custom Kernels include a bypass for this. Magisk alone should also work. I think you missed one important step:
Open Play Store Settings. Scroll down. It says 'Uncertified' at the bottom, right? Now install and set up Magisk. Go to system App Settings and clear Data and Cache for Play Store. Return to the Play Store Settings and scroll down. Now it should say 'Certified'. It might not be immediate, but it will happen. Now your Banking Apps work.
If you don't want, or have no luck with Magisk, simply flash a Custom Kernel that bypasses Verified Boot, and works with OOS.
Simple.
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
ako673de said:
Thank you. That was for sure a major part of the overall issue. Unfortunately it didn't yet fix it. I'm now certified in play store and magisk succeeds with both safety net checks (which however it also did before). And root is disabled in magisk. dm-verity does not show the warning during Boot and the Check itself should be disabled (I followed the recommendation in another Thread to Patch the Boot Image).
Anything else you can imagine?
Click to expand...
Click to collapse
Link to other Thread?
I don't know Magisk but are you hiding Root from your Banking App? Have you cleared Data and Cache for the Banking App since getting Certified?
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
ako673de said:
Any other idea?
Click to expand...
Click to collapse
Nope. If Play Store says Certified you should be good to go. I can only imagine it's a Magisk issue. Post screenshots of your config and let the Magisk experts pick through them. Maybe there's something not set up correctly.
ako673de said:
First my phone did not Boot any more after installing superSU. Fixed that by patching Boot.img (to disable dm-verity) according to this thread: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
Now data and cache of all (now) 3 affected Apps has been cleared and Magisk is configured to be hidden for them, but still no change.
However, in Magisk there is the "extended" option "AVB 2.0/keep dm-verity", which is unticked. I'm not sure, should I try to set it?
Any other idea?
Click to expand...
Click to collapse
Hide Magisk Manager. I had to do that to get my banking app to work.
Edit: you may need to reboot after hiding Magisk Manager and clear you banking app's data before it works.
Sent from my OnePlus3T using XDA Labs
Thank you, indeed that WORKED! Well, at least for 2 out of 3 Apps. I think I can tell which one: "HVB banking". Maybe could somebody cross-check this one on his/her phone?
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
ako673de said:
After firmware update to OOS 5.0.5 I now have the problem that my PlayStore can no longer be convinced in any way to show that it's certified. But interestingly my banking Apps work (currently really no root app installed). I even waited for one day because earlier in this thread somebody mentioned that it might take awhile. Is there anything special I need to care about under the new OS version?
Click to expand...
Click to collapse
Did you reflash custom kernel after update?
I'm not using any. What I did right after the update is to disable dm-verity (with a patched boot.img), like I did last time. But magisk is not yet re-installed because I wanted to see at least once the HypoVereinsbank App working, which it in fact does (different to last time when the phone was not rooted as well, and the store not certified!).
ako673de said:
But magisk is not yet re-installed
Click to expand...
Click to collapse
That's why... You can't pass the ctsProfile check if your bootloader is unlocked, and if you can't pass the ctsProfile check the Play Store won't be certified. You need Magisk for that...
Now I'm getting confused. The initial mail of this thread explains the situation as it was when I opened this thread:
--> Original ROM, no root, and banking apps didn't work <--
The advice to clear data of the PlayStore immediately brought the PlayStore back to "certified".
This is clearly in contrast to what you're saying now.
I can imagine only one reason: Maybe the older PlayStore had a bug and therefore was able to "certify" even with unlocked bootloader?
Sidenote: My main intention to do the firmware upgrade was that the "safety net checks" in Magisk suddenly stopped working one day (with the error message "invalid response", most probably you know what I'm talking about, I've read some comments from you on this issue). Therefore it's maybe really not too unlikely that Google has changed something very basic. Could you please confirm?
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
ako673de said:
Edit: Now magisk is back, version 16.7, and in fact PlayStore is back to "certified" AND now even the HypoVereinsbank App works. Just one thing remains: magisk safety net check still says "invalid response" (after it downloaded some "FOSS" code, which it didn't do last time, when it was still working).
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_The_response_is_invalid
Sorry, now comes a probably often asked question: do I need the safetynet check option in magisk for something real? Or do the alternative apps fulfill all possible needs? What are these needs? Isn't that exactly what the PlayStore does to determine "certified"?
After quite some months of absolutely no "root" problems with any of my apps, since today o2banking again doesn't work.
I tried to update Magisk, but after update of the Magisk manager app to v7.1.1(203) it reports that Magisk is not installed at all, and any update of Magisk itself resulted in just the same. So I reverted back to v6.1.0(165) and everything seems to be okay, except that o2banking doesn't work. SafetyNet is clean, Magisk is hidden for o2banking and Magisk manager is repacked.
Does anybody know what the problem might be? Especially with that new version of the manager app, but also with Magisk v19.0 which cannot be installed from v6.1.0 (max. is v18.1). Any ideas welcome! I'm now on OOS 5.0.8 by the way.
SOLVED it myself: As mentioned somewhere in the update FAQ of Magisk there was a bug in manager v6.1.0 that causes the updated v7.1.1 to co-exist with the old version if the old version has been re-packed. If anybody encounters the same problem, the solution is at the bottom of this page: https://www.didgeridoohan.com/magisk/ManagerIssues.
o2banking will then still not work. Update to v19.0 is mandatory. But that is no problem then any more...
probably your banking app identified oxygen os as custom rom and have root. 1 out of 3 banking app in my phone doesn't work with lineageos even though i already hide magisk, but when running oxygen os with magisk hide, and also hide magisk manager (turn it on in magisk manager setting) all 3 banking app work just fine. maybe try sending a message to bank app developer to add oxygen os as exception.
Did you notice my edit? It was a problem with magisk manager update and magisk main version. Now everything is back up and running.
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
evan5935 said:
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
Click to expand...
Click to collapse
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
white7561 said:
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
Click to expand...
Click to collapse
Dang, really? Thanks man!
evan5935 said:
Dang, really? Thanks man!
Click to expand...
Click to collapse
Yep!! Its working on mine ....
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Its not workin for me bro, i hide magisk manage, have no folders or files named makgisk, or even have magisk in the name, hide the root apps with magisk as well as the fortnite installer and app before i launch each of them. It just deosnt work for me :'(
Are you running in magisk core mode, with adb/root disabled as well?
And what about USB/ADB Debugging? Have you turned that off as well?
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Didgeridoohan said:
And what about USB/ADB Debugging? Have you turned that off as well?
Click to expand...
Click to collapse
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
evan5935 said:
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
Click to expand...
Click to collapse
Prob yeah ...
white7561 said:
Prob yeah ...
Click to expand...
Click to collapse
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
evan5935 said:
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
Click to expand...
Click to collapse
Yep. Also . No xposed . Since it fails the safety net [emoji4]. Well. Happy gaming!! [emoji4][emoji4][emoji4]
Working still Season 9 Magisk 19.1? Not I
Anybody still using this method? I get all the way to the drop then get kicked out "can't sync user profile"
Magisk is hidden in a random folder, installer and game both hidden. Tried with Developer settings off and also with them on. Rooted.
Even Google Pay works so I'm head scratching here if there is a system processes that is now needing hidden or what to play the newest Beta. All help appreciated.
I have the same problem. Google pay is working but fortnite not
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
Curious what was your setup? To have it work?
Pvt WhoOkid said:
Curious what was your setup? To have it work?
Click to expand...
Click to collapse
Stock OnePlus 7 pro with magisk and TWRP. Epic launcher and Fortnite both hidden in magisk hide. USB debugging turned off. No modules installed. Just using it for root. Worked fine until last night. Gpay and all other safety net apps work fine. It's just Fortnite. Logged in on a friend's Xbox and a really laggy ipad and could play on both so it's not my account - it's definitely the rooted phone and magisk no longer hides itself from Fortnite.
I'm really irritated with the whole thing because I was so close to finishing the season pass and now I can't play at all.
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
white7561 said:
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
Click to expand...
Click to collapse
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
I have pretty much the same setup as you. Do you happen to get lag here and there? During game play? I was able to get mine working again by renaming the folder for trwp as suggested.
Chuck_C said:
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Click to expand...
Click to collapse
With Tasker or Automate, you can set a trigger to automatically rename folder on start of Fortnite and rename back, after the game is closed.
Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...
h0l said:
Hi, my original plan was keeping my OP7 root-free because I need that banking app - which has an incredibly good root detection.
Long story short, a few days later and went back to my old habits... Magisk, Kernel, you name it. And the banking app stopped working again.
I do pass the safetynet test, have repackaged Magisk Manager. Google Pay is working like a charme. But Fidor bank seems to be better than Google, at least in this regard. I tried logging traffic using adguard, the app does not connect to anything, no dns requests as well.
Most of the times the app won't start at all, sometimes the first screen flashes for a very short period, and sometimes chrome opens with a webpage from the bank telling me my device is modified. How the **** do they know?
Maybe you guys may have a hint in what direction I could continue poking, because carrying a second phone just for banking is a little bit overkill...
Click to expand...
Click to collapse
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs
DarkSJ1998 said:
Did you clear data of the banking app after Repackaging Magisk & adding it to Magisk Hide? I assume you did it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
I did. And rebooted. And reinstalled. And combinations of those.
A short screenrecord of what is happening as soon as I try to open the app can be found here (youtube link)
I have the exact same Problem
Everything works: Netflix, other banking apps, etc.. Just Fidor. I do not really know how their detection works, but I assume it's not just a root detection.
The weird thing is, it worked flawlessly 2 years ago Now it's just annoying..
Waited a few versions oft Magisk now, however nothing changes.
You're not alone
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Same problem here ... since the new fidor version v3.14 is out, no way to getting it to work. Downgrade to 3.12 is futile, it forces the update to 3.14 immediately.
As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98
Thank you, the issue seems to have been addressed there. But as far as I can see, the canary version does not have the optional modules, correct? So I think, unfortunately I will have to wait for an adapted release of the regular magisk.
rpc75 said:
But as far as I can see, the canary version does not have the optional modules, correct?
Click to expand...
Click to collapse
I have no idea what that means... Magisk modules works just fine on the Canary releases.
Didgeridoohan said:
As an amendment to my post above (where you'll find pretty much all you need to hide from almost any app), I've successfully tested and hidden root from Fidor v3.14.0.1.
https://forum.xda-developers.com/showpost.php?p=79997227&postcount=98
Click to expand...
Click to collapse
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!
dagoban said:
Thanks for sharing!
I have successfully installed the canary Magisk, have Magisk hide enabled, safetynet pass etc.
All bank apps work after adding them to the hide list, for example trying "Kontist" w/o hide gave error, with hide it works.
However, Fidor (3.14.0.1) is still not working for me :/
The app stays open for 1-2 seconds on the canary build, quite a bit longer than on stable version (instant close), clean cache + clean app data, still no luck.
So Fidor must use another detection method that the other bank apps don't have.
Any advice would be greatly appreciated!
Click to expand...
Click to collapse
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.
alike03 said:
Similar Problem, my bank brought out a new app, that is detecting the root/custom rom somehow. The app closes and shows me security bull**** about root, jailbreak, custom roms. I don't know how everything should be hidden, SafetyNet checks out but this app can detect it. No idea how.
Click to expand...
Click to collapse
Check the link, one post before yours...
Didgeridoohan said:
Check the link, one post before yours...
Click to expand...
Click to collapse
Thanks, I was already going through that one.
Turns out the Banking app was detecting the Original Magisk Package.
Hiding Magisk Manager itself fixed my problem. Thanks for the link.
Didgeridoohan said:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Click to expand...
Click to collapse
Still did not get Fidor to work. Crashes after the initial first 2-3 seconds. If I uninstall Magisk it works again. Disabling modules, delete files from sd-card, etc. didn't change a thing.
This also seem not to be the problem, since it works after uninstalling Magisk.
Fidor is hidden from Magisk, Magisk is repacked with other name.
Mind giving specific instructions on what you did to make Fidor work on your device?
Thyrador said:
Mind giving specific instructions on what you did to make Fidor work on your device?
Click to expand...
Click to collapse
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...
Didgeridoohan said:
It's all right there in the link provided. I'm not doing anything that's not described there... Of course, there's a whole lot of things there that I didn't do.
Here's my setup:
Android Pie.
Magisk v19.4 (19307), with hidden Manager.
The app on the Hide list.
My internal storage is full of Magisk files and I never bother to disable any modules (all of the ones I have installed can be hidden without issue). I also have OEM Unlocking disabled, but that's just by chance and not something I've done because of an app detecting it...
Click to expand...
Click to collapse
So basically same setup. Still doesn't work with latest Fidor Release.
Thyrador said:
So basically same setup. Still doesn't work with latest Fidor Release.
Click to expand...
Click to collapse
When you say "basically", what's the difference?
Didgeridoohan said:
When you say "basically", what's the difference?
Click to expand...
Click to collapse
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.
Thyrador said:
That's the question. Even if I do a complete fresh install without anything else beside Magisk and Fidor: as soon as Magisk is running (hidden manager & Fidor, SafetyNet Pass and certified in PlayStore), Fidor stops working.
Click to expand...
Click to collapse
You're going to have to start digging deeper then...
I'm trying to use this app: play.google.com/store/apps/details?id=br.com.banrisul
I've added to the hiding list and enable core only mode, it still closes at startup after saying my phone is either root or running a modified system. I've tested with rootbeercheck and it doesn't detect root in any of its tests.
i.imgur.com/60Zs5IH.png
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
Didgeridoohan said:
No issues opening the app here... That means Magisk is perfectly capable of hiding from it, but you might have something else in your setup that triggers it.
Click to expand...
Click to collapse
but what exactly would trigger it? The link talks mostly about methods to hide magisk, I didn't find anything about what to do if magisk is working but the check fails. I've uninstalled titaniumbackup and rootbrowser. I've disable adb and developer options, I've deleted any folder or downloaded file related to magisk or those apps.
I'm running lineageos, would that be it? How would I go about it?
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Didgeridoohan said:
Could be any number of things... Your ROM might be one of them (more details about that?). It's pretty much impossible for me to do anything else but make educated guesses. The only thing I can say with relative certainty is that it shouldn't have anything to do with Magisk (since I can hide from the app just fine when testing).
You do pass SafetyNet, right? Could be that this is one of those apps that actually use SN.
Click to expand...
Click to collapse
It passes both checks.
I am running lineage OS 14.1 (Android 7.1.2) on a moto g4.
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Didgeridoohan said:
My main guess is that it's detecting something about your ROM. LOS is well known enough for apps to look for certain properties of it.
Click to expand...
Click to collapse
Yes, after searching around a bit more I found about why. I completely forgot that I had flashed supersu on my phone before flashing magisk. So I guess that's what the app was freaking out about. So I flashed a supersu removal and reflashed my ROM, now the app is working normally
Thanks for the help!
Same problem
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
hammohammo said:
Hello everyone
After the last update of my banking app and wallet too
Both apps stopped starting due tl root device detection
While it was working well yesterday
I just updat apps to the last version
I think these app's developers find a way to detect magisk
Of course im hiding and randomly renaming it
Click to expand...
Click to collapse
What version of the application do you want?
I have the latest version installed and it does not detect root
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
hycraig said:
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
Click to expand...
Click to collapse
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
vash_h said:
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Biggest_Noob said:
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
Click to expand...
Click to collapse
My safteynet passes fine on both my devices
Thanks
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
h4lli said:
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
Click to expand...
Click to collapse
thanks @h4lli i couldn't see sky go version 13.1.1 for uk
so i got Sky Go UK 12.4.14 from apkmirror and can confirm is working fine
yeah still doesnt work, latest sky go app 20, latest magisk, still detects, anyone able to reverse the sky app to see what methods its using?
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
beardymarrow said:
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
Click to expand...
Click to collapse
Yeah still can't get it working. Damn it.
Hast everyone a sollution for running the sky Go App on rooted phones?
Skygo doesnt Work... hast anyone a sollution?
eula1977 said:
Skygo doesnt Work... hast anyone a sollution?
Click to expand...
Click to collapse
Have you tried this? It worked for me
SkyGo app detected root!
Hi everyone i have a problema using SkyGo app on my device because It detects the root. I renamed magisk , used magisk Hide , tried magiskhide props config , tried to delete cache and re-install SkyGo app but nothing worked...any solution...
forum.xda-developers.com