Develop Bugs

[Q] Is this normal for a xperia play to act like this ?

hello i'm just wondering has anyone experienced there plays randomly rebooting or just turning to sim locked ? its very frustrating i got the phone for christmas.This phone has been bootloader unlocked but relocked again would i still have warranty ?

jakestarz said:
Nope your gonna have to flash a new firmware. UnfortUnately there is no r800at on wotan. You need to flash a r800a. It will. Be ok then
Sent from my R800a using xda premium
Click to expand...
Click to collapse
There are AT firmware files around xda. If he doesn't have the right firmware, warranty won't work.
You could try a factory reset first, or maybe a different kernel. If nothing works and you think it's a hardware issue, relocking and sending it in for repair might be the best idea.

Forgot to mention its a r800i I done a factory reset a few times after a week it starts back up but I was seeing if theres anymore problems and found 1 when I push the gameplay out and push it back in to fast it shuts the phone off it has the right firmware it has 2.3.4

kylemc1 said:
Forgot to mention its a r800i I done a factory reset a few times after a week it starts back up but I was seeing if theres anymore problems and found 1 when I push the gameplay out and push it back in to fast it shuts the phone off it has the right firmware it has 2.3.4
Click to expand...
Click to collapse
Sounds like a hardware problem.

[Q] Possible bricked wonder?

Hello,
Recently I've flashed Arco's CM9 version. It all went well for a couple of weeks until today. When I booted my phone, suddenly all apps started crashing and then it rebooted. But, the problem is, it is now stuck on a flashing Samsung logo.
Before I've started this thread, I've read many many similar threads about this, and started a 'rescue operation' by my own by using the tutorials for flashing back a stock rom with ODIN and other possibilities.
Unfortunately, after I've tried twice using ODIN, my phone is still stuck in the Samsung logo loop. I also can't enter Recovery mode, but am able to enter Download mode, as you've probably noticed.
As this is my first Android phone, I've always carefully read the tutorials and disclaimers about possible failures. I'm aware that the maker of the rom is not responsible for this.
Since I tried to flash back to stock android 2.3.6 from CM9 kernel, I've read that this could give some problems. My question is:
- Would flashing CM9 back worth a shot, or totally useless?
I hope you can help me, and if there isn't a solution, I hope the shop can cover this as I've got warranty for one year and 9 months.

Care to share how you had flashed it at first...
And you can still boot to recovery rite ?
Sent from my GT-I8150 using xda premium

countdown93 said:
Hello,
Recently I've flashed Arco's CM9 version. It all went well for a couple of weeks until today. When I booted my phone, suddenly all apps started crashing and then it rebooted. But, the problem is, it is now stuck on a flashing Samsung logo.
Before I've started this thread, I've read many many similar threads about this, and started a 'rescue operation' by my own by using the tutorials for flashing back a stock rom with ODIN and other possibilities.
Unfortunately, after I've tried twice using ODIN, my phone is still stuck in the Samsung logo loop. I also can't enter Recovery mode, but am able to enter Download mode, as you've probably noticed.
As this is my first Android phone, I've always carefully read the tutorials and disclaimers about possible failures. I'm aware that the maker of the rom is not responsible for this.
Since I tried to flash back to stock android 2.3.6 from CM9 kernel, I've read that this could give some problems. My question is:
- Would flashing CM9 back worth a shot, or totally useless?
I hope you can help me, and if there isn't a solution, I hope the shop can cover this as I've got warranty for one year and 9 months.
Click to expand...
Click to collapse
it happened to my friends phone also, he can go to DL mode but not recovery mode, he flashed a stock rom via odin, but that didnt help, he was still stuck at samsung logo, and about flashing CM9 again, i guess u cant bcoz u cant go to recovery mode, if youve flashed a stock rom again and that didnt work for you too, i guess u need to send to samsung for repair, i remember my friend said it was a hardware problem, good luck

