Develop Bugs

[Q] note 2 dead please help

I just got this phone and was looking at my email when the screen just turned black. No restart or anything.. Hit the power button and nothing. Pulled the battery and nothing. I've notice a little red light next to the speaker flashes every few seconds. I've gotten it to turn on once. It shows the Samsung logo and dies again. I had pulled the battery and constantly hit the power.button after letting it sit for a while but it doesn't seem to do it now. Plug it into the charger still nothing. The battery had about 97% when this happened. Anyone know how to save my phone? I bought it through walmart wireless and my experience with this has bee less then satisfactory so far.

Thats quite unfortunate.Try booting into recovery mode. Hold Power+Vol Up+Centre buttons and see if you can load the recovery.
If you do, do a factory reset. That might save your phone. Good Luck. Let me know your outcome

pransh said:
Thats quite unfortunate.Try booting into recovery mode. Hold Power+Vol Up+Centre buttons and see if you can load the recovery.
If you do, do a factory reset. That might save your phone. Good Luck. Let me know your outcome
Click to expand...
Click to collapse
Thanks for the suggestion.. Tried and it did nothing.. I took a volt meter to the battery and voltage is tops.. The red light flashes every 10 seconds.. I wonder if its a diagnostic light..

Jerky_san said:
Thanks for the suggestion.. Tried nothing.. I took a volt meter to the battery and voltage is tops.. The red light flashes every 10 seconds.. I wonder if its a diagnostic light..
Click to expand...
Click to collapse
My best advice. Call in your warranty if you just got the phone before you make any tweaks that could affect it. You can get it handled directly with Samsung. Cause I don't think this happens a lot. If expired, then go experimenting

pransh said:
My best advice. Call in your warranty if you just got the phone before you make any tweaks that could affect it. You can get it handled directly with Samsung. Cause I don't think this happens a lot. If expired, then go experimenting
Click to expand...
Click to collapse
What sucks is I only had it for about 5 hours.. I did the root mod that doesn't change the counter or anything that was shown on here.. Only thing is my email is on it and it makes me nervous they won't properly wipe it..

Jerky_san said:
What sucks is I only had it for about 5 hours.. I did the root mod that doesn't change the counter or anything that was shown on here.. Only thing is my email is on it and it makes me nervous they won't properly wipe it..
Click to expand...
Click to collapse
I managed to replace my evo3d after the warranty expired (marginally though) and after rooting my phone with s-off. My display was screwed so they probably couldn't find out. Maybe I'm fortunate to live in this country or sometimes you just have to try your luck

Possibly bricked E4GT. Advice please.

Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.

Can you get into recovery or odin mode?

bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.

anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d

bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.

Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app

BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.

Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.

Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!

Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2

anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)

Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).

rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.

I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2

anindrew, how did it all turn out?

[Q] My Xperia S wont start, no led, no vibration, wont charge.

Hello everyone,
So my friend borrowed my phone to take a selfie and returned it shortly afterwards(im giving this info because i cant say if it shut down while my friend was using it or while it was in ny pocket). I just put it in my pocket and after about 20 minutes i wanted to see the time and it wouldnt turn on.
I tried pressing only the power button and nothing, i tried power + vol+ it didnt work, waited to get home to recharge, put it on my charger and no led no nothing.
I am just wondering what could be the problem and is there a way to fix it? Is it the battery? Im asking to see if it is worth to spend money to repair it as i bought a new phone.
Also the water damage indicator on the back is pink but i have never exposed it to water. (That has been pink for over a month before it died).

semirr said:
Hello everyone,
So my friend borrowed my phone to take a selfie and returned it shortly afterwards(im giving this info because i cant say if it shut down while my friend was using it or while it was in ny pocket). I just put it in my pocket and after about 20 minutes i wanted to see the time and it wouldnt turn on.
I tried pressing only the power button and nothing, i tried power + vol+ it didnt work, waited to get home to recharge, put it on my charger and no led no nothing.
I am just wondering what could be the problem and is there a way to fix it? Is it the battery? Im asking to see if it is worth to spend money to repair it as i bought a new phone.
Also the water damage indicator on the back is pink but i have never exposed it to water. (That has been pink for over a month before it died).
Click to expand...
Click to collapse
try to flash a stock rom via flashtool

