The pics have screenshots from an app (SFOS forum viewer). This app is not a part of SailfishOS. So ask the app developer not Jolla
2 Likes
Maybe one hard question, but are there somebody who could make own device Jolla C2 to the factory reset status and after make some dump of partions (dtbo, system, userdata, etcâŚ) and publish here, that can be so helpfully? @rubdos or @poetaster or @Obikawa or @vlagged or @nthn or anybody else?
You are not logged in on the first screenshot.
Indeed, your question should be moved to a dedicated topic.
1 Like
sorry and thanks for the help.
1 Like
I also got my device today:
Experience:
Arrived with 59% power, put on charge
No SIM inserted
Booted, added 8 security code, completed setup
Networking wasnât functioning, device recommended reboot, rebooted
Asked for passcode on boot, informed that encryption had failed. After that Wizard again.
Next step reboot again and spinner of deathâŚ
1 Like
I can certainly dump some of the mentioned partitions but to what means, if you canât have a flashing mode like fasboot accesible?
2 Likes
first this is a good idea to backup anything you find under /boot
1 Like
There absolutely is a way of downloading images back to the device, if you do not care about your warranty. No device disassembly necessary. As long as you are having one of those âbadâ 5.0.0.5 units, at least.
1 Like
There is no fimage available for the ramdisk to execute a factory reset successfully.
There are no entry points to the recovery menu.
1 Like
The issue with the faulty units (the WiFi not being there) does not seem to be caused by a hardware issue. Having a shell on a âbrokenâ 5.0.0.5 device, I managed to connect to my home WiFi with no issues. This does not help the UI and the âfrontâ part of the system realize it has network connectivity, though.
Having a unit in a âlockedâ state can be salvaged from, temporarily, in a setup like mine, by wiping the sailfish/home logical volume and re-creating a plain EXT4 FS on it. That âresetsâ the deathloop back to the âfirst Wizardâ state (then it goes to the âSecond wizardâ, then to âSpinner of deathâ again).
Inspecting the ext4 FS from a âSpinner of deathâ state, I saw an overly long log from fsck, resolving to an empty FS. Maybe the previously sounded theory about the second call of the Wizard corrupting the file system is close to truth.
Last edit: Looks like connman not being launched is the reason behind the UI giving up on connectivity. If connman is launched, the device is able to connect to everything.
16 Likes
How did you do that, with what tools/sofrwares?
Thanks
3 Likes
Just to be clear, cause it seems like I sent the broken device, it was fixed and sent back to me.
No. I received a new device. The locked device should be soon if not already back at Jolla Devs to understand what is possible to do.
In my humble view, such devices need to be send back to the factory. I donât think you can connect to it unless you undergo some hardware hacking.
And besides the obvious bugs of a non-mature software, there might be things to improve at the hardware factory level too.
2 Likes
I might have missed some of your other posts, maybe elsewhere. How can you connect to a locked device that has no option to enter in recovery mode ? The device is not visible, to a Linux OS for example. How did you do it ?
1 Like
I saw a comment here somewhere that said âlot of people have issuesâ but then again, this is the forum where people mostly come to vent when things go wrong.
So, here is the view from Dublin :
New C2 Arrived, on time, as scheduled, on Thursday.
Shoved a power cable in
Noted it was 54% powered.
I did nothing and carried on for the rest of the afternoon working.
Evening time : 100% charge.
Powered on.
Followed the instruction to the letter.
I am now the owner of a gorgeous Jolla Sailfish device, working and issue free.
This weekend Iâll start setting up like I have my Jolla One.
Canât find Heebo though !!
Happy sailing.
4 Likes
I was reading user meolic question concerning about changing the filesystem encryption pin code not the device pin code.
As far as i am aware this is the only place in the settings where you are given the option of changing a PIN.
I always assumed they were the same thing as you use that code to unencrypt the /home partition on bootup.
1 Like
Hi. I might be wrong. Just does not feel safe or practical to have a ~5 character long password in file system encryption and longer password is not convenient if you need to input it dozen time a day.
1 Like
Opened this morning - same issues as some , no WLAN so device prompts to re-start. No luck, restart again - spinning wheel after security login.
I expected some bugs in operation , but this seems a fail so early in trying to commission the phone.
2 Likes
Is there a clear consensus about first time start up? Or no matter what we do it wil be either ok or get bricked?
1 Like