Database Info

3 Pulses and a Flashing Orange Light.

My Inspire seems to have gone wonky. I was using it, picked it back up, and it was off. When I turned it back on, the vibration motor pulsed three times quickly, and the orange light started blinking. The light won't stop blinking until you turn the battery off. It seems after letting it sit for an extended period of time, it will turn on and work normally. AT&T is sending me a refurbished unit, and I need to send this one back. This one is rooted, and has a custom rom and clockworkmod installed. I was able to get s-on, but couldn't get into the bootloader. I'd like to either a) completely brick it so ATT can't see that it's rooted when they get it, or b) return to stock. I was able to get s-on, but need to flash it or as previously mentioned, brick it. Any suggestions? Thanks!

Did you try running the RUU?
Do a search for:
Code:
RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed.exe
run it and it should return you to stock.

Gene Poole said:
Did you try running the RUU?
Do a search for:
Code:
RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed.exe
run it and it should return you to stock.
Click to expand...
Click to collapse
Thanks for the tip. I have tried to run it, but soon as I get it to boot, it re-bricks on reboot, preventing RUU from rebooting into the bootloader. I'm trying to get into the bootloader again, but I might have to wait a few hours before I can get it to boot again.

ColonelPan1c said:
Thanks for the tip. I have tried to run it, but soon as I get it to boot, it re-bricks on reboot, preventing RUU from rebooting into the bootloader. I'm trying to get into the bootloader again, but I might have to wait a few hours before I can get it to boot again.
Click to expand...
Click to collapse
Another thing to try is to flash the signed RUU's rom.zip directly. The RUU exe contains a signed rom.zip which can be written to the SDCard as PD98IMG.zip and installed that way. An HTC signed PD98IMG.zip will install even with S-ON.
To extract the rom.zip from the RUU, run the RUU to the point where it asks you to "agree". Then search for rom.zip on your harddrive. It will be extracted into a randomly named folder in your temp directory, but the temp directory is different on different versions of windows so searching is the best way to find it.

I'll try, but what I'm ultimately going to do probably is just splice a spare 12v or 19v AC adapter I have laying around to a micro USB cable, and send a nice voltage spike through the phone. Should brick it nicely and still have it covered under warranty.

Oddly enough, 19v over USB didn't do anything to the phone, with or without the battery. I got it to boot, into the os, but the bootloader seems to be borked. Can't get into it on boot, just back to that flashing red/orange light. I found another thread of people with a similar issue, and it looks like HTC is replacing even rooted phones without any question. Hopefully ATT is nice about my replacement.

ColonelPan1c said:
Oddly enough, 19v over USB didn't do anything to the phone, with or without the battery. I got it to boot, into the os, but the bootloader seems to be borked. Can't get into it on boot, just back to that flashing red/orange light. I found another thread of people with a similar issue, and it looks like HTC is replacing even rooted phones without any question. Hopefully ATT is nice about my replacement.
Click to expand...
Click to collapse
Care to post the thread?

ColonelPan1c said:
I'll try, but what I'm ultimately going to do probably is just splice a spare 12v or 19v AC adapter I have laying around to a micro USB cable, and send a nice voltage spike through the phone. Should brick it nicely and still have it covered under warranty.
Click to expand...
Click to collapse
I certainly don't recommend this approach. Instead of HTC having to do a relatively inexpensive firmware reflash (essentially free to them) they have to replace a mainboard to refurb the device. This raises costs for all of us.
Can you actually get to an hboot screen? Have your tried "adb reboot bootloader" or "adb reboot oem-42" while the phone is booted? If you leave it off for awhile as you mentioned, can you boot it to hboot with the VOL-UP POW combination? If so, you got a route for recovery.
If you feel you must brick the device, try to do it in the firmware only by zeroing out an essential partition. Use a terminal emulator or "adb shell" and do:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p17

Here is the thread I've found:
http://forum.xda-developers.com/showthread.php?t=1121767
I was able to get RUU to flash back to stock this morning. It rebooted consistently a few times, then right back to the orange flashing light. I'm comfortable sending it back now at least.
Thanks for your help everybody.

My phone vibrated 3 times and started flashing orange when it suffered water damage. Not saying that this is your problem, but I do know that these indicators indicate damage of some sort. Be careful about returning it for warranty because if they come to the conclusion that its damage caused by the user, they will charge you full price of the phone. Food for thought.
Sent from my Inspire 4G using XDA App

