Develop Bugs

Will android pay work if I'm un-encrypted but not rooted?

Has anyone tried following the steps from this video https://www.youtube.com/watch?v=mUq1xdJ-7-E
but stopping before flashing the superSU? Will android pay work after a reboot?

As long as you are using the stock ROM and not rooted, I don't think it will be a problem.
I followed that guide and even flashed superSU, but when I realized Android pay won't work with root, I unrooted. I was then able to add my cards in Android pay. Hopefully purchases go through fine, no reason they wouldn't as long as you aren't rooted or modified the stock ROM.
Sent from my Nexus 5X using Tapatalk

thesoldier said:
As long as you are using the stock ROM and not rooted, I don't think it will be a problem.
I followed that guide and even flashed superSU, but when I realized Android pay won't work with root, I unrooted. I was then able to add my cards in Android pay. Hopefully purchases go through fine, no reason they wouldn't as long as you aren't rooted or modified the stock ROM.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Let us know if it works! I want to unencrypt but I don't want to lose any functionality and I don't mind being unrooted for now.

nvertigo said:
Let us know if it works! I want to unencrypt but I don't want to lose any functionality and I don't mind being unrooted for now.
Click to expand...
Click to collapse
Yep works fine. Unrooted last week and tried today and it worked.
{
"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"
}
Sent from my Nexus 5X using Tapatalk

thesoldier said:
Yep works fine. Unrooted last week and tried today and it worked.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
hi thesoldier,
Does Android Pay still work after a reboot? Somehow I read somewhere on forum it doesn't work after reboot.
And is your recovery TWRP?
Do you notice any performance increase when taking multiple pictures after decryption?
Thanks,
Jack

ubcjack said:
hi thesoldier,
Does Android Pay still work after a reboot? Somehow I read somewhere on forum it doesn't work after reboot.
And is your recovery TWRP?
Do you notice any performance increase when taking multiple pictures after decryption?
Thanks,
Jack
Click to expand...
Click to collapse
I'm also curious about the picture speed without encryption.

Ajfink said:
I'm also curious about the picture speed without encryption.
Click to expand...
Click to collapse
Since my last post I've unencrypted my phone (not rooted).
Android pay works, even after reboot. Performance increase is huge, especially the camera.

nvertigo said:
Since my last post I've unencrypted my phone (not rooted).
Android pay works, even after reboot. Performance increase is huge, especially the camera.
Click to expand...
Click to collapse
Can someone please point me to a guide or provide some direction as to how one unencrypts without rooting? The majority of guides here are about rooting which I am not interested in. In fact, I thought I had to root to unencrypt. Apparently not, based on the above comment.
Thanks,
Derek

Just follow the video ^^ to unlock the bootloader, install TWRP and format data. After the format the encryption is gone. Then just do not flash SuperSU if you do not want root.

berndblb said:
Just follow the video ^^ to unlock the bootloader, install TWRP and format data. After the format the encryption is gone. Then just do not flash SuperSU if you do not want root.
Click to expand...
Click to collapse
i am using Chroma 11-30 on my nexus 5X
can i backup my data, then go to TWRP and format data, then I get a decrypted rom?
someone said I need flashing a force decrypt kernel.. i am confused.

Samsung Pay Help

Great Minds of XDA ...I need a bit of help.
I recently switched to the OnePlus 5T and I am having trouble getting Samsung Pay to work on my Gear S3.
I have everything installed but when I launch Samsung Pay I get an error message that it doesn't support rooted devices.
I have rooted with Magisk and I am on stock OOS 4.7.4 . I also have set Magisk to Hide root on all the Samsung Gear apps/plugin's.
Thanks in advance.

bump

If you use the apk from apkmirror it will let you set up the card so long as you don't update it. I'm not sure how long you can put off updates, but it's at least a start:
https://forums.oneplus.net/threads/samsung-pay-with-s3-on-5t.692652/
https://www.apkmirror.com/apk/samsu...g-pay-for-gear-1-5-6306-android-apk-download/
I have the Gear S3 on this phone too, but I've never used Samsung pay. Mine doesn't mention root though, it just says there's some security issue with my device (on the latest update.

shadeau said:
If you use the apk from apkmirror it will let you set up the card so long as you don't update it. I'm not sure how long you can put off updates, but it's at least a start:
https://forums.oneplus.net/threads/samsung-pay-with-s3-on-5t.692652/
https://www.apkmirror.com/apk/samsu...g-pay-for-gear-1-5-6306-android-apk-download/
I have the Gear S3 on this phone too, but I've never used Samsung pay. Mine doesn't mention root though, it just says there's some security issue with my device (on the latest update.
Click to expand...
Click to collapse
Thanks for the assistance. This gets me a bit further along. Now I can see the app in the Gear Manager app but unfortunately I am getting a different error.
{
"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"
}
Sent from my ONEPLUS A5010 using Tapatalk

