You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current setup (if I'm right) may end up in undesired situation if one uses a
secure setup (I mean setup no one can abuse by rebooting to unprotected
fastboot/recovery):
* phone is rooted (and BootUnlocker is installed)
* bootloader is locked
* stock recovery
* OTA update is proposed and accepted
=> oops!
* phone is not rooted anymore
* bootloader is locked
* stock recovery
=>
At that point one will have to use again fastboot oem unlock and erase
everything
So what I'm doing on my phone:
echo "# Remove me to allow OTA update" >> /system/build.prop
This makes sure nobody can apply OTA by accident before unlocking bootloader
(to allow booting on alt recovery and applying rooting again)
This could be actually a feature of BootUnlocker:
Prevent automatically that OTA updates can be applied (and root access lost) if
bootlocker is locked.
Some details of the full procedure:
http://wiki.yobi.be/wiki/Android#Rooting_and_OTA
I know rooting software try to preserve root access over OTA but by experience
over those last OTA, it often fails so it's critical to have an unlocked
bootloader when applying OTA update.
Original issue reported on code.google.com by [email protected] on 20 Jun 2014 at 9:06
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 20 Jun 2014 at 9:06The text was updated successfully, but these errors were encountered: