Related
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
Armando Penblade said:
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
Click to expand...
Click to collapse
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/showthread.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
BadUsername said:
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/showthread.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
Click to expand...
Click to collapse
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.
Armando Penblade said:
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.
Click to expand...
Click to collapse
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
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?
Armando Penblade said:
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?
Click to expand...
Click to collapse
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
Hi my SGS III apparently had a sudden death issue. The phone turned off out of nowhere and has not turned on. I have tried another charged battery to see if the battery was the issue but it did not work. I also notice that when I attempt to charge the phone it doesn't respond in any way (lights, vibration, led, or screen). However my phone does begin to heat up within about a minute of me connecting the charger.
Some one mentioned that my charging habits caused this. I leave the phone charging all night while I sleep. I did not know if this caused it, but someone told me its a bad habit to have.
Anyways my real question is: If I activate a new phone on verizon can I still at some future point turn on my phone (if I get it repaired) and recover my data from it? In other words if data recovery was a possibility, would me activating a new phone with the same number as this phone prevent me from recovering data from my phone (pictures, documents)?
I am not sure how phone activation affects a phone. Also sorry as English is not my first language.
universem2 said:
Hi my SGS III apparently had a sudden death issue. The phone turned off out of nowhere and has not turned on. I have tried another charged battery to see if the battery was the issue but it did not work. I also notice that when I attempt to charge the phone it doesn't respond in any way (lights, vibration, led, or screen). However my phone does begin to heat up within about a minute of me connecting the charger.
Some one mentioned that my charging habits caused this. I leave the phone charging all night while I sleep. I did not know if this caused it, but someone told me its a bad habit to have.
Anyways my real question is: If I activate a new phone on verizon can I still at some future point turn on my phone (if I get it repaired) and recover my data from it? In other words if data recovery was a possibility, would me activating a new phone with the same number as this phone prevent me from recovering data from my phone (pictures, documents)?
I am not sure how phone activation affects a phone. Also sorry as English is not my first language.
Click to expand...
Click to collapse
No, this would not cause any issues with data recovery.
Hello,
Let me make this as short as possible. I have a 3 and a half year old Nexus 5. Just got off a plane 6 hours ago, and when i wanted to check my Facebook the display looked like it failed. I had red vertical lines running up and down the stream and the brightness was extremely low even though the setting in the phone had not changed. All the while, the phone was also impossible to maneuver. I rebooted it, the problem persisted for 5 minutes, and then after a quick lock-unlock, it fixed itself.
About 10 minutes later, when I again tried to unlock my phone to check if things were okay, the display went completely black. If I connect the phone to a charger, the display gets a little illuminated like it's going to start but nothing actually happens, I cannot see anything on the screen. The phone is responsive, if I plug it into a PC it starts charging and the PC recognizes it, but I can't see absolutely anything but black on the screen. Now with the questions:
1) What type of problem do you think this is. Wiring, display, or dead phone and no repair possible? As a best guess at least.
2) Before I take the phone into a service, I would like to know if there's any way I can download the pictures and data I had stored on it that was not yet backed up. As I said, I was just returning from a trip and I have some pictures on it, and while the PC recognizes the phone, it is put automatically in USB Charge mode and not USB Mass Storage Device mode. The phone is NOT rooted and USB Debugging was enabled before it crashed. The phone is up to date with the latest firmware.
Thank you in advance.
Does the touch function work? Is the bootloader unlocked?
If yes to both, you could load twrp, boot into twrp, mount the data partition, and copy off files.
It sounds like a failed screen to me. Was the phone ever dropped or exposed to moisture?
audit13 said:
Does the touch function work? Is the bootloader unlocked?
If yes to both, you could load twrp, boot into twrp, mount the data partition, and copy off files.
It sounds like a failed screen to me. Was the phone ever dropped or exposed to moisture?
Click to expand...
Click to collapse
The screen is pitch black. If I touch the screen I can't feel anything or see anything, and I have no certainty I would be in the right menus. The only reaction I get is if I plug it in or reset it. The phone was never dropped, it is still in impeccable condition, no scratches or bumps. It wasn't exposed to moisture either, I wonder if the flight had anything to do with it, pressure and all.
So basically, apart from what you mentioned, there's no other way if my data is not backed up? I will be taking it in tomorrow, hoping for the best.
It's weird that this happened suddenly. The simplest solution may be to place the motherboard into another working phone.
You didn't answered about unlocked bootloader.
adrian.lupas said:
Hello,
Let me make this as short as possible. I have a 3 and a half year old Nexus 5. Just got off a plane 6 hours ago, and when i wanted to check my Facebook the display looked like it failed. I had red vertical lines running up and down the stream and the brightness was extremely low even though the setting in the phone had not changed. All the while, the phone was also impossible to maneuver. I rebooted it, the problem persisted for 5 minutes, and then after a quick lock-unlock, it fixed itself.
About 10 minutes later, when I again tried to unlock my phone to check if things were okay, the display went completely black. If I connect the phone to a charger, the display gets a little illuminated like it's going to start but nothing actually happens, I cannot see anything on the screen. The phone is responsive, if I plug it into a PC it starts charging and the PC recognizes it, but I can't see absolutely anything but black on the screen. Now with the questions:
1) What type of problem do you think this is. Wiring, display, or dead phone and no repair possible? As a best guess at least.
2) Before I take the phone into a service, I would like to know if there's any way I can download the pictures and data I had stored on it that was not yet backed up. As I said, I was just returning from a trip and I have some pictures on it, and while the PC recognizes the phone, it is put automatically in USB Charge mode and not USB Mass Storage Device mode. The phone is NOT rooted and USB Debugging was enabled before it crashed. The phone is up to date with the latest firmware.
Thank you in advance.
Click to expand...
Click to collapse
It's just the ribbon cable .You can change it by yourself it's too damn easy plus the cable is really cheap
It's either the flex cable or the LCD itself.
cheeze.keyk said:
It's either the flex cable or the LCD itself.
Click to expand...
Click to collapse
It was the LCD. I got a replacement LCD but now even with my brightness to the maximum, the phone still is darker than before. I also got a new battery in it. Is there an option to change the brightness that is hidden, or some kind of power saving option?
Thanks.
This Tuesday my OnePlus One fell into a lake. I let it dry for 2 days before powering it on, but there are a couple things wrong. The screen has messed up colors and what looks like artifacting (water stains I've heard them called?) so I've resigned myself to buying a new phone (hopefully tomorrow), but there are some files I had stored on my now old phone that I'd like to try to recover.
Even after leaving it to charge all night, it won't turn on unless plugged in. When plugged in, it will continuously show the Low Battery screen (with the Chinese text). If I hold volume-down while plugging it in, it will enter a bootloop (vibration, OnePlus logo, screen off, repeat) until unplugged, at which point it immediately stops and turns off. My PC doesn't register it at all when either of these two things happen. The screen doesn't turn on if I hold volume-up while plugging it in, but it will register on my PC as QDLoader 9008.
Before all this I was running the latest nightly of LineageOS and TWRP with an unlocked bootloader.
I've been very happy with my phone for the past 4 years but with the screen the way it is I'm not interested in fixing it, all I want is to access the data partition from my PC. I have Android Studio, adb, etc installed on my PC, is there any way to get adb to recognize my phone either in the low-battery screen or when recognized as QDLoader? Turning off immediately when the charging cable is removed makes me think its a broken battery which I could just replace, but I'd prefer not to spend any money if I don't have too seeing as I'm buying a new phone.
I've spent hours searching forums and Google for solutions, but all the solutions seem to involve wiping the drive to save the phone, while I'm not interested in saving the phone, just my data. The stickied debricking thread also seems to be targeted to hard-bricks, but considering the circumstances I don't think my phone is actually bricked at all, it just probably has a damaged battery.
Thanks!
Sorry to hear about your phone. Have you opened it up to check that all the contacts are dry? Water may have caused corrosion. Also, if you encounter water damage in future, it would be better to place your phone in a desiccant.
Hello!
I recently tried to replace my LCD/Digitizer on my S6 edge SM-G925V. Everything went well...at least I thought. The display works great! However, I believe I have either a battery issue or a OS issue.
After I installed the new screen, I booted the phone up. It loaded up fine. I went to check to make sure every feature worked. I was playing music to test the speaker and the phone just restarted on its own. I found that to be odd, and so I tried again. Same thing. This is just a couple minutes into it turning on by the way. Sometimes it would take longer to restart than others, but it was generally in the same time frame. I did try other apps to see if maybe the music app was causing it to have issues. The phone would restart randomly regardless of what I was doing.
I first thought that maybe the battery wasn't charged up enough. I charged it some, but was still getting the same issue. I then went to try and boot into safe mode. Still the same issue was there. I tried resetting the phone, master resetting the phone, and also wiping the partition. The phone now boots to the Samsung screen, then goes to the Verizon screen and then reboots in a endless cycle.
So...it was booting correctly, but randomly restarting. NOW, it's not getting past the Verizon screen and rebooting.
I tried using Odin and resetting it using the latest software update. It would pass just fine. The phone would reboot then go to "Installing Updates". It would get to 32% then say "Erasing". It would reboot back to the Samsung screen and start the endless boot process again.
The one thing that Intrigued me and led me to trying to use Odin was that when I would boot to the Downloader screen (The blue screen where you have to press up on the volume button to continue or down to cancel) the phone would never restart on that screen. I figured if it was a battery issue then it would restart regardless of what screen I was on.
But, I noticed something after all of this. The LED stays light up blue when the phone is powered off. The LED lights work correctly when the phone is on (Red when charging, changing from blue to green in a wave like pattern when turning on).
That kind of made me rethink the problem, and go back to it being a battery?
So, this is where I stand now. The phone would boot up, but randomly restart. I thought the OS may of been corrupted or something went wrong during the replacement of the screen so i tried resetting it, etc. Now, it the phone is just stuck in a endless loop. I noticed the LED lights up blue while the phone is turned off, so it has led me back to thinking it's a battery issue.
Lastly,
I don't believe I messed anything up when removing the battery. I was very gentle. I was watching a YouTube video that pointed out that thier technician poked the battery in the video, and they kept it there so we could learn from their mistake. Their battery leaked out a little and showed some residue on the black part of the piece it is mounted in. I never seen in residue or anything like that when I did mine.
I also unplugged the battery first before unplugged any of the other ribbons connected to the motherboard.
I am new to repair screens and I wanted to try on some of my old phones to get practice. Although this issue is frustrating, it is giving me a loads of knowledge on issues. It would be greatly appreciated if anyone could help me out with this. I'm not sure where else to go from here. I do have a battery ordered, but probably will not get here til sometime next week.
Thank you everyone for taking the time to read this long post!
Try replacing the battery. Make sure all grounding pathways and connectors are properly connected. Sometimes they may use unconventional pathways like the frame or a screw.
Impacts that can break the screen can cause high enough G loading to internally damage chipsets, fracture solder bonds (including hidden BGA ones) and damage internal mobo traces.
The display and mobo when out of circuit are suspectable to ESD damage. Full ESD protocols and procedures should be followed. Even though many techs don't do this doesn't mean they don't damage hardware. It may take weeks or even years to manifest itself. Handle the mobo, display and sim card like a stick of ram.
In 11 years I've only seen one tech install a sim card properly; ESD mat and wrist strap.
blackhawk said:
Try replacing the battery. Make sure all grounding pathways and connectors are properly connected. Sometimes they may use unconventional pathways like the frame or a screw.
Impacts that can break the screen can cause high enough G loading to internally damage chipsets, fracture solder bonds (including hidden BGA ones) and damage internal mobo traces.
The display and mobo when out of circuit are suspectable to ESD damage. Full ESD protocols and procedures should be followed. Even though many techs don't do this doesn't mean they don't damage hardware. It may take weeks or even years to manifest itself. Handle the mobo, display and sim card like a stick of ram.
In 11 years I've only seen one tech install a sim card properly; ESD mat and wrist strap.
Click to expand...
Click to collapse
Hi!
Thank you for the detailed reply. Very insightful.
I've been at work for the last few hours. I left the phone powered off while I was gone. I got back and the phone is powered off, but the LED light is still blue. The only way to get that to go off is by unplugging the battery ribbon from the motherboard.
The phone was on at least 70% of battery before I left. I get back and it started charging at 20%. Mind you, it's been off while I was gone.
Do you think the safest route would be to unplug the ribbon until the new battery arrives?
TrumpXLV said:
Hi!
Thank you for the detailed reply. Very insightful.
I've been at work for the last few hours. I left the phone powered off while I was gone. I got back and the phone is powered off, but the LED light is still blue. The only way to get that to go off is by unplugging the battery ribbon from the motherboard.
The phone was on at least 70% of battery before I left. I get back and it started charging at 20%. Mind you, it's been off while I was gone.
Do you think the safest route would be to unplug the ribbon until the new battery arrives?
Click to expand...
Click to collapse
If you think the battery has failed don't charge it.
Any swelling is a failure.
A sudden drop in capacity or erratic charging are also signs of a failure. I just went through this with my 10+'s battery
It's possible the battery was physically damage when the screen got broke, they're are really flimsy.
Best to rule out the battery.
It won't do your sanity much good until you do.
Examine the charge port PCB closely for any damage or solder cracks.
Examine the mobo as well. A stereo magnifying visor helps.
Hopefully the new battery will get it
Hello, I have the same exact problem. Verizon phone. Replaced screen from another phone. The phone boots normally, reaching the lock screen/home screen, but restarts after a few seconds. Performed a factory reset via the recovery menu, but now I'm stuck on the Verizon logo. Never-ending restarts. Never reaches the setup screen. The LED keeps on flashing blue-cyan at times despite forcing the phone off from maintenance boot mode (vol down + power). Tried factory resetting from there as well to no avail. Swapped back the old screen, but the boot loop persists. The battery is new (manufactured in 2020), had no random shut-off whatsoever prior to the swap, and had great SOT.
The worse part is the phone is undetectable via USB, the phone rarely fast charges. I suspect a burnt diode/capacitor on the mainboard itself because prior to the screen swap, I tried a daughterboard swap first. Both daughterboards work just fine and can handle both fast charging and data transfers on the donor phone. Both didn't work on the Verizon one. Can't even try flashing the firmware via Odin because of this.
Have you ever gotten to find a solution to this?
wildcatacu said:
Hello, I have the same exact problem. Verizon phone. Replaced screen from another phone. The phone boots normally, reaching the lock screen/home screen, but restarts after a few seconds. Performed a factory reset via the recovery menu, but now I'm stuck on the Verizon logo. Never-ending restarts. Never reaches the setup screen. The LED keeps on flashing blue-cyan at times despite forcing the phone off from maintenance boot mode (vol down + power). Tried factory resetting from there as well to no avail. Swapped back the old screen, but the boot loop persists. The battery is new (manufactured in 2020), had no random shut-off whatsoever prior to the swap, and had great SOT.
The worse part is the phone is undetectable via USB, the phone rarely fast charges. I suspect a burnt diode/capacitor on the mainboard itself because prior to the screen swap, I tried a daughterboard swap first. Both daughterboards work just fine and can handle both fast charging and data transfers on the donor phone. Both didn't work on the Verizon one. Can't even try flashing the firmware via Odin because of this.
Have you ever gotten to find a solution to this?
Click to expand...
Click to collapse
The part number on the daughter board must match the replacement. There maybe two US versions... if so they are incompatible.
blackhawk said:
The part number on the daughter board must match the replacement. There maybe two US versions... if so they are incompatible.
Click to expand...
Click to collapse
I do have the SM-G925V (Verizon, 64GB) and SM-G925F (Global, 32GB). Originally, Verizon had a broken screen, a USB issue, and randomly restarts. SM-G925F did have a Knox-tripped mainboard and a faulty daughterboard, but only the 3.5mm jack didn't work.
Swapping only the daughterboards, I was able to use the Global just fine even after flashing the original firmware. The Verizon one despite having an older battery did suffer fewer random restarts and I started using it primarily as a hotspot device. The global one uses a newer battery I ordered online.
Prior to Verizon's factory reset via recovery menu, It had all the original components except the newer battery and the screen from global. I tried a reset because the random restart became even more persistent even while doing nothing. Now, Verizon is stuck, boot loop. I tried swapping even all the original components (older battery, broken screen) just to see if the phone will proceed to the setup screen. It didn't.
Were you able to fix the boot loop issue on your Verizon?
wildcatacu said:
I do have the SM-G925V (Verizon, 64GB) and SM-G925F (Global, 32GB). Originally, Verizon had a broken screen, a USB issue, and randomly restarts. SM-G925F did have a Knox-tripped mainboard and a faulty daughterboard, but only the 3.5mm jack didn't work.
Swapping only the daughterboards, I was able to use the Global just fine even after flashing the original firmware. The Verizon one despite having an older battery did suffer fewer random restarts and I started using it primarily as a hotspot device. The global one uses a newer battery I ordered online.
Prior to Verizon's factory reset via recovery menu, It had all the original components except the newer battery and the screen from global. I tried a reset because the random restart became even more persistent even while doing nothing. Now, Verizon is stuck, boot loop. I tried swapping even all the original components (older battery, broken screen) just to see if the phone will proceed to the setup screen. It didn't.
Were you able to fix the boot loop issue on your Verizon?
Click to expand...
Click to collapse
I know about because I ran into that problem on my N10+ N975U. Apparently there are 2 C port pcb variants. In my case the original pcb was still good so they just put it back in.
So much for preventive maintenance...
blackhawk said:
I know about because I ran into that problem on my N10+ N975U. Apparently there are 2 C port pcb variants. In my case the original pcb was still good so they just put it back in.
So much for preventive maintenance...
Click to expand...
Click to collapse
Sorry, I thought you originally posted the problem. I just noticed it was @TrumpXLV. Nevertheless, thanks for providing some insight. I did try to swap back all the original components on both of the variants, Global and Verizon. Did a factory reset via recovery menu on both, but only the Global one reset just fine and the Verizon one didn't.
I was curious if @TrumpXLV did find a solution. This is the only post I found that described the same issue, the same model. Might have to shelve this phone for now. Was planning to repurpose this phone in some way originally. I'm daily driving S10+ atm.