[Q] Sensation 4g starts on a black screen, help

I own a htc sensation 4G. The phone was S-off and was rooted. I am new to android but i did follow every procedure perfectly till the following happened.
I downloaded the ota update. Whilst updating it, the update was successful but now my phone just shows a blank display. The phones on, i can receive calls too but its a blank black display with no touch capable.
I tried to run recovery (PG58IMG), it was successful, but when rebooting same problem.
From boot(vol down + power), if i go into recovery, nothing happens, phone simply boots up
Same is the result with factory reset. No matter what i try to do, the phone accepts the command and boots up leaving me with an on phone and no screen.
Next i tried RUU , RUU_Pyramid_TMOUS_1.45.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_208218_signed and the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714_signed VERSIONS.
It runs but, when it comes to the point where it says, waiting for fastboot, There is a htc screen(white and black text) and the phone just wont go into fastboot. ten odd mins later i get a msg saying error 177, usb not found on my cpu and the only option on screen is exit. When i pull out the usb from the phone, for abt 5 seconds it shows the fast boot screen with RUU written below the basic information and it goes back to the htc screen. Only way to cancel is to pull out the battery...
Now everything that i could find on the forum and net, i have tried.. Please tell me if there is another option or am i doing something wrong???
My big problem at the moment is that im not in the states, am in India and cant take the phone to a service centre... PLS HELP

Any inputs guys?? really stuck here

Have u tried the tmous 1.50.ruu?

mugetsu666 said:
Have u tried the tmous 1.50.ruu?
Click to expand...
Click to collapse
RUU in general has a problem, the program keeps waiting for fastboot whilst i only have a screen with an htc logo on it. Only after waiting for a couple of hrs and disconnecting the usb cable, i get a fastboot screen with ruu written for abt 5 secs and it automatically goes back to the HTC screen..
I have tried 2 different ruu's and same end result.. so so..

Have u tried talking to a tech at HTC?

mugetsu666 said:
Have u tried talking to a tech at HTC?
Click to expand...
Click to collapse
i did today, they told me that everything possible that he would advice me to do, you have already done so. There is nothing left to be done. Get it over at a service centre to check for hardware defects or a possible re-programing of the phone.
The thing is, In india, htc sells like hot cakes, but their back-end service is horrendous. Service centers are not htc's but third party and they charge crazy sums for a customer doesn't have a 2nd option.
Hence am considering and trying all other options before going to a htc service center.
Is there anything that i have missed out in trying from my end???

Not that I know of, it sounds like the ota bricked ur phone and I'm not that good at that part. My knowledge only goes so far, sorry man.

Have you tried getting the PC to recognise the phone in fastboot?
If you have working fastboot then you can normally recover it.
Pull battery, reinsert, volume down & power then connect to PC.
Open cmd prompt as admin, cd to your fastboot folder, then enter "fastboot devices" and post the result.
Instructions on fastboot/adb if you are unfamiliar in the sticky guide to everything in dev forum.
Sent from my HTC Pyramid using xda premium

#mugetsu666 , i doubt the phones bricked, whilst everything is not working, aka fastboot, recovery, factory restore etc, the phone does boot and is on. How do i know this?? well, when i dial my no, the phone does ring but the screen is dead, as in black.. the 4 tabs below too r lit up but just no response..
#stringer7 , i did all of that already but whilst u asked me to post results, something just struck me.. when the phones put on usb, it charges and i can take it to fastboot too, but, on the task bar far right in devices, the pc is trying to search drivers for usb. Thats always on, even after leaving the phone on load overnight.. The pc is always searching for drivers and when i unplug usb, the no drivers found error does pop up..
"device driver software not successfully installed", is the windows error
Is the above info of any help?? considering the fact that i can take the phone on fastboot usb, but on the pc screen comes the error that usb not found or waiting for fastboot...
help

----------

Can you get a message from "fastboot devices" as above? If so you should be able to run the correct ruu to recover.
Sent from my HTC Pyramid using xda premium

