Banking apps such as Google Pay (Wallet) and games like Pokemon Go are common examples of such apps. That said, it’s still not a big deal because you can always restore the stock firmware and relock the phone’s bootloader if and when you want.Ģ) SafetyNet/Play Integrity and Android apps: There are several apps that utilize the SafetyNet/ Play Integrity APIs to check if the phone’s bootloader is unlocked and might stop working if it is. I was particularly disappointed considering that phones from several manufacturers such as OnePlus and even Google itself are covered under warranty even after the bootloader is unlocked. So I reached out to Nothing through their customer support page for clarification and according to the support executive – “ Unlocking Nothing Phone 1’s bootloader voids warranty“. With bootloader unlocking, there are a few important things you should take note of.ġ) Effect on warranty: The manufacturer hasn’t provided any public statement to confirm the effects of bootloader unlocking on the phone’s warranty. If you’re interested in extensively modifying the stock firmware by rooting it or flashing a totally different firmware (a custom ROM) altogether, then you will need to unlock the bootloader of your Nothing Phone 1. And as I mentioned earlier, a locked bootloader does not allow flashing the device partitions at all. Things such as rooting, flashing custom ROMs/kernels, installing a custom recovery, etc, involve flashing different partitions such as /boot, /recovery, /system, /vendor, among others.
This brings us down to the question - Why and when would you need to unlock the bootloader? And preventing users from flashing bootloader and other device partitions.Verifying the integrity of /boot and /recovery partitions during the boot-process.Like most other Android phones, the bootloader on the Nothing Phone 1 is locked to ensure that the phone only runs the manufacturer-authorized firmware.
You can refer to the official documentation if you wish to learn more about the Android Bootloader and boot-process.
0 kommentar(er)
