Changing the thread around to reflect the current situation, new text at the bottom of the post.
While out to dinner with my family an hour or so ago, my phone suddenly stopped working. I had been checking some emails when the food arrived, so I pressed the power button to shut down the screen and set the phone to the side. About 30 minutes later, I tried to open my phone to continue where I had left off, only I got no response at all from the device. I immediately tried the normal troubleshooting actions (holding power button for 30+ seconds and attempting to go into recovery mode), but still got no response from the phone. I have since tried charging it at home with it's original quick charger, but even after 15 minutes on the charger, there isn't even a red light indicating it is charging. Is there anything that I can try to fix this on my own, or is it likely that I've got some technical fault that only Verizon can deal with?
Thanks.
PS: I'm 100% sure that no liquid came in contact with my phone during dinner. Even if I wasn't so sure, both the phone and case have been bone dry through the entire ordeal.
New situation:
The "techs" at Verizon were less than useless... While there, they tried fewer fixes than I was able to attempt before telling me that the only option they could offer is to replace the phone. The problem, as I've said a little lower in this thread, is that I've got some irreplaceable photos of my recently deceased cat of 19 years stuck on the phone that I never got the chance to back up before this event.
And so now I need options. I'm willing to do pretty much anything, up to and including tearing the phone apart to manually access the memory unit, but the end result absolutely has to be those photos recovered.
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
DroidXrei said:
Did you do the hard reset combination (Power, Vol Down?) I've had the problem happen to me before. Usually, what happens is it will lock up when it is having memory issues, freeze, then if I'm lucky, it will come out of it. Otherwise I have to do a hard reset.
It hasn't happened yet since I've been on 5.1.1 but I've only been on that for 3 days or so.
Edit: Just in case you didn't know, the recovery combination is Power, Vol Up, and Home when the phone is actually off. When the phone freezes like that and you don't get a response it's still on but completely locked up until you power off the phone.
Sent from my Super Computer (1976) with Tap Tap Talkolution
Click to expand...
Click to collapse
I've tried soft reset (hold power only), hard reset, and recovery, all to no avail, and holding each for long after it's supposed to respond (at least 60 seconds).
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Theodric58 said:
Volume down and power should simulate a battery pull. If that does not work, I would recommend going to a Verizon store.
Give your name to the concierge.
When they call your name, try the Volume down + Power again.
It should work then.
Click to expand...
Click to collapse
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
treblesum81 said:
I'm really hoping they will provide more help than that. There are some pictures of my cat on the phone that I had to euthanize last week after 19 years that I never had the chance to back up.
Click to expand...
Click to collapse
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Theodric58 said:
I'm sorry about your cat.
It was more to the point that what doesn't work when you are on your own, will work perfectly when you take it to the technician.
I used to do tech support for phones and tablets. I've seen lots of instances where the customer tries something with me on the phone that they had tried multiple times before, and with me on the phone it works immediately. Try the key combos with it plugged in, with it plugged in to a different charger, with it plugged into your computer. If none of those work, then take it to Verizon.
Click to expand...
Click to collapse
All of this was done before taking it to Verizon. All key combinations were tried unplugged then plugged into 3 different chargers and also my computer with 3 different cables and several different USB ports. When I went to Verizon, they tried the key combinations unplugged and then tried plugging it in and seeing if it would take a charge... hence the assertion that they tried less than I was able to attempt at home.
Time to find someone who can repair the phone locally. Any type of warranty or factory repair will cost you the pictures.
Sounds like it's safe to say the phone is beyond simple trouble-shooting. I found myself in a similar predicament last year when I busted the screen on my S4. I dropped my phone on some concrete steps and the screen (in addition to being shattered) went completely black, but I knew the phone was still working because I could still hear the person I was taking to on the phone lol.
I ended up replacing the phone through Verizon. They referred me to some third party company that agreed to replace the phone for $100 and sent me a replacement with a box to put the busted one in. At this point I found myself presented with a unique opportunity, given the fact that I had both a working S4 and my broken one.
Because I didn't have the chance to back up the phone before I lost access to it (it's pretty hard to unlock a phone without the screen) I looked up a guide on how to disassemble the S4 on YouTube in order to gain access to the motherboard. The whole process was relatively easy to carry out and I was able to disassemble both phones, switch the motherboards, backup the information I needed, and switch them back.
Sorry for the long-winded response. I realize this is a pretty drastic measure to take and that you may not have access to a second S6. It's also entirely possible that the motherboard on your phone is part of the problem so switching it wouldn't help much in that case (like I said, I knew my phone was still working despite the screen). Just wanted to offer another option =).
I am in a similar predicament, desperate to get my photos and videos back and have been watching your thread for some ideas. My 7 week old Verizon Samsung Galaxy S6 G920VVRU4BOG9, android version 5.1.1. ceased to do anything on Monday for reasons unknown. It is now back on but it has been wiped clean. I had to do a hard reset. Samsung & VZW tech support were not helpful. May I ask what model your phone is? Provided you are able to get yours back on, I'm wondering if you may have some success with some of the following:
Wondershare Dr Fone for Android
Asoftech Data Recovery
Kvisoft Data Recovery
Ease US data recovery.
I could not get them to work because you must first have a rooted phone to retrieve them and mine apparently can't be rooted. I apologize if this is redundant but I thought I'd throw that out there in case you might have a change of recovering those photos. I'm sorry for your loss. It's very hard to lose a beloved pet.
Related
Hi!
Today I got from my friend a bricked Desire S.
He said, he tried updating a pile of apps at once and it froze. He left it to cope with that and when he was back it was turned off.
When turned on it would stuck on htc logo. He read somewhere that he has to perform a "factory reset". I'm not sure what exactly has he done later (he did this with holding the volume up and power buttons and than there had to be, as he said, an option to reset the device), but the result is, that the device doesn't respond at all.
Nothing happens when connected to USB or charger.
Is there anything I can do about it?
Maybe force push bootloader with adb?
Please, help guys
Hi,
it doesn't do anything at all?
Power button?
Power button + Volume down?
Recharge battery?
Connect to a PC with properly installed htc drivers?
Remove battery and put it back?
Unfortunately yes.
Tried different combinations several times - once or twice the led blinked for like a half a second, but than nothing.
I have some flashing experience and I learn quickly. If You have ANY ideas, I'll try to make them happen.
I will try everything, as I have nothing to loose
Regards.
SorbetM said:
Hi!
Today I got from my friend a bricked Desire S.
He said, he tried updating a pile of apps at once and it froze. He left it to cope with that and when he was back it was turned off.
When turned on it would stuck on htc logo. He read somewhere that he has to perform a "factory reset". I'm not sure what exactly has he done later (he did this with holding the volume up and power buttons and than there had to be, as he said, an option to reset the device), but the result is, that the device doesn't respond at all.
Nothing happens when connected to USB or charger.
Is there anything I can do about it?
Maybe force push bootloader with adb?
Please, help guys
Click to expand...
Click to collapse
Whenever we see “And I was updating apps and it froze up.....” we have a suspicion we perhaps have another case of the eMMC chip packing in. At least he didn’t do a battery pull. Holding UP + DOWN + POWER has a similar effect to hitting reset on a PC. You can’t get to recovery this way.
With the phone off, hold just the DOWN + POWER. Does the phone then boot into HBOOT? (white screen with coloured text and little green androids at the bottom). If it does, great. You can choose RECOVERY from this and do a factory reset. If the phone does a series of (seven?) quick vibrations maybe not so good.
Search for “eMMC” in this forum to get plenty of people who had this problem, and how (some of them) have been able to fix it. Knowing what to search for is half the battle!
For example check this thread out...
http://forum.xda-developers.com/showthread.php?t=1284196
Geek out!
Thanks for the reply,
I actually have tried entering the hboot few times - with no success.
It doesn't respond at all.
I've read about this chip, but I want to make sure there is no option to force the phone to enter recovery. Than I would probably know what to do next.
Regards.
SorbetM said:
Thanks for the reply,
I actually have tried entering the hboot few times - with no success.
It doesn't respond at all.
I've read about this chip, but I want to make sure there is no option to force the phone to enter recovery. Than I would probably know what to do next.
Regards.
Click to expand...
Click to collapse
Not sounding good I'm afraid. The last resort would be to contact HTC and try to get it repaired on warranty. They are very very aware of the problem, and once you tell them "I was updating all apps at once and it froze" they'll accept it as a known hardware failure. Like you say, you have nothing to loose in trying.
A friend recently had this, and sent if off to HTC for repair. As the description of the fault was a known hardware failure, they never bothered to test it first, so they didn't notice it had been rooted! It just went straight through to get a main board replacement. It took five weeks for them to return it though. Best fish out that battered Nokia in your drawer and charge it up ready!
Good luck!
Uh, these are quite bad news, but I'm pretty sure they will accept it on warranty, since my friend haven't done anything "illegal" with it
Thank You for Your fast replies
Regards.
So my story begins with me purchasing a used white Nexus 5 for $155 from swappa over a week ago for my wife. *
Phone arrives in perfect condition.
I first unlocked and flash twrp via adb. I proceed with installing Chroma and elementalx. Spend few hours on making the new Nexus 5 the same as my wife's current Galaxy Nexus.
Phone is running great. Zero issues for about 3 days while the phone was just at home running. She throws the phone into her purse and goes to work. Within hour she calls that her phone won't stop rebooting…. *Oh no…. The dreaded power button issue… right?
So I'm assuming the seller did the old “whack against a solid object” temp fix and sold it. I have no proof of that so I'm assuming.
So what do to? Well fixing the power button is still cheaper than buying another Nexus 5 phone. Everyone one quoted me $60. It is what it is… at this point I could have gotten a refurbished phone but what can you do…
So you would think this is the end of my story, right? Wrong.
I go to a cell phone repair place close to my work. They have this tiny power button in stock and replaced it many times before. I come back later that day to pick it up and they have bad news… of course they do.
After the switch replacement, the phone did the same reboot. Goes to Google logo and reboot. If I fiddle with the power button I can get to the OS but reboot right away. The guy proceeds with that it is me rooting it that caused it and I need a new motherboard, price $100.
I started questioning if he really did replace the switch. If it was OS related, the phone would not have worked for couple days and then break randomly. It would not boot to the OS sometimes or at least it would let me boot into TWRP, right?
Long story short, I left with spending the $100 on getting this used $155 phone fixed. Super annoyed at this point.
So after this long story, is there any chance this was really OS related and not a faulty power switch or did I just got lied to and the power switch was never replaced?
For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk
Curiousn00b said:
For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I sure tried to get into recovery but wouldn't work. Just kept rebooting. I had a nandroid backup done a day before but the phone would not stay powered on for long enough to do anything. It was the equivalent of having no battery left and phone just shut down and attempted to reboot constantly. I took out the motherboard and played around with the button before I went out to repair it but it was the same results. If I "massaged" the button then maybe the phone would get past the Chroma logo and get into the OS, but as soon as I attempted to touch the power button again it would reboot.
I tried reviewing the old motherboard and unless this shop's soldering skills are top notch, I can't tell that the switch was replaced. The soldering point were identical to the volume buttons. When I questioned the store owner, he stated they are that good with their infrared soldering He took out a package of 3 Nexus 5 switches and one was missing... meaning he installed it.
I highly doubt it was OS related. If you brick a phone when flashing, then it would just be constantly in a boot loop, right? I know I can easily go into recovery and flash whatever .img I need to, but this was just nonstop reboot and different times
My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/
Hi,
I think I have bricked my S7.
Yesterday I installed Superman Rom and everything was working fine until this afternoon.
I played a bit around and somehow my S7 got stuck and it seemed like i messed something up. I was in some kind of bootloop so i flashed everything new -Bootlaoder, Modem and Superman Rom.
Now I have a black screen and the LED is light up in blue.
I can't do anything. Tried to restart with Home Vol- and Power key but it doesn't work.
If I connect it to the Computer it won't be recognized.
Strange thing is, if I press the Power Key the computer recognizes Exynos8890 in the device manager, but only if I keep pressing the power key.
As soon as I release the power key the computer recognizes nothing...
Does anyone have an idea?
Try holding Volume Down & Home & Power until the phone reboots twice, keep the buttons pressed for 2 full reboots, and hopefully the 2nd one will get you back into download mode
Thank you for your help!
I tried that but it doesn't work.
It's strange because I can do what I want and nothing happens.
Black screen and blue light. It doens't even turn off or reboot...
Only thing what happens is that exynos8890 appears in the device manager as long as I keep pressing the power button.
Same problem as me?
http://forum.xda-developers.com/galaxy-s7/help/boot-loop-bricked-t3499109/post69596073#post69596073
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
alexx3333 said:
Sounds different.
Because you are able to get into recovery and download. I'm not able to do that
Click to expand...
Click to collapse
How long are you holding the button combination for?
Try 30 seconds+
I tried for several minutes, but the phone doesn't do anything.
I can only think you'll need to wait until the battery runs out, the phone shuts off, then when you charge it again, try the download mode button combo when you power it back on
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
alexx3333 said:
Ok thank you.
I thought the same.
Unfortunately the battery was at 90% so I think it will take a few days/weeks until it dies...
Click to expand...
Click to collapse
Connect the white Micro > Normal USB adapter that came with the phone to the MicroUSB port, and connect a power hungry USB device to it, I just tried with a USB desk fan and the phone powered it on spinning
That will drain the battery quickly
Great idea but it doesn't seem to work.
Looks like I have no power in the USB connection.
Seems like the phone is totaly frozen.
Ok so how it looks at the moment, my only choiches are wait several days until the battery dies (don't know how long this will take) or sending it to Samsung for a repair.
Thank you for your help!
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
*Detection* said:
Good luck, if I think of anything else I'll reply here, hope you get it sorted
EDIT - Did you try holding the power button while you had the USB device connected, to see if it provides USB power then?
Click to expand...
Click to collapse
Yes I have tried that but no power at all...
stoanhart said:
Wow, the exact same thing literally happened to me yesterday.
I wasn't doing anything to the phone - it's completely stock and unrooted, and I wasn't messing with anything. At the time it happened, I scrolling through the task switcher when all of the screenshots of running apps suddenly became white squares. I tried pressing the home button but it didn't respond (though I could still scroll fluidly through the white squares). A few seconds later the screen went black and that was it. Dead dead dead. Totally bricked. The only response I can get is "Exynos8890" in the Device Manager when holding the power button, just like you.
This really sucks because I paid full cash and imported an international version, so I have no warranty. I'm off to the Samsung store to plead with them about honoring the warranty anyway, maybe if I offer some cash on top.
I suspect the storage chip failed. Yesterday before it died, I was downloading all of my images off of the SD card to organize them, and I noticed that about 5% of them failed to copy due to an unknown I/O error. Of course I assumed this was a corrupt SD card, not internal storage. I did manage to pull them all off (though some were damaged) through a combination of adb shell, dd, and adb pull. During the process the phone hard-locked a few times, but each time I was able to reboot via the VolDown+Power combo.
When the phone finally died for good, it was several hours after I had finished copying the photos and since hte last reboot. It had been working perfectly since then - I was browsing reddit, watching netflix, etc. However, given that I got the white squares in the task switcher right before it kicked the bucket, I think the internal storage was actually to blame, not the SD card. The white squares indicates that it was trying to fetch the screenshots off the disk and failing.
It's very odd that I cannot find any other instance of this kind of failure on the internet except this one thread, which happened on the exact same day that my phone died. Very strange.
Click to expand...
Click to collapse
That sounds exactly like my Problem.
A faulty storage chip would also explain my Problems before the phone died for good.
The day my phone died I had some Problems. The phone was frozen from time to time until it got into the bootloop, but I thought I messed something up in the Rom because I did a lot of testing and the Combo also did work.
After reflashing the Rom everything seemed to be fine first until it died for good.
Yes it's strange, I also didn't find anything similar on the Internet.
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
stoanhart said:
I have learned my phone is from Nigeria. This should be a fun RMA process. FML
Click to expand...
Click to collapse
Contact Samsung on twitter, unlikely they'll force you to RMA to Nigeria, they'll have service centres in your region
I managed to get Samsung Canada to refer me to a local service center. I drove 1.5 hours to go there today, the dude plugs it into a charger, and the damn thing just lights up like nothing ever happened. Now it's working fine, but I swear this thing was fully bricked before. The battery still had 73% charge when it came back alive...
I'm happy it's working now, but I'm worried it's just going to crap out again at any time.
Update: after the phone revived itself, it worked pretty well for a week. It locked up a few times, but I was able to reboot each time.
But, after a week, it hard-froze again. This time, it happened to be on charge while it froze so the green LED was on. It's been completely unresponsive for 2.5 weeks now, off charger, with the green LED on. I keep waiting for the LED to drain the battery, but it's taking forever. I'm losing hope that it will recover this time. I guess I'll re-start the process of getting in touch with Samsung, or alternatively, look for a replacement motherboard on eBay.
Does anyone know if the G930F motherboard fits into the G930FD body? I don't actually care about dual sim, but I'm concerned the SIM tray/slot won't work with the G930F motherboard.
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
alexx3333 said:
Update:
so in the meantime the battery of my s7 died but that didn't change anything. I wasn't able to charge it after that so now it was completely dead.
So I contacted Sasmsung.
They replaced the motherboard and the USB connector on warranty.
Seems like it really was a hardware issue...
Click to expand...
Click to collapse
Hi,
Do you need Proof of Purchase for the warranty?
Thanks.
I posted this on the tmobile site but can't seem to get an answer. I have no idea what to do.
So I've had my phone on for at least 7 days. A notification from Samsung's plus app told me to reboot it because blah blah it helps or something.
So I turned it off.
Now it wont turn back on. Tired holding power plus volume down. Tried booting into recovery. Don't have a Windows PC irght now to plug into and try things , but will install windows on a mac via bootcamp.
When I plug it into any charger. Nothing.
When I set it atop a wireless charger. The wireless charger detects it, meaning it lights up. But the phone itself doesn't give any LED notification.
Phone gets warm while on wireless charging pad also. So it may be charging.
What is going on? Any advice?
Plug it into a charger, hold the vol down and power button for like 30 seconds then the screen should turn on saying its charging, then just power it it on.
Nothing. It gets warm when charging. But nothing.
Am I pressing it wrong maybe?
Strange that usually worked for me when i couldn't turn on my phone normally, can you get into download mode? Vol up + home + power.
Well this sucks i can't turn my phone on now, the battery was depleting somewhat rapidly so i rebooted the phone, once it got to the unlock screen it froze. Now no matter what i try i can't get it to turn on.
Today it managed to start charging, but when I turn it on when it's charging the screen freezes into a garbled mess, without charging it manages to boot.
peachpuff said:
Today it managed to start charging, but when I turn it on when it's charging the screen freezes into a garbled mess, without charging it manages to boot.
Click to expand...
Click to collapse
Same charging from PC?
Tried a different cable?
I have a Lumia 535 that messes up touch if I use my Sammy charger, same if I use my Raspberry Pi charger on my Windows tablet, the touch screen goes mental
Try a different charger / USB lead
I used various cables/chargers so that wasn't it. I went to a Samsung repair center and they suggested that... I have too many apps installed and that's causing the issue? Oooooook, granted this was just a rep and not someone doing the actual repairs.
Again my battery was low and I decided to reboot it and I can't start it again, very strange. If I get it working again it seems easy to duplicate if I goto Samsung again.
Called my credit card company and they have extended warranty on all purchases so i'm safe, the samsung store suggested to bring it in if happens again and they'll extend my warranty 3 months too.
peachpuff said:
I used various cables/chargers so that wasn't it. I went to a Samsung repair center and they suggested that... I have too many apps installed and that's causing the issue? Oooooook, granted this was just a rep and not someone doing the actual repairs.
Again my battery was low and I decided to reboot it and I can't start it again, very strange. If I get it working again it seems easy to duplicate if I goto Samsung again.
Called my credit card company and they have extended warranty on all purchases so i'm safe, the samsung store suggested to bring it in if happens again and they'll extend my warranty 3 months too.
Click to expand...
Click to collapse
Too many apps installed... how do these guys get the job in the first place, even as a rep?
It does sound hardware related, I'd probably use your 3 months ext warranty before it expires and the S7 finally commits suicide
Don't think knowledge is a requirement for these types of jobs, phone died again after a reboot and I can't start it anymore, going to the repair center after work.
It would seem not
Hopefully you get someone with at least some knowledge to help this time, likely you'll be needing a new motherboard / phone, unless it's something a bit less drastic like a dodge USB port
I thought it would be the usb port too but i tried using my wireless charger and the light on the charger was on meaning it was charging but it still wouldn't power up, i had it plugged in the whole day today and its completely dead.
Anyway it seems samsung warranty goes by build date + 1 year + 3 months leeway, unless you give them a receipt and then its just one year, so mine was built in feb 2016 so it has warranty till the end of may without a receipt.
Ah well, I suppose at least you get a new phone / board out of it, even thought it's a PITA RMAing your phone
Mine was manufactured 2016.08.16, just two weeks before I got it, so I guess that means November this year without a receipt, but pretty sure I still have the receipt anyway
They replaced the board and all is well now, first time any of my phones failed like this, and it had to be the pricey one.
They did it there and then for you? Was expecting a few days at least, nice job
Yea I've not had any failed phones to date either, hopefully not this one either
I dropped it off at 4 yesterday and it was ready by 7, i was a bit surprised by the speed too, seems they got all the parts in stock.
Can't complain about that service, makes you wonder if they have them in stock and can replace them in such a short time for a reason though... hope it's not a common fault