Ok I have a gear s3 and using samsung pay
I'm on open beta 1 but also when I was on 4.7.6. It also worked.
I installed the apk from apk mirror. After this make sure u have the latest magisk. 15.3 magisk hide everything with the name samsung in it.
Also make sure u are passing safety net and don't have mods like xposed.
Btw I cannot see samsung pay in gear manager. Make sure u install the gear plugin version and it will install as a service not a app. So download a service launcher like this (https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut )
To make it an app
And it should work.

Here's what mine looks like

millerd79 said:
Thanks for the assistance. This gets me a bit further along. Now I can see the app in the Gear Manager app but unfortunately I am getting a different error.
Click to expand...
Click to collapse
Yeah, that's the same error I get. I'm curious if it's related to root or if there's some error contacting the server
---------- Post added at 04:49 PM ---------- Previous post was at 03:56 PM ----------
Jamie_oppo said:
Here's what mine looks like
Click to expand...
Click to collapse
That's the version that I linked to, but my phone says there's an update available and Samsung Pay will not work after the update. I can see the plugin in my gear app both before and after the update.

Well I see this a lot too.

I'm getting the same error now. Seems to be a knox error I think. I restored a backup of the older version .
You's find a workaround?

New Pixel XL owner, root help.

Have a decent understanding of how to unlock/root/xda, just want to make sure, so any help would be appreciated.
Still on 7.1.1, (Google edition? Bought on eBay and not really sure because oem unlock is greyed out, no Verizon apps though) wondering best way to get to android O/P with the bootloader unlocked. Should I OTA then try the Verizon unlock method? Or try the unlock method on 7.1.1 then flash a android O/P rom/modem/baseband etc? Got some reading to do....
Any other tips would be appreciated as well, thanks for your time.
{
"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"
}

So if your Button is greyed out... It's a Verizon variant.
https://www.facebook.com/IsMail.AmZdak reach out to that guy and donate what ever you can and ask if he can bootloader unlock your phone. it doesn't matter what version of Android you're on.
Once he unlock your bootloader proceed to downloading developer preview 4 and run flash all command.
Once it has finished flashing Android p the phone will then reboot let it get to the main screen and then reboot the phone and put into bootloader mode.
Download TW RP image and run Fastboot boot ( twrp image ) and wait for it to boot twrp. When you're computer reads the phone, drag and drop twrp installer into phone and the install. Reboot to recovery >> flash magisk >> boot up

You can use the Verizon method on 7.1.1 or newer as far as I know.

lafester said:
You can use the Verizon method on 7.1.1 or newer as far as I know.
Click to expand...
Click to collapse
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....

lordodin912 said:
So even though there are no vzw apps, bootanimation or any vzw stuff, this phone still a Verizon one? Weird....
Click to expand...
Click to collapse
Are you on Verizon? The apps only load with their sim.

lafester said:
Are you on Verizon? The apps only load with their sim.
Click to expand...
Click to collapse
Yes on Verizon, still no apps, rebooted multiple times and updated all playstore apps......no vzw stuff anywhere (not complaining, ha) just seems odd.
Is it better to OTA update to 8 then unlock/root, or is there another way (flash rom/modem...etc over 7.1.1, might not play well with bootloader though, jw).
Thanks.

Screens for proof....

Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
lordodin912 said:
Screens for proof....
Click to expand...
Click to collapse

lafester said:
Well im not on vzw but have a vzw pixel. My fi app downloaded when I put in the sim. Figured vzw would be the same.
Click to expand...
Click to collapse
Gotcha.
Edit: CID getter shows rom.boot.cid:[VZW_001], also checked verizon account, shows up as Pixel XL, not "non vzw device" which someone said it should say if it's google edition.
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Edit: Got root/twrp, no problems.
Thanks again.

lordodin912 said:
Ugh, any real difference between the Google edition vs VzW (except, ya know, the bleeping bootloader unlock)?
Click to expand...
Click to collapse
Not sure if this was answered already, but no. The bootloader being locked is the only difference.

Device is not certified

So apparently there has been an update and all my devices are now showing up as uncertified in the Play store. Anyone seen a new work around for this while running custom ROMs?
On the bright side it seems devices that you side load apps too, still get updates for the moment.

Stock OOS 5.1.4 UBL is also uncertified :|
Anyone else have this issue on Stock OOS with unlocked BL??
I've never seen my device be certified since I began using this phone. Is it normal for UBL phones to be uncertified even if they aren't rooted?

TechieTwinToes said:
Anyone else have this issue on Stock OOS with unlocked BL??
I've never seen my device be certified since I began using this phone. Is it normal for UBL phones to be uncertified even if they aren't rooted?
Click to expand...
Click to collapse
Mine is certified with unlocked bootloader and root (on latest openbeta)
{
"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"
}
Sent from my ONEPLUS A5010 using Tapatalk

