Brick - Fascinate Q&A, Help & Troubleshooting

Was running AOKP milestone 4 when spontaneously there appears on my screen an empty battery icon. This was in spite of the fact that battery was fully charged. The phone was completely unresponsive 2 rebooting or going into recovery. I was able to get my computer to recognize the phone 1 time and I odined back to stock gingerbread. Booted fine and seemed to be okay when it happened again. Now it just sits at an empty battery icon. The computer no longer recognizes it. If I plug it in to charge it briefly displays what appears to be stock recovery. The stock recovery however is not responsive to any key presses. Anyone experienced this or have any ideas how I can rectify it. Fortunately I have a backup fascinate and was able to activate it. I'd like to keep the other as a spare if I can figure out how to get it to respond.
Sent from my backup (lol) SCH-I500 using Tapatalk

thedoman said:
Was running AOKP milestone 4 when spontaneously there appears on my screen an empty battery icon. This was in spite of the fact that battery was fully charged. The phone was completely unresponsive 2 rebooting or going into recovery. I was able to get my computer to recognize the phone 1 time and I odined back to stock gingerbread. Booted fine and seemed to be okay when it happened again. Now it just sits at an empty battery icon. The computer no longer recognizes it. If I plug it in to charge it briefly displays what appears to be stock recovery. The stock recovery however is not responsive to any key presses. Anyone experienced this or have any ideas how I can rectify it. Fortunately I have a backup fascinate and was able to activate it. I'd like to keep the other as a spare if I can figure out how to get it to respond.
Sent from my backup (lol) SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Did you try switching batteries?
Sent from my Glitched AOKP Unicorn.

Absolutely. Tried 3 others all Samsung, all previously used w/o problem. Don't think AOKP did anthing. Can you flash a phone to death? I certainly have changed mine up enough over the last year.
Sent from my SCH-I500 using Tapatalk

thedoman said:
Absolutely. Tried 3 others all Samsung, all previously used w/o problem. Don't think AOKP did anthing. Can you flash a phone to death? I certainly have changed mine up enough over the last year.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Every piece of equipment has a different life span. If you can not Odin to fix it, it may be more than software.
Sent from my Glitched AOKP Unicorn.

thedoman said:
....Can you flash a phone to death? I certainly have changed mine up enough over the last year.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Flash memory does have a limit to the number of times that it can go through the erase/program cycle but it's somewhere between 10,000 and 100,000 cycles for NAND flash.

I've had some charging issues after flashing to AKOP, but that may or may not be related to your issue.
Sometimes I can get it to respond in download mode then take it to stock but most of the time it's just a waiting game. Everything seems to run fine on stock. If I go to CM7 or AKOP (or any ICS ROM) I randomly get instant battery drain and an somewhat unresponsive charging port.
I've also noticed some of the Fascinates that come through where I work only take certain batteries. Some take the blue Samsung and others take the black ones.

Related

[Q] OTA Bricking phones?

