I've searched for this issue for a while but nothing comes up. If i missed it or this post is redundant . I apologize in advance.
Last week, My Sony xperia Z1c screen broke ,so i changed a new one. After that a few hour, I locked phone and when i wake it up, Touch screen wasn't respond. I mean phone is still functional ,you can see new notification coming up, but can't touch anything. Until I hard reset my phone, it was back to normal, touch screen is working, JUST FOR A WHILE. And this issue keep coming back.
I went back to a shop that changed my broken screen in the first place. They changes a new screen for me again, But the issue was still there.
I've no idea what's happens to my phone. Does anybody having a same issue? Please Help me.
Did you try to flash other firmware and check if this still persist?
Madtung said:
I've no idea what's happens to my phone. Does anybody having a same issue? Please Help me.
Click to expand...
Click to collapse
perhaps there needs to be a calibration process after the screen has been installed.
If it were my phone I would try and flash with the latest firmware for your area/provider.
I would recommend IaguCool's thread on Xperia Firmware Downloader & Checker, if you have flashtool installed you can make your own ftf that is exactly right for your phone.
Related
First time I tried flashing I got a error 270. And that was after running the SDA app unlock. So then I tried using the USPL error 270 fix. The problem I'm having Is right when it says "the screen should turn almost black". The screen turns white. At that point active sync doesn't recongnize the phone anymore, and the phone is stuck unresponsive, with a white screen.
So heres a few questions to make sure I'm doing this right.
When I run the sda unlock. Should the phone respond in any way? When I press the ok button I get a instant verification that the phone is unlocked. The phones screen doesn't light up or anything of the sorts. It almost seems like nothing happened.
When you say reboot (yeah this is a dumb question!) I'm just turning the phone off, and then turning it back on again. Is the correct way to do it?
It is a brand new excalibur I'm working with. The one with the all black face. I just figured I should throw that in there in case there was any little difference that would be causing me problems.
I can't wait to get this phone flashed! Looking at all the tweaks and tricks and not being able to try them out is killing me!
oilspot said:
First time I tried flashing I got a error 270. And that was after running the SDA app unlock. So then I tried using the USPL error 270 fix. The problem I'm having Is right when it says "the screen should turn almost black". The screen turns white. At that point active sync doesn't recongnize the phone anymore, and the phone is stuck unresponsive, with a white screen.
So heres a few questions to make sure I'm doing this right.
When I run the sda unlock. Should the phone respond in any way? When I press the ok button I get a instant verification that the phone is unlocked. The phones screen doesn't light up or anything of the sorts. It almost seems like nothing happened.
When you say reboot (yeah this is a dumb question!) I'm just turning the phone off, and then turning it back on again. Is the correct way to do it?
It is a brand new excalibur I'm working with. The one with the all black face. I just figured I should throw that in there in case there was any little difference that would be causing me problems.
I can't wait to get this phone flashed! Looking at all the tweaks and tricks and not being able to try them out is killing me!
Click to expand...
Click to collapse
Yes rebooting is when your phone turns off and back on. Soft reset is when you power the phone off and power it back on.
Did you follow these instructions to T?http://forum.xda-developers.com/showthread.php?t=415225
http://forum.xda-developers.com/showpost.php?p=2807194&postcount=485
stylez said:
http://forum.xda-developers.com/showpost.php?p=2807194&postcount=485
Click to expand...
Click to collapse
ran both, failed at 0% this time. Left the phone stuck with the tri colored screen. But, in that thread, it says I may have to try it a few times. I'll give it another shot and see what happens.
really wish rebooting the phone was quicker!
tried again. phone locked up and didn't want to connect with active sync.
overall I've tried several times. Is it normal to have this many problems? I'm starting to get frustrated!
Don't get me wrong. I really appreciate all the info and help I'm getting with this. The frustration is just not being able to make it work.
oilspot said:
ran both, failed at 0% this time. Left the phone stuck with the tri colored screen. But, in that thread, it says I may have to try it a few times. I'll give it another shot and see what happens.
really wish rebooting the phone was quicker!
tried again. phone locked up and didn't want to connect with active sync.
overall I've tried several times. Is it normal to have this many problems? I'm starting to get frustrated!
Don't get me wrong. I really appreciate all the info and help I'm getting with this. The frustration is just not being able to make it work.
Click to expand...
Click to collapse
No it normally doesn't give you that many problems, except if you made a mistake flashing. I flashed three times within my first week before I found the rom I liked, and never had a single problem. See what I did was print all the instructions on flashing and had them on my lap while I was flashing and double checking every step before going to the next. Is very important that you follow the steps to a T so nothing like this happens. If you can get the bootloader screen , I would suggest to reinstall the official 6.0 rom, get the phone back to factory, and then try again to flash to 6.1.
Do you know the bootloader procedure?
I'm following these instructions... to a T.
http://forum.xda-developers.com/showthread.php?t=415225
I'm not sure if you would call that a bootloader procedure? Is there something else I need to know how to do?
I've had it completely lock up during the flashing process, and have had to pull the battery to get the phone to work again. The phone works just like normal after I've had to do that. Are you saying that I need to re flash the stock rom before I can flash it to a different one?
oilspot said:
I'm following these instructions... to a T.
http://forum.xda-developers.com/showthread.php?t=415225
I'm not sure if you would call that a bootloader procedure? Is there something else I need to know how to do?
I've had it completely lock up during the flashing process, and have had to pull the battery to get the phone to work again. The phone works just like normal after I've had to do that. Are you saying that I need to re flash the stock rom before I can flash it to a different one?
Click to expand...
Click to collapse
The phone is working normally now? so nothing happened? are you still on the 6.0 and everything is operational? If you are then you don't need the bootloader.
yeah the phone works fine. No glitches.
Got frustrated with it yesterday so I just left it. Going to try again today.
Does it make any differance that it's the new black faced excalibur? I read that not much changed except the color.
WOO-HOO!
I got it! Did the same things I did before, for some reason this time it worked.
Have only had a few minutes playing with it but so far I love it! I was dissapointed with the lack of configuration in the "stock" OS. I've already got everything moved around just where I want it.
Thank you soo much for the help! You guys are great!
oilspot said:
WOO-HOO!
I got it! Did the same things I did before, for some reason this time it worked.
Have only had a few minutes playing with it but so far I love it! I was dissapointed with the lack of configuration in the "stock" OS. I've already got everything moved around just where I want it.
Thank you soo much for the help! You guys are great!
Click to expand...
Click to collapse
Awesome, glad you figured it out. Enjoy.
Hi
I am facing unusual touch behaviour with my widfire , the problem has been persistant past 2 days but today its on and off.
When i try to flick the pages between the 6 homecreens i mostly end up with 6 screen formation which usually occur when i pinch in home screen or press the home button in home screen
also i am getting this 6 homecreens pinch in formation in home screen everytime i flick from lower left corner toward the upper right 10/10 times .
i havent seen this behaviour before.
and while unlocking lock screen i have to press power button again twice to unlock it
I tried checking by playing Air control, i am unable draw the path of planes across lower left region , seems like a patch doesnt responding in tht region alone
But this issue doesnt happen all time, its on and off. at time my mobile works perfectly fine ,even the air control game
I tried reseting my phone and removed my memory card but it didnt help
has thisproblem occured to anyone before
kindly post your replies
thank you
pradeep
I'd recommend flashing RUU, see if this fixes the issue, if not send it to HTC if under warranty.
Regards
f0xy said:
I'd recommend flashing RUU, see if this fixes the issue, if not send it to HTC if under warranty.
Regards
Click to expand...
Click to collapse
Can you link me to any guide for flasing RUU.
Thanks
f0xy said:
I'd recommend flashing RUU, see if this fixes the issue, if not send it to HTC if under warranty.
Regards
Click to expand...
Click to collapse
i have flashed RUU 1.25vers but it didnt solve the problem
so i went to HTC but had my touch replaced
But the problem is whether i need to root again.
i tried restoring through rom manager was unsucessful
even went through recovery but was unable to restore
Have i need to go through the rooting process once again
please help
Flashing an RUU will remove root. So, you will have to root again.
3xeno said:
Flashing an RUU will remove root. So, you will have to root again.
Click to expand...
Click to collapse
Sucessfully Re rooted and restored my previous phone
thanks for your replies.....
after i have rooted and restored the original firmware after software bricking it trying to unlock the bootloader on my E975, i restored the original software and rooted it, but it's like sometimes when i click i only get black screen on, and click again i get the phone unlocked and ready to use, and after that, it doesn't matter help much i push down the power bottom it don't come up with the menu but turn off the screen and i can battle with it for sometime and it automatically reboots.
anyone got a solution for this, i am ready to try it, bcs i am tired of having this problem :crying:
hmm it has already happened twice after i made this post.
hmm yesterday i got enough, and reflashed the original firmware E97510B_00.kdz (E97510b-EUR-xx) i downloaded it with this Application for download Original LG Firmware.
this morning when i didn't hear the alarm normally this doesn't happen, but the alarm got stuck, and after 20mins or something when i force stopped the Alarm/Clock the phone rebooted on it's own.
could it be that the Original LG Firmware program found the wrong firmware out from my phone's serial i put in?
No
Did you do a factory reset?
rogem_kk said:
No
Did you do a factory reset?
Click to expand...
Click to collapse
yap, right after flashing the phone, and i tried around 8 or something this morning after it ****ed up again, downloading Apex Launcher Pro and installing it, and that worked for like 5 or 6 hours without a problem but then like less then an hour ago i just got black screen using the power bottom :crying:
so what is wrong here?
hmm no one got a solution or something I can try to do so I can get rid of this problem?
hmm, not much about the problem i see, so maybe i am the only one?
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?
Hi all,
I am encountering this strange bug randomly: sometimes the device Is rebooting itself and it goes automatically in recovery mode, sometimes after a reboot it does the same. The error is always: Can’t load Android system. clicking on “try again” solves the issue (sometimes at the first retry, sometimes after some retries).
I’m attaching the error screens, also because the error message is not every time the same (Attaching also a normal way to enter recovery).
Has someone encounter this bug?
Any hints on how to solve this? I haven’t already do a full reset of the phone, but i think it wilL be the next step I’ll do if the phone is continuing like this.
Thanks!
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.
Arobase40 said:
This mostly happens when you did some tricky things on your phone. lol
If full reset is not enough (specially when the system is missing....) you'd have to restock it with an official Samsung firmware... ^^
Click to expand...
Click to collapse
Hi Arobase40, thanks for your answer.
Yes i know that this things could happen if you do some strange things to the phone (and in my past i was used to that ) but in this case, all is pure and untouched, no unathourized apk and no modding at all. (My use is quite noob-ish now eheh)
And that's seems very strange! :/ I made only ota update and this happened both with android 11 and 12.
Arobase40 said:
Well ok, in your case try to flash back a stock firmware from Samsung with Frija or Samfw (don't forget to supply the correct model and CSC) using PC Odin.
If that don't fix the problem then get in touch with your local Samsung website and you should find a phone number for the after sale service and they will give you the nearest Samsung official repair center from your home.
They should fix this issue very quickly using most probably the same tool which is PC Odin.
If you go to the repair center don't forget to backup all your apps and data, remove your scard if you have one and also your sim card...
Click to expand...
Click to collapse
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
IvanCattaneo95 said:
Thanks for your help and explanations.
Just to be updated and make some laugh: today the phone while was charging has become completely unresponsive, showing "Samsung Galaxy" on a black screen when touching Power Button or connecting to Power. After a while (hard pressing Power Button and Power+vol up) it restart itself and works again. Never had such an experience with a phone (a COMPLETELY stock phone)
Click to expand...
Click to collapse
Idk, seems like a hardware issue to me. Try and have a go at where you've bought it and have them check it over.
My first thought too is hardware.
A few years ago I had something similar with a different phone (Moto G) - as a last ditch effort I popped out the SIM and SD cards and reseated them and it worked perfectly after that. If you have an SD card you might even want to leave it out a few days just to see.
Not saying this is your issue but couldn't hurt to try!