removing gapps and a charging question - TouchPad Q&A, Help & Troubleshooting

I have the original charger, when I put the TP on the charging cradle, while it's off, it turns on. I don't like this. Any solutions?
I'd like to remove gapps and keep using F-Droid. Is this possible without compromising the system.
Thanks a lot.

nestaISright said:
I have the original charger, when I put the TP on the charging cradle, while it's off, it turns on. I don't like this. Any solutions?
Yes the solution is very simple and just a flash, follow this guide: PowerOFF
Click HERE for hp-touchpad-poweroff-prevents-battery Drain
I'd like to remove gapps and keep using F-Droid. Is this possible without compromising the system.
I do not know what could happen, do a back up first using TWRP. Then remove gapps and see how it goes, if it breaks anything restore from backup.
My recommendations is to start with a fresh install to use Fdroid, also follow this guide to get the most performance out of the tablet:
https://forum.xda-developers.com/hp-touchpad/general/hp-touchpad-optimize-android-swap-t3901773
Thanks a lot.
Click to expand...
Click to collapse
PowerOFF will keep the Tablet off, if it turn on by accident or by connecting a charger while off.
After PowerOFF is flash, it will be the default ROM selection on the Moboot Menu. Instead of starting any Android ROM it will turn off in the same way as selecting shutdown from Android or TWRP.
This is very important and will keep the battery working normally at all time.
Once the Tablet is place on any charger, it will wake up and start TWRP or Android. ( This is an extremely bad action to take on a device that runs on battery supply )
The default action should be stay off to protect battery drain.
Now the Tablet is on the charger and is off. If there is any changes to the electricity lets say a temporary on and off, then the Tablet will turn on again..
With PowerOFF it will shutdown, protecting the battery.

HP_TOUCHPAD said:
PowerOFF will keep the Tablet off, if it turn on by accident or by connecting a charger while off.
After PowerOFF is flash, it will be the default ROM selection on the Moboot Menu. Instead of starting any Android ROM it will turn off in the same way as selecting shutdown from Android or TWRP.
This is very important and will keep the battery working normally at all time.
Once the Tablet is place on any charger, it will wake up and start TWRP or Android. ( This is an extremely bad action to take on a device that runs on battery supply )
The default action should be stay off to protect battery drain.
Now the Tablet is on the charger and is off. If there is any changes to the electricity lets say a temporary on and off, then the Tablet will turn on again..
With PowerOFF it will shutdown, protecting the battery.
Click to expand...
Click to collapse
Thannks a million, as ever so helpful. I flashed it and it was nice to see that when the TP rebooted, among options at the first screen where you can choose WebOS, or whatver, a new addtion "power off." I did notthing and it shutback down. Thanks a lot.

Related

[Q] Galaxy Tab battery drains full to empty in 20 minutes

