Database Develop

Android Pay after root?

I'm trying to get Android Pay to work after unlocking. I've tried Root Cloak module on Xposed, which solved similar issues on rooted phones in the past, but no luck.
I keep getting the error message below.
Any suggestions?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Read the chroma thread for nexus 6
Sent from my Nexus 6 using Tapatalk

spider623 said:
Read the chroma thread for nexus 6
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Link?

Sorry 6p, just Google Chroma 6P xda
Sent from my Nexus 6 using Tapatalk

rlmesq said:
I'm trying to get Android Pay to work after unlocking. I've tried Root Cloak module on Xposed, which solved similar issues on rooted phones in the past, but no luck.
I keep getting the error message below.
Any suggestions?
Click to expand...
Click to collapse
Just go to SuperSU and disable supersu. Then go to settings, app and open Android pay in all app tap. Then erase cache and data. Then open android Pay and tray the setting again.
Sent from my SM-N915F using Tapatalk
---------- Post added at 03:51 PM ---------- Previous post was at 03:49 PM ----------
dominguezcarlosm said:
Just go to SuperSU and disable supersu. Then go to settings, app and open Android pay in all app tap. Then erase cache and data. Then open android Pay and tray the setting again.
Sent from my SM-N915F using Tapatalk
Click to expand...
Click to collapse
If you use xposed this app doesn't work.
Sent from my SM-N915F using Tapatalk

Follow the instructions at the end of this post: http://forum.xda-developers.com/showthread.php?p=64199915
Essentially you have to flash unSU.zip to remove the current super user files, and flash the systemless supersu zip.
EDIT: Make sure you take a backup of your current ROM in TWRP, because I don't believe the systemless root has been tested on the turbo yet. If you want to wait a couple hours, I am planning on trying this out myself it a little while.

jwort93 said:
Follow the instructions at the end of this post: http://forum.xda-developers.com/showthread.php?p=64199915
Essentially you have to flash unSU.zip to remove the current super user files, and flash the systemless supersu zip.
EDIT: Make sure you take a backup of your current ROM in TWRP, because I don't believe the systemless root has been tested on the turbo yet. If you want to wait a couple hours, I am planning on trying this out myself it a little while.
Click to expand...
Click to collapse
Systemless only work with SDK 23, it mean Android 6.0.
Sent from my SM-N9200 using Tapatalk

Its like Samsung saying that the system is modified. Payment doesn't work maybe because Google doesn't want to take liability for a modified rom doing something wrong.
Sent from my ONE E1003 using Tapatalk

Android pay won't work on any rom that is not CTS compliant. That means, Samsung, LG, OnePlus, Cyanogen OS, HTC, etc will work. Custom ROMs will not work.
You'll also need to disable root. I use SuperSU and just disable root when I need to use pay. Works just fine.

dasunsrule32 said:
Android pay won't work on any rom that is not CTS compliant. That means, Samsung, LG, OnePlus, Cyanogen OS, HTC, etc will work. Custom ROMs will not work.
You'll also need to disable root. I use SuperSU and just disable root when I need to use pay. Works just fine.
Click to expand...
Click to collapse
I guess it's hit and miss. I'm on stock, bootloader unlocked, and I've tried it by disabling root - even uninstalled SuperSU and cleaned the cache in TWRP. I figured it's TWRP or that it's unlocked.
Is Xposed installed too?

Device certification

Do you guys have uncertified in device certification from the playstore?
I never saw this on my previous nexus devices!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My bootloader is unlocked and i'm using stock OOS rooted with ElementalX kernel.

I'm all stock and my device is "Certified".

Means you are failing safetynet. Some apps won't even appear.
Sent from my Pixel using Tapatalk

milan187 said:
Means you are failing safetynet. Some apps won't even appear.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
So what's the cause?apps like?
And is there a solution?

