First of all, ive tried searching all morning for a fix - but so far no dice.
I have an xperia z2 that's is about 7 months old, and over the past two or three days I've started running into issues where the screen is really slow to wake up. Instead of being instantaneous when pressing the wake/power button, there is a 2-3 sec delay before the screen turns on and I can swipe to unlock.
I've tried removing the SD card (which can apparently cause this type of issue) but wanting to hear other opinions before I try messing around with wiping caches in recovery etc.
Any thoughts?
Thanks
Try reflashing your rom.
If that doesnt fix it then reflash a FTF
Ive descovered that very rarely a partition can corrupt and cause some odd lag on a device.
Forgot to mention that the screen has stopped auto-rotating as well. Are these issues likely to be connected?
nick_sixx said:
Forgot to mention that the screen has stopped auto-rotating as well. Are these issues likely to be connected?
Click to expand...
Click to collapse
as said try reflashing your Rom(if runing a custom one). if its still there try flashing A FTF.
if the problem is still there after that then the device has become defective and should be covered by warrenty. you should recieve a free repair if you call sony mobile.
Envious_Data said:
as said try reflashing your Rom(if runing a custom one). if its still there try flashing A FTF.
if the problem is still there after that then the device has become defective and should be covered by warrenty. you should recieve a free repair if you call sony mobile.
Click to expand...
Click to collapse
Hmmm not running a custom ROM but will give FTF a whirl
Envious_Data said:
as said try reflashing your Rom(if runing a custom one). if its still there try flashing A FTF.
if the problem is still there after that then the device has become defective and should be covered by warrenty. you should recieve a free repair if you call sony mobile.
Click to expand...
Click to collapse
Hmmm not running a custom ROM but will give FTF a whirl
Related
Hey Guys, been Having A Problem With My Xperia Recently.. I Will Say That It Is On Stock Firmware & Kernel After Some Advice From Sony Support But The Problem Still Isnt Fixed..
The Fone Has A Mind Of Its Own Sometimes It Will Turn Off IN My Pocket No Apparent Reason Then Red Light Flashes, To Switch It On I Usually Have To Pull Battery Out Hold Back Button And Power On..!
Sometimes It Will Just Freeze On The Main Screen When I Come To Use It & Even Reboot Itself Sometimes...
Any Ideas On How To Fix This @ All Cuz It Doing My Tree In Doin The Same Routine Daily 5-6-7 times....!
Thanks In Advance..!
X10i
2.3.3 Android Version
2.1.71 BB
2.6.29-00054 Kernal Version
3.0.1.g.0.75 Build
Rooted?
If not, may be the motherboard. I've got the same problem with mine, and I'm going to return it to store for a fix.
You may also want to try to plug it to the computer and open PC Companion and try the "repair" function. But backup everything you need first, I don't think everything get's deleted but be aware that it may happen.
Do u overclock it?
Sent from my X10S using XDA
Sikiduck said:
Rooted?
If not, may be the motherboard. I've got the same problem with mine, and I'm going to return it to store for a fix.
You may also want to try to plug it to the computer and open PC Companion and try the "repair" function. But backup everything you need first, I don't think everything get's deleted but be aware that it may happen.
Click to expand...
Click to collapse
Ive Done That And It Seems To Not Have Fixed The Problem @ All, Its what SE Sent Me An Email Explaining How To Fix It..!
laneyofdeath said:
Do u overclock it?
Click to expand...
Click to collapse
Not To My Knowledge @ The Mo Its Just Running Standard Firmware & Kernal..!
Hi, I got a similar problem. Since a few weeks ago, flashed a ROM and when I've tried to use the phone, it keeps turning off randomly, sometimes after a few minutes, sometimes after hours. So, I tried to take it back to the clean original 2.3.3 ROM, but it keeps happening. ¿Any idea? ¿Any solution? Please, help me.
h3nd0 said:
Ive Done That And It Seems To Not Have Fixed The Problem @ All, Its what SE Sent Me An Email Explaining How To Fix It..!
Click to expand...
Click to collapse
Didnt PCCompanion/seus fix it? And still persists?
Then it's time to get a new chipset.
Or a new device.
mickeas said:
Hi, I got a similar problem. Since a few weeks ago, flashed a ROM and when I've tried to use the phone, it keeps turning off randomly, sometimes after a few minutes, sometimes after hours. So, I tried to take it back to the clean original 2.3.3 ROM, but it keeps happening. ¿Any idea? ¿Any solution? Please, help me.
Click to expand...
Click to collapse
Did u try the repair function in PC Companion/SEUS (SE update service)?
Sent from my LT26i using xda premium
Hi mates!
Few months back I unlocked my bootloader and recently used many custom ROMs and kernels. Unfortunately I could not use my wifi properly - I was on FreeXperia kernel and at very start wifi worked ok, but it stopped finding any networks after couple days of rom usage. Problem was reported on the Android Development sections in the ROM thread by many users, so I thought it will be fixed soon. Couple days ago I switched to DoomKernelv3, his wifi modules and Oodies MIUI ROM - worked perfectly but my wifi worked occasionally and stopped working again. I got back to stock now and I'm on Z's Recovery (very first one I used and had no wifi problems) and problem with no wifi networks still persists. Did I brick my wifi somehow? Is it possible? Does anybody experienced similar problem?
Any help would be GREATLY appreciated.
hey
honestly... i think there is a hardware problem in your phone....
cuz even after switching rom's you still have the same problem....
i would sugggest that your use seus and get back to stock version... and just get it fixed by them.....just keep saying them that wifi doesnt works and all.....
rohit25 said:
honestly... i think there is a hardware problem in your phone....
cuz even after switching rom's you still have the same problem....
i would sugggest that your use seus and get back to stock version... and just get it fixed by them.....just keep saying them that wifi doesnt works and all.....
Click to expand...
Click to collapse
Seus says my phone is up to date. Besides, I assume I need to unoot it and lock the bootloader back to use varanty?
Sent from my X10i using xda app-developers app
easy pesy
botson said:
Seus says my phone is up to date. Besides, I assume I need to unoot it and lock the bootloader back to use varanty?
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
very easy mate....
just open seus.... support->update phone->repair phone written in red color->wait and then from the list of phone choose your's->now take the battery out for 5 seconds(15sec might also work)->put the battery in->press back button and keep pressing it and then connect the usb cable....->it would flash the stock rom back plus automatically lock the bootloader again....
VOILA....
claim your phone is having hardware problems to the repair guys..... if under warranty
rohit25 said:
very easy mate....
just open seus.... support->update phone->repair phone written in red color->wait and then from the list of phone choose your's->now take the battery out for 5 seconds(15sec might also work)->put the battery in->press back button and keep pressing it and then connect the usb cable....->it would flash the stock rom back plus automatically lock the bootloader again....
VOILA....
claim your phone is having hardware problems to the repair guys..... if under warranty
Click to expand...
Click to collapse
I don't think seus locks your bootloader you have to use s1 tool I'm pretty sure I may be wrong though
sent from my x10 using xda premium
it does lock.... coz every-time i got f'd while flashing i used seus and had to unlock the boot-loader every-time.... even though i checked with s1 tool first if the boot-loader was locked or not....
any way if you r on stock rom... those repair guys... wont even notice that you flashed the device
Hi!
I have had the same problem as you. Still after repairing it in PC Companion, the problem was still there.
So I left the phone for couple of days because I got Xperia S, and when I turned it on one day and searched for WiFi networks, it finally found some networks!!!
I don't know what 'fixed' it, but I think it's a hardware issue and I was going to get it repaired until it fixed itself
Sent from my LT26i using xda premium
I repaired the system with SEUS, no Recovery or root available anymore. I assume bootloader is locked back. Wifi works same way as it worked. Is there some wifi debug software to figure out what is going on?
Anyone?
botson said:
I repaired the system with SEUS, no Recovery or root available anymore. I assume bootloader is locked back. Wifi works same way as it worked. Is there some wifi debug software to figure out what is going on?
Anyone?
Click to expand...
Click to collapse
yes, me use rom manager. browse all options. u should see one called wifi scan interval. if i am not wrong, default is 480. change to the lowest possible
I'm kindly posting this question to help my friend's X10 Mini Pro.
The phone is hardbricked two times, the first one is we accidentally flashed the wrong .ftf file on Flashtool last month and sent to repair center, it came back to life. The second one is that the phone did not power on after turning it off (happened almost 1 month after the repair). So here's the problem:
So the phone vibrates shortly everytime I'll try to turn it on but there are no signs of led and screen to lit up. The good news is the computer (I'm using Win7) recognizes the phone when I connect it but a couple of seconds, it just disconnects and reconnects again sometimes it just normally connects with no interruption. I tried to flash back to stock using Flashtool (the .ftf file)
According to the message log, it successfully flashed so I disconnected it and turned on the phone but still, it just vibrates and the screen did not turn on. Tried Sony PC Companion-failed I don't know if the bootloader is STILL unlocked after the repair because I unlocked the bootloader before the first hardbrick event happened. So I'm thinking about what if he accidentally accepted an OTA update? maybe that's the reason of being hardbricked? what do you think? I really appreciated your help
Hi ,
You tested another of kernel? Probably, is a bad question, but, can helped with solveding your problem...
GAMELASTER said:
Hi ,
You tested another of kernel? Probably, is a bad question, but, can helped with solveding your problem...
Click to expand...
Click to collapse
Nope I don't tested any kernel yet because it might give me a big problem than this situation
JovieBrett said:
Nope I don't tested any kernel yet because it might give me a big problem than this situation
Click to expand...
Click to collapse
:/ You have only one solution: repair.... The reason of the problem is[probably] new chip with Hard Secure, when you a hard bricked your phone...
GAMELASTER said:
:/ You have only one solution: repair.... The reason of the problem is[probably] new chip with Hard Secure, when you a hard bricked your phone...
Click to expand...
Click to collapse
Omg again
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
baldevp said:
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
Click to expand...
Click to collapse
You are not alone.
The question is if you have warranty or not?
Because if yes, that play dump in Sony Service Center.
Otherwise you will need to open your device.
Solution is not ready yet, I am working on it.
I am waiting for new battery(I damaged mine), after that I will continue experiments.
Stay in touch in this tread, it's for Z1, but they have hell a lot of bricks.
vovanx500 said:
You are not alone.
The question is if you have warranty or not?
Because if yes, that play dump in Sony Service Center.
Otherwise you will need to open your device.
Solution is not ready yet, I am working on it.
I am waiting for new battery(I damaged mine), after that I will continue experiments.
Stay in touch in this tread, it's for Z1, but they have hell a lot of bricks.
Click to expand...
Click to collapse
its rooted do you expect warranty on that
baldevp said:
its rooted do you expect warranty on that
Click to expand...
Click to collapse
If you got a red blinking led or no led at all, then they will change a motherboard.
Even if you got unlocked bootloader.
Just go to Sony and tell then something like " The Sony software asked for update,and after that my device died"
Remember not to use words such "Root" or "firmware"
Just play noob.
Just make sure phone is completely dead
My situation is worse, my phone is from Singapore so, no warranty for me.
vovanx500 said:
If you got a red blinking led or no led at all, then they will change a motherboard.
Even if you got unlocked bootloader.
Just go to Sony and tell then something like " The Sony software asked for update,and after that my device died"
Remember not to use words such "Root" or "firmware"
Just play noob.
Just make sure phone is completely dead
My situation is worse, my phone is from Singapore so, no warranty for me.
Click to expand...
Click to collapse
thanks man a lie can surely save my day
baldevp said:
thanks man a lie can surely save my day
Click to expand...
Click to collapse
You are welcome.
You can always open your device, but then no warranty for sure.
vovanx500 said:
You are welcome.
You can always open your device, but then no warranty for sure.
Click to expand...
Click to collapse
ya why to void it
baldevp said:
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
Click to expand...
Click to collapse
Which ftf did you flash?
What parts of the ftf did you flash (or exclude)?
What exactly are the symptoms?
What was the battery state when you started the flash?
What firmware did you start on?
What dos the LED do when the phone is on charge?
Does the PC make any sound or say anything when the phone is connected?
What does flashtool say when the ultra is connected?
baldevp said:
ya why to void it
Click to expand...
Click to collapse
I got your PM... I'm hoping that you were using the latest version of Flashtool. As that could be the bugger!
Using the previous version has been bricking devices flashing .290. Not sure about .132 but im betting it does too...
Check if you had the latest version.... if not then your are currently screwed!
If it was the latest, then I'm sure it can be resolved.
Note: opening your device rips some adhesive tape inside it. So then technicians know that you've been inside your device... and hence warranty void!
hamdogg said:
Using the previous version has been bricking devices flashing .290. Not sure about .132 but im betting it does too...
Click to expand...
Click to collapse
This is mostly for @hamdogg regarding the above
One thing I have noticed and has been mentioned in the Z1 forum is that flashing .290 ftf often dropped the battery by huge amounts, I have seen 40% or more, and then very fast charging - looks like calibration is right out of whack.
Yesterday when flashing to play with root (I flashed .136 mayby 6 - 8 or more times) I never saw a battery drop/jump outside of the few % I would expect from a full flash.
This leads me to believe that there was something very wrong in .290
blueether said:
This is mostly for @hamdogg regarding the above
One thing I have noticed and has been mentioned in the Z1 forum is that flashing .290 ftf often dropped the battery by huge amounts, I have seen 40% or more, and then very fast charging - looks like calibration is right out of whack.
Yesterday when flashing to play with root (I flashed .136 mayby 6 - 8 or more times) I never saw a battery drop/jump outside of the few % I would expect from a full flash.
This leads me to believe that there was something very wrong in .290
Click to expand...
Click to collapse
Yeah good points. When piecing together the ROM tree for doggROM (still not 100%, but its up; need to work on the kernel image) I noticed quite a few added lib files. There are a few changes that we probably wont see for a while.
I also flashed dogg and stock FTF probably about 10 times yesterday. went from 60-30-odd %... not bad for constant use for 3 hours and then flashing different ROM's..
blueether said:
This is mostly for @hamdogg regarding the above
One thing I have noticed and has been mentioned in the Z1 forum is that flashing .290 ftf often dropped the battery by huge amounts, I have seen 40% or more, and then very fast charging - looks like calibration is right out of whack.
Yesterday when flashing to play with root (I flashed .136 mayby 6 - 8 or more times) I never saw a battery drop/jump outside of the few % I would expect from a full flash.
This leads me to believe that there was something very wrong in .290
Click to expand...
Click to collapse
Same thing happened to me yesterday. I continuously flashed or 2-3 hours first flashed .532 to gain root ,then flashed.290 couple of times, and then.136 .
Flashing .290 always lead to drop in % around 40.But after flashing .532 over .290 lead to battery percentage rise.Also flashing .136 or .532 had percentage dropped by 5-6 only.
Now am on .136 and charged it and charging was way faster than before.
Wanted to know did it anyhow damaged the battery considering the faster charging?
Or it will be normal after a while?
baldevp said:
Bricked my phone by flashing it with firmware in this link http://forum.xda-developers.com/showthread.php?t=2453921, now it wont go into flashmode or do anything infact any ideas how to revive it
Click to expand...
Click to collapse
What firmware were you updating from?
Did you use latest Flashtool?
Most importantly, did you flash the 136 kernel but not the 136 bootbundle?
Im asking because if answer yes to the last question, the brick bug hasn't been fixed.
blueether said:
Which ftf did you flash?
What parts of the ftf did you flash (or exclude)?
What exactly are the symptoms?
What was the battery state when you started the flash?
What firmware did you start on?
What dos the LED do when the phone is on charge?
Does the PC make any sound or say anything when the phone is connected?
What does flashtool say when the ultra is connected?
Click to expand...
Click to collapse
it does not connect man, its ****ed up, i cant connect it in any mode or start it, it goes goo-gaa some time when connected to lappy by connecting-disconnecting continously but many times do not connect i flashed the generic firmware, 1 st link on the link given originally
baldevp said:
it does not connect man, its ****ed up, i cant connect it in any mode or start it, it goes goo-gaa some time when connected to lappy by connecting-disconnecting continously but many times do not connect i flashed the generic firmware, 1 st link on the link given originally
Click to expand...
Click to collapse
We want to know exactly the firmware you flashed, just saying the first link is hard for us, as we dont know the model phone you have etc
anyway did you just leave it as all defaults when you flashed?
and what about the other questions?
blueether said:
We want to know exactly the firmware you flashed, just saying the first link is hard for us, as we dont know the model phone you have etc
anyway did you just leave it as all defaults when you flashed?
and what about the other questions?
Click to expand...
Click to collapse
battery was way above 80%
I didn't exclude any part
the pc connects and disconnect and many times doesn't even detect it
flashtool doesn't detect it
flashtool version 0.9.11.0
I used the earlier 14.1.B.1.526 GENERIC Taiwan http://forum.xda-developers.com/showthread.php?t=2439438
baldevp said:
battery was way above 80%
I didn't exclude any part
the pc connects and disconnect and many times doesn't even detect it
flashtool doesn't detect it
flashtool version 0.9.11.0
I used the earlier 14.1.B.1.526 GENERIC Taiwan http://forum.xda-developers.com/showthread.php?t=2439438
Click to expand...
Click to collapse
ok, that is a different link than in your first post, but atleast we know what you were flashing.
What firmware were you on before the flash?
I have a feeling the issue might be with the old version of flashtool. I have used that version before without issues, and also that FTF without issues.
I think it might be bricked, but there may still be hope.
Upgrade flashtool to at least 0.9.13.0
Reboot the computer
Reinstall drivers
If you hold the volume + and plug in the phone to the PC do you get any lights on the Ultra?
How about if you hold the volume - and plug in the phone to the PC doe the leds flash then go out?
do the above two while the new flashtool is running and post it's output if you can.
I'll be away fron a PC for most of the next 30+ hours but hopefully @hamdogg, @LordManhattan, @zeppelinrox will have some more hints
Oh it's likely due to the old Flashtool version.
9.13 was giving an error (at bootbundle phase) to one guy so he tried 9.11
Bricked it.
http://forum.xda-developers.com/showthread.php?t=2624641
9.11 and newest ftfs don't go well together but I don't know exactly why.
Does 9.11 not flash the bootbundle?
@Androxyde would have the best guess as to what goes wrong with 9.11
But my guess is that you ended up with a 526 bootbundle with the 136 kernel and if so, that means the brick bug hasn't been fixed.
zeppelinrox said:
Oh it's likely due to the old Flashtool version.
9.13 was giving an error (at bootbundle phase) to one guy so he tried 9.11
Bricked it.
http://forum.xda-developers.com/showthread.php?t=2624641
9.11 and newest ftfs don't go well together but I don't know exactly why.
Does 9.11 not flash the bootbundle?
@Androxyde would have the best guess as to what goes wrong with 9.11
But my guess is that you ended up with a 526 bootbundle with the 136 kernel and if so, that means the brick bug hasn't been fixed.
Click to expand...
Click to collapse
so what do i do now, will they accept it at service centre if i play noob
Yep they will.
It got bricked while updating to latest Sony release.
Just get an RMA from Sony support.
First they'll give you instructions on how to reset the phone with PCC.
Then you say "hello... I can't get into flash mode..."
Need an RMA and BTW, there's over a hundred reported bricks plus god knows how many more
I know I asked you guys about this before, but since I don't want to bump that thread I thought of starting another one instead.
I'm at a loss as to why my mum's Xperia Go kept on hanging up and restarting, either after using it for some time, or by itself on occasion. It's been like that since we bought the device, and I didn't even root or tamper it at the time. Even after flashing a custom ROM the symptoms still persist, to which I'm suspecting that it might have something to do with a hardware defect or bug, but is it still possible to fix or at least work around the problem? I can send the phone to the local service centre if needed, but I'm not that arsed to shell some $$$ for having the phone fixed.
I'll see if I could turn up a logcat or dmesg log and paste it here for analysis.
blakegriplingph said:
I know I asked you guys about this before, but since I don't want to bump that thread I thought of starting another one instead.
I'm at a loss as to why my mum's Xperia Go kept on hanging up and restarting, either after using it for some time, or by itself on occasion. It's been like that since we bought the device, and I didn't even root or tamper it at the time. Even after flashing a custom ROM the symptoms still persist, to which I'm suspecting that it might have something to do with a hardware defect or bug, but is it still possible to fix or at least work around the problem? I can send the phone to the local service centre if needed, but I'm not that arsed to shell some $$$ for having the phone fixed.
I'll see if I could turn up a logcat or dmesg log and paste it here for analysis.
Click to expand...
Click to collapse
If flashing ROM didnot help, I would advise you to just send it for warranty/service center. Trust me, the work around to fix it would be too frustrating than to actually fix the phone. Sometimes it takes over 9 hours straight in front of PC with no use....
Hnk1 said:
If flashing ROM didnot help, I would advise you to just send it for warranty/service center. Trust me, the work around to fix it would be too frustrating than to actually fix the phone. Sometimes it takes over 9 hours straight in front of PC with no use....
Click to expand...
Click to collapse
Yeah, but what about the bootloader to which I tampered with? I know there's a way to relock it, but does it also work on the latest stock firmware?
blakegriplingph said:
Yeah, but what about the bootloader to which I tampered with? I know there's a way to relock it, but does it also work on the latest stock firmware?
Click to expand...
Click to collapse
Well, do you know about FLASHTOOL ?
Download it from here.
http://www.flashtool.net/download.php
It can lock your bootloader in a minute.
Also, you can just tell the service centre it hangs alot and restart. No need to tell them what you did with phone!
Good Luck
Hnk1 said:
Well, do you know about FLASHTOOL ?
Download it from here.
http://www.flashtool.net/download.php
It can lock your bootloader in a minute.
Also, you can just tell the service centre it hangs alot and restart. No need to tell them what you did with phone!
Good Luck
Click to expand...
Click to collapse
OK, noted.