Develop Bugs

Super Mario Run not working

Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?

app is good. i got it on my op3 stock and it works fine. looks like its an rom related problem.

doesn't work on my OnePlus 2 with RR 7.1.1

sasanksai said:
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
Click to expand...
Click to collapse
had the same issue , turns out it's failing a safetynet issue .
install magisk SU to pass safetynet issue and it should work fine.

See my sig, works with that system.

pawanraju said:
had the same issue , turns out it's failing a safetynet issue .
install magisk SU to pass safetynet issue and it should work fine.
Click to expand...
Click to collapse
Yes did that too. My magisk passed safetynet also i tired hiding magisk for mario. Didn't help tho

sasanksai said:
Just downloaded the game not a fan tho, Wanted to try. I'm on RR 7.1.1 Unified builds and magisk enabled. The game seem to be force closing all the time. A red Nintendo screen splashes and fades away. I'm not t=sure the problem is with the ROM or app itself. I tried clearing cache,Rebooting and all.
Anyone facing the same issue?
Anyone knows how to fix?
Click to expand...
Click to collapse
Sam here

its a problem with supersu root, if you use Magisk (you can hide it inside official app) won't have problems. I can play to Pokemon GO and SM Run without problem using it
MasterJack1697 said:
Sam here
Click to expand...
Click to collapse
enter in Magisk app - Settings - Magisk Hide
enable it and enjoy the game

Spector_Prophet said:
its a problem with supersu root, if you use Magisk (you can hide it inside official app) won't have problems. I can play to Pokemon GO and SM Run without problem using it
enter in Magisk app - Settings - Magisk Hide
enable it and enjoy the game
Click to expand...
Click to collapse
Same with that, doesn't work..

I think it would be interesting to kow if ppl who say it fails to work use OxygenOS or something else. My configuration works for PKMN Go and Mario Run without ANY problems at all.

ManuBBXX said:
Same with that, doesn't work..
Click to expand...
Click to collapse
are you using custom rom? because some roms have root included and you manage it in developer options.
With Magisk configurated and included root turn off, you should play without problems

Spector_Prophet said:
are you using custom rom? because some roms have root included and you manage it in developer options.
With Magisk configurated and included root turn off, you should play without problems
Click to expand...
Click to collapse
I use latest BJRR RR from Eliminater, wich includes by default magisk
Rooted systemless with magisk, safetyCheck pass, magisk hide enabled !

ManuBBXX said:
I use latest BJRR RR from Eliminater, wich includes by default magisk
Rooted systemless with magisk, safetyCheck pass, magisk hide enabled !
Click to expand...
Click to collapse
ouch..... I haven't more ideas
hope someone can help you

How to install Magisk on RR 7.1.1?

Hi! I have a one plus one and I am running Lineage OS 14.1-20170130 (7.1.1) and I can't play aswell.
I get the red Nintendo splash screen and it closes.

Running latest lineage weekly with zenith EAS 004 kernel and magisk and no issues whatsoever, I was able to start up the game and make a profile and play without any craziness

Update the magisk to latest version11.6 ! It helped me....
Hope it helps you. Thanks!

