Develop Bugs

[SOLVED!!] Looping Bootloader or startup and unable to charge to reflash

I really don't know what's just happened...I think maybe my TP2 just decided to die on me.
I was using NRGZ Leo ROM from 22nd Feb. All was going well until my battery ran out today. At the time, my daughter was playing a game on it, not from WM, but from the Android port (Haret). While she was playing, I heard the familiar short vibrate of a soft reset. I know my battery was low and I suspect the battery wasn't charging, although it was plugged in (not sure if Android supports charging yet in the later builds)
Anyway, for some reason, it wouldn't go past the vibrate/Touch Pro2 screen. It just kept resetting and looping back. I attempted to do a hardware reset (power button, talk/send, end buttons) but accidently chose the wrong combo (power button, volume down) and entered bootloader. No problem yet, just reset and try again, right? Only I didn't get the chance, as it reset itself and looped through bootloader.
Now I am stuck in this loop. I can't flash from SD as it wont stay on long enough before self-resetting to find the RHODIMG.nbh on the card. I can't connect to my PC as it wont stay in bootloader long enough before self-resetting for my PC to install the "Windows Mobile Device" drivers, and even if it did, when it self-resets, it would disconnect anyway. I can't connect to MTTY for the same reason. I can't connect to ActiveSync or WMDC as I can't boot to WM to get ActiveSync running on the device.
When plugged in to AC power or through USB, it fires itself up automatically and into this loop, and it wont turn off manually, reset or accept any other button combos to enter RUU (from SD method) or to do hard reset. When it is not plugged in to any power source it won't even switch on.
I suspect it is resetting as it is not charging. I'm guessing that when in bootloader, charging is disabled, and I think this because I was originally getting 3 seconds of bootloader, now I am getting around 8 seconds, but it doesn't get any better than that, and I don't know of a rom upgrade method that can be done in 8 seconds! There are a few seconds of charging time before bootloader kicks in and the orange LED goes out and presumably stops charging. Am I right in thinking there is no charging in bootloader and in the Android port (I am using the latest version from 27/2, rhod100).
Basically, to summarise, I am stuck in bootloader-reset-bootloader loop, I cannot connect to pc in any way, flash from SD, Hard Reset, I have very little or no battery and it won't charge because it keeps going into bootloader where there is no charging taking place and it wont turn off to charge that way either.
Any help will be greatly appreciated. I don't hold out much hope though. At the moment, it doesn't seem that I am able to interact with it at all to make it do anything different or to manipulate what it is trying to do. Hopefully someone will see something familiar and maybe have some suggestions.
Oh, and by the way, it's nothing to do with a bad flash. I've been doing this for long enough to know what I'm doing, and I wasn't even doing a rom upgrade at the time. My last rom upgrade was 2 days ago and all went well, and I have been using it without problems since, until now. I haven't flashed my Radio or SPL since HSPL was released, so I know it has nothing to do with that either.
Thanks in advance for anyone who can give any advice at all, or even just take pitty on me! Apologies for all the text. I know it looks boring and may put some people off reading, but I needed to get all the info in.

Are you able to charge when it completely turned off?

can you pull the battery out, put it back in and simply charge for an hour or so to get some juice into the battery?
Then you could maybe reflash it from the bootloader or sd card...

shadixs said:
Are you able to charge when it completely turned off?
Click to expand...
Click to collapse
I can't get it to turn off, power button has no effect.
clauswl said:
can you pull the battery out, put it back in and simply charge for an hour or so to get some juice into the battery?
Then you could maybe reflash it from the bootloader or sd card...
Click to expand...
Click to collapse
If I take the battery out, obviously, it cuts the power and the looping stops...until I put the battery back in, and it starts itself again. I can't stop the loop and I can't turn the power off or even stop it switching itself on.

