[Q] FXP failure to boot - Xperia Play Q&A, Help & Troubleshooting

Hello again. This is sort of a continuation from my previous thread about trying to replace the touch screen, but it's an entirely new problem, so I figured it warranted it's own thread. Since the replacement screen that I received didn't allow touch to work, I thought I'd try going back to the old cracked screen to see if it was the screen, or the hardware. I got all the way through the process of swapping the screens, and put it back together.
Now when I try to boot up, I get the Free Xperia Project boot up screen. After about 20~30 seconds, the purple LED comes on. At that point, I'm used to seeing the Cyanogen Mod boot animation, but now it just sits on the FXP screen. After a short wait, the screen dims and there's a very tiny vibration, even shorter than the power-up vibration. If I tap Volume down during the FXP screen, and try to enter CWM, all I get is a screen full of randomized snowy rainbow colored pixels
I've tried disassembling and reassembling the phone several times. I've tried reflashing the boot image in fastboot mode, which I don't seem to be encountering any trouble with. Does anyone have any advice for me at this point? Or should I just give up and get a replacement? Thanks.

ProcyonSJJ said:
Hello again. This is sort of a continuation from my previous thread about trying to replace the touch screen, but it's an entirely new problem, so I figured it warranted it's own thread. Since the replacement screen that I received didn't allow touch to work, I thought I'd try going back to the old cracked screen to see if it was the screen, or the hardware. I got all the way through the process of swapping the screens, and put it back together.
Now when I try to boot up, I get the Free Xperia Project boot up screen. After about 20~30 seconds, the purple LED comes on. At that point, I'm used to seeing the Cyanogen Mod boot animation, but now it just sits on the FXP screen. After a short wait, the screen dims and there's a very tiny vibration, even shorter than the power-up vibration. If I tap Volume down during the FXP screen, and try to enter CWM, all I get is a screen full of randomized snowy rainbow colored pixels
I've tried disassembling and reassembling the phone several times. I've tried reflashing the boot image in fastboot mode, which I don't seem to be encountering any trouble with. Does anyone have any advice for me at this point? Or should I just give up and get a replacement? Thanks.
Click to expand...
Click to collapse
Did you follow the instructions and do you have a unlocked bootloader? ? Did you use flashtool to update the xperia play to the 2.3.4 before flashing FXP? Did you wipe dalviche cache, data reset, and cache during Clockwork mod recovery before installing the zip file? Did you download the correct zip for the Zesus file? If you downloaded zesusc =CDMA varient and zesus = GSM varient.

chery2k said:
Did you follow the instructions and do you have a unlocked bootloader? ? Did you use flashtool to update the xperia play to the 2.3.4 before flashing FXP? Did you wipe dalviche cache, data reset, and cache during Clockwork mod recovery before installing the zip file? Did you download the correct zip for the Zesus file? If you downloaded zesusc =CDMA varient and zesus = GSM varient.
Click to expand...
Click to collapse
Thanks for your concern chery2k, but this didn't happen as a result of the FXP installation. I have been successfully running FXP for around a year now. This all started because my touch screen got stepped on and cracked, and I had the bright idea that I could buy a touchscreen replacement for $30 and do the installation myself. While I was successful (somewhat) at replacing the screen, the touchscreen itself was defective (no touch), so in my impatience, I attempted to put the cracked screen back. Once the phone was reassembled, this was the outcome. Even though nothing about the process should have directly contributed to the state of the phone, there's no telling how the frequent assembling and disassembling may have damaged the electronics or ribbons, despite how careful I tried to be.
I have regrettably downgraded back to my old HTC Eris. I'm due for an upgrade, and looking at the HTC Droid DNA, but the lack of a card slot bothers me. The SGN2 seems just too big for me as a phone. As much as I'd love more powerful hardware, it looks like I may have to find an Xperia Play on eBay or something, and pay to have the bootloader unlocked

Related

Help! Phone loads boot instead of ROM, and get frozen!