maddboss said:
try to flash a stock rom via flashtool
Click to expand...
Click to collapse
Thanks for the reply I understand everything i have to do. Its just that this is my first time dealing with a hard brick and didnt know whether i could fix this myself or i should take it to repairs.
I have tried this method about a week ago and the led wouldnt glow and the phone wouldnt turn on. I have read now that i should charge it for 16+ hours and then try again.(first red LED then try)
Currently my laptop is in repairs, as soon as i get it back ill try the charging for 16+h method and the rubber band method.
I have root and unlocked bootloader so i dont have anything to worry about right?

I have been charging it for 44 hours and still no red LED. its still charging...

semirr said:
I have been charging it for 44 hours and still no red LED. its still charging...
Click to expand...
Click to collapse
We you able to fix it?

[FIXED] Multiple Blue Screen Glitches Led To Phone Bricking For No Reason

Before the phone turning brick, I was having these weird blue screen glitches that took almost half of the screen. It would stop after a few seconds, but this type of "glitch" happened a few times. 2 days later, I was on the home screen and the phone screen turned fully blue. It didn't go away so I took out the battery. After that the phone turned on with the boot logo but then shutdown itself. Now the phone won't turn on, charge, go to recovery, or go to download mode. Is there any way to fix this? (I don't have insurance on this :/)
(FIXED) It was "fixed" by leaving it charging, but now the blue screen showed up again. Now phone is probably damaged internally :/

ACViperPro said:
Before the phone turning brick, I was having these weird blue screen glitches that took almost half of the screen. It would stop after a few seconds, but this type of "glitch" happened a few times. 2 days later, I was on the home screen and the phone screen turned fully blue. It didn't go away so I took out the battery. After that the phone turned on with the boot logo but then shutdown itself. Now the phone won't turn on, charge, go to recovery, or go to download mode. Is there any way to fix this? (I don't have insurance on this :/)
Click to expand...
Click to collapse
I did flash a rom, but this was like 2 weeks ago. I wasn't having blue screen glitches until 3 days ago.

Thanks for the help guys..... 32 views but no one really? I literally got a blue screen for no reason when I was on the home screen. Any tip? I will even open the phone and try to fix it. Please any one??

ACViperPro said:
Thanks for the help guys..... 32 views but no one really? I literally got a blue screen for no reason when I was on the home screen. Any tip? I will even open the phone and try to fix it. Please any one??
Click to expand...
Click to collapse
My tip: http://forums.androidcentral.com/lg-g3/578393-why-my-lg-g3-boot-looping-blue-screen-3.html

ACViperPro said:
Thanks for the help guys..... 32 views but no one really? I literally got a blue screen for no reason when I was on the home screen. Any tip? I will even open the phone and try to fix it. Please any one??
Click to expand...
Click to collapse
There is no solution to blue screen glitches.it is caused by a current IC that draws more current and heats up within 3 5 seconds. I lost one mobile in this game. I feel sorry for you too, it is hardware issue and won't get any repair.

Jahanzaibawan said:
There is no solution to blue screen glitches.it is caused by a current IC that draws more current and heats up within 3 5 seconds. I lost one mobile in this game. I feel sorry for you too, it is hardware issue and won't get any repair.
Click to expand...
Click to collapse
What is "IC"? Also the phone turned on finally last night but when I connected it to a charger the same blue screen happened and now I can't turn it on again. Thanks for the information though

ACViperPro said:
What is "IC"? Also the phone turned on finally last night but when I connected it to a charger the same blue screen happened and now I can't turn it on again. Thanks for the information though
Click to expand...
Click to collapse
IC means integrated circuit. It's basically an electronic chip.

BSOD Fix
I had the same issue and was able to fix it temporarily for a few weeks but in the end I had to replace the motherboard from a donner phone. I had a lg d850 att and swapped out the mother board with a d851 from T-Mobile phone I found that had a broken screen and it worked fine after some tweaking. As far as your temporary fix (maybe permanent in your case idk) I took out my motherboard and put it in the oven at 385 degrees and baked it for 10 minutes let it cool off and reinstalled it. Phone came right up and worked like normal. Use some aluminum foil balls to put the motherboard on to keep it off of the surface in your oven that you put the motherboard on. That's it!

gixxergabi said:
My tip: http://forums.androidcentral.com/lg-g3/578393-why-my-lg-g3-boot-looping-blue-screen-3.html
Click to expand...
Click to collapse
This method really works, I already did it on mine. Slight problem after two weeks my Bluetooth and wifi stopped working, so i dont have that anymore..

BoriaTV said:
This method really works, I already did it on mine. Slight problem after two weeks my Bluetooth and wifi stopped working, so i dont have that anymore..
Click to expand...
Click to collapse
Didn't work for me :/ Thanks anyways

Fixed the wifi / bluetooth issue it was from something bugged in the software!

z5 premium sudden death

About a week ago, with my battery at 39% i plugged my z5 premium in to charge and it never came back on again.
I have tried all the usual tricks, pwr and vol up, removing the battery, the sim slot button, and pretty much any combination of buttons and still nothing.
It will charge just fine, but will only reach the white sony xperia screen and no further. it will flash up the white screen then go black with the notification light flahing red 3 times and then staying red. once or twice it has started to load the 'powered by android' screen and then just blackness. If i hold vol down and plug into laptop the notification light will turn blue and it shows up as 'adb android device'. Thats the extent of the life left in it.
So what would people suggest as my next step? is it still possible to recover the data thats on the phone or is it a total loss?

I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD

Pixelado said:
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Click to expand...
Click to collapse
hello,
im having the same issue, but how it would be flashed and the computer didn't detect it?
what's the trick in that? thank you

Nidhal AKA the king said:
hello,
im having the same issue, but how it would be flashed and the computer didn't detect it?
what's the trick in that? thank you
Click to expand...
Click to collapse
If your computer cant detect the phone, it could be one of the following:
- Bad usb cable
- Bad usb charging port on the phone
- Dead battery
- Dead motherboard
If your computer doesn't make any sound when plugging the phone in, then missing drivers shouldn't be the problem and you should troubleshoot each of the possibilities I mentioned.

Pixelado said:
If your computer cant detect the phone, it could be one of the following:
- Bad usb cable
- Bad usb charging port on the phone
- Dead battery
- Dead motherboard
If your computer doesn't make any sound when plugging the phone in, then missing drivers shouldn't be the problem and you should troubleshoot each of the possibilities I mentioned.
Click to expand...
Click to collapse
Thanks for the tips.. I will check again and i hope it will be detected.
Sent from my Sony H8416 using XDA Labs

2-minute reset.
I thought mine was bricked after only 2 months. I came across this fix on the Sony website and it fixed mine where it could work again. I had to factory reset it. It was just locking up and freezing. Be sure to hold that button in for 2 solid minutes. I watched the clock. Longest 2 minutes of my life.
https://support.sonymobile.com/glob...em-&-performance/i-cannot-power-on-my-device/
Pixelado said:
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Click to expand...
Click to collapse

I am just adding a list of similar threads that have been recently posted regarding this strange sudden death issue, battery not charging, weird non-software bootloop.
Sudden Death
InfiniteBootLoop
Unable to Turn On
My Phone Just died (april2019)
Not charging (user is rooted though)
I think i will also collate many of the similar threads into titles and post it as a new thread. As this forum is extremely bloated and repetitive whilst simultaneously being confusing for some users.
I guess Z5P is old now, but trust me the XZ3 is complete garbage so support for Z5P should be much cleaner and better organised now.

Any news for this?