If you connect usb while holding voldown, fastboot will be availavle?

lsusb still lists a qualcomm device, it will however not list as a block device - the last thing I hoped for.

There is no more fastboot.

No, the only way to safe this device is using Qualcomm tools. Ian not sure if even Jolla got those (they are licensed $$$)
Read my answers to this special bootloader mode in other threads.
While the mentioned tool can be found, pirated, we still need certain files and XML partition layout for this.

It's not undoable, but we don't have all the pieces of the puzzle.

I suspect any event where Jolla sends one or more hackers. Only FOSDEM comes to mind right now, but I hope there's some earlier developer/community event before that (like the JollaC one).

Obviously, at least some sailors have access to factory images and flashing tools.

Interesting , do you know who?

For others, like I said, the SBL(1) is erased/damaged and thus the phone don't know how to boot. Leaving it in this factory mode. Unable to enter fast boot, recovery, or, normal boot.

There is good reference, also how this can be fixed on certain Android devices.

If we can create similar for Jolla phones, yes, it is recoverable , but until then, probably only the factory can recover this.

More info: http://forum.xda-developers.com/show....php?t=2625332

I will make a case against being able to modify SBL or partition tables from the phone in general just by being root. There should be one more layer of protection.

I have been through many of the XDA resources along with some android unbrick blogs - they all rely on the provided images. I have yet to see a 'reverse engineered' effort succeed reviving a phone with some frankenstein image.

Citation from a comment I received on the following resource by androidbrick: http://www.androidbrick.com/ultimate...oad_qpst_qfil/

"Thank you so much for the kind words. As to your problem : Qualcomm 9008 port is simply just a “service port” that waits right files from you to wake up the device. Just a commication port, you cant manualy flash anything over it. You need a proper service rom that includes ““rawprogram0.xml”, “patch0.xml”, “prog_emmc_firehose_XXXX.mbn” or “MPRGXXXX.mbn”” in it, without those files your phone cant come back sorry. Those mbn files are a must to turn your bricked phone into EMMC mode again (Qualcomm 9006), so your phone’s EMMC drive will wake and accepts your backed up partititons again from linux or from an other windows based partition software.. So you just need to find those, or nothing can be done, sorry. Greetings."

So for now that means we (I) need to switch from Qualcomm 9008 (service port) to Qualcomm 9006 (emmc mode) requiring:

- rawprogram0.xml
- patch0.xml
- MPRGXXXX.mbn (as at least Jolla C listens to Sahara protocoll, not the supposedly newer Firehose protocol)

And I don't even think that the .mbn file is the actual whole ROM, in our case SFOS but just the part needed to revive the device. Does it include anything that falls under NDA? Who can tell.

That's our situation, judging from the dead Jolla 1 thread.

The mbm files can indeed contain full rom.
But to recover only the SBL is needed.
The xml files can proberly be reconstrocted, proberly also the mbm files, but not without a great deal of effort.

So, yes, as I said, at the moment most likely only the factory have all the pieces to this.

Being able to do it only as root is the protection, so I am against any "uber-root" hurdles you're proposing.

<rant>
The problem is that people (especially Android users, but many people on TMO as well) don't realize what it means to do stuff as root. With the power comes a great responsibility and regular users should never play with root access.

Yet there's a lot of "yo yo, I just rooted my phone, just because I can" attitude.

Just look at the "SailfishOS pre-pre-release" threads where good amount of users goes through an unnecessary risk and then is surprised when something breaks. There were plans by Jolla last summer to introduce upgrades that would overwrite the system partition so you don't have to hop over updates every time after resetting your phone, but imagine what disaster it would be if they tried to do it and bunch of users went ahead with their

routine prematurely...
</rant>

There should be no "just by being root".

Well, rainisto and Stskeeps both mentioned at some point having it.
However, to the best of my knowledge, both have left the company. :/

I stand corrected and have underestimated a well know effect.



Do you suggest to not even create dedicated posts here on TMO for those topics or how should this be handled ethically correct?