Good Morning. Last night I flashed the latest RUU so I could install Nils latest Business Sense. After the RUU flash, everything booted fine so I rebooted into the boot loader and flashed the latest TWRP. It said it flashed fine, press power to reboot. I did that and now nothing.
I don't get a charging light when I plug it in, I let it sit over night on the charger, still nothing.
I've pulled the battery, I've tried connecting it to my PC so I can run adb reboot, nothing.
The phone is S-OFF. I've done some messed up stuff before but I've always been able to at least get a response out of the phone. With this, I don't get anything.
Appreciate any help anyone can provide. Thanks!
To clarify, I can't get into HBOOT, nothing. Why would flashing TWRP do that?
ChaOConnor said:
Good Morning. Last night I flashed the latest RUU so I could install Nils latest Business Sense. After the RUU flash, everything booted fine so I rebooted into the boot loader and flashed the latest TWRP. It said it flashed fine, press power to reboot. I did that and now nothing.
I don't get a charging light when I plug it in, I let it sit over night on the charger, still nothing.
I've pulled the battery, I've tried connecting it to my PC so I can run adb reboot, nothing.
The phone is S-OFF. I've done some messed up stuff before but I've always been able to at least get a response out of the phone. With this, I don't get anything.
Appreciate any help anyone can provide. Thanks!
To clarify, I can't get into HBOOT, nothing. Why would flashing TWRP do that?
Click to expand...
Click to collapse
Silly question, but did you verify md5 sums on the RUU and twrp?
If not go ahead and check those from where you downloaded them and see if they match.
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
Silly question, but did you verify md5 sums on the RUU and twrp?
If not go ahead and check those from where you downloaded them and see if they match.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not a silly question at all. Yes, they do match.
I'm just at a loss, I can't get the phone to register anything. Won't turn on, won't pick up when connected to a PC, no screen flash, no charging light. Nothing. Very odd.
ChaOConnor said:
Not a silly question at all. Yes, they do match.
I'm just at a loss, I can't get the phone to register anything. Won't turn on, won't pick up when connected to a PC, no screen flash, no charging light. Nothing. Very odd.
Click to expand...
Click to collapse
You can't get into the bootloader?
Sent from my ADR6425LVW using Tapatalk 2
ChaOConnor said:
Not a silly question at all. Yes, they do match.
I'm just at a loss, I can't get the phone to register anything. Won't turn on, won't pick up when connected to a PC, no screen flash, no charging light. Nothing. Very odd.
Click to expand...
Click to collapse
Ok next thoughts. If you know for sure your battery had a decent charge, leave battery out for a few hours and try again.
If you are not sure see about trying someone elses charged battery or go to a VZW store and try one of their batteries.
Realistically the only thing twrp could do is possibly have the same bug CWM has and not allow the phone to charge when powered off. Hadnt heard of this but also havent run 2.2 since i just got the sgsiii
Sent from my SCH-I535 using xda app-developers app
ijustwantmydock said:
You can't get into the bootloader?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
No, it's like it won't turn on.
I thought it was like the old CWM issue when a battery ran down and you had to let it charge over night. I did that. But nothing happens even when I connect it to a PC, I should in theory if it's the same problem, adb and reboot it.
I may very well have bricked it, but it just doesn't make sense. The MD5's matched. There was no power disconnect. It finished properly and told me to push power to reboot.
nosympathy said:
Ok next thoughts. If you know for sure your battery had a decent charge, leave battery out for a few hours and try again.
If you are not sure see about trying someone elses charged battery or go to a VZW store and try one of their batteries.
Realistically the only thing twrp could do is possibly have the same bug CWM has and not allow the phone to charge when powered off. Hadnt heard of this but also havent run 2.2 since i just got the sgsiii
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Okay, I'll give that a shot. Thanks!
ChaOConnor said:
Okay, I'll give that a shot. Thanks!
Click to expand...
Click to collapse
You see it more with computers but sometimes when things go funky, you cannot just do a normal battery pull as the capacitors dont drain that fast. So by leaving the battery out and letting the capacitors drain you might luck out.
You can also for a quick try pull battery and hold the power button down for 30 seconds and try. If not try leaving the battery out for a few hours.
If that doesnt work let us know and we will come up with other ideas.
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
You see it more with computers but sometimes when things go funky, you cannot just do a normal battery pull as the capacitors dont drain that fast. So by leaving the battery out and letting the capacitors drain you might luck out.
You can also for a quick try pull battery and hold the power button down for 30 seconds and try. If not try leaving the battery out for a few hours.
If that doesnt work let us know and we will come up with other ideas.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's funny you said that, I was thinking about when I flash the bios on my MB I always drain the capacitors after I flash and before I reboot. I tried the quick pull and held the power for 30 seconds. No joy.
I'll let it sit without the battery for a few hours and try.
The ***** of it is, I'm in Afghanistan right now, so I'm pretty much SOL for getting another battery, etc. Oh well... guess when I get home from deployment I'll just buy a few phone if I really hosed this up.
Did you download the first version of the recent update he put up because it was messed up and said not to download that one. Try contacting Con see if he can help
Sent from my Sense4 ICS Rezound
LakerStar25 said:
Did you download the first version of the recent update he put up because it was messed up and said not to download that one. Try contacting Con see if he can help
Sent from my Sense4 ICS Rezound
Click to expand...
Click to collapse
Just posted over there, thanks!
nosympathy said:
You see it more with computers but sometimes when things go funky, you cannot just do a normal battery pull as the capacitors dont drain that fast. So by leaving the battery out and letting the capacitors drain you might luck out.
You can also for a quick try pull battery and hold the power button down for 30 seconds and try. If not try leaving the battery out for a few hours.
If that doesnt work let us know and we will come up with other ideas.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
No dice, nothing happening. Hmm... I'm really at a loss. I just ordered another batter to try, but that's going to take a week or two to get here.
EDIT: Good news! Left the battery out over night, this time it booted up fine. Defintely related to some weird electrical issue after flashing.
ChaOConnor said:
No dice, nothing happening. Hmm... I'm really at a loss. I just ordered another batter to try, but that's going to take a week or two to get here.
EDIT: Good news! Left the battery out over night, this time it booted up fine. Defintely related to some weird electrical issue after flashing.
Click to expand...
Click to collapse
Bah. None of this voodoo stuff works on my phone. I've become certain ICS broke it but I have a cracked screen... :crying: Unless something electrical is fried. I never smelled anything...
Related
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
I accidently installed cwm on my phone with Rom manager and let it die. Obviously it wouldn't charge up because i was using cwm. So I popped in the extended battery and installed amon ra 3.15 with Scotts cleanflash tool. The dead battery still won't charge. How do I fix it?
Sent from my ADR6425LVW using Tapatalk
have you tried turning your phone off then putting in the dead battery. place it on the charger while the phone is still off and try to charge it. enable/disable fast boot may help also.
when testing cwm a few months back I ran into the same issue, but it was solved by switching to amon ra and charging the dead battery once in a standalone charger.
***EDIT: I just came across this thread when doing a search:
http://forum.xda-developers.com/showthread.php?t=1489687
This should help you out.
randpost said:
have you tried turning your phone off then putting in the dead battery. place it on the charger while the phone is still off and try to charge it. enable/disable fast boot may help also.
when testing cwm a few months back I ran into the same issue, but it was solved by switching to amon ra and charging the dead battery once in a standalone charger.
***EDIT: I just came across this thread when doing a search:
http://forum.xda-developers.com/showthread.php?t=1489687
This should help you out.
Click to expand...
Click to collapse
Thanks. Im still toying with it but so far all I get is a flicker of the orange light after I hit the power button. Will try with fast boot enabled.
Sent from my ADR6425LVW using Tapatalk
pmania said:
Thanks. Im still toying with it but so far all I get is a flicker of the orange light after I hit the power button. Will try with fast boot enabled.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
excerpt from another post:
"I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!"
If it comes down to it, just take the battery into VZ and get a defect replacement.
randpost said:
excerpt from another post:
"I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!"
If it comes down to it, just take the battery into VZ and get a defect replacement.
Click to expand...
Click to collapse
I did something similar to this. Reboot phone to bootloader while plugged in, then swap to the dead battery then rebooted. Then I let it charge to about 40% before I had to take it off. It died a while ago and the charging problem persists.
Sent from my ADR6425LVW using Tapatalk
pmania said:
I did something similar to this. Reboot phone to bootloader while plugged in, then swap to the dead battery then rebooted. Then I let it charge to about 40% before I had to take it off. It died a while ago and the charging problem persists.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
try the recovery method with the battery in question, meaning: don't use the extended. just throw the the phone onto usb with the dead battery and try adb recovery.
hopefully you can save yourself a trip to VZ.
randpost said:
try the recovery method with the battery in question, meaning: don't use the extended. just throw the the phone onto usb with the dead battery and try adb recovery.
hopefully you can save yourself a trip to VZ.
Click to expand...
Click to collapse
I will tomorrow. I don't have computer access now. I'll keep the extended charged though
Sent from my ADR6425LVW using Tapatalk
pmania said:
I will tomorrow. I don't have computer access now. I'll keep the extended charged though
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes! Good luck and happy Easter!
randpost said:
Let us know how it goes! Good luck and happy Easter!
Click to expand...
Click to collapse
Welp I just tried the adb reboot recovery and I am still getting the flashing light.
Will try again.
When this happened to me I had to keep plugging and unplugging the charging cable while holding the power button to get it to turn on. It's worth a try!
I did what others did n plugged into computer n booted to bootloader/ect
My rezound died this week end and wouldnt charge. Took it the VZ store and found out they no longer had in-store tech support. Anyway, the in store person concluded the charge port somehow wouldnt take a charge. Ended up calling tech support for a replacement. Should be here by Tues
Well I figured it out. I just got home to try again and I looked at the cmd window. It turns out I only typed "adv reboot recover" so yea my bad . Worked like a charm!
Sent from my ADR6425LVW using Tapatalk
pmania said:
Well I figured it out. I just got home to try again and I looked at the cmd window. It turns out I only typed "adv reboot recover" so yea my bad . Worked like a charm!
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
awesome man. glad you got it working.
So yea phone wont boot or charge or do anything. No a single screen will turn on i press the power button and it just stays the way it is dead. Im pretty convinced that i bricked it since i cant get to anything. All i was doing was making a backup and then when i went to flash the zip file it said no sdcard. So i did what i always do with this error bull the battery take out sdcard put it back in and go back to recovery to try again. Except this time it wont power back on into anything. Is there any hope for me?
What recovery did you have installed?
con247 said:
What recovery did you have installed?
Click to expand...
Click to collapse
i had amon ra recovery i know there were problems with cwm but i had amon ra and i cant get to it either
Leave the battery out and make sure it is unplugged from USB. Do that for like an hour.
con247 said:
Leave the battery out and make sure it is unplugged from USB. Do that for like an hour.
Click to expand...
Click to collapse
ok ill try that and get back to you.
It probably isn't dead. I have heard this happening before and leaving it without the battery or USB connection for several hours fixed it.
con247 said:
It probably isn't dead. I have heard this happening before and leaving it without the battery or USB connection for several hours fixed it.
Click to expand...
Click to collapse
Same concept as with computers I assume. By leaving it disconnected it allows all the capacitors to drain which means anything funky going on with the phone should "reset"
Sent from my ADR6425LVW using xda app-developers app
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.
So I have a verizon s4 (rooted) and it is bricked. If I take the battery out and put it back in the screen shows "Samsung" and then goes black and nothing else happens. I cant get it to start in bootloader or recovery mode either.
I am not sure if or how this is relevant, but I have been having issues with the power button, meaning that it wouldnt work when pressed except sometimes if I held it down long enough the "shut down/reboot" option showed up. In short I am not so convinced that it is working properly or maybe even at all.
Any help would be appreciated
Were you doing anything when it happened? Trying to install a rom, recovery etc?
Sent from my NCC-1701 using Tapatalk.
riker147 said:
Were you doing anything when it happened? Trying to install a rom, recovery etc?
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
no, I was having an issue with my internet and I took out the battery hoping to restart it and then this happened
pie are squared said:
no, I was having an issue with my internet and I took out the battery hoping to restart it and then this happened
Click to expand...
Click to collapse
Stupid suggestion, but try plugging the phone in to charge. I had some odd things happen to my phone where it would try to boot and continue to shut down. I knew I had charge on the battery, but when i plugged in the phone to the wall adapter, it acted like the battery did not have any power left. Once charged enough to boot, the phone would work fine.
Skeetch79 said:
Stupid suggestion, but try plugging the phone in to charge. I had some odd things happen to my phone where it would try to boot and continue to shut down. I knew I had charge on the battery, but when i plugged in the phone to the wall adapter, it acted like the battery did not have any power left. Once charged enough to boot, the phone would work fine.
Click to expand...
Click to collapse
Just tried that, didnt help
I guess what I am looking for is a way to take over the phone via a computer and somehow force it to behave
Skeetch79 said:
Stupid suggestion, but try plugging the phone in to charge. I had some odd things happen to my phone where it would try to boot and continue to shut down. I knew I had charge on the battery, but when i plugged in the phone to the wall adapter, it acted like the battery did not have any power left. Once charged enough to boot, the phone would work fine.
Click to expand...
Click to collapse
Additionally, when I did plug it in it made no indication of being plugged in (the light didnt go on, the cahrging battery picture didnt show up, nothing)
pie are squared said:
Additionally, when I did plug it in it made no indication of being plugged in (the light didnt go on, the cahrging battery picture didnt show up, nothing)
Click to expand...
Click to collapse
Maybe your battery is hosed or this is worth a call to Samsung and maybe they can perform a repair if need be
Skeetch79 said:
Maybe your battery is hosed or this is worth a call to Samsung and maybe they can perform a repair if need be
Click to expand...
Click to collapse
I guess I can try someone elses battery and see what happens, otherwise I dont know if my warranty will cover it cause its rooted and it turns on long enough to show the open lock and "custom"
Ok, I tried using someone elses battery still no luck...
Sent from my SM-T520 using XDA Premium 4 mobile app
install adb shell and see if you can boot into recovery or bootloader from there
pie are squared said:
Ok, I tried using someone elses battery still no luck...
Sent from my SM-T520 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
looks like your S4 is toast most likely
52brandon said:
install adb shell and see if you can boot into recovery or bootloader from there
Click to expand...
Click to collapse
How do I do that?
Sent from my SM-T520 using XDA Premium 4 mobile app
pie are squared said:
So I have a verizon s4 (rooted) and it is bricked. If I take the battery out and put it back in the screen shows "Samsung" and then goes black and nothing else happens. I cant get it to start in bootloader or recovery mode either.
I am not sure if or how this is relevant, but I have been having issues with the power button, meaning that it wouldnt work when pressed except sometimes if I held it down long enough the "shut down/reboot" option showed up. In short I am not so convinced that it is working properly or maybe even at all.
Any help would be appreciated
Click to expand...
Click to collapse
I am having the same issue - http://forum.xda-developers.com/galaxy-s4-verizon/help/gs4-shuts-startup-t2823928
Any luck yet?