It is "quite easy" to flash the bootloader to an old version

Someone needs to upload it though.

AFAIUI there are flashing tools on board, and if you have Developer Mode, you can use them.

Yes, you can flash with dd and sha1sum afterwards. But you still depend that someone uploads an unlocked bootloader image. And that the partition remains readwrite in the future.

As stated somewhere in this thread, the possibility to mask partitions readonly exists.

several backups of bootloader unlocked version exists - mine included, if someone needs I can post a share link.
But, dd'ing bootloader can be fatal, it does do the job when done right.

Not to digress from your main point (which is somewhat of a digression itself), but do you use both devices heavily still?

Can't you reset to factory settings, access with fastboot, dd the bootloader and then upgrade and do whatever?

At the moment this should do the trick. But someone asked what if factory state will be updated to new bootloader

I can tell you why it was keep: it was just more work to remove it. Which is what I fear with the "cripple first" approach. That when the time comes to actually make on the promises made, "there is no manpower"/"it is Christmas". But oh, there certainly was manpower to cripple it in the first place.

(We'll never learn)

Please, let's not follow this. Because then I'll ask why are they not using Android in the first place, which is what the "rules of the market" call for. We're trying to define new rules of the market here. That's how one makes sales when they're the small newcomer.
Discussing this would bring too much OT on this thread, so let's keep it at that. I can open a new thread if desired.

See above -- no one is demanding "all at once". Let's define groups of users A (tinkerers) and B (those who want a locked bootloader when a lock code is active). In the preChristmas situation group A was "pleased" while B was not. Jolla knows of a method to please both groups, but it involves some implementation cost (namely a way to unlock the bootloader).

Which one of the following options would you chose?

1) Tell group B to wait until the optionally-locks-bootloader update "which may or may not come". A is happy.
2) Annoy A by locking their bootloaders unconditionally. Tell group A to wait until the optionally-unlocks-bootloader update "which may or may not come". B is happy.

If you chose 2, then, well, it's a valid option, but you just shown your true colors. And obviously, you should expect rage from A.

i know this is OT, and many hates FB ....

https://www.facebook.com/photo.php?f...6237701&type=1

My main phone is bb10 as harmattan started to lag and bb10 great screen and qt support as well as company support made me switch. But N900 I used till its last day(usb broke up second time after soldering), even when I had new iPhone 4 in the box (i took it as part of operator plan and planned to sell it). I even consider buying it again or neo900.
As we learned there are two kinds of support, one from company and one is from community and as you see not always go both ways. And it would be okay, but only if they do not go opposite ways by company making it's more difficult to community to support device.
You can see examples in android world when there are custom roms from community with newer firmware than last company released. Or even custom features with add-ons companies failed to bring. And while company try to sell you new phone every few months you can still use optimized supported by community rom for old one.


I feel that every new platform starting from maemo we go few steps forward and dozen backwards. Yes, they need to sell phones and make money, but when what is 'unlike' about? Is it about new UI and same crippled device as all others on market?