yes. atm its a lottery. some devices works, but many ending in spinning circle of death (Schrödinger’s brick)
Mine arrived today, plugging it in revealed it was at 50% battery, I charged it to 100% (as someone else already wrote, the percentage only gets updated when you unplug the cable), then turned it on, encryption took a couple of seconds, and now it appears to be working fine. Still have to update, but considering everything went well so far, I don’t think it’ll suddenly decide to brick.
Perhaps the charging to 100% is important (or at least helpful), as all the posts I’ve read where people charge it to 100% haven’t had a brick.
I’ll also note that my C2 was turned off in the box, and inserting the charger made it go directly to the charging screen, it didn’t try booting.
I do not recommend performing the same procedure as I did, so I am not going to document it. But it is a known software issue of some Unisoc devices with old BSP, documented plenty. I got my device for development purposes, so I voided my warranty, do not do what I did. Please refer to the official support channels for device recovery.
Can you please shortly explain how you connected to a locked device ? I am curious.
Huh, you basically used an exploit good job:)
i would say - some sort of serial console pins on the mainboard. for serial communication only 3 connections are needed - RX, TX, GND.
Without translation couldn’t work out whether battery terminal became detached from motherboard during disassembly or whether a likely scenario if device is dropped in use. There wouldn’t be enough time at Support Days if disassembly was required for repair.
Jolla managed to build a first true quantum smartphone! Never underestimate finnish people:)
The guy doesn’t know what a hairdryer is!
i have the exact same issue, not sure how to make progress
just opened a Zendesk case with Jolla
That is the right proces.
I am afraid you will need to send it back though.
Is it already possible to install chum gui with sailfishos-chum-repo-config-0.6.8-1.4.1.jolla.src.rpm on the C2?
My understanding is that if you can’t connect to the internet to setup your account and update to 5.0.0.21 before reboot, you’re screwed.
But if what @lineprinter says is true and you can enable developer mode, enabling connman from the command line might save your device?
But that’s just speculation on my part.
If something going wrong with encryption (like in my case and in case of many others) - i doubt that Update to 5.0.0.21 will save you from the spinning circle bug - but well - its a valid option to try.
I think the encryption issue arise when it tries a second time to encrypt it. At least for me, I could unlock the phone after the first reboot, before it tries to perform the initial setup again.
Anyway, someone also reported not being able to enable developer mode so this workaround may not be possible at all.
I plugged the charging cable into the device and turned on the power. I selected the language and the device started encrypting and immediately reported 0% power. The device turned off the power. I let the device charge 100% and turned it on and when the device got to the language selection it did not reaggress in any way. I turned power on and off many times and same situation. I sent a query to Jolla on how I can send C2 back.
Some people worked around the not working touch panel by connecting a usb mouse through a usb-c dock, if you have one, give it a try
I have only usb A mouse. I think phone is useless if touching is not working.