Originally Posted by djselbeck

I would like to not flash my bootloader. This is the riskiest operation I could imagine.

I'm at the point where my loyalty for your platform comes to an end.

If you write openess on your flags you should deliver it.

I don't see why this bootloader update today was necessary.

Anyone who depends on data security for this BETA PLATFORM at the moment is mentally not clear.

My jolla goes in to the bay on sunday. If someone wants to make a good offer go ahead and PM me

Originally Posted by rainisto

One of the rationales was that you have setup devicelock code with immediate lock, have company emails setup in your device, your company policy forces lockcode to protect company secrets.

"oem boot" allowed you to copy whole root partition without asking the lockcode. With this change copying root partition is only allowed after you have entered the devicelock code.

So hypotically if someone has option to follow mail for exchange security policy vs remove whole mfe support in future updates, which one has valid businesscase? Or if hypotically you can skip devicelock code query without any effort, would you trust your device any more?

You can say that you dont use mfe and dont care if people can steal your data easily, thats why there is still option to flash old bootloader back to device (or just make custom recovery image). But personally I use devicelock code on my device and have updated to latest bootloader and revocery partition.

Originally Posted by djselbeck

As an owner of an Xperia Z from Sony I know how it could be done so don't give me wrong facts.

fastboot oem unlock 0xKEY would've been the perfect way. This would've given the geeks around here the possibility to do what they want. Now we can't do this.

If you were unable to implement this in time, you should provide the bootloader image yourself. Also a way you've not taken.

From an open company I expect this.

I'm done. I'm writing developer care right now to pull my app from your store and sell my device.

Good luck satisfying your MFE customers

Originally Posted by Raim

This is disappointing.

On the one hand Jolla encourages hacking of the device to developers (which are probably the sole user base at the moment?). On the other hand they now want to secure the device for the normal user and take away functionality we saw as a feature. I understand the security concerns here. However, without any way to easily reset the device by flashing an image, this makes me more cautious with any experiments…

At least it seems like the old mmcblk0p17 seems to be the same for everyone – the checksums published earlier in this thread matched.

Originally Posted by djselbeck

Maybe updates take their time. But I'm not DDing my bootloader. No way.

Also I don't want to wait until the device is worthless on ebay. So goodbye jolla community for now.

SMPC will be pulled from harbour, development stopped.
MTBtracker development stopped.

This will be my last post. Goodbye everyone, this has been a great experience the last few weeks. Also a much better community than XDA for example.

Originally Posted by rainisto

This update also included recovery image (power+volumedown), which allows to factory reset your btrfs back out of box state. Which should make your experiments a bit safer. As you can use recovery image to get into bootable state, and you can use root-shell to recover for example your latest rdiff-backup to your device.