matmaneyre said:
I can't get it to turn off, power button has no effect.
If I take the battery out, obviously, it cuts the power and the looping stops...until I put the battery back in, and it starts itself again. I can't stop the loop and I can't turn the power off or even stop it switching itself on.
Click to expand...
Click to collapse
I had exactly that problem after a bad romflash. I bought a decktop cradle for the tp 2 that has 2nd. battery charger. Charged the battery and reflash, everything was ok again.
So, juice up the battery and do a hard reset or reflash..
SOMETHING LIKE THIS

I know you prob dont wanna hear it, but id say its a warranty job. Theyll just force flash it anyway so they wont notice the rom you were using.

Cheers guys. I thought it might be the rom. Not sure how though as like I said, my last rom flash was a couple of days ago and it was fine. Guess these things just happen sometimes. I'll try and get the battery charged somehow. Trouble is, I don't know another single person who has a TP2, so it looks like the cradle option I think. It did cross my mind to be honest when I was trying to think of alternative charging methods.
As for the warranty idea, if it can be avoided, I'd rather not take that route if I can help it, but thanks for the suggestion. Lets just say that will remain an option as my last resort if all else fails.
Still open to suggestions if anyone knows of any miracles....any Hogwarts graduates kicking about these forums with a few magic words to spare?

Hey man, I had the same issue when my phone wouldn't for some unknown reason charge.
1) Take our your battery
2) Plug in your DESKTOP CHARGER (not USB from PC!!) to microUSB slot
3) Put your battery back
4) Wait few moments (5 minutes)
5) and you are ready to boot, now you can even charge from USB. No idea why, but looks like booting takes more than 500mA :O
If it wont help, swap those 2 and 3 points

Hey guys! Please give this thread a better title. More related to the problem. Sounds like it could be useful in the future for hopefully very few people.

OK, I will change the thread title. I searched for quite a while but couldn't find any similar cases. But it seems it is more common than I thought since I raised the issue, so a new, more specific title might be more beneficial to other users experiencing similar problems.
For the record, I haven't solved it yet. Waiting on a standalone battery charger I bought from eBay. Didn't really want the cradle. THIS is the one I have bought. I will update on my progress when it arrives.
Thanks for your help to all who have contributed so far.

Hi I have the same problem the phone won't charge or connect via usb I think it is a faulty usb port the phone have & because of that it is causing the phone to go to bootloader.

I've had this happen before, just plug it into the mains charger (wall charger) and let it sit for a while. It will loop a couple times but once there is enough juice in the battery it will be back to normal.
Since you have RHODIMG.nbh on your sd card, maybe taking your sd card out would help it a bit.
There have been other posts with the same issue and plugging it into mains will solve the problem
spark001uk said:
I know you prob dont wanna hear it, but id say its a warranty job. Theyll just force flash it anyway so they wont notice the rom you were using.
Click to expand...
Click to collapse
Not true. just the battery is really low, once charged enough to power device after boot, everything will be back to normal.

fone_fanatic said:
Not true. just the battery is really low, once charged enough to power device after boot, everything will be back to normal.
Click to expand...
Click to collapse
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.

This might sound a little stupid, but I actually know somebody that said it worked for his iPhone (waste of 3-4 mins if not). Plug in the USB charger from PC. Reboot the PC without disconnecting the phone. Wait 3-4 minutes...

Toleraen said:
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
Click to expand...
Click to collapse
from what i remember, it won't boot without the battery.

fone_fanatic said:
I've had this happen before, just plug it into the mains charger (wall charger) and let it sit for a while. It will loop a couple times but once there is enough juice in the battery it will be back to normal.
Since you have RHODIMG.nbh on your sd card, maybe taking your sd card out would help it a bit.
There have been other posts with the same issue and plugging it into mains will solve the problem
Click to expand...
Click to collapse
I left it looping for hours....no joy I'm afraid. Just gonna have to wait for this charger to arrive I think
Toleraen said:
Seems like it would make sense. I don't have my wall charger on me now...does the Rhodium not boot up without a battery in it? I thought my old Hermes did, guess I've never tried it with the TP2.
Click to expand...
Click to collapse
fone_fanatic said:
from what i remember, it won't boot without the battery.
Click to expand...
Click to collapse
Definitely doesn't power up plugged in without a battery. Battery needs to be present. Still waiting on this charger though. I'm hoping it's not one of those where it says the item location is Cardiff (UK) when actually it's in Hong Kong and takes 14 years to arrive