My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
durthquake said:
My friend and I both have Rezounds. I have yet to get the update, he had Scott's ICS ROM on his. The update forced itself onto his phone and bricked it. When he went to the store, the reps told him the update seems to be doing this to alot of people (rep said they saw 10 of them today!). Anyone else have the OTA brick a ROM's phone or even stock?
Click to expand...
Click to collapse
No, but I am sure if you have a custom recovery on your phone with a custom rom an official update sure isn't going to help ..but I figured it would just error out. How did it brick it ? he was unable to load Hboot anymore ?
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Could you get into hboot and run the ruu? If you can do that, the phone isn't bricked...
Sent from my ADR6425LVW using XDA App
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I suspect the no charging is due to running the battery down all the way. There's a thread or two about that issue. I think the solution was to pull the battery, plug in the charger then put the battery back in while phone is connected to charger. Then you might have to wait up to 30 minutes for the light to turn on and for it to start charging.
And yeah, if you can boot into hboot you should be able to get the phone back with RUU or if the ROM is fine then flash Amon Ra recovery in fastboot.
It didn't allow anything to be done in hboot. It won't even turn on now, i have him my battery to try and still doesn't turn on.
Sent from my ADR6425LVW using Tapatalk
Well read through this thread:
http://forum.xda-developers.com/showthread.php?t=1434532
and see if you can at least get it charged up again. Then go from there.
Both me and my wife have had the OTA for at least a week and we have not had any issues with the OTA.
Also, I must say, this is the first time I have heard of the OTA causing bricking of the unit.
If you can't get it charged, try the writing hack to get it involved. Basically you just take a regular usb cable and snip the connector off. From there you take the ground and the power, and then you put the ground and power to the battery in the respective places. Worked for a bad Atrix flash that killed my battery.
Sent from my Galaxy Nexus using Tapatalk
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
drtnsnw said:
It bricked my stock Rezound. Could not have happened on a worse day to. I had to do a factory reset to get it to come back. Real PIA
Chris
Click to expand...
Click to collapse
That's not a brick. That's a pain in the ass.
tekhna said:
That's not a brick. That's a pain in the ass.
Click to expand...
Click to collapse
+1
a brick is just what it is.. a brick.
which means the phone is done. you can't use it again.
durthquake said:
It went to the HTC screen and stayed there, when tried to go-to recovery it wouldn't work, eventually screen went black and wouldn't turn on, or even charge!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If it can get to the HTC screen, it isn't bricked. Put your battery in his phone and see if it can get to HBOOT.
durthquake said:
I hadn't heard of it bricking it till I saw it first hand... As far as charging, it's a non issue since I have my friend my fully charged battery to try and wouldn't turn on. (Note that this is happened only after it stayed on the HTC screen for about 30 minutes, so it may have overheated or something during that time?)
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I don't think you can write off the battery/charging issue. It takes some time for people who have let their battery fully drain to get the phone to charge it again although they were able charge on an external charger iirc. Anyway, point is it may be the phone not the battery that needs to "wake up" (for lack of a better term) again.
So definitely go through that dead battery charging thread and try everything in there to get the phone to charge the battery again. Then you'll know the phone is functioning as it should, atm it may not be.
I don't understand how the the OTA forced itself since all of Scotts ROMs are debloated. Everyone that rooted and debloated running stock, said that the update failed in recovery, I know I witnessed it on mine. Being on an ICS build, one would think that the update wouldn't even be downloaded.
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
con247 said:
yeah it is strange. Even if I force check for update on my Rez the update doesn't come. Are you sure your friend is telling you the whole story?
Click to expand...
Click to collapse
I am said friend.
Durthquake sits in the cube next to me. He watched the whole event transpire.
Here's what happened and what was tried and the resolution,
Rezound reboots to the HTC screen. Won't show the think brilliantly words. Just stayed on HTC.
So I did a battery pull and rebooted phone and same thing. Just HTC.
Now I reboot to recovery, get hboot and try to do a wipe. It blinks like its going to try to go to recovery then turns off.
Do another battery pull boot maneuver and it does the same thing.
As we are at work I did have to work so I leave it on the stock wall charger for about an hour and try to turn on again. HTC screen so I leave it to see what happens, maybe I didn't wait long enough.
Like 35 minutes later screen goes black.
Now it won't power on, won't go to hboot, basically a brick. So I pull my battery give it to durthquake who gives me his rezound battery. His phone turns on, mine doesn't.
Now I try pulling sim, sdcard, and putting my battery back in. Still nada. Phone be properly bricked.
Bring it home put sim, sdcard, and battery back in and put on HTC wall charger overnight. In the am nothing. Still a pretty beats brick.
Go to vzw and the try charging turning on etc. Nada. They say since the ota they've had about 5 of these in.
The resolution is vzw sending me a new rezound and I buying a new phone so I can give the resound to my gf.
Sent from my Galaxy Nexus using Tapatalk

After flashing Jokers CM9 ICS Rom problems