alessandro_xda said:
Mine is certified with unlocked bootloader and root (on latest openbeta)
Click to expand...
Click to collapse
Hey alessandro,
Does disabling Play Protect have any role in this? I keep it disabled because I side-load many apps.

OhioYJ said:
So apparently there has been an update and all my devices are now showing up as uncertified in the Play store. Anyone seen a new work around for this while running custom ROMs?
On the bright side it seems devices that you side load apps too, still get updates for the moment.
Click to expand...
Click to collapse
Sorry, your account has been flagged for piracy, so you'll have to reflash every 7 days else your account won't give up updates.

killier2653 said:
Sorry, your account has been flagged for piracy, so you'll have to reflash every 7 days else your account won't give up updates.
Click to expand...
Click to collapse
That's not what it means. Custom ROMs, unlocked boot loaders, rooted devices, etc, can trigger this. Generally custom kernels or Magisk would prevent this. However not anymore . Right now I'm seeing it across 4 accounts, 8 devices, 4 different types of devices, all LOS.

Here is the fix. Just tested this on the latest build of LOS, and it works fine. Direct link to the Magisk module.
Also those directions, say they chose a Pixel fingerprint, I chose the OP 5T fingerprint, it worked just fine. My device is now certified.

OhioYJ said:
Here is the fix. Just tested this on the latest build of LOS, and it works fine. Direct link to the Magisk module.
Also those directions, say they chose a Pixel fingerprint, I chose the OP 5T fingerprint, it worked just fine. My device is now certified.
Click to expand...
Click to collapse
can you pass safetynet ?
try this app
latest safetynet api
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample

AlMaghraby said:
can you pass safetynet ?
try this app
latest safetynet api
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Click to expand...
Click to collapse
I tried that app, yes it passes. Both CTS profile and Basic Integrity come back true.
(Obviously adding that app to the hide list)

OhioYJ said:
I tried that app, yes it passes. Both CTS profile and Basic Integrity come back true.
(Obviously adding that app to the hide list)
Click to expand...
Click to collapse
thank you so much that was the only thing preventing me from updating

Should a custom kernel fix this?

I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?

Unlocked and still certified. I assume it's because I haven't modified the system partition by only using systemless mods in magisk
Sent from my Pixel 3 XL using Tapatalk

Pic
{
"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"
}
Sent from my Pixel 3 XL using Tapatalk

If you've installed overlays, they reside in system/app, and thus you have modified system.
You're certified because Magisk hide is doing its job in relation to SafetyNet.
superchilpil said:
Unlocked and still certified. I assume it's because I haven't modified the system partition by only using systemless mods in magisk
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk

diesteldorf said:
I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Click to expand...
Click to collapse
I'm bootloader unlocked, rooted, running a Substratum theme and Android Pay works fine plus my device is certified in Google Play.
You have to use Magisk hide on the apps that don't work with root. As far as your device showing up as not certified, use Magisk hide on Google Play store then reboot, then clear the storage and cache on the play store, reboot again and it will show up as device certified.

These are the apps I use Magisk hide on and everything on my Pixel 3 XL works like it's not rooted.

diesteldorf said:
I recently got the Pixel 3 XL, and was working to get it setup. However, I am going to wait to activate it until I know that I can successfully pass the SafetyNet Check and use Android Pay.
I have quite a few apps so I wanted to transfer a lot of them via Titanium Backup. I successfully installed Magisk, flashed the patched boot.img file, verified I was rooted, and installed all of my apps via Titanium Backup---from one of my other devices.
Then I re-flashed the original boot.img file to partition A & B and verified that I was no longer rooted.
However, my Device shows up as NOT CERTIFIED in Google Play. I totally expected this, since my bootloader is definitely unlocked.
Question #1: When developers start releasing custom kernels, will this issue probably be resolved? I don't care about root, beyond restoring my apps, but Android Pay is highly utilized.
Question #2: Has anyone unlocked your bootloader and still had their device show up as CERTIFIED, with Android Pay working as expected?
Click to expand...
Click to collapse
Just clear data in the play store. Thats all it needs....

micmars said:
If you've installed overlays, they reside in system/app, and thus you have modified system.
You're certified because Magisk hide is doing its job in relation to SafetyNet.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Overlays are in the vendor partition not system.
Back on my Pixel C when we didn't have twrp I would unpack the vendor partition and place the overlays.
NVM I guess OMS has changed since I last used it
Sent from my Pixel 3 XL using Tapatalk

No, not on Pie.
superchilpil said:
Overlays are in the vendor partition not system.
Back on my Pixel C when we didn't have twrp I would unpack the vendor partition and place the overlays.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk

elreydenj said:
Just clear data in the play store. Thats all it needs....
Click to expand...
Click to collapse
That fixed mine from saying that it was not certified. Thanks!