Related
Hello there
I am running a custom ROM on my Galaxy S8 and it is rooted using Magisk rather than SuperSU. SnapChat works fine with Magisk as it does not detect the root, however I've tried everything with the Barclays Mobile App but I just get stuck on the first screen and nothing happens afterwards.
At first it used to ask me to grant it root permissions and of course I did, but it has never actually worked.
I am not completely sure, but I have a feeling it has to do with the fact that my device is rooted.
Can someone please shed some light on this? I really need to get this application working as it is important for me. Do I have to go back to completely stock in order to use this application?
Thanks!
yes, it doesn't work on rooted devices. One of the ways that it tries to detect root is by trying to get root, as it happened in you case. By granting it root access, you marked your phone as rooted, and disabled the app. In case you were wondering, it has many other ways to detect root. It used to work with magisk hide, but I tried just today, and it seems that they can detect it too, as I can't use it anymore. By the way, your phone is flagged as rooted, and you will either have to do a factory reset to get it working, or call Barclays, but I think that there is no way to get it working. If you find out how to get it to work, please share it.
TarekElsakka said:
Hello there
I am running a custom ROM on my Galaxy S8 and it is rooted using Magisk rather than SuperSU. SnapChat works fine with Magisk as it does not detect the root, however I've tried everything with the Barclays Mobile App but I just get stuck on the first screen and nothing happens afterwards.
At first it used to ask me to grant it root permissions and of course I did, but it has never actually worked.
I am not completely sure, but I have a feeling it has to do with the fact that my device is rooted.
Can someone please shed some light on this? I really need to get this application working as it is important for me. Do I have to go back to completely stock in order to use this application?
Thanks!
Click to expand...
Click to collapse
Barclays app worked for when I was using magisk v14. Since update magisk v.15 barclays app stop working. If you can try to install magisk v.14
P.s. I was using magisk v14 and somehow magisk updated itself to v.15
What's up everyone. Just got a Samsung gear S3 watch but am having a hard time installing the Samsung apps I need too since my phone is rooted.
I found a modded Samsung gear app that installed but I can't get the other apps I need installed.
Can anyone help or point me in the right direction??
Bump
Mine was also rooted but everything worked fine. Try installing the apps from apkmirror.com
-however on android P the pairing doesn't work as intended, at least not from scratch
bender_007 said:
Mine was also rooted but everything worked fine. Try installing the apps from apkmirror.com
-however on android P the pairing doesn't work as intended, at least not from scratch
Click to expand...
Click to collapse
I can get the main app to install but it's the plug-in app that isn't working. I've tried a few diff ones and they won't install. Which one did you use??
mpetruzz said:
I can get the main app to install but it's the plug-in app that isn't working. I've tried a few diff ones and they won't install. Which one did you use??
Click to expand...
Click to collapse
btw..there is magisk and magisk hide so you can actually install all the stuff
bender_007 said:
btw..there is magisk and magisk hide so you can actually install all the stuff
Click to expand...
Click to collapse
Gotcha. I thought I did cause I can watch Netflix which won't run unless you hide root.
I tried like 4 versions off of the apk site and none installed.
Not sure how I got here.
Yesterday, went to pay at a Grocery Story with Google Pay, got a message that said "You can no longer pay in stores with Google Pay." Magisk seemed okay, seemed like I was passing SafetyNet (tried two different apps, including Magisk's built-in checker). No big deal, paid the old-fashioned way.
Today, I decided since Magisk or Google Pay was going to be that way, I might as well update EMUI—I've put it off for a good six months or so, because everything was working fine. Now that it wasn't, why not do the whole shebang?
Update went smoothly. Now on B376 (I think).
Updated Magisk. Patched boot.img, all that.
Now, however, I'm getting this screen, and I think somewhere I must have flashed the wrong Magisk. I'm still rooted (Adaway works), but MagiskManager won't get past this screen.
Any ideas on how to do this properly so Magisk and MagiskManager are on the same page?
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Haluter said:
Hi Daina,
same problem here with a HTC U11. Unfortunately no ideas and no workaround yet.
---------- Post added at 03:22 PM ---------- Previous post was at 02:51 PM ----------
Hi Daina
I downloaded the new Magisk Release 18.1 from github.com and installed the ZIP File via TWRP. After a reboot everything works fine now.
TE]
Click to expand...
Click to collapse
Thanks for this.
Just downloaded Magisk 18.1.zip from Github. It's currently on my computer.
My question is... how do I install it at this point? I don't have TWRP on my Mate 9, since it's so finicky to use. Yesterday, after I updated EMUI, I installed Magisk Manager, and had it sort of install/do its thing. I assume it downloaded its own Magisk, though which version, I have no idea. I used the custom channel found here.
However, now that I'm retracing my steps, I just noticed the verbiage in @Wirmpolter's guide, that says
Latest Magisk Manager and magisk work now so no longer need to setup and flash the specific version found in the original post from topjhnwu.
Click to expand...
Click to collapse
So... no need to use the custom channel URL from Magisk Manager. Got it.
Any advice on how to proceed? Currently... I have Magisk and Magisk Manager installed. Magisk Manager is 7.0, but Magisk itself, I suspect, is not 18+.
If I had to lay it out, I might try:
Uninstall Magisk (uninstall.zip, or whatever it's called)
Reinstall Magisk Manager 7.0
Use @Wirmpolter's instructions, pulling, patching, and re-pushing boot image (again!) in fastboot.
Is there an easier way to do this? Just curious.
EDIT: Another quick question to the big bad XDA world out there: do I flash the Magisk uninstall zip in fastboot, as well?
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
daina said:
So I did it.
I uninstalled Magisk Manager 7.0, which didn't work with the version of Magisk I flashed yesterday.
Installed an older Manager just to bring up the interface.
From there, I uninstalled Magisk completely, using the Uninstall option from within the manager.
Then I followed @Wirmpolter 's guide, only getting stuck when my computer refused to see my phone in fastboot. I finally managed it, though, and now I have Magisk 18.1, with the Magisk Manager 7.0 interface.
Google Pay is still failing, though, even though I pass Safety Net.
Anybody have any clues why?
Click to expand...
Click to collapse
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
ante0 said:
Try using play services version 15.1.78 beta, others had this too but that version of play services fixed it (for some reason).
Click to expand...
Click to collapse
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
daina said:
Thanks. No luck. Obtained 15.1.78 beta from apkmirror, and installed. Tried it on the Coke machine at work, same screen.
Someone on reddit ended up wiping cache and data on Google Play Store and Google Play Services, but then they ended up having to set up their cards again in GPay. Do you think this is the way to go?
Was trying to avoid having to set up cards again, since one of my cards involves having to call the bank to get it authorized...
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/showpost.php?p=79029481&postcount=9
Its a temporary fix as well... But beats calling the bank I guess
Hi Daina,
after a short-lived success I ended with the same problems the next day. Afterwards I tried all suggestions from various forums but nothing worked.
After a short period of frustration I decided for a radical solution and installed a new OS on my HTC U11. (Lineage unofficial)
And... surprise! GPay works without any flaws.
I updated to the new OOS 11 via the Oxygen updater app and all is fine except safety net fails. I have an unlocked boot loader and coming from root, but I just wanted to try this out and don't care about having a rooted device at the moment, so I upgraded without doing anything else, but now safety net fails. And stuff like google pay doesn't work now.
Does anyone know how to fix safety net?
J3STUR said:
I updated to the new OOS 11 via the Oxygen updater app and all is fine except safety net fails. I have an unlocked boot loader and coming from root, but I just wanted to try this out and don't care about having a rooted device at the moment, so I upgraded without doing anything else, but now safety net fails. And stuff like google pay doesn't work now.
Does anyone know how to fix safety net?
Click to expand...
Click to collapse
yeah i can confirm having the same problem. I unrooted the phone and google pay only operates in rooted mode.
Unlocked bootloader always trips SafetyNet.
Go into Magisk settings and enable the "Magiskhide - Hide Magisk from various forms of detection" then reboot and try again.
Should show attached after that
djsubterrain said:
Go into Magisk settings and enable the "Magiskhide - Hide Magisk from various forms of detection" then reboot and try again.
Should show attached after that
Click to expand...
Click to collapse
I don't have that option in the settings. Do I have the wrong magisk version or something. I think it's the newest version.
J3STUR said:
I don't have that option in the settings. Do I have the wrong magisk version or something. I think it's the newest version.
Click to expand...
Click to collapse
I don't think you have root applied properly, this is what I see...
djsubterrain said:
I don't think you have root applied properly, this is what I see...
View attachment 5269509
Click to expand...
Click to collapse
on the main screen of magisk. tap the shield icon on bottom of screen. you should be able to find the magisk hide then.
MrSteelX said:
on the main screen of magisk. tap the shield icon on bottom of screen. you should be able to find the magisk hide then.
Click to expand...
Click to collapse
Um, why you telling me? Mine is working fine?
djsubterrain said:
I don't think you have root applied properly, this is what I see...
View attachment 5269509
Click to expand...
Click to collapse
No I don't have root. I just wanted to go back to stock, so I directly install the android 11 without doing anything. Do I need factory wipe to get it to back to normal?
J3STUR said:
No I don't have root. I just wanted to go back to stock, so I directly install the android 11 without doing anything. Do I need factory wipe to get it to back to normal?
Click to expand...
Click to collapse
Well, Magisk is for obtaining root, if you don't have root then why would you need to "hide" root that you haven't applied?
If you're asking about the bootloader then the only thing you could do is to lock it again, which will wipe your storage so make sure you back up
I'm on OB4 with lastest magisk canary without problems, try using it and enable magisk hide option and if problem persist enable magisk hide por Google play services and wipe playstore data.
Hi!
I have an issue and was wondering if anyone have a solution. Suddenly Google wallet stopped working, saying that my phone is not up to security standards. It worked fine until this Sunday.
I'm using beyondrom, magisk app (zygisk and hidden) with Universal safteynet fix v.2,4 and Shamiko v.0,6. I also have all Google services etc. in deny list.
Anyone have had the same issue and/or something to try to fix?
eddy92 said:
Hi!
I have an issue and was wondering if anyone have a solution. Suddenly Google wallet stopped working, saying that my phone is not up to security standards. It worked fine until this Sunday.
I'm using beyondrom, magisk app (zygisk and hidden) with Universal safteynet fix v.2,4 and Shamiko v.0,6. I also have all Google services etc. in deny list.
Anyone have had the same issue and/or something to try to fix?
Click to expand...
Click to collapse
What does Play Integrity Checker or TB Checker report for Play Integrity results?
V0latyle said:
What does Play Integrity Checker or TB Checker report for Play Integrity results?
Click to expand...
Click to collapse
Huh, actually only meets device and Basic Integrity, strong Integrity is red.
Any tips on what to do/check?
eddy92 said:
Huh, actually only meets device and Basic Integrity, strong Integrity is red.
Any tips on what to do/check?
Click to expand...
Click to collapse
Strong integrity will always be red on an unlocked bootloader. Basic and Device integrity are the only requirements, Wallet does not use Strong. If you don't already, enable DenyList on Wallet and GPay - make sure you expand and enable on all subprocesses. Then, clear Wallet data and reopen it.
I had this issue a few days ago and fixed it with this method.
V0latyle said:
Strong integrity will always be red on an unlocked bootloader. Basic and Device integrity are the only requirements, Wallet does not use Strong. If you don't already, enable DenyList on Wallet and GPay - make sure you expand and enable on all subprocesses. Then, clear Wallet data and reopen it.
I had this issue a few days ago and fixed it with this method.
Click to expand...
Click to collapse
I have tried this several times, even with installing the wallet app in between. Unfortunatley it does not work! I have no GPay app, just the Wallet one.
I have fixed several other apps with this method, but Wallet does not want to work with me
eddy92 said:
I have tried this several times, even with installing the wallet app in between. Unfortunatley it does not work! I have no GPay app, just the Wallet one.
I have fixed several other apps with this method, but Wallet does not want to work with me
Click to expand...
Click to collapse
If you're running the latest kdragon version of safteynet fix, try deleting the module and install the latest version of the safteynet fix by displax. I myself had problems sometime ago and this helped. Then clear everything again restart and it'll probably work.
erik2041999 said:
If you're running the latest kdragon version of safteynet fix, try deleting the module and install the latest version of the safteynet fix by displax. I myself had problems sometime ago and this helped. Then clear everything again restart and it'll probably work.
Click to expand...
Click to collapse
Hi, thanks for the tip. Sorry stupid question maybe, but where can i find Displax safteynet fix? When searching I can only find Kdrag0ns version. Even on Displax Github it seems to link to the Kndrag0n version.
EDIT: Sorry, nvm I found it! (Link if someone else is looking: https://github.com/Displax/safetynet-fix/releases)
Still does'nt work though
I just realised, with the latest beyondrom magisk got changed to magisk alpha, so you kinda have to go and re-hide the app and so on. Have you done that?
erik2041999 said:
I just realised, with the latest beyondrom magisk got changed to magisk alpha, so you kinda have to go and re-hide the app and so on. Have you done that?
Click to expand...
Click to collapse
I have not yet updated to BeyondROM 2.3, I am still on 2.2 BVL1 version (from december 22). I will update to version 2.3 when I can, then perhaps I can try these steps again. Meybe it can help.
I should not have to re-hide etc. since I didnt update, right?
Nope, sorry I thought you did. But that's probably the reason for why the wallet isn't working. In that case first update and go through all the steps, should work then. It's one of the reasons magisk got replaced by magisk alpha in the newest beyond rom version.
erik2041999 said:
Nope, sorry I thought you did. But that's probably the reason for why the wallet isn't working. In that case first update and go through all the steps, should work then. It's one of the reasons magisk got replaced by magisk alpha in the newest beyond rom version.
Click to expand...
Click to collapse
Excellent, I will try asap. Thanks for all help!!
eddy92 said:
I have not yet updated to BeyondROM 2.3, I am still on 2.2 BVL1 version (from december 22). I will update to version 2.3 when I can, then perhaps I can try these steps again. Meybe it can help.
I should not have to re-hide etc. since I didnt update, right?
Click to expand...
Click to collapse
If you're on a custom ROM you may need to use MHPC to spoof a valid device profile.
I had the same problem here, I managed to solve it by installing Magisk delta and Universal SafetyNet modded.