[4.0.1.48] Phone unresponsive after update

General
1

Last night I have updated Sony Xperia XA2 Ultra dual sim to 4.0.1.48. Progress bar on update screen went all the way to completion a remained stucked od 100% the whole night. I tried to reboot the phone and after few cycles of showing white screen with sony logo it finally booted SailfishOS. I have entered PIN code and all was working fine. I have received some calls, sent some SMS, read e-mails, done some web browsing.

However after pulling the phone from my pocket later, I have discovered that it is not responding. Screen is black, buttons do not work. Holding power button does nothing. Pluging the phone to charger / USB cable does nothing, even the small LED indicator does not light up.

Tried VolumeDown + Power with USB cable plugged in and the device shows up as:

Bus 001 Device 067: ID 0fce:ade3 Sony Ericsson Mobile Communications AB QUSB__BULK

I googled it, and it may seem the phone is bricked for good. Any guidance on how to diagnose the problem appreciated.

2

Wouldn’t write it off just yet, have you tried keeping VolumeUp/Down (press middle of rocker) whilst pressing On button and see if you get one vibration or even three if you hold both down long enough? Failing that you may have to get out a heat gun to remove back cover to allow you to disconnect battery.

3

Well since the phone is apparently still under warranty I have decided to send for repair. Hope they will be able to reflash it.

4

I have just received package from servicing center. They were not able to fix the phone so they are sending me replacement. Xperia L4 Dual. Duh…

5

I have just had the same issue several weeks ago on 5.0 on XA2 (H3113), but this is probably not related to an update, since I have not updated the system for a year probably.

So far, I added XA2 USB ids to GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) and tried reading Aleph Security’s report on how exactly this QUSB__BULK/ EDL mode works Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
It might be possible to dump the full data partition, or to at least debug what is causing the brick: it seems that it might be the flash memory or the RAM desoldering. I just checked my XA2 again and it does not even show up as the QUSB__BULK device. Not sure what is causing it, but I remember it sometimes did show up and sometimes not at all. The cpu itself is fine for sure, because it is able to flash a red light three times.

6

Seems like you provided relevant info, but this thread is way too old and the issue is way too broad and unclear.

Yeah sure. First search result was something Android related with tons of log output and OP probably didn’t even check if that line is relevant. Something like that.

Seriously, open your own thread and don’t take OP’s words for truth.

1 Like