As the title states I flashed the latest CM9 ICS rom from Joker and It started off working fine after getting the radio to finally work but now it randomly turns off and i won't be able to turn it back on unless i do a battery pull and also the phone tends to overheat way too much. I didn't flash anything other then the Gapps and the rom itself.
Jaemostoriginal said:
As the title states I flashed the latest CM9 ICS rom from Joker and It started off working fine after getting the radio to finally work but now it randomly turns off and i won't be able to turn it back on unless i do a battery pull and also the phone tends to overheat way too much. I didn't flash anything other then the Gapps and the rom itself.
Click to expand...
Click to collapse
It's overclocked by default. So that's probably heating it up. I recommend lowering it to 1ghz or lower. As for the radio... it's turning off? Or data? Just curious.
Sent from my MB853 using XDA
na7q said:
It's overclocked by default. So that's probably heating it up. I recommend lowering it to 1ghz or lower. As for the radio... it's turning off? Or data? Just curious.
Sent from my MB853 using XDA
Click to expand...
Click to collapse
i'm not to sure how exactly to do that but i'll do some searching. and at first the radio just wasn't picking up a provider but then i flashed the 0.3.1 or w.e it was first and now that is working. the only issue now is that it will reboot randomly and thats the biggest problem for me. I thought it had something to do with the overheating?
Jaemostoriginal said:
As the title states I flashed the latest CM9 ICS rom from Joker and It started off working fine after getting the radio to finally work but now it randomly turns off and i won't be able to turn it back on unless i do a battery pull and also the phone tends to overheat way too much. I didn't flash anything other then the Gapps and the rom itself.
Click to expand...
Click to collapse
Its a beautiful rom, however I had to switch to miui because I started getting an error "the process android.phone.com has stopped unexpectedly" and I would lose all service. I couldn't take it anymore.
Sent from my MB855 using xda premium
MrWhite1127 said:
Its a beautiful rom, however I had to switch to miui because I started getting an error "the process android.phone.com has stopped unexpectedly" and I would lose all service. I couldn't take it anymore.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
If either of you get that error with no service all you have to do is flash a previous version such as 0.3.0. Reboot into the OS. Go back to the recovery and update to the latest. Do not wipe anything when updating! It's an easy fix and all will work afterwards. Flash them twice if necessary.
Sent from my MB853 using XDA
MrWhite1127 said:
Its a beautiful rom, however I had to switch to miui because I started getting an error "the process android.phone.com has stopped unexpectedly" and I would lose all service. I couldn't take it anymore.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
na7q said:
If either of you get that error with no service all you have to do is flash a previous version such as 0.3.0. Reboot into the OS. Go back to the recovery and update to the latest. Do not wipe anything when updating! It's an easy fix and all will work afterwards. Flash them twice if necessary.
Sent from my MB853 using XDA
Click to expand...
Click to collapse
@Mr white I love this rom which is why I want it to stop rebooting randomly just do what @na7q said and it should work I'm just curious if it's the overclocking and over heating that's causing it to reboot?
Now it seems like it shuts down when I have wifi connected after some time. Any suggestions?
Sent from my MB855 using XDA
EDIT: also it only shuts down whenever the phone is sleeping never when i'm actually using it
Jaemostoriginal said:
As the title states I flashed the latest CM9 ICS rom from Joker and It started off working fine after getting the radio to finally work but now it randomly turns off and i won't be able to turn it back on unless i do a battery pull and also the phone tends to overheat way too much. I didn't flash anything other then the Gapps and the rom itself.
Click to expand...
Click to collapse
I am having the same issue. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Galaxy_S_ said:
I am having the same issue. But strangely it only seems to happen when I am outside. The first time I noticed it was when I went fishing. My phone had about 80% charge, and when I picked it up maybe 30 mins later is was scorching hot. To the point that it burnt me. And it had shut off. I didn't have it in the sun or anything. It was in the shade inside a bag. I was not able to get it to turn on even with a battery pull even after it had cooled down. The battery completely drained in a matter of minutes. I couldn't even get it to charge in the truck on the car charger, either. It got too hot on the charger to the point it wouldn't even get a charge. This has happened about 3 or 4 times since. It will go from a full battery, get super hot, and completely drain within minutes. This never used to happen in the house, it was only an issue outside. until today. Went fishing, phone had full charge. It managed to hold the battery for a couple hours, unlike the other times, but eventually got hot and died. Then when I got home, plugged it into the charger and went to sleep, woke up a couple hours later and it was burning hot, and had no charge. Other things on it are acting weird now, as well. The screen keeps turning on and off every few seconds by itself. I don't know what the issue is, but I might have to switch back to stock if I can't find a solution. Because eventually this is going to fry my phone. And I don't want that to happen. It is also a huge inconvenience for your phone battery to drain in a matter of minutes and become a useless paperweight when you are in the middle of nowhere and need a form of communication in an emergency.
Click to expand...
Click to collapse
I'm currently having the same issue again where the phone gets extremely hot it will shut off and drain the battery . Are you overclocking?
Sent from my MB855 using xda app-developers app
if anyone needs a fix all i did was flash the oleg peetr 1GHz kernel v4 http://forum.xda-developers.com/showthread.php?t=1520417
gtalk
Jaemostoriginal said:
if anyone needs a fix all i did was flash the oleg peetr 1GHz kernel v4 http://forum.xda-developers.com/showthread.php?t=1520417
Click to expand...
Click to collapse
Is anyone having issues where Gtalk with FC when trying to do video chat?