vanir29 said:
it happened to my friends phone also, he can go to DL mode but not recovery mode, he flashed a stock rom via odin, but that didnt help, he was still stuck at samsung logo, and about flashing CM9 again, i guess u cant bcoz u cant go to recovery mode, if youve flashed a stock rom again and that didnt work for you too, i guess u need to send to samsung for repair, i remember my friend said it was a hardware problem, good luck
Click to expand...
Click to collapse
I've read elsewhere that it was a hardware problem that appeared on 1:10 Wonders... I'm really disappointed since this was my first smartphone...
A small question though: Since I've (tried to) flash it back to stock rom, if I bring it back to the shop where I bought it, would they notice that there was another rom, which could give them a reason that I've void the warranty? I really don't want to pay another amount of cash for this (faulty) phone.
Also in reply to andynroid: I've flashed CM9 the first time with CWM, as adviced by Arco68.

Can you still go to recovery ?
Sent from my GT-I8150 using xda premium

countdown93 said:
I've read elsewhere that it was a hardware problem that appeared on 1:10 Wonders... I'm really disappointed since this was my first smartphone...
A small question though: Since I've (tried to) flash it back to stock rom, if I bring it back to the shop where I bought it, would they notice that there was another rom, which could give them a reason that I've void the warranty? I really don't want to pay another amount of cash for this (faulty) phone.
Also in reply to andynroid: I've flashed CM9 the first time with CWM, as adviced by Arco68.
Click to expand...
Click to collapse
well in my friend's case, samsung accept it and repair it, if the stock rom is flash successfully, i think they wont notice that you've flash i custom rom, good luck though

Am I being dense.... but what is 1:10 Wonder???
I saw this also mentioned by Rio S. (I think)....but did not think anything about it.... but, is it HW version??
Where can I see it on device.
Andy....
Guy says in OP...
can't get Recovery!!!
:banghead:
Sent from my GT-I8150 using Tapatalk

irishpancake said:
Am I being dense.... but what us 1:10 Wonder???
I saw this also mentioned by Rio S. (I think)....but did not think anything about it.... but, is it HW version??
Where can I see it on device.
Andy....
Guy says in OP...
can't get Recovery!!!
:banghead:
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
Hi...
I wrote in this thread
http://forum.xda-developers.com/showpost.php?p=25616419&postcount=17

The only solution seems to be to flash an Asian rom with multi package.
Sent from my GT-I8150 using Tapatalk

when you try to enter recovery mode, what is the image you first see? is there an image that look like an android? i cant remember the exactly image but if you see that image, i think you must reflash the CWM via odin. Because every time i reflash the stock rom, my recovery mode will gone. So try to reflash CWM via odin. Nothing wrong if you give it a try

irishpancake said:
Am I being dense.... but what is 1:10 Wonder???
Click to expand...
Click to collapse
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high

Experienced this as well. Just sent it for warranty and they swapped out the motherboard.

alidsd said:
The only solution seems to be to flash an Asian rom with multi package.
Sent from my GT-I8150 using Tapatalk
Click to expand...
Click to collapse
I've heard and read about that, I thought that Rio did that, but it wasn't succesful.
tomatoman23 said:
when you try to enter recovery mode, what is the image you first see? is there an image that look like an android? i cant remember the exactly image but if you see that image, i think you must reflash the CWM via odin. Because every time i reflash the stock rom, my recovery mode will gone. So try to reflash CWM via odin. Nothing wrong if you give it a try
Click to expand...
Click to collapse
I wished I could enter Recovery mode, but the problem is: I can't
. But I also didn't know that if I flash back to stock rom, the recovery would be gone too. Maybe I should reflash CWM via odin. Nice advice.
vanir29 said:
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Click to expand...
Click to collapse
Jup. One out of ten => 10%. Such an error rate may not appear for such a great brand. That is ridiculously high. Even 1% is too high in my opinion.
Deathmax said:
Experienced this as well. Just sent it for warranty and they swapped out the motherboard.
Click to expand...
Click to collapse
Yeah, but what I've heard from others in the Netherlands: they will say that your device has been damaged by water, which isn't protected by warranty. And the bill is equal to a new device, or even more expensive. I hope they're in 'good mood', otherwise I maybe have to search for another device.

Hey Bro... this happen to me a while ago.... but covered by warranty , just simply told them at the SSC that you do an update via Kies and sxxt happen , coz in my place there are cases that the phone hang after update via Kies not only this model , it happen to others model too.
I suggest that you flash it back to stock before you send it back to SSC , without CWM .
cheers

