maemo.org - Talk
Page 12 of 34 « First 21011 12 131422 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Jolla1 & TOH (https://talk.maemo.org/forumdisplay.php?f=56)
-   -   [HOWTO] Comprehensive Firmware Flashing Guide for Jolla (https://talk.maemo.org/showthread.php?t=91885)

nieldk 2013-12-27 21:19
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
Quote:
Originally Posted by djselbeck (Post 1401224)
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
+1

10 freakin locked chars

rainisto 2013-12-27 21:27
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
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 recovery partition (as I can always use recovery partition to get my device to match my latest rdiff backup that I have in a cloud).

djselbeck 2013-12-27 21:31
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
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 :p

nieldk 2013-12-27 21:32
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
Quote:
Originally Posted by rainisto (Post 1401232)
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.
Then I guess Jolla made a decision when it comes to openess and a development friendly community device versus a closed, secure device.
Goodbye Jolla from me

rainisto 2013-12-27 21:36
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
Quote:
Originally Posted by djselbeck (Post 1401235)
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 :p
Like I said we are working on possibility of allowing "fastboot oem unlock 0xKEY" but updates take time to implement. I did not say that you never will be able unlock your fastboot. And this change was not done because of MFE, you should have read 'hypotically' part.

Raim 2013-12-27 21:37
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
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.

djselbeck 2013-12-27 21:41
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
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.

rainisto 2013-12-27 21:56
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
Quote:
Originally Posted by Raim (Post 1401240)
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.
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.

nieldk 2013-12-27 21:58
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
Quote:
Originally Posted by djselbeck (Post 1401242)
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.
While I will stop my Jolla adventure. I will not stop on this community.
I will, hopefully, achieve my own goals with N9xx, or neo900 or ... But here, in this community is plenty of talents to support. Just wish Jolla would have acknowledged that

nieldk 2013-12-27 21:59
Re: [HOWTO] Comprehensive Firmware Flashing Guide for Jolla
 
Quote:
Originally Posted by rainisto (Post 1401249)
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.
You clearly dont understand the needs that some developers have. This is fine, but not for me.


All times are GMT. The time now is 09:10.
Page 12 of 34 « First 21011 12 131422 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8