Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 19 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 4 hrs ago - more...
djselbeck |
2014-04-18
, 14:44
|
|
Posts: 113 |
Thanked: 303 times |
Joined on Dec 2013
@ Germany
|
#291
|
I can confirm that usb boot doesn't work. Flashing a boot image works but directly booting the same file from usb does not.
|
|
2014-06-26
, 20:13
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#293
|
Originally Posted by szopin
Yeah, seems like I bricked my device to a non-restorable state (including having the device lock my unlocked bootloader during a faulty update)
Soooo.... it has been a while, just wanted to check if any improvements happened on that front?
But, I guess most of you have seen both my twitter feeds and TJC and TMO post on this :/
|
|
2014-06-26
, 20:18
|
|
Posts: 2,076 |
Thanked: 3,268 times |
Joined on Feb 2011
|
#294
|
Originally Posted by nieldk
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)
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 :/
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: | ||
|
|
2014-06-26
, 20:26
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#295
|
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
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: | ||
 |
|
2014-06-27
, 16:01
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#296
|
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.
(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: | ||
|
|
2014-06-27
, 16:55
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#297
|
Originally Posted by javispedro
in fairness to Jolla, that warning is OK,
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.
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: | ||
|
|
2014-06-29
, 14:25
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#298
|
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....
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: | ||
|
|
2014-06-29
, 19:19
|
|
Posts: 39 |
Thanked: 124 times |
Joined on Oct 2009
|
#299
|
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...
|
|
2014-06-29
, 20:25
|
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#300
|
Originally Posted by Nekron
QPST is a great tool, but - not publically avaliable (for d... good reasons LOL)
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...