I've recently sold my rooted HTC Desire with MIUI installed.
However the buyer contacted me today saying the phone is not working.
It was working fine when I sold it to him, but now has the following problems:
- It normally loads the boot screen instead of the ROM.
- In the boot screen everything is frozen ( I know you need to wait 10 sec). It takes a few minutes until it actually registers that you pressed something.
- If you actually do get to go to the recovery screen, it is very buggy - it mostly doesn't respond to pressing the optical button, and sometimes it selects something without you pressing anything.
- If you do get to load the ROM (I've managed to install GingerBurst Sense 2.1 ROM. So I've tried this with this and MIUI), it loads in safe mode, and whenever you lock the screen and try to open it again, the phone resets to the boot screen, which again is frozen...
I've managed to wipe the phone and install the gingerbread rom mentioned above, but the problems still persist.
Does anyone have any idea what's wrong with my phone all of the sudden, and how it can be fixed?
Could it finally have died and there's nothing else I can do?
If it helps, the phone is a HTC Desire Bravo S-ON with ClockWorkMod Recovery v2.5.0.7
Thanks for reading!
Liran
liranh said:
I've recently sold my rooted HTC Desire with MIUI installed.
However the buyer contacted me today saying the phone is not working.
It was working fine when I sold it to him, but now has the following problems:
- It normally loads the boot screen instead of the ROM.
- In the boot screen everything is frozen ( I know you need to wait 10 sec). It takes a few minutes until it actually registers that you pressed something.
- If you actually do get to go to the recovery screen, it is very buggy - it mostly doesn't respond to pressing the optical button, and sometimes it selects something without you pressing anything.
- If you do get to load the ROM (I've managed to install GingerBurst Sense 2.1 ROM. So I've tried this with this and MIUI), it loads in safe mode, and whenever you lock the screen and try to open it again, the phone resets to the boot screen, which again is frozen...
I've managed to wipe the phone and install the gingerbread rom mentioned above, but the problems still persist.
Does anyone have any idea what's wrong with my phone all of the sudden, and how it can be fixed?
Could it finally have died and there's nothing else I can do?
If it helps, the phone is a HTC Desire Bravo S-ON with ClockWorkMod Recovery v2.5.0.7
Thanks for reading!
Liran
Click to expand...
Click to collapse
It all looks like it was dropped or moisture got inside of it. I would try with 2.3 ruu, to get it back to fully stock on all partitions and try it there. If problem continues it's a hardware failure, and if everything works great, then Revolutionary (s-off and root) and a choice of custom rom. However I would stick to stock for selling, unless the buyer requests different.
nlooooo said:
It all looks like it was dropped or moisture got inside of it. I would try with 2.3 ruu, to get it back to fully stock on all partitions and try it there. If problem continues it's a hardware failure, and if everything works great, then Revolutionary (s-off and root) and a choice of custom rom. However I would stick to stock for selling, unless the buyer requests different.
Click to expand...
Click to collapse
You are quite right, I have dropped it hard and got it wet several times, so it probably is indeed a hardware fault.
I'll try your suggestions, but it seems to me like I will probably have to refund the buyer.
Thanks for your help.
Liran
Try with disassembling and cleaning of all connectors.
I've just refunded the buyer.
Thank you both for your help

[Q] Screen Issues Lead To Bricked Device

I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery

[Q] My Xperia Play does not seem to boot. Can you help me?

Hi!
My Xperia (with Cyanogenmod 9.1 ROM) started to behave in an unstable way a week ago, for no apparent reason. The screen would start to freeze and the only way I had to reboot the phone would be to remove the battery and put it back again. Sometimes the screen would show what I presume to be heavy screen corruption, like in the image I attached to this post.
Yesterday, the battery removal trick stopped working. Basically, the phone boots into the FreeXperia Project logo and then nothing shows up. The screen goes black into screen saving mode and if I touch the power button again, an image like the attached one appears.
I tried to reinstall the CyanogenMod ROM following the instructions you can see over wiki.cyanogenmod.org/w/Install_CM_for_zeus.
All goes well up to the point I press the Volume rockers to get into ClockworkMod Recovery mode. Instead of the Recovery Menu, all I get is an image like the one I attached.
Any ideas on how to solve this problem?
Thanks in advance for your help.
Your flex cable is damaged, you will need to change it with a new one, for buying it, go here:
http://www.ebay.es/itm/Replacement-...e_Replacement_Parts_Tools&hash=item27ce40c39b
Thank you for you reply.
I thought it was a software problem, since the screen seemed to work well when the FreeXperia Project logo showed up.
Still have to decide if I have the guts to open my Xperia to fix it or send it for repair. I know there are some tutorials on Youtube showing how to do it, but I am not sure if I have a firm hand to do it without damaging anything else.
Once again thank you for your reply.
I agree that is most likely flex problem, but you try to flash stock firmware and see is software or hardware problem.
If it is the same on stock firmware, then it's flex 100%
Bakisha said:
I agree that is most likely flex problem, but you try to flash stock firmware and see is software or hardware problem.
If it is the same on stock firmware, then it's flex 100%
Click to expand...
Click to collapse
I am going to try to flash the phone with another ROM. If the problem continues I am going to replace the flex cable.
Thanks for the help!
Yup, it's the flex cable
Just an update. I turned on the phone again today, before starting to open it to replace the flex cable and the phone started to boot normally. It was functioning properly until I slid the pad. The screen stopped updating immediatly.
I think this confirms the problem is the flex cable.
Once again, thanks for your help!

