So, my S2 would occasionally overheat, then hotboot and just hang on the boot animation, so I would have to pull the battery.
This morning same thing happened so I pulled the battery, and I'm sure it burned out.
Main signs:
1: plugging into the wall, the phone just vibrates "on" every 3-4 seconds.
2: holding the power button to turn it on, it vibrates, then nothing.
3: holding volume buttons, it vibrates, flashes "samsung" then nothing.
4: i haven't tried download mode, but I wouldn't expect much.
I just wanna know if there's any way to access the internal memory, and try to pull off any files I can.
Luckily I did a nandroid backup yesterday, so I can get everything back to normal pretty quick, but getting everything I had saved would be nice.
Hi there cavemaneca...
From my experience with Samsung devices, I find that when they are in a state of very low charge their usability takes a ****. I have had this experience on 3 different Samsung devices, the Infuse (I997), the T-Mobile S989, and the (Vibrant?) Roommate's T-Mob Galaxy 4S phone. One particualr issue is that when the battery is in the red, and it is actively plugged into a charger, the touch screen becomes either completely non responsive at all, or the touchmove events get all corrupted in weird counter intuitive directions. This happens until the battery is around the yellow areas, somewhere like +15% or +20%.
I have also consistently encountered your specific issue, in which a Samsung phone, once drained dry, will not actually appear to be charging, but rather just give steady *buzz* *buzz* *buzz* for what seems to be an indefinite amount of time. This however, for myself, has always self corrected after some time. I suggest the following two parts to the solution:
1) Get a strong enough charger base plug thing. For lack of the appropriate lingo, I use either of the following:
This grey base charger from T-Mobile directly for androids with the extra usb port on board. Good charging rate...
OR
Your standard HTC charger base
2)Once you have gotten a strong charger connected directly to it., GO DO SOMETHING ELSE. I recommend Dark Knight Rises, Cabin In The Woods, possibly the new Todd Solondz film with Christopher Walken, or Ted. I would bet good money that when you return, your phone will have stopped vibing and will be nearly charged. It's happened to me on this phone way more often than I would care to admit...
Salutations!
99% sure your phone isn't bricked. Your phone vibrates and flashes the Samsung logo... It's not bricked. it might be a battery problem try a different battery or charger, i used a bad cable and it took forever for it to finally hold enough charge to boot up.
But yeah try getting into download mode... Connect into a computer holding +/- buttons, it should boot into it automatically.
Sent from my SGH-T989 using xda app-developers app
Whether you can go into download mode IS the sign if you are bricked or not. Though, it sounds like a battery issue.
Sent from the pink Unicorn from the Darkside.
Thanks for all of the replies!
This is my first Samsung device, I'm use to HTC devices that brick pretty easy.(had about 4 or so so far that bricked)
It turns out that out of the 2 micro-usb plugs I had on my desk, one wasn't plugged into the wall, so I thought it had been charging all night but it just ran it completely dead, coupled with the fact that it had frozen in a bootloop.
It took over an hour, but it's at least showing signs of life now (still says 0%). I guess my device just needed that day off...
Probably your charger, time to invest in a new one.
Sent from my SGH-T989 using xda app-developers app
It feels like it was yesterday that this was happening to me. Now if your phone boots up the logo and goes black to continue vobrating, your power button could be at fault.
Sent from my SGH-T989
Related
I have a stock Tmobile G2 that I have not rooted or done a thing too. I've been enjoying it just like it is.
Last night, I plugged it in at night and went to bed. This morning, the green LED was on saying it was fully charged, but it wouldn't power on? I finally pulled the battery and it powered on to the standard white HTC screen, but hung there for 5+ mins. I pulled the battery and again and I think the HTC screen came up again and hung again. After that battery pull, I could no longer get it to even power on.
Here's what I've noticed.
-After a battery pull and then plugging it in, I get an "orange" LED, but nothing happens. Can't power on, and it doesn't ever seem to turn green even after hours on the charger. When I remove the plug, the orange LED stays on and nothing happens.
- If I pull the battery and try to turn it on before plugging it , nothing happens, but in the same token, it won't show the orange LED if I plug it in.
The only thing different I did last night was that I used a Mini to Micro converter plug for the first time. I have a ton of Mini-USB plugs, so just ordered 2 of these. Could have been coincidence, but thought I would mention it.
My battery has been fine and has shown no issues of being bad, but wondering if they just crap out or something? The no charging LED after trying to turn it on is strange?
Any ideas?
Return it and call shenanigans?
That's really quite strange. Have you modded anything on the system that would affect it at all?
yeah, the hardware in your phone is simply broken. to make sure this is true, try doing a recovery. pull the battery, put it back in, hold the volume DOWN key, while hitting the power on button, use the volume rocker to go down to recovery, and then follow the instructions to recover the phone. but it sounds to me like water damage of some sort around the plug, or you pulled out the charger wrong and broke it. **this will remove all apps you have installed, but its better than having to wait for t-mo to send you a new one**
dietotherhythm said:
Return it and call shenanigans?
That's really quite strange. Have you modded anything on the system that would affect it at all?
Click to expand...
Click to collapse
Haven't touched a thing on this phone. I have an older G1 I've played with ROM's on and stuff, but I've left the G2 alone.
Only thing is standard apps from the market.
jenlow said:
yeah, the hardware in your phone is simply broken. to make sure this is true, try doing a recovery. pull the battery, put it back in, hold the volume DOWN key, while hitting the power on button, use the volume rocker to go down to recovery, and then follow the instructions to recover the phone. but it sounds to me like water damage of some sort around the plug, or you pulled out the charger wrong and broke it. **this will remove all apps you have installed, but its better than having to wait for t-mo to send you a new one**
Click to expand...
Click to collapse
Just tried the recovery, but nothing.
No water damage or anything. Phone has been well taken care of and looks new.
I guess its just a failure. Only had it a month or so. Guess I'll contact tmobile about a replacement.
These things happen, my original G1 died after about a week of use, though I would have expected that after a month you would be in the clear.
raitchison said:
These things happen, my original G1 died after about a week of use, though I would have expected that after a month you would be in the clear.
Click to expand...
Click to collapse
Yeah, kind of surprised myself. Electronics do fail though.
BlueLghtning said:
I have a stock Tmobile G2 that I have not rooted or done a thing too. I've been enjoying it just like it is.
Last night, I plugged it in at night and went to bed. This morning, the green LED was on saying it was fully charged, but it wouldn't power on? I finally pulled the battery and it powered on to the standard white HTC screen, but hung there for 5+ mins. I pulled the battery and again and I think the HTC screen came up again and hung again. After that battery pull, I could no longer get it to even power on.
Here's what I've noticed.
-After a battery pull and then plugging it in, I get an "orange" LED, but nothing happens. Can't power on, and it doesn't ever seem to turn green even after hours on the charger. When I remove the plug, the orange LED stays on and nothing happens.
- If I pull the battery and try to turn it on before plugging it , nothing happens, but in the same token, it won't show the orange LED if I plug it in.
The only thing different I did last night was that I used a Mini to Micro converter plug for the first time. I have a ton of Mini-USB plugs, so just ordered 2 of these. Could have been coincidence, but thought I would mention it.
My battery has been fine and has shown no issues of being bad, but wondering if they just crap out or something? The no charging LED after trying to turn it on is strange?
Any ideas?
Click to expand...
Click to collapse
I'm on my 4th G2. The screen kept going out on two of them and the other one, all the apps were force closing on me. I almost gave up on this phone and went to a nexus s but I love the quality of this phone as in it don't feel or look cheap. Also I would have missed my hardware keyboard for my fat fingers lol. I was not going to get a mytouch 4g. Wanted to get as stock vanilla android as I could.
Just send it back and get a new one. Hopefully the next one won't give you these problems.
Sent from my T-Mobile G2 using XDA App
Those are usually the signs of water damage or a fried battery
Sent from my HTC Vision using XDA App
Tmobile assisted me and all is well!
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
So here's the story.
It was last night. It was dark, and I proceeded to charge my phone. I didn't see where I was plugging in the adapter into the wall, so instead of having both adapters in the correct sockets, I had the right prong of the adapter into the left hole of the power bar socket, and the left prong of the adapter into nothing.
Of course, being dark, I didn't see, but it went in so I thought I plugged it in properly.
So my phone is "charging", and I proceeded to flash a new ROM (Android Overdrive). My battery at that time was at around 30%. So I went to recovery, did the regular full factory reset, and flashed it, and when it rebooted, it had the 4-coloured X boot animation playing, when I heard a funny, continuous, low electronic humming sound eminating from my phone and the screen started getting funky and turned a shade of purple. I quickly unplugged the usb, and proceeded to restart the phone.
Phone freezes at boot animation.
I went into bootloader, and successfully navigated to recovery. I proceeded to do a full wipe, and reflash the old rom.
It flashed successfully but I had the same problem of getting stuck on the bootanimation.
Now the phone won't turn on when I press the power button. When I plug it into the wall it shows the charging icon thing, then it turns off, then it turns back on, and repeats like that forever.
When I press the power button when it's plugged in the phone gets stuck at the charging battery screen (The screen freezes).
Also, when I plug my phone into my computer, my computer (windows 7) makes a disconnect sound, followed by three short beeps in quick succession that are at the same pitch as the last note of the two-note disconnect melody. It does this on repeat forever.
PS: I just managed to put the phone into bootloader mode and I am leaving it plugged in. I am going to see if it is still responsive after 30 minutes of just sitting there on the homepage of bootloader mode.
PPS: It was stable after 30 mins; I could still press up and down and select whatever i want. BUT as soon as I unplugged the USB, the device shut off. Is it the battery problem?
Does anyone know yet what's wrong with my phone?
A friend of mine had a similar problem... Never solved it, keep us updated mate...
Sounds like a battery problem. You might wanna get a replacement battery if you can. Word of advice. Never ever flash anything if your phone isn't fully charged or at a good battery percentage. Personal experience
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
Sounds like a battery problem. You might wanna get a replacement battery if you can. Word of advice. Never ever flash anything if your phone isn't fully charged or at a good battery percentage. Personal experience
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yes sir you are correct! I have a friend who also had a Gnex, and I swapped batteries and lo and behold, my phone works again! Now I don't have to drop $400 on a nexus 4 =D
So I woke up this morning and my phone was A-OK. Charged to 100% overnight, and I left it plugged in while getting ready for work. I came back to it 20 minutes later and it was really warm/borderline hot to the touch (through a case). The battery was down to 85% yet still plugged in. I then drove to the train station 5 minutes away and it went down to near 50%, still really warm/hot.
Streamed some music and watched some Netflix on the 90 minute ride, and the battery was down to 35%. At this point I turned the phone off because it was still hot.
Plugged it in to charge at the office, and got a blinking red light for about 10 seconds. It then went solid red and stayed that way until I unplugged it 4 hours later. The phone was still quite warm, but no longer hot. Hold down the power button... nothing. Plug it back in, same red light pattern. I got nervous at this point and hit up good old El Goog to see what could be wrong.
Found a lot of threads pointing to the One X suffering this fate, along with a few One's. Followed the advise of holding VolUp + VolDown + Power for 2 minutes. The phone got hot again. Unplugged the phone, removed the SIM, and held the buttons again. The phone had cooled off dramatically while doing this, to the point that it is now cold to the touch. Reinserted the SIM, and plugged it in again... no light at all this time.
From this point on, the various threads disagree on the next steps. Plugging it in to the computer yields no light, just like an wall charger. I don't have the HTC cord with me at work. I've tried a Nokia micro USB cable and a Sony wall charger. Other suggestions call for leaving the phone off (like I have a choice on that part) and unplugged for several hours. Others say to mash the Power button for 10-20 times and that may cause it to power on.
Any suggestions on how I should proceed with this? My phone is unlocked, so I'd love to avoid replacing it.
NotATreoFan said:
So I woke up this morning and my phone was A-OK. Charged to 100% overnight, and I left it plugged in while getting ready for work. I came back to it 20 minutes later and it was really warm/borderline hot to the touch (through a case). The battery was down to 85% yet still plugged in. I then drove to the train station 5 minutes away and it went down to near 50%, still really warm/hot.
Streamed some music and watched some Netflix on the 90 minute ride, and the battery was down to 35%. At this point I turned the phone off because it was still hot.
Plugged it in to charge at the office, and got a blinking red light for about 10 seconds. It then went solid red and stayed that way until I unplugged it 4 hours later. The phone was still quite warm, but no longer hot. Hold down the power button... nothing. Plug it back in, same red light pattern. I got nervous at this point and hit up good old El Goog to see what could be wrong.
Found a lot of threads pointing to the One X suffering this fate, along with a few One's. Followed the advise of holding VolUp + VolDown + Power for 2 minutes. The phone got hot again. Unplugged the phone, removed the SIM, and held the buttons again. The phone had cooled off dramatically while doing this, to the point that it is now cold to the touch. Reinserted the SIM, and plugged it in again... no light at all this time.
From this point on, the various threads disagree on the next steps. Plugging it in to the computer yields no light, just like an wall charger. I don't have the HTC cord with me at work. I've tried a Nokia micro USB cable and a Sony wall charger. Other suggestions call for leaving the phone off (like I have a choice on that part) and unplugged for several hours. Others say to mash the Power button for 10-20 times and that may cause it to power on.
Any suggestions on how I should proceed with this? My phone is unlocked, so I'd love to avoid replacing it.
Click to expand...
Click to collapse
Have you tried the bright light trick? Hold the phone under a bright light (really bright light, the brighter the better) and hold down the volume button + power for 15-20 seconds. That should get you into your bootloader. This will tell you whether or not its rom based, or phone based.
If you cant even get into your bootloader, it sounds like a hardware problem. If you can get into your bootloader but it will not boot to your rom, then its software.
Thats all I got for now. Sorry.
Seriously sounds like a battery/charging issue, gives all signs of a discharging battery. That would explain the heat build-up.
Was you using the charger that came with it? Or are you using a different charger? I once used my motorola cord to charge my phone and it felt like it was going to burst in to flames. I then got the HTC cord that came with the phone and it cooled down.
Sent from my HTC6500LVW using Tapatalk 2
No luck on the bright light trick. I tried holding just power, power + down, power + up, and power + both underneath a fairly bright fluorescent light.
Dark Jedi said:
Was you using the charger that came with it? Or are you using a different charger? I once used my motorola cord to charge my phone and it felt like it was going to burst in to flames. I then got the HTC cord that came with the phone and it cooled down.
Sent from my HTC6500LVW using Tapatalk 2
Click to expand...
Click to collapse
I don't have the OEM charger here, but I was using it at home to charge it. I'm hoping leaving it alone for another 4 hours will bring it back to life on the HTC cable.
NotATreoFan said:
No luck on the bright light trick. I tried holding just power, power + down, power + up, and power + both underneath a fairly bright fluorescent light.
Click to expand...
Click to collapse
Lets hope that it didnt turn on because the battery died. Hopefully the OEM HTC cable/charger will fix your issue.
If your battery is truly completely drained, it may take a few seconds for the light to finally come on... so dont freak out in the first 10 seconds.
Your battery could of went bad. Does your phone look like it has swelled anywhere from the battery expanding ?
Sent from my HTC6500LVW using Tapatalk 4
Red5 said:
Lets hope that it didnt turn on because the battery died. Hopefully the OEM HTC cable/charger will fix your issue.
If your battery is truly completely drained, it may take a few seconds for the light to finally come on... so dont freak out in the first 10 seconds.
Click to expand...
Click to collapse
I'm trying to remain calm until I get home. I haven't gotten a light in 30+ minutes of being connected to the Sony charger, but I'm chocking that up to it not being the HTC original.
Dark Jedi said:
Your battery could of went bad. Does your phone look like it has swelled anywhere from the battery expanding ?
Sent from my HTC6500LVW using Tapatalk 4
Click to expand...
Click to collapse
It's tough to properly gauge it with my eyes, but nothing looks off. If I press down on the center of the phone at the top, the it does not lift off the table. If that push from the center at the bottom, it does lift off ever so slightly. But I don't know if this is because of the camera location or what.
Called up Verizon just to make sure there's no other method that I didn't try, and they advised me to get a replacement. I've got a few days to try and get this thing working before I'll have to send it back and say goodbye to root.
Interestingly enough, they were sure to warn me about physical damage and being subject to a $299 charge if there is any damage. But they didn't make any mention about if the device is found to be unlocked.
Well the cooling down certainly could have been the battery finally being completely dead. Maybe stop in a Verizon store to try another battery? No chance a bad SIM card could cause this right?
kennyglass123 said:
Well the cooling down certainly could have been the battery finally being completely dead. Maybe stop in a Verizon store to try another battery? No chance a bad SIM card could cause this right?
Click to expand...
Click to collapse
Try another battery? You mean just pop off the back cover, take out the old battery and try a new one? You're one sick troll.
Red5 said:
Try another battery? You mean just pop off the back cover, take out the old battery and try a new one? You're one sick troll.
Click to expand...
Click to collapse
Yes..very devious!!! I don't know what I was thinking :silly:
kennyglass123 said:
Well the cooling down certainly could have been the battery finally being completely dead. Maybe stop in a Verizon store to try another battery? No chance a bad SIM card could cause this right?
Click to expand...
Click to collapse
I did remove the SIM before doing some of the steps as there were reports that a missing one will cause the phone to pop into recovery. I really hope I can get this one back to life so I don't have to wait for an S-Off exploit to root again.
Got home, plugged it in for several hours, no light. Looks to be quite dead.
Really sorry to hear this man.
I would keep it off 12-24 hours.
try it out.
also I have sent back MANY HTC Dev unlocked phones, they just flash the new software re-setting it back to S-ON, and stock. I don't think they really give a ****, esp if it's not an issue from say, S-OFF.
That's a pisser. My One has been rock solid. Sounds like a really weird issue. I doubt it's recoverable. I'd just go for the replacement. Generally even if it's unlocked they won't have any issue replacing it. In fact, here is Australia, retailers aren't allowed tor efuse warranty claims even if the device has been unlocked, rooted etc...
Perhaps put it into a bag and into the freezer for a few hours. That can sometimes resolve battery issues.
Did I read it correct that you were not able to go into the bootloader? (full Power off > vol down + power)?
If that's the case then you should head for a replacement.. if it is dead they probably wont be able to fire it up to check if its locked or not anyway
PG101 said:
Did I read it correct that you were not able to go into the bootloader? (full Power off > vol down + power)?
If that's the case then you should head for a replacement.. if it is dead they probably wont be able to fire it up to check if its locked or not anyway
Click to expand...
Click to collapse
Very good point, and by the time they do, the guys at the repair center can't physically go and find every rooted phone, then bring it to corporates attention, they get the phones, reflash the software fix the problems listed and out goes another returd. I mean refub, sorry.
First thing is first, I have been searching here and Google and have not found this exact problem.
I am running cm-11-20140719-NIGHTLY currently
Today my phone turned off on its own while connected to a car charger.
Here is what it is doing.
When the battery is connected the phone turns on and gets to the Samsung logo, then it goes black. No back light, nothing. If I pull the battery and re-insert it, it happens again. Once it goes black none of the buttons seem to be responsive (cannot force a reboot by holding the power button). Once it goes black if I connect it to a charger I get no LED indicating charge level.
If I try to boot into recovery I see the blue text and then it goes black.
If I try to boot into download mode I can get to the triangle screen if I am fast and then it goes black.
If I have a data USB cable connected and I connect the battery the phone does nothing, and will not respond to the power button, again no LED light indicating charge level.
If I have a charge only cable (wall outlet) connected and I connect the battery I see the battery charge icon for about 1 second and then the screen goes black. and the phone will not respond to any buttons.
I have duplicated all these things with 2 batteries both actual Samsung batteries, neither of the batteries is bubbled out at all.
I have tried leaving the battery out for several hours, but this did not help.
I have data on this phone that was not backed up so any suggestions I will try.
Thanks
daemorok said:
First thing is first, I have been searching here and Google and have not found this exact problem.
I am running cm-11-20140719-NIGHTLY currently
Today my phone turned off on its own while connected to a car charger.
Here is what it is doing.
When the battery is connected the phone turns on and gets to the Samsung logo, then it goes black. No back light, nothing. If I pull the battery and re-insert it, it happens again. Once it goes black none of the buttons seem to be responsive (cannot force a reboot by holding the power button). Once it goes black if I connect it to a charger I get no LED indicating charge level.
If I try to boot into recovery I see the blue text and then it goes black.
If I try to boot into download mode I can get to the triangle screen if I am fast and then it goes black.
If I have a data USB cable connected and I connect the battery the phone does nothing, and will not respond to the power button, again no LED light indicating charge level.
If I have a charge only cable (wall outlet) connected and I connect the battery I see the battery charge icon for about 1 second and then the screen goes black. and the phone will not respond to any buttons.
I have duplicated all these things with 2 batteries both actual Samsung batteries, neither of the batteries is bubbled out at all.
I have tried leaving the battery out for several hours, but this did not help.
I have data on this phone that was not backed up so any suggestions I will try.
Thanks
Click to expand...
Click to collapse
Return to stock with Odin to see if the problem goes away. If not, report back and we will go from there.
The Sickness said:
Return to stock with Odin to see if the problem goes away. If not, report back and we will go from there.
Click to expand...
Click to collapse
I would if I could get it into download mode... The screen will not stay on for more than 5 seconds and ODIN never sees the phone.
Here's a thread talking about that issue. I'm afraid it sounds like your display is dead:
http://forum.xda-developers.com/showthread.php?t=2267827
Sent from my SGH-M919 using XDA Premium 4 mobile app
I had this problem before and I was freaking out, but it was just the cord I used when trying to connect it, but yours sounds like an overload problem, maybe from your car charger if it plugs into the car lighter socket. My buddy has a super recharger that hooks into his lighter socket, and while it may charge fast, it might have jolted your phone, or maybe you had it over clocked in your rom? Or was it a recent occurrence or did it happen as soon as you installed the rom? Because this happens on a bad flash sometimes, if your Wi-Fi connection is shaky or far off, you could get a bad download and it will royally harm your time having to mess with it.
Sent from my GT-I9505G using XDA Free mobile app
Android_Monsters said:
Here's a thread talking about that issue. I'm afraid it sounds like your display is dead:
http://forum.xda-developers.com/showthread.php?t=2267827
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If it was just the screen wouldn't I still be able to get into download mode?
NinjaTale said:
I had this problem before and I was freaking out, but it was just the cord I used when trying to connect it, but yours sounds like an overload problem, maybe from your car charger if it plugs into the car lighter socket. My buddy has a super recharger that hooks into his lighter socket, and while it may charge fast, it might have jolted your phone, or maybe you had it over clocked in your rom? Or was it a recent occurrence or did it happen as soon as you installed the rom? Because this happens on a bad flash sometimes, if your Wi-Fi connection is shaky or far off, you could get a bad download and it will royally harm your time having to mess with it.
Sent from my GT-I9505G using XDA Free mobile app
Click to expand...
Click to collapse
I had flashed the night before and it ran fine all night and all morning, then it just shut down. The car charger I use is not a super charger, but it is also not a Samsung charger. I was not overclocked and my wifi is not shaky usually.
Seems like I am screwed either way.
daemorok said:
First thing is first, I have been searching here and Google and have not found this exact problem.
I am running cm-11-20140719-NIGHTLY currently
Today my phone turned off on its own while connected to a car charger.
Here is what it is doing.
When the battery is connected the phone turns on and gets to the Samsung logo, then it goes black. No back light, nothing. If I pull the battery and re-insert it, it happens again. Once it goes black none of the buttons seem to be responsive (cannot force a reboot by holding the power button). Once it goes black if I connect it to a charger I get no LED indicating charge level.
If I try to boot into recovery I see the blue text and then it goes black.
If I try to boot into download mode I can get to the triangle screen if I am fast and then it goes black.
If I have a data USB cable connected and I connect the battery the phone does nothing, and will not respond to the power button, again no LED light indicating charge level.
If I have a charge only cable (wall outlet) connected and I connect the battery I see the battery charge icon for about 1 second and then the screen goes black. and the phone will not respond to any buttons.
I have duplicated all these things with 2 batteries both actual Samsung batteries, neither of the batteries is bubbled out at all.
I have tried leaving the battery out for several hours, but this did not help.
I have data on this phone that was not backed up so any suggestions I will try.
Thanks
Click to expand...
Click to collapse
This blows, I just had the Same Exact thing happen last night, word for word.
Although I'm on a stock Rom that's rooted.
Phone was in my pocket and it vibrated as it restarted on its own. Pulled it out of my pocket, waited for it to fully start up, then I could use it.
However, it rebooted 2 minutes later and has Never come back yet.
I wish there was some sure fire way to verify if its the screen that went bad or the logic board. The mere fact the screen shows the Galaxy S4 logo, or Download Mode for a few seconds before shutting off seems weird if the screen was in fact bad.... =(
jamesvtw said:
This blows, I just had the Same Exact thing happen last night, word for word.
Although I'm on a stock Rom that's rooted.
Phone was in my pocket and it vibrated as it restarted on its own. Pulled it out of my pocket, waited for it to fully start up, then I could use it.
However, it rebooted 2 minutes later and has Never come back yet.
I wish there was some sure fire way to verify if its the screen that went bad or the logic board. The mere fact the screen shows the Galaxy S4 logo, or Download Mode for a few seconds before shutting off seems weird if the screen was in fact bad.... =(
Click to expand...
Click to collapse
Check your power button, it could be stuck.
serio22 said:
Check your power button, it could be stuck.
Click to expand...
Click to collapse
You were correct! Had to mess with that button a bit to get to work properly, but its still an issue. One to many power button presses and the issue returns.
I have tested the phone without the exterior power button only using the logic board button and it did that same thing. Am I correct to assume that the fault is the actual button on the logic board? So new logic board to fix this? =(
Why so many presses of the power button?
Pp.