Hi,
Last week I purchased a Z3 via Optus Australia. I charged the phone for the recommended 30 minutes before turning on and initially the phone was working fine. As soon as I had internet connection (I had no wifi, and had to wait for my new nano sim to activate which took a couple hours) I began the setup process, syncing my google account etc and the screen basically shat itself. It wouldn't respond to touch or if it did a yellow box would appear and I would have to tap several times to unlock the phone. Did hard factory reset and as soon as I got to the part of the phone setup where I sync my accounts the same thing occurs. I took the phone back to Optus who sent it off for testing, Sony agreed it was ****ed and Optus gave me a brand new z3. I've just tried to set it up and the screen is doing the exactly the same thing as the previous one. Understandably I'm mega pissed off.
So i guess my question is, is this a common fault or am I setting up the phone incorrectly (which I can't see how as I am just following on screen prompts)? Is there anything I can do, or is this one a write off as well? At the moment I'm pretty sure I'm gonna cancel my contract and switch to a samsung or HTC , which is a shame as I was looking foward to this phone.
Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Good luck
Moved!
Hi all,
Hoping a kind tech wiz will be able to help me out here, having had a Z3 for a couple of weeks I dropped it- back down - from a couple of feet and the front glass completely shattered leaving the screen unresponsive.
Having received a quote in the region of £200 I figure I may as well sell it for spares and buy a new device. However, for peace of mind, I'd like to wipe the phone completely before selling it on. Is this possible to do without being able to use the screen?
Thanks
Dan
There are several ways you can factory reset your phone with broken screen. The first one that comes to mind is with PC Companion repair option. Make sure your battery level is above 80%.
Follow this tutorial and you're all set.
https://www.youtube.com/watch?v=CFUEQV6ob_4
fijasko said:
There are several ways you can factory reset your phone with broken screen. The first one that comes to mind is with PC Companion repair option. Make sure your battery level is above 80%.
Follow this tutorial and you're all set.
Click to expand...
Click to collapse
I've tried this but I can't get very far because my phone had a pin lock on before it broke and the companion app doesn't work if the screen is locked. I know what the pin is but obviously can't input it, any other ideas that could help?
Hello,
My father bought Xperia Z5 about a week ago.
Sometimes phone screen just goes black and the phone becomes unresponsive, nothing works except notification LED. It can even happen in mid call.
The only solution to fix this is to restart the phone using volume up + power button. When the phone is restarted, battery stats shows no data while the phone was frozen and it drains the battery much faster.
It has already happend twice in 7 days.
Does anyone else face the same issue?
Any reccomendations on what should I do ? Or should I just send the phone to warranty?
Thanks.
do a software repair with sony pc companion and report back
Ok I did the repair
2 days so far so good but im not 100% confident that it's gone. I'll reply if it occurs again
Sorry for reviving and old post. I guess the OPs issue as resolved by the companion repair?
I had this issue with my Z5 and non of the steps suggested (here or by Sony) worked - reset factory defaults, sony companion repair etc. I even waited for the 6.0 update to fix it and it made it worse . I sent my phone to Sony for repair, they said it was the screen which was replaced (at my expense) and when it came back it froze on the first charge .
Just got off the phone with Sony support and they said the most common cause of this issue is incompatible SD cards (or incompatible data on SD cards). Not sure I am convinced but thought I would mention it as I never saw this mentioned when googling this issue before!
Will post back if the issue reoccurs after reformatting my SD card (it had been used on a previous phone).
==Update==
Well that didn't take long. The phone crashed (within 3 hours) even without an SD card...
Wait a minute - Sony says the cause of the problem is the screen and makes you pay for the replacement???
Ever figure out what the problem was?
DroidDogg said:
Ever figure out what the problem was?
Click to expand...
Click to collapse
No, I've had to send it back to Sony multiple times with no fix. Now they have agreed to replace the handset and send me a new one in hopes it will fix the issue - here's hoping it's hardware, not a software issue.
And yes, Sony made me pay for a replacement screen, even though the screen wasn't the issue (it had a line of dying pixels, so wasn't 100%, but shouldn't have crashed the phone). No joy on a refund for the repair either.
A little while ago I broke my screen on my Sony Xperia z3 compact, so naturally I replaced the screen and the digitzer, and it worked (hurray!) for about five minutes (Boo!), after which the backlight stopped working, apparently this is a common issue and I managed to find a solution after googling "sony experia z3 compact backlight not working". Should be the first result (cant post outslde links as noobie)
So i attempted to make the jumper with a soldering Iron, but my soldering experience is clearly evidence of my ability to break phones as in the process I burned through the component (I think. though the whole mess is covered in Solder right now). And although the charging light comes on the phone it self will not turn on. It is completely dead, I have tried various resets but none work, I should mention the phone worked perfectly before hand it was just the backlight that was the problem..
Is it time to get a new phone, or is there still hope? I've already sunk over £100 into trying to repair the stubborn basterd but I've not quite given up hope
Hi,
I would say you need to buy a new phone, but I'm not good at repairing phones either, so perhaps you should register and ask your question here. Good luck!
Hi all. I have a 2016 Sony Xperia XZ running on Android 8.0 Oreo. My battery got swollen and I try to replace it with newer battery.
The process went normally, but when I try to boot the device, the phone just shutdown and after its reboot, I got a message said "your device is corrupted and cannot be trusted".
It's weird, it never happened before. And when I shut off the phone, it didn't even charge. My question is;
1.Did I messed up the battery connector, I try using my old battery(swollen, but still has good health), but it got the same issue, and it wouldn't charge.
2.If I messed up the battery connector, for sure it wouldn't boot up, but the phone boots, but after 1 second it shut off.
3.Does sub-par BMS chip can cause the motherboard goes haywire? Or it just a firmware/software issues?
4.I use a Japan secondhand set(SOV34 KDDI AU), the bootloader is can't be unlock, but I already enable USB debugging on developer option, can I use any firmware flasher on Windows?
Try a factory reset.
You may have damaged the display and/or mobo assuming it has power.
The brick alone doesn't supply enough current to boot.
blackhawk said:
Try a factory reset.
You may have damaged the display and/or mobo assuming it has power.
The brick alone doesn't supply enough current to boot.
Click to expand...
Click to collapse
Thanks for your reply, I will try it. My phone is a Japan secondhand set with bootloader status unlock: no, but I still can use Flashtool or Sony Companion right?
faizikari said:
Thanks for your reply, I will try it. My phone is a Japan secondhand set with bootloader status unlock: no, but I still can use Flashtool or Sony Companion right?
Click to expand...
Click to collapse
The firmware shouldn't be corrupted. It rarely happens. If you flash go with a stock rom although with an unlocked bootloader you have more flexibility. Try to rule out a hardware issue first.
A factory reset wouldn't be the first option I would until I was confident it wasn't a hardware caused failure. Flashing be my last resort. I never had to flash any of my Androids in over a decade due to corruption. Usually it's the user partition that gets corrupted or more likely a 3rd party app screws it up. A factory reset would set back to its default settings*.
The bootloader being unlocked plus running on Android 8 make it much more susceptible to rootkits and malware... bare that in mind. Android 9 is a more secure OS. 10 is sort of a pain and uses more resources.
*Android 8 and lower are suspectable to partition worming rootkits like Xhelper. If infected with that it can be purged without a reflash now, I believe. If present it would need to be addressed though...
blackhawk said:
The firmware shouldn't be corrupted. It rarely happens. If you flash go with a stock rom although with an unlocked bootloader you have more flexibility. Try to rule out a hardware issue first.
A factory reset wouldn't be the first option I would until I was confident it wasn't a hardware caused failure. Flashing be my last resort. I never had to flash any of my Androids in over a decade due to corruption. Usually it's the user partition that gets corrupted or more likely a 3rd party app screws it up. A factory reset would set back to its default settings*.
The bootloader being unlocked plus running on Android 8 make it much more susceptible to rootkits and malware... bare that in mind. Android 9 is a more secure OS. 10 is sort of a pain and uses more resources.
*Android 8 and lower are suspectable to partition worming rootkits like Xhelper. If infected with that it can be purged without a reflash now, I believe. If present it would need to be addressed though...
Click to expand...
Click to collapse
I saw lots of Pixel and few Sony, LG and Moto also had that issue. In terms of Sony, I did saw Xperia XZ2 did had that issues.
But my phone can turn on, it went to the lockscreen and less than second it shut off. I'm quite scared if its a hardware issue, it couldn't charge, but the battery connection looks okay to me. Does low quality BMS chip can cause some haywire to the motherboard?
My bootloader unlock status is no, because it's rare to found a Japan import set that can unlock its bootloader.
faizikari said:
I saw lots of Pixel and few Sony, LG and Moto also had that issue. In terms of Sony, I did saw Xperia XZ2 did had that issues.
But my phone can turn on, it went to the lockscreen and less than second it shut off. I'm quite scared if its a hardware issue, it couldn't charge, but the battery connection looks okay to me. Does low quality BMS chip can cause some haywire to the motherboard?
My bootloader unlock status is no, because it's rare to found a Japan import set that can unlock its bootloader.
Click to expand...
Click to collapse
Is the battery known to be good? What voltage is it showing? That's not a load test though.
I know it's new, but...
A new battery should have somewhere between a 30-70% charge on it when recieved. So if good it should have enough to boot it even if not charged. If not charging and especially if the power state is unknown flashing firmware is unwise.
If there's no indication of charging it could be anything from the outlet, brick, cable, port, connector(s), battery or mobo. The SOC is a BGA chipset and can be damaged by excessive board flexing as can other chipsets.
Can you get into the recovery menu?
blackhawk said:
Is the battery known to be good? What voltage is it showing? That's not a load test though.
I know it's new, but...
A new battery should have somewhere between a 30-70% charge on it when recieved. So if good it should have enough to boot it even if not charged. If not charging and especially if the power state is unknown flashing firmware is unwise.
If there's no indication of charging it could be anything from the outlet, brick, cable, port, connector(s), battery or mobo. The SOC is a BGA chipset and can be damaged by excessive board flexing as can other chipsets.
Can you get into the recovery menu?
Click to expand...
Click to collapse
I've read review of the seller of that battery, mostly positive, and I bought my past battery from the same seller and it didn't had any issues other than swollen after 1 year of usage. The battery arrived I think at 40%.
I've read on some thread that when Android phones got corrupted like mine, it can't be charge at its off state, unless if it's enter flashmode, then it can be charge. But I couldn't remember what thread that was, it might be XZ2 thread. On Pixel and OnePlus thread that I found also said the same thing.
Can I know how to enter recovery mode for Sony Xperia XZ? For the time being I unable to access to any Windows PC, so I can't try charging my phone via flashmode.
faizikari said:
I've read review of the seller of that battery, mostly positive, and I bought my past battery from the same seller and it didn't had any issues other than swollen after 1 year of usage. The battery arrived I think at 40%.
I've read on some thread that when Android phones got corrupted like mine, it can't be charge at its off state, unless if it's enter flashmode, then it can be charge. But I couldn't remember what thread that was, it might be XZ2 thread. On Pixel and OnePlus thread that I found also said the same thing.
Can I know how to enter recovery mode for Sony Xperia XZ? For the time being I unable to access to any Windows PC, so I can't try charging my phone via flashmode.
Click to expand...
Click to collapse
I don't know if that's true or not. Try some Goggle searches. It's a handful.
It shouldn't have gone corrupted unless there was physical damage as flash memory retains its data for many years without power.
ESD damage is also a possibility. If you can't bring up recovery it's essentially bricked... I think.
The battery seems isolated from the mobo. Check the C port pcb for damage. The display is in harm's way. I had a battery fail on my N10+, because of the case I didn't notice the bulging rear cover. I was very lucky the display wasn't damaged.
Maybe someone else here has a better plan.
blackhawk said:
I don't know if that's true or not. Try some Goggle searches. It's a handful.
It shouldn't have gone corrupted unless there was physical damage as flash memory retains its data for many years without power.
ESD damage is also a possibility. If you can't bring up recovery it's essentially bricked... I think.
The battery seems isolated from the mobo. Check the C port pcb for damage. The display is in harm's way. I had a battery fail on my N10+, because of the case I didn't notice the bulging rear cover. I was very lucky the display wasn't damaged.
Maybe someone else here has a better plan.
Click to expand...
Click to collapse
Oh, I'm sorry, I forgot to mention that my older sister phone, Sony Xperia X Performance, also use Snapdragon 820 and Android 8.0 Oreo also had that same issue as mine once when I swap a new battery, but it happened once and now that phone just run normally without any issues.
It's totally weird why I saw lots of Pixel device got the same issue as mine, and most of it said they never open their phone and never even disturb its bootloader or some sort.
I think the last resort is for me to use Sony PC Companion to repair my phone, or flash the whole firmware using Flashtool. If it still had that issue, it must be I messed up the board or something.
Thanks so much for your help, I really appreciate it a lot.
faizikari said:
Oh, I'm sorry, I forgot to mention that my older sister phone, Sony Xperia X Performance, also use Snapdragon 820 and Android 8.0 Oreo also had that same issue as mine once when I swap a new battery, but it happened once and now that phone just run normally without any issues.
It's totally weird why I saw lots of Pixel device got the same issue as mine, and most of it said they never open their phone and never even disturb its bootloader or some sort.
I think the last resort is for me to use Sony PC Companion to repair my phone, or flash the whole firmware using Flashtool. If it still had that issue, it must be I messed up the board or something.
Thanks so much for your help, I really appreciate it a lot.
Click to expand...
Click to collapse
You're welcome.
If it's a known issue than it maybe exactly that.
Sorry I couldn't be of more help to you.
blackhawk said:
You're welcome.
If it's a known issue than it maybe exactly that.
Sorry I couldn't be of more help to you.
Click to expand...
Click to collapse
Oh not at all, I'm totally glad that someone reply my post. I'd just found the thread that I mentioned, it's from Sony Xperia 1 II thread. This person had the similiar issue as mine. Hopefully it's a software issue consider their phone did successful to boots up.
1. Phone got corrupt.
2. Battery is low and can't charge when it's off.
3. Only charge if it's in flashmode.
Bootloop - Your Device is Corrupt
Yesterday I flash SEA firmwear to Xperia 1 ii via Flasher which result to constant boot loop with error message "Your device is corrupt. It can't be trusted and will not boot" I have attempted to repair the phone via Xperia Companion, however...
forum.xda-developers.com
Sometimes it takes a while to get replies especially with older phones.
Yeah I found this. Hope that gets it for you.
Try Google searches like: "Sony Xperia XZ, your device is corrupted and cannot be trusted"
Google searches are the easiest and probably the best way to search the XDA forum
The Google web crawlers never sleep... they don't find everything though even with precise key words. You may dig up some more useful information as it is out there by now.
Cross platforming works many times; it doesn't need to be that exact Sony model. Many issues are long standing and are found on to several models even years apart. Use whatever comes in handy...
Woah, thanks a bunch for posting link for that thread, I keep Googling it but never found that thread on Sony's forum yet.
I did found some Xperia XZ2 that had the same issue as mine. I totally curious what cause the software to be corrupt like that, bad apps maybe? I did uses a few cracked apps that I sideload the APK, maybe that one of the reason.
faizikari said:
Woah, thanks a bunch for posting link for that thread, I keep Googling it but never found that thread on Sony's forum yet.
I did found some Xperia XZ2 that had the same issue as mine. I totally curious what cause the software to be corrupt like that, bad apps maybe? I did uses a few cracked apps that I sideload the APK, maybe that one of the reason.
Click to expand...
Click to collapse
Bad apps can screw up the user partition data and sometimes cause a boot loop. They normally can't corrupt the system partition though... they shouldn't be able to.
There's the little monster xhelper. Android 8 and lower are vulnerable to it. Always scan any side loaded apps first with Virustotal. A seemingly good app could also latter download its payload.
If any doubt exists do not install it.