Develop Bugs

Android Pay broken, was working.

Hey all, I am running stock US unlocked Rom 1.80.617, rooted, s-off, Verizon radio, and Android pay was working fine. Just went to use it and said it couldn't work on this system,... Yada yada.. The only thing that has changed between the last time and this time I used Android pay was that I updated to SuperSU 2.76 through Android play store and I updated AdAway through xda labs. Can someone explain to me why either of those updates would have broken AP or could it be something else? Also, is there any easy way to check if I still have systemless root? Assuming I would do that with an ADB command. Can I run the command in a terminal emulator on the phone? Don't really want to boot up the computer of I don't have to. Thanks in advance.

changed permissions of /su/bin to 751 and safetynet checker passes.. . Assume that means AP will work. Will purchase something and report back. Still unsure why AP worked before then randomly quit.
Edit: OK, safetynet checker didn't pass when i reran it, seems random when it passes or not. Anyone have any ideas?

Light1984 said:
Hey all, I am running stock US unlocked Rom 1.80.617, rooted, s-off, Verizon radio, and Android pay was working fine. Just went to use it and said it couldn't work on this system,... Yada yada.. The only thing that has changed between the last time and this time I used Android pay was that I updated to SuperSU 2.76 through Android play store and I updated AdAway through xda labs. Can someone explain to me why either of those updates would have broken AP or could it be something else? Also, is there any easy way to check if I still have systemless root? Assuming I would do that with an ADB command. Can I run the command in a terminal emulator on the phone? Don't really want to boot up the computer of I don't have to. Thanks in advance.
Click to expand...
Click to collapse
Well you screwed yourself. Adaway modified system, Android pay will not work on a modified system. That's why it require systemless root to work

Behold_this said:
Well you screwed yourself. Adaway modified system, Android pay will not work on a modified system. That's why it require systemless root to work
Click to expand...
Click to collapse
But I used Android pay fine with AdAway for a while right after you posted the 1.80.617 RUU. Installed AdAway from XDA labs and updated if through labs as well. Honestly just seemed to randomly stop working.
So if AdAway is the culprit, is there an app with similar functionality that doesn't break AP (xposed is obviously out cause it breaks AP)?

Light1984 said:
But I used Android pay fine with AdAway for a while right after you posted the 1.80.617 RUU. Installed AdAway from XDA labs and updated if through labs as well. Honestly just seemed to randomly stop working.
So if AdAway is the culprit, is there an app with similar functionality that doesn't break AP (xposed is obviously out cause it breaks AP)?
Click to expand...
Click to collapse
Installing adaway isn't the problem. using ad away is the problem. As soon as you apply ad blocking adway modifies your host file. At that point system has been modified and Android pay will fail.

Behold_this said:
Installing adaway isn't the problem. using ad away is the problem. As soon as you apply ad blocking adway modifies your host file. At that point system has been modified and Android pay will fail.
Click to expand...
Click to collapse
But I updated host files as soon as I installed AdAway when I clean flashed the 1.80.617 RUU you provided. It worked after that on two occasions, would it fix it if I change where the host file is saved (after a clean install before applying updated host files of course)? I think that's an option in AdAway, you can move it into \data.

Light1984 said:
But I updated host files as soon as I installed AdAway when I clean flashed the 1.80.617 RUU you provided. It worked after that on two occasions, would it fix it if I change where the host file is saved (after a clean install before applying updated host files of course)? I think that's an option in AdAway, you can move it into \data.
Click to expand...
Click to collapse
Yeah, i would think that should.

If anyone else is following this I believe google has changed something to kill AP with root again. I've been following another thread (for a different phone) and it seems others have experienced the same thing.
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659/page43

Android pay on our OP3 with root?

Need help! Don't know if it's been answered. I've checked and haven't going anything. I've tried the chmod 751 in terminal and everything systemless and nothing has worked. Echo command did nothing.

It got patched yesterday. AP doesn't work anymore on rooted devices. Not sure if it's against the rules to link reddit but check r/android for updates like this