smajlo said:
I'm all stock and my device is "Certified".
Click to expand...
Click to collapse
By stock you mean locked bootloader and unrooted?

Midomad said:
So what's the cause?
Or is there a solution?
Click to expand...
Click to collapse
Anything that breaks Safetynet. Most commonly root or even unlocked bootloader without a custom kernel (on some devices).
I don't have this device right now so I'm not sure if unlocked bootloader effects it but it does on Nexus/Pixel.
If it's root there are some ways to hide it possibly.
Sent from my Pixel using Tapatalk

milan187 said:
Anything that breaks Safetynet. Most commonly root or even unlocked bootloader without a custom kernel (on some devices).
I don't have this device right now so I'm not sure if unlocked bootloader effects it but it does on Nexus/Pixel.
If it's root there are some ways to hide it possibly.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Thanks,as you can see i'm rooted with unlocked bootloader, what ways can hide it?
With my N5X i didn't get that problem.

Midomad said:
Thanks,as you can see i'm rooted with unlocked bootloader what ways can hide it?
With my N5X i didn't get that problem.
Click to expand...
Click to collapse
Its new maybe less then a month since they started doing it with PlayStore.
I know on Nexus you can use magisk to hide root. I have not looked into details. You will have to research if it's possible on your device.
Unlocked bootloader is easy. All custom kernels have a patch to hide it.
Sent from my Pixel using Tapatalk

I'm on OOS 4.0.3, unlocked bootloader, rooted with SuperSU, Magisk installed and with a custom (Franco r12) kernel. Play store is stating that my device is uncertified as well.
My banking app closes itself whenever I launch it, which I'm assuming is because I tripped safetynet. Oddly enough, when I uninstalled and re-installed the banking app, it seems to work now. While I can still update and download free apps on Play Store, I can't seem to buy paid apps. Whenever I get to the payment window and click "Buy", the Play Store app closes itself.
I had all of the above modifications while I was on OOS 4.0.2 and I didn't notice any problems. Purchasing apps worked fine before updating. I'm also getting the DM-Verity message during boot now, which I didn't have before updating.

I'm uncertified too but my banking apps work tdbank and capital one apps... On oos 4.0.3 rooted with ElementalX

Had this for a few weeks already.
With Magisk and Magisk hide should make it show up as Certified.
If not, clear the Play Store's app data and it should fix it.

Spasticdroid said:
Had this for a few weeks already.
With Magisk and Magisk hide should make it show up as Certified.
If not, clear the Play Store's app data and it should fix it.
Click to expand...
Click to collapse
I'm using SuperSu as root!
Magisk is the only way?

Thread closed at OP's request.

[MODULE][Test-C01] ★ AlienoidMod ★ | Metamorphic framework.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Intro:
A framework for various mods working easily on cross-devices with different archs and roms.
Compatibility:
Android 5.0 - 7.1.2
Magisk v14 +
CPU Arch: arm, arm64, x86 and x86_64
NOTE!!! All thing are prototypes now and in very experimental condition, even this post can look like unsorted, I'll sort out all soon. Feel free to ask if you have any suggestions or questions.​
Upcoming Features:
*Various mods working easily on different devices.
*Anyone can create a magisk mod easily by using the framework.
*A mod's various task's can be done by the amf interface.
*I will give u the template or instruction how you have to create the mod using amf.
Currently defined functions:
getamf, getors, setors, audmod, overmind
more to come....
Downloads:
Follow the attachments...
Contributors
metaspook
Version Information
Status: Test
Test Version: C01
Release Date: 2017-09-17

Reserved
Reserved post.

Reserved2
Reserved post 2.

Definitely going to follow development of this. Looks very promising.
Sent from my LG Nexus 5X using XDA Labs

New test build "amf-test-C01.zip" uploaded ...

Reason unknown, no sound is coming from my phone ever since I flashed this and the viperfx. Even after uninstalling both there is still no sound. Galaxy S6 7.0 magisk 14