vanir29 said:
i think it is one(1) out of ten(10) or 1 is to 10 sgw has a hardware problem, i guess thats what he meant, but isnt it kinda high
Click to expand...
Click to collapse
My friend!!!
I think you have solved the mystery of 1:10......
but can Rio S. confirm??
I don't have bricked phone....
but I try to understand what is causing these, so to be of some help....
and 1:10 was a puzzle to me, so thank you...
Sent from my GT-I8150 using Tapatalk

So I think I am pretty much screwed, any help appreciated

Recently switching from a iPhone to HTC One X I was absolutely loving my new phone for almost a month. But all of a sudden yesterday the screen stops working. It simply does not display anything. But the touch screen still works, and phone works too(if i swipe i can hear the phone unlocking, press home it vibrates, etc, basically phone is working, but display is not). This is not the first time this happened. It happened 3 days ago for about an hour and the screen started working by itself after the hour. But after the last time the screen stopped working it hasn't come back on(i was hoping it would, but it has been 2 days). Also i feel like I should mention this, both times the screen stopped working i was using Nes.Emu(a NES emulator). The screen didn't turn off suddenly, at first the screen stopped responding, stuck at like an image. I noticed the phone was working even then, but the screen just wasn't responding. After that i locked the phone and the display went dark, and hasn't come back on since. I even boot into bootloader and it still wasn't working.
Now i wont get any warranty as i unlocked the bootloader thus voiding the warranty. Currently have ARHD 6.1.0 rom on it. I have no idea what to do. I was guessing somehow going back to stock, then relocking the bootloader before taking it to HTC, dunno if they'll do it under warranty. But thats not my biggest issue. I am travelling South Asia this summer(bought the phone from India), and basically dont know how the hell do i even give it to an HTC support center, cause I'll have to come back to the support center to pick it backup and i wont be in any place that long.

Tried holding the power button for 30 seconds?

try running an RUU that matches your cid/sw version (1.29.XXX.11).
Look here for the RUU that matches your sw version. Don't forget to flash stock recovery and run fastboot OEM lock before you run the RUU.
http://www.filefactory.com/f/7cc7b2fbdd03c031/
Sent from my HTC One X using Tapatalk 2

shadehh said:
Tried holding the power button for 30 seconds?
Click to expand...
Click to collapse
Yep. Many times.
nikorette said:
try running an RUU that matches your cid/sw version (1.29.XXX.11).
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Will running an RUU that matches my CID return me to stock firmware? I thought that only updated the Hboot or something?

Yeah, it also re-locks the phone.
Its worth a try. Can you not even get the bootloader up? Poer button + vol down?

Mcyates said:
Yeah, it also re-locks the phone.
Its worth a try. Can you not even get the bootloader up? Poer button + vol down?
Click to expand...
Click to collapse
Yeah, I assume i can get into bootloader since the rest of the phones works fine. But the screen does not even work in bootloader. I will try doing what you suggested, but kind of hard without the screen.

It sounds like Hardware fault rather than software.

ShyamSasi said:
It sounds like Hardware fault rather than software.
Click to expand...
Click to collapse
Yep, but i want to be on default software with a relocked bootloader before i send it to HTC. Since you're a Docomo user i'll assume you're from India. I was wondering if you have any idea about HTCs service in India? How much time do you think will it take them to sort this issue out?

