In my case it was possible to charge without the phone booting automatically. In fact, I let the phone to charge, almost fully, before booting the phone. The setup process and update to .21 was smooth.
I guess the bug is in the setup process when interrupted abruptly, eg shutdown on low battery?
mine had full battery, i made 5x digits code, it started with no wifi. i restarted it and got an encryption error. after reboot → asks for the code, you enter the code and get endless spinning circle.
I managed to pass all the potholes and got through the initial setup by just dismissing Wifi connection altogether.
Was in a hurry to see the new Sailfish 5 desktop and did not want to tinker with my long Wifi password so I skipped setting network connections at all and had no SIM card.
I did Wifi settings only after first reboot.
Everything went fine. My troubles started only after failed update attempt.
I am using an 8-digit code, I’ve activated wifi and jolla account during the setup, and then went through the tutorial. I think at that point it got an upgrade notification to .21 which I followed. No resets before that. During the OS upgrade the phone rebooted a couple of times.
The phone works fine since then and I have rebooted it, for other reasons, several times without issues.
Hello,
I have used during the first boot a code with a letter of my language (not English).
I followed all the steps in the tutorial and can activate the jolla account, use the wifi and install applications by default. The phone could be locked and unlocked perfectly and everything seemed ok.
Today I downloaded the pending update and when I reboot for the first time it turns out that to enter the code the keyboard is English and does not appear the letter of my language, so I can not unlock the phone and therefore does not boot. I have tried to connect a keyboard but I only write numbers not letters, I have also tried to induce many failures with the idea that all failed attempts will be erased and can start again but it does not work.
Does anyone have any idea if I can do anything else or will I have to send it to be re-flashed?
Thank you very much.
Regards.
Good news, look at the second-to-last paragraph of the letter attached to @NikosAlexandris’ new, debugged C2 (to Finland and back in only 3 days):
“We’re working to deliver recovery mode via over-the-air software update.”
So it looks like once you get your C2 to work, any future bricks should be salvageable without sending it in for repair. At least, once said software update is out.
@meolic: Thank you for your advice.
It worked all as you mentioned! Now I have the feeling that it runs smoother as with the initial version 5.0.0.5.
How? If there is no internet connectivity?
imho i think it would be better, everyone would enter a very simple unlock code like 55555 or so for the first tests and no letters, until a stable state is reached, to avoid problems with keyboard layouts/languages, if it changes itself, or also if the touchscreen is unresponsive. (I would do so)
It can be changed later.
i just changed the PIN in Settings > Device lock > Change security code twice without anything being deleted
Is it normal that the C2 doesn’t show the same options as the Xperia10? It’s also not possible to write answers on my C2.
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
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.
sorry and thanks for the help.
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…
I can certainly dump some of the mentioned partitions but to what means, if you can’t have a flashing mode like fasboot accesible?
first this is a good idea to backup anything you find under /boot
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.
