Nexus 6P remembers whether he was ever modified
5
OS Smartphone
1856 Views
The question of security of mobile devices is paramount not only to the owners of devices, but and producers. Two-factor authentication, a fingerprint scanner and a lot more created with the only aim to maximally protect our data.
With the development of mobile technology Payments devaysa reliability to a new level. In fact, hardly anyone would be delighted if, after, say, the loss of the phone, a stranger will be able to gain access to another account at the bank.
If you are familiar with the solution from Samsung, called KNOX, you probably understand what will be discussed further. The other day on Reddit published information on the new chips from Google’s flagship Nexus 6P. Definitely, like it is not all.
As you can see in the image below in the loader device has a new line: «Note the Qfuse Status: Enabled». Now a special tool keeps track of whether the firmware ever modified.
In other words, if the user Nexus 6P unlocked bootloader, install a modified system ( events, custom, beta), smart phone will remember this action, even if the drain after a return to the version of Android and block the loader back. The principle of the mechanism is very simple: the default Qfuse switch is in the active position until it is unlocked Bootloader. Only once having done so, Qfuse remember the operation. Delete the data on this will not be possible.
On that counts Google, and letting such innovation is unclear. Perhaps the new security measure created in connection with the service Android Pay, and is necessary for the Android for Work. On the other hand, with Qfuse many uniquely increases fear of being left without a guarantee, given that one of the notable features of Android, such as smart phones line Nexus, has always been the customization and freedom in the choice of the firmware.
In your opinion, that made the corporation: has introduced a new measure of safety or a complicated life lovers modify your Android-device?
On materials El Androide Libre
No comments:
Post a Comment