3 ms·
I can guess what the reason for this is: probably every phone that leaves Google must pass SafetyNet, and an unlocked bootloader will make SafetyNet fail. This
by deng 4y ago
I can guess what the reason for this is: probably every phone that leaves Google must pass SafetyNet, and an unlocked bootloader will make SafetyNet fail. This cannot be circumvented, see this thread from the Magisk developer:
https://nitter.net/topjohnwu/status/1237830555523149824 https://nitter.net/topjohnwu/status/1237830555523149824
- nfriedly 4y agoI should probably have clarified that I expected an unlockable phone, not an unlocked one. Unlockable meaning that it is still locked, and still passes SafteyNet, but I can flip the switch in developer options and run the fastboot command and then unlock it. That capability is what they took away. IMO, that shouldn't cause SafteyNet to fail either, but that's a different issue... Also, the phone was bought in 2017, and the repair happened in 2018, so I think all of it predates that SafteyNet tightening.