GReetings,
So I have searched for a lot of forums to see if there is an answer to this.
So the story goes. I got myself a new phone and put the TP2 in a drawer. After moving, I have a reason to pull it out and get it ready to be used again. However, it wont turn on.
So I figure the battery went dead. I plug it into the charger, the LED lights up, and got to wait a few minutes. After a minute or so, the white HTC screen suddenly comes on the screen, it vibrates one quick, and shuts off again.
I cant power it up, I can get it to boot loader. Really not sure what the problem is here.
Any ideas suggestions would be welcome as I want to put this one back to stock so I can send it to my step-kid for use.
Try charging it for a few hours, while it is closed. If the phone regularly reboots and then switches off, leave it that way.
The idea is to charge the battery enough, so as the phone boots.
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
kilmarac said:
Ok will try that tonight when I'm heading for bed. Ill leave it to charge while I'm at work because I get tired of hbearing it vibrate every 20 seconds while its charging
Click to expand...
Click to collapse
Did you get it to work? I'm having the same problem. I posted in another thread that had the same problem as you.
Maybe HTC really is pushing an auto kill program.
Sent from my PG86100 using Tapatalk
Unfortunately, it didnt work. I think the phone was probably dropped one too many times and is broken. I cant get it to boot, cant even get into the bootloader. So I have no idea.
Steefje said:
had the same prob the other day
what helped here was:
remove the battery and let it out of the phone for a couple of hours (i did it at night). had the battery removed for about 8 hours. put it back in and it worked for me again.
give it a try and let me know!
Click to expand...
Click to collapse
I also had the same problem I took out the battery and blew on it to get it to cool down and had it sit out of the phone for 10-15mins then put it in the phone and plugged into charger and left it for 30mins then hit the power button.
This reboot cycle happens when my phone dies in android and it works every time for me.
Hope that helps
for future reference, the phone died with a Sim card in it, revived when a Sim card was replaced.
Sent from my cm_tenderloin using Tapatalk
yesterday I had the same problem, boot loader doesn't work. But.... I charged my battery, replaced it, pushed Vol. down + EndCall btn. + Power btn and inserted battery. As a result my boot loader is working now. But after running task 29 and flashing custom firmware my phone doesn't came back alive. I'm looking for solution now. Did anybody have the same problem?
When I'm flashing original firmware the process stops on checking my phone.
Please, give me advice how to solve my problem. Thx.
RHOD*** 32M SS-BC
SPL-0.88.000
MircoP(LED) Wrong Plat(0x0)
MicroP(KEY) Wrong Plat(0x0)
Turbo HW/Turbo SW
TP MFG DATA
501,526 793,854
810,209 211,200
211,855 Calibrated
First off it looks like you are not Hard SPLed so custom ROMs will be a problem for you. Second you have a major error with your keyboard and touch screen. I have a TP2 that took a dip into some water that has the same error - MircoP(LED) Wrong Plat(0x0) and MicroP(KEY) Wrong Plat(0x0). When I first got the phone it would not turn on but would make a noise that sounded like it was crying. I got another TP2 that works fine and swapped the top halfs of the phones because the new one looked like a dog chewed on it. It still worked but in real bad shape. The touch screen that got wet works fine so it is on the TP2 that I use all the time. The wet TP2 will now start up but the keyboard, all of the front buttons but the end key, and touch screen don't work. The touch screen will only register getting touch in one spot. So if you have a software keyboard up only the t will be hit. I Hard SPLed it, ran task 29, and installed a custom rom on it. I have to use My Mobiler to do anything with it. It also will take a battery that has a full charge and drain it to about 50% in about 20 minutes and then claim the battery is dead even on a charger. Something to play with.
With the error you have unless you got it wet you might have a bad flex cable. I would try to fix the error first before trying to change roms.
Thank you for answer.
My phone was HardSPLed and flashed by custom firmware and works fine for half a year. The reason for my situation was broken charger... I think that problem in hardware when I put it on charge, my phone lightly flashed by orange lamp and became can't turn on
You are told that it is looks like it doesn't hacked because I tried to roll it back to original.
Are you sure the phone did not get wet? Everything you describe makes it sound like the phone took a dip. If not, try plugging it into a computer and see if it will charge and turn on.
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
You can only HSPL once. If they (or you) relocked the device, you won't be able to unlock it again unless you can get Olipro/cmonex to take pity on you.
Glad I could help. Here is a small warning. Once a phone gets wet it's days are numbered. You might have a week, a month, or a year but the phone will die. I would plan ahead for the phone to die and keep an real close eye on it.
Sent from my HTC Touch Pro 2 running FRX07.1 using the XDA mobile application powered by Tapatalk
AlexeYM007 said:
I resolved my problem krekol, you are right at 100%!!! I took my phone from work-shop and they told me that some water get there, or it was just condensate. As a result oxidation around microphone and some connections.
Now, my phone works fine on WM 6.1 (they flashed it) and somewhy I can't flash Jackos S3 JackFULL 1.7.0. and Rhodium-HardSPL_V2_00R3 too
maybe it is effects of oxidation.... I'm trying flash from my flash-card.
Click to expand...
Click to collapse
If you need to HardSPL a second time, PM me.
Related
So my phone just flat out went nuts, It just restarts itself and can no longer fully start back up.. Sometimes it will get a min into the start up and boom restart, or sometimes i get the first splash screen for about a second or two and then it restarts.
Another weird thing it is doing if i pull the battery out for a few mins as soon as i put the battary back in the phone trys to start (without me hitting the power button).. Im not sure what to do i have tried different rom, kernals..
i was running the new OTA De-odexed with the new stock kernal
now im runninng gingerbread evo deck and the kernal that came with it..
If i pull the battery for a few hour and put it back in ill be able to start up my phone it will run with no problems for 30-60mins and then it starts this all over agian..
Any one have any ideas? or is there a way i can do a real wipe and get back to factory? I just need my damn phone
Someone had posted a similar problem with their daughters phone a few weeks ago, they found that the metal tabs for the battery was not making full connections. The problem was remedied by carefully bending the tab(s) (on the phone, not the battery) out to make a better connection...
I'm not saying this is your problem, but it would only take 10 seconds to check it
Swyped from my Raided Evo
Vinchenzop said:
Someone had posted a similar problem with their daughters phone a few weeks ago, they found that the metal tabs for the battery was not making full connections. The problem was remedied by carefully bending the tab(s) (on the phone, not the battery) out to make a better connection...
I'm not saying this is your problem, but it would only take 10 seconds to check it
Swyped from my Raided Evo
Click to expand...
Click to collapse
great idea i checked and they look fine, but thats kinda the way i was thinking.. it appears as though i have a short or something maybe.. at first i was thinking it was software releated... But now i dont think it is so much... at least i dont believe (i could be wrong) but if i pull my battery out and put it back in the phone shouldnt try and turn itself on unless i hit the power button
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.
Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...
i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%
It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.
Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...
I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal
May I ask what rom are you currently on?
datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel
It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness
Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.
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 ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
I have same problem!
Bump. I have the same problem too. Seems to have come out of the blue for an otherwise functional phone. Can't figure it out.
I'll add that I can get into twrp and it seems to function without the charger plugged.. But otherwise, if the charger is removed, phone dies like OP.
Anyone can help?
Hey, this happened to me too while I was using the camera too! What's the linkage?
@yakultski, have you figured this out yet?
Try to flash a RUU and if you got the same it should be an hardware problem...
yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
Did you resolve the issue. I heard it could be the battery failing, but i'm not so sure anymore, because when i run antutu benchmark my phone shuts down when using fisheye image processing or 3D, it turns off even when it's plugged in.
I suspect it's the GPU failing or something similar. That is weird since i wasn't using any intense 3D games. I'm sure this is my last HTC.
yakultski said:
My phone won't boot unless it is plugged in via wall charger.
If I got it to boot while charging, it instantly turns off when I unplug it even with battery at 100%.
I am able turn to go into hboot mode(power + volume down), even when it is unplugged. But it dies if I access recovery. I am able to perform "show image crc" function.
The problem started while I was using the camera and it just turned off by itself.
I was on SROM at the time when the problem started.
I managed to change ROM to SD, and even used lollipop RUU(verizon), but the problem wasn't resolved.:crying:
What do you think? Am I right to assume this is a hardware problem?
Click to expand...
Click to collapse
I don't know if you managed to solve your problem, but in my case I replaced the battery and now the problem is gone. So defective battery is the reason in my case. I replaced it my self which is quite a task but not so hard, you just need patience and time. So if you have time to reply me, please do, as i would like to help.:good:
Gunman84 said:
I don't know if you managed to solve your problem, but in my case I replaced the battery and now the problem is gone. So defective battery is the reason in my case. I replaced it my self which is quite a task but not so hard, you just need patience and time. So if you have time to reply me, please do, as i would like to help.:good:
Click to expand...
Click to collapse
Hey Gunman84, my phone is behaving in a similar fashion as the OP. I have an AT&T phone converted to a GPE. So everything is stock in that sense. If plugged in, phone operates normally. As soon as I unplug it, a couple of seconds later it will power off. If I boot into hboot, the phone will stay on for a long time (its been an hour+ already and its still on).
I watched a youtube video showing how to replace the battery and that was pretty intimidating - haha. Where did you get your battery replacement? and how much did it cost?
thanks
clemdaddy said:
Hey Gunman84, my phone is behaving in a similar fashion as the OP. I have an AT&T phone converted to a GPE. So everything is stock in that sense. If plugged in, phone operates normally. As soon as I unplug it, a couple of seconds later it will power off. If I boot into hboot, the phone will stay on for a long time (its been an hour+ already and its still on).
I watched a youtube video showing how to replace the battery and that was pretty intimidating - haha. Where did you get your battery replacement? and how much did it cost?
thanks
Click to expand...
Click to collapse
Hi, it's not so intimidating . Well you just need to be careful and patient, there are lots of small resistors, connectors and so on. Check the iFixit site for proper instructions here is the link https://www.ifixit.com/Teardown/HTC+One+%28M8%29+Teardown/23615 this is full teardown, and here is 2nd link where they focus mainly on replacing the battery https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650. I'm from Slovenia, and the battery cost me 20€, which is around 25US dollars, the battery was original one. I bought it from local supplier. It took me around 2-3 hours to replace it, or something like that, that's because i wanted to be careful.
Gunman84 said:
Hi, it's not so intimidating . Well you just need to be careful and patient, there are lots of small resistors, connectors and so on. Check the iFixit site for proper instructions here is the link https://www.ifixit.com/Teardown/HTC+One+%28M8%29+Teardown/23615 this is full teardown, and here is 2nd link where they focus mainly on replacing the battery https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650. I'm from Slovenia, and the battery cost me 20€, which is around 25US dollars, the battery was original one. I bought it from local supplier. It took me around 2-3 hours to replace it, or something like that, that's because i wanted to be careful.
Click to expand...
Click to collapse
Thanks so much for the links.
The phones behavior really makes me question if its the battery. For example, it stayed on in the hboot/recovery screen for 10+ hours (without being plugged in). So the battery can definitely hold a charge.
I'm afraid to open up the phone (and potentially break it), when there is potentially something else going on (maybe a software issue). I guess if I run out of ideas, I'll have no choice but to attempt the battery replacement.
thanks again!
clemdaddy said:
Thanks so much for the links.
The phones behavior really makes me question if its the battery. For example, it stayed on in the hboot/recovery screen for 10+ hours (without being plugged in). So the battery can definitely hold a charge.
I'm afraid to open up the phone (and potentially break it), when there is potentially something else going on (maybe a software issue). I guess if I run out of ideas, I'll have no choice but to attempt the battery replacement.
thanks again!
Click to expand...
Click to collapse
Well in my case i could also stay in recovery mode(TWRP) indefinitely also in bootloader mode, that's because you are not in the operating system. The graphics are not running at that point and so on, it doesn't drain that much power at that point either.. It's a different story if you try to flash a rom in aroma, at that point the phone shuts of if not plugged in. It is the battery, trust me.
Gunman84 said:
Well in my case i could also stay in recovery mode(TWRP) indefinitely also in bootloader mode, that's because you are not in the operating system. The graphics are not running at that point and so on, it doesn't drain that much power at that point either.. It's a different story if you try to flash a rom in aroma, at that point the phone shuts of if not plugged in. It is the battery, trust me.
Click to expand...
Click to collapse
Really appreciate your responses. Makes sense what you say. I'm going to attempt the battery swap. Got no other option!
For the adhesive parts of the phone. When putting it back together, did you need to reapply more adhesive?
Thanks
clemdaddy said:
Really appreciate your responses. Makes sense what you say. I'm going to attempt the battery swap. Got no other option!
For the adhesive parts of the phone. When putting it back together, did you need to reapply more adhesive?
Thanks
Click to expand...
Click to collapse
Nope, no additional adhesive was needed in my case. I used the hair dryer to soften the original adhesive. The speaker grills were difficult to remove as they are glued quite well, but eventually they came off. The toughest part was separating the back casing, as you do need quite a few prying picks or guitar picks.
Just be careful with the motherboard, slowly remove the tape that covers the connectors, you don't want to rip apart any flat cables. And don't throw away that tape, you will need it.
Ohh i have the same issue.i used phone normally before and battery worked fine.but then i flashed ICE rom and when i was using the camera this happend.is this really a battery issue?
Sent from my HTC Desire EYE using XDA-Developers mobile app
Kasun72 said:
Ohh i have the same issue.i used phone normally before and battery worked fine.but then i flashed ICE rom and when i was using the camera this happend.is this really a battery issue?
Sent from my HTC Desire EYE using XDA-Developers mobile app
Click to expand...
Click to collapse
Well if yours symptoms are the same as clemdaddy has, then yes. Sorry, but at least now you know what the problem is.
Got the new battery today and performed the phone surgery. All the connections looked good. Pieced it all back together and everything works BUT the new battery won't charge. The phone is running off the battery, so the connections I made must be correct. Running off the battery the phone no longer exhibits the symptoms I described above (so this most likely confirms my previous battery was the culprit). I tried the hold all buttons for 2 minutes to re-calibrate the new battery. All that did was made the phone now display a full battery (instead of the empty battery it initially showed).
On the weekend I'll open it up again and see if I missed something.
Got the replacement battery. Re-opened up the phone. This time I over heated the upper and lower panels which caused them both to warp a bit, and one of them to have its paint bubble :crying: :crying: :crying: :crying:
I replaced the new defective battery with the most recent one. Put the phone back together and it is back to normal again! Also probably because of the over heating, there is now a little bit of a rainbow effect on the lower part of the LCD screen!
A real pity the first battery was defective, causing me to have to re-open it and carelessly overheat it. Otherwise the 1st attempt would have been a flawless repair!
With the warped panels, the bubbling paint and now the rainbow effect on the screen, I wonder how long I'll keep the phone. These little things are definitely bugging me... If I get rid of it, I'll really miss my google edition htc one m8! Nothing like a nexus like experience with a remove-able microSD card. Such a thing no longer exists