Hello. I'm super new to this forum. I created this account and thread because I'm a bit desperate. I'm no expert in this so I'll try to explain the situation the best I can. I'd like for people to try and do the same, because, as I said, no expert.
The situation is this: my phone is known as the LG G3 Beat (D722). One year ago, I decided to root and also install a custom rom (CM12.1), which worked perfectly. A few months ago, I changed it to CM13. Worked great too.
3 days ago, I left my phone charging while I went away for a few minutes (maybe 10-15min). When I came back, the phone was completely dead. It won't turn on, it won't boot to TWRP, it won't light anything, no nothing. I know it was working because, before I went away I listened to my notification ringtone, and I ignored it because I was busy. I need some help because I think the phone somehow hard bricked.
Here's the info for tl;dr guys:
- D722p with CM13 installed
- Was charging
- Dead after checking the phone... Can't boot, go to TWRP, connecting the charger won't do anything nor connecting it via USB to the PC.
- Taking the battery / SIM out for a few minutes... connecting the charger without the battery... Those won't work.
So, possible things that happened in my opinion:
- Charger had some issues (it was faulty, but if left still, it would charge okay) could've possibly damaged the battery, making it useless (although, the battery looks fine).
- The phone's "motherboard" was fried because of the 1st thing mentioned, which I don't want to say it did.
I really think there's a way to recover this phone. And I'd love some help. Thanks in advance.
Related
Edit: Before you proceed, let me make clear the problem is already fixed!
Hey,
I'm terribly sorry to dilute this forum with this thread, but I really need some help over here.
Let's start of with some information about my phone. Obviously, it's a DHD and I've had it since november. It's been rooted (radio S-Off ENG H-Boot SuperCID etc.). I proceeded to install revolution HD, then CM7 and a phew tweaked CM7 mods. About 2 weeks ago, I also flashed LordModHD kernel with an undervoltscript (UUV). I tried PUV, but my phone would freeze, so I sticked with UUV. It never felt extremely hot, so there was no indication that my DHD was on the edge of failure.
I don't know if the following is relevant, but I'll post it anyway:
Everything worked fine, untill a phew days ago. I tried flashing the original CM7, instead of [email protected], but whenever it rebooted, launcherpro would force close. So I was forced to do a data wipe and start from scratch. Although this did work, I couldn't get titanium back-up to install. Everytime I tried to install it, my phone would reboot.
This didn't work out for me, so I decided to do a nandroid. Now my phone was back to normal. Actually, everything worked like it should, except for Gmail. Gmail would leave my read messages "unread", which was a bit annoying but didn't seem like such a problem.
Now the following is important:
Today I woke up to my alarm (which is my DHD) and I set it to snooze a couple of times. Then I decided to wake up and leave my DHD on the charger and go eat breakfast. Now a few hours later I came back to my DHD to read any new messages, only to find out it wouldn't wake up. I instantly panicked and tried every button combination I could think of. When I came to realize none of them worked, I decided to pull out my battery and put it back in, but still nothing happened. I tried this a few times, wiping the battery and blowing in every corner of my DHD. Sadly, none of these things would have any effect.
What can I do now, besides tell Vodafone to replace my DHD with a new one?
Tl;dr: Rooted my DHD months ago; it stopped working this morning. What do?
vinnieminnie said:
Hey,
I'm terribly sorry to dilute this forum with this thread, but I really need some help over here.
Let's start of with some information about my phone. Obviously, it's a DHD and I've had it since november. It's been rooted (radio S-Off ENG H-Boot SuperCID etc.). I proceeded to install revolution HD, then CM7 and a phew tweaked CM7 mods. About 2 weeks ago, I also flashed LordModHD kernel with an undervoltscript (UUV). I tried PUV, but my phone would freeze, so I sticked with UUV. It never felt extremely hot, so there was no indication that my DHD was on the edge of failure.
I don't know if the following is relevant, but I'll post it anyway:
Everything worked fine, untill a phew days ago. I tried flashing the original CM7, instead of [email protected], but whenever it rebooted, launcherpro would force close. So I was forced to do a data wipe and start from scratch. Although this did work, I couldn't get titanium back-up to install. Everytime I tried to install it, my phone would reboot.
This didn't work out for me, so I decided to do a nandroid. Now my phone was back to normal. Actually, everything worked like it should, except for Gmail. Gmail would leave my read messages "unread", which was a bit annoying but didn't seem like such a problem.
Now the following is important:
Today I woke up to my alarm (which is my DHD) and I set it to snooze a couple of times. Then I decided to wake up and leave my DHD on the charger and go eat breakfast. Now a few hours later I came back to my DHD to read any new messages, only to find out it wouldn't wake up. I instantly panicked and tried every button combination I could think of. When I came to realize none of them worked, I decided to pull out my battery and put it back in, but still nothing happened. I tried this a few times, wiping the battery and blowing in every corner of my DHD. Sadly, none of these things would have any effect.
What can I do now, besides tell Vodafone to replace my DHD with a new one?
Tl;dr: Rooted my DHD months ago; it stopped working this morning. What do?
Click to expand...
Click to collapse
isn't your battery dead? or youre charger? did you try to load it from a usb on a computer?
Well, that could be the problem. I used to get 60 hours out of one charge. Yesterday I put it in the charger and also used the wifi hotspot function. It dropped 5 percent in those few hours, but I just figured the hotspot function would cause a massive battery drain. Yesterday I put it in the charger at 7%, which is very unusual for me. I almost never consume 93% on one day, but again, I figured it was from the use of the hotspot function.
I plugged it in my computer now, but it still won't show any sign of life.
Try another battery, try another charger, try turning on the charger (i know this has happened to me) Try twisting the head of the charger completely into place as this can stop the charger from getting through, try using simply the usb cable plugged into a pc / mac.
Chances are this will thread will get deleted or moved, try to keep it in the Q+A area in future, if you get it working then let ppl know so it can be removed.
Good luck.
EDIT: You can grab a cheap battery from amazon for like £6 i got one and it lasts the same as the normal DHD one, it says it's 1600mah but i doubt it is, infact i'm sure it's not.
vinnieminnie said:
Well, that could be the problem. I used to get 60 hours out of one charge. Yesterday I put it in the charger and also used the wifi hotspot function. It dropped 5 percent in those few hours, but I just figured the hotspot function would cause a massive battery drain. Yesterday I put it in the charger at 7%, which is very unusual for me. I almost never consume 93% on one day, but again, I figured it was from the use of the hotspot function.
I plugged it in my computer now, but it still won't show any sign of life.
Click to expand...
Click to collapse
or your dhd charging point (the micro usb) is faulty then it wouldn't charge either
Now that I've had some more time to think about it, I think the battery is indeed out of juice. It had 7% left last night, so that might have just been enough to get through the night and wake me up. But when I got to get breakfast, it must have died on me.
Now if this hypotheses is right, I just need to figure out how to get charged again.
I use the regular charger, so there is no on/off button (for as far as I can see). There are 3 components that might have failed on me:
-The charger that gets plugged in to the powernet.
-The cable that connects my DHD to the charger.
-My battery
-Micro-usb connection
I've connected it to my computer now and it still doesn't work. So we can safely asume that the charger is not the problem here.
Now how would I be able to check wether it's my battery or cable that has failed me? I have no spare cables or battery.
I could go up to the Vodafone shop and ask them to replace one of these two and see if it works. Does anyone have a better idea?
Btw, if this thread really violates the rules, feel free to move it before I get my question, but please don't delete it. You've been a great help so far, let's get my DHD running again.
Edit: OMG it just flashed a little when I tried moving around the cable. I suppose I somehow wrecked the cable in the past few days.
I guess there's no other option than to get a new cable from Vodafone.
Edit2: Yay, it works once again. I can't seem to reproduce the problem, but there's definately something wrong with one of the components that compose my juicepump.
I'll figure out what component to replace myself, thx for the help guys.
Mod's can delete this thread now.
vinnieminnie said:
juicepump.
Click to expand...
Click to collapse
Made my day, love it
I'm glad it seems to be fixable. I'd hate to have gone through all of that reading for nothing. Post a pic of a juicepump when you find one, just so we know.
Try checking the contacts of the cable. It is possible that it was a faulty product, just as my cable. Stable contact was missing just inside the microUSB plug. If you like mending stuff, you can try to locate the flaw by flexing the cable and checking the contact with a neede, if you don't... well, a cable is cheap compared to a new handset
Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c
Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.
Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?
Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
LizardProtection said:
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
Click to expand...
Click to collapse
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
de4life said:
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
Click to expand...
Click to collapse
That seems to be exactly my problem! Thanks!
About a week ago, with my battery at 39% i plugged my z5 premium in to charge and it never came back on again.
I have tried all the usual tricks, pwr and vol up, removing the battery, the sim slot button, and pretty much any combination of buttons and still nothing.
It will charge just fine, but will only reach the white sony xperia screen and no further. it will flash up the white screen then go black with the notification light flahing red 3 times and then staying red. once or twice it has started to load the 'powered by android' screen and then just blackness. If i hold vol down and plug into laptop the notification light will turn blue and it shows up as 'adb android device'. Thats the extent of the life left in it.
So what would people suggest as my next step? is it still possible to recover the data thats on the phone or is it a total loss?
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Pixelado said:
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Click to expand...
Click to collapse
hello,
im having the same issue, but how it would be flashed and the computer didn't detect it?
what's the trick in that? thank you
Nidhal AKA the king said:
hello,
im having the same issue, but how it would be flashed and the computer didn't detect it?
what's the trick in that? thank you
Click to expand...
Click to collapse
If your computer cant detect the phone, it could be one of the following:
- Bad usb cable
- Bad usb charging port on the phone
- Dead battery
- Dead motherboard
If your computer doesn't make any sound when plugging the phone in, then missing drivers shouldn't be the problem and you should troubleshoot each of the possibilities I mentioned.
Pixelado said:
If your computer cant detect the phone, it could be one of the following:
- Bad usb cable
- Bad usb charging port on the phone
- Dead battery
- Dead motherboard
If your computer doesn't make any sound when plugging the phone in, then missing drivers shouldn't be the problem and you should troubleshoot each of the possibilities I mentioned.
Click to expand...
Click to collapse
Thanks for the tips.. I will check again and i hope it will be detected.
Sent from my Sony H8416 using XDA Labs
2-minute reset.
I thought mine was bricked after only 2 months. I came across this fix on the Sony website and it fixed mine where it could work again. I had to factory reset it. It was just locking up and freezing. Be sure to hold that button in for 2 solid minutes. I watched the clock. Longest 2 minutes of my life.
https://support.sonymobile.com/glob...em-&-performance/i-cannot-power-on-my-device/
Pixelado said:
I had exactly the same problem over a month ago. I am pretty sure it happened because of liquid damage to my motherboard.
I managed to bring it back to life by flashing with flashtool and ticking ALL wipes and resets available.
It worked fine until it died for good weeks later (I had left it to charge overnight and there were no signs of life the next morning). After a quick visual hardware inspection (aka teardown) I concluded that the only solution was to replace the motherboard. I did just that, and every other component works fine.
TL;DR: Give it a go, flash with all wipes and resets offered by flashtool (you'll lose all data) and hope for the best. You better be looking at prospective phones in case your mobo goes kaput.
EDIT: wow I'm only 4 months too late haha. Pretty sure he has a new phone already xD
Click to expand...
Click to collapse
I am just adding a list of similar threads that have been recently posted regarding this strange sudden death issue, battery not charging, weird non-software bootloop.
Sudden Death
InfiniteBootLoop
Unable to Turn On
My Phone Just died (april2019)
Not charging (user is rooted though)
I think i will also collate many of the similar threads into titles and post it as a new thread. As this forum is extremely bloated and repetitive whilst simultaneously being confusing for some users.
I guess Z5P is old now, but trust me the XZ3 is complete garbage so support for Z5P should be much cleaner and better organised now.
Any news for this?
So I've had this phone for about a year now, loved it (other than the lack of custom ROMS but that was my own fault for not doing enough research to begin with..) Anyways, to the problem..
The phone ran completely fine for about 6 months, no issues whatsoever. Then, I cracked the screen while working (oops). I consider myself at least a bit knowledgeable when it comes to phone repair, as I have done many in the past successfully. I purchased a new screen off E-bay, and installed it. No issues other than it had a few weird spots on the screen but it was bearable so I was living with it. About a month later I started having charge port issues. I had to prop it up certain ways to get it to charge, etc etc. I looked it up and apparently many people had this problem. It was running fine still for about another month until the strangest thing happened that I've never seen before.
The batter would immediately say 100% when I first plugged it in, and after powered on, it progressively brings itself down to 0% and then dies completely. Never seen it before and couldn't find anything about it on the internet really.
I figured that it was probably just the battery crapping out on me, so I thought, if I'm going to keep this phone (can't really afford a nicer phone right now), that I may as well purchase a new charge port and battery and repair them both.
The repair went flawlessly. The charge port works again perfectly but the battery problem still remains. It still says 100% and gradually goes down to 0% and dies.
What is going on here? Any ideas? I am now trying a system restore (my phone was encrypted so I wasnt able to get into TWRP without remembering the password which I don't even remember putting on there). I did a wipe on the phone and now I am able to access TWRP just fine on my internal storage, is there anything that may be able to fix this? Assuming this is a software issue and not a hardware one? And if it is a hardware one, what could it be??
Thank you for your time!
EDIT:
I forgot to mention. About a day before the battery started doing this. I downloaded the magisk module "ACC" (Advanced charging controller), thinking it may be useful considering how weird my charge port thing was being. It completely made my phone unable to charge when plugged in. I disabled and deleted the module and it went back to the way it was before (it didn't have the weird issue of discharging constantly). The next day or 2 that's when it started discharging immediately and always says its at 100% when I first plug it in. Don't know if that's relevent or not but I figured I would add it.