Yesterday morning I pulled the TAB from the net adapter. Immediately it beeped and turned off. Plugging it back in, the battery indicator went from 0 to 100% in 5 minutes.
Turning it back on, it died in 10-20 minutes.
Turned it back off again, fully loaded it again and played a movie on it, 50% back-light. It lasted for just 20 minutes.
I made a backup to SD, did a factory reset and charged the unit (powered off) to 100%.
Did a restore, and everything worked again.
Battery is still working at 80% after an evening of restoring apps and a night of stand-by.
What the heck happened?
perhaps one of your apps? try installing them a few at a time to see which app is causing it
info5i2002 said:
perhaps one of your apps? try installing them a few at a time to see which app is causing it
Click to expand...
Click to collapse
I also think it's a software problem, after the problem disappeared with the factory reset.
I'm going to check slowly which program is the culprit.
I just can't imagine that a program can stress the TAB so hard it realy drains the battery.
I think it could probably be a misguidance of the android OS from a wrong setting?
I had a similar problem but not nearly as bad as yours. I had my tab unplugged for a while and checked the batter: 30%. So that was fine so I opened up dolphin and INSTANTLY the screen went really dim and said I had less than 3% battery which I did not believe.
Turning the tab off and back on the battery was now at 27%. This only happened that one time and I havent seen it agian. Must be some weird battery level reading bug.....
I have the same situation and also make a backup and factory reset amd later a restore.
That was 2 months ago and until now it works like a charme.
Sent from my GT-P1000 using XDA App
Power off g tab drain the batt
I have my Galaxy Tab for about 3 days ago. Charge to 100% the battery, and then, I decide power off (totally) the Tab. Hold power button, and in the pop-up window, power off the phone!!
After a 1 hour, I saw the screen message with the android icon "POWER RESET or UPLOAD MODE"....and drain totally the battery!!!
What can I do???
See the attached image.......please help me!!
Only 2 things are likely to cause this, the battery being stuffed, or the battery stats database getting corrupted. You could try the "bump charge" method and see if it resets it. (Charge fully while on from AC, unplug, turn it off, charge for an hour or so from AC, unplug, turn it on, turn it off again once booted, charge for another hour or so, unplug, turn it on).
The battery stats can be wiped from the CWM recovery if you wanted to flash that, I'm not sure where the file lives to do it manually.
Dann said:
I have my Galaxy Tab for about 3 days ago. Charge to 100% the battery, and then, I decide power off (totally) the Tab. Hold power button, and in the pop-up window, power off the phone!!
After a 1 hour, I saw the screen message with the android icon "POWER RESET or UPLOAD MODE"....and drain totally the battery!!!
What can I do???
See the attached image.......please help me!!
Click to expand...
Click to collapse
Hi, just like to share my experience with you guys. I encountered the same problem as mentioned, especially the sudden request to shut down due to battery becoming 3%, although it has 50% left. I tried recharging a few times but the same thing happens, something, it will shut down at 30% battery power level. Then, one afternoon, while I was looking at my pictures (at Gallery), I saw duplication of my photos (3 times) that appeared on my gallery folder. But the key issue is I stored all these pictures (taken by camera or by transfer from PC) in the microSD card (8GB). I tried to do a deletion on the addition pictures (it showed 3, so I tried to delete 2). But to no avail, and the system keep processing even though I tried stopping it. After about 2 minutes, the promot came up, requesting me to do a shut down saying the battery level was low, although I have about 50% battery power left. So, I shut down the tab immediately and removed the microSD card. After that, I switched on the tab and it says 50% power left. But I have to make sure it is possible to utilize the tab until it drains out the battery. Finally, I managed to cross the 20% power level and the tab can still be used .
I was curious about my microSD card, thinking that it may be faulty. I used a pc to open up the content and I discovered the SD card has no problem at all, it didn't have duplication when viewed from the pc. For your information, I have installed "angry bird" onto the 8GB microSD card, I am not sure if it is causing any problem to the tab or draining power from it, because the download (from Goggle market) mentioned something about "preventing phone from sleeping - System tools". I am not sure how this is link to the duplication of the pictures in the gallery folder as well, but I am glad I have found the fault to the draining of the power by the tab.
I would suggest, before anyone proceed with the factory reset, do a check on your storage card or the apps that you have installed in your tab, try to solve the simple way and it can save us a lot of troubles .
I hope it helps............
Henry Lam
As knightnz mentions ~ It's the Battery Stats Database being corrupt.
To repair, simply:-
Connect the Tab to it's Charging Cable and ensure the Tab is switched Off.
Next, hold the Power On Button whilst at the same time touch and hold the screen.
You will notice the battery indicator will pop up.
The Tablet will now reboot.
Everything should now return back to normal.
This procedure can also be used for a Tab that refuses to switch on.
Should I do this when the tab is off? or when it is on?
I actually tried both, but I dont see "the battery indicator pop up" as mentioned.
Beards said:
As knightnz mentions ~ It's the Battery Stats Database being corrupt.
To repair, simply:-
Hold the Power On Button whilst at the same time touch and hold the screen.
Next you will notice the battery indicator will pop up.
The Tablet will now reboot.
Everything should now return back to normal.
This procedure can also be used for a Tab that refuses to switch on.
Click to expand...
Click to collapse
shinji21 said:
Should I do this when the tab is off? or when it is on?
I actually tried both, but I dont see "the battery indicator pop up" as mentioned.
Click to expand...
Click to collapse
Actually, I missed out an important ingredient ~ The Power Cable.
You need to have the Tab connected to your charging cable as if you were charging the Tab and the Tab switched Off.
Next, hold the Power On Button whilst at the same time touch and hold the screen.
Next you will notice the battery indicator will pop up.
The Tablet will now reboot.
Everything should now return back to normal.
I'll amend my previous instructions to include the Power Cable.
Beards said:
Connect the Tab to it's Charging Cable and ensure the Tab is switched Off.
Next, hold the Power On Button whilst at the same time touch and hold the screen.
You will notice the battery indicator will pop up.
The Tablet will now reboot.
Everything should now return back to normal.
Click to expand...
Click to collapse
This is not working for me. The battery indicator pops up, but nothing else happens. The battery indicator even does not do any animations.
Beards said:
Actually, I missed out an important ingredient ~ The Power Cable.
You need to have the Tab connected to your charging cable as if you were charging the Tab and the Tab switched Off.
Next, hold the Power On Button whilst at the same time touch and hold the screen.
Next you will notice the battery indicator will pop up.
The Tablet will now reboot.
Everything should now return back to normal.
I'll amend my previous instructions to include the Power Cable.
Click to expand...
Click to collapse
Hi Beards,
Sorry to ask again, is there any way to verify that it has been solved without really draining the power to 0%? Is there any clear indication?
Thanks.
Henry
loonyt said:
This is not working for me. The battery indicator pops up, but nothing else happens. The battery indicator even does not do any animations.
Click to expand...
Click to collapse
henrylam said:
Hi Beards,
Sorry to ask again, is there any way to verify that it has been solved without really draining the power to 0%? Is there any clear indication?
Thanks.
Henry
Click to expand...
Click to collapse
The trick is in holding the screen whilst powering up.... It bypasses the normal start-up routines, resetting any errors that would sometimes require a Factory Reset to correct.
This info was passed on to me by a Samsung representative.
Easy fix, get a replacement, thts bad hardware, shouldn't have a problem exchanging, assuming it was purchased thru an auth retailer. No sense in messing with software and having a headache over it.
Seriously, the press screen thing doesn't work at all. Eventually, I brought it to the service center to do a firmware upgrade and it is back to normal...............
New upgrade:
Baseband version: P1000DXJM2
Kernel version: 2.6.32.9 [email protected]#1
Build number: FROYO.DXJM4
The funny thing is my wife has a unit that was using the same version as mine (old version, we bought them at the same authorised dealer), but she did not encounter such problem. I am just puzzled.
It did not work for me either. Is the charging cable supposed to be plugged in to the power socket or just the cable? (I tried both and neither worked)
I also did a firmware upgrade with Roto JMIv2. And I still see the problem.......Anyone having any suggestions please?
If your GALAXY Tab is running from fully charged to flat in under 20 minutes I wouldn't recommend anything other then... Sending it back to where you go it from?!
It doesnt go flat in 20mins. As a matter of fact, it lasts a couple days with my work load. Its just that when i put it in standby mode let say overnight at 80%, when i turn it on in the morning the battery will be at 50-60%. But when i restart it will go back up to 78-79%.
So im not losing battery capacity here i believe, but its annoying to have inaccurate reading, especially when i am on a trip or sth.
Sent from my GT-P1000 using XDA App
I can understand your predicament, I have those "moments" before. Mine just dies off and need reset to get the battery back. The unknown is always not welcomed to all since we paid so much for them.

