Related
I'm curious to figure out the problems with my G1 while it's charging. Maybe some of you wise folks on here can help me out...here's the deal:
When I plug in my G1 to the wall charger, swiping from screen to screen twitches, sometimes sticks, pushing something on-screen is a nightmare, usually results in something being pushed that I didn't push, browser becomes a disaster (zooming in and out when I push something on the webpage) .. basically my phone just spazzes out.
When it does these things, I can push the red call button to put it to "sleep" then I unplug the charger, and push Menu to bring it back alive, and the problems are gone.
The problems only occur while it's plugged in and charging.
I've had this phone for around 8 months now, never had this problem until around a month ago. Thank you to anyone that can help!
Hi guys and gals!
I've been experiencing these problems for a long time, but it didn't piss me off enough till today. Is it only me? Whenever the phone is charging it takes me forever to turn it on. If I press the power button this stupid battery appears and nothing happens. The same if I hold the power for 8-10 seconds (hard reset). I always manage to turn it on somehow eventually but it can take a while and I never know what actually made the damn thing to come alive. Are there others out there suffering the same fate?
seems like the problem many are having with the usb charging port. My problem is that phone keeps charging even after the usb cable is disconnected. the phone thinks its still charging and goes through the battery charging animation yet the phone is not even connected. then the phone will not turn on at all. So the way I would turn it on would be to connect it to usb charging and wait 5 minutes, then click on the power button and hold it a few seconds. then the phone would turn on.
Here is a test you can do to confirm if the usb port is going bad. when the phone is off and won't turn on and battery charging animation is on, take a plastic strip and try to push in the usb pins inside the charging port. I mean, to push the pins inside the phone, straight back. then turn on the phone and it will turn on. if that is the case, then your usb port circuit has to be changed inside the phone.
pjm77 said:
Hi guys and gals!
I've been experiencing these problems for a long time, but it didn't piss me off enough till today. Is it only me? Whenever the phone is charging it takes me forever to turn it on. If I press the power button this stupid battery appears and nothing happens. The same if I hold the power for 8-10 seconds (hard reset). I always manage to turn it on somehow eventually but it can take a while and I never know what actually made the damn thing to come alive. Are there others out there suffering the same fate?
Click to expand...
Click to collapse
Yup, this happens to me too. But not really a biggy, more of an inconvenience, but an inconvenience that I could live with as I don't start/reboot my phone plugged in all the time and if ever, i just unplug it, start, and voila, problem solved.
I recently went on a 3 month trip. Before I left, my nook was working perfectly fine, when i got back, it didn't work at all. It's not dead because i left it plugged in overnight but it still didn't turn on. when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all. I can't get to recovery either.
This is a Nook HD, I believe it had CM11.
:crying:
Can this be fixed
or should i plan it's funeral
Same here
The same has happened to me. Screen doesn't turn on, but there is power, I can play it into my laptop and something is there, just not enough.
Good excuse for a new tablet!
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
tambourineman86 said:
It can be fixed. I've done it before. It has to do with the fstrim not being compatible with certain hardware versions of our device. If I can remember how I fixed it, I'll post it here. Trying to fix mine (again).
Click to expand...
Click to collapse
If would be fab if you could fix. Seems to be a common issue
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
tambourineman86 said:
I was able to fix it. YMMV.
1) Make sure the Nook is completely off and unplugged
2) Take out your sdcard
3) Hold down power button until the "battery depleted" icon shows, then promptly plug in the power before the icon disappears.
4) Let it set. The screen will go black, then it will attempt to boot and get stuck on the faint black screen, but this time, the charging light should stay amber.
If you want to be safe, wait until the device reboots itself. That could take hours though. If you're plugged into the wall wait at least 30 - 45 minutes before holding the power button down til it shuts down and then rebooting it (with the sdcard inserted).
Good luck, I hope it works for you.
EDIT: Also, I've read this may also have to do with wifi sending the device into some sort of strange bootloop when the screen is off. I personally believe it has more to do with the fstrim of JB but perhaps changing the wifi sleep policy may prevent this issue from happening again. I'm skeptical, but figured I'd pass that info along if anyone wants to try it as well.
Click to expand...
Click to collapse
Not sure we have the same problem. My screen doesn't come on at all, I don't get a battery depleted icon, no matter how long I hold in the power button. The only sign of life I get is when it's plugged in, when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
YMMV. But mine was the same issue. You should be able to get the icon by holding the power button down for 5 or 6 seconds. I'd say just eff with it until that icon appears. Try different button combinations. I used power and home trying to get the icon to show.
developerbuzz said:
when it goes from orange to green after about 10 seconds.
Thanks for the help, but I think it's a lost cause.
Click to expand...
Click to collapse
Anyway... since people are continually running into this kind of issue...
Give or take 21 seconds after turning orange it turns green during actual boot cycle into rom
Give or take 10 seconds after turning orange is cwm internal recovery.
After about 10 seconds the charging screen image disappears.
The charging screen image once finally no longer may not show up again until full power off/on (holding power button > 10 seconds or full battery discharge). Unplugging and plugging back in does nothing except making the device look bricked if there's too much light shining on it.
Device may not automatically leave the above state under a specific situation(s). May still need manual full power off/on.
Guessing 10 seconds could also be something else during the early/late boot process or other. The light changing color though should indicate that something is indeed happening.
Light should stay green during the boot process if its completely and fully no questions asked 100%. If you go based on that than yours doesn't appear to be completely fully charged which should either mean its turning on and using battery or not charging correctly.
The light turning off is curious. The device could be shutting off. If light comes back on a moment later then the device has rebooted. if the light stays off = n/a.
If its booting into recovery then the device would be available via adb. At that point it could be further evaluated.
On the off chance the screen was damaged it should boot and usb should be available via computer as well as adb.
If not then its probably toast unless its simply not getting a good enough current causing mislead battery stats and/or not enough energy to get to charging screen (bad wall power adapter in use, damaged power cable - though could be bad battery, defect, damage or whatever). OR there's some major error on behalf of the user happening (think should have tried that in the morning not while 1/2 asleep or came home from long trip and forget how that works).
Maybe the only other things are the emmc brick bug, was left sitting in the sun or heat or ocean air or other physical damage/defect even to the power port as well.
Or maybe it was mad that you left it. Shouldn't have hurt its feelings you know. At least its not crying battery acid on you.
That should just about cover everything except for the things not mentioned. Since its your device, you decide what happened.
Its complicated so anyone see any improvements, clarifications, or mistakes? Please put it in a post.
Jsorren said:
when i plug it in the LED goes from orange to green and then off (or green to orange, i can't remember). The screen doesn't turn on at all.
Click to expand...
Click to collapse
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
sandsofmyst said:
Bumping this thread to make it aware that there is a real answer. I have been able to duplicate this problem and rather easily too.
The problem is indeed from bad power. The device isn't receiving the correct amount of power needed to charge and start from a fully discharged battery.
To safely* duplicate this you can use a usb extension that isn't fully connected to the nook power cable. You may need to fully connect it first then slowly disconnect/connect till the light turns green when it should actually be charging. It won't actually charge in this state, or if it is, its very little and the battery percentage will continue to drop.
Leave the cable as is and unplugged. After the tablet is fully discharged, connect the usb cable. The light will change through the modes and turn off. The device will not turn on.
There are probably other ways to cause the problem like for instance a portable usb battery that doesn't put out enough juice (not the orange kind). Etc.
* It didn't hurt mine, but not my fault if it breaks your device.
Click to expand...
Click to collapse
I actually ended up fixing it yesterday!! I haven't touched it in about 3 months, and I was planning on just throwing it out getting rid of it some how. For the heck of it, I decided to plug it in, assuming that it was gonna go through the same process. But this time it went from green to amber, but it never went off. So I pressed the power button and the battery icon appeared. This was a really good sign. So I left plugged in for about 5 to 10 minutes then tried to power on.:fingers-crossed: As soon as I saw that '' Nook" boot up screen, my heart stopped. It booted up perfectly and I almost blew up from excitement :victory:. So I then flashed the stock firmware back onto it, so this would never happen again.
I guess the battery had to be completely depleted or just had to cool down. Idk but either way this was one heck of a miracle
So I recommend for anyone having this problem to just leave it off and don't mess with it. I wouldn't say for 3 months like I did but maybe test it each week or wait a month if you have good patience
Wow. Man, that's awesome! Glad you posted that update on it. Thought if you had posted an update it would be the opposite as in trashed it
Actually, I guess only you could answer if you had also moved/unplugged the power cable from the wall adapter or put it into a different wall adapter, etc. Thinking there could have been a difference there.
These modern day devices are so finicky, guess anything is possible. Like you say, maybe sitting without power is another answer.
From some experimentation I have etermined that your power adapter (that plugs into the outlet) is the issue. It does not like to be leaft plugged in indefinately. It will continually use power even when the nook is not plugged in.
Also, if you use a differnt adapter you will have the same problem unless it is also of the exact same voltage and amps.
Hi
I’m wondering if anybody has any advice regarding my problem. I have looked here and tried what has been suggested.
My stock, never rooted, never flashed, Xperia T (think it was Android 4.3 but can’t now check, the latest Sony rolled out) was working fine until yesterday. I was on a plane and noticed it had 20% battery life left so I plugged it into the onboard USB port. The problem is I think I hay have plugged the cable into the port the work way round – not the connection on the phone, but the actual USB socket. This should be impossible but somebody obviously had broken the port and it turned out the cable could be plugged in both ways! (I don’t know if it was plugged in the wrong way round but is the only thing that could possible explain the sudden death.)
Could this have bricked it? I suddenly couldn’t get a red light to show charging and holding down power on and volume up or down does nothing. I tried charging overnight via a wall socket when I got home but the result is still the same. Just a black screen and no sign of life. I have also tried plugging it into a computer with Sony’s PC Companion but as the phone is not ‘on’, it can’t be found.
Does anybody have any advice where to go from here? I’m more concerned about some recent data from holiday on the phone than the actual handset itself. If the phone is dead, is there any way to read the internal memory?
Thanks
Try this: Unplug the charger, press the power button. The phone won’t power up because there is no charge left in the battery. But press the power button along and while doing so, connect the charger without releasing the button. Now, you will probably see the red light. Please don’t take off your finger from the power button for around 1 to 2 minutes when the red light for charging will glow continuously. If you feel tired holding it, you can try sticking a tape on it in it’s pressed mode. Once you are sure that the phone is now charging the battery again(red light keeps glowing even after the power button is released) kindly wait for 5 to 10 minutes or may be more before you press the power button again to power the phone up. Now the phone will be up and running
If that doesnt work maybe ur battery is dead or usb port broken
Thanks for the advice. I gave that a go after trying a 24h wall charge and not touching it (which did nothing).
So, I held the power down, plugged it in but nothing. I held it down for around 5 minutes both manually and then repeated the process using the rubber band trick to keep the button held down but no red light ever came on. I think I’m going to try a new battery as I genuinely see that I have nothing to lose as I doubt it will be possible for anybody to recovery data given as the phone can’t be switched on so if I break it further I’m in no worse position!
Thanks again for trying to help though!:good:
When I got my xperia t it was in described condition. I also tried everything (rubberband trick and so on) but the only thing working was to open it and pull and put in again the plug of the battery. After that it booted immediately and I got this sleep-of-death-thing nearly every day... Since I soldered the battery as described in this Topic it happens only ~once a week. Good luck!
SOLVED! In preparation for the new battery arriving, I decided to take the back cover off. I unhooked the top battery connector and decided to connect it back up again, just to see if it did anything. Plugged in the charger and a red light came on straight away! I let it charge for a good couple of hours and switched it on – not as easy without the case attached – and it worked. I’m so frustrated with it being such a simple issue as needing to disconnect the battery but even more frustrated with the design that it is meant to be a ‘sealed’ unit with a non-removable battery. I used to often need to disconnect my old Omnia II battery to restart it but that was a simple case of cover off, remove battery, replace battery , put cover back on, not the creaky, back cover fear of cracking exercise of yesterday. Still it’s working now and hopefully life in the old phone yet!
Isodrac said:
SOLVED! In preparation for the new battery arriving, I decided to take the back cover off. I unhooked the top battery connector and decided to connect it back up again, just to see if it did anything. Plugged in the charger and a red light came on straight away! I let it charge for a good couple of hours and switched it on – not as easy without the case attached – and it worked. I’m so frustrated with it being such a simple issue as needing to disconnect the battery but even more frustrated with the design that it is meant to be a ‘sealed’ unit with a non-removable battery. I used to often need to disconnect my old Omnia II battery to restart it but that was a simple case of cover off, remove battery, replace battery , put cover back on, not the creaky, back cover fear of cracking exercise of yesterday. Still it’s working now and hopefully life in the old phone yet!
Click to expand...
Click to collapse
Nice to see that bro!
Hi guys, I have a huge problem.
Currently I'm on vacation in Croatia, where it's around 38-40 C every day. One day I had to log into an unsecured wi-fi. I know, i shouldn't have done that but it was urgent. Well, the same night (while charging) my phone turned off itself and I had to turn it back on on the next day. It worked the whole day until I opened the camera. Suddenly the phone went off and I wasn't able to turn it on. At first I thought the battery has drained so I plugged it into the original OP charger (dash). It gets warm while charging, but the LED is not turning on. After an hour of charging I still can't turn the phone on. Not even after a charging over night. There's also no vibration after holding the power button, neither holding the power-button for 20 (or more) seconds . I can't even get into recovery mode by holding volume-down and power.
I'm on original Resurrection Rom.
Is there anything else I could try? Could it be that some hardware is damaged (overheated)?
Since I'm on vacation there's currently no way for me to do any kind of unbricking until I find some phone-repair service.
I'm not a pro, but Im pretty sure the problem occur on the hardware side since the phone is not taking the charge and no vibration
I once had an Android phone (not 3t), the same thing occured, the phone I had had some hardware damage near the battery so I experienced the same problems you listed, ended up getting a new phone
Overheating is probably not the issue, at least not the 40C air temps you mentioned. These devices can probably something like 60C (internal temp at CPU or battery) before seeing any damage. Lot of folks live where it's just as hot as where you are, if not hotter. So I have to think the device is designed to work under such conditions.
Try holding the power button longer (a minute or more). I don't know about this device. But on my old HTC M8, there were instances where the phone powered off by itself. And the power button needed to be held over a minute, to make it boot. Although no charge LED is concerning.
Mine did the same a few days ago, was tethering and the phone just shut off. Buttons didn't work, no vibration, no charge LED, no anything. Thought it died but after plugging it into a PC it was detected as QHSUSB_BULK (hardbrick).
But it turned on normally after a minute lol.
Hallo. Mine also crashed. I was in the sunset playing game and taking pictures. Then phone suddenly got so warm and lagged, It turned off itself. No reaction. I connected into charger and then turned on hopefully. I think you must take care, because it has metal body and easy heating, and when heating it's lagging and not works good
My opinion is that it's overheat problem
BTslo said:
Thought it died but after plugging it into a PC it was detected as QHSUSB_BULK (hardbrick).
Click to expand...
Click to collapse
You will see Qualcomm download mode message (QHSUSB_BULK) whenever the device is powered off. It needs to be powered on, at least to bootloader (or recovery or OS) for the PC to connect in any other way.
Update
After 3 days, it finally turns on and charges as expected. Don't know if it has to do anything with it, but i let it in the charger for 1 day.
but now another problem occured.
every time I press the homebutton the phone crashes and goes off. this only happenes if the fingerprintscanner is not requested.
i.e. unlocking phone with fingerprint, does not crash, but... pressimg homebutton to go back to home screen crashes.