Can't you use recovery mode and restore a backup?
Before you start with the emulator again you could test for a few days without it and see how your screen responses?
Other things you can try is flash a different rom?
Even return to stock is an option to investigate?
Reading your story it doesn't look like a hardware failure but more as a software bugger.
Just a taught.
boobinator said:
Recently switching from a iPhone to HTC One X I was absolutely loving my new phone for almost a month. But all of a sudden yesterday the screen stops working. It simply does not display anything. But the touch screen still works, and phone works too(if i swipe i can hear the phone unlocking, press home it vibrates, etc, basically phone is working, but display is not). This is not the first time this happened. It happened 3 days ago for about an hour and the screen started working by itself after the hour. But after the last time the screen stopped working it hasn't come back on(i was hoping it would, but it has been 2 days). Also i feel like I should mention this, both times the screen stopped working i was using Nes.Emu(a NES emulator). The screen didn't turn off suddenly, at first the screen stopped responding, stuck at like an image. I noticed the phone was working even then, but the screen just wasn't responding. After that i locked the phone and the display went dark, and hasn't come back on since. I even boot into bootloader and it still wasn't working.
Now i wont get any warranty as i unlocked the bootloader thus voiding the warranty. Currently have ARHD 6.1.0 rom on it. I have no idea what to do. I was guessing somehow going back to stock, then relocking the bootloader before taking it to HTC, dunno if they'll do it under warranty. But thats not my biggest issue. I am travelling South Asia this summer(bought the phone from India), and basically dont know how the hell do i even give it to an HTC support center, cause I'll have to come back to the support center to pick it backup and i wont be in any place that long.
Click to expand...
Click to collapse

boobinator said:
Will running an RUU that matches my CID return me to stock firmware? I thought that only updated the Hboot or something?
Click to expand...
Click to collapse
Yes, it returns the phone to the stock state. RELOCK before using the RUU. Install the correct stock recovery before relock. A link to stock recoveries are in the cwm thread.
Sent from my HTC One X using Tapatalk 2

Well it seems that i am just out of luck. It turns out the RUU that I will be needing 1.29.720.11 is not yet available for download
I do have a Nandroid backup of my stock rooted rom if it will work somehow

That's all you need.

I encountered the exactly same problem as you did. HTC replaced the main board and battery for me, problem solved. Hope this helps
Sent from my HTC One X using xda app-developers app

I have the same phone. I have a nandroid backup of the stock rom. Don't know if that'll help you.
Sent from my HTC One X using xda premium

Thanks for the offer iTeeXDA, but i managed to get back to stock(using nandroid backup). The issue seemed to be that i had named the folder of the backup rom(no spaces).
Now what should i do next? I imagine i should be reflashing stock recovery right? Then relocking the bootloader? Will i run into issues cause i came back to stock from a nandroid backup?
EDIT:So, ok, i went back to stock recovery and relocked bootloader. Phone keeps booting into hboot after i relock bootloader. I've unlocked the bootloader again and the phone seems to have booted

If u can't see anything then HTC people also won't be able to see anything..so go ahead with the phone as it is..n as somebody has already told u that they will be replacing your board the firmware is gonna be gone anyways..I guess I am correct here ...
N this is India man..here HTC people cannot even tell the screen resolution of the phone..forget about the bootloader..happened with me when I took my Note to Samsung ..
Sent from my HTC One X using xda premium

LakshayX said:
If u can't see anything then HTC people also won't be able to see anything..so go ahead with the phone as it is..n as somebody has already told u that they will be replacing your board the firmware is gonna be gone anyways..I guess I am correct here ...<SNIP>
Click to expand...
Click to collapse
Unless they DO replace the screen and boot the phone finding the bootloader unlock then charge for the repair haha. Doh. Let's hope not.

iTeeXDA said:
I have the same phone. I have a nandroid backup of the stock rom. Don't know if that'll help you.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
@iTeeXDA can you please upload your nandriod backup for 1.29.720.11.I want to go back to stock but was not able to find the RUU for the same.

May I have the nandroid backup as well ? Pretty please!

Urgent help needed

Well it seems my Play has finally died.
Woke up this morning and my touchscreen wouldnt respond so I reflashed the ROM Im using (MIUI v4).
Now, for some reason, it wont make it past CWM no matter what kernel I flash.
So I used Flashtool to go back to a stock ftf and it freezes at the SE logo. However, when connected with PC Companion it gets to the lockscreen but the touchscreen wont work :S
Im at a loss completely :S
Any help would be great

Woo man.. That sounds srious. Its like the phne touchscreen has been disable. Did u try flashing a kernel with full touch recovery n see if its touch-able?? Just a suggestion. Its really weird how that happen, really. It shouldn't matter if u plug ur phone to pc or not. If the screen boot it should respon with any touch u make. Weird...

