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
I posted this in the noob thread and I'm not sure how posting a new thread will help but hopefully someone may be able to sort me out.
I was using my phone in the car about an hour ago, listening to music (3.5mm jack). At this point my battery was at 3%. I opened Snapchat and the camera was being weird; it had purple noise(?) lines all over the screen every time I pressed the screen to focus it which tells me the camera is stuffed for whatever reason.
Anyway, the phone died on me. I assume the battery died as it was already low. However, it then starts to bootloop about 4-5 times and only manages to reach the encryption screen once, at which point it just switches off. Again, I thought the battery died! So I walk in to my flat, plug the charger in and expect it to boot but nothing happens. At this moment, there is no LED light on the front to indicate charge despite having been on charge for over half an hour, there is no vibration or any form of life from the phone. It just seems to have flat out died on me.
Now I know people will say I dropped it or its water damage so right off the bat, it is neither of those. It was dropped around 3 months ago, once, on carpet, from about 1.5ft if that. Never seen liquid and never been pulled out in the rain or anything like that. Last night it charged fine and today it worked fine too. Now it's dead!
Is there anything I can do/try? The USB cable/charger are fine, I tested them with a volt meter. Other things I have done include trying to boot the phone in any way possible through a number of button combinations, with and without SIM/SD card and even tried to plug the cable into my laptop. It's simply dead. Finally, if this helps: the phone is stock apart from an unlocked bootloader. It is rooted and has xposed installed with 3-4 mods, none of which do a lot (Snappreffs, xnotifications, dpi manager etc). It is running old firmware (like from last May when I bought it. Just never got around to updating I guess!) but this has never caused a problem.
Thanks in advance for any help.
Edit: Phone now responsive after 45 mins+ of being plugged in. Charging and working fine. Weird af..Mods feel free to delete this thread.
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.
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Bootloops/shutdowns are going to corrupt your data. I would RUU the thing before looking for hardware trouble, which you've likely sorted out by replacing the battery (of course, we're assuming the new battery is good).
BUT before that, is there a memory test in the bootloader or recovery? If so, I would run that very first thing.
bluedimensional123 said:
Recently I posted about a problem others had as well - when under 50% ish battery, my HTC 10 would randomly reboot, and that would loop until it was plugged in.
Once plugged in and fully rebooted, the battery % reading would vary from where it was before to 1%. Also, certain apps' data or cache would be deleted. I would open, Macrodroid, for example, and it acts like it's the first time being opened after installation.
This has been exhausting, having to constantly be charging, staying above 60% - and even then it still happening. After it does, the apps whose data was cleared varied, and I wouldn't always know until I opened each.
So after this I dropped it and cracked the screen. I have fixed all of my HTCs before with various problems - M8, M7, DNA, Incredible, Max - so I decided to put in a new battery to hopefully fix the bootloop problem.
After watching a few disassembly videos, it seemed best to replace the screen when I opened it for the battery. So I ordered a screen, and waited more, constantly charging, restoring data to apps like Macrodroid and initializing apps all over again.
I finally have the new battery and screen. I have a few hours. I get out all my tools.
A few hours later, I have put it back together. It's like Medusa inside this thing! I was really being risky doing this last night, because I have a ton of work to do today, yet here I am typing this on my backup nexus 5x - so slow!
So the result? Success for the screen replacement, and the battery as well. But, now, it is bootlooping still! I plug it in, and two things:
Plugging it in does not stop the bootloop.
The charging LED does not light up.
So I am hoping someone may have some insight as to what I may not have connected properly. I can post pictures later, I'm not home right now.
I looked and looked and looked and cannot find where I went wrong. I am going to take it apart and put it back together if I can't find the error. Any ideas? Any other places I should post this?
I guess when I get home, assuming it has completely drained itself, I can plug it in, and see if it gets a charge, and if the LED illuminates. I am thinking: charging port is not properly connected back + the new battery did not fix the bootloop / battery issue.
Thoughts?
Click to expand...
Click to collapse
Whatever happened to your phone? I have the exact same problem. Infinite boot loop, no illuminated LED, and no way of getting into recovery or anything else with it bootlooping. It occurred after I made the mistake of trying to restart it at 25%. I have the new battery and screen. i'm going to attempt to open this Pandora's box. Seriously going to have to turn my back on HTC. The 10 is so full of software issue problems regarding the batteries that they never bothered to address.
I did the exact same thing a few days ago and my phone won't charge or boot, but I do think the problem is with the button strip, that's what i think, because i tried turning it on before re assembling it and it did turn on successfully and was charging normally but when i re Assemble it, the phone got this problem, now i think when i turned it on before assembling i pressed the power button with a screw driver because i couldn't press it with my fingers, I think there i messed it up, any advice how to fix the button strip and remove a slip nut would be very much appreciated
I had the exact same issue as you(shutting down at 50%), have you found any solution to it?
edit: I THINK clean flashing oreo firmware then latest RUU then twrp then lineage fixed my issue, charging to full rn will drain it over the next day and report back if its gone for good