[Q] Unrooted phone stuck in Android System Recovery

Hello everyone,
My phone is NOT rooted. Earlier today it was stuck on the Samsung Screeen when I turned my phone on. I then used the power, camera, volume down button combo to bring me into recovery mode. Now everytime my phone turns on it stays in recovery mode. I can scroll up and down on my choices but there is not a key that I can press that will select a choice. Any ideas for how I can get my phone to work?
Screen I am stuckl on reads: "android system recovery <3e>
enter: OK key, Select : Vol UP/ Vol Down
reboot system now
apply update from SD cared
Wipe Data/factory reset
wipe cache partition
then theres an exclimation mark in a triangle with the android dude below that
#manual Mode#
If you don't care about existing app data, Odin would be a great choice. Either Odin-ing in a custom recovery or a fresh stock system would get you out of the situation.
Sent from Samsung Captivate Glide @ CM10.1.2
Sounds like you tried to do something and the phone didn't like it, hence you boot back into recovery on it's own.
Use Odin and reflash stock.
Much Thanks
Thank you very much for the responses, for some reason I was under the impression that your phone had to be rooted in order to use odin, much thanks!
I do not care about my personal files getting lost, but just out of pure curiosity, roughly, how would one accomplish that?
I'm try out odin now!
Back to my old problem! Any ideas?
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
apugslovesxda said:
So odin passed twice with all the stock software. Now I am back to my old problem that I had before I was stuck on the recovery screen (hardware issue? idk) When my phone boots up it stays on the samsung screen for 2 mins, then it lags like crazy on the 4g screen (sound and video), and it stays frozen at the Galaxy S screen (for over 6 mins). I need a working phone, luckily I am elgible for an upgrade, but really dont see the need to spend 250 to upgrade my phone or spend 100 for insurance to replace it!
Any ideas anyone?
Thanks again for all of your help so far
Click to expand...
Click to collapse
Well, first boot of flashing any custom or stock rom takes a bit to fully boot. If you're stuck at the Samsung or Galaxy S screens, then you should reflash. If you have tried that and still having the same issue, then try a few more times. I've read posts of people having constant boot loops on flashes and they finally got one flash to properly stick after many tries.
So odined again and again, this time my phone eventually did turn on but it literally took 30 mins. When it did turn on I had no network connection nor could I use my touchscreen, it eventually shut off. I'ma go get robbed at the sprint store in a bit lol.
End Thread
End Thread- I got a Samsung Galaxy Note 3. My god- this phone is amazing. Kinda bull**** that I got nothing for my old phone with full insurance when it seems like it was a hardware failure!
Can't wait to play with this beast of a phone tomorrow!

[Q] White-red-ish screen, in big trouble?!

Hey,
so I just recently bought the Oppo Find 7 (2560x1440) and just wanted to root it and install a custom ROM. When I attempted to flash another recovery it failed, I assume due to resolution issues (it only showed half of the recovery while flashing incredibly).
Then I managed to get nameless' recovery which apparently has the right resolution and could work with it. But it was already reddish / white from the get go, didn't think much of it and kept using it.
Now, when booting up the device, there's a white/red corner around the whole screen, that is supposed to be black and I can see elements from nameless' recovery.
Also flashed CM12 onto it and everything is white/red, when pressing the power button to lock / sleep the device, and pressing it again screen stays black.
Any help would be appreciated.
Problem solved. Thread closed at OP's request.

Categories

Resources