[HOWTO] Comprehensive Firmware Flashing Guide for Jolla - Page 30 - maemo.org

djselbeck | # 291 | 2014-04-18, 14:44 | Report

I can confirm that usb boot doesn't work. Flashing a boot image works but directly booting the same file from usb does not.

szopin | # 292 | 2014-06-26, 19:52 | Report

Soooo.... it has been a while, just wanted to check if any improvements happened on that front?

The Following User Says Thank You to szopin For This Useful Post:
jalyst

nieldk | # 293 | 2014-06-26, 20:13 | Report

Originally Posted by szopin View Post

Soooo.... it has been a while, just wanted to check if any improvements happened on that front?

Yeah, seems like I bricked my device to a non-restorable state (including having the device lock my unlocked bootloader during a faulty update)
But, I guess most of you have seen both my twitter feeds and TJC and TMO post on this :/

The Following 5 Users Say Thank You to For This Useful Post:
jalyst, juiceme, MartinK, Nekron, szopin

szopin | # 294 | 2014-06-26, 20:18 | Report

Originally Posted by nieldk View Post

Yeah, seems like I bricked my device to a non-restorable state (including having the device lock my unlocked bootloader during a faulty update)
But, I guess most of you have seen both my twitter feeds and TJC and TMO post on this :/

Sorry, didn't see your tmo post, just thought it might be a good idea to revive this. Quite a lot of time passed, jolla promised improvements, I myself am hoping this to improve soon, been so scared of bricking that I'm not blindly replacing libs by debian ones like I used to on n900 (which absurdly enough only once caused reboot loop with glibc, maybe libglib? srry don't remember now)

Last edited by szopin; 2014-06-26 at 20:34. Reason: probably libglib rather

The Following User Says Thank You to szopin For This Useful Post:
jalyst

nieldk | # 295 | 2014-06-26, 20:26 | Report

Short version
Device rebooted during update
Device is in boot-loop
Bootloader became re-locked (shouldnt happen)
I cant get into Jolla's recovery

While I have dd images of all partitions, I have no way to put them back on device since fastboot is now crippled with restrictions

The Following User Says Thank You to For This Useful Post:
jalyst

javispedro | # 296 | 2014-06-27, 16:01 | Report

And this is why, when I see the stupid "unlocked" red warning while booting, instead of thinking "OMG some cracker is stealing my internets", I actually feel more safe.

(Even if I'm not booting a custom kernel at the moment)

Makes one wonder why they added that warning in red letters.

Last edited by javispedro; 2014-06-27 at 16:04.

The Following 3 Users Say Thank You to javispedro For This Useful Post:
reinob, ZogG, zxcvbnm3230

nieldk | # 297 | 2014-06-27, 16:55 | Report

Originally Posted by javispedro View Post

And this is why, when I see the stupid "unlocked" red warning while booting, instead of thinking "OMG some cracker is stealing my internets", I actually feel more safe.

(Even if I'm not booting a custom kernel at the moment)

Makes one wonder why they added that warning in red letters.

in fairness to Jolla, that warning is OK,
But, that being said, the poor design (you can totally make a brick locked or unlocked, just enabling dev mode and do (DONT) df if =/dev/random of=/dev/mm...blk0..) makes that warning quite the opposite. Should be a 'congratulations, you can recover a brick' LOL

The Following 3 Users Say Thank You to For This Useful Post:
jalyst, Nekron, peterleinchen

javispedro | # 298 | 2014-06-29, 14:25 | Report

In fairness to Jolla too, overwriting the entire eMMC/NAND with random values also bricks any Maemo device to date, save for the N900 for which some people found how to coldboot (which is similar to fastboot, AFAIK).

Recovery is hard (albeit seemingly possible as seen in this forum) _unless_ you made an image of the entire eMMC/NAND, since the public images for Maemo don't contain all partitions either.

The only difference with Jolla is that instead of shipping incomplete images Jolla doesn't ship _any_ image at all.

On an unrelated topic, since the Qualcomm bootloader tries to parse the GPT, which is a somewhat complex data structure, I ponder how much garbage you need to write to the eMMC until you hit a qcom bug and create a TRUE brick....

The Following 4 Users Say Thank You to javispedro For This Useful Post:
jalyst, Nekron, peterleinchen

Nekron | # 299 | 2014-06-29, 19:19 | Report

Mhh... what about overwriting your fastboot bootloader with rnd() values? Isnt it bricked then and can not be recovered since fastboot is no longer working... QPST to the rescue... but how...

nieldk | # 300 | 2014-06-29, 20:25 | Report

Originally Posted by Nekron View Post

Mhh... what about overwriting your fastboot bootloader with rnd() values? Isnt it bricked then and can not be recovered since fastboot is no longer working... QPST to the rescue... but how...

QPST is a great tool, but - not publically avaliable (for d... good reasons LOL)