Develop Bugs

SafetyNet / Android Pay Failure

Hello, I am having an issue with my wife's Robin. The phone is completely stock other than an unlocked bootloader and unencrypted storage. System, boot, recovery, kernel, etc. are all stock and no root. I have even wiped the system partition and reflashed the system.img for good measure. The device is failing SafetyNet checks, however. This means Android Pay is not working and displays the following error. "Android Pay can't be used on this device. This may be because your device is rooted, has an unlocked bootloader, or is running a custom ROM. As a result, Google can't confirm that your device meets Android Pay's security standards." Does anyone else with ONLY an unlocked bootloader have the same issue? Could lack of encryption have anything to do with it? I am puzzled. I have an old Nexus 5 with an unlocked bootloader, rooted, with no encryption and I am still able to toggle root and pass SafetyNet checks. Anyone else have a similar issue? If this is the case, she might as well have root and the advantages (as well as the potential hazards) that come with it.

Your wifes robin has an unlocked bootloader and you had to batch the kernel (boot.img) if she is still running stock os.
This is enough to trigger saftynet. If you want to pass saftynet again I suggest you go back to full stock or you flash magisk
( https://forum.xda-developers.com/apps/magisk ) and the phh supersu module. then you could activate magisk hide in the settings and you will pass saftynet. Thats what I am doing to play Pokemon Go

flyfire04 said:
Your wifes robin has an unlocked bootloader and you had to batch the kernel (boot.img) if she is still running stock os.
This is enough to trigger saftynet. If you want to pass saftynet again I suggest you go back to full stock or you flash magisk
( https://forum.xda-developers.com/apps/magisk ) and the phh supersu module. then you could activate magisk hide in the settings and you will pass saftynet. Thats what I am doing to play Pokemon Go
Click to expand...
Click to collapse
Thanks for the response and link. I ran the OEM unlock command and have since flashed the boot.img from the official Nextbit factory images. So unless that boot.img is itself patched, then I should be stock (other than the unlocked bootloader of course). That is likely the issue, but I want to see if anyone else who is stock with an unlocked bootloader has the same issue.

Then read this: https://www.xda-developers.com/sult...otloader-check-on-latest-cm13-builds-for-op3/
Then you will understand that an unlocked bootloader by itself can trigger saftynet. magisk removes the the verified boot flag.

Another easy solution is to just lock the bootloader using the oem lock command. This will not wipe the device like unlocking does.

So to be clear, my choices to get SafetyNet to pass are to:
OEM lock thus returning to complete stock or
Flash a modified kernel to suppress the bootloader unlocked flag or
Flash Magisk and phh root and activate Magisk hide
If I do the last option, do I also need a modified kernel or will this hide the bootloader unlock status from SafetyNet with the stock kernel? Thanks for the feedback.

CTS fail right after flash-all

My Pixel 2 XL running on DP2 pass CTS test no problem. I could use Google Pay normally. (with Magisk v16.4)
Today I update to DP3 with factory image (flash-all with wipe), but CTS profile match failed...
I tried to downgrade to Oreo Jun with factory image (flash-all with wipe), CTS profile match still fail...
No TWRP, No Magisk, No Xposed. Tested right after initial configuration (Google account, etc.) The Only APP installed is CTS test APP. Android Pay refused to add credit card, complaining device being rooted.
My 2 XL is oem unlocked (had always been since I got it months ago)...
Any idea?

Answering my own question:
I tried lock bootloader-->CTS pass
unlock bootloader-->CTS fail... (However, before by bootloader is always unlocked and CTS pass)
It seems DP3 need bootloader to be locked to pass CTS profile... Anyone notice similar issue?

lssong99 said:
Answering my own question:
I tried lock bootloader-->CTS pass
unlock bootloader-->CTS fail... (However, before by bootloader is always unlocked and CTS pass)
It seems DP3 need bootloader to be locked to pass CTS profile... Anyone notice similar issue?
Click to expand...
Click to collapse
You always need to have bootloader locked or install custom kernel like Flash if bootloader is unlocked to pass safetynet

ram4ufriends said:
You always need to have bootloader locked or install custom kernel like Flash if bootloader is unlocked to pass safetynet
Click to expand...
Click to collapse
But before DP2 (as well as Android 8 up to May update) I always have bootloader unlocked with Magisk and CTS profile pass (Stock, Magisked kernel) ... Now CTS doesn't pass with or without Magisk...

Just a wild guess but since you wiped your device and installed from scratch did you enable Magisk Hide from the settings?

danielt021 said:
Just a wild guess but since you wiped your device and installed from scratch did you enable Magisk Hide from the settings?
Click to expand...
Click to collapse
Yes... I did everything that should be done....
Out of desperation, I still tried to set up a Credit card in Google Pay and interesting thing is that although my system still CTS failed, I was able to add my credit card to Google Pay and made a payment! Really strange.....
Anyway as long as Google Pay works, really don't care about CTS status...
Thanks for all your reply...

Can i relock the bootloader after changing from china rom to global rom?

So i have successfully changed from the china rom to the global rom on an 8G/128G device and even updated to Miui 11, Everything works fine phone reboots perfectly it's all happy except i need to lock the boot loader to use Google pay, Is it going to brick it? and how do i do it.

Confused_adria said:
So i have successfully changed from the china rom to the global rom on an 8G/128G device and even updated to Miui 11, Everything works fine phone reboots perfectly it's all happy except i need to lock the boot loader to use Google pay, Is it going to brick it? and how do i do it.
Click to expand...
Click to collapse
I have no experience with this phone, but I feel you are going to EDL mode by doing that.
Stay unlocked and use Magisk tools.

lolo9393 said:
I have no experience with this phone, but I feel you are going to EDL mode by doing that.
Stay unlocked and use Magisk tools.
Click to expand...
Click to collapse
only guides i can find for magisk require tWRP, which means custom roms and that insta bricks these devices.

Question Cannot lock bootloader

Hi,
I unlocked the bootloader of my oneplus 9 pro.
After finding out that I cannot use Google Pay anymore I wanted to lock the device again.
When using fastboot oem lock I get the message that my phone has been tampered with and it will not boot.
I tried flashing the stock rom using payload_dumper and locking the bootloader afterward, but no succes.
The only thing I can do at the moment is unlocking the bootloader and using the phone like this.
Does anyone have a solution?

Never mind I found the solution
-> flash the same OTA twice via local system upgrade
-> reboot into bootloader
-> fastboot oem lock

glad you got it sorted!

That is the correct way to lock. But I am typing on a 9 Pro that has Magisk installed with GPay working flawlessly. Running 11.2.6.6

That is weird.
My gpay app would always say that my device was rooted of tampered with.
I followed the guide to install magisk.
After that I flashed a custom kernel.
Used magisk hide on gpay and my banking apps.
I even used the hide magisk app feature and I was still unable to get gpay working.
I removed magisk and still gpay would not work.
I wonder how you got it to work.

Question OnePlus 9 pro le2125 corrupt after relocking bootloader

Hi, i bought a OnePlus 9 pro NA unlocked version le2125 from Amazon. I unlocked the bootloader to root it but after several of my banking apps refuse to work properly i decided to unroot it. I did the fastboot oem lock and now the phone will not boot because it says it's corrupt. what would be my best course of action to just get the phone back to stock?

Use MSM tool

SupposedlySam said:
Use MSM tool
Click to expand...
Click to collapse
Yes i eventually found the right version of msm tool and successfully unbricked it. Thanks.

pdrift said:
Hi, i bought a OnePlus 9 pro NA unlocked version le2125 from Amazon. I unlocked the bootloader to root it but after several of my banking apps refuse to work properly i decided to unroot it. I did the fastboot oem lock and now the phone will not boot because it says it's corrupt. what would be my best course of action to just get the phone back to stock?
Click to expand...
Click to collapse
You can just use the forked magisk which still has magisk hide. All my apps work, do does gpay

Zeus0fyork said:
You can just use the forked magisk which still has magisk hide. All my apps work, do does gpay
Click to expand...
Click to collapse
Where can i find this forked version? I just finished setting up my phone and all my apps again but if i can get root and still use those apps then i might give it another try.