Ask / Submit
2

Stuck on 1.0.7.16 after Factory reset [answered]

asked 2016-01-24 15:35:26 +0200

cocof2001 gravatar image

updated 2016-01-25 12:27:49 +0200

Hello,

I was on 2.0.0.10 (Saimma) and wanted to go for 2.0.1.7(early access). Optimization failed a lot and then I decided to free up some space (during optimization). I had some sort of a soft reboot and then black screen. Tried option 5 in recovery but it was doing nothing. Went for the shell and tried btrfs check and repair but it was showing full of errors and then decided to go for Factory Reset.

Ok, Factory reset worked, but then I was in 1.0.7.16 and never got to upgrade to 1.1.2.16. It will always die during the upgrade. I tried to get some logs but journalctl does not show much. From my last attempt using ssu re 1.1.2.16 and version--dup I got this before it died and entered bootloop:

Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1795589 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1795639 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1795728 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1795866 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1795913 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1796004 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1796083 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1796176 Jan 24 15:06:45 Jolla ambienced[993]: [D] FileManager::event:299 - FileManager idle in 1796243 Jan 24 15:06:46 Jolla packagekitd[2949]: Install progress update: 76 of 501 Jan 24 15:06:47 Jolla packagekitd[2949]: Install progress update: 77 of 501

[root@Jolla nemo]# ssu re 1.1.2.16 Changing release from 1.0.7.16 to 1.1.2.16 Your device is now in release mode! [root@Jolla nemo]# version --dup Refreshing cache Waiting in queue Waiting for authentication Waiting in queue Starting Refreshing software list Getting upgrades Waiting in queue Waiting for authentication Waiting in queue Starting Refreshing software list Resolving dependencies Installing updates Downloading packages Installing packages [=== ] (15%)

It looks kind of ok when running in 1.0.7.16 What now?

Update: I read a lot of threads here and I tried to do a btrfs balance and then the phone rebooted to go again in bootloop. The image of 1.0.7.16 didn't work anymore after a new factory reset. Read again through threads and ended up doing some btrfs scrub. Found 21 errors that can not be fixed. Ok... A new try to reboot the phone and I am back at 1.0.7.16. This looks more like an internal memory corruption. Anyone had the same problem? If this is the case is it possible to create some working file system on the memory card and go with that?

Update: My last try at getting to upgrade to 1.1.2.16 before waiting for professional help as stated by chemist. Upgrade from GUI rebooted the phone at around 15% and then I was in a state where GUI was flashing for a few times and then blackscreen (had some error about display in journalctl). Went for the debug mode:

[root@Jolla nemo]# version --dup Refreshing cache Waiting in queue Waiting for authentication Waiting in queue Starting Refreshing software list Fatal error: Download (curl) error for 'https://releases.jolla.com/jolla-apps/1.1.2.16/armv7hl/repodata/repomd.xml': Error code: Connection failed Error message: Couldn't resolve host 'releases.jolla.com'

Getting upgrades Waiting in queue Waiting for authentication Waiting in queue Starting Refreshing software list Resolving dependencies Installing updates Installing packages [================ ] (78%)

