Bricked with 4.0.1 EA

Bug Reports
2

I’ve got into the same. (albeit on Xperia X) Update halfway, try again later …
I’m exploring repair option. Unfortunately I didn’t secure my ssh passowrd.

Fast boot works after some trial and error (had to shutdown completely - VolUp + Power - vibrates once, keepgin buttons for another few secons - vibrates 3 times and shuts down).
Just figured out fastboot blue icon is almost invisible. Managed to boot into recovery following this instructions.

Update (08/02/21):
I’ve managed to recover from broken upgrade successfully.
References I’ve used in the process:

My recovery process was (working on Ubuntu 20.04):

  • boot into recovery enabling sshd, backup nemo user (rather spend another hour and half than be sorry later);
    hint (mount home partition under homefs): ssh root@10.42.66.66 "cd /homefs; tar czf - nemo" > nemo.tgz
    Note: compression is not needed and probably just took some extra time.
  • install zypper & augeas libs;
    I was doing this before I got network up. So I’ve lost quite some time getting right rpm (guessing urls). I have used (3.4 version): augeas-libs, zypper. Suppose I could’ve done pkcon install zypper if I had network up before.
  • link zypper cache: I have mounted home partition on /homefs and binded it into rootfs, linked zypper as per instructed in several other posts
  • zypper dup (I’ve got some 300 packages upgraded, some removed, some dowgnraded), restored zypper cache, rebooted
  • phone booted functional; so I followed by
    devel-su
    pkcon refresh # took quite a while
    pkcon update # was very surprised when I saw some 250 pkgs to be updated; seems it is normal
    Note: pkcon update completed, but also messaged an error at the end about screencast package (kind of scripts issue), discovered two versions installed (.18 & .19), so I removed both by explicit names e.g. rpm -e --noscripts screencast-0.3.0-10.19.1.jolla.armv7hl; not sure how I got into this, but it is kind of unusual. I’m guessing this could be a culprit for a broken upgrade in first place.
  • rebooted again (just in case)

Lessons learned:

  • remember ssh password (recovery would not require using fastboot and recovery image),
  • verify that you have a clean system prior to starting upgrade process (if it was screencast, that the issue was there from before, because I have tryed to deinstall it through warehouse, but didn’t check if operation succeeded; obviously it failed),
  • good old Jolla 1 phone still works surprisingly well and gave me opportunity to reherse my OTP (harbour-sailotp) and password (ownKeepassx) recovery skills. :grinning:
  • learning tons of new stuff along the way.
1 Like