The thing is, that the comps not reading the phone as a android device.
It charges the phone but doesn't read it. Hence cant do anything..
Any RUU doesnt move beyond the usb detection point leaving me with an "ERROR 170", cannot read usb..
Did the ota do this or does this look like an hardware error?
The 1.45 ruu of t-mobile seems like the most common one, but i cant even put that 1 to the test cause it just doesnt go beyond detection

Is there a chance that my problem could have cause a motherboard or other hardware problem???

[Q] my htc sensation will not boot

I have a Htc Sensation running on the Tmobile network
i decided to go with a different rom and tried to install the rom from COREDROID SENSATION XE & 4G v5.1.
after installing it was stock on the boot screen.
I tried to SCID and install PG58DOAG.
at this point my phone will not boot.
I can get into the the recovery mode after i select "recovery" it goes to a screen with a red triangle and an exclamation mark.
I the volume up and power and the try to install a update...but non has worked
can get one help??

download this file http://www.filefactory.com/file/c19...00U_10.14.9035.01_M_release_223976_signed.exe
and run it with your phone plugged in your pc, it should do a stock recovery on your phone.

I faced the same issue with another ROM.
The only way I found to reboot was to reinstall the firmware while connected via USB with the PC.
And after that, I reinstalled the ROM.

I couldnt even boot.

primekrieger said:
I couldnt even boot.
Click to expand...
Click to collapse
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?

Skipjacks said:
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Click to expand...
Click to collapse
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks

primekrieger said:
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
Click to expand...
Click to collapse
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.

primekrieger said:
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
Click to expand...
Click to collapse
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:

primekrieger said:
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
Click to expand...
Click to collapse
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.

primekrieger said:
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
Click to expand...
Click to collapse
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid

rzr86 said:
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
Click to expand...
Click to collapse
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.

walkermoon said:
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
Click to expand...
Click to collapse
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)

rzr86 said:
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.

walkermoon said:
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
Click to expand...
Click to collapse
hmm,
probably you need to use the temproot remove.bat file to remove temproot
check for troubleshooting in this thread
http://forum.xda-developers.com/showthread.php?t=1661631
also refer you issue there
ganeshp will help you further
or you can install 4ext recovery
enable smartflash from it and flash a custom rom

[Q] Hard-Brick?

Got an Infuse, that when I hold power button, nothing happens at all, no samsung logo even. Pluging it into computer does nothing, not even driver install. No download mode, no recovery. Bought a usb jig on amazon, that also did nothing. Have tried every usb port on my computer (have 6; 4 back, 2 top ports). Removed battery for 10 minutes put back in, nothing. Anybody got any ideas? Is it dead?

blscallions said:
Got an Infuse, that when I hold power button, nothing happens at all, no samsung logo even. Pluging it into computer does nothing, not even driver install. No download mode, no recovery. Bought a usb jig on amazon, that also did nothing. Have tried every usb port on my computer (have 6; 4 back, 2 top ports). Removed battery for 10 minutes put back in, nothing. Anybody got any ideas? Is it dead?
Click to expand...
Click to collapse
Yours or did you bought it used?
any history? different fully charged battery?

qkster said:
Yours or did you bought it used?
any history? different fully charged battery?
Click to expand...
Click to collapse
Mine, only owner,
Was working on a new recovery for jb and goofed somewhere. I think I may have damaged the bootloader trying something crazy, I think an installer I was working on damaged the boot image. Tried to install a recovery (cwm zip) I was working on and upon reboot the phone would not show anything, not even samsung logo. Tried different battery too. Still did nothing. I've seen that JTAG could probably save it, but I am unfamiliar with that process and don't want to risk more damage.

blscallions said:
Mine, only owner,
Was working on a new recovery for jb and goofed somewhere. I think I may have damaged the bootloader trying something crazy, I think an installer I was working on damaged the boot image. Tried to install a recovery (cwm zip) I was working on and upon reboot the phone would not show anything, not even samsung logo. Tried different battery too. Still did nothing. I've seen that JTAG could probably save it, but I am unfamiliar with that process and don't want to risk more damage.
Click to expand...
Click to collapse
Sounds like you're not getting any power to the circuits at all.
If it's not a battery issue, you might be right about the boot loaders. It may be hard bricked.
I recalled Adam Outler made a lot of break through on unbricking devices. I think this may be the thread:
http://forum.xda-developers.com/showthread.php?t=1153310
but I would check out all his threads:
http://forum.xda-developers.com/search.php?searchid=83200448
and locate the one you think may apply to you.
JTAG may also be your last hope if nothing else works..I think "mobiletech" something has been recommended by other users