soocerclaude said:
Hi I have the same problem the phone won't charge or connect via usb I think it is a faulty usb port the phone have & because of that it is causing the phone to go to bootloader.
Click to expand...
Click to collapse
I really don't think it's the mini usb port as it charges and tries to connect to pc before bootloader kicks in & it all stops.

Hi I found a way 2 get past the bootloader loop just plug your headphones went in bootloader and restarted the phone but it still won't charge or sync with computer.

soocerclaude said:
Hi I found a way 2 get past the bootloader loop just plug your headphones went in bootloader and restarted the phone but it still won't charge or sync with computer.
Click to expand...
Click to collapse
Well when I unplug the ac adapter, mine doesn't last on bootloader for more than a couple of seconds before dying. Doesn't even get to the RHODIMG.nbh update screen that way - not enough charge (I'm still hoping). Tried charging overnight while looping but still wouldn't charge enough. The trouble is that obviously the bootloader is killing the battery as it's not charging very much.
Got my charger finally....but they sent the wrong one. Waiting on a response from the seller. The "dock" on the charger wasn't big enough, so while the connectors were in the right place to charge the battery, the battery didn't sit flush, so they wouldn't reach the points on the battery itself. Hope they have a TP2 one & it's not just them thinking it's compatible, as it's the only one on the whole of ebay UK that has them in stock in the UK. Don't want to have to wait up to 2 weeks for one from HK.
I will keep you posted anyway.

Hi I brought mine 2 get fix because my warrenty got void due 2 water damage. I think it is the usb port that is causing this, saw in other forums the same thing. Will get back the phone on monday & I will update u on the situation.

usb dead. need to re-lock, this is a weird one!!

Sorry this is a long one. Phone is a Verizon Galaxy Nexus about five months old.
Using Galaxy Nexus Root Toolkit v.1.3 I managed to get the phone unlocked and (I think) install clockwork mod but when attempting to flash to root I got as far as "install from zip file . . .' but the next option "select zip file . . ." leads to a either an icon of a hat (which I presume is clockwork icon?) or a picture of an android with his belly open and an exclamation mark in a red triangle. I can no longer get to this point to confirm exactly which. Now when attempting to get to recovery mode I get into fastboot but after selecting "recovery mode" I always get the android with his belly open and a red exclamation mark and can never get to any menu.
Now all of a sudden possibly as a result of this process or else by coincidence usb on the phone appears to be either dead or sub-functional. This may also be why I could never flash to root, (bad USB led to corrupt or missing zip?). Windows does not detect any usb connection from phone, not even a failed one (no sound, no error message) but I have confirmed it's not the PC's error as other usb connections are working.
Also, confirming some sort of USB issue, the phone does not show the charging icon when I plug it into a charger UNLESS the phone is powered off, when I do see the charging animation. To make matters even more confusing despite not seeing the charging icon or the battery manager reporting that the battery is charging the phone does appear to be charging even while powered on but this was only after one night and I'm not quite 100 % certain it charged or that it charged at the usual speed. (thankfully I have an extra, separate, standalone battery charger).
I have re flashed to factory from the " backup and reset" menu inside Android and this did not help.
Simple question: any way to RELOCK phone without USB so I can at least make the phone appear un-tampered with so I can get a warranty service or replacement to fix the apparent usb problem?
bigger question: wtf is going on, is the usb issue perhaps a software problem? and is there anyway to fix the failed flashing process by perhaps transferring a zip file by some other means than usb to the proper directory?
Thanks for anyone who bothered to read this far.
Note: the actual sequence of events is a bit more complicated and now foggy in my memory but this I hope is close enough. If anyone wants more info I'll try to supply it. Let me just say that there were issues from the start of this process. merely unlocking the phone the first time had bricked my boot, all I saw was "Google" and a picture of an un-locked lock, getting into fastboot and then choosing recovery mode led to the picture of the belly up android but after several attempts I finally got past that one time and elected to flash back to stock from recovery menu. This was all before trying to root.

No to first question.
As for second question, pull the battery for about 10 minutes and see if it fixes your USB issue. Don't connect it to a computer to test the charging issue, and instead an outlet.

adrynalyne said:
No to first question.
As for second question, pull the battery for about 10 minutes and see if it fixes your USB issue. Don't connect it to a computer to test the charging issue, and instead an outlet.
Click to expand...
Click to collapse
Trying now, will report back. I think I already tried this though. I should also tell you I have three different batteries and behavior is same for all of them.

I'm not thinking its the battery but something stuck in hardware. Hence the leave it out for 10 minutes.

Left battery out phone unplugged for almost twenty minutes... and still no luck.

oops, I see I was supposed to put this in the Q and A section, sorry, new here, should I start over there?

Could be a hardware issue with your usb connector. Try cleaning it out with a blast of compressed air or something. I just found out today that the USB ports on the GNex are weak and prone to maybe needing repair.
Good news is that the part only costs $6.00 on ebay - if you're a DIYer.

zuberio said:
Could be a hardware issue with your usb connector. Try cleaning it out with a blast of compressed air or something. I just found out today that the USB ports on the GNex are weak and prone to maybe needing repair.
Good news is that the part only costs $6.00 on ebay - if you're a DIYer.
Click to expand...
Click to collapse
That was it! I blew it out, and then I cleaned a bit with alcohol, and then when that didn't do it I pushed up (or down) on the cable while it was plugged in and suddenly it came to life. I was able to connect to PC and lock it back. Now at least I can attempt a warranty repair if I so decide.
I had gently pushed up and down on the cable before to try to make a good connection but never once did it connect - I feel like the cleaning must have been needed but apparently was not sufficient to fix it fully.. So I suppose something is still amiss with the connector - either it is damaged or askew or else still a bit dirty.
I'm happy to be back to full stock, maybe I'll root again another day after I sort out the USB issue.
Thanks everyone!

In the future, I'd recommend steering clear of "one-click" or "toolkit" root methods. Sure, they work, and gosh darn it they are easy... but when something goes wrong, you'll never know what's actually the problem. Get comfortable working with fastboot and adb; it will take you a long way with this device.
This should help get you started in the right direction.

[Q] Bricked phone? Flashing red LED w/ no vibrations

Background: I was flashing a backup via TWRP, which failed because it could not write to memory. I rebooted the phone and it no longer responded.
Currently: the phone only has a blinking red LED whenever the USB cable is connected. I cannot connect into fastboot. The phone does not respond or do anything. No vibrations.
Is there any possible way to fix this? Or am I screwed?

Been there. No button combinations work nor vibrates at all. PC sees the device, but it is unrecognized. The LED flashes, but that's it. In the end it was power problems, battery and motherboard had lost communication with each other somehow. Thankfully the phone was under warranty and they swapped the mobo.

Koostis said:
Been there. No button combinations work nor vibrates at all. PC sees the device, but it is unrecognized. The LED flashes, but that's it. In the end it was power problems, battery and motherboard had lost communication with each other somehow. Thankfully the phone was under warranty and they swapped the mobo.
Click to expand...
Click to collapse
Thanks for the reply. You think they'll be able to find out (or be bothered to find out) that I unlocked the bootloader? Standard rooting = no warranty problems :\

I guess it depends on how much they want to find out. Although I believe it's pretty much impossible to find out anything if your mobo is dead unless they do some really complicated soldering, which I doubt they would.

Thanks for your help! We'll see how this goes once I get back from holidays. Also, what excuse did you give to justify the phone getting sent off?

Well my case was a little different: I bought the phone second-handed and the guy told me that nothing had ever been done to it (no rooting, no bootloader unlocking or whatsoever). However I found out that it had been and still was rooted, so I recycled it via Sony companion and charged it fully afterward. 5 minutes later it died. When I went to the service center, I didn't tell them much, nor did they ask much. "The phone went to sleep and never turned on again" had enough justification for them. Hope it's enough for you as well.

I had this issue when my phone got water damaged. I left it plugged in for a few hours and it would boot after, though the backlight was dead due to the aforementioned water damage. It might work for your phone.

Help! Blue screen, no download mode, can't factory reset.

Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew

rewkim said:
Hello!
A few months back I rooted my Verizon LG G3 without any issue. Worked great, went smoothly.
Last night I was watching Netflix when the phone suddenly shut off without warning. I haven't recently installed anything out of the ordinary. When I tried to reboot, I got the green screen with a HW reset warning. Pressing Vol down to reboot gave me a blue screen. I'm able to reboot using Power + Vol down, but if I try any of the options [including factory reset] it suddenly goes to the blue screen.
I also tried getting into download mode without any luck - you guessed it: Blue screen. If I connect the phone to a PC, it doesn't recognize it. I've tried downloading and running the LG PC Suite, but it can't connect to the phone.
Any thoughts on what's going on and how I might be able to repair it? I've looked through various threads here and anything similar seems to revolve around flashing gone awry...and I'm not flashing anything (nor do I really have the know-how to do so).
Thanks, in advance, for any assistance.
Andrew
Click to expand...
Click to collapse
Do you get the blue screen when attempting both recovery and download mode?

Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.

rewkim said:
Blue screen no matter what I do - recovery, download or normal mode. As a matter of fact, now the phone won't attempt to boot at all.
Really strange.
Click to expand...
Click to collapse
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?

Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
I appreciate your help - thank you. For what it's worth, no - there was never any text on my blue screen, and I couldn't ever get it to get into Download Mode. Plugging it in to a computer did nothing except give me a blue screen, and the computer never recognized it as a device.
I ended up getting a replacement G3, so [for now] my troubles are over. Thanks, again, for your help.
(I guess this thread can be closed now.)

Bastienhere said:
I feel you. I started a thread about my issue but sadly no one helped...
Seems like you got a "bricked" phone though Qualcomm phones are theoretically unbrickable.
I was in a worse situation than you, I think my board fried haha, but i'll try my best to help you here
Do you have a custom recovery?
IS there anything else showing on the blue screen? (example: Factory Reset Status)
also does your led flashes?
If you can't boot, or flash through download mode (KDZ and TOT method) I think either your bootloader got messed up (for no apparent reasons apparently) or it's simply a physical defect.
Are you sure your PC doesn't detect your phone's USB after installing the appropriate drivers?
Or does it detect the a device as "QDLoader 9008"?
Click to expand...
Click to collapse
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.

rewkim said:
Quick update: I just learned today that a co-worker who also has a G3 (T-Mobile) also got a blue screen last week. He was told that this was a "known issue" with this phone...but they wouldn't provide him with a replacement, which also seemed strange.
Click to expand...
Click to collapse
Glad you got it replaced!!
And a shame for your friend :/
In my case, it was practically hopeless, nothing seemed to work, eventually i had to have the motherboard replaced. It was clearly a damaged bootloader, yet, they repaired it under warranty! funny
I doubt you can damage a bootloader without root or stuff.

I wonder what would suddenly mess with the bootloader after months of no issues?

I'm having the same issue. Or rather I had the same issue but I was able to get it back to stock through all the various .tot methods and using download mode and everything. I had no issues so I rooted it again, installed the 35B firmware from xdabbeb, as well as his 46A so everything is still stock, and running the latest android update, but the phone is still rooted. In any case it has been working fine for almost a week. Today it shut itself off again and now only blue screen when I turn it on. It barely gets past the LG logo before it blue screens again. I can't enter download mode because while installing the device on the PC it blue screens and crashes in download mode.
So I'm not sure what the deal is. I have the extended insurance and warranty but if you pull the battery for a couple hours and put it back in it will boot past the LG screen and start the OS, but the boot loading screen shows "Android" instead of "Verizon" so they'll know it's a custom firmware and do nothing for me. If anyone has any ideas I'm open to them! I would love to revert back to stock but with it crashing in download mode I can't even do that.

try these things but g3 is crap phone
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.

can you explain what outfit in you are talking about? i am facing the same problem,
Simaramis said:
you can try these things: use stock charger and try to boot then, i think its a 2amp charger. if it boots then swapping out battery with good one will likely cure it. its hard to find good new oem batteries though. usually that only works if you see a blue screen with a number on it. if its just a flat blue screen and connected to stock charger wont improve anything then its likely corrupted bootloader (hard brick). i currently am trying to resurrect one that is acting the same, it will only randomly turn on to blue screen, sometimes after days left with battery in while turned off. all the tricks like taking battery out, connecting to charger or computer without battery or holding power button to drain capacitors with batt out dont seem to help really. i am trying to get it to turn on into download mode at which point i will flash stock kitkat but seems like it wont happen. seems like lollipop 5.0 has something to do with this issue. there is an outfit on ebay that fixes it for 29bucks in texas. you will find them on youtube. g3 is crap. g2 was excellent except for touch screen issues.
Click to expand...
Click to collapse
..

ARYA3 said:
..
Click to expand...
Click to collapse
Sorry "outfit on ebay" means seller on ebay. Don't remember what their name was. With the g3 it's like this: bootloop is usually fixable with a new battery. If it loads with charger connected, then definitely try new battery. If blue screen without a number, it's likely faulty motherboard. It may still boot occasionally, after leaving batt out or putting in freezer (yes freezer). If it does boot then do a backup immediately but phone is likely in need of new motherboard.

http://forum.xda-developers.com/showpost.php?p=70264535&postcount=9

BSOD is not so BSOD as you might think. This is actually the default view of the screen controller. It just means.... well... basicly... you're ****ed....
Something in the hardware doesn't fire up as it should and it's usually the SoC.... or the so called processor. Heating and baking might help if the problem is with low temperature welding but again it might not. And even if it does... it will be totally temporary (most cases weeks) because of the rapid increase/decrease of the processor temperature and thus welding joints... I'm basically in the same situation right now with the same phone... he fought well as it is 2014 phone after all but in the end it died heroically.... ;(

Z5P bricked after 3 vibrations reset... No chance for repair service nor warranty(UB)

Hello!
Well, I had the really bad luck of a very bad hard brick... my xperia was on low battery (around 15%) the last time that I use it, then around 20min later I got it and try to check, but screen didn't turn on, and the Led was blinking White color, since I deal in the past with this issues (around 3 or 4 times), I connect the usb cable to power adapter and simply did the reset button under sim flap, and my phone made the normal 3 vibrations, so, I hope that everything was fine, however, after that, I simply try turn on it, but never happen, No led of charge, no more vibrations and no power on, no signal of operation at all... so, I test remove and reconnect the usb cable and nothing, so, I try make another sim flap reset button test, but at this time and until now, no more 3 vibrations response and nothing else... and now, after reading some many posts, and try everything suggested in other posts about I really sad and hope for some help or feedback, if somebody may help...
By now I tested on my windows 7 notebook, and at first the phone was not recognized by drivers however it shows the bad message QHUSB_BULK error usb device, in later attempts, I made after some buttons tests looking for some response I got the phone change the messague, at the moment of connect it with usb cable to my pc, it was recognized as SEMC Flash Device... In both cases windows didnt allow or recognized for a proper driver installation....
But after other attempts, I lost the SEMC Flash Device status, and by now not remember what I did to get this mode or if it may be of some help...
By now I am really worry, since I got my phone from Hong Kong, and it came and worked fine until today, but in my country there is no service for this model since it not still on sale at official dealers/ carriers, and I believe that I don't have warranty service (since is an international purchase and not on local dealer) and also because I Unlock Bootloader for getting root and Sony records that information for warranty purposes (since I unlocked BL, I installed TWRP then I installed the romAUR custom rom and I upgraded it to 1.25 version with last kernel available from the same rom thread but thas was a month ago and phone worked fine after all custom rom installation)...
By now, I would like to ask if may be possible please, some guidance and help...
1) I was made attempts by the last 6 hours after brick without luck, and I wonder and suppose that the battery may be very low, but since I don't get any charging led, I wonder if by left It connected to the original sony charger with original sony cable (almost new and working both, and also tested both with other cell), my bricked phone may still get some charge on the battery.... somebody konws if possible to charge an xperia bricked?... I wonder/hope about that, if may be a charged battery may help in got the 3 vibes reset again that I hope may fix the issue and return my phone to boot...
2) Since seems that i don't have chance to get repair service on warranty since I unlocked my phone (and in my country the cost service for such model could easily be so high as almost a new phone), and also low chance for a warranty replacement from seller, I wonder about take the chance of open it and try to remove battery connector at a last resort since , I may suppose that this may allow for clear internal electrical charged registers of system and may allow me for a reset, but I wonder if the white flap sim buttons really did the same, that is simply open the battery connections, but, I doubt about that, since in this procedure the cel made 3 vibes and the energy for the vibes need to come form a connected battery...
3) May somebody with more luck, knowledge and experience, may suggest or share some help or advice about this issue...
I am a long time cell phone fan and long time in the issues of unlocking and installing custom roms, but until today, and after I survived many other phones bricks, my highest and loved phone of all my time, is bricked in a way that I am start to desperate, since I almost no clue by now about what could I try looking for a fix....
So, thanks in advance and if some body may help, I would be very grateful....