Newer Magisk beta update 14.1 seems to broke viperfx module.
It keep asking for install drivers... Reboot and no drivers installed...
Revert back to last stable 14.0 and everything back to work again...

L.F.B. said:
Newer Magisk beta update 14.1 seems to broke viperfx module.
It keep asking for install drivers... Reboot and no drivers installed...
Revert back to last stable 14.0 and everything back to work again...
Click to expand...
Click to collapse
Hope you will find in next release.

Yep. It was a magisk problem. 14.2 fix all modules. ?

Hi there, I was wondering if this works on Android 8.0? I would like to get Viper4Android or ViperFX on my Nexus 6P running 8.0.
If not, can anyone recommend a way to get V4A on my phone? Thx

Dionykn said:
Hi there, I was wondering if this works on Android 8.0? I would like to get Viper4Android or ViperFX on my Nexus 6P running 8.0.
If not, can anyone recommend a way to get V4A on my phone? Thx
Click to expand...
Click to collapse
Try install the magisk version that doesn't work on magisk 14 and install the materialized apk then when it says to install the driver from the app you do it and reboot after you enable everything you want. That's how I got it to work on my s6 using lineage os 15 Oreo 8

What does this do?

Shen Ron said:
Try install the magisk version that doesn't work on magisk 14 and install the materialized apk then when it says to install the driver from the app you do it and reboot after you enable everything you want. That's how I got it to work on my s6 using lineage os 15 Oreo 8
Click to expand...
Click to collapse
What do you mean by "magisk version that doesn't work on magisk 14"?

Dionykn said:
What do you mean by "magisk version that doesn't work on magisk 14"?
Click to expand...
Click to collapse
The one that wasn't updated to the latest template and only worked with magisk 13

Shen Ron said:
The one that wasn't updated to the latest template and only worked with magisk 13
Click to expand...
Click to collapse
Don't you mean "alienoidmod that doesn't work with magisk 14"?

Ask : V4A

Did anyone success install V4A on miui 10 and the drive is normal? i tried more than 10 times... not working on any method.....
edit : i got the answer now.
and working good.
MOD EDIT: REMOVED
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Here... V4A is perfectly working here. Im using the Magisk Module and the audio compatibility Patch

unrated87 said:
Here... V4A is perfectly working here. Im using the Magisk Module and the audio compatibility Patch
Click to expand...
Click to collapse
Can you describe the method please?

MOD EDIT: no redirect to outside group allowed - give answers here i have answer for your question, no need magisk module, no need audio compatibility Patch, just flash trough twrp, and done.

Eagledig said:
Can you describe the method please?
Click to expand...
Click to collapse
1. Install TWRP
2. Flash Magisk
3. Install the XDA Labs app
4. Search for Viper4Android and install it
5. Search for Selinux Switcher and install it
6. Open Selinux Switcher and select Permissive
7. Open Viper4Android and install the drivers ( choose 2.5.0.4 ) and give Magisk permission to it when asked to.
8. Reboot
9. Enter Selinux Switcher again and set back to Enforcing

unrated87 said:
Here... V4A is perfectly working here. Im using the Magisk Module and the audio compatibility Patch
Click to expand...
Click to collapse
I'm running magisk and viper module without a patch and its working well
Gesendet von meinem MI 8 mit Tapatalk

The Marionette said:
1. Install TWRP
2. Flash Magisk
3. Install the XDA Labs app
4. Search for Viper4Android and install it
5. Search for Selinux Switcher and install it
6. Open Selinux Switcher and select Permissive
7. Open Viper4Android and install the drivers ( choose 2.5.0.4 ) and give Magisk permission to it when asked to.
8. Reboot
9. Enter Selinux Switcher again and set back to Enforcing
Click to expand...
Click to collapse
Thanks !
But I can't found Viper4android in XDA labs app
and installation failed for Selinux switcher.

