I have no idea what went wrong or where. One day a few apps starting force closing. Then I got weird unlocking problems. Now google play crashed consistently on any search, as well as ****ing settings. I ****ing hate this phone.
-Rooted and unlocked via freegee.
-Installed clockwork over adb(everything was fine at this point)
-Flashed a few different ROMS
-Flashd beanstalk, and then the problems started.
-Can't get ****ing adb to connect no matter what so I can't flash a new recovery
-Considering beating in my phone with a bat.
Anyone have any suggestions for getting recovery working again? Clockworks app doesn't work, similar to what this fellow went through (and apparently solved) http://forum.xda-developers.com/showthread.php?t=2258671&highlight=can+t+boot+recovery
Haven't tried LGNPST because I have no idea what the acronym stands for and no one says what it is.
Refer to tinybin thread in android development
Sent from my Optimus G using Tapatalk 2
drwario said:
Refer to tinybin thread in android development
Sent from my Optimus G using Tapatalk 2
Click to expand...
Click to collapse
I've exhausted everything I could find through the teenybin thread. LGNPST and teenybin gave me back fastboot, but I still have no recovery.
Oh yeah, and a sweet bonus: My phone refuses to go past the boot screen when booting and adb on both my desktops refuses to recognize my device! Anyone want a free phone before I smash it to bits against my face?
Update: For all you poor fools who are following the same path, heres what happened.
Left it plugged in all night and it continued to flash red for a while, and then show a full charge screen, then turn off. Repeated this throughout the whole night.
Come morning I perform a hard battery pull via this thread: http://forum.xda-developers.com/showthread.php?p=45849420#post45849420
I wait a minute with the motherboard connector disengaged. Hold power button for 10 seconds. Plug back in, absolutely no change in my situation. I tried again for about 5 minutes, ditto.
So in conclusion, I broke my phone because I installed a custom rom and LG didn't want me to. I hope whatever team was in charge of developing this phone burns in hell like they so sweetly deserve.
**** you LG. ****. YOU. I want my ****ING money back. You make **** PRODUCTS.
Dude you are aware it's YOUR fault if any thing bad happens when you are playing around with a rooted phone. U installed it and its your own bad....
Sent from my LG-E975 using xda app-developers app
steffenbakke said:
Dude you are aware it's YOUR fault if any thing bad happens when you are playing around with a rooted phone. U installed it and its your own bad....
Sent from my LG-E975 using xda app-developers app
Click to expand...
Click to collapse
Yeah its my fault for installing a custom ROM. You wouldnt be saying this if a desktop or laptop magically stopped working after reinstalling windows or linux. If those were as randomly, stupidly risky, people would be ****ing in arms at microsoft, as they rightfully should be at carriers. Whatever man.
If you can't access recovery or the phone will not boot then adb won't work. You said that you do have the ability to use fastboot though. Have you tried flash twrp from fastboot?
Sent from my LG-E970 using xda app-developers app
Why you install recovery over adb? I mean, when you unlock with freegee it installs the recovery you want (cwm or twrp), so no need for adb.
Have you tried to KDZ a stock rom and do a hard reset?
putsometrebleinit said:
If you can't access recovery or the phone will not boot then adb won't work. You said that you do have the ability to use fastboot though. Have you tried flash twrp from fastboot?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I tried LGNPSTING a lot of things and now the battery is ****ed. Hard battery disconnect did nothing. It'll flash its light and maybe show the lg logo when plugged in.. but other than that its frustratingly dead.
Just sell the ****ng phone man...
You got frustrated due to a lack of patience. You can flash recoveries via fastboot. If you actually searched well you would have seen that.
Sent from my Optimus G using XDA Premium 4 mobile app
DeathmonkeyGTX said:
You got frustrated due to a lack of patience. You can flash recoveries via fastboot. If you actually searched well you would have seen that.
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesnt work, and never did. The ****ing phone drivers are so ****ty and proprietary, no computer I used would recognize my phone. I actually managed to flash the stock AT&T rom to my phone through LGNPST, along with a recovery, or so LGNPST said, but of course another problem had to come up. Fantastic ****ing phone here.
swashy said:
Doesnt work, and never did. The ****ing phone drivers are so ****ty and proprietary, no computer I used would recognize my phone. I actually managed to flash the stock AT&T rom to my phone through LGNPST, along with a recovery, or so LGNPST said, but of course another problem had to come up. Fantastic ****ing phone here.
Click to expand...
Click to collapse
Then it sounds likely that you're doing something wrong, have an antivirus conflict, or genuinely do not have access to one well-maintained windows machine.
swashy said:
I tried LGNPSTING a lot of things and now the battery is ****ed. Hard battery disconnect did nothing. It'll flash its light and maybe show the lg logo when plugged in.. but other than that its frustratingly dead.
Click to expand...
Click to collapse
You can melt the software side of these phones so badly and still recover with the Qualcomm tools after the fact, it's not even funny how bad things can go before no return. Flashing a rom didn't do this, period. I want to believe you just suffered from a fluke hardware failure. Even more so it sounds like the USB connector went ape and continued wigging out from there.
The universal drivers also work perfectly. Considering in every way this is the nexus 4 with an SD card slot and a better LTE amplifier, everything you're ranting about is invalid.
The phone is a sanctioned, flash to hell and back model. You need to do some soul searching and find out where YOU went wrong. Or at least get an el cheapo multimeter out and start checking continuity. If it turns out you broke the charging connector or the battery connector off of the board you can STILL be saved. Just put in some effort and try to find the root cause. Screaming and cursing on a random corner of the internet isn't solving your problem
Making up crazed excuses isn't doing any service to you or the other forum users either. Especially the driver ranting. They work flawlessly. Hell even the generic Google provided SDK abd driver works.
If you figure anything out we're here to try and get you back to good.
Sent from my Optimus G using xda app-developers app
-edit- and leave the battery disconnected for awhile. The reason I suggest holding the power button while battery disconnected is in the hope that it will drain any remaining current out of the phone. There's no documentation to say it does or doesn't. So let the thing sit and be absolutely sure it's got a chance to reset. And check the battery voltage to confirm if it's dead or not. Since the contacts will be right there when it's disconnected...
That red light flashing / lg logo when plugged in is exactly where my phone and others was when needing a battery pull. It's fixed every phone I've heard of in that state. Try it again?
The same thing happened to me twice before. Both times I was able to recover my LG you get back into my recovery screen. What works for me is using Lgnpst back to stock jb. Next I flashed both teeny bins. Immediately after flashing the teeny bins, I open my LG up and pulled the battery. I waited about 10 minutes attach the battery back into the LG. Booted to the device and a factory reset my holding the power button in the volume down button. After the the device finished the reset I was good to go and my LG back to normal. This is what works for me give it a try... And good luck.
Sent from my Optimus G using Tapatalk 2
Well, another free day off, guess I'll give it a go again.
The connection of the battery to the mobo is most definitely intact. Pulled the plug to the mobo for ten minutes, plugged back in.
It still just steadily flashes red whenever I charge it. Nothing.
I'll try holding the power button while its disconnected, but I don't have a multimeter to check voltage.
Edit: Something changed. After sitting with the battery disconnected and a rubber band around the power button for 20 minutes, it showed a battery with a charge icon, then nothing. Havent had a screen for awhile. Pressing the power button, nothing. Holding it for awhile gets the full-charge battery, and if I keep holding it, the google symbol, and then nothing. I guess I'll try pulled the battery for 20 minutes again, Maybe it didn't fully discharge?
Edit 2: I've been informed that after a hundred battery pulls, the battery probably has something physically wrong with it. ****ing phenomenal goddamned phone here!! Why do I pay tech companies money for **** again?
swashy said:
Well, another free day off, guess I'll give it a go again.
The connection of the battery to the mobo is most definitely intact. Pulled the plug to the mobo for ten minutes, plugged back in.
It still just steadily flashes red whenever I charge it. Nothing.
I'll try holding the power button while its disconnected, but I don't have a multimeter to check voltage.
Edit: Something changed. After sitting with the battery disconnected and a rubber band around the power button for 20 minutes, it showed a battery with a charge icon, then nothing. Havent had a screen for awhile. Pressing the power button, nothing. Holding it for awhile gets the full-charge battery, and if I keep holding it, the google symbol, and then nothing. I guess I'll try pulled the battery for 20 minutes again, Maybe it didn't fully discharge?
Edit 2: I've been informed that after a hundred battery pulls, the battery probably has something physically wrong with it. ****ing phenomenal goddamned phone here!! Why do I pay tech companies money for **** again?
Click to expand...
Click to collapse
go to a service, ask them if it can be repaired, if they say yes go home and wait for an idea
if they say no dont lose the hope
its a great phone, and as you see you are the only one with this problem
and with that angriness you will do nothing, remember you and only you are the responsable for any damage your phone suffers, not the developer of that rom
Related
I'm having a hard time turning my phone on while its charging. It is difficult otherwise, but impossible during charging. Am I the only one with this issue?
Sent from my PG86100 using XDA Premium App
I literally just experienced this, so frustrating. Especially with a case.
Sent from my PG86100 using XDA Premium App
Are you rooted and have clockwork? There are issues with it with power when off, not charging and could be result kept it.
I don't have clockwork, have the other one. Name escapes me currently.
Sent from my PG86100 using XDA Premium App
This is one of the reasons I am going for the SGS2. Most times I have to--have to--do a battery pull to get it to turn back on. Sometimes the SDcard too. Sometimes it doesn't even charge. Sometimes I charge it while on and wake up to a green light, phone locked hard off (requiring battery pull and sdcard pull), and when I boot it up (if I can) the battery is completely dead.
It's a major issue with the 3d. There have been a ton of threads. And BTW, it happens on rooted AND stock devices. My phone died last night. Took me 32 effin minutes to get it to come back on. One of the reasons I'm getting rid of it
sent from my DAMN 3D!!!
Success100 said:
It's a major issue with the 3d. There have been a ton of threads. And BTW, it happens on rooted AND stock devices. My phone died last night. Took me 32 effin minutes to get it to come back on. One of the reasons I'm getting rid of it
sent from my DAMN 3D!!!
Click to expand...
Click to collapse
2 days before release I stopped into my local Radioshack to play with the demo phone. I saw it turn on, we played with it. Powered off...and never came back on. One of my friends did that eventually too.
...can't say I'm not scared of that happening to me.
daneurysm said:
2 days before release I stopped into my local Radioshack to play with the demo phone. I saw it turn on, we played with it. Powered off...and never came back on. One of my friends did that eventually too.
...can't say I'm not scared of that happening to me.
Click to expand...
Click to collapse
I can believe it...
How the f this thing made it into production with this big of a software glitch Or whatever the he'll it is riddles me
Success100 said:
I can believe it...
How the f this thing made it into production with this big of a software glitch Or whatever the he'll it is riddles me
Click to expand...
Click to collapse
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
pinky059 said:
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
Click to expand...
Click to collapse
Actually I absolutely noticed this before rooting...but back then I barely ever powered off. Nothing to flash, no way to flash it. I'm pretty sure it was just the same except we had much much much less reason to power off and reboot.
daneurysm said:
Actually I absolutely noticed this before rooting...but back then I barely ever powered off. Nothing to flash, no way to flash it. I'm pretty sure it was just the same except we had much much much less reason to power off and reboot.
Click to expand...
Click to collapse
I never did. I could power it on no problem before rooting. Didn't flash anything (I like Sense, what can i say...)....anyways, I noticed it afterwards and maybe it is true what that guy at AlphaRev said, it is the way HTC designed it for some weird reason....
Not a big deal for me though, now that he told me that...
pinky059 said:
It's not a glitch. For some reason, HTC designed it that way. If the phone is off and rooted, but still connected to some sort of AC power or USB power, the phone is actually in recovery mode, however, the screen just appears black. You wouldn't even know it!! LOL.....but, if you pull the AC power or USB power from the phone, and wait like 5-10 seconds it will boot right up, no problem or issues.
Crazy, huh? It may be a bug with revolutionary root; I reported it to IMFDM or however you spell it and the above is what he told me.
If you noticed, before you were rooted, it wasn't a problem. Don't keep removing the case and pulling the battery, just wait a bit after you pull the plug, It will be good to. Trust me, I go through it regulary!!
Hope that explains it for you guys...and helps you out.
Click to expand...
Click to collapse
this happens to my coworker that has this phone, and she is NOT rooted. And the above method never worked for me. Ive done that a million times trying to get it back on. Thanks for the tip though..
This has happened to me as well several hundred times it seems! It also did it when the phone was new. We had gone away on vacation like the week after the 3D came out, my phone had died while we were out, I plugged it into the charger, went to power it back on a couple hours later, and NOTHING! Probably took me a good 20-25 minutes to finally get it to come back on, with me eventually pulling the battery. This was stock at the time.
My 2 biggest gripes with the 3D, signal/call quality, and the power on glitch...
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
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.
Hello,
So last night I was using my optimus g, the notification that my battery was too low came up, and the phone shut off. After that I went to charge my phone and the usual red light did not come up around the power button and the phone will not charge. There is no water damage or sudden incident that could have caused this to happen. AT&T will not replace the phone due to a small scratch on the front of the screen done a couple months ago. Does anyone have any suggestions about how to get my phone to charge and turn on again??
Any help is greatly appreciated! Thanks!
have you tried to hold the power button down for like 10 seconds? try a different plug outlet and plug it in and see what happens
If you can't get it working then send it in to LG since AT&T won't help you.
Have you tried a different charger? Tried usb charging? Somewhere in this forum are instructions for removing the back case and battery. Two others had similar problems and removing the battery helped.
Sent from my LG-F180K using xda app-developers app
Jank4AU said:
Have you tried a different charger? Tried usb charging? Somewhere in this forum are instructions for removing the back case and battery. Two others had similar problems and removing the battery helped.
Sent from my LG-F180K using xda app-developers app
Click to expand...
Click to collapse
Yeah, I tried a lot of different chargers, USB charging and different outlets. I will have to try to remove the battery i guess. AT&T told me that I could not have LG repair it because it has a small crack in the bottom left that I made a couple months prior to this happening. Do you know how to get to the thread about removing the battery? I cant seem to find it =/
Anyone have any other ideas?
Here's the thread for accessing the battery btw.
http://forum.xda-developers.com/showthread.php?t=2127122
Sent from my Optimus G
If that doesn't do the trick then replacing the damaged portion of the phone and then claiming warranty would probably work, especially since it's already bricked and you don't have to worry too hard about it not turning on again after you reassemble it because again, it's already bricked probably a whole lot cheaper than buying a new one off contract.
Sent from my LG-E970 using xda premium
DeathmonkeyGTX said:
If that doesn't do the trick then replacing the damaged portion of the phone and then claiming warranty would probably work, especially since it's already bricked and you don't have to worry too hard about it not turning on again after you reassemble it because again, it's already bricked probably a whole lot cheaper than buying a new one off contract.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
The only problem is that the crack is on the front class screen, and I have heard that the screen is hard to replace
Before you open it up and go fiddling around on the inside, try these (in order):
1. Hold down your power button for at least 15 seconds.
2. Plug in your charger
3. (If that doesn't work) Use a different outlet/adapter.
4. If all else fails, try the 15 second power button thing and then connect it to your computer.
My Nook Tablet's display wouldn't work once and it took me the better part of a week to figure out that holding the power button down for 10+ seconds manually turns it off (I was a noob). (I then plugged it into my computer instead of the charger and it powered on!) A lot of people forget to try the simple things first...
amazingbonz said:
The only problem is that the crack is on the front class screen, and I have heard that the screen is hard to replace
Click to expand...
Click to collapse
Ok, let me rephrase that. A new one is $450. You can get a screen/digitizer for ~$85. I'm not a math whiz but to me the difficulty is worth saving that much cash.
download mode
it could be a software problem try going into download mode (holding vol down and power then plugging it in at the same time) it may take a couple trys but if you can get into that then it could possibly be a software issue maybe its a prob with bootloader if it is try useing some teenybins somthing similar happened to me i unlocked the bootloader and everthing got better post back if you can get into download mode
I too have started having problems charging this phone when it goes all the way down which it does fast usually listing android operating system or my screen as the main culprit....try booting to bl then recovery and clearing cache and dalvic....I use twrp recovery and there no battery stat wipe function but in rom toolbox pro there is although the merits of such is questionable.....I also used a battery calibration app recently and it seemed to help... I've also had to plug it up and just leave it for a while whether it's convenient or not it works....???
I've wondered about awesome kernel cleaning script... As well as some of the battery saving apps in conjunction with Eco mode and power saver function.... I've used juice defender ultimate for a while and recently battery guru from Qualcomm and Antutu but same crash today leaving phone down 2 hours plus easily not to mention getting stuck in power save popup warning viscious cycle of popping up every keystroke is gonna get this device slammed up against a wall and I don't want to replace it but any help on this also appreciated....
Sent from my LG-E970 using xda premium
USB Cable
Have you tried another USB cable? :silly: I stopped using USB cords ever since my grandpa got a wireless charger (yes, my grandpa ) but you better be careful with those since not all of them are compatible with LG phones, check the reviews and device compatibility, mine is a Powermat 3X
im having the same problems too... using the latest cyanagen mod... the battery just doesnt hold the charges like it says and shuts off.. i need this phone as an alarm......
There's problems with fast charge for cm try turning it off its on by default
Sent from my LG Optimus G using xda app-developers app
Same problem ughhhhhhhhhhhhhhhhhhh
I have this problem now, and can't get it to work. Anybody figure it out?
So there seems to be a desease of optimuses
My phone was charging while I was sleeping, and I accidentaly putted my hand on my phone while I was sleeping, and the phone was seriusly hot! I got up, upluged the phone from the charger, let it cooldown, plug it in on another charger, the phone responded in the first place, but the red flashing light was coming up really quickly. I switched it of and on and now it is showing me the battery that is shown when the device is charging. Been doing this charge for like an hour or more, with varius attempts to switch it on but it still it wont switch on! Any tips or anything? I am going to leave it charging for a coupe of hours and see if I have any results...
My phone started having issues where it would randomly shut off and sometimes holding power for approx 20 seconds or so would turn it back on or other button combinations sometimes requiring me to force download mode. I have always been able to force it back on however previously when plugged into a charger the notification light wouldn't do anything.
It shut off yesterday and I have tried every combination of buttons for at least 30 seconds, including trying to force download mode with volume up and down and USB into computer and nothing. The difference this time every time I plug it in the notification light either is solid or pulsing rapidly and will not turn on or go to download mode.
Phone is rooted running paulicats aosp and has been since I got the phone 3 months ago, it was dropped in water the week I got the phone but was disassembled and cleaned that day with no issues until this last week.
Any help or input is greatly appreciated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bump
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yesterday my dna died while at a dealership then I went to plug it into my car charger and the led came on to indicate charging. The phone automatically booted into the bootloader at which point I selected reboot phone and after that it went black as if there wasn't enough juice to boot and shut off. Since then the phone won't charge. When plugged into the wall, no orange led comes on to show its charging and after being left plugged in over night I'm still having the same issue.
I've got a lot of important things on there and I really hope there's something I can do.
Thanks :crying:
it may be in a boot loop try booting into the boot loader and flashing twrp then boot into it and let it charge
Sent from my Nexus 7 using Tapatalk 4 Beta
Make sure your cable isn't borked. For some reason, the cable wires break at the connector on the small end. Try a different cable. The orange charging light should come on after about 5-15 minutes of charging depending how dead it is.
zachf714 said:
it may be in a boot loop try booting into the boot loader and flashing twrp then boot into it and let it charge
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
At this point the phone is refusing to do anything or at least appears to be doing nothing. Pressing the power does nothing and when plugged into any power source no orange led. I don't know how I would boot into the boot loader while the phone is in this state.
superchaos said:
Make sure your cable isn't borked. For some reason, the cable wires break at the connector on the small end. Try a different cable. The orange charging light should come on after about 5-15 minutes of charging depending how dead it is.
Click to expand...
Click to collapse
Thanks. I've tried several cables and from different charging sources, wall, computer USB and my car and none make the orange led come on. I've tried holding the power for 20-30 seconds to see if I could reboot it but that didn't work either. The phone has never been dropped on anything but carpet once or twice and never near any water.
dev/null/ said:
At this point the phone is refusing to do anything or at least appears to be doing nothing. Pressing the power does nothing and when plugged into any power source no orange led. I don't know how I would boot into the boot loader while the phone is in this state.
Thanks. I've tried several cables and from different charging sources, wall, computer USB and my car and none make the orange led come on. I've tried holding the power for 20-30 seconds to see if I could reboot it but that didn't work either. The phone has never been dropped on anything but carpet once or twice and never near any water.
Click to expand...
Click to collapse
I have this exact same problem; however, my phone came back in a few days? It seems to get stuck like that every so often but then comes back and has around 30-40% battery left. I am about to lock it and put it back to stock and get a replacement.
Were you running any ROMs? I'm running a clean stock ROM.
Maybe try to open it up and disconnect the battery. This is a common pro let on the Nexus 7 and usually people get it fixed by disconnecting the battery and putting it back on. If you feel comfortable opening the phone you could try that.
Sent from my HTC6435LVW using xda premium
Salsbar said:
I have this exact same problem; however, my phone came back in a few days? It seems to get stuck like that every so often but then comes back and has around 30-40% battery left. I am about to lock it and put it back to stock and get a replacement.
Were you running any ROMs? I'm running a clean stock ROM.
Click to expand...
Click to collapse
I'm running stock rom with root and clockwork. I've had the phone like that since late December and nothing wrong until now. Now that you mention though, the same thing did happened awhile back but like you it randomly started working again on its own. I hope it comes back soon.
Jaggar345 said:
Maybe try to open it up and disconnect the battery. This is a common pro let on the Nexus 7 and usually people get it fixed by disconnecting the battery and putting it back on. If you feel comfortable opening the phone you could try that.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I was going to disassemble it after finding a guide and almost purchased a replacement charging port for the phone thinking maybe it was broken or something but I may try that. Thanks.
dev/null/ said:
I'm running stock rom with root and clockwork. I've had the phone like that since late December and nothing wrong until now. Now that you mention though, the same thing did happened awhile back but like you it randomly started working again on its own. I hope it comes back soon.
I was going to disassemble it after finding a guide and almost purchased a replacement charging port for the phone thinking maybe it was broken or something but I may try that. Thanks.
Click to expand...
Click to collapse
Cool. Keep me updated. I'm very curious now.
When you hold down the power button for 10-15 seconds, do the led's on the bottom of the screen blink? I let mine drain all the way out. Plugged it in. the orange light was blinking slow. I held down the power button until after the led's blinked 13 times. I don't know why they blinked 13 times but they did. held down the power button again and it booted up.
When you connect it to your computer, is it found as a device through ADB commands? Is it listed as a drive attached to the computer?
Salsbar said:
Cool. Keep me updated. I'm very curious now.
Click to expand...
Click to collapse
Good news, I disassembled it and disconnected the battery from the mobo like another user suggested earlier and after putting it together and plugging it in it is charging and booted to recovery
superchaos said:
When you hold down the power button for 10-15 seconds, do the led's on the bottom of the screen blink? I let mine drain all the way out. Plugged it in. the orange light was blinking slow. I held down the power button until after the led's blinked 13 times. I don't know why they blinked 13 times but they did. held down the power button again and it booted up.
When you connect it to your computer, is it found as a device through ADB commands? Is it listed as a drive attached to the computer?
Click to expand...
Click to collapse
Prior to disassembling it no, the LEDs never blinked when holding it down and when I tried charging it through my computer USB port it was never detected. Everything seems to be fixed now but thanks for suggestions. I still don't know what happened but hopefully it was just a one-off thing
dev/null/ said:
Good news, I disassembled it and disconnected the battery from the mobo like another user suggested earlier and after putting it together and plugging it in it is charging and booted to recovery
So it does sound like a hardware problem. Maybe I'll return mine and get a new one.
Click to expand...
Click to collapse
Glad to hear your back up. Good job. It could also possibly be that the battery somehow got disconnected. I wouldn't return it unless it happens again. Just try not to let it die and I don't think it will happen again. Or if you drop it, it may also disconnect. But I wouldn't get a replacement unless the issue comes up again.
Sent from my HTC6435LVW using xda premium
If you get a replacement your phone will be unlockable.
Glad you found the problem.
For future reference, my experience when my android phone had died, always plug the phone into the wall. If not, it takes forever for the phones light to come back on. Its happened to me a bunch of times. Haha
Sent from my HTC6435LVW using xda app-developers app