sdojoin said:
Woo man.. That sounds srious. Its like the phne touchscreen has been disable. Did u try flashing a kernel with full touch recovery n see if its touch-able?? Just a suggestion. Its really weird how that happen, really. It shouldn't matter if u plug ur phone to pc or not. If the screen boot it should respon with any touch u make. Weird...
Click to expand...
Click to collapse
I tried the CWM with touch support and it doesnt respond at all. When I flash a ROM it wont make it past CWM so it seems like Ive got 2 problems. Well, if I flash a stock ftf file it sticks at the first Sony Ericsson logo as well so flashing back to stock isnt a solution either
EDIT: I appear to have life CM9 has booted to the main splash screen. However, touch input is still gone

CTU_Loscombe said:
I tried the CWM with touch support and it doesnt respond at all. When I flash a ROM it wont make it past CWM so it seems like Ive got 2 problems. Well, if I flash a stock ftf file it sticks at the first Sony Ericsson logo as well so flashing back to stock isnt a solution either
Click to expand...
Click to collapse
Meaning the touchscreen is completely dead or it dosen't boot up the system completely?? This is hard. If the screen is touch-able u obviously wont hav any problem. Did u try any othert .ftf besides the 1 u already hav?? Just curious...

sdojoin said:
Meaning the touchscreen is completely dead or it dosen't boot up the system completely?? This is hard. If the screen is touch-able u obviously wont hav any problem. Did u try any othert .ftf besides the 1 u already hav?? Just curious...
Click to expand...
Click to collapse
Ive managed to boot into CM9 (official) but the touch screen is still dead
Think I may have to get a new screen

CTU_Loscombe said:
Ive managed to boot into CM9 (official) but the touch screen is still dead
Think I may have to get a new screen
Click to expand...
Click to collapse
Bump!!! Sorry for lost bro....($£$£)

sdojoin said:
Bump!!! Sorry for lost bro....($£$£)
Click to expand...
Click to collapse
Since Ive flashed my phone the warranty is gone too
Guess this is the end of my days in the Xperia Play section

CTU_Loscombe said:
Since Ive flashed my phone the warranty is gone too
Guess this is the end of my days in the Xperia Play section
Click to expand...
Click to collapse
No man....don't say that. You have been a big help here, especially to me. I wonder what you did to that screen and if it happened from a rom flash or what.
Sent from my R800i using xda premium

cyrusalmighty said:
No man....don't say that. You have been a big help here, especially to me. I wonder what you did to that screen and if it happened from a rom flash or what.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
I flashed an MIUI ICS rom and the following morning it was locked up. Now certain kernels wont go past CWM.
FXP kernels seem to work for me though but the touchscreen doesnt work. Some of the stock firmwares wont even boot but even if they do, the touchscreen doesnt work. Ive wiped data/cache/dalvik so many times but I havent a clue whats happened :S
Im still gonna stick around the Play section though
This has been the only phone issue thats ever had me stumped completely

Did u did a factory reset also before flashing anything?

Can you enter the service menu by dialing *#*#7378423#*#* in phone dialer?? Then you can test the touchscreen, hard keys, proximity, ALS, and almost all other functions. I'm not sure if its the same numbers for all versions of Play or just AT&T's version. If not google service menu+android or something. Or maybe its something that can fixed with computer by the guys who unlock fix Sony phones.(Jinx13 & alejandrissimo-*probably misspelled)
Sent from my R800i using xda premium

Sure. U can test the touchscreen on that menu. If u can get to it. The code r the same for all xperia phone, i guess.

sdojoin said:
Sure. U can test the touchscreen on that menu. If u can get to it. The code r the same for all xperia phone, i guess.
Click to expand...
Click to collapse
Got to that menu and its still not responding to touch.
Sold the phone for scrap today. I had no warranty due to unlocking the bootloader via the Sony Unlock site so sending it for repair was out of the question. Moving on to HTC at the weekend. Gonna get the Explorer I think it was

[Q] HELP! My Xperia Play Died!

