Related
My wife was using the KF which has a cm9 build on it. I forgot to tell her how to properly shut it down instead of the normal popup menu option. It died and wont charge. I do not have the oem charger as i got the device in a trade deal. I have tried the 2 charger blocks i have at the house and even the car charger that has revived a phone before that wouldnt charge when completly dead. If there is anyone that will loan one to me or even let me rent one that would be stellar. If you are in virginia, near fort lee that would be even better. I will dance at your wedding!!!
Courtesy of these thumbs to your face
what bootloader do you have?
bzmotoninja83 said:
My wife was using the KF which has a cm9 build on it. I forgot to tell her how to properly shut it down instead of the normal popup menu option. It died and wont charge. I do not have the oem charger as i got the device in a trade deal. I have tried the 2 charger blocks i have at the house and even the car charger that has revived a phone before that wouldnt charge when completly dead. If there is anyone that will loan one to me or even let me rent one that would be stellar. If you are in virginia, near fort lee that would be even better. I will dance at your wedding!!!
Courtesy of these thumbs to your face
Click to expand...
Click to collapse
In the device's present state, the OEM charger would probably be less of a help than you might think. Your best bet right now is FFF 1.4a and the power out of the USB port on your computer...
http://forum.xda-developers.com/showthread.php?t=1623244
As far as bootloadwr i dunno. It was FFF oackage or something. Its hooked to the computer now. Dropped it off at the house during lunch. Will check on it after work.......
Courtesy of these thumbs to your face
Have you tried holding the power button for 20 seconds while you plug it in to charge?
Same thing happened to me once and a soft reset got it back up and running.
I have not but i should be home about 10:45 est. And will try that too. Its plugged into the pc right now
Courtesy of these thumbs to your face
eaglet1223 said:
Have you tried holding the power button for 20 seconds while you plug it in to charge?
Same thing happened to me once and a soft reset got it back up and running.
Click to expand...
Click to collapse
Worked perfect. Left it plugged into the PC. Came home and tried to power it on but no joy. Plugged it into the ac charfer and held the power button for 20 secs and booted into TWRP...... Rebooted system and the battery is at 100%....... If i could press thanks more than once i would.
Courtesy of these thumbs to your face
Just a suggestion if you havent upgrade your bootloader http://forum.xda-developers.com/showthread.php?t=1500935 that method or this one http://forum.xda-developers.com/showthread.php?t=1632375 your battery situation could have been far worse http://forum.xda-developers.com/showthread.php?t=1623244
Cool beans y'all. Thanks also to the one above me as I didn't know the fff and whatnot has been updated.....
MAKE IT SO NUMBER 1.
I am glad I could help
Sent from my ADR6425LVW using xda premium
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?
Hello everyone.
I have been using Tasks ROM for a while now. Last night my phone had a random reboot and other than that, no troubles.
Well about 20 minutes ago, my phone just turned off and will NOT come back on at all. I have done nothing different, cant get in to get a logcat or lastkmsg. It will not even boot up to the samsung screen.
It will vibrate when I plug it in or take out the battery and reput it in.
The only response I am getting is taking everything out (batter/sim/sd) and plugging it into my comp. The response is a Red light in the notification LED and a short vibrate, then nothing.
I get a Samsung logo if I just pull battery and reinsert.
Any help would be greatly appreciated.
Thanks
So you can't get into CWM or TWRP? And what Galaxy S3 Variant are you using?
axel4401 said:
Hello everyone.
I have been using Tasks ROM for a while now. Last night my phone had a random reboot and other than that, no troubles.
Well about 20 minutes ago, my phone just turned off and will NOT come back on at all. I have done nothing different, cant get in to get a logcat or lastkmsg. It will not even boot up to the samsung screen.
It will vibrate when I plug it in or take out the battery and reput it in.
The only response I am getting is taking everything out (batter/sim/sd) and plugging it into my comp. The response is a Red light in the notification LED and a short vibrate, then nothing.
I get a Samsung logo if I just pull battery and reinsert.
Any help would be greatly appreciated.
Thanks[/QUOTE
Ii it possible you may have a bad battery? How new is it?(not that age of it matters) Also, do you have a case on the phone? Check to make sure the power button is not stuck. If you can get to boot logo, then its not dead-dead. If you've had your phone for awhile, double check the battery terminals are not oxidized. Unlikley, but worth checking and maybe check battery wih voltage meter if you have access to one. Then charge it overnight and check it again. One last thing to try is plug it in with the battery out and see if that does anything. Have you flashed anything lately? Modem? Scripts?
Click to expand...
Click to collapse
I have taken the battery out and plugged the phone straight into the computer and all that i get is a red light where the notification light is and then it disappears.
As for age, its a little over a year old.
I wasnt doing any flashing at the time, it just went kaput right after a phone call.
I had a mophie case on it, but not right now. I guess ill take it a part when i can and throw som alcohol on the battery button to see if it loosens it up. But other than that, I'm at a loss.
Not trying to pay $80 for a craigslister either.
Bubba Fett said:
axel4401 said:
Hello everyone.
I have been using Tasks ROM for a while now. Last night my phone had a random reboot and other than that, no troubles.
Well about 20 minutes ago, my phone just turned off and will NOT come back on at all. I have done nothing different, cant get in to get a logcat or lastkmsg. It will not even boot up to the samsung screen.
It will vibrate when I plug it in or take out the battery and reput it in.
The only response I am getting is taking everything out (batter/sim/sd) and plugging it into my comp. The response is a Red light in the notification LED and a short vibrate, then nothing.
I get a Samsung logo if I just pull battery and reinsert.
Any help would be greatly appreciated.
Thanks[/QUOTE
Ii it possible you may have a bad battery? How new is it?(not that age of it matters) Also, do you have a case on the phone? Check to make sure the power button is not stuck. If you can get to boot logo, then its not dead-dead. If you've had your phone for awhile, double check the battery terminals are not oxidized. Unlikley, but worth checking and maybe check battery wih voltage meter if you have access to one. Then charge it overnight and check it again. One last thing to try is plug it in with the battery out and see if that does anything. Have you flashed anything lately? Modem? Scripts?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Man, I don't know. Sounded like a charging issue at first, but looking I'm not so sure now. Anything stuck in your power slot? Maybe try leaving battery out overnight and see if it clears anything. If it starts to boot I would go right to recovery and try flashing something. I would be concernedabout going straight to download mode and using oOdin cause of it does during the flash that is really bad...
Can you get into download mode? Pull battery plug in USB and hold volume down and home buttons I think... when you plug USB in to computer does Odin recognize it at all?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I just started having the same issue. I have a an ATT S3 running the newest Hyperdrive. Mine wasnt doing a random reset, but it seemed like it has been turning itself off. Totally intermittent, i couldnt pinpoint the cause.
Then just today when i went to see if i had any messages and the phone was off again (i had about a 60-75% charge) I hit the power button a few times and now i am getting the symptoms described above.
When i try to go into TWRP, i get the blue text at the top left of the screen, sometimes i make it to the first hyperdrive screen, then it goes black.
When I go to download I can get to the hit up or down screen, i hit up to go into download, i get to the next screen then it goes black again.
I did leave the battery out for about 15minutes and no dice. I even tried to leave it on the charger thinking i lost all charge or something.
I am just a mere user, but i have always been able to tinker around enough not to bother the devs and get my way out of these situations, but I think i am stuck. Anyone have any ideas?
Thank you!
nightwulfss said:
I just started having the same issue. I have a an ATT S3 running the newest Hyperdrive. Mine wasnt doing a random reset, but it seemed like it has been turning itself off. Totally intermittent, i couldnt pinpoint the cause.
Then just today when i went to see if i had any messages and the phone was off again (i had about a 60-75% charge) I hit the power button a few times and now i am getting the symptoms described above.
When i try to go into TWRP, i get the blue text at the top left of the screen, sometimes i make it to the first hyperdrive screen, then it goes black.
When I go to download I can get to the hit up or down screen, i hit up to go into download, i get to the next screen then it goes black again.
I did leave the battery out for about 15minutes and no dice. I even tried to leave it on the charger thinking i lost all charge or something.
I am just a mere user, but i have always been able to tinker around enough not to bother the devs and get my way out of these situations, but I think i am stuck. Anyone have any ideas?
Thank you!
Click to expand...
Click to collapse
Maybe a stuck power button? Try cleaning it out a little. .. sounds like it's rebooting itself.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Maybe a stuck power button? Try cleaning it out a little. .. sounds like it's rebooting itself.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I am trying that, it doesn't seem like there is anything in there, but you never know.
If the power button was stuck on, wouldn't the phone keep trying to restart? Or no?
nightwulfss said:
I am trying that, it doesn't seem like there is anything in there, but you never know.
If the power button was stuck on, wouldn't the phone keep trying to restart? Or no?
Click to expand...
Click to collapse
I believe so, unless you pull the battery. In fact pull battery plug into usb and go into down load mode and see if it restarts. Or go into recovery without holding power button, and if you can then that means the power button is stuck on.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
I believe so, unless you pull the battery. In fact pull battery plug into usb and go into down load mode and see if it restarts. Or go into recovery without holding power button, and if you can then that means the power button is stuck on.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have tried that as well. Whenever it goes into download mode the screen goes black after a couple of seconds. And it doesn't boot into recovery as well since it seems to go dead too quick.
I mainly just want to recover my pictures at this point. I am leaving the battery out of the phone for the day and see if that makes a difference this evening.
I am out of ideas, lol
nightwulfss said:
I have tried that as well. Whenever it goes into download mode the screen goes black after a couple of seconds. And it doesn't boot into recovery as well since it seems to go dead too quick.
I mainly just want to recover my pictures at this point. I am leaving the battery out of the phone for the day and see if that makes a difference this evening.
I am out of ideas, lol
Click to expand...
Click to collapse
Take the six acres it and open her up, Take out button off and clean it and where it goes.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Take the six acres it and open her up, Take out button off and clean it and where it goes.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure the flex cable on you're power button is not working as intended, could be a short from a rain drop or just everyday wear and tear another issue could be that the battery is fried and can't hold a charge, but this seems unlikely given you're circumstance.
I always tell people to utilize pie controls to save you're everyday use from wearing out our precious hardware buttons, My power and home only get pressed to wake the device, everything else is pie control via LMT launcher
That happened to me a few months ago. I was at work when it happened. The phone would just continually restart, vibrate, restart, back and forth. I ended up taking the battery out so it wouldn't get drained. Had it out for about four hours. Once I got home, I put it back in and never had any more problems. It was just a random thing, so try keeping the battery out for a while.
I'll keep my fingers crossed. I took the phone apart last night to clean it out and it was pretty spotless. But It keeps shutting off after trying to boot after a few seconds. I just hope I can get to a point where I can get my pictures off of it now.
nightwulfss said:
I'll keep my fingers crossed. I took the phone apart last night to clean it out and it was pretty spotless. But It keeps shutting off after trying to boot after a few seconds. I just hope I can get to a point where I can get my pictures off of it now.
Click to expand...
Click to collapse
Hello all, as an update, I did nothing to my S3 over the weekend haping something magical could happen.
Today I went through all the normal steps again, and still a dead soldier. Now it wont ever SHow the Samsung logo however - just a short vibrate then nothing..
Still get a red light and a short vibrate when plugging into the comp without battery in though.
I have NOT taken it apart yet, but I will tonight most likely.
Thanks for all the suggestions and Ill keep this updated.
axel4401 said:
Hello all, as an update, I did nothing to my S3 over the weekend haping something magical could happen.
Today I went through all the normal steps again, and still a dead soldier. Now it wont ever SHow the Samsung logo however - just a short vibrate then nothing..
Still get a red light and a short vibrate when plugging into the comp without battery in though.
I have NOT taken it apart yet, but I will tonight most likely.
Thanks for all the suggestions and Ill keep this updated.
Click to expand...
Click to collapse
Hello again,
Some news, I am able to get it into download mode for about 1 second then the phone shuts off - just like the other person in this thread with the same issue.
I took the phone apart and used a Qtip with 91% isopropyl Alcohol to try and clean the power button (which looks surprisingly clean). Still the same thing happening.
I'm running out of ideas here, so please chime in if you have any.
Thanks
axel4401 said:
Hello again,
Some news, I am able to get it into download mode for about 1 second then the phone shuts off - just like the other person in this thread with the same issue.
I took the phone apart and used a Qtip with 91% isopropyl Alcohol to try and clean the power button (which looks surprisingly clean). Still the same thing happening.
I'm running out of ideas here, so please chime in if you have any.
Thanks
Click to expand...
Click to collapse
I was going to try the alcohol tonight, but I am afraid that I will have same results. I am going to try a new battery from another s3 tomorrow. I will post the results.
nightwulfss said:
I was going to try the alcohol tonight, but I am afraid that I will have same results. I am going to try a new battery from another s3 tomorrow. I will post the results.
Click to expand...
Click to collapse
Final update (hopefully)
I got the qtip and scrubbed anything to do with the battery, pressed the power button, got more alcohol in by the button (not a lot) scrubbed some more terminals, and the battery terminals, etc. waited about ten minutes and put the battery in...
Low and behold, something worked and now the phone comes on.
I dont know which part of the scrubbing actually did it, but something worked.
All in all I have no idea what actually fixed it, but the point is that it works.
Thank you for who those that insisted that it was a power button issue - you were most likely right.
So here are my results as of today, and what I have tried to get to this point:
After my S3 died and wouldn't boot up into recovery i tried cleaning all the internals with alcohol. I cleaned thoroughly, and focused on the charging port, the power switch and battery terminals. The phone acted exactly the same.
I then tried putting it in a bowl of rice for about 24 hours. I was thinking that it might have been caused by some condensation. No success.
I was thinking since the power would turn on whenever i plugged the battery in, that maybe the switch was stuck. I took it apart again and tested the switch with a multi-meter. The switch seemed fine. It was responding when i pushed it, so i figured that wasn't the problem.
I kept reading that apparently this is an issue with the mother board. I tried the broken PS3 method of heating up the motherboard with a heat gun in hopes to re-seat something that may be loose. This did not work either. After this, I figured i was SOL since I was out of ideas and out of warranty (which didn't really matter anyway since I am running Hyperdrive).
Earlier today I figured the best tool in your toolbox sometimes is a hammer. I started tapping the phone on the side of my table, especially around the power button, while trying to turn it on. It didn't seem like it was doing anything either. I then plugged the phone into the charger since i thought the battery was totally dead.
A few minutes after i walked away from the phone, I came back into room and the red charging light was on. I tried turning it on, and holy cow it works...wtf...
I have no idea what made this work. It could be a complete coincidence. But, this phone has not worked since last Saturday. I just kept messing with it and may have just gotten lucky. I don't think banging your phone will fix this, but if truly was a hardware issue, maybe something in the phones mother board is becoming loose from the extreme heat they endure at times. I know my S3 has gotten pretty hot when I use it to navigate and leave it in the case.
I don't know if any of this will help anyone, but this is my experience so far of my S3 having what I think is the sudden death failure. I will followup with any updates if it decides to act up again.
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.
Well something catastrophic just happened. I had downloaded and installed the one-click full restore for 4.4.2 and everything seemed to work perfectly. Worked as advertised.
It rebooted and started the typical google play updates... working great. It happened to be plugged into my USB port at this time. I unplugged the USB and plugged it into the wall (factory charger) and the screen went blank and alittle hot one the back left side (looking down at screen) in the middle. No power, nothing. Will not turn on... just completely dead.
I have tried the getting into recovery etc etc... nothing. I didn't know if there was another set of HARD reboot actions I could pursue to try to get this thing to turn on?
Appreciate anything..
Thanks
One more thing to add... Im wondering if the battery was completely dead... seconds before, I looked and it was at 38% while plugged into USB... it was draining with the limited USB power, so I was plugging it into the wall for more power when it died.
At this point, I am just leaving it plugged in for awhile... it seems when I first got it the battery was so dead it wouldn't turn on... but.. I think I at least got the battery screen.'
now found on EBAY for parts...LOL
Well that sucks.
You could try a new battery?
Have you tried calling the service department?
dtaylorr said:
Well that sucks.
You could try a new battery?
Have you tried calling the service department?
Click to expand...
Click to collapse
Yes it does suck..LOL I could try a new battery, but I don't think I have ever seen a battery cause no power immediately. If it wer the battery I would think plug power would work... but not knowing exactly how it is wired.... the motherboard heats up when charging so it appears power is getting past the charging port..
I haven't called service... I voided warranty with rooting.
If you are getting anything on the screen at all then a usb download jig (cheap and available on the web) will likely get you to download mode. If it does then you can flash via Odin or Heimdall as you please.
There are tutorials on YouTube for how to use a jig (super easy) and even how to build your own (also easy).
I guess you could try it even if you have only black screen too, but chances are less likely that it will work in that case.
Sent from my SAMSUNG-SGH-I337 using Xparent Cyan Tapatalk 2