We have moved to a new Sailfish OS Forum. Please start new discussions there.
5

Issue when restarting xperia 10 plus

asked 2019-12-01 23:48:36 +0200

rubyhorse gravatar image

My xperia 10 plus had been running smoothly for a few days. Today when I restarted it after the sony logo the LCD seems to be at maximum brightness but displaying "black" and the LED is stuck in white.

Any ideas, it seems like a re-flashing kinda solution :/

edit retag flag offensive close delete

Comments

After 2 weeks of usage I'm facing the same problem. did a reboot and now this :(

luchmhor ( 2019-12-03 14:18:52 +0200 )edit
1

Yeah I had to reflash and start from scratch... this version of sailfish is starting to seem too alpha... no wonder it was sold at a discount...

rubyhorse ( 2019-12-04 06:01:15 +0200 )edit

I add the same problem and had to reflash too after only one day of use :(

pat_o ( 2019-12-05 20:36:33 +0200 )edit

2 Answers

Sort by » oldest newest most voted
1

answered 2020-01-19 01:50:19 +0200

codeandcreate gravatar image

any news about this... ? i have the same problem with initial setup of the device; after installing some apps with storeman it doesn't boot anymore and the root partition is damaged.

edit flag offensive delete publish link more

Comments

Little Update on this: i had my 3rd initial installation and all went fine so far. what i have done differently from the two previous adepts: - no outlook support installed - finger print not on initial setup configured - no reboot option in developer settings activated/used

i think the reboot option is maybe the cause?

codeandcreate ( 2020-01-19 02:52:40 +0200 )edit
0

answered 2019-12-03 15:51:23 +0200

luchmhor gravatar image

updated 2019-12-03 16:12:34 +0200

So I booted the phone with the recovery image:

https://jolla.zendesk.com/hc/en-us/articles/360002996893#32

and did a filesystem check, which gave mit something like 2% non-continguous errors ... definitely not good. this step didn't repair anything, so I ran in shellmode this command:

fsck -b 32768 /dev/mapper/sailfish-root -y -C0
fsck -b 32768 /dev/mapper/sailfish-home -y -C0

as both were affected ... but not matter. It did not help. The filesystem(s) seem completely broken. This never happended before with btrfs btw.


result now: I reflashed.

edit flag offensive delete publish link more

Comments

i guess the fs-encryption stops e2fsck working...

manu ( 2019-12-03 18:17:12 +0200 )edit

Yeah I am not as proficient on debugging phones or as hardcore with linux... I just reflashed after 15 minutes and a couple of re-starts

rubyhorse ( 2019-12-04 06:02:09 +0200 )edit

No, the encryption is not the problem, the partitions are open.

luchmhor ( 2019-12-04 11:11:52 +0200 )edit

hm, i ran e2fsck before i tried to resize the root-partition on 10 plus. it asked me to correct errors (for every inode?), so i guess even if partitions are open, the filesystem is not...

manu ( 2019-12-05 19:08:28 +0200 )edit

what exactly do you mean with:

"even if partitions are open, the filesystem is not"

?

luchmhor ( 2019-12-06 09:54:37 +0200 )edit
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2019-12-01 23:48:36 +0200

Seen: 427 times

Last updated: Jan 19 '20