Help! I think My Xperia Play died on me! Here's what happened. It may be a long post but PLEASE bear with me. I really need your help guys! My phone was just lying around on my desk and I decided to use it and was surprised because it won't unlock. So i thought that my home button was just malfunctioning and tried to slide it's game pad as it unlocks the phone by itself but still no respond. So I thought it turned off by itself and when I tried to turn it on, it won't turn on at all because there's no short vibration. Usually when we turn on our device, there's a short vibration right? So I removed the battery, placed it back again and turned on my phone and at last there's the short vibration. But after a while I noticed that the boot splash hadn't appeared yet. I waited for a couple of minutes but still nothing happens. When I turned it on again there's the short vibration and that's it. So I searched for solutions here on XDA and on the web and I tried almost all of it. I flashed it back to it's stock firmware using Flashtool and still the same. I tried using PC Companion and Sony Ericsson Update Service but still to no avail. I also relocked it's bootloader and reflashed everything again but nothing works. So I gave up because I thought it might be a hardware issue but I didn't drop my phone or anything so i don't know what went wrong.
Then the following day I decided to check on my phone again and to my surprise it's back to normal and I was really glad about it. So I didn't flash any custom ROM and Kernels because I'm afraid that it might screw everything again. I just rooted it and completely debloated it and installed init.d support for stock kernel. I flashed CrossBreeder and RTMixManager and modified it's systemui for quick panel and battery % mod. I also flashed custom boot animation and that's it. I was happy about my phone because it seems all is well.
But yesterday when I was about to use my phone, the same thing happened again! I tried to redo everything I did all over again but still nothing! I can still use it in flashmode and fastboot though. I also tried entering CWM Recovery. After I turned on my phone I spam pressed volume down and blue LED showed up with the vibration if you enter recovery mode but there's no display. Can anyone tell me what's the problem? It might be the flex cable or the digitizer but I don't know. Has anyone encountered the same situation as mine? Please help me! I don't know what's wrong with my phone!
P.S. I can't send it to Sony Centre as my warranty is already expired. My only option is buying a new Xperia Play. Because I browsed for replacement parts on the web and they don't ship it directly to my country and it costs too much if I have it ship to me indirectly.

You have a hardware failure, I see that right now is very common, you will need to replace the automatic light sensor, to get it working, or if you don't want replace it, you will have to switch onto JB, because it has ALS disabled by default.

Windshade said:
Help! I think My Xperia Play died on me! Here's what happened. It may be a long post but PLEASE bear with me. I really need your help guys! My phone was just lying around on my desk and I decided to use it and was surprised because it won't unlock. So i thought that my home button was just malfunctioning and tried to slide it's game pad as it unlocks the phone by itself but still no respond. So I thought it turned off by itself and when I tried to turn it on, it won't turn on at all because there's no short vibration. Usually when we turn on our device, there's a short vibration right? So I removed the battery, placed it back again and turned on my phone and at last there's the short vibration. But after a while I noticed that the boot splash hadn't appeared yet. I waited for a couple of minutes but still nothing happens. When I turned it on again there's the short vibration and that's it. So I searched for solutions here on XDA and on the web and I tried almost all of it. I flashed it back to it's stock firmware using Flashtool and still the same. I tried using PC Companion and Sony Ericsson Update Service but still to no avail. I also relocked it's bootloader and reflashed everything again but nothing works. So I gave up because I thought it might be a hardware issue but I didn't drop my phone or anything so i don't know what went wrong.
Then the following day I decided to check on my phone again and to my surprise it's back to normal and I was really glad about it. So I didn't flash any custom ROM and Kernels because I'm afraid that it might screw everything again. I just rooted it and completely debloated it and installed init.d support for stock kernel. I flashed CrossBreeder and RTMixManager and modified it's systemui for quick panel and battery % mod. I also flashed custom boot animation and that's it. I was happy about my phone because it seems all is well.
But yesterday when I was about to use my phone, the same thing happened again! I tried to redo everything I did all over again but still nothing! I can still use it in flashmode and fastboot though. I also tried entering CWM Recovery. After I turned on my phone I spam pressed volume down and blue LED showed up with the vibration if you enter recovery mode but there's no display. Can anyone tell me what's the problem? It might be the flex cable or the digitizer but I don't know. Has anyone encountered the same situation as mine? Please help me! I don't know what's wrong with my phone!
P.S. I can't send it to Sony Centre as my warranty is already expired. My only option is buying a new Xperia Play. Because I browsed for replacement parts on the web and they don't ship it directly to my country and it costs too much if I have it ship to me indirectly.
Click to expand...
Click to collapse
You could try using this app, https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness&hl=en , but i don't think thats the issue personally.