Curious about changing battery

In changing the battery, I turn the device off and when I do the device vibrates and the menu and back keys stay lite for a bit. So I am wondering, if I need to wait for those
lights to go out before pulling the battery out of my Note? Secondarily, is it ok to pull the battery without turning it off? I am thinking there might be a shut down procedure.
Anybody know?
thanking you in advance.
It's always best to wait for the phone to shut down before pulling battery. It's the same thing as on regular computers: if you pull power before it's down you might risk filesystem corruption and even unbootable system.
WereCatf said:
It's always best to wait for the phone to shut down before pulling battery. It's the same thing as on regular computers: if you pull power before it's down you might risk filesystem corruption and even unbootable system.
Click to expand...
Click to collapse
I agree. I always wait for the button lights to go off and a few seconds just in case.
I would also never just remove the battery without a shutdown except in the case of a crash.
So what you guys are saying is that from the time you confirm the shut down until the light go out, the device is processing data.
I suspected as much. Thanks for your thoughts.

Bricked Touchpad need help

NOTE - I added this post here thinking the CM9 experts could help. I then realized it should be in the Q&A section. If this does not belong here, I ask a moderator to please delete it.
I have been running CM9 nighties for some time now with no issues on my 16GB US WiFi only Touchpad. I installed TWRP and after some time decided to remove it and just use CWM. After trying several things from the posts (which would not work) I decided to remove CM9 completely then reinstall. This is where I got into trouble...
I loaded all necessary CM9 files in the cminstall folder on the Touchpad. I successfully ran ACMEUninstaller and got back to the WebOS language selection (i.e. the initial WebOS screen from factory). Instead of logging into WebOs (felt there was no-need since I never use it), I put the unit in Download mode (vol down + power). I then ran ACMEInstaller2. I received an error (text on the black touchpad screen which I assume is the bootloader) saying the needed files were not installed and something like "remove the wall". I thought I would reboot the unit and now log into WebOS and reinstall the CM9 files (thinking I made a typo when loading them). Now I cannot get the Touchpad to reboot - totally black and even when connected to the PC I dont get the USB connection sound.
Does anyone know if there is a hardware method to bring the unit back (maybe a different sequence of button presses or shorting a pin on the USB connector)? I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port.
Any thoughts would be greatly appreciated.
Resolution: In a post I saw dated May of 2012, the user indicated HP was still honoring their warranty. I contacted HP via their Chat service, after giving them my model and serial number, I was told I had three weeks remaining on my warranty. HP sent me the return box with authorization and in a week I received (what seems to be) my exact Touchpad... only now it booted just fine. I have since reinstalled ICS and am running fine. Thanks to all who responded. I wanted to share this as I am extremely impressed with HP's warranty service (no questions were asked if I had rooted the device, where I bought the device, etc).
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
chozyn said:
I remember this happened on my brothers and what it was is that the battery was completely dead. I believe it has a backup that needs to charge before the main one. That's the only time I have personally seen this happen. Perhaps if you leave it on the charger for a while it will boot and u can use web os doctor to get it to stock.
Live and Die on this day....
Click to expand...
Click to collapse
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
It's a good idea to use only stock cable and charger.
Sent from my ClassicJewel
enmriley said:
Thanks, I let it charge all night then tried it this morning (as described not just powering it on). Of course, with only a black screen I can't tell what the charge is. I have checked the cable and am now using a different power supply in case that had failed. I think because this happened during the removal/install process I scrogged something in the bootloader?
Click to expand...
Click to collapse
Are you able to get into download mode at all?
A$$h4t said:
Are you able to get into download mode at all?
Click to expand...
Click to collapse
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
enmriley said:
No, totally black device. I was hoping at least I'd get the USB connection on my PC, but not even that.
Click to expand...
Click to collapse
This happened once to my TP when I first put CM7 on the device a while back. I woke up one morning, forgot to plug it in overnight and it had died. No response to any charger, I was getting worried but then I found a solution. With it plugged in, hold the power button and home button down together for 15 to 30 seconds. It was that or hold the power button down and keep pressing the home key over and over. Not 100% sure, but it came back to life and I remember it took me a couple tries. Try holding both down simultaneously for 30 seconds or a minute, if that doesn't work, push and hold power first then home right after and hold both for 30 seconds.
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
-SGA- said:
Okay.... hard reset has been a life saver for me. Hold the home button down, then press and hold the power button, so you will be pressing them at the same time. Keep holding them till you see the HP splash screen, it may take a few min and seem like nothing is happening. I thought I fried mine the first day I got it, but this worked for me!
Good luck!
And, if you decide that does not work for you there is such a thing as the WebOS doctor which will get you back to stock. Link here: http://en.m.webos-internals.org/wiki/How_To_Recover?wasRedirected=true
Click to expand...
Click to collapse
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
rhidalgo1973 said:
This post should do the trick for you....just press the power and home buttons at the same time, hold them down for about 30 seconds until you see the HP logo on the screen then release them...good luck!!!:good:
Click to expand...
Click to collapse
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
enmriley said:
Nope... As stated in the OP, "I have tried home+vol up+power, home+vol down + power, home + power, and of course power only and home only. Each combination was held for 30 seconds and then again for a minute and with power connected, PC connected, and nothing connected to the USB port."
I need to know if ACME Installer is doing anything in the Bootloader. I have flashed and reflashed CM7, CM9, and multiple ROMs. Even uninstalled CM all together when I went from CM7 to CM9. I am familiar with getting into Download Mode and the hard reset (which apparently isn't solving this issue).
I appreciate the feedback, just hoping someone familiar with the Bootloader and Touchpad partitions can help out.
Click to expand...
Click to collapse
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
sstar said:
Bobtidey
To prevent myself or more importantly my daughters tablet ever having this problem I have now purchased Tasker as recommend by yourself and others. But cannot yet figure out how to setup an automatic shutdown, if you have the time could you possibly advise how to do it . I have read the guide but am struggling any help would be appreciated.
Thanks
Click to expand...
Click to collapse
In Tasker add a New profile and give it a name like Battery_Low
Choose State and then Power for the profile.
In Power choose Battery level and set From to 0 and To to say 8%
Set New Task and do Add give it a name like Shutdown and then pick the Misc category
Choose Reboot and set Reboot type to Shutdown
All done. When battery level drops to 8% or below then Tasker will shut the tablet down. Note it will do this without warning. I think one could probably arrange a pop up warning first but I preferred to keep it simple.
bobtidey said:
If the battery was low when you got into this state then it could be that there is not enough power to even let the charging circuits work properly. WebOS has better protection against getting into this fix.
I experienced this once and the trick that fixed it for me was to connect the standard micro USB to the Touchpad and use the standard HP charger unit. Then repeatedly remove the big USB from the charger, wait about 5 seconds then plug it in, wait about 10 seconds and repeat the cycle. After about twenty goes I was rewarded with the battery low icon and it started charging again. I think the theory behind this trick is that when you first plug the power in the battery gets a bit of charge before the circuits kick in, detect very low battery and stop the charging cycle. Doing it enough times gets enough charge into the battery to kick start proper charging.
Now I am not saying this will fix your problem but it might be worth giving it a go.
To prevent myself ever getting into this state again indavertently I now have Tasker set up to shutdown the whole device if the battery level drops below 8%.
Click to expand...
Click to collapse
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
enmriley said:
I have tried this since your post - thanks. No luck, but will continue to try. I found a post online with disassembly instructions. I think I may try pulling the battery. Looks rather easy... with the right tools.
Click to expand...
Click to collapse
The only way I know is to put it on a Touchstone and after an hour or so it Will come back to life. All thanks to Reverand KYLE. His site is well worth checking out.

[Q] 4.3 Low Battery Reboot Cycle

Hey guys, I've got a bit of a problem after the latest 4.3 update. My phone battery went to 7% and then suddenly to 0%, upon which it turned off. Now whenever I try to turn it on the red light flashes and whenever I try to turn it on whilst charging (because I don't think it charges if I just leave it plugged in), it just enters a reboot cycle, whereby it goes to the lock screen, shows the "Shutting Down" window and reboots. I have no clue how to fix this.
I don't really care about the phone at this point, but I do have some photos I want to keep from there...
Any ideas? The software hasn't been pampered with.
same here
hey, feeling with you.
I recently updated my Xperia T to 4.3.
While in 4.1.2 the "low battery" behavior was quite weird, as my T did not charge (no red LED), I was able to get it back to life by pressing and holding the power button for quite some time, lets say 5 min. or so, as it was loading then. This was independent from whether it was exhausted (blinking red LED) or "simply of"(not blinking but not charging anyways).
Through this whole power pressing procedure (I just wrapped the cord around the phone several times) the LED was red and the phone was charging, but it did not turn on. After the 5 min. I freed the T an hit the power button again. Now it was booting as expected and did not immediately go off again.
On 4.3 unfortunately this does not work anymore . The phone just tries to boot and enters the reboot cycle as you described (with the difference that it does shut down instead of reboot).
Now first I would like to know, if your T behaved like mine under 4.1.2 (guessing that was your last Version too). From what I've read I assume that wasn't really normal behavior. I think there must be something wrong with the hw, as my 4.1.2 was neither unlocked nor modified in any other way.
Second I would advise you boot into recovery and select boot into bootloader* (if you have installed one) or connect your T to your PC and boot into flashmode (power+vol.down I guess) as it might charges in there. The recovery worked for me, flashmode should work, but I never tried.
Finally I guess chances are good, that your device works totally normal if it gets charged again (just don't let it run out of energy again )
btw. does the Xperia T normally charge while it's powered off? Anyone has send his phone back on warranty because of charging problems?
good luck to you,
wk
*I am using this 4.3 rom (http://forum.xda-developers.com/showthread.php?t=2647459) atm, as I have root there. But the recovery is really buggy right now so it just restarts all the time. I'm not quite sure where the "boot into bootloader" option gets you ( never heard, that you could boot into bootloader on an xperia device) but the LED shines blue and the T charges and that's important right?
Yeah, my T would sometimes do that when the battery completely drained. I'd have to hold the button for a few minutes while the red light was on until it booted and started charging autonomously.
Now that doesn't work. It doesn't charge when it's off and when I connect it to the charger and turn it on, it restarts. Eventually though the battery drains completely and the old trick works again, but even when it manages to boot to the lock screen, it shows 0% battery again and restarts.
I've tried turning it on while holding the power+down button and charging. The green light came on and disappeared but it started rebooting again. Same with connecting it to my PC.
Can you remove the battery?
Same thing happens to mine,and i just remove battery,plug it without battery,it starts,then put the battery back on.
And it charges fine.
Sent from my Arc S using Tapatalk 2
herokickxx said:
Can you remove the battery?
Same thing happens to mine,and i just remove battery,plug it without battery,it starts,then put the battery back on.
And it charges fine.
Sent from my Arc S using Tapatalk 2
Click to expand...
Click to collapse
But the battery is inbuilt, no? Would I have to disassemble it?
KalST said:
But the battery is inbuilt, no? Would I have to disassemble it?
Click to expand...
Click to collapse
So I think you are facing the same issue as mine... the phone has no time to charge. So what I did was flash an OmniRom with only the SystemUI apk and launcher apk. The intention was to make the boot time shorter so that the battery will not go down by the time it boots. But it ended up causing a bootloop: it was constantly stuck in the bootanimation. And it does charge during the bootanimation. So I let it be like that for about 30 minutes, rebooted to recovery and flashed the stock rom. And all my data was safe. This is more like a fluke so try it and maybe it would work.
If you can disassemble it, then yes, you can do the battery thing. There is just one screw under the SIM flap. I didn't do it because my screw driver kit was borrowed.
The battery trick worked! Now it discharges really fast though.
5% in less than 5 minutes...
KalST said:
The battery trick worked! Now it discharges really fast though.
5% in less than 5 minutes...
Click to expand...
Click to collapse
Try recalibrating
Sent from my Arc S using Tapatalk 2
herokickxx said:
Try recalibrating
Sent from my Arc S using Tapatalk 2
Click to expand...
Click to collapse
How do u recalibrate the battery?

[Q] [Help Thread] Nook HD not booting at all

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.

Categories

Resources