katsumex said:
It got patched yesterday. AP doesn't work anymore on rooted devices. Not sure if it's against the rules to link reddit but check r/android for updates like this
Click to expand...
Click to collapse
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?

It should work with systemless root, but you have to disable xposed.

lparcshinoda said:
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
Click to expand...
Click to collapse
So if you haven't purchased anything yet, try to. It probably won't work. It fails on two parts, me trying to add a credit card after a factory reset and when I had the credit card on it and tried using a touch pay thing.

daClaus said:
It should work with systemless root, but you have to disable xposed.
Click to expand...
Click to collapse
As @katsumex stated, it was patched.
Thread here if you're curious: http://forum.xda-developers.com/oneplus-3/help/oos-3-2-2-safetynet-t3427833

Works fine systemless without xposed enabled

Thanks a lot guys. Well I am systemless and it did t work and this was before the patch. Also don't have exposed and still didn't work. Guess I'll be waiting for a newer setup. Urghhh. To root or not to root?, in the name of Android Pay!!!

lparcshinoda said:
On my device it does seem to work with systemless root (latest supersu). When do you receive the alert?
Click to expand...
Click to collapse
Any specific steps to set it up? I mean I am systemless and I don't have Xposed. Still nothing. Maybe I forgot to set something.

SuperSU v2.76 on 3.2.1 stopped working for me yesterday. Have over 20 transactions where it has. According to the play store the app itself last updated 11th July. And I have transactions done after. So whatever's changed is not on the app.
Btw, i will try systemless and report back.

TheLoverMan said:
Works fine systemless without xposed enabled
Click to expand...
Click to collapse
Not anymore.

Correct. The safetynet check no longer passes. The check is performed server side, so there is really no way to work around it at the moment, unless you fully unroot of course. So, even a fully proper systemless root method will fail. Oh well. I have never, nor ever will most likely, use Android Pay anyway. Lol. I was just curious why it wasn't working...so apparently Google has caught on for now. This goes for all phones too, not just the OP3. Good luck!

Root + Android Pay. What does OEM Unlock do?

I rooted my phone only so I could use AdAway. So once I update the hosts file with AdAway, technically I can disable root and only enable root once a week or so to re-run AdAway and update the hosts file again correct?
So I want to use Android Pay too... I keep reading that if I disable root in SuperSU it'll work, but my Android Pay flat out rufuses to work.
Only other thing I can think of is disabling OEM Unlock. What does that even do? I'm currently running custom recovey (TWRP).
Does OEM Unlock need to remain enabled? Could that prevent Android Pay working when SuperSU root is disabled?
Thanks

If your root method modified /system/ then you will never be able to use Android Pay as it checks this. Even systemless root stopped working with the August security patch. It's why I didn't root my Note 7 when I got it because I figured this out on the 6P. Sad but true.

Is there a way to un-root and re-root quickly? I disabled root in SuperSU but it doesn't help.
All I really want to do is block ads via the host file with adaway (which is how it works right?) And I can enable root every time I want to update the ad block list.
Thanks for reply

I found a few ways to do it on other sections of this forum but they seemed tedious and I haven't really looked since the August patch flarked everything up for folks who want AP. Sorry. I wish I could answer.

Build.prop and tether

Can the build.prop still be edited to allow tethering without the carrier check?

Yes but you need root and if you have root you have magisk and if you have magisk you can install the tether module which changes the build prop for you.

bigv5150 said:
Yes but you need root and if you have root you have magisk and if you have magisk you can install the tether module which changes the build prop for you.
Click to expand...
Click to collapse
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.

you can root, modify build.prop then unroot...

gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
I'm pretty sure magisk has a module that hides root or magisk hide root I've never had to hide root so I really don't know but I'm pretty sure you can do that

gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
If you have time, I would try Magisk with the hide enabled and see if your apps complain. I have not had any detect it yet. Back with supersu even with its hide add on it was a challenge but Magisk is spot on.

With magisk I was able to still use snap chat since it hides the root. YOu should be fine using other apps with magisk.

