2 week old edge just completely frozen - T-Mobile Samsung Galaxy S6 Edge

Went to use the phone (was charging and about 80%) and nothing works.
Screen won't come on, only sign that anything is working is the solid red LED battery light (which should be flashing if low battery?).
Tried the volume down/power button thing, holding for up to a minute. Once in every few tries I'll either get the boot screen (Samsung Galaxy S6 text) then black screen and nothing, or I'll get the battery charging image (showing zero battery) for a few seconds then nothing. All the while the red LED stays solid.
Tried removing the Sim card and holding down volume/power but same thing. Tried leaving on charger for a few hours but nothing changes.
Phone is completely T-Mobile stock, no root, no custom recovery etc (it's my girls phone and she likes everything stock).
Any ideas? Is this likely a complete failure? I can't imagine I'll be able to use Odin to fish sick ROM if I can't get to download mode - I guess this was my last idea to try and bring this back to life.

get it replaced; sounds like its defective

wase4711 said:
get it replaced; sounds like its defective
Click to expand...
Click to collapse
Yup. Replacement on its way. Can't believe that it could get so borked! Never had a phone I couldn't fix.
Thanks.

considering how many millions of these things they shipped out so quickly, there are bound to be defects..
always better to replace it when its under warranty, then to mess around with it yourself

Yeah. Only downside is that there's a chance I'll get a refurbished phone, which I'm extremely unhappy about. If T-Mobile send a refurb then I'll use the option to send back to Samsung who will actually repair the phone and send it back..... I do not want to go thru putting that screen protector on again.

Using the XDA SEARCH option here, ony nine (9) entries existed for "Galaxy s6" "screen frozen".
A "kind" moderator closed the one thread that had the same problem as me, referring them to a thread where there was no such topic.
Just happened to my S6, a week old, Australian stock, not affiliated with any ISP.
Third time now. Waiting for battery to drain completely ... again. Then recharge a little. But this time, I'll try to wipe the ROM & re-install the original somehow.
It happened jut after it auto-updated OTA to Android 5.1.1.
It only has Playstore apps on it, & generally runs Nova. But error happens with other launchers as well.

Related

Screen Wont turn on!!! Help!

My evo's screen started flickering earlier and then went completely off. I pulled the battery and the phone comes on, button lights work, i hear sound, i get calls but the screen wont turn on at all. Is there any way to fix this i am not under sprint TEP warranty and would really like to solve this issue asap.
i flashed cm7 7.0.2 this morning if that information helps. anyone?? PLEASE?!!!
Try taking out the battery, putting it back in and hold Volume down and power, see if it boots into recovery.
Nope. wont even boot into recovery. screen is completely unresponsive. any other suggestions?? i just called sprint and placed TEP on my account. when can i take it in since it was just placed on my account today??
You can take it in now, shouldn't matter. The only requirement they have is you be in the first 30 days of the device. I have even seen people in sprint stores suggest adding it right there to get a new phone and then telling the customer to call later and have it removed.
sent from my locked EVO via tapatalk
i actually got it to reboot in rcovery. (screen didnt turn on but i can read out the menus under a very bright light) i wiped EVERYTHING except the sdcard and now the phone wont turn on at all. the charging light wont even come on when connected to the charger. does this have to do me wiping the battery stats??
wow. threads like this annoy me. ROOTING YOUR PHONE HAS NOTHING to do with a hardware failure. if the phone is less than 1 year old. then it is covered under the warranty. you do NOT HAVE to pay a damn dime. don't let them tell you that. contact HTC directly and inform them that your backlight on the evo has failed. Let them know even when you restart it, the screen doesn't light up how it should. If they can't see the screen to see root, then all good. lol. but the fact is that root can't cause that issue. HOWEVER, SADLY. you won't have root again until they release the unlocked bootloader. sorry!
Btw, why the hell would you wipe the phone? WHY WOULD you wipe everything? lol. wow. take the battery out and charge it in a third party charging unit out of the phone. What is with people and wiping the battery stats? does ANYONE EVEN KNOW WHAT THAT MEANS!?
Wipe ONLY IF you are sending it back to HTC so people don't get your personal information. and take the SDCard out and back it up and format it and put it back into the phone.
Bro chill the **** out will ya??? thanks for the 1st paragraph but **** u for the second. Comments like yours annoy the **** out of me, helpful with a bit of prick on the side. Anyway it was a defective battery causing the issue. I went to sprint ( almost got hustled by the technician who claimed my motherboard was damaged) purchased a new battery and voila!

CDMA galaxy nexus - unresponsive to touch

Hello everyone,
Basically went to unlock my phone today and touch screen is not responding, however the hardware buttons work fine. Now i've done some research and found other posts of people with the same problem, however their touchscreen problems seem to be fixed(temporarily, at least) with a battery pull.. mine however is still unresponsive after half a day and multiple battery pulls.
Id rather not have to send in for certified to replace an otherwise perfectly working phone.
Any ideas/suggestions would be greatly appreciated!
bigdeezer20 said:
Hello everyone,
Basically went to unlock my phone today and touch screen is not responding, however the hardware buttons work fine. Now i've done some research and found other posts of people with the same problem, however their touchscreen problems seem to be fixed(temporarily, at least) with a battery pull.. mine however is still unresponsive after half a day and multiple battery pulls.
Id rather not have to send in for certified to replace an otherwise perfectly working phone.
Any ideas/suggestions would be greatly appreciated!
Click to expand...
Click to collapse
are u undervolting?
Nope, sorry forgot to say. Completely stock never unlocked or rooted.
Also i tried getting into recovery to try and do a factory reset but when i select recovery i just get the android on his back with the red triangle..
so instead i just went through the steps and unlocked the bootloader and booted up (in order to give me the factory reset without having to touch the screen)
It unlocked and booted up fine but still no response..
No new recent app installed and never had this happen before.
Mine did this after a few days of owning it, and luckily the store took it back and swapped it out with a perfectly working unit. Is yours within a few weeks of purchase?
Figured this out randomly. Remove battery cover. With phone turned on, press on the area to the to the left of the camera lens until the screen is responsive. My screen becomes unresponsive when the phone is dropped and this fixes it.
dailong said:
Figured this out randomly. Remove battery cover. With phone turned on, press on the area to the to the left of the camera lens until the screen is responsive. My screen becomes unresponsive when the phone is dropped and this fixes it.
Click to expand...
Click to collapse
hrmm this does not seem to fix either. I also have never dropped my phone, although this seems to be worrisome if the issue is hardware related.
@ tmellen i purchased the phone from amazon and am a few days past my return date :-/
Guess ill just give them a call and hope for the best. Thanks for the ideas everyone.
(update) called amazon and they are sending me a brand new phone.
Knowing this i thought i'd try dailong's method again only this time i was quite a bit more "rough" with pressing down on that area, and it actually worked!
Ill still be taking the new phone once it gets here but for anyone who is having this problem there's a sweet spot on the left edge of the phone towards the top (looking at it with the back cover off) there should be a circle shape. press on that area really hard and it should fix.. weird
Experienced the same on my GSM version a few minutes ago. I had to call my mobile to get it to respond. After that it worked again as normal. I'll see if I get this issue again in the next few days. Hope it's just random
Had the same happen earlier to mine and I was on AOKP. I've had this happen to other phone before, shouldn't be a a cause for alarm unless it happens very frequently. Btw, next time it happens to me I'll give that left side of the camera trick a try.
mine got fixed by removing battery.

[Q] Possible water damage, Now capacitive buttons showing as screen touches.

Okay, so when I press Back and Menu they show up as button presses on the screen, not actions. I can verify this with visual screen touches in Development settings. What do?
I guess there are two possible reasons. Last thursday my boss and I got back to the shop after a day of jobs and it was pouring, like torrential. Like the storms of two months saved up. We got ready to get out of the car. he didn't. Locked the doors. I was in the rain for at least a minute with nothing to shield the phone with in my pocket. This morning he came into the office and startled me, causing me to drop my phone. Since this morning, after the drop, the buttons don't work for back and menu. Quick button/camera works, volume, power. I guess the buttons work but they show up as presses, not actions. I am using the unofficial Cyanogenmod 10.2 and this morning I was using 9/13. The issues happened, I upgraded to 9/15 or 16, the recent one. Still persisted. all day it goes crazy. Sometimes they both act like they're being pressed insanely fast, like both of them a dozen times a second. When it happens I have to pull the battery because it is impossible to navigate the power menu. The buttons work, they are receptive when I longpress them, they just don't work correctly.
I wiped all but internal data and installed the 9/16 Unoffical CM 10.2 rom again with the modem and still the problem persists. In TWRP they don't respond but I can't remember if they are working in TWRP or not.
I'd love if someone could give me any advice. Thanks for reading.
Well when having issues with a phone flashing custom roms is the last thing you should do for 2 reasons.
1. its NOT going to hurt to test it by flashing it back to stock. Instead of keep flashing CM on it.
2. If something happens to make the phones buttons complelty act up you WOULD NOT be able to return to stock and the stores would clearly see you had something done or flashed on it and try to blame it on that (Even though its most likely not)
Pull the battery door off the phone look to the right of the camera do you see a tiny hole and something White or red? If its red then your warranty is void as it has got wet. But if its white just call up AT&T and have a replacement sent. (Assuming you have the E980 att version and on AT&T) You did not say what model nor carrier.
hyelton said:
Well when having issues with a phone flashing custom roms is the last thing you should do for 2 reasons.
1. its NOT going to hurt to test it by flashing it back to stock. Instead of keep flashing CM on it.
2. If something happens to make the phones buttons complelty act up you WOULD NOT be able to return to stock and the stores would clearly see you had something done or flashed on it and try to blame it on that (Even though its most likely not)
Pull the battery door off the phone look to the right of the camera do you see a tiny hole and something White or red? If its red then your warranty is void as it has got wet. But if its white just call up AT&T and have a replacement sent. (Assuming you have the E980 att version and on AT&T) You did not say what model nor carrier.
Click to expand...
Click to collapse
Sorry, you're right; I didn't specify. I have an AT&T e980, less than a month old. No water damage, it is still white in a little white circle then right next to it in a little square placed inside a clear circle, white as well. I will begin the process tomorrow of reversing it to stock and unrooting it. I didn't get your post in time and flashed to Paranoid Android because of tablet UI, I can get onscreen controls as well as PIE to choose from, in case I had to live with it. Thanks for your info and advice.

Black Screen, phone still works?

Hello XDA members, this time I'm writing to all of you to tell you something that happened to my Optimus G E987 from Claro Argentina, also, to ask you something related to the topic.
I bought this phone about 4-5 months ago, and I have taken really good care of it, without using any film protection or case, it was working perfect and with not a single scratch on it, not even a little hit.
But then, some days ago, I decided to "protect it" a little bit, so I got one of this:
htt-p://i[dot]imgur[dot]com/YtgK1aS[dot]jpg
htt-p://i[dot]imgur.com/la1kI5e[dot]jpg
(Sorry, I'm new to this forum so it won't let me post links)
I used it like.. dunno, 3-4 days. One night, my phone was on 53% battery, to lazy to charge it so I just let it like that. Next day I gave it some use, so it dropped to 33% of battery life, I had to go work so I turned it off. When I finished, I tried to turn it on again, but nothing happened, tried more times and nothing, then I noticed I liiiitle light in the screen, the phone was turned on, but with REALLY low visibility, almost everything black but with a little of sight.
I though it was just a battery problem, so I charged it, but to my surprise, nothing happened, well something did happen, the little bit of sight that I had just went full black with no visibility. I noticed that the touch screen and buttons actually worked, I could "easily" navigate through the phone by just using it as normal, but without seeing (you can do this by just knowing your phone a bit).
And that's the story, basically, after using that case, the phone "casually" stopped working properly, all I got was a functionally phone with a black screen.
I managed to connect it to my pc through wifi and launched Android Screen Cast, to see what was happening on my phone. The glow was at 100% (I tried changing it) and everything seemed normal.
If you don't want to read, here is a TL;DR
>Bought Magnetic* Flip Stand Leather Wallet Case for Optimus G
>Some days after, phone screen stopped working (phone was still normally working, just with a full black screen)
About the Magnetic thing.. is there any possibility that this was the problem? the magnetic thing?
Btw, I sent the phone to tech service because it was still on warranty and they have me a new one, now I'm scared of putting it again in the leather case I bought, I don't want this to happen again.
Something to comment? hope you can give me some advice, thanks in advance!
Also having similar problems as you. Somehow, i am quite sure its the stock rom causing the problem.
Had the very same issue few weeks ago, had to send the phone back to LG ( who replaced the motherboard :/).
I was also on stock rom, had root and unlock bootloader (of course I clean all that **** before sending it back).
For my part, I was unable to go to recovery and download mode was quit impossible to access (may be my finger fault )
BUT! some time if I let the phone off for a moment or spam the power key, the backlight turn back on until I power down the phone, so it's could be a software issue ...
Anyway, an other info, when the backlight was off, if i tried to change backlight level i was getting a error message about overeating or something like that...

[Q] Tab Pro 12.2: Screen and Button Issues

I just got this tablet (to replace the garbage SGH-I467) a few days ago (Thu., May 15th). For the first couple of days it worked like a dream. However, the last 4 nights/3 days, I have been encountering some strange issues. What I will do here is describe the issues I've been having, what I have done in attempts to fix them, list some of the things I think may have caused it, and include any additional info/questions.
Before all that though, I would like to mention that I am not a developer, but I am a bit 'tech savvy' and am more familiar with/knowledgeable of technology than the average user. Also, I have spoken with Samsung tech support and even had the support guy access my Tab Pro 12.2 remotely (I will explain what I learned from that below). So, without further ado (I apologize in advance for the long winded nature of this post, but I want detailed):
The Issues:
1) Screen "flickering"—By flickering I mean that it is shutting off and turning on rather rapidly and sporadically, though inconsistently.
I first encountered the problem 3 days ago (the 18th).
Four nights ago (the 17th), before going to bed, I plugged the device into the same outlet I have used for all my mobile devices, when I woke up (on the 18th) the screen was doing exactly what I described. I hit the home button a few times and it stopped.
That night (the 18th) I plugged it back in to the usual spot before going to bed. The next morning (yesterday, the 19th), the screen was "flickering" again. I tried to press the home key a few times, as well as both the soft keys, nothing. In between "flickers" you can see the lock screen, where I have to enter a pin, but even while visible I can't type anything. So this time, to try to solve the problem, I held the power button + volume up to get to recovery and wiped the cache partition, rebooted the device, and viola, it worked again. Thinking that I may have to factory reset the device if the problem persists, I used Kies to backup all my data. I used the tablet the rest of the day, even plugged it in (in a different outlet than the one next to my bed) for a while and had no issues.
Last night (the 19th) I did pretty much the same thing, but this time, thinking that it might be an issue with the device getting too much power (the Quick Start Guide says: "Note: Connecting the travel adapter improperly may cause serious damage to the device."), I used a travel adapter from one of my other, USB 2.0 devices (the only difference between the adapters is the output: 2.0 = 5.0V—2.0A vs. 3.0 = 5.3V—2.0A, and output was specifically what I was concerned with). This morning (the 20th) the problem has returned, but now includes my second issue: the hard home button and both soft keys, back and recent apps, no longer function. So I immediately tried to wipe the cache partition and reboot, but this time it didn't work. Thankfully I had anticipated this yesterday and had that Kies backup, so I wiped the entire device back to factory settings. But alas, it was unsuccessful and the problem persists, including the loss of button functionality, with the exception of the power and volume buttons.
It is important to note that when I first got the Tab Pro 12.2 and set up the lock screen, I used the option that delays the actual locking of the device 10 minutes after screen timeout, but set it so that if I lock the screen with the power button it ISN'T delayed and immediately locks. That being said, a couple of times when the "flickering" stopped long enough to momentarily use the device, I was able to enter my pin and unlock. But when the screen starts flickering again, it locks the device, so the power button must be affected as well. Though since the first factory reset of the device, I haven't set up a pin. I have done several factory resets and none of them have worked. The best result has simply been limited (no back, recent apps or home key) and momentary functionality. I tried using Kies to do emergency firmware recovery, but every time I click the option it disconnects the device.
When Samsung tech support remotely accessed by device (I used one of the momentary functionality windows to download the required application) the agent was able to utilized soft and home key functionality, even though I couldn't. This tells me that it was hardware related, not related to UI/software.
So there are a couple of things I think may have caused/contributed to the problem:
The first, which I vaguely touched on above, is the power issue. Perhaps I have shorted the device out somehow. The outlet I use to charge things while I'm sleeping is on the wall behind my bed, so I have to use a common extension cord, one that has 3 outlets at the end. I have a light plugged into that and in the past have charged both my SGH-I467 (AT&T Note 8.0) and my SGH-I747 (AT&T S4 Active) with that cord and outlet. That is the only place I have charged the SM-T900 overnight, but none of the other power sources I have used have caused these issues.
The second possibility is a virus some sort. I have never used the Samsung app store on any of my other devices, but in order to update the Hancom Office suite I had to. Since I had an enjoyable time using it to that end, I decided to see what else I could find on Samsung's store. I downloaded a couple of things (the "Official Captain America game" and a couple wallpaper/theme apps) and was looking around the store to see if there was anything else I wanted to download. I found several apps that had reviews claiming they were trojans, so I immediately checked the reviews for the apps I had downloaded, but none of them had similar reviews. However, that does not mean they didn't have viruses.
So, what do the resident Android gurus of XDA think about these issues?
I tried searching all over the forums and elsewhere online for people having the same issues, but couldn't find anything. Have any of you ever encountered something similar to this?
Until recently, I hadn't ever heard of anyone getting a virus on an Android device. Are they common? What is the nature of Android viruses?
If these issues do have something to do with overcharging/shorting the device, how can I mitigate that problem? Tonight when I charge the tablet, instead of using the USB 3.0 charging cable, I am going to try just using the 2.0 cable. As I understand it, that can be done by simply plugging it into the right side of the port. Hopefully that will stop exacerbating the problem.
Again, I apologize for such a long winded post. I would like to thank you all in advance. If ever I have problems with an Android, you guys are the ones to ask!
*UPDATE* Before I started typing this I was attempting to run the Kies 'Firmware Upgrade and Initialization', as opposed to 'Emergency Firmware Recovery', to see if that too would disconnect the device. Unfortunately it said that my device needed to be charged first. So I shut it down and plugged it into a surge protected strip and began typing this post. Occasionally I would go over an check the charge. While it was shut down and charging I was able to use the home key to bring up the green battery. Once the charge looked like it was about 75% complete I turned it back on and lo and behold, the "flickering" issue looks resolved and so does the button issue. I can go back, enter the recent apps and task manager, and use the home key functions. For how long this will last, however, is unknown. I guess we'll see in the morning. I'll post what happens tomorrow.
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
RE: Case?
dodo99x said:
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am not using a case or cover at all...
same issues here
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
VeinkWiles said:
So, what do the resident Android gurus of XDA think about these issues?
Click to expand...
Click to collapse
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Mike Austin said:
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Click to expand...
Click to collapse
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
VeinkWiles said:
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
Click to expand...
Click to collapse
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Re: developer settings; display touches
dottat said:
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Damn! That's an outstanding idea! The only downside is that last night I sent the tablet to Samsung's repair department, so I can't test that out. But once I get it back, if the problem persists I will definitely be doing that first. Thanks for the advice dottat.
Fw:Re: developer settings; display touches
mikegbg said:
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
Click to expand...
Click to collapse
Hey dude, check out dottat's reply. He's got a really good idea that may shed some light on the source of the problem. Unfortunately, I can't try it out. If you do it, let me know how it goes. Maybe you can take some screenshots? Either way, hopefully you can get something out of it.

Categories

Resources