Yep, just tried with magisk and it worked. I found it on this reddit just after my previous post. At the r/LineageOS subreddit (the name of the post is "Super Mario Run came out about minutes ago, but crashes on start (Kenzo)" ). (I can't post urls yet)

Doesn't work on latest RR with latest magisk, safetyCheck pass and hide too.
I was on my previous install with latest RR AND superSU
I dirty flashed the ROM to remove superSU and work root with magisk
Is dirty flash is enough to remove superSU ?

ManuBBXX said:
Same with that, doesn't work..
Click to expand...
Click to collapse
-Deleted-

Oneplus 5T with OxygenOS, TWRP and Magisk 17.1 SafetyNet fail after a few hours

I have a OnePlus 5T that passes fully the SafetyNet test, but after a few hours it gives false in ctsProfile and BasicIntegrity, I am with Android 8.1 OxygenOS 5.1.5 (I already tried with 5.1.4 doing a thorough cleanup between rom exchange and also unsuccessful ), I unlocked Bootloader and installed TWRP 3.2.3 Blu spark v9.85, then i flash Root Magisk 17.1 by twrp, Installed from a clean ROM and I've already tried with 17.2 and It's the same thing at the end, I have also tried to install Magisk 16.0 from a clean rom and then upgrade to 17.1 directly via Magisk Manager but it was the same, already activated the Magisk Hide in all necessary applications, I hid the Magisk Manager, I've tried flashing Petnoire's SafetyNet Spoofer and me too changed the device fingerprint by MagiskHide Props Config but nothing solved my initial problem, every time I restart the device it passes on the SafetyNet again but after a few hours it fails again, Now i tried to flash the module Universal SafetyNet Fix v3 beta1(MG v17 fix) by Magisk Manager, but Magisk Manager stopped opening even uninstalling the application and installing other versions, I tried more than once and the installation of this module always presents this problem even flashing by TWRP, and after a few hours too SafetyNet failed, Can inform me the latest version of OxygenOS for OnePlus 5T that passes on SafetyNet without any problem? Even though OxygenOS is perfect for me, I'm willing to change rom in the last case, because the most important thing for me is to go through SafetyNet to use the applications I need.

Try to disable "developer menu" in "settings", then reboot and check safetynet again.

Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...

anatoly1983 said:
Try to disable "developer menu" in "settings", then reboot and check safetynet again.
Click to expand...
Click to collapse
I tried to do this yesterday but the initial problem persisted, every time I restart the device it passes on the SafetyNet again but after a few hours or minutes it fails again.

yoye_cros said:
Try Magisk 17.2 and delete if you have the magisk folder (now it uses the Download folder). You can also try the latest OB (17). If it's not working, FYI I'm using the CNP rom (Pie) with Magisk 17.2 and SafetyNet is OK, so you can try it if you want...
Click to expand...
Click to collapse
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?

Mega_Monster_X said:
I had already deleted the Magisk Manager folder and as for this rom it is stable? Can you inform me the serious bugs?
Click to expand...
Click to collapse
Honestly, I didn't have found any bug. I tried crDroid but I wasn't really happy, and CNP is for my use very stable without bug. I don't know if Volte or VoWifi is working because I don't use this. Also, it's very easy to install compared to other Pie Roms. I just can advise you to try it.

Try a different play services apk. This was the case with me previously.

Seagorilla2 said:
Try a different play services apk. This was the case with me previously.
Click to expand...
Click to collapse
I've tried this but to no avail

With Magisk 16.0 everything went fine, the problem is the Magisk modules I used that are not compatible, but I'll search here to see if I find the modules I want for Magisk 16.0.

I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?

floborg said:
I have been running into this same problem for the last 2 months or so.
I am on OOS 5.1.4, with the official TWRP, and Magisk 18.
Has anyone had this problem and found a solution?
Click to expand...
Click to collapse
I have not found a solution yet, when I fail on SafetyNet I reboot the device and pass SafetyNet a few times for a short time and sometimes lasts several hours but then fails again , I'm using Magisk 18 in OOS Open Beta 20 Android 9.0

GPay Can tell root now???

FIX:
1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
2. Add Google Pay and Google Services Framework to Magisk Hide
3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)
Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??

mine is fine
try re flash your rom

i42o said:
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
Click to expand...
Click to collapse
Long thread and a lot of moving parts, so work backwards on the thread. Personally, I am just waiting until a final and formal fix is found on stable Magisk and up to date Play apps.
https://forum.xda-developers.com/app...ssion-t3906703

My experience with this issue is I run GPay, go back to Magisk, safetynet fails on both.. So I force close Magisk, clear cache and data.. reboot. Open Magisk back up, Safetynet passes.. Gpay sets up fine. Sometimes you have to do this several times and it's a real pain but it's always worked for me..

this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!

dipstik said:
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Click to expand...
Click to collapse
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?

jbarcus81 said:
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
Click to expand...
Click to collapse
Get a 2.83 build. Xda shortens links and you lose them on copy text

dipstik said:
Get a 2.83 build. Xda shortens links and you lose them on copy text
Click to expand...
Click to collapse
I know.. it's ridiculous, appreciate the clarification!

I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.

rob42ert said:
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
Click to expand...
Click to collapse
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.

This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5

TonikJDK said:
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
Click to expand...
Click to collapse
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.

sliding_billy said:
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
Click to expand...
Click to collapse
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.

TonikJDK said:
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
Click to expand...
Click to collapse
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.

sliding_billy said:
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
Click to expand...
Click to collapse
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.

Bogega said:
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Click to expand...
Click to collapse
And the doubt kicks back in, LOL. Luckily, I just carry a real card until this is formally solved (hopefully).

Bogega said:
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
Click to expand...
Click to collapse
Sadly this method only works for a limited time.
Overnight GPS updates to version 15 by its own self and GP stops working.
I'm not sure I'm ready to to this procedure daily just for Google pay. For the time being I'll use my card until Magisk developer finds solution to this problem.

Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.

yeah nothing worked for me even when I uninstalled magisk and tried the steps above on stock. Ended up factory resetting. but thats the last move to do

TonikJDK said:
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
Click to expand...
Click to collapse
Google Pay is a real asshole and doesn't let you know something is wrong until you actually tap to pay.
It's happened to me a couple of throughout my ownership of Pixels.

Stockish P2XL Magisk and Google Pay

I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions

fortillian said:
I was running Android 9 Aug?2018 update with a custom kernel and Magisk. A few weeks ago Google Pay stopped working and i read the long thread here about the Google Play store update and Magisk no longer hiding root. I dirty flashed an updated stock rom and removed the format (-w) switch. I stayed with the stock kernel. Re-rooted with update Magisk root and Magisk app. In Magisk i pass SafetyNet Check ctsProfile and basicIntegrity. When i try to use Google Pay I still get the error message that i cannot use GooglePay there. I am very close to just going completely stock with no root as I am not jacking with my phone as much as i did years ago, android is progressing nicely and plus many devs have moved on from the P2XL. I just really dont want to have to re setup my phone. Any thing else i can try to use GooglePay before i go back to stock?
P2XL Bootloader unlocked
Android: 9.0 3/5/19
Magisk V19.0 (19000)
Magisk Manager 7.1.1
Not running any Magisk Modules
Thanks for any help or suggestions
Click to expand...
Click to collapse
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.