Is there really a reset button under the sim flap? Maybe you damaged the internals when trying this..

slayerz said:
Is there really a reset button under the sim flap? Maybe you damaged the internals when trying this..
Click to expand...
Click to collapse
Yes, I've used it many times it's highly unlikely to damage it from that. Unless you press it harder than a gentle touch.
Sent from my E6653 using Tapatalk

Yes, there it is, well, by now I am collecting more info and try about fully discharge my phone in order to get a RED permanent charging Led light (for future reference, seems that a Pulsing RED charging led means NO detection of battery...), by no today at morning I put my phone on charger and it only warn a little, and according with some info, the best chance by now is to plug it for a long time (other models of xperia reports around wait 24+ hours for get a RED permanent light...)
By now, I already purchased a set of adhesive gaskets, in preparation to open my phone (I did in the past and have some skills for doing it, but not that I really like to do over a so new and expensive phone... ), since by now, if I fail in got a RED permanent charging light, seems that the next step is to open back cover a remove battery connector, plug in usb cable connected to wall charger and then after 3 minutes wait, reconnect battery connector with the usb cable still attached, this would reset a really brick phone, and suppose tho reset the charging process of xperias...
By now, and in case of help other people that may need it now or in future, the guide that I am following advice is this:
[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick
http://forum.xda-developers.com/showthread.php?t=1849170
The info in the page seems with lots of sense, and the charging process description seems very similar at I would believe could be used in my previously Z2 and my now in comma, Z5P.... But by now, I need to get a RED light in order to try to unbrick without need to open back cover glass....
Any info, advice, comments or better, experience share, would be very gratefull...
Best regards...

Did you ever solve the problem? My Z5 died and wont turn on. Flashing lights when the usb is plugged in. Tried unplugging the battery and charging for hours

you have no fastboot ( vol+ blue led ) and no flashmode ( vol- green led )?

No, only a flashing red light when plugged in. The phone dos not react to any buttons.
Sony Xperia Companion does not recognize the phone.
"lsusb" in linux shows nothing when i plug the phone in.

xaser66 said:
Hello!
Well, I had the really bad luck of a very bad hard brick... my xperia was on low battery (around 15%) the last time that I use it, then around 20min later I got it and try to check, but screen didn't turn on, and the Led was blinking White color, since I deal in the past with this issues (around 3 or 4 times), I connect the usb cable to power adapter and simply did the reset button under sim flap, and my phone made the normal 3 vibrations, so, I hope that everything was fine, however, after that, I simply try turn on it, but never happen, No led of charge, no more vibrations and no power on, no signal of operation at all... so, I test remove and reconnect the usb cable and nothing, so, I try make another sim flap reset button test, but at this time and until now, no more 3 vibrations response and nothing else... and now, after reading some many posts, and try everything suggested in other posts about I really sad and hope for some help or feedback, if somebody may help...
By now I tested on my windows 7 notebook, and at first the phone was not recognized by drivers however it shows the bad message QHUSB_BULK error usb device, in later attempts, I made after some buttons tests looking for some response I got the phone change the messague, at the moment of connect it with usb cable to my pc, it was recognized as SEMC Flash Device... In both cases windows didnt allow or recognized for a proper driver installation....
But after other attempts, I lost the SEMC Flash Device status, and by now not remember what I did to get this mode or if it may be of some help...
By now I am really worry, since I got my phone from Hong Kong, and it came and worked fine until today, but in my country there is no service for this model since it not still on sale at official dealers/ carriers, and I believe that I don't have warranty service (since is an international purchase and not on local dealer) and also because I Unlock Bootloader for getting root and Sony records that information for warranty purposes (since I unlocked BL, I installed TWRP then I installed the romAUR custom rom and I upgraded it to 1.25 version with last kernel available from the same rom thread but thas was a month ago and phone worked fine after all custom rom installation)...
By now, I would like to ask if may be possible please, some guidance and help...
1) I was made attempts by the last 6 hours after brick without luck, and I wonder and suppose that the battery may be very low, but since I don't get any charging led, I wonder if by left It connected to the original sony charger with original sony cable (almost new and working both, and also tested both with other cell), my bricked phone may still get some charge on the battery.... somebody konws if possible to charge an xperia bricked?... I wonder/hope about that, if may be a charged battery may help in got the 3 vibes reset again that I hope may fix the issue and return my phone to boot...
2) Since seems that i don't have chance to get repair service on warranty since I unlocked my phone (and in my country the cost service for such model could easily be so high as almost a new phone), and also low chance for a warranty replacement from seller, I wonder about take the chance of open it and try to remove battery connector at a last resort since , I may suppose that this may allow for clear internal electrical charged registers of system and may allow me for a reset, but I wonder if the white flap sim buttons really did the same, that is simply open the battery connections, but, I doubt about that, since in this procedure the cel made 3 vibes and the energy for the vibes need to come form a connected battery...
3) May somebody with more luck, knowledge and experience, may suggest or share some help or advice about this issue...
I am a long time cell phone fan and long time in the issues of unlocking and installing custom roms, but until today, and after I survived many other phones bricks, my highest and loved phone of all my time, is bricked in a way that I am start to desperate, since I almost no clue by now about what could I try looking for a fix....
So, thanks in advance and if some body may help, I would be very grateful....
Click to expand...
Click to collapse
I know you probably have but did you try holding volume up and power to force reset it?
You say you couldn't get a proper installation of hardware, so the computer can see the device? Is it showing an exclamation point next to the device driver?
---------- Post added at 04:27 PM ---------- Previous post was at 04:15 PM ----------
I know you probably have but did you try holding volume up and power to force reset it?
You say you couldn't get a proper installation of hardware, so the computer can see the device? Is it showing an exclamation point next to the device driver?
Edit: Go to device manager and right click phone and do update drivers.
Click browse for update yourself and direct it to WINDOWS/INF folder and check "include subfolders".
Then click where it says "let me pick from a list of device drivers on my computer"
Then click Android phone from the list and click MTP USB driver and click OK for install.
Your phone should be installed correctly.
Then try fastboot etc.