Sailfish X freeze on Sony whitescreen
asked 2019-03-25 18:59:21 +0200
My Xperia X device get stuck on the Sony whitescreen for forever. The phone is fully charged.
During the boot with USB connected to PC I could see, that the phone is detected (so it boots up partially, and is not fully bricked??):
Mar 25 19:30:18 kLatitude-E6430 kernel: [96049.969958] usb 3-1: new high-speed USB device number 42 using xhci_hcd
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.098963] usb 3-1: New USB device found, idVendor=05c6, idProduct=0afe
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.098971] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.098975] usb 3-1: Product: Xperia X
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.098979] usb 3-1: Manufacturer: Sony
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.098982] usb 3-1: SerialNumber: CB512A13TX
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.100105] usb-storage 3-1:1.0: USB Mass Storage device detected
Mar 25 19:30:18 kLatitude-E6430 kernel: [96050.100846] scsi host27: usb-storage 3-1:1.0
Mar 25 19:30:18 kLatitude-E6430 mtp-probe: checking bus 3, device 42: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Mar 25 19:30:18 kLatitude-E6430 mtp-probe: bus: 3, device: 42 was not an MTP device
Mar 25 19:30:19 kLatitude-E6430 kernel: [96051.098724] scsi 27:0:0:0: Direct-Access Linux File-CD Gadget 0310 PQ: 0 ANSI: 2
Mar 25 19:30:19 kLatitude-E6430 kernel: [96051.099842] sd 27:0:0:0: Attached scsi generic sg2 type 0
Mar 25 19:30:19 kLatitude-E6430 kernel: [96051.100760] sd 27:0:0:0: [sdc] Attached SCSI removable disk
Mar 25 19:30:26 kLatitude-E6430 kernel: [96057.781095] usb 3-1: USB disconnect, device number 42
Mar 25 19:30:26 kLatitude-E6430 kernel: [96058.085578] usb 3-1: new high-speed USB device number 43 using xhci_hcd
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.214614] usb 3-1: New USB device found, idVendor=05c6, idProduct=0afe
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.214621] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.214626] usb 3-1: Product: Xperia X
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.214629] usb 3-1: Manufacturer: Sony
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.214633] usb 3-1: SerialNumber: CB512A13TX
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.215673] usb-storage 3-1:1.0: USB Mass Storage device detected
Mar 25 19:30:27 kLatitude-E6430 kernel: [96058.216068] scsi host28: usb-storage 3-1:1.0
Mar 25 19:30:27 kLatitude-E6430 mtp-probe: checking bus 3, device 43: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Mar 25 19:30:27 kLatitude-E6430 mtp-probe: bus: 3, device: 43 was not an MTP device
Mar 25 19:30:28 kLatitude-E6430 kernel: [96059.214375] scsi 28:0:0:0: Direct-Access Linux File-CD Gadget 0310 PQ: 0 ANSI: 2
Mar 25 19:30:28 kLatitude-E6430 kernel: [96059.215418] sd 28:0:0:0: Attached scsi generic sg2 type 0
Mar 25 19:30:28 kLatitude-E6430 kernel: [96059.216967] sd 28:0:0:0: [sdc] Attached SCSI removable disk
Last time I had similar problem with bootloop after Sony white screen, the solution was to conduct Option 4 (Filesystem Check) from Recovery Menu.
This time Option 4 do not help, but it shows some problems with this partition:
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
Jolla Recovery v2.0
-----------------------------
Welcome to the recovery tool!
The available options are:
1) Reset device to factory state
2) Reboot device
3) Shell
4) Perform file system check
5) Run sshd
6) Exit
Type the number of the desired action and press [Enter]:
4
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
2 logical volume(s) in volume group "sailfish" now active
e2fsck 1.43.1 (08-Jun-2016)
root: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (256533, counted=256530).
Fix? yes
Free inodes count wrong (121787, counted=121784).
Fix? yes
root: ***** FILE SYSTEM WAS MODIFIED *****
root: 31816/153600 files (0.2% non-contiguous), 383470/640000 blocks
e2fsck 1.43.1 (08-Jun-2016)
home: recovering journal
Clearing orphaned inode 2566 (uid=100000, gid=100000, mode=0100644, size=12564)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (263516, counted=263541).
Fix? yes
Free inodes count wrong (1045422, counted=1045419).
Fix? yes
home: ***** FILE SYSTEM WAS MODIFIED *****
home: 31797/1077216 files (5.0% non-contiguous), 4521611/4785152 blocks
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
0 logical volume(s) in volume group "sailfish" now active
Done
Press [Enter] to return to recovery menu...
I wonder whether this is the reason why the boot process get stuck at white screen??: NO, AFTER FRESH FLASH I HAVE THE SAME OUTPUT AND DEVICE CAN BOOT UP
# e2fsck -f /dev/mmcblk0rpmb
e2fsck 1.43.1 (08-Jun-2016)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/mmcblk0rpmb
Could this be a zero-length partition?
/ # fdisk -l /dev/mmcblk0rpmb
fdisk: can't open '/dev/mmcblk0rpmb': Input/output error
Attempts to fix this partition or just check it's properties failed.
Whether anyone had seen this, and have the suggestion how I could recover from this issue?, without factory reset which would be the last step I would like to try?
Unfortunately seems similar to this Xperia X:link text
aspergerguy ( 2019-03-25 22:08:33 +0200 )editThank for link Aspergerguy. Good to know, that reflash should bring back to life my phone.
krzyklo ( 2019-03-28 18:32:53 +0200 )edit