Eagledig said:
Thanks !
But I can't found Viper4android in XDA labs app
and installation failed for Selinux switcher.
Click to expand...
Click to collapse
http://lmgtfy.com/?q=xda+labs+viper4android
As for Selinux Switcher, you probably need to dig through the MIUi settings and disable a security restriction.

The Marionette said:
http://lmgtfy.com/?q=xda+labs+viper4android
As for Selinux Switcher, you probably need to dig through the MIUi settings and disable a security restriction.
Click to expand...
Click to collapse
Big thanks to you !!
V4A works perfectly !

darkwader18701 said:
I'm running magisk and viper module without a patch and its working well
Gesendet von meinem MI 8 mit Tapatalk
Click to expand...
Click to collapse
Can you link me up the right v4a module or tell me what is the right module in magisk list

the module is in magisk
marcel112 said:
Can you link me up the right v4a module or tell me what is the right module in magisk list
Click to expand...
Click to collapse
Gesendet von meinem MI 8 mit Tapatalk

I know but there are several v4a in magisk .. what is the correct one?
V1.4
V1.7
For magisk 15(I have 16.4)
For xhifi
?

I use this one here.

unrated87 said:
I use this one here.
Click to expand...
Click to collapse
Thanks, got it working .

Mobile Money App not working . Any solution?

Hi , there's an app which is not working on rooted devices ,but it does work on unrooted custom ROM, called Mpesa App , actually there's two apps by the same company , both of them don't work , basically used for mobile Money . It fails at the first screen saying device is locked.
Am running A11 , Magisk 22.1 and Magisk canary APK , safety net passes successfully
Steps done :
1.basic Magisk hide toggling on
2.Hidden the full package with random(setting name)
3.Deleted Magisk itself
3.Renamed TWRP folder
4.Used Riru + Riru unshare + Riru + XPrivacy
5.Used Riru momohider+ Riru unshare
6.Use isolation mode
7.Used island app
I guess I tried those will add if I remember it , yeah and still I couldn't pass the first screen , any assistance is appreciated .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link to apps :
1.My Safaricom
2.Mpesa

For the record, I had no issues hiding Magisk from either of those apps. Just added them to the Hide list and they were good to go... Magisk app repackaged with a random name, of course, and no TWRP directory, Titanium backup or other known directories or apps that are used to "detect" root. Other than that I use nothing special (no Xposed type frameworks installed, etc).
In other words, it's perfectly possible for Magisk to hide from those apps.

Didgeridoohan said:
For the record, I had no issues hiding Magisk from either of those apps. Just added them to the Hide list and they were good to go... Magisk app repackaged with a random name, of course, and no TWRP directory, Titanium backup or other known directories or apps that are used to "detect" root. Other than that I use nothing special (no Xposed type frameworks installed, etc).
In other words, it's perfectly possible for Magisk to hide from those apps.
Click to expand...
Click to collapse
Did you get to the sign in screen ? Wow am having issues still , and are you running custom ROM ?
Thanks

majorkid said:
Did you get to the sign in screen ? Wow am having issues still , and are you running custom ROM ?
Thanks
Click to expand...
Click to collapse
Before adding the apps to the Hide list I saw the same messages as in your screenshots. After adding them to the list I did not get those messages anymore...
OnePlus 3T, custom Android 9 ROM (ArrowOS).

Didgeridoohan said:
Before adding the apps to the Hide list I saw the same messages as in your screenshots. After adding them to the list I did not get those messages anymore...
OnePlus 3T, custom Android 9 ROM (ArrowOS)
Click to expand...
Click to collapse
Yeah I don't know what the problem is , I just flashed oneui rooted , and just added the app to magisk and it worked . I still have no idea why it doesn't work with rooted custom ROMs, any idea ?

Test this 2 app & :
1.My Safaricom - not working & not find fix
2.Mpesa - posible fix & works
But this app must Safari sim card.