Recovery not working after update 2.1.4.14

asked 2018-03-11 21:06:08 +0300

Amboss gravatar image

updated 2018-03-24 10:11:02 +0300

objectifnul gravatar image

Yesterday I installed the latest update on my Jolla 1 after clearing all patches and even rebooting. Update went through fine. So I started activating some of the patches from patch manager. This broke lipstick I guess, cause after I rebooted again, the PIN mask came up and if I was fast enough I passed SIM-PIN as well. But it rebooted again. I found out, that If I wait longer, it reboots before I enter the PIN, too.

I know using patches is a bit risky but there is recovery mode which I happened to need quite often in the last 5 months and that not for the patches but some filesystem issues. Well, there was recovery mode.

My phone is not going there anymore! I am so annoyed because of all the issues I had (hardware replacement, 3x btrfs write issues to recover) and now I can't even get to a point where I could fix things!

Does anyone know, why recovery mode won't start?

EDIT to answer a question: Actually, I am not even sure, if it recognizes my attempt. It feels more like always regularly booting. I press volume down (either while inserting battery or right aftewards) and holding it power. Then it vibrates. Up to that point it looks like its going for recovery mode. But when I put in USB nothing happens, instead it continues as it did when not pressing volume down, booting to lipstick. Fastboot comes up fine though.

edit retag flag offensive close delete

Comments

On which step did you get stuck? I tested on my Jolla1 and can confirm recovery mode is still accessible for me on 2.1.4.14. https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode

Carl ( 2018-03-11 21:43:05 +0300 )edit

Generall speaking, recovery mode does work on Jolla1 running 2.1.4.14.
https://jolla.zendesk.com/hc/en-us/articles/204709607-Jolla-Phone-How-to-use-Recovery-Mode

If it does not work on your device, make sure you have a proper USB cable with data line connected. Or if you use WLAN make sure your computer and phone are connected to the same IP address (given in Settings > Developer tools > WLAN IP address. If you use a Windows computer then it is good to check the RNDIS settings in Device Manager.

jovirkku ( 2018-03-11 22:08:04 +0300 )edit

@Carl: see edit in my original post for answer.

Amboss ( 2018-03-11 23:18:28 +0300 )edit
1

@Amboss:

  1. Detach battery from Jolla1. Detach USB cable (if connected).
  2. Press VolDown key and keep it pressed.
  3. Intert battery while you continue keeping VolDown key pressed.
  4. Press Power key and keep it pressed (also VolDown key must be pressed) until you feel the vibra play.
  5. Release both keys.
  6. Connect USB cable between Jolla1 and computer - nothing happens at this point.
  7. Create a telnet session to address 10.42.66.66 from you computer. Recovery Mode menu should appear at computer terminal window.
jovirkku ( 2018-03-12 13:01:44 +0300 )edit

@jovirkku: Thx for trying to help. I am familiar with this procedure. Believe me, in the last 6 months after I had my mainboard replaced, I have been using it more often than I would wish for.

Got my phone back in septembre, first crash happened in octobre. It took me 2 weeks to find out, that most recovery options are sh** because they break phone more. The routine I found working I had to use end of novembre then again in january. It is as if the phone has btrfs failures every 2 months.

Every time it was:

  1. dd /dev/mmcblk0p28 to sd
  2. create new image with new btrfs layout on laptop
  3. btrfs restore from sd to new fs (this didn't work on the phone because of the old btrfs version!)
  4. adjust settings (set root for btrfs, UUID, ...)
  5. copy new image back to phone via sd

so step 1 and 5 were in recovery mode on any of those 2-monthly occasions

While mmcblk0p28 btrfs failed me all those times, recovery mode never failed me. So now, the main fs is coming up with settings broken and recovery partition is dead it seems.

@all: thx for confirming that it is probably not an issue of the new 2.1.4 version updated

Amboss ( 2018-03-12 22:39:16 +0300 )edit