Ask / Submit
4

HELP! 1.1.4.29 almost bricked my device [answered]

asked 2015-04-28 14:05:14 +0200

objectifnul gravatar image

updated 2015-04-30 01:24:49 +0200

Deep trouble. Just upgraded to 1.1.4.29. No display after boot, screen unresponsive except swipe from top (lock image briefly displayed). Black screen so no unlock. However SSH access still possible from PC (Putty). PowerMenu appears when power button is pressed, but no powermenu command does anything. Double press on power button turns "Torch" on (as this is what my powermenu options are supposed to do).

What can I do from Putty terminal to unlock my device? (already removed the battery, doesn't help)

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by simo
close date 2015-08-15 01:11:05.634577

Comments

By PowerMenu, do you mean this one? http://talk.maemo.org/showthread.php?t=93587 Did you disable Openrepos repositories before updating?

simo ( 2015-04-28 14:22:19 +0200 )edit

Yes, CodeRus' powermenu2. No, I didn't disable openrepos repositories. I thought 1.1.4.28 to 1.1.4.29 was just a minor update (it was much faster than previous upgrades). ssu and pkcon commands still accessible from Putty.

objectifnul ( 2015-04-28 14:27:54 +0200 )edit

ALWAYS good to disable, and especially when separately mentioned in the release notes. Hmm... Luckily you can SSH, so try disabling them via terminal and after that do version --dup to try to fix the update. However, I'm not sure if the repositories are the reason for your issue, but I'd say it's a very possible candidate.

simo ( 2015-04-28 14:32:49 +0200 )edit

Okay, but disabling repositories won't uninstall anything I guess. It will just prevent from updating installed apps and patches. Is there a terminal command to remove all patches without knowing their exact names?

objectifnul ( 2015-04-28 14:38:09 +0200 )edit

True... About removing all at once, that's possible only if they would have same part in their names in each (and you'd still need to know that part), and that part was also unique to patches only... I suggest listing your installed patches here or at TMO and ask nicely if @coderus has a command or two for you. Openrepos itself shouldn't be the problem, but that you had patches installed might be.

simo ( 2015-04-28 14:45:50 +0200 )edit

3 Answers

Sort by » oldest newest most voted
5

answered 2015-04-28 15:24:33 +0200

simo gravatar image

updated 2015-05-03 10:39:56 +0200

Solved in comments with help from @coderus , the reason to the problem was that patches were not reverted before updating the system.

EDIT: Question reopened, as there's still a compatibility issue. Reverting the patches in advance enables updating the system, so no problem in the update itself, but one or few of the patches remains non-compatible with this SFOS version (1.1.4.29) and those patches shouldn't be reapplied until the patches itself are updated too.

edit flag offensive delete publish link more

Comments

Note: all patches I mentioned are working with 1.1.4.29 provided they are activated separately. The compatibility issue, if any, only appears in the activation process.

objectifnul ( 2015-05-03 12:11:56 +0200 )edit

I have the same problems but had disabled them in patch manager (not uninstall them) before updating. I did not disable the respective repositories. In release notes, it was only mentioned that Phonehook (whatever that is) repositories should be disabled. I don't understand what you mean by "reverting" patches.

bennypr0fane ( 2015-05-06 14:21:49 +0200 )edit
1

answered 2015-04-29 23:25:41 +0200

objectifnul gravatar image

updated 2015-04-30 13:29:47 +0200

Anyway the same issue happens again if I reapply all installed patches in the same session (black screen after boot, so pkcon install lipstick-jolla-home-qt5 jolla-settings-system jolla-settings-bluetooth jolla-settings-networking. reboot, then unlock screen is normal but all patches are now disabled although they still appear "active" in settings/patchmanager. Must then force all patches to "disabled" and reboot.

Then I re-activate patches one by one and reboot after each of them. This is he only way I found to have all patches back without the damned unresponsive black screen (BSOD?)

Probably one patch has a compatibility issue (at least during the activation process) with some other, however the possible combinations are so numerous that I'm unable (or too lazy) to check all of them pair by pair (I use 9 patches, so I should check 36 pairs; 45 pairs for 10 patches).

So I disagree with the sentence "the problem was that patches were not reverted before updating the system". The problem occurs with or without system update when patches are disabled then reactivated without caution. Compatibility issues between released patches need investigation.

edit flag offensive delete publish link more

Comments

As a reminder, this is the list of patches I am using:

  • Wallclock
  • Browser text selection
  • Launcher combined patch
  • Eventsview controls
  • Battery StatusBar on lockscreen
  • Add Sneak Peak option to display settings
  • Show month and days of the week heading in Calendar
  • Lockscreen voicemail notification
  • Meecast-lockscreen
  • Disable volume warning

Reproducible issue: disable all patches, reboot, enable all patches above, reboot.

NOTE: to disable/enable "Battery StatusBar on lockscreen" you must first erase "/usr/share/lipstick-jolla-home-qt5/lockscreen/BatteryStatusBar.qml"

objectifnul ( 2015-04-30 13:19:58 +0200 )edit

After various tests, my primary suspects are "Battery StatusBar on lockscreen" and "Lockscreen voicemail notification". Not sure though. However, obviously lockscreen-related patches are to be investigated first.

objectifnul ( 2015-04-30 13:33:24 +0200 )edit

Yes, I was able to get it working by commenting out BatteryStatusBar in /usr/share/lipstick-jolla-home-qt5/lockscreen/Lockscreen.qml. I had to do it through recovery mode and then mount mmcblk0p28 to get to the file. Should have thought of reading about it here first... but found it by checking modified date of files.

shellkr ( 2015-05-03 01:48:14 +0200 )edit

@objectifnul Question reopened and the previous answer edited, thanks for your updates. I guess we'll first need to wait for the public SFOS release (which might be other but 1.1.4.29), and then wait for the patches to be updated for that release.

simo ( 2015-05-03 10:38:56 +0200 )edit
0

answered 2015-04-30 14:50:22 +0200

Maus gravatar image

updated 2015-04-30 14:55:43 +0200

Before applying patches, upgrading your system or using pkcon, your phone has to be in a consistent state. With active patches, overwriting files (pkcon/system update) may corrupt patchmanager's knowledge about your files' content. On the other hand, (partially) re-writing files during a system update or with pkcon while patches are active may also cause inconsistencies that render your phone unusable. So please only use pkcon / system update on an unpatched phone unless you know you don't cause inconsistencies (e.g. if pkcon actions don't interfere with installed patches).

edit flag offensive delete publish link more

Comments

In other words, performing 'version --dup' with zero patch enabled should make my system clean and consistent, right?

objectifnul ( 2015-04-30 15:25:38 +0200 )edit

Sorry for nit-picking, but: no. While this sounds sensible, this cannot be derived from my words (“In other words”).

Maus ( 2015-04-30 17:30:12 +0200 )edit

Question tools

Follow
2 followers

Stats

Asked: 2015-04-28 14:05:14 +0200

Seen: 1,407 times

Last updated: May 03 '15