[Q] Charging issue

My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
mistabeo said:
My problem is kind of strange.. when I turn off the phone, it thinks it's being charged (no cable plugged in).. and i'm unable to boot the OS as per usual. The only way for me to do it is to load CWM and choose the reboot option, which does work but only with 1 battery (a spare hyperion one). The stock battery and my other hyperion aftermarket battery does not work. Instead, it takes me to the stock recovery system.
I tried remedying this problem by doing wiping battery stats, but it doesn't help any. I also decided to make the jump from unnamed ROM (gingerbread) to an ICS rom (AOKP)
On top of that, the phone no longer makes a beeping sound when i plug the cable in, but it does charge the battery.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
It seems like this might be a hardware issue, but i'm no expert.
Click to expand...
Click to collapse
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
jt.61 said:
I would try wiping cache and dalvik cache in cwm. Also, fix permissions in cwm. If that does nothing, I would try a different kernel. However, this may be an internal issue of the phone.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
122ninjas said:
Well you fixed your charging issue by itself It says that because the flash counter has been tripped. Just use any triangle away app from the play store.
Click to expand...
Click to collapse
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
mistabeo said:
i just flashed to AOKP ics rom yesterday from unnamed ROM, so i doubt it's a a kernel issue. just tried wiping cache, dalvik cache, and fixed permissions. still the same issue. im afraid of shutting the phone off or changing the batteries now, which is a pain since the new ICS rom burns battery power like crazy.
the flash counter isn't a big issue for me; thought i had circumvented it when i flashed the ROM 10 months ago, but i guess not. the phone still thinks it's being charged when it's turned off though. that's my main problem.
Click to expand...
Click to collapse
Try to go to stock and see if the problem persists. If it does obviously a hardware issue
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
mistabeo said:
ultimately, if i really want to confirm, i'd probably have to do that. but i've already installed 2 different ROMs and the issue is still persistent, so i'm just going to assume it's a hardware issue. it also seems now that the phone no longer turns off. if i choose to turn it off, it'll just reboot the phone. this phone will have to last me another 9-10 months, i just hope it doesn't die out on me.
but yeah, i tried ICS for about a day and didn't like it. bad battery life, seems slower, and less user intuitive UI.. so i'm going back to gingerbread.
Click to expand...
Click to collapse
you know samsung has factory warranty for that kind of stuff.
i got my phone refurbished, about 9 or so months ago.. it only came with 3 months for the warranty. i guess getting a returned phone ended up biting me in the ass.
now the phone is overheating when im charging it.. looks like it's going to crap out on me soon.
Download the stock 2.3.4 firmware from the download repository. Do a full wipe including system data cache and dalvik. Boot into download mode hook up Odin and flash the stock firmware. If its a hardware issue your problems will persist in which case u could sell it on eBay for parts. If its a software issue that will fix it.
Sent from my SGH-I777 using xda premium
that's what i'll probably have to do tomorrow. if i remember correct, rooting the phone on 2.3.4 wasn't that straight forward, so i'd have to read up on how to do that again. but im just gonna leave it as is right now.
the phone acts really weird. when i took out the battery and replaced it with another one, it would keep doing the same thing. so then i plugged the phone into the USB charger and tried turning it on - that worked.
if it's a hardware thing, it's got to be something to do with the battery sensor. the phone is simple to remove, so i wonder if i can replace it myself.
i believe my phone is now semi-FUBAR.. it still runs, but seems like the battery sensor issue is a hardware one. i just tried doing a stock flash/odin thingy, and it still has the same issues... also, the phone is now permanently showing as MTP connected. i am also seeing decreased battery life.. only lasts about 1/2 a day now.
i guess i learned my lesson.. don't switch out the batteries too often, or your phone will die.
Another thing: the boot screen (when turning phone on) shows "samsung i9100" when i'm pretty sure my phone is an i777.. i might have done something to this phone when i got it about 10 months ago, but i don't remember. All i remember was rooting the phone and flashing it to unnamed ROM.
Click to expand...
Click to collapse
is this a big deal? i'm also having samsung i9100? im using ucle5 AJ's rom/kernel.
i'm also having issues with charging the phone. it seems to charge forever, i have to unplug and plug the charger again to properly charge it.
When it says i9100 it means you tripped the flash counter. If you want to reset it use a triangle away app.
Sent from my SGH-I777
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
bubuty said:
i see thanks.
i'll try to run this app and see what will happen.
do wiping battery stat needs to be in full charged? i used to do that on my tab so i guess same principle applies.
Click to expand...
Click to collapse
No the same principle does not apply. Battery state wiping has no effect on this phone.
Sent from team Pirate! Using Tapatalk 2