gangstermartorell said:
You have a hardware failure, I see that right now is very common, you will need to replace the automatic light sensor, to get it working, or if you don't want replace it, you will have to switch onto JB, because it has ALS disabled by default.
Click to expand...
Click to collapse
Okay I will try that later. Thanks!
fma965 said:
You could try using this app, https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness&hl=en , but i don't think thats the issue personally.
Click to expand...
Click to collapse
But I can't use it because there's no display on my phone.

Windshade said:
Okay I will try that later. Thanks!
But I can't use it because there's no display on my phone.
Click to expand...
Click to collapse
Flash a stock FTF again and see what happens.
try
fastboot erase system
and
fastboot erase userdata

fma965 said:
Flash a stock FTF again and see what happens.
try
fastboot erase system
and
fastboot erase userdata
Click to expand...
Click to collapse
I already tried it but it says permission denied because the device must be rooted. >.<
Sent from my GT-I9505 using xda app-developers app

Windshade said:
I already tried it but it says permission denied because the device must be rooted. >.<
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
actually no, it needs a unlocked bootloader to use those commands.

fma965 said:
actually no, it needs a unlocked bootloader to use those commands.
Click to expand...
Click to collapse
Yeah, tried it for the 2nd time.. I was able to erase system but I can't erase data because it says partition not found or permission denied.

Windshade said:
because it says partition not found or permission denied.
Click to expand...
Click to collapse
Which 1 is it?

fma965 said:
Which 1 is it?
Click to expand...
Click to collapse
That was the error message. It says "failed: partition not found or permission denied."

Windshade said:
That was the error message. It says "failed: partition not found or permission denied."
Click to expand...
Click to collapse
hmm i dunno then, wait for some one else to assist

Windshade said:
Help! I think My Xperia Play died on me! Here's what happened. It may be a long post but PLEASE bear with me. I really need your help guys! My phone was just lying around on my desk and I decided to use it and was surprised because it won't unlock. So i thought that my home button was just malfunctioning and tried to slide it's game pad as it unlocks the phone by itself but still no respond. So I thought it turned off by itself and when I tried to turn it on, it won't turn on at all because there's no short vibration. Usually when we turn on our device, there's a short vibration right? So I removed the battery, placed it back again and turned on my phone and at last there's the short vibration. But after a while I noticed that the boot splash hadn't appeared yet. I waited for a couple of minutes but still nothing happens. When I turned it on again there's the short vibration and that's it. So I searched for solutions here on XDA and on the web and I tried almost all of it. I flashed it back to it's stock firmware using Flashtool and still the same. I tried using PC Companion and Sony Ericsson Update Service but still to no avail. I also relocked it's bootloader and reflashed everything again but nothing works. So I gave up because I thought it might be a hardware issue but I didn't drop my phone or anything so i don't know what went wrong.
Then the following day I decided to check on my phone again and to my surprise it's back to normal and I was really glad about it. So I didn't flash any custom ROM and Kernels because I'm afraid that it might screw everything again. I just rooted it and completely debloated it and installed init.d support for stock kernel. I flashed CrossBreeder and RTMixManager and modified it's systemui for quick panel and battery % mod. I also flashed custom boot animation and that's it. I was happy about my phone because it seems all is well.
But yesterday when I was about to use my phone, the same thing happened again! I tried to redo everything I did all over again but still nothing! I can still use it in flashmode and fastboot though. I also tried entering CWM Recovery. After I turned on my phone I spam pressed volume down and blue LED showed up with the vibration if you enter recovery mode but there's no display. Can anyone tell me what's the problem? It might be the flex cable or the digitizer but I don't know. Has anyone encountered the same situation as mine? Please help me! I don't know what's wrong with my phone!
P.S. I can't send it to Sony Centre as my warranty is already expired. My only option is buying a new Xperia Play. Because I browsed for replacement parts on the web and they don't ship it directly to my country and it costs too much if I have it ship to me indirectly.
Click to expand...
Click to collapse
This happened to me and i had the phone checked and it was the flex cable that needed replacement

Did you find any solution or are blocked in recovery or flash mode?