[HELP] Bricked Z3 [D6603]

Hi all,
Thanks for your help in advance.
I think I've bricked my phone, however I'm not sure whether it's recoverable or not.
What I did, was flash my phone back to it's original ROM and rooted using the guide in a sticky on this board 'D66XX 5.0.2/5.1.1 Flashable stock Lollipop pre-rooted collection & XZ dualrecovery'
This was fine, and it booted fine, I installed root checker and confirmed that it was rooted.
I then downloaded the Official Cyanogen 12.1 Nightly build from their website, cleared cache/dalvik etc.. and attempted to flash that using TWRP. I had an error, which was something along the lines of "E:Error executing" and this was followed by "This device is leo".
I googled a little bit and found that I had to modify the 'updater-script' file in the nightly .zip in order to flash, so I did this and it seemed to install fine with no errors..
I then rebooted, and since then I've had no response from my phone. No LEDs on charging (after an hour or so). No response from holding any combination of Power/Volume buttons, and even the hard reset button located inside the SDCard cover doesn't cause any vibrations from the handset.
I'm not sure where else to go.. After a lot of searching a lot of people are suggesting to leave it charging and then try again after a long charge. I'm wondering what other people would suggest in my situation, is my handset recoverable?
Any help is greatly appreciated! Cheers
Sam

Hi, if your phone's bootloader isn't unlocked this is most likely why it's not booting up. I once installed a ROM on my phone and skipped the line where it said the bootloader needed to be unlocked(I realised this after reading through the install instructions again), I then used the flash tool to install a stock ROM and the phone was fine again, after that I unlocked the bootloader reinstalled that custom ROM that needed an unlocked bootloader and it worked. If you don't know how to do any of this an are just too lazy to find the links that guide you through this I'll find it for you and post it here(you will wait a while though). Hope this helps

GenericBridge said:
Hi, if your phone's bootloader isn't unlocked this is most likely why it's not booting up. I once installed a ROM on my phone and skipped the line where it said the bootloader needed to be unlocked(I realised this after reading through the install instructions again), I then used the flash tool to install a stock ROM and the phone was fine again, after that I unlocked the bootloader reinstalled that custom ROM that needed an unlocked bootloader and it worked. If you don't know how to do any of this an are just too lazy to find the links that guide you through this I'll find it for you and post it here(you will wait a while though). Hope this helps
Click to expand...
Click to collapse
Right.. so first of all, you're correct.. my bootloader is still Locked, as I did not unlock it.
The rest you are totally wrong about, I am unable to get any response from the phone whatsoever.. There's no bootloop, there's no response from screen, no LEDs, no vibrations, nothing. The PC (including Flashtool) doesn't recognize the phone. So flashing is kind of impossible in it's current state.
I've left it overnight (since my post) connected to a wall charger and still nothing so far. Going to leave it charging just in case it wants to resurrect itself at some point (fingers crossed).

Strickened said:
Right.. so first of all, you're correct.. my bootloader is still Locked, as I did not unlock it.
The rest you are totally wrong about, I am unable to get any response from the phone whatsoever.. There's no bootloop, there's no response from screen, no LEDs, no vibrations, nothing. The PC (including Flashtool) doesn't recognize the phone. So flashing is kind of impossible in it's current state.
I've left it overnight (since my post) connected to a wall charger and still nothing so far. Going to leave it charging just in case it wants to resurrect itself at some point (fingers crossed).
Click to expand...
Click to collapse
Does your phone get warm at all while it's in this state? Also does it not get picked up at all by your computer or does it just come up as an unrecognized device? I'm going to assume your phone might be on, in which case I'd recommend holding in the Vol+ button and then the off button, this will force the phone to shutdown if it's on, if your phone vibrates three times then it's definitely off now and you should try seeing if you can go into fastboot or flashmode mode using a computer if that doesn't work then I'm sorry but I think your phone might just be too far gone.

GenericBridge said:
Does your phone get warm at all while it's in this state? Also does it not get picked up at all by your computer or does it just come up as an unrecognized device? I'm going to assume your phone might be on, in which case I'd recommend holding in the Vol+ button and then the off button, this will force the phone to shutdown if it's on, if your phone vibrates three times then it's definitely off now and you should try seeing if you can go into fastboot or flashmode mode using a computer if that doesn't work then I'm sorry but I think your phone might just be too far gone.
Click to expand...
Click to collapse
It did come up as "Unknown Device (Device Descriptor Request Failed)", but no longer does, I'm assuming that it WAS on, but now the battery has run out and it's not charging.
I did try an "adb devices" command when it was plugged in previously but it did not list my device, and as far as I know I have all the correct drivers installed, as I used flashtool to flash CM 12.1.
I can no response from volume/power buttons with any combination as per OP.
*EDIT* The device does not raise in temperature either was connected to USB/Wall Charger

OK So I have an update..
I've removed the back of my phone, removed battery connector and replaced, and now when I connect to my Laptop using USB, The device is recognised as "SEMC Flash Device", however when holding the Volume Down button when connecting I do not have a Green LED, it shows a Red LED for roughly 2-3 seconds and then that dissappears.
Flashtool kind of "half recognises" my phone as per the following:
31/050/2015 14:50:55 - INFO - Device connected with USB debugging off
31/050/2015 14:50:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
and it also shows:
31/052/2015 14:52:19 - INFO - List of connected devices (Device Id) :
31/052/2015 14:52:19 - INFO - - HID\VID_0FCE&PID_D1AC\6&8FB5D7D&0&0000 Driver installed : true
31/052/2015 14:52:19 - INFO - - USB\VID_0FCE&PID_D1AC\5&88A806&0&1 Driver installed : true
31/052/2015 14:52:19 - INFO - List of ADB devices :
31/052/2015 14:52:19 - INFO - - none
31/052/2015 14:52:19 - INFO - List of fastboot devices :
31/052/2015 14:52:19 - INFO - - none
ADB doesn't recognise and neither does Sony PC Companion, but surely this is progress in the right way? If it's now being recognised as an SEMC Device

Strickened said:
OK So I have an update..
I've removed the back of my phone, removed battery connector and replaced, and now when I connect to my Laptop using USB, The device is recognised as "SEMC Flash Device", however when holding the Volume Down button when connecting I do not have a Green LED, it shows a Red LED for roughly 2-3 seconds and then that dissappears.
Flashtool kind of "half recognises" my phone as per the following:
31/050/2015 14:50:55 - INFO - Device connected with USB debugging off
31/050/2015 14:50:55 - INFO - For 2011 devices line, be sure you are not in MTP mode
and it also shows:
31/052/2015 14:52:19 - INFO - List of connected devices (Device Id) :
31/052/2015 14:52:19 - INFO - - HID\VID_0FCE&PID_D1AC\6&8FB5D7D&0&0000 Driver installed : true
31/052/2015 14:52:19 - INFO - - USB\VID_0FCE&PID_D1AC\5&88A806&0&1 Driver installed : true
31/052/2015 14:52:19 - INFO - List of ADB devices :
31/052/2015 14:52:19 - INFO - - none
31/052/2015 14:52:19 - INFO - List of fastboot devices :
31/052/2015 14:52:19 - INFO - - none
ADB doesn't recognise and neither does Sony PC Companion, but surely this is progress in the right way? If it's now being recognised as an SEMC Device
Click to expand...
Click to collapse
Do as follows:
1. make sure your phone is off ( hold down volume+ and than press the power button, hold them down like that until the phone vibrates 3 times)
2. run flashtool as an administrator (right mouse click on the flashtool icon > Run as an administrator) ,once flashtool opens click on the lightning icon, select "OK" to chose the flashmode, and than select your stock z3 ftf file at the top ( if you have one, if not then download xperi firm and use it to download stock z3 rom )
3. after selecting the stock rom make sure APPS_LOG and USERDATA (on the upper right side) are ticked. Than go ahead and select flash (bottom right corner)
4. wait for flashtool to do its thing, eventually it will prompt you to plug in your phone
5. once that happens go ahead and hold down the volume down button, and while still holding it plug your phone to an usb cable, ( which is already connected to your pc )
6. after that flashtool will start flashing the rom
7. dont touch anything until the phone boots itself up

Brontok said:
Do as follows:
1. make sure your phone is off ( hold down volume+ and than press the power button, hold them down like that until the phone vibrates 3 times)
2. run flashtool as an administrator (right mouse click on the flashtool icon > Run as an administrator) ,once flashtool opens click on the lightning icon, select "OK" to chose the flashmode, and than select your stock z3 ftf file at the top ( if you have one, if not then download xperi firm and use it to download stock z3 rom )
3. after selecting the stock rom make sure APPS_LOG and USERDATA (on the upper right side) are ticked. Than go ahead and select flash (bottom right corner)
4. wait for flashtool to do its thing, eventually it will prompt you to plug in your phone
5. once that happens go ahead and hold down the volume down button, and while still holding it plug your phone to an usb cable, ( which is already connected to your pc )
6. after that flashtool will start flashing the rom
7. dont touch anything until the phone boots itself up
Click to expand...
Click to collapse
The phone won't boot into Flashmode, or fastboot mode, or recovery mode.. Nothing, no Sony logos, no response, no vibrations.

Strickened said:
The phone won't boot into Flashmode, or fastboot mode, or recovery mode.. Nothing, no Sony logos, no response, no vibrations.
Click to expand...
Click to collapse
Make sure the phones is turned off, then open flash tool, connect the cable to your phone while holding the volume down button, see if flashtool will say "device connected in flashmode".. if it does than you can proceed with the previous instructions, from top to down.

The problem you now have I think is you have a custom kernel installed on a locked bootloader device, with a now completely dead battery.
I don't know if it will charge in this state as I think the kernel controls charging, and as your kernel won't function with a locked bootloader, it's not going to charge either. If it's not going to charge at all, it's not going to have enough power to get into flash mode to flash a stock ftf.
The red led means there's not enough power . . . I'm wondering if you could get hold of another battery with some charge in it, if it would then allow flash mode?
I think your phone was frozen when you were trying initially, and it just stayed that way until it went dead.
I'm no expert, but I'd be willing to try if it was me, seeing as you've already dismantled it anyway.
Somebody correct me if I'm wrong, I hope there's an easier way than this.

MickieH said:
The problem you now have I think is you have a custom kernel installed on a locked bootloader device, with a now completely dead battery.
I don't know if it will charge in this state as I think the kernel controls charging, and as your kernel won't function with a locked bootloader, it's not going to charge either. If it's not going to charge at all, it's not going to have enough power to get into flash mode to flash a stock ftf.
The red led means there's not enough power . . . I'm wondering if you could get hold of another battery with some charge in it, if it would then allow flash mode?
I think your phone was frozen when you were trying initially, and it just stayed that way until it went dead.
I'm no expert, but I'd be willing to try if it was me, seeing as you've already dismantled it anyway.
Somebody correct me if I'm wrong, I hope there's an easier way than this.
Click to expand...
Click to collapse
Thank you for your suggestions, unfortunately I'm unable to get a battery with charge, and have therefore give up.. I will accept that I have bricked my phone beyond recovery, and will learn from my mistakes.

Strickened said:
Thank you for your suggestions, unfortunately I'm unable to get a battery with charge, and have therefore give up.. I will accept that I have bricked my phone beyond recovery, and will learn from my mistakes.
Click to expand...
Click to collapse
Seems a shame to give up. There's nothing wrong with the hardware by all accounts.
You can get a new battery off ebay for £10 to £15 and they're factory charged to at least 50%.
http://pages.ebay.com/link/?nav=item.view&id=291420999095&alt=web
It may or may not work, but I'd rather try than bin a couple of hundred pounds worth of phone.
Whatever you decide, I'll help if I can. I love my Z3, even more so than my Z5 right now.
Good luck either way,
Mick
Edit:
I'd even go so far as to say, if you still have the complete phone, post it to me and I'll see what I can do with it. I'll post it you back when I'm done, and if I can fix it, it's only gonna be a new battery at the most. You can't really lose, it's not working as it is.
I'd cry if I bricked my Z3, honestly. I'd like to help.

this happen to me before, same like your phone and i think it brick cos system partition already mess up...
lucky me i still have warranty on that time so i sent to SC and change new motherboard....
whatever i do, still no succeed, just blink red led
i think u need to sent it to SC, don worry they cannot detect ur phone rooted or UB cos motherboard already fried up....
hahahaha

MickieH said:
Seems a shame to give up. There's nothing wrong with the hardware by all accounts.
You can get a new battery off ebay for £10 to £15 and they're factory charged to at least 50%.
http://pages.ebay.com/link/?nav=item.view&id=291420999095&alt=web
It may or may not work, but I'd rather try than bin a couple of hundred pounds worth of phone.
Whatever you decide, I'll help if I can. I love my Z3, even more so than my Z5 right now.
Good luck either way,
Mick
Edit:
I'd even go so far as to say, if you still have the complete phone, post it to me and I'll see what I can do with it. I'll post it you back when I'm done, and if I can fix it, it's only gonna be a new battery at the most. You can't really lose, it's not working as it is.
I'd cry if I bricked my Z3, honestly. I'd like to help.
Click to expand...
Click to collapse
As much as I'd love to trust you, and I'm sure you're a man of your word, I wouldn't risk sending it out to someone I don't know.. Who's to say I'd get it back? Bricked or not it's money. I don't mean to offend you.
Buying parts that only possibly fix the issue is currently out of the question to due finances, but is a possibility further down the line.
Thank you for all your help, and if I ever do manage to fix it, or require more help I'll be sure to come back again, you've been a great help.
Cheers

Strickened said:
As much as I'd love to trust you, and I'm sure you're a man of your word, I wouldn't risk sending it out to someone I don't know.. Who's to say I'd get it back? Bricked or not it's money. I don't mean to offend you.
Buying parts that only possibly fix the issue is currently out of the question to due finances, but is a possibility further down the line.
Thank you for all your help, and if I ever do manage to fix it, or require more help I'll be sure to come back again, you've been a great help.
Cheers
Click to expand...
Click to collapse
Lol, it's ok. I don't offend that easily, but I did laugh, so thanks for that. Was probably a stupid offer anyway, thinking about it. Perhaps it's me who's too trusting lol. Funny thing is, I would have sent it back, fixed or no, but that's just me. I'm sure there's plenty of people out there who would like to rinse you of a Z3, but me, I've already got one. And a Z5. And a Z4 Tablet, oh and my old Z1 which I gave to my daughter. I've even still got my old Arc S. Either way, good luck. I hope you do get it sorted. Just don't bin it.
As for the battery. I bet any money you'd be able to flash it IF you can get a battery in it with some charge.
Here's a counter offer: I fixed a Z3 for a friend of mine a few months ago. I'll ask him if I can have his spare battery. I made one good Z3 out of two broken ones you see, for him. If he let's me have it, I'll post it to you free of charge. Even if it doesn't work, at least we tried.

MickieH said:
Lol, it's ok. I don't offend that easily, but I did laugh, so thanks for that. Was probably a stupid offer anyway, thinking about it. Perhaps it's me who's too trusting lol. Funny thing is, I would have sent it back, fixed or no, but that's just me. I'm sure there's plenty of people out there who would like to rinse you of a Z3, but me, I've already got one. And a Z5. And a Z4 Tablet, oh and my old Z1 which I gave to my daughter. I've even still got my old Arc S. Either way, good luck. I hope you do get it sorted. Just don't bin it.
As for the battery. I bet any money you'd be able to flash it IF you can get a battery in it with some charge.
Here's a counter offer: I fixed a Z3 for a friend of mine a few months ago. I'll ask him if I can have his spare battery. I made one good Z3 out of two broken ones you see, for him. If he let's me have it, I'll post it to you free of charge. Even if it doesn't work, at least we tried.
Click to expand...
Click to collapse
I might be able to get a battery today actually, a friend of mine has a z3 and he's looking to sell it, but before he does he's going to borrow it to me in order to use his battery! I may just be in luck.
If I do manage to get the battery, I'll be sure to update this post with the verdict. The only worry is that if there's any cracks in the glass at the back, I won't be able to get the battery without completely ruining his phone, so don't want to do that.
I know that my back piece is completely shattered, so if I do manage to get the phone working after all, I'll have to source a new back lol.
Also, back to the topic of trust.. It's not that I don't trust you personally, I just don't trust the internet! I greatly appreciate the offer, and if this battery doesn't working out for me I'd gladly appreciate any help from you in the future.
Thanks again!