[Q] HTC Thunderbolt Bricked, Won't Charge Or Turn On

as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
stanleyopar2000 said:
as you read in the topic title. My HTC thunderbolt is dead. nothing. no yellow / green light at all. This has happened before..but a simple battery pull for about 20 minutes and a restart got me going again. Now...it won't work. I'm not a noob where I flashed the wrong radio or something stupid like that. I had fully functioning Thunderbolt with LiquidSmooth ICS JMOD MR2. Before my phone decided to commit permanent suicide, it was rebooting to the boot screen every hour or so to the LiquidSmooth boot animation while I was using PowerAmp. Then I shut if off normally (just like last time..) and now it won't charge turn on, or do ANYTHING. It won't even go to the HTC logo where I can go to clockwork or the hBOOT menu. I'm running out of options. If anyone could give me advice. That would be great, as I cannot afford another one :___;
Thanks for your time = ]
Click to expand...
Click to collapse
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
jonah1234 said:
Flashing the radio is the only thing u can flash and completely brick your phone with no fix if you flash wrong or the radio is for a different device then I think your just gonna have to move on to a different phone.
Sent from my AOKP HTC Thunderbolt from Tapatalk 2.4
Click to expand...
Click to collapse
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
stanleyopar2000 said:
This is exactly what I didn't do. I was just stating that because I bet some users on here flash the wrong radio or unplug it during flashing and cry on here later for a solution. This is what I did not do.
With that said...is there any possible solution for my dilemma?
Click to expand...
Click to collapse
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
smtom said:
Not any solution or consolidation, but my first bolt did the exact same thing after flashing a rom that I won't name here. The issue was most likely mine,but it happened to me and at least one other user as well.
If yours spontaneously croaked, most likely not the same issue, but mine presented exactly what you described.
I had to get a replacement.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
I had 4.0 LiquidSmooth ICS JMOD my custom ROM on my phone ever since the rom first came out.and it was perfectly...fine...
and this same problem happened when I had GB ThunderShed CM7..but my gf told me to pull the battery out and leave it out for 20 minutes..then it put it back in. It worked. She did this many times with her Droid 1. Since it was problematic with this issue. (first android phone OF COURSE its going to have problems) Now she's an iPhone user i'm constantly trying to convert back lol
anyway...as stated before..it's now done it again and this time it's totally dead. my phone was trying to tell me something I bet.
How old is your phone?
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Doubt that'll work if its the same as mine. PC and adb won't see it. And I used known good batteries and charger from my other bolt.just gonna hold on to it in case I find one with a busted screen for cheap on craigslist
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Lightning Won't Strike Twice Folks
disconnecktie said:
Try a different battery maybe. It might be dead. Your USB port could have gone bad too.
Sent from my Thunderbolt using Tapatalk 2
Click to expand...
Click to collapse
I had 2 differernt batteries one extended...the other the stock small one. both would not charge. and both had decent battery power when I shut it off.
Shadow Death said:
How old is your phone?
Click to expand...
Click to collapse
Got it a month after it came out first 4G LTE phone maaan
dopediculous said:
Nothing to do with radios or ROMs. A bricked phone will still receive a charge. You need to try a different battery ( preferrably 1 that is charged and for the Thunderbolt) once you get it booted into whatever ROM you're using, go to menu, settings, power and make sure that "fastboot" isn't checked. By default fast boot is checked by HTC and by most ROMs. What fastboot does is just put your phone into "hibernate" much like a PC does.
So when you turn your phone off, it appears that its off, but its really just sleeping. If the battery dies and fastboot is checked, the phone is hella confused about its current state. HTC did this by default for a better customer experience, but its kinda dumb and bad in the long run as your phone never gets a freaking break. Lol
Thats why I'm suggesting getting a good battery to boot up to a ROM or whatever, turn off fastboot, properly turn off the phone then charge your battery. It may take up to 10+ min before you to get an orange light that'll flash then eventually go solid. Let it go solid for about 20+ min to be on the safe side, then boot
Good luck man
Sent from my Geeked n Tweaked GS3
Click to expand...
Click to collapse
this phone does not. I had two batteries with a decent charge and they didn't charge on it. The ROM I was using was a AOSP rom. not sense based...so there was no power menu and a fastboot option to uncheck
wampuscat said:
Man I bought one off craigslist that did the exact same thing. Had it about a week. Started random reboots so I was restoring a backup. While trying that recovery randomly rebooted a couple times them finally restore finished. It bootlooped so I pulled the battery and that was the last time it did anything. PC won't see it, won't get a charge light. Put a fully charged battery from my other tbolt in it. Still nothing. It literally died in my hands. I guess a hardware failure was the cause. Also picked up the wireless charging battery cover to try my power mat to see if that would at least make the charging light come on ....nope
Click to expand...
Click to collapse
yep. it did die in my hands. I'm chalking this up to hardware failure as well...
playerjunglejosh said:
You should try this, heck order a battery and wall charger off of Amazon for about $15.... Put the battery in and use ADB to put your phone into recovery....
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
two batteries and they do the same thing..and I cant boot into ADB mode if the damon can't detect the device on.
playerjunglejosh said:
Well I've searched the net and this has happened to several people that weren't even rooted or on a custom Rom. To me it seems like the motherboard(or the phones equivalent) is fried....that would explain why it happens on many thunderbolts(but it could just be a simple fix that I don't know of)
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Yep. the Motherboard is fried. has to be.
Thank you so much everyone for your advice, concern and help..but nothing can fix or repair hardware failure to this extent
I got a used HTC Rezound. It's amazing...it's everything the T-Bolt should have been
even though I had this problem before and a long term battery pull fixed it...Looks like Lightning Will Not Strike Twice for The Thunderbolt.
Thank you for your concern and support....but it's just as good as a future spare parts phone on craigslist.
This thread can be locked now.

(Q) HELP. Vibrant keep turning off& won't hold the charge

So my vibrant is acting up its been like 2 weeks keep turning it self off then on like every 15 minutes. I was rooted I tried different Roms nothing worked I went back to stock still have the same issue..
Any one experienced this hardware issue?
Thx
Sent from my Nexus 4 using xda premium
Lt.Tealc said:
So my vibrant is acting up its been like 2 weeks keep turning it self off then on like every 15 minutes. I was rooted I tried different Roms nothing worked I went back to stock still have the same issue..
Any one experienced this hardware issue?
Thx
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Sounds like a bad battery. I have 2 vibrants and 5 batteries 1 of which causes the phones to act just like that.
PA_Vibrant 360° Productions
I replaced the battery with oem still doing it. Thx for the help though
Sent from my Nexus 4 using xda premium
I've been having a similar issue with my Vibrant only it rarely lasts 2 minutes. It sometimes seems software related, but mostly appears to be a hardware issue. I've tried 2 different batteries with no change. It will not even stay on if plugged into a charger unless it is in download mode (luckily it runs fine in download mode and most of the time in recovery mode). I've tried ODINing back to stock and various other tricks (different bootloader, ROMs, etc.) but nothing seems to work. It seems to run best right after an ODIN to stock (lasts maybe 10-15 minutes) but it eventually turns off (doesn't shut down, it just goes instantly black). After it shuts off it usually won't turn back on until I pull the battery for a while. I've basically given up on that Vibrant--but I just bought 2 more used Vibrants for me and the wife.

Categories

Resources