1.1.0.38 Upgrade problem

Thanks so much @simo, I read that before attempting the update but unfortunately none of the other options are feasible at this stage so I think I'm going to have to go into recovery (not just for my Jolla!).

If you or anyone else has any other bright ideas I'm all ears! Thanks, Timo

OK I removed the battery to go through the recovery mode procedure. When the battery was reinserted the Jolla screen appeared and the phone appeared to boot. When the main screen came up I tried opening Settings but it won't open. The screen also blanks after a few seconds making it difficult to do anything on the screen. It seems from the link you provided that I need to delete /home/nemo/.cache/store-client/os-info and then stop the store process. The problem is doing this when the screen blanks whenever I try and run say file manager. The screen is also showing that an OS update is available.

Do I need to try and access via SSH? If so how do I find the IP to use?

@ninepine Settings (if you get it open) > System > Developer tools > Enable SSH (give a new password, remember it) and you'll see IP for both WLAN and USB (wlan is much easier to access). However, you can delete it also in the Terminal app, just with smaller keyboard in the phone. That's visible in your launcher when you activate the developer tools, but enable SSH connection as well to give the new root password (deleting might require root access)

@JollaTides How's your memory situation?

@ninepine I've decided to leave this to the morning now but will chk back here tomorrow and hopefully we'll find a workaround by then. I've also contacted Jolla in case there's a quick fix and will post here their response. Good luck with it and hope you find a solution in the meantime! :)

EDIT @simo: internal memory had around 3gb so fine :)

@JollaTides@simo Thanks for the pointers. I'm going to have to leave this till tomorrow (evening) now too but I'll see if I can connect to the phone via SSH / Wifi in the meantime. Good luck too!

@Nieldk - that's expect, you can also just use 'devel-su -p' and then use pkcon, wasn't it like that already in update 8 ? can't really remember long time ago :)

@Nieldk were you running Google services before the upgrade? Just want to see if there is a common theme here. As you can see I'm probably going to have to do a factory reset so further information on the conflicting qt5 libraries and whether you had to do anything to overcome that issue would be really helpful please.

@VDVsx In 1.0.8.21 pkcon would run as nemo. (for me at least). @ninepine Google services I suppose was present (from Jolla android support, not the hack for Google Play). There were a bunch of conflicting Qt libraries (not sure if I can get the log again since I reset the device). I know for a fact that I didnt create my 'own' Qt libraries. But it might very well be some from warehouse. I had several apps from openrepos installed, but removed those that I kind of suspect would cause issues (patch manager and patches being the biggest concern that I know could cause issues)

@Nieldk in 1.0.8.21 could worked because you had warehouse installed (it addes policy for nemo user allowing it to use packagekit). After factory reset, there is no warehouse and it's policy, so pkcon fails.