Android phone corrupted - Needs repair

goocreations

Well-Known Member
Joined
Mar 6, 2009
Messages
158
Reaction score
0
I have a Sony Xperia M on which I installed CyanogenMod. The phone worked perfectly for 2 months and then suddenly switched off and now it doesn't want to boot anymore. The phone is still able to boot into CWM, flashmode and fastboot mode, so the phone's hardware is not physically damaged.

At the moment I'm unable to install a new OS on the phone. Even a lot of people at XDA developers were unable to help me - seems I'm the absolute only one in the world with this problem.

So my question: even thought my warranty is void, can I still send my phone to Sony and pay for a repair, or won't they accept flashed phones? If not, any other place I can send it to?
 
When you say you cant flash a new OS,is this from CWM only or odin too?
 
I echo PsyWUlf, have you tried Odin?

But also note that you may need a few tries with Odin, I nearly bricked my Galaxy S2 with it though, took me 2 hours of trying before the software completed installing(the usb connection to my pc kept dying through the install)
 
I have a Sony Xperia M on which I installed CyanogenMod. The phone worked perfectly for 2 months and then suddenly switched off and now it doesn't want to boot anymore. The phone is still able to boot into CWM, flashmode and fastboot mode, so the phone's hardware is not physically damaged.

At the moment I'm unable to install a new OS on the phone. Even a lot of people at XDA developers were unable to help me - seems I'm the absolute only one in the world with this problem.

So my question: even thought my warranty is void, can I still send my phone to Sony and pay for a repair, or won't they accept flashed phones? If not, any other place I can send it to?

Try using adb to push the latest Cyanogenmod across and install it from CWM. I had to do this for my tablet a couple weeks ago.
 
I was able send my Samsung for a warranty repair even though it had a custom ROM and was rooted. So maybe send it in, and try your luck?
 
I've tried probably every possible solution out there.

1. Nothing in adb works. Although fasboot detects my device, adb doesn't.
2. As far as I'm aware, Odin is Samsung specific. I tried it in any case, but it doesn't detect my phone. There is something similar for Sony, namely Flashtool, but that laso gives me an error for pretty much every ROM out there.
3. I can't install ANY ROM in CWM (not even stock firmware). I always get a symlink error during installation and no one on XDA knows why.

Thanks dovij for your reply. Did any one try to send in a flashed Sony device for repairs?
 
I echo PsyWUlf, have you tried Odin?

But also note that you may need a few tries with Odin, I nearly bricked my Galaxy S2 with it though, took me 2 hours of trying before the software completed installing(the usb connection to my pc kept dying through the install)

Meh ... The S2 is indestructible!!
 
I've tried probably every possible solution out there.

1. Nothing in adb works. Although fasboot detects my device, adb doesn't.
2. As far as I'm aware, Odin is Samsung specific. I tried it in any case, but it doesn't detect my phone. There is something similar for Sony, namely Flashtool, but that laso gives me an error for pretty much every ROM out there.
3. I can't install ANY ROM in CWM (not even stock firmware). I always get a symlink error during installation and no one on XDA knows why.

Thanks dovij for your reply. Did any one try to send in a flashed Sony device for repairs?

wipe cache ? wipe system using format system in mounts and storage then mount system then reflash the ROM . or look for a cwm backed up ROM this had worked were update zip has failed .
 
As I said, I've tried everything, but nothing works. And not even the people at XDA can help.
 
As I said, I've tried everything, but nothing works. And not even the people at XDA can help.

The guys at XDA can hardly speak english, so I wouldn't consider them the be all and end all for tech support.

Haven't you got a nandroid backup?
 
No, sadly no kinds of backups. My phone just automatically switched on and then never wanted to boot into Android. I later found out that for some unknown reason the entire OS corrupted (a lot of symlink problems - probably the filesystem or filesystem table corrupted). So there was not even time to create a backup.
 
More than likely your flash is corrupted, and that pretty much means you will need a new phone.
 
I'm not sure what you mean by "flash", but I'm able to boot into flashmode, fastboot mode and into CWM, so I highly doubt that something physical has been damaged.
 
I'm not sure what you mean by "flash", but I'm able to boot into flashmode, fastboot mode and into CWM, so I highly doubt that something physical has been damaged.

Some areas of the flash have become inoperable - ie dead flash cells, past the design number. I would send it in for repairs. See if you can flash the original kernel and recovery image back first.
 
greenbean32:

Yes, I've tried your first option. TWR has same problems and CWM is currently in the newest version. What do you mean by "repartition"? I've formated all partitions, which work fine, but installing a ROM afterwards still gave me the symlink errors.
 
Some areas of the flash have become inoperable - ie dead flash cells, past the design number. I would send it in for repairs. See if you can flash the original kernel and recovery image back first.

I've now send an email to Sony SA in order to determine what their policies are. On the site where you get your unlock code for Sony devices, it was stated that you will lose the warranty and if you send it in for repairs it will cost a "substantial" amount of money to repair. So I'm waiting for Sony's reply on what exactly "substantial" means.
 
Flash back stock recovery,send in,sounds like a hard fault
 
What exact error does it give?

I had issues flashing any ROM recently on my S4 when I updated to the latest CWM. It kept failing. I had to revert to an older version to be able to flash again.
 
I get a symlink error when install ANY kind of ROM:

symlink: some symlinks failed

Here is my original post on XDA with a detailed description: http://forum.xda-developers.com/showthread.php?t=2680479

And another post, taking off at the 0017 error at the end of the previous post: http://forum.xda-developers.com/showthread.php?p=51106316

I've also had a PM conversation with one of the XDA people where he suggested using custom ROMs that are banned on XDA (they can sometimes be installed in fastboot mode). But that also didn't work.
 
Top
Sign up to the MyBroadband newsletter
X