Hello,
First post here because I need help. Lately, I've been using my Xperia M (C1095) with CM11 Beta 1 and everything was fine. Like, really fine, no problem whatsoever coming from the ROM. But then, for no apparent reason, my phone refused to reboot today. Well, maybe playing with Xposed was the cause, but that would be weird considering it rebooted just fine after I was done with it. It just kept stuck on the Sony logo, but I could still access CWM. ADB is working fine, Fastboot is working fine, and I can mount everything in CWM. No hardbrick here.
After a couple of attempts to flash CM11 again (I ended up with a Status 7, some symlinks failed all the time), I decided to redo things from scratch by flashing the stock 4.1.2 ftf file for my device with Flashtool. Everything went fine, until... this.
Yeaaaah. So I thought maybe it came from my PC (I'm running Windows 8.1), so I tried to use another one. Then another one. All of them ended up getting the same error. I was surprised, because Flashtool used to work fine with my Xperia M.
I also tried with another ftf file, and the same result kept popping up.
The good thing is, I still have access to CWM, so is there something I can do with it?
EDIT : Little update here, my phone is actually still in the same state as before. I thought we had repaired it... well, nope.
The main thing is, my device can boot into Android (CyanogenMod 11), but it's apparently hard locked in read only mode. If you uninstall an app then reboot it, the app will be back. If you touch anything in /system, for example uninstalling/reinstalling BusyBox, no changes at all after reboot. That also explains why you can't wipe the device through CWM or ADB or even Flashtool. And even if I wanted to brick it, I couldn't.
So yeah. In a way, my phone is Schrödinger's cat. Completly unusable due to its weird behaviour and unexpected reboots, but alsol completly alive.
If anybody is skilled enough to find a solution other than destroying the phone discretly and trying to send it back to Sony, that would be great - although I'm not expecting much.
First post here because I need help. Lately, I've been using my Xperia M (C1095) with CM11 Beta 1 and everything was fine. Like, really fine, no problem whatsoever coming from the ROM. But then, for no apparent reason, my phone refused to reboot today. Well, maybe playing with Xposed was the cause, but that would be weird considering it rebooted just fine after I was done with it. It just kept stuck on the Sony logo, but I could still access CWM. ADB is working fine, Fastboot is working fine, and I can mount everything in CWM. No hardbrick here.
After a couple of attempts to flash CM11 again (I ended up with a Status 7, some symlinks failed all the time), I decided to redo things from scratch by flashing the stock 4.1.2 ftf file for my device with Flashtool. Everything went fine, until... this.
04/037/2014 10:37:41 - INFO - <- This level is successfully initialized
04/037/2014 10:37:41 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
04/037/2014 10:37:46 - INFO - Device disconnected
04/024/2014 09:24:59 - INFO - Selected C1905 / 15.1.C.2.8 / CE
04/037/2014 10:37:48 - INFO - Preparing files for flashing
04/037/2014 10:37:54 - INFO - Please connect your device into flashmode.
04/038/2014 10:38:04 - INFO - Device connected in flash mode
04/038/2014 10:38:04 - INFO - Opening device for R/W
04/038/2014 10:38:04 - INFO - Reading device information
04/038/2014 10:38:05 - INFO - Phone ready for flashmode operations.
04/038/2014 10:38:05 - INFO - Current device : Unknown: Aug 22 2013/01:15:50 - YT910B0LQG - Unknown: Aug 22 2013/01:15:50 - Unknown: Aug 22 2013/01:15:50 - Unknown: Aug 22 2013/01:15:50
04/038/2014 10:38:05 - INFO - Start Flashing
04/038/2014 10:38:05 - INFO - Processing loader.sin
04/038/2014 10:38:05 - INFO - Checking header
04/038/2014 10:38:05 - INFO - Flashing data
04/038/2014 10:38:05 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
04/038/2014 10:38:06 - INFO - Processing partition-image.sin
04/038/2014 10:38:06 - INFO - Checking header
04/038/2014 10:38:06 - INFO - Flashing data
04/038/2014 10:38:06 - INFO - Processing kernel.sin
04/038/2014 10:38:06 - INFO - Checking header
04/038/2014 10:38:06 - INFO - Flashing data
04/038/2014 10:38:06 - INFO - Ending flash session
04/038/2014 10:38:06 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C ";
04/038/2014 10:38:06 - ERROR - Error flashing. Aborted
04/038/2014 10:38:07 - INFO - Device connected in flash mode
04/038/2014 10:38:07 - INFO - Device disconnected
Yeaaaah. So I thought maybe it came from my PC (I'm running Windows 8.1), so I tried to use another one. Then another one. All of them ended up getting the same error. I was surprised, because Flashtool used to work fine with my Xperia M.
I also tried with another ftf file, and the same result kept popping up.
The good thing is, I still have access to CWM, so is there something I can do with it?
EDIT : Little update here, my phone is actually still in the same state as before. I thought we had repaired it... well, nope.
The main thing is, my device can boot into Android (CyanogenMod 11), but it's apparently hard locked in read only mode. If you uninstall an app then reboot it, the app will be back. If you touch anything in /system, for example uninstalling/reinstalling BusyBox, no changes at all after reboot. That also explains why you can't wipe the device through CWM or ADB or even Flashtool. And even if I wanted to brick it, I couldn't.
So yeah. In a way, my phone is Schrödinger's cat. Completly unusable due to its weird behaviour and unexpected reboots, but alsol completly alive.
If anybody is skilled enough to find a solution other than destroying the phone discretly and trying to send it back to Sony, that would be great - although I'm not expecting much.
Last edited: