Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,729,023 Members 41,132 Now Online
XDA Developers Android and Mobile Development Forum

Is My VZW S3 Dead? (Symptoms in Text)

Tip us?
 
Armando Penblade
Old
#1  
Junior Member - OP
Thanks Meter 3
Posts: 11
Join Date: May 2010
Location: Raleigh, NC
Default Is My VZW S3 Dead? (Symptoms in Text)

About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.

Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.

The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.

Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.

----------------------------------------------

The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).

I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.

Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).

The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
 
BadUsername
Old
#2  
BadUsername's Avatar
Senior Member
Thanks Meter 630
Posts: 1,287
Join Date: Mar 2013
Quote:
Originally Posted by Armando Penblade View Post
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.

Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.

The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.

Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.

----------------------------------------------

The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).

I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.

Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).

The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/show....php?t=2581166

Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.

Sent from my SCH-I535 using Tapatalk 2
The Following User Says Thank You to BadUsername For This Useful Post: [ Click to Expand ]
 
Armando Penblade
Old
#3  
Junior Member - OP
Thanks Meter 3
Posts: 11
Join Date: May 2010
Location: Raleigh, NC
Quote:
Originally Posted by BadUsername View Post
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/show....php?t=2581166

Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.

Sent from my SCH-I535 using Tapatalk 2
This doesn't seem to have any effect on the proceedings.

I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
 
BadUsername
Old
#4  
BadUsername's Avatar
Senior Member
Thanks Meter 630
Posts: 1,287
Join Date: Mar 2013
Quote:
Originally Posted by Armando Penblade View Post
This doesn't seem to have any effect on the proceedings.

I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
But that's what it's supposed to look like when it's hard bricked, keep trying to write it then boot with it. Eventually it's going to work, unless you somehow fried your motherboard.

Sent from my SCH-I535 using Tapatalk 2
The Following User Says Thank You to BadUsername For This Useful Post: [ Click to Expand ]
 
Armando Penblade
Old
(Last edited by Armando Penblade; 15th February 2014 at 10:16 AM.)
#5  
Junior Member - OP
Thanks Meter 3
Posts: 11
Join Date: May 2010
Location: Raleigh, NC
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.

Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
 
BadUsername
Old
#6  
BadUsername's Avatar
Senior Member
Thanks Meter 630
Posts: 1,287
Join Date: Mar 2013
Quote:
Originally Posted by Armando Penblade View Post
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.

Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Not really, if you're getting that error message I'm assuming this should work. At the very least you could get a jtag repair and that'll definitely fix it. You could always try the other debrick file available from that thread also.

Sent from my SCH-I535 using Tapatalk 2
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Remove Unnecessary WhatsApp Elements with Xposed

In modern life, you can’t underestimate the power ofthe dark sidemessaging … more

MaR-V-iN to Talk Google and Android APIs at XDA:DevCon 2014

Our international xda:devcon 14in Manchester, UK on the weekend of September … more

But First, Let Me Take a #Selfie

“Today while browsing XDA,I’m going tocheck to seeif my favorite ROM has been updated–but … more