Jan 25 11:26:58 Jolla packagekitd[2912]: Install progress update: 330 of 423 Jan 25 11:26:59 Jolla booster-silica-qt5[1534]: Failed to load platform plugin "wayland". Availabl...re: Jan 25 11:26:59 Jolla kernel: booster-silica-(8713) send signal 6 to booster-silica-(8713) Jan 25 11:26:59 Jolla mapplauncherd[8705]: Booster: Failed to invoke: Booster: Loading invoked ap...Eii' Jan 25 11:26:59 Jolla mapplauncherd[946]: Boosted process (pid=8705) exited with status 1 Jan 25 11:26:59 Jolla invoker[8702]: Failed to invoke: Booster: Loading invoked application faile...Eii' Jan 25 11:26:59 Jolla systemd[870]: voicecall-manager.service: main process exited, code=exited, ...LURE Jan 25 11:26:59 Jolla invoker[8702]: invoker: Invoking execution: '/usr/bin/voicecall-manager' Jan 25 11:27:00 Jolla systemd[870]: Unit voicecall-manager.service entered failed state. Jan 25 11:27:01 Jolla systemd[870]: voicecall-manager.service holdoff time over, scheduling restart. Jan 25 11:27:01 Jolla systemd[870]: Stopping Voicecall manager... Jan 25 11:27:01 Jolla systemd[870]: Starting Voicecall manager... Jan 25 11:27:01 Jolla systemd[870]: Started Voicecall manager. Jan 25 11:27:01 Jolla booster-silica-qt5[1534]: Failed to load platform plugin "wayland". Availabl...re: Jan 25 11:27:01 Jolla kernel: booster-silica-(8721) send signal 6 to booster-silica-(8721) Jan 25 11:27:02 Jolla invoker[8715]: /usr/bin/connectionagent: symbol lookup error: /usr/lib/libQ...nEii Jan 25 11:27:02 Jolla mapplauncherd[946]: Boosted process (pid=8737) exited with status 127 Jan 25 11:27:03 Jolla invoker[8715]: invoker: Invoking execution: '/usr/bin/connectionagent' Jan 25 11:27:03 Jolla systemd[870]: connectionagent.service: main process exited, code=exited, st.../n/a Jan 25 11:27:03 Jolla systemd[870]: Failed to start Connection Agent. Jan 25 11:27:03 Jolla systemd[870]: Unit connectionagent.service entered failed state. Jan 25 11:27:03 Jolla booster-silica-qt5[1534]: Failed to load platform plugin "wayland". Availabl...re: Jan 25 11:27:03 Jolla kernel: booster-silica-(8741) send signal 6 to booster-silica-(8741) Jan 25 11:27:04 Jolla systemd[870]: connectionagent.service holdoff time over, scheduling restart. Jan 25 11:27:04 Jolla systemd[870]: Stopping Connection Agent... Jan 25 11:27:04 Jolla systemd[870]: Starting Connection Agent... Jan 25 11:27:05 Jolla booster-silica-qt5[1534]: Failed to load platform plugin "wayland". Availabl...re: Jan 25 11:27:05 Jolla kernel: booster-silica-(8747) send signal 6 to booster-silica-(8747) Jan 25 11:27:06 Jolla mapplauncherd[8744]: Booster: Failed to invoke: Booster: Loading invoked ap...Eii' Jan 25 11:27:06 Jolla invoker[8740]: Failed to invoke: Booster: Loading invoked application faile...Eii' Jan 25 11:27:06 Jolla mapplauncherd[946]: Boosted process (pid=8744) exited with status 1 Jan 25 11:27:06 Jolla invoker[8740]: invoker: Invoking execution: '/usr/bin/voicecall-manager' Jan 25 11:27:06 Jolla systemd[870]: voicecall-manager.service: main process exited, code=exited, ...LURE Jan 25 11:27:06 Jolla systemd[870]: Unit voicecall-manager.service entered failed state. Jan 25 11:27:06 Jolla systemd[1]: Job dev-zram1.device/start timed out. Jan 25 11:27:06 Jolla systemd[1]: Timed out waiting for device dev-zram1.device. Jan 25 11:27:06 Jolla systemd[1]: Dependency failed for Enable/disable zram swap target. Jan 25 11:27:06 Jolla systemd[1]: Job dev-zram0.device/start timed out. Jan 25 11:27:06 Jolla systemd[1]: Timed out waiting for device dev-zram0.device. Jan 25 11:27:06 Jolla systemd[1]: Dependency failed for Enable/disable zram swap target.

Then again phone rebooted and blackscreen and I will stop here with the trial and error.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by nthn
close date 2017-03-04 13:00:54.789772

Comments

You've probably tried removing the batter for another 30min + holding now and then the power button? Good luck mate!

kuzeyron ( 2016-01-26 04:36:24 +0200 )edit

2 Answers

Sort by » oldest newest most voted
5

answered 2017-03-04 08:04:12 +0200

cocof2001 gravatar image

I finally solved the problem by using the "jollarecovery" image that is hard to find on the internet. (don't bother to open a ticket as jolla care will only provide the solution to send the phone in service)

Thanks to "CODERUS" I managed to dd the /dev/mmcblk0p28 and I have a working phone again.

The updates are also working, although it is a long way to get to the final version (not to mention that I had to go through one version --dup for one of them - ssu customer-jola authentication issue).

I'M HAPPY AGAIN! :)

PS I know there are some legal issues with this recovery image, but Jolla should really provide an EASY OFFICIAL WAY to recover our phones.

edit flag offensive delete publish link more
1

answered 2016-01-25 11:32:32 +0200

chemist gravatar image

Keep calm, some Jolla folks are investigating as you should be presented another version, so wait for it please.

edit flag offensive delete publish link more

Comments

@chemist

I am calm now :)

cocof2001 ( 2016-01-25 12:29:18 +0200 )edit

Does anyone have the recovery image for Jolla? I know this one is not available in public, but I read that some people managed to restore their phones using this solution.

cocof2001 ( 2017-03-03 01:02:23 +0200 )edit

Question tools

Follow
1 follower

Stats

Asked: 2016-01-24 15:35:26 +0200

Seen: 507 times

Last updated: Mar 04 '17