For me, updating immediatelly and BEFORE first reboot worked OK. During the update process, the phone will rebooted twice (if I remembered).
2 Likes
Is changing PIN later possible or it will delete all your data? - which is not problem in this beta testing of initial setup.
Iâm not sure good question. Iâll dig out documentation to see if itâs possible to change it, be really strange youâre not allowed to do so!
The device arrived today discharged. The screen was completely off when taken out of the box. I must have inadvertently pressed some language and then the phone turned off. After charging, there is a choice of language again, but with a blue stripe at the top. Nothing else reacts, it just turns off.
@Jolla please update your instructions. It seems you rushed to get the device to our hands and you have skipped proper testing to the point that lots of us are getting devices that are designed to get borked on the first boot.
For anyone who is getting their device now, connect your charger and let it charge for at least 20 minutes before even interacting with it. For some odd reason when the charger is connected the phone boots automatically to Sailfish instead of the special boot loader state where it only charges.
There is no indication during the first boot and the setup/tutorial about how much battery is left. If like me you selected a language and accepted the terms and conditions without letting the battery get some juice first to probably pass the 10% mark, the phone will automatically turn off on the next step where it starts encrypting. This happens REGARDLESS IF YOU HAVE A CHARGER CONNECTED OR NOT. I had a type-c cable connected to the 65W PD type-c port of a PinePower, and it was providing 5V and 2A which means the device doesnât support fast charging or any of the higher voltage UBS PD specs. Either during the encryption process, the phone reached a point where it was consuming more power than it was receiving from the charger, or the check on how much battery was left isnât triggered until that point which results in a borked device.
If you boot the device again then the touch screen wonât be responding to your interactions. Me and a few other people tried connecting a USB mouse/keyboard which lets you move to the next step and select a language. Encryption will fail and then you will be asked to set a pin. Now you have the keyboard bug here letting you enter a 4-character pin when you shouldnât but even if you set a longer pin (7 characters in my case) the phone is still borked as networking is not working at all (WiFi or ethernet through usb) and dev mode canât be enabled without internet. Even worse when you next reboot the phone even if you set a pin longer than 5 chars the phone will stuck in an infinite loading state. The touchscreen will be responding thoughâŚ
Itâs been a week since this bug has been mentioned with a clear ask for instructions on how to reflash sailfish but we havenât had a proper reply or instructions on how to deal with it. On your [Release notes] Tampella 5.0.0.21 for Jolla C2 is explicitly mentioned:
NOTE 3:
The Jolla Shop has the images of the latest OS release only. Keep the previously downloaded ones stored on your computer if you should want to reflash one of them later on.
Which seems to be just copy paste from previous release notes as this doesnât apply to the C2.
Please JOLLA update your instructions ASAP. The last thing anyone here wants is for you to spend more time and money on arranging devices to be sent back to you to be fixed instead of fixing Salfish bugs and evolving the OS further.
9 Likes
I think if they could - they had offered this solution.
First devices (including mine) with the âspinning circle of deathâ bug are already on the way back to Jolla for Reflash/Exchange.
We donât know yet why Jolla doesnât offer this possibility, it can have many roots:
-
C2 is not Qualcomm SoC and could not be flashed the simple fastboot way like Sony Xperia Devices.
-
Special Hardware / Software needed for Flash
-
They are not allowed to redistribute Firmware Images
I also wish a clear statement from @Jolla, why Self-Flashing is not possible and that all folks with unusable C2 should contact Jolla Zendesk and send the phone back for reflash/exchange/repair whateverâŚ
3 Likes
This is really worrying. Both the original Jolla and the first Jolla C had a recovery mode where you could technically return to the factory firmware while wiping all data - so not having redistributable images for those phones was fine as you could always use recovery mode.
So if we donât even have that option for C2 then this is a huge oversight as things can go wrong and will go wrong based on past experience with Sailfish firmware upgrades.
It also makes the device even less appealing compared to any of the Sony offerings.
2 Likes
Hello @spienima @rainemak, please could you publish to the community just a part of firmware for Jolla C2 5.0.0.5, juste a partitions concerns only SailfishOS datas to solve problem of bootloop, and after have to possibility to upgrade to 5.0.0.21? Is the solution acceptable by Jolla or Jollyboys company?
Again, this is only MY OWN SPECULATIONS. We donât know the real reasons for sure.
i hope they will add recovery mode with new versions
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.
1 Like
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.
2 Likes
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.
1 Like
@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
2 Likes
