Ask / Submit
4

Release optional unlocked bootloader

asked 2014-07-02 02:40:54 +0200

00prometheus gravatar image

updated 2014-07-02 09:57:22 +0200

In the 1.0.2.5 firmware, the bootloader became locked to close a security hole that could give access to the phone without a phone pin-code. This is understandable, many users prefer to have their phone more secure, rather than having a completely unlocked bootloader. However, not so for everyone.

A simple solution is to make an optional package with an unlocked bootloader available, only installable from command line. That way users that wish to tinker with their phone and don't mind the reduced security can do so, and users that prefer a tighter lock on their phone can have that. It would require the official updates to have the unlocked bootloader as an acceptable dependency so that OTA updates still work.

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted
1

answered 2014-07-02 10:47:21 +0200

rainisto gravatar image

updated 2014-07-02 10:50:53 +0200

You can dd the bootloader from 1.0.7.16 over 1.0.2.5 without problems (or use the rpm for 1.0.7.16), but maybe your not asking for that?

Ie most likely you want 1.0.2.5 release packages to be altered in a way that upgrade from 1.0.0.5 to 1.0.2.5 would take 1.0.7.16 bootloader package into use? Most likely changing repository packages after they have released is a bad idea or it might end up in unforseen problems. So most likely that wont happen.

We are trying to streamline updates in the future in a way that factory btrfs snapshots would up upgraded also. But there is no ETA yet for it. Ie after you would have upgraded to 1.1.x.x and you would do factory reset, you would go back to 1.1.x.x instead of 1.0.0.5. That way you wouldn't need to worry having 1.0.2.5 step in upgrade processes.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
5 followers

Stats

Asked: 2014-07-02 02:40:54 +0200

Seen: 619 times

Last updated: Jul 02 '14