gatortuba said:
Can i edit it by just unlocking the boot loader and do it through adb? I don't want to root since certain apps don't work with it.
Click to expand...
Click to collapse
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.

brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Do i need to unlock to bootloader to root with magisk?

brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
How does Magisk work when updates need to be applied?

brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Does it work on the latest build?

Hi, are you using pixel 2 xl..? If you are, can you provide me a copy of the build.prop of pixel 2 xl?

brkshr said:
You can pull the build.prop through ADB, edit it, push it back and chmod the permissions of the file. There are guides out there with all of the necessary steps. I used to do it this way, but it got to be a pain when they started monthly updates. I went back to rooting the monthly updates and editing the build.prop.
Click to expand...
Click to collapse
Another, possibly easier option is to install Magisk, download a file explorer from the play store, then scroll down to build.prop and just add the net.tethering.noprovisioning=true. Worked like a boss.

cedargreen said:
Another, possibly easier option is to install Magisk, download a file explorer from the play store, then scroll down to build.prop and just add the net.tethering.noprovisioning=true. Worked like a boss.
Click to expand...
Click to collapse
I can't get the file it needs, all of the files are in a payload.bin file.

Ok don't get mad I need to know if I unlocked device will wipe..
I don't want root
After unlock how. Can edit build prop to get tether working and ones I do will I be getting ota ?

vivrosh said:
Ok don't get mad I need to know if I unlocked device will wipe..
I don't want root
After unlock how. Can edit build prop to get tether working and ones I do will I be getting ota ?
Click to expand...
Click to collapse
If you use Magisk, pretty sure you can just sideload the OTA updates. You will have to go to the TWRP and Magisk threads for the XL 2. Magisk is root, but does not break Android Pay.

Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.

vinhdizzo said:
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
Click to expand...
Click to collapse
Good question.

vinhdizzo said:
Can anyone summarize how best to enable hotspot tethering on the pixel 2 xl? I don't need root, and prefer to not have it enabled. I don't mind rooting it once to enable it, then unrooting, so long as the tethering capability remains and so long as Android updates occur as normal, without the need to re-enable tethering. Is this possible? Thank you.
Click to expand...
Click to collapse
You can change build prop and then remove root but when you take the ota it may fail I'm not sure I just flash factory images to update. The other issue would be if the ota overwrites the build prop. If that happens you would have to repeat the process after every update.

bigv5150 said:
You can change build prop and then remove root but when you take the ota it may fail I'm not sure I just flash factory images to update. The other issue would be if the ota overwrites the build prop. If that happens you would have to repeat the process after every update.
Click to expand...
Click to collapse
I'm so sorry for the stupid question, but how do you do that? How to edit the build prop? I can't find any guide. I don't see any tethering module in magisk and I can't use my preferred tethering app with magisk (I contacted the dev and he said magisk broke the app). Not being able to tether is the only reason why my new P2X continues in a drawer and in I'm still using my Note 4. Please shed some light on this moron.

Oneplus 5t security updates vs custom ROM newbie

Hi I've never wanted to root or custom ROM. I read the instructions and they are pages deep and the issues that come up and are discussed in threads have such confusing back and forth discussions using lingo and abbreviations that make my head spin.
However... Oneplus did their last update on my 5t my fourth oneplus phone... With an already old security update.
Is the only way to not throw away a perfectly working, phone with good Ram and a fairly new battery I paid to have installed just months ago?
If I'm wanting to hold on another year or 2 use the only option custom ROMs that contain security updates?
Is there a way to add security updates without a ROM? Or maybe at least just learn to root and then add just updates or is it only in ROMs?
I could probably happily use my phone as is but worried what effect no security updates really is to my use.
I really tried videos on doing so this myself I'm not comfortable if problems happen. Not very techy.
Any help appreciated

Unfortunately you can no longer get security updates once your device is deemed as old.
Your options will be to get an antivirus app on your phone, install a custom ROM (like LOS or pixel exp), or you can get a new phone.
Since you're new to this stuff I highly recommend you just get a new phone or simply install an antivirus.
Not sure which anti virus is better than which. But I'm confident in Avira, McAfee, and Norton. You may want to purchase their plan though.
Hope I helped.

Thanks alot for the reply. I'll start with an antivirus.

Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks

Personally I think that your company has put an unfair burden on you to run company mail and apps on your personal phone while expecting you to have an updated phone at the same time. An updated phone should have been "given" to you.
That being said, you can actually flash and run a custom rom without root. Root is optional.
Process is as follows: (you'll need a PC for this)
1. Backup ALL your data
2. Unlock the bootloader
3. Install custom recovery and reboot to recovery
4. Wipe cache & system and format internal memory
5. Copy custom rom & gapps to internal memory
6. Flash custom rom & gapps and reboot system

miloinodense said:
Hello,
I have similar issue, since I would need security patch update to keep running company mails and apps.
I have 2 doubts:
- if I root and install Android 11 custom ROM, security patches will be updated too?
- after this, would I be able to unroot and install company mail apps ( if rooted they will not work) ?
Thanks
Click to expand...
Click to collapse
Yes if you install custom ROM you'll have security updates. It doesn't have to be Android 11 and you don't need root to install a custom ROM.
Also make sure to follow a precise guide about it so you don't encounter any issues. Always make a backup even if you're 100% sure you won't need it.
As far as I know mail apps don't check the integrity or do a SafetyNet check, so even if you root or don't it will work fine.
If you mean banking apps then you can install some modules to bypass the check or just completely remove root. Assuming that you rooted the device.

It shows my lack of knowledge never ever did I think you could Flash a ROM without being rooted.
Thanks

I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...

miloinodense said:
I successfully installed custom ROM w/o root.
But regarding company mail apps, I would need to hide bootloader unlocked status.
maybe it's impossible, if someone has a good idea...
Click to expand...
Click to collapse
My banking apps working fine without root with crdroid 7.3 and flamegapps. Might work for your company mail app too.
Some roms readily hide bootloader status

Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.

miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
Hence that's why the burden should be on the company to provide the "up to date" phone

miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
And that's why the burden should be on the company to provide the "up to date" phone

miloinodense said:
Thanks for the hint, but these company mails apps are checking security patch date too. Last available for oneplus 5t are September 2020, and no further support from oneplus.
Click to expand...
Click to collapse
I think if you change build.prop to some other phone with recent security patches you can bypass this.

XDHx86 said:
I think if you change build.prop to some other phone with recent security patches you can bypass this.
Click to expand...
Click to collapse
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.

miloinodense said:
Today, I was thinking that this could be good way.
Root, change build.prop, and then unroot.
If you have a link for a good tutorial on change bulid.prop would be nice, thanks.
Click to expand...
Click to collapse
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved

miloinodense said:
Just for update:
I tried to Root a stock ROM, edit build.prop (security patch date), unroot, and then lock bootloader.
But even if it was a stock ROM, OP5T was not booting.
Booloader was stopping boot since it was detecting a non-stock ROM.
Indeed, I had to unbrick OP5T since I was not possible to unlock bootloader.
So, still not solved
Click to expand...
Click to collapse
Just edit build.prop and use magisk hide module from magisk manager.

XDHx86 said:
Just edit build.prop and use magisk hide module from magisk manager.
Click to expand...
Click to collapse
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.

miloinodense said:
Edit build.prop w/o root and unlock bootloader is not possible...
Moreover, hiding root will not work with more recent android updates and for sure it will not hide unlock bootloader.
Click to expand...
Click to collapse
Yeah I assumed you would know that you should root first. But seeing you even attempted to lock bootloader after modifying the device, seems I assumed wrong.
Magisk hide is working fine on later android versions like 8+. And for the bootloader it only trips CTS if your bootloader is using hardware backed key - Which is the case with OP5 - as CTS check also has hardware attestation. But it is possible to bypass said check by using SafetyNet Fix module, of course you will also install that from magisk manager.