answered
2014-12-23 11:48:57 +0300
I had this happen as well. The update seemed to go all the way through, but afterward the device showed only a black screen after the Jolla logo. There was some life, however, as the LED was constant white and could be turned off and on with short presses of the power key or off with a double tap on the screen.
I was able to shut down the phone. The LED turned red for a while and then switched off. After a moment the screen reverted to the charger screen; however, it did not seem to respond to connecting or disconnecting the USB cable. I then entered recovery mode as follows: 0) shut down phone, 1) remove USB cable and battery for 10+ seconds, 2) reattach battery and USB cable, 3) press Power and Volume Down keys together until the Jolla logo was displayed together with a solid white light. I had installed the HoRNDIS driver on OS X Mavericks from http://joshuawise.com/horndis to enable USB tethering. The phone appeared as a network device named "Recovery" with the address 10.42.66.66.
I then opened a terminal window and was greeted with the Jolla recovery menu.
$ telnet 10.42.66.66
Trying 10.42.66.66...
Connected to 10.42.66.66.
Escape character is '^]'.
-----------------------------
Jolla Recovery v0.2.7
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset device to factory state
2) Reboot device
3) Bootloader unlock [Current state: locked]
4) Shell
5) Try btrfs recovery if your device is in bootloop
6) Exit
Type the number of the desired action and press [Enter]:
I tried the following options:
- Reboot device (#2). The device rebooted, but the problem wasn't solved.
- Try btrfs recovery (#5). This didn't make any difference, which makes sense, since the phone wasn't in a boot loop.
- Shell (#4). What I wanted was to download the /home/nemo directory, along with the most recent backup, as the next thing I was going to try was a factory reset. Turns out netcat (nc) was available, so this should be easy enough.
On the laptop, I started nc listening to an arbitrary port and had it dump everything to a file:
nc -l 9999 > jb.tar
On Jolla, I made a tar archive of the directory into standard output and redirected it to nc, connecting to the laptop's previously chosen port (the laptop's address was 10.42.66.67):
cd /home/nemo
tar cvf - . | nc 10.42.66.67
On the laptop, I verified the intergrity of the archive by listing its content:
tar tf jb.tar
This isn't foolproof, it doesn't detect corrupted files, but it does act as a check that the archive has actually been made.
After this had finished, I exited the shell with Ctrl-D (the exitcommand works just as well) and was shown the recovery menu again. I now selected option #1, Reset device to factory state. This restored the Sailfish version to 1.0.0.5 and deleted all data and settings. I made the minimal settings outlined in https://jolla.zendesk.com/hc/en-us/articles/201890427 and upgraded the OS first to 1.0.2.5 and then 1.1.1.27. After the last upgrade, I enabled developer mode, SSH connection, and the USB tether (this required a reboot), and uploaded the .vault directory from the previously made archive. The phone appeared now as a device called Sailfish, with the address 192.168.2.15 (which is visible in the system settings). The command I gave on the laptop looked like this:
cat jb.tar | ssh nemo@192.168.2.15 tar xvf ./.vault
In other words, the archive is sent over, and part of it is extracted.
I then went to the Backup menu, where all of my previous backups had become visible. I restored the latest one.
There were a few glitches:
- No apps were installed, nor were they
visible in My Apps in the Jolla
store.
- Linked contacts had to be
relinked, as all links were broken. A
couple of contacts still remain
nameless, they only have numeric FB
id's and unlisted telephone numbers. I am unable to link them to any
others, as a reverse lookup on the
telephone numbers produces no
results.
- Upon restoring the backup,
voicecall-ui started eating hideous
amounts of memory, causing the device
to consume all of its swap. The LED
started flashing rapidly and went
through all sorts of colours.
However, I still had an active ssh
connection, so I didn't touch the
power button. The situation resolved
itself in a few minutes as the memory
hog was killed. Cookies and passwords
seem to have been forgotten in the
browser, i.e. not restored.
my jolla is not working after the last update!! the logo appears at the beginning and that's all. the proximity detector seems working but no more ...black screen ...what to do???? I tryed the recovery mode option (5) to restore but it still not working!
dingo ( 2014-12-23 00:11:48 +0300 )edit@dingo This is not an answer - please convert this into a comment under the question. I hope your issue gets solved!
simo ( 2014-12-23 00:17:05 +0300 )editYea same things on my device and I also tried to fix it on recovery mode but couldn't get it working.
Joel ( 2014-12-23 00:19:14 +0300 )editThe same happened for me. I proceeded to probably irrevocably destroy my Jolla by trying the recovery option that isn't factory reset in the recovery mode. Will have to migrate to Firefox OS as I can't afford a new Jolla at the moment. EDIT: Turns out option 5 doesn't (always) turn your phone into toast. So if you have ended up pressing it accidentally, don't throw your Jolla away yet. ;)
randomstringofletters ( 2014-12-23 00:28:39 +0300 )editmy jolla is not working after the last update!! the logo appears at the beginning and that's all. the proximity detector seems working but no more ...black screen ...what to do???? I tryed the recovery mode option (5) to restore but it still not working!
dingo ( 2014-12-23 00:38:57 +0300 )editSame thing happened to me :( . I didn't check the disk space before (noticed that only after started to read zendesk page 201836347 ) , but I think I was just above the limit. So, I did backup and left phone to update itself, while charging. The end: splash screen is visible, but then screen stays black. If I plug in USB cable, Windows sees sth but can't access the disk. So Care or trying to reset? I had developer mode on if that has any significance.
viuh ( 2014-12-23 02:51:47 +0300 )edit
dez ( 2014-12-23 10:29:18 +0300 )editIf somebody is able to execute commands in the Recovery mode, it is possible to try to execute several commands in the recovery mode shell to try to detect the root cause.
If somebody is living near Helsinki or Tampere and can deliver device to the Jolla office to check, it can be also an option,
You can wait until investigation will be done and maybe some way to reanimate device will be found,
You can perform factory reset.
Also, there is a advice before you go for the options listed above to try to boot device after upgrade several times. So, if device is booted to the black screen, long press for power off, wait until device shuts down, power on again and wait. Only if several tries are failed, options above are in force.
dez ( 2014-12-23 10:51:31 +0300 )editSame situation here. Used a new phone for one week without issues, then updated to 1.1.1.27 yesterday. Noticed that some Android-apps weren't working any longer. After rebooting phone this morning, it didn't boot any longer, just stays in the logo screen.
I can access recovery mode with telnet, but the phone doesn't seem to respond to any recovery commands.
chroniz ( 2014-12-23 11:02:29 +0300 )editMy experience:
I left the Warehouse repos on which was a bit of a ** move, shouldn't have been trying to update at 1 in the morning.
Progress bar went half-way, then the phone rebooted, then blank screen...off.
Got it into recovery, reset it to factory settings, reboot (presumably it was now 1.0.2)
Phone is now in boot loop, and recovery is broken. I cannot complete the device setup without it rebooting. Re-inserting the battery immediately puts it into normal boot cycle even before I push the power button.
Paspie ( 2014-12-23 15:40:00 +0300 )editSure recovery mode is broken? I also needed several tries to get the right timing to reach it.
Halo2 ( 2014-12-23 17:12:52 +0300 )edit