Post 903272 by gsora@bsd.network
(DIR) More posts by gsora@bsd.network
(DIR) Post #903050 by gsora@bsd.network
2018-11-01T14:41:01Z
0 likes, 0 repeats
Welp, looks like my #Jolla device has been definitely bricked. Doesn't boot anymore, and the recovery system asks for an unlock PIN, which I never even set on the OS itself. Looks like there's still no way of manually flashing the device via Fastboot... Sadly I didn't unlock the bootloader back in the days, so I'm not able to boot a custom-made ramdisk. If anybody knows someone/something that would help me getting this thing back alive again, it would be great.
(DIR) Post #903051 by amiloradovsky@functional.cafe
2018-11-01T14:54:10Z
0 likes, 0 repeats
@gsoraI don't understand: "definitely bricked" and "didn't unlock the bootloader" — how did that happen?Usually devices get bricked in an attempt to flash a custom ROM, *after* the unlocking, wrong?
(DIR) Post #903216 by gsora@bsd.network
2018-11-01T15:04:49Z
0 likes, 0 repeats
@amiloradovsky if you set a pin code in the OS, the recovery system (which is a script running in a ramdisk, which accepts command via telnet) will ask for it when you try to either factory reset or unlock the bootloader. I have never set up a pincode but still, the recovery asks for it. Since the only way I have to "reflash the stock OS" is via the factory reset function, I'm stuck with a non-bootable device because I don't have said PIN.
(DIR) Post #903239 by gsora@bsd.network
2018-11-01T15:06:00Z
0 likes, 0 repeats
@amiloradovsky if I had unlocked the bootloader, I could have loaded a custom-made ramdisk with a custom kernel to either bypass the pin check completely, or at least brute force it (5 numbers maximum).
(DIR) Post #903245 by gsora@bsd.network
2018-11-01T15:06:21Z
0 likes, 0 repeats
@amiloradovsky if I had unlocked the bootloader, I could have loaded a custom-made ramdisk with a custom kernel to either bypass the pin check completely, or at least brute force it (5 digits maximum).
(DIR) Post #903272 by gsora@bsd.network
2018-11-01T15:07:56Z
0 likes, 0 repeats
@amiloradovsky you have a maximum of 4 PIN tries before the device locks itself down and forces you to wait 24h. The funny thing is that if you remove the battery for a couple seconds, the 24h lockdown vanishes.
(DIR) Post #903466 by amiloradovsky@functional.cafe
2018-11-01T15:21:47Z
0 likes, 0 repeats
@gsoraNo, I mean how did it get bricked: failed update?What I'm asking, practically: maybe it's a good idea to unlock the bootloader right after the purchase… just for the cases like this?
(DIR) Post #903504 by gsora@bsd.network
2018-11-01T15:24:36Z
0 likes, 0 repeats
@amiloradovsky yes, after a failed system update. Yes, if you want even the slightest chance of recovering your device maybe unlocking the bootloader is the right thing to do.
(DIR) Post #903670 by amiloradovsky@functional.cafe
2018-11-01T15:35:36Z
0 likes, 0 repeats
@gsoraP.S. Of course all these "security" measures are just laughable; adding them, the engineers implement an absurd minimum of what the "spec" requires…The ultimate reason of all this silliness, if you ask me, is the dumbass but pretentious "spec writers", who basically have no idea what is necessary and sufficient for what — in short, incompetent managers.
(DIR) Post #903915 by gsora@bsd.network
2018-11-01T15:48:03Z
0 likes, 0 repeats
@amiloradovsky historically sailfish has been an impressive project, but lacking some fundamental privacy/security functionalities, like VPN or disk encryption. This whole device code system has been enforced in sailfish 2.0. It's just a big patch for a problem that required much more work power and thought. Sailfish 3 is the first ever release employing full disk encryption. I believe they were just trying to emulate the whole Apple/iCloud Lock situation.