Related
So it looks like netflix is incompatible with the Tab 3...Is there a solution or do we need to wait for netflix to come out with an update?
Are you saying Netflix shows up as "not compatible with this device" in your Play Store? It was available in mine. Did you search in the Galaxy Apps store?
Are your rooted? Netflix stopped supporting rooted devices. You can still side load it though. Netflix isn't supported in all countries and if you have a foreign tablet that could also be the issue.
It works fine on my S3 in the US. If you're rooted, it won't install, or run if you sideload it. There are a few articles about that, and they mentioned at least one root hide.
Alternatively, you can root your tablet as described in https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359, but instead of SuperSU use Magisk. Be sure not to install the permissive kernel as it will break your Magisk SafetyNet status. Once Magisk is up and running (and green) you can install Netflix and other similar apps directly from Play Store. Hope this helps.
I'm having this same issue on a new tablet. It's never been rooted, but the Netflix app won't update. I can download the new apk from apkmirror, and everything runs just fine. I don't understand. But at least I got it working.
On Angler (Nexus 6p) I flashed the latest stock rom. (After a complete wipe) Afterwards I flashed TWRP and unzipped Magsik. Subsequently I did update to the latest version. After that I changed the packagename of Magsik manager. Furthermore I installed Xposed framework. Afterwards I enabled root hide for the TAN app:
https://play.google.com/store/apps/details?id=com.starfinanz.mobile.android.dkbpushtan&hl=en
This software is meant to give you the tan without using sms services.
Still, the app crashed right at the start without any error notification. Android Version is 8.1 and Magsik is v16. While I did the test, the bootloader was unlocked and TWRP was still the recovery. Can these two things affect the verification of the Banking app? I tried this several times ago in the past, but I was never to make this app running.
If anyone would be able to give helpful advice here, it would be very much appreciated.
Best,
scarline
I have heard that DKB Tan2Go does not work with newer Android versions like Oreo 8.1.x at all.
I can also confirm that. I tried it on a Sony cellphone. The cellphone was not rooted and with a completely new and 'clean' ROM. It was to no avail.
A friend has been forced to buy a chip reader. I am fortunate to be able to use normal TAN lists at the moment. If the DKB tries to exclude me from online banking, I will change the bank.
DKB Tan2Go seems to be one of the worst and most insecure apps ever. The reviews in Google PlayStore confirm this conclusion.
Maybe there will be a solution someday?
DKB TAN2go works with Magisk:
1. Install the TAN2go app (but don't open it)
2. Add the TAN2go app in Magsik Manager in the menu "Magisk Hide"
3. Reboot the phone (I don't know if this is necessary)
4. Open TAN2go, works fine.
**** DKB and this stupid security features which bring absoltuely no security.
That's exactly what I tried - without success. I read that it only worked with an old, obsolete version of Tan2Go. However, I could not find this version and I'm not sure if it still works at all. Did you have the latest version of Tan2Go from Google PlayStore? According to DKB, the recent Tan2Go does not work with devices that was once rooted or had a CustomROM. Even if you go back to stock the Root Counter changed and DKB Tan2Go will never work on this device. Unfortunately, I have to confirm that.
I am working on it to change the bank, because of that.
exaveal said:
DKB TAN2go works with Magisk:
**** DKB and this stupid security features which bring absoltuely no security.
Click to expand...
Click to collapse
Indeed!
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
I tried that to no avail. I heard once the root counter has a value other than 0, one can't go back. Probably it is also the Sony bootloader and it is different with other devices?
exaveal said:
Yes, I have installed the latests version of LineageOS, latest version von Magisk and the latests version of the TAN2go app.
Click to expand...
Click to collapse
I have a Xiomi Mi5 rooted with Magisk and Tan2go used to work for the last year or so. But yesterday I tried to make a transaction and BOOM! App crashed without an error message. Tried to use a newer Magisk, tried reinstalling the App, nothing helped.
The worst thing is that I do not know if some of my programs have a battery checker or a screen reader plugin that I am not aware of, or if Tan2Go suddenly detects my root. Regardless, crashing without an explanation is like the worst programming practice ever.
Since I do not need this kind of ****e in my life I will probably change Bank, I mean what good is an internet Bank if you cannot do transactions over your mobile device?
Well, willy-nilly I try to use the only other option from DKB: the German TAN Generator. Every other bank equips you with such a device, if they want you to use it. The DKB does not. Actually, I ordered the 3rd TAN Generator and fully paid for it. The first one drains the battery within days. The second one let me type in all the numbers and for no reason the TAN code does not show up on display.
These devices are very annoying anyway, because you have to type in a lot of numbers for every money transfer, the characters are very small (on the laptop) and you have to carry the TAN Generator + the DKB debitcard all the time. Of course this is less secure.
I would change the bank immediately, but want to keep the Visa credit card. I have higher limits on it. That's the only reason. As soon as I found an alternative bank in Europe, I will leave the DKB for good.
It dont worked with Lineage 14.1 but with 15.1 unoffical build on Samsung S4 together with latest Magisk .Rom from here
https://www.cyanogenmods.org/forums/topic/lineageos-15-1-for-galaxy-s4-lte-android-8-1-oreo/
Works for me
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
DKB already updated their app - they patched it
kyodhin said:
Just tried again. It hasn't been working for me in the past. When downloading & opening the app, I had the same problems.
Then I simply followed the above advice: downloading the app again, didn't open it, hide with Magisk, reboot and opened the app - worked well and was able to register for tan2go.
I am using Lineage 16.0 and Magisk v18.0
Click to expand...
Click to collapse
The app version from September (version 2.3.0) does work, the newer app version from 4.4.19 (version 2.4.0) does not...
Tested working combination: Magisk 18.0, Magisk Manager 6.1, DKB version 2.3.0
Can confirm that, working with magisk and 2.3.0. Not working anymore with 2.4.0.
I have another Tan app from another bank and with the new version it also stops working. Seems that magisk is now quite to popular and they working on better detection. Magisk hide is useless on the recent version of these tan apps.
That really sucks. No way to get 2.4.0 working. Hoping for a magisk fix. Are the magisk developer informed that there are problems with magisk hide? I think others will have similar problems too.
I successfully got 2.4 working again, after it got updated and refused to start.
Following the steps from this post made it work again (German):
https://www.android-hilfe.de/forum/...trotz-magisk.901517-page-2.html#post-11532359
I installed Magisk 19.0 (beta) but contrary to the above mentioned post I left my Magisk modules installed as they were before the update.
Both the Magisk modules as well as TAN2Go 2.4 are now working again.
I had to authenticate the new TAN2Go installation by adding it as a "new device" using SMS verification.
I was not able to get it to run with the above mentioned instuctions.
Device: Nexus 6P (angler), ROM: LineageOS 15.1-20190419, Magisk modules: MagiskHide Props Config (required for ctsProfile test), Busybox for Android NDK (required for MagiskHide Props Config).
DKB Tan2Go crashes immediately when started.
Same for me. The above instruction doesn't work.
Downgrade to 2.3.0
I experienced the same problem. Had to do an important transfer yesterday. And of course Tan2Go-2.4.0 crashed. I'm using Magisk v18.1.
Today I did a downgrade via Aptoide to 2.3.0 and had to register the smartphone again via SMS. This worked without any problems.
To avoid the update problem and keep with 2.3.0:
Start Titanium Backup
Select the DKB Tan2Go App
Long click on the App.
Connect with Google Play Store (forced)
Long click the App again.
Disconnect from Google Play Store
Hope it helps. I don't think there's much to change in the DKB Api. I'll use 2.3.0 until they block it via the API.
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
musv said:
If more people confirm the proposed solution with Magisk v19, I'll try it maybe.
Click to expand...
Click to collapse
I have the same issue. Hopefully it can be fixed via Magisk one day.
Worked with T2G 2.4, 19, 7.1.1
Walhalla said:
I got it working with v2.4.0, but don't know which step was the solution. Switching to the "Canary" channel of Magisk or hiding the Magisk Manager in the settings. I think the last one was the solution.
Can you guys try and give feedback?
Don't forget to uninstall and install the app before testing again.
Click to expand...
Click to collapse
Hi Walhalla,
Hi All
In Settings "General">"Hide" via other apk name it worked for me. V19.0, v7.1.1, Tan2Go 2.4
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
nola mike said:
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
Click to expand...
Click to collapse
That's not an issue with Pay. If Magisk was being blocked by root/unlocked bootloader, you would get a message when you first fire up Pay that your phone can't be verified so "Google Pay can't run on this device".
Have you contacted your bank to make sure they support it? If it's not being verified with your bank, sounds like you need to call them. For the last few years, my bank didn't. It wasn't until this past year that they actually allowed it.
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
nola mike said:
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
Click to expand...
Click to collapse
Well that's weird. Glad it's working though! :good:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Redmi 4 using Tapatalk
Yes and No
cneeli78 said:
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
Sent from my Redmi 4 using Tapatalk
Click to expand...
Click to collapse
Phone permissions have nothing to do with root features, I didn't exactly understand what do you mean by reuse root features but I don't recall any root solution app or framework asking for Phone Permission. If you are asking about granting phone permission to Google Play Services after Google Pay registration, you should do it, it's not recommended to deny phone permission to Google Play Services. And once you hide Magisk you don't need to change it's state as Magisk will continue to work as expected whether it's hidden or not.
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
Yes it's working
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
thanks.its working
You are welcome
Arokia said:
Yes it's working
Click to expand...
Click to collapse
Karthik Arun said:
thanks.its working
Click to expand...
Click to collapse
There is a thanks button you can press if I could help you
JackFrost said:
There is a thanks button you can press if I could help you
Click to expand...
Click to collapse
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
raguilera510 said:
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
Click to expand...
Click to collapse
Did you by any chance remove phone permission from Google Pay app? You need to turn off telephone permission from Google Play Services and Google Play Store. Google Pay app needs phone permission to verify the phone number, don't turn off phone permission from Pay, do it for only play store and play services. Hope that helped.
Does not work
Once I renable telephone permission for Google Play Services, googlepay does not work anymore. Asks me to register and then I cannot register as I dont pass the security test. I am on lineage os 15.1
Non rooted lineageOS
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
kekekelasomot said:
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
Click to expand...
Click to collapse
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
ChazzMatt said:
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
Click to expand...
Click to collapse
Thank you. Just flash magisk and hide google pay using it. From what i under stand is i have root access+ unlocked bootloader+ google pay functionalities. And the reason not to root is just because i want the feel of stock android+some nice modification
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
AsItLies said:
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
Click to expand...
Click to collapse
Thank you. That's all I had to do to get it working for me.
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Forsh said:
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Click to expand...
Click to collapse
Use Magisk v19. I believe it's a beta at the moment
A13 stock. Magisk 25203. PS Remote Play app 5.5, and hidden in the Magisk deny list, like other apps.
Other typical root detecting apps foiled, but not this one. Hiding the Magisk manager itself didn't help.
Suggestions?
Assuming you're on the stock ROM, else you might need to use MagiskHide Props Config. Try turning on Zygisk and adding Displax's version of USNF and Shamiko (note: Shamiko is a closed-source root hider, so your call if you trust it). Keep in mind that if you use Shamiko, then the "enforce deny list" switch needs to be off. Shamiko reads from the list and handles it instead (so you do still need to have Google Play Services and PS Remote Play in the deny list). So far I haven't had anything detect root with this setup as long as it's in my deny list, though I don't have a PlayStation so I can't test it with this specifically.
I am on A13 stock. I'll look into this. FWIW, one doesn't need a PlayStation to see the app PS Remote App fail the root check, which is upon opening it, resulting in error 88001003
PS Remote Play - Apps on Google Play
Access your PS5 or PS4 wherever you go.
play.google.com
Interesting, it's happening the moment you open the app? I don't have a Playstation account, but I can open the app and get in far enough to see the account login screen with no error. That's on my system with the above utilities installed as well as Magisk and LSposed, running the Android 13 QPR1 beta. If you set all that up and it's still happening, try clearing the PS Remote Play app's data, too.
Jaitsu said:
Interesting, it's happening the moment you open the app?
Click to expand...
Click to collapse
Yes. It may be using some data from the general PS App to auto-login, but it appears as instantaneous error to me, even after full storage/cache wipe and force close.
I just updated USNF, and installed the MOD version on top of that as you suggested, still no go. Disney+, Nintendo, other apps that check still work. Play Store certified, pass YASNAC.
Haven't tried the Shamiko thing yet
Are you hiding the Magisk app itself?
I'm using Canary manager, btw
deusfaux said:
Yes. It may be using some data from the general PS App to auto-login, but it appears as instantaneous error to me, even after full storage/cache wipe and force close.
I just updated USNF, and installed the MOD version on top of that as you suggested, still no go. Disney+, Nintendo, other apps that check still work. Play Store certified, pass YASNAC.
Haven't tried the Shamiko thing yet
Are you hiding the Magisk app itself?
I'm using Canary manager, btw
Click to expand...
Click to collapse
I am hiding the Magisk app itself, with the default "Settings" name. Normal release (25.2/25200) of Magisk. Do you have any other root-related apps the PS Remote Play app might be looking for? (Though I myself have Fox's Magisk Module Manager, LP, the TWRP app, and Franco Kernel Manager installed on my phone and they don't seem to be setting it off.)
I'd suggest turning off USB debugging. I had similar issue with some of my banking and other apps and tried every possible solution but didn't work. Finally I read somewhere to turn off USB debugging and Eureka!!
I've narrowed it to something the recent app version 5.5 is doing
Versions 5.0 and earlier have no problems loading.
My USB debugging is/was off.
It must be looking at / for some other app I have installed, which is really annoying to troubleshoot
Hello,
As you said, I downgraded the app to the version 5.0 ans now I can login
But I can't associate the playstation
It ask me to upgrade to the last version and if i refuse, the association failes.
Do you have the same problem ?
Thx
twingo_man said:
Hello,
As you said, I downgraded the app to the version 5.0 ans now I can login
But I can't associate the playstation
It ask me to upgrade to the last version and if i refuse, the association failes.
Do you have the same problem ?
Thx
Click to expand...
Click to collapse
Ver 5.01 asked me if I wanted to update but i could choose 'later' and successfully connect to my PS5
i choose later but I can't connect to my ps5
i will try to put it on wifi...
twingo_man said:
i choose later but I can't connect to my ps5
i will try to put it on wifi...
Click to expand...
Click to collapse
We should also try to determine what exactly latest version is detecting and preventing app from working
My question is not directly tied to Pixel 6, but since I have that one, I will post it here.
After I unlocked bootloader, I cannot find Revolut in my Play store. After I somehow managed to find it, it says that I cannot install it on that device.
Is there a way to hide the fact that bootloader is unlocked or any other way which will let me install it?
Try rooting and see if Magisk's denylist and the Universal Safetynet Fix module help. But simply locking the bootloader is about the only way for apps that detect the bootloader to work.
Tried both but didnt help.
My device is rooted, my denylist has the appropriate Google apps (Wallet, GPay) selected, and the USNF is installed. Something else is blocking you. I not only see the app in my Play Store, I installed it and ran it without issue.
Take a look at this guide, particularly Part II step 5 ("Root/Reroot with Magisk and pass SafetyNet"). You don't need Magisk Canary, but do follow the rest, particularly where it mentions "Get Device Certified". Your device may have lost certification status, and this will bring it back. You may also need Shamiko, it hides Magisk/root from some things that still manage to detect it, but there's a little controversy around that with it being closed-source.
edit: should mention, with this arrangement I am personally able to see Revolut in the Play Store as well.
Unfortunately I rooted my device, and I'm NOT able to see the Revolut app in the play store.
I have enabled SafetyNet, have hide Magisk and gave permissions to the apps, installed the systemless hosts module, and still nothing.
When I download it from apk, still not being able to start it, or it bring me to an error at some point..
Any ideas?
teddysx3 said:
Unfortunately I rooted my device, and I'm NOT able to see the Revolut app in the play store.
I have enabled SafetyNet, have hide Magisk and gave permissions to the apps, installed the systemless hosts module, and still nothing.
When I download it from apk, still not being able to start it, or it bring me to an error at some point..
Any ideas?
Click to expand...
Click to collapse
Make sure you have Magisk's denylist enabled, and the most current version of the Universal Safetynet Fix module as well. Revolut, as mentioned upthread, appears in my Play Store and was able to run without a problem.
I'm also rooted and bootloader unlocked and revolut is working fine for me. Maybe you're not running the correct universal safety net fix.
If you can't resolve you can try Aurora store from f-droid. I use it for unsupported app in my country, so when playstore says tha the app is not supported in Croatia i use Aurora to donwload it. Working perfect.
I have root and i am using all banking apps, gpay with no problems. Also Revolut app
So I think I have managed to understand why the revolute app is not showing up in the store.
I think it's because the bootloader is unlocked, ever since I have unlocked it, the app is "not visible in the country you are in" that's the message from the play store.
I have managed to download the apk manually, CLEARED STORAGE INSIDE APP VERY IMPORTANT, hide magisk, enabled deny list, I pass all safety net and cvt profile and the app is now working.
teddysx3 said:
So I think I have managed to understand why the revolute app is not showing up in the store.
I think it's because the bootloader is unlocked, ever since I have unlocked it, the app is "not visible in the country you are in" that's the message from the play store.
I have managed to download the apk manually, CLEARED STORAGE INSIDE APP VERY IMPORTANT, hide magisk, enabled deny list, I pass all safety net and cvt profile and the app is now working.
Click to expand...
Click to collapse
Just to point out your issue must be a country restriction. My bootloader is unlocked.
Strephon Alkhalikoi said:
Just to point out your issue must be a country restriction. My bootloader is unlocked.
Click to expand...
Click to collapse
Before I rooted my phone, I had no problem with downloading the app from the play store...
teddysx3 said:
Before I rooted my phone, I had no problem with downloading the app from the play store...
Click to expand...
Click to collapse
And I have no problem downloading it now, so something in your setup differs from mine.
Strephon Alkhalikoi said:
And I have no problem downloading it now, so something in your setup differs from mine.
Click to expand...
Click to collapse
Wow, now all of the sudden I'm able to see it, I can even update it to a new version. Something very strange is happening, which I cannot understand, anyway I can see it...
Your problem was probably that your device was not certified.
PlayStore -> Settings: there shows that your device is certified and was probably missing before.
Cheers
Tom
I am unable to see the app on my playstore.
Using prerooted rom with safety net passing too. Google play store is certified too
With Android 13, Revolut now demands that the app is installed through the Paly store and Huawei store.
borisSweden said:
With Android 13, Revolut now demands that the app is installed through the Paly store and Huawei store.
Click to expand...
Click to collapse
Does this mean that Revolut won't work on Android 13 and a rooted phone?