I got myself a HTC One a few months ago and gave my trusty ol' HD2 to my wife who had just lost her Galaxy S2. The HD2 was always working perfectly. Soon after I gave it to her, she started complaining that the battery drained only in a few hours and that she constantly had to fiddle with it on it's docking station for it to charge.
Yesterday she gave it to me because it wouldn't charge anymore. Suspecting a dirty USB port, I sprayed some "contact spray" in it. I accidentally sprayed a little bit on the buttons as well but I immediately wiped the buttons clean.
Anyway, when I turned it on, the phone was going crazy. It looked like the home key was randomly being pressed. It would constantly go to the home screen or it would display the "Recent Apps" screen (I had flashed MIUI Android on it and the Recent Apps screen is what you get when you long press the Home button). After a while the home button stopped working altogether.
Anyway, it still won't charge. And when I hook it up to my PC, I get the message "USB Device Not Recognized - One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it."
Another thing I notice is that as soon as I take the phone out of standby, the battery gets hot and it drains very quickly. I already tried a few other batteries (I have another HD2) as well as different USB cables (and chargers).
I also did a factory reset (through MAGLDR AD Recovery) but that made no difference.
So are there some easy checks I can do to narrow down what could be causing this?
Thanks in advance.
Related
Hi everyone,
I have had some trouble with my Vogue. At first it simply would not turn on. I would get a red light when I plugged the phone in to charge it. I have been using my old phone for several months now. Today I went out to the nearest Bell store and it seems like anything new is going to cost in the $500 area because I still have 1 year left on my contract. So I have renewed my interest in getting my Vogue working again
The original thread describing my original problem (with the red light) is here:
http://forum.xda-developers.com/showthread.php?t=546674
I purchased a new battery and now when I plug it in on the USB I can turn it on (no lights, red, green, or otherwise) but it does turn on. It boots up just passed the blue “Bell” splash screen and then reboots. It does this over and over again.
I am able to get into the boot loader screen by holding down the power and camera buttons and pressing the reset button.
Any ideas on what I can do? Any suggestions are welcome.
Regards,
The Fish
Reflash your rom when you get to the bootloader screen.
If you are unlocked flash nfsfan or whatever, just rename the nbh file to 'VOGUIMG.nbh' and it will flash.
If you were on stock you'll need the nbh from the stock package.
OK, here is an update
I have tried a hard-reset (press Send and End buttons at the same time and press reset button). This worked but the phone still kept rebooting. Tried the original battery, phone booted a little further up before rebooting.
I got the phone into boot loader mode and left it plugged in on the USB cable for a few minutes. This time when I rebooted I became ecstatic. I got all the way to the “align your screen” stage before hearing the “phone is dying” sound and the phone turned off. So here is what I think may have happened:
I have long lost the home charger kit. So I have, for as long as I can remember, been charging it by plugging it into a PC via the USB. This is fine except that Windows will only power the USB for the device if there is a driver installed. The device/phone looks different to Windows when it is in boot loader mode then when it is fully booted up. If the device is so dead as to not even have a flicker of life I don't think Windows sees it.
I have been doing this tonight under Linux. Linux seems to either have the driver, a more generic driver or powers the USB all the time for any device. I noticed this same behavior when charging my Moto Razr the same way. Under Linux it just worked by plugging it in. Under Widows I had to install the driver. So maybe here is what happened.
The battery got SO dead that it was not able to boot the phone up far enough for Windows on the PC to see it, recognize it and begin powering the USB port. Perhaps leaving the phone in bootloader mode and plugged into a Linux box got the battery a little more charged till I got to the point of being able to align the screen.
Anyway, I am more then ever convinced that this is some kind of battery/power issue. The phone is now lying here powered up and charging (already at 20%). The carrier customizations ran, rebooted while I crossed my fingers, and came back up. I even called *BELL and got a message about activating my phone. Tomorrow if the phone is charged up and behaving normally I will get an ESN change done and be back in the world of decent smartphones. Man have I ever missed my Google Maps
The next step is to flash a more up-to-date ROM... if I dare mess with a good thing.
The Fish
I've seen a few people with the exact same problem around the web, but no one has ever posted a solution (if they ever found one).
The kids were playing Angry Birds on the Nook before dinner, when I went to turn it back on after dinner it wouldn't boot (was working when I put it down).
When I plug it in the wall charger the light is always green.
When I plug it into a computer USB port it is momentarily detected as omap 3630 instead of Nook Color like it used to, then windows reports that it's been disconnected.
It had been running CM7 for a few weeks off of emmc, but now I can't even get it to boot from a uSD card into CWM.
When plugged in (computer or wall charger) I can see the backlight turn on and off every few seconds.
No combination of button presses seems to have any effect (power, power+n, power+n+vol+, etc.)
Try holding the power button for a full minute... release and try turning it on again... see if that don't do it.
Thanks for your reply.
I wish that worked, but I don't even see the back light flicker on for a split second unless it's plugged into the wall or a computer.
It's a shame too, I got it as a Christmas present from the wife and our toddlers really loved to play the games on it. They keep asking where "bad birdies" went
Your problem sound similar to an issue I had with charging. I has a bad charger/usb cable. Its a known issue and BN will replace it for free. If you are registered, call BN support a request a new one. I have done this twice. Once when the end bent and a second time when I had a green N but not juice (just flicker and/or a 'plug in the charger' symbol). The NC requires more power than the typical usb charger/cable setup, thus spares usb chargers AND cables around the house do not work.
I hate to do this because it was so maddeningly frustrating to see the same thing posted in the thread about boot problems here and elsewhere, but it turned on today and I have no idea why.
I'd been messing with it for a few days and finally after an unsuccessful morning I left it on my dresser. I was in the kitchen making hot chocolate after playing in the snow with the kids when my two year old comes walking down the stairs with the nook and drops it at my feet. When I went to pick it it, it was in the process of booting. Whether he had done something to it or the short fall jarred something that was loose I can't say, but it now seems to be fine.
It had about 50% battery and the lights on the charging cord now respond like they should.
I have no idea what happened, but I wish I did so I could help others in my boat.
Still could be your charger/usb cable. When the charger/cable start going bad, it takes for ever to charge. Like all day just to get enough juice to boot up. If it dies again and doesnt reboot after its been on the charger for a few minutes or you're only getting a partial charge over night, its the charger and or cable.
It charged fine overnight.
There definitely must be something loose on the inside. If I give it a fairly significant whack (nowhere near a punch, but harder than a tap) it will reboot. I think it was a refurbished unit. The newer units seem to have serial numbers where the first four digits correspond to the year. The first four digits of this one are 2004! Looks like they never fixed what was wrong in the first place.
You just ran it too dead. It won't power on until it's established a decent charge first.
Sent from my MB865 using xda premium
Ok so:
Had CM 10.2 nothing else crazy (unlocked/rooted)
One day wifi started acting up (kept dropping) and USB started not being recognized.
Decided that maybe software might be acting up, switched to PA 3.99RC2: FUll Wipe, reinstall
Next day riding out to a meeting phone starts rebooting randomly while running Google maps and music
Keeps locking up and rebooting
Getting really hot
Turn phone off, go to meeting
Phone will not turn back on (solid red dot by usb)
Go home
Recovery no go, phone will not charge on wall or USB charging at all.
Red dot comes on when plugged into wall then turns off after about 30min, plugging/unplugging turns the solid red dot on again.
Put on wireless charger, for an hour
Phone boots up, at 60% charge
USB only charges phone does not send any kind of signal that it is there, no windows sound, nothing in device manager
No charging light at all, but the icon shows as charging.
Have airdroid installed, might try stock google, but it looks like something hardware related.
Has anyone experienced something similar?
Since I don't have ADB working how do I return to stock? (I presume unpackage the distro, airdroid them over, and then install individually?)
I called Google and they say that if they deem that the phone works, not only will they keep the phone I sent them, but they will also charge me for another nexus 4, this is kinda BS and wiht the Nexus 5 around the corner it seems even more BS.
Not sure what to do, as I have about another 1.5 weeks of warranty left. The USB seems jacked up but I am not sure if there are other diagnostics to confirm.
Slappy00 said:
Ok so:
Had CM 10.2 nothing else crazy (unlocked/rooted)
One day wifi started acting up (kept dropping) and USB started not being recognized.
Decided that maybe software might be acting up, switched to PA 3.99RC2: FUll Wipe, reinstall
Next day riding out to a meeting phone starts rebooting randomly while running Google maps and music
Keeps locking up and rebooting
Getting really hot
Turn phone off, go to meeting
Phone will not turn back on (solid red dot by usb)
Go home
Recovery no go, phone will not charge on wall or USB charging at all.
Red dot comes on when plugged into wall then turns off after about 30min, plugging/unplugging turns the solid red dot on again.
Put on wireless charger, for an hour
Phone boots up, at 60% charge
USB only charges phone does not send any kind of signal that it is there, no windows sound, nothing in device manager
No charging light at all, but the icon shows as charging.
Have airdroid installed, might try stock google, but it looks like something hardware related.
Has anyone experienced something similar?
Since I don't have ADB working how do I return to stock? (I presume unpackage the distro, airdroid them over, and then install individually?)
I called Google and they say that if they deem that the phone works, not only will they keep the phone I sent them, but they will also charge me for another nexus 4, this is kinda BS and wiht the Nexus 5 around the corner it seems even more BS.
Not sure what to do, as I have about another 1.5 weeks of warranty left. The USB seems jacked up but I am not sure if there are other diagnostics to confirm.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post...I'd return it all to stock and RMA it.
mrhiab said:
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post...I'd return it all to stock and RMA it.
Click to expand...
Click to collapse
Thanks for the tip, I was just wondering how this sort of malfunction happens. I never really used the USB port after I got wireless charging, so maybe some light dropping? I dunno
My girlfriend has been using a Galaxy Express for about two years now. I had an unofficial Cyanogenmod installed on it, but it was working fine. Yesterday, when she went to use her phone, she found that it wasn't responding. Plugging it in with the battery in would show the battery charging screen for about three seconds, then nothing. Plugging it in without the battery gave a rumble, but still nothing. Pressing Vol Up + Home when plugging it in showed that it started to go into Recovery, but then shut off again. I opened up the device to replug everything connected to the motherboard, and now the device no longer even rumbles and shows nothing on the screen. However, when I plug it into my PC, it detects that it was plugged in, but then plays the unplugged sound a few seconds after. What could have happened? Should I go deeper and reset the cables on the middle bezel? There really isn't much I can do at this point, and this device doesn't even have a dedicated forum, so I put this post here.
As a side note, although she had a rubber case on, my girlfriend had dropped the phone numerous times from the couch onto the carpet. It wasn't a large drop by any means, but it happened quite often.
So, any ideas?
OMIGHTY1 said:
My girlfriend has been using a Galaxy Express for about two years now. I had an unofficial Cyanogenmod installed on it, but it was working fine. Yesterday, when she went to use her phone, she found that it wasn't responding. Plugging it in with the battery in would show the battery charging screen for about three seconds, then nothing. Plugging it in without the battery gave a rumble, but still nothing. Pressing Vol Up + Home when plugging it in showed that it started to go into Recovery, but then shut off again. I opened up the device to replug everything connected to the motherboard, and now the device no longer even rumbles and shows nothing on the screen. However, when I plug it into my PC, it detects that it was plugged in, but then plays the unplugged sound a few seconds after. What could have happened? Should I go deeper and reset the cables on the middle bezel? There really isn't much I can do at this point, and this device doesn't even have a dedicated forum, so I put this post here.
As a side note, although she had a rubber case on, my girlfriend had dropped the phone numerous times from the couch onto the carpet. It wasn't a large drop by any means, but it happened quite often.
So, any ideas?
Click to expand...
Click to collapse
I think its died motherboard. My express died in the poket of my jeans)))Price of mother is about 34 euro. Now i am looking in some chines shops for cheap price.
OMIGHTY1 said:
My girlfriend has been using a Galaxy Express for about two years now. I had an unofficial Cyanogenmod installed on it, but it was working fine. Yesterday, when she went to use her phone, she found that it wasn't responding. Plugging it in with the battery in would show the battery charging screen for about three seconds, then nothing. Plugging it in without the battery gave a rumble, but still nothing. Pressing Vol Up + Home when plugging it in showed that it started to go into Recovery, but then shut off again. I opened up the device to replug everything connected to the motherboard, and now the device no longer even rumbles and shows nothing on the screen. However, when I plug it into my PC, it detects that it was plugged in, but then plays the unplugged sound a few seconds after. What could have happened? Should I go deeper and reset the cables on the middle bezel? There really isn't much I can do at this point, and this device doesn't even have a dedicated forum, so I put this post here.
As a side note, although she had a rubber case on, my girlfriend had dropped the phone numerous times from the couch onto the carpet. It wasn't a large drop by any means, but it happened quite often.
So, any ideas?
Click to expand...
Click to collapse
Hi,
my name is Mr. M. Yusuf and I would like to respond to this matter fisrtly the problem is the motherboard go to eBay and type GT I8730 motherboard and It should come up if you can install it it then that’s great but if you can’t don’t buy it take it to a nearby shop that fixes phone and they should charge you a maximum of £30 so I hope this advice would be able to help you.
Yours Sincerely,
Mr. M. Yusuf
Verizon V20, bought it new, no software mods.
I can't remember the error code, but if I shut down the phone and restart...for example, when I swap batteries, the phone gets stuck in "Firmware Update Waiting for any connection."
I found I can get to another menu by tapping the power button 7 times, but not much I can do but scan for wifi or shut down. After reading around, I found that I can start the phone just fine by shutting down, plugging in a charging cable, waiting for the battery icon, and then powering on.
So yes, so long as the phone is plugged in I can start it up, and I'm even using it now. But it's frustrating that I can't swap batteries on the fly, anymore, and I can get stuck without a phone. Happened 2x now, with a sick wife at home and I have no way to contact her.
What I know so far is that the phone is probably stuck in download mode. 2 things may have caused it.
1. I have been avoiding an update, up until yesterday, mostly just never a convenient time of day. Not sure if something got stuck in the boot command.
2. I was at the beach the other day before it happened. Phone wasn't near the water, but wouldn't surprise me if the charging port got sand or salt in it. I noticed it was harder to get a charging cord to lock in. Perhaps it thinks there's a data connection plugged in when there's not.
Ninety-9 SE-L said:
Verizon V20, bought it new, no software mods.
I can't remember the error code, but if I shut down the phone and restart...for example, when I swap batteries, the phone gets stuck in "Firmware Update Waiting for any connection."
I found I can get to another menu by tapping the power button 7 times, but not much I can do but scan for wifi or shut down. After reading around, I found that I can start the phone just fine by shutting down, plugging in a charging cable, waiting for the battery icon, and then powering on.
So yes, so long as the phone is plugged in I can start it up, and I'm even using it now. But it's frustrating that I can't swap batteries on the fly, anymore, and I can get stuck without a phone. Happened 2x now, with a sick wife at home and I have no way to contact her.
What I know so far is that the phone is probably stuck in download mode. 2 things may have caused it.
1. I have been avoiding an update, up until yesterday, mostly just never a convenient time of day. Not sure if something got stuck in the boot command.
2. I was at the beach the other day before it happened. Phone wasn't near the water, but wouldn't surprise me if the charging port got sand or salt in it. I noticed it was harder to get a charging cord to lock in. Perhaps it thinks there's a data connection plugged in when there's not.
Click to expand...
Click to collapse
Try to clean it out with the end of a safety pin
Sent from my LG-H918 using Tapatalk
I have a v20, and have the same issue, please help
Hello to all who view this,
I own an unlocked V-20 LG-H918 Its an unlocked T-Mobile variant that I use on Metro PCS, I have never had any issues, the phone works near perfectly.
I have a couple batteries which I switch out periodically, I just decided to switch to my backup battery to ensure that it was still okay, and charged... the phone refused to start, once I placed the new battery into it, instead it went to the "firmware updating screen waiting for a connection"
I was able to get the phone to start by pulling the battery and then plugging it into the wall PRIOR to starting it, and it started fine. however there is a reason I still use this outdated phone. I ENJOY IT. I would hate to end up replacing it, so i would like to know if there is a fix for this issue yet.
*for the record* I have not been able to ROOT this phone, I gave up about 10 months ago, and have had no issues, though as said I was unable to gain root acccess