CyberpodS2 said:
There is a lot of talk in many threads about this. There is a good tutorial or two around that do work but seemingly only temporarily then it breaks again. Seems Google would a way to detect stuff that is not patched yet. I am at work so I don't have much time to go searching but it should not be hard to find. It includes deleting a folder and reinstalling and hiding magisk.
Click to expand...
Click to collapse
Yea, I've been through that 106 page thread and a few others. Renamed folders, deleted folders, reinstalled apps, hid services in magisk hide. I was never a fan of NFC payment until I started using it lol.

Try safety patch module in Magisk to pass Safetynet

HueyT said:
Try safety patch module in Magisk to pass Safetynet
Click to expand...
Click to collapse
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.

fortillian said:
I appreciate the reply. installed this plugin. cleared cache/data for Google Pay and Deleted the GMS folder again. Reinstalled GPay, no joy
Trying to decide on checking out Android Q or Dirty Unicorn. I dont jack with my phone much anymore, may be worth it to checkout Q and lock it up for GPAY atleast for now.
Click to expand...
Click to collapse
I'm thinking the same

Workaround for Magisk + Bank apps

Hey guys.
I would like to ask you, if it's possible to use bank apps + root on this device?
I tried it yesterday several times and couldn't get it to work. On my previous phones if worked perfectly.
What I did:
- unlock OP7T
- root with self-made Magisk patched boot
- hide Magisk Manager itself
- hide the bank app
It worked even yesterday on my other phone, before I switched to 7T.
I'm wondering why it doesn't work on 7T and maybe there is some fix for it?

What happens when you try the bank apps? I've used several (US Bank, Chase, Discover, etc.), and haven't had any issues

It could be detecting another root app or even a folder associated with a root app (Pokemon Go does this with the Magisk Folder). Start digging through your storage to see if there's anything that might be root related.

Kollachi said:
Hey guys.
I would like to ask you, if it's possible to use bank apps + root on this device?
I tried it yesterday several times and couldn't get it to work. On my previous phones if worked perfectly.
What I did:
- unlock OP7T
- root with self-made Magisk patched boot
- hide Magisk Manager itself
- hide the bank app
It worked even yesterday on my other phone, before I switched to 7T.
I'm wondering why it doesn't work on 7T and maybe there is some fix for it?
Click to expand...
Click to collapse
Have you installed magisk with another package name (4th voice on settings)?

giacomowrc said:
Have you installed magisk with another package name (4th voice on settings)?
Click to expand...
Click to collapse
Yep did it.
MansonDroid said:
It could be detecting another root app or even a folder associated with a root app (Pokemon Go does this with the Magisk Folder). Start digging through your storage to see if there's anything that might be root related.
Click to expand...
Click to collapse
Nah. Seems to be the same as my other device.
adobrakic said:
What happens when you try the bank apps? I've used several (US Bank, Chase, Discover, etc.), and haven't had any issues
Click to expand...
Click to collapse
Could your try the app i used? Does it work for you?
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.pushtan

S-pushTan works fine with root, just tried.

Lupus77 said:
S-pushTan works fine with root, just tried.
Click to expand...
Click to collapse
Strange. Don't get it, why it's not working for me.

Did you try hiding them using Magisk Hide?

cucumbersmell said:
Did you try hiding them using Magisk Hide?
Click to expand...
Click to collapse
Yeah sure.

Try restoring Magisk Manager via Settings and hide Magisk Manager again.

Lupus77 said:
Try restoring Magisk Manager via Settings and hide Magisk Manager again.
Click to expand...
Click to collapse
Did that too. But something doesn't work correctly.
Rootchecker says I'm rooted and also magisk says installed. Also the apps have root rights in magisk. But root doesn't work lol.
I have completely uninstalled magisk and reflashed it again. Root works now. But magisk hide is broken. Maybe OxygenOS is the reason.

Kollachi said:
Did that too. But something doesn't work correctly.
Rootchecker says I'm rooted and also magisk says installed. Also the apps have root rights in magisk. But root doesn't work lol.
I have completely uninstalled magisk and reflashed it again. Root works now. But magisk hide is broken. Maybe OxygenOS is the reason.
Click to expand...
Click to collapse
Oxygen os cant be the reason when its working for everyone else....start everything again afresh. Something you are messing up...i would restore the phone with msmdownload tool to be sure everything is back to normal then start everythung again

v.konvict said:
Oxygen os cant be the reason when its working for everyone else....start everything again afresh. Something you are messing up...i would restore the phone with msmdownload tool to be sure everything is back to normal then start everythung again
Click to expand...
Click to collapse
Yep I thought the same to start with MSMTool.
I never used OxygenOS also on the other OnePlus devices. That's why I thought there is something wrong with it.
BTW which version of magisk do you guys use?

Here it works great. Have hide my bankapp in magisk, than repack magisk have give it the name "funny" now my bankapp works great. I use the latest Canary magisk