Related
So I rooted my EVO 3D using the HTC method. Then I installed CWR and SU. Installed Titanium backup and took a couple of backups. Everything was fine. Then I had this bright idea of installing ROM Manager. I run ROM Manager and I see this option for backing up existing ROM. I click on it and it asks me to install a boot loader or something. I install it. Then click backup again. BAM ! Phone reboots and goes blank. Now the red LED is consistently blinking every short while and the phone wont start.
Tried removing the battery and holding power to drain the cap. Then tried holding power. No dice. Tried holding power + Volume - no dice. The phone simply wont boot.
How do I fix it ? Is it bricked for good ? Anyone else have this problem ?
Try unplugging and then turning it on. Shouldn't be bricked either way. Hope this helps.
Try running the HTC method again
Sent from my PG86100 using xda premium
If the suggestions already given do not work try hooking it up to your
PC and seeing if adb works? Them try to boot into fastboot, then fastboot recovery.
If not, try hooking into sync and seeing if you can initiate an Ruu. The Ruu will more than likely not be successful because you are unlocked and would need to lock first, but some communication between your phone and pc is a great sign.
also there is a thread here (I think sticky) that says "think you broke your phone, look here". Check that thread out to see if any suggestions.
Edit: added link
http://forum.xda-developers.com/showthread.php?t=1281729
Sent from my PG86100 using XDA App
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
nimkar said:
To try all of that it needs to power on and the screen needs to show something. It simplywont power on. Red led keeps blinking. Tried charging it, connecting it to my Mac. A DB reboot. A DB reboot recovery. Says device not cnected.
Click to expand...
Click to collapse
Well if the red light is blinking I highly doubt it is bricked.
If Adb doesn't work, try running an Ruu through sync. Even if it says there is no device connected to sync, run the Ruu anyhow. I can tell you that I had an issue Once where I hooked it up to sync and it said there was no device connected. I tried to run Ruu anyhow and it initiated. It didn't complete because I was still locked, but at least it was a sign of life. And after it did it's partial run, I was able to but back into hboot.
Try it. You've got nothing to lose. Me though....I'm losing sleep and have to get up early tomorrow so I'm going to bed. I'll subscribe to this thread to try to keep up with it in the morning to see where you are at. Good luck.
oh. And sleep on it too if you find yourself getting frustrated. Sometimes I find that a night to sleep on it really clears my head to and let's me look at it with a fresh perspective the next morning.
Sent from my PG86100 using XDA App
All suggested up is what I'd recommend. I wish you best of luck.
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Try typing fastboot oem boot in terminal with your phone connected obvs
Sounds like a dead battery. Try leaving it plugged in overnight or switch out the battery with a good one.
wrong section btw
Sent from my Touchpad using xda premium
thanx all for your responses. I appreciate them all. The only thing I haven't tried from suggestions above is keeping the battery out for extended period of time. Trying that now. Also since I am a complete noob what is ruu and is I avaliabe or Mac.
I had this issue with the 1.0.x versions on twrp
charge the battery externally if you can. then put it back in and try to turn it back on
do you have insurance? if nothing works take it to sprint service and act all dumb
mildlydisturbed said:
remove power from the thing for 10 minutes - this means take the battery out, do not have it plugged in... then try again... sometimes they freak the f out over nothing...
Wife's stock EVO has done that when an app tried to reboot the thing.
Click to expand...
Click to collapse
This was the fix that worked. Removed the battery for 2 hrs. Phone was fine after that. Posting from phone !
I had a the exact same thing happend to mine.
Repeated battery pulls did not help and it would just blink.
Took it to a sprint keosk at a mall and they just pulled the batter and replaced it with another battery and it booted fine, and then they put my battery back in and it was fine after that, although the battery needed to be charged.
Yeah that happened to my og evo I was all flippin out over a dead battery hahaha
Yep, dead battery. Freaked me out the first time this happened also.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
nimkar said:
This is not a dead battery issue but more accurately a "You phone thinks the battery is dead when its actually not" issue. I charged the battery for a long time using usb cable and my Mac and then using the stock charger and even that did not help. Repeated battery pulls also did not help. Only when the battery was taken out and left for a extended period was it fixed.
Here is my theory. All EVOs have a powerful capacitor inside them somewhere where they store the "Battery is almost dead" info and this capacitor takes some time to discharge. Every time you pull the battery and put it back in again the capacitor is not fully discharged and retains the "battery is almost dead" flag and never updates it even after repeated charging. The only solution is to pull the battery and leave it out for some time ( I left it out for 2 hours, someone here suggested 15+ minutes is good enough) and let the capacitor fully discharge at which point it will loose its "Battery is almost dead" flag. Then plug in the battery and everything is fine.
This explanation is a complete assumption but it is based on my observations and expriments. I have seen a lot of people post the same problem however no clear solution and tried solution as the one above so I hope this post helps others like me.
Click to expand...
Click to collapse
Glad you got it working.
Sent from my PG86100 using XDA App
Just installed CM9 A0.6. All looks nice except it will not charge. It quickly ran out of battery even with charger connected.
Any suggestions?
Check your charging wall wart - make sure it didn't spin loose. If that's good did you try a reinstall? clear cache and your user settings flash again?
Yeah, I noticed that also. It does charge on WebOS though. So I just switch over to that when I need to charge the device.
rgwebster said:
Just installed CM9 A0.6. All looks nice except it will not charge. It quickly ran out of battery even with charger connected.
Any suggestions?
Click to expand...
Click to collapse
Boot back to webos if u can. or u could have real trouble according to other threads about tp not charging.Then try a different rom and see or even flash cm9 again.
It charges fine when I boot into webOS, so the connections are fine. i have tried to re-flash the rom, but it still does not charge.
Still experimenting...but it may be due to flashing the rom with the charging cable attached. I re-flashed after removing the cable, and it looks to be charging now. Fingers crossed
One of the bugs in CM9 Alpha 0 is that the tablet charges very slowly. But there’s already a fix for that. You can download the update-chargerFix-alpha0.zip file from goo-inside.me(Sorry wont let me put url since I am a "Noob")
"goo-inside.me/roms/teamdouche/tenderloin/alpha"-url
1.Place the zip file in the root directory of your TouchPad’s storage (or in a folder that you can remember).
2.Press-and-hold the power button to reboot the touchPad.
3.From the Moboot menu, choose ClockworkMod.
4.Use the volume keys to scroll down to the entry that says “install a zip from SDcard” and tap the home button to select.
5.Using the volume and home keys, highlight the update-chargerFix file and select it.
6.Scroll down to select yes.
7.When it’s done installing reboot into CyanogenMod.
My wife's TP is doing the same thing. Mine isn't. What I did to help her was to install Cyboot from webOS nation through preware.
With Cyboot you can set it to boot into webOS rather than cm9. Also, the time can be set up to 9 seconds.
When she plugged the charger in and then left it, it would turn on and boot into cm9. For some reason the TP in cm9 drains the battery faster than it charges. Now it boots into webOS and charges.
Sent from my DROIDX using XDA App
I have the same issue with mine in CM9.0a6. After running it down the first time, I had to boot to WebOS to recharge to 100%.
I rarely unplug it (using it as a wall-mounted slate more than anything), and CM has no troubles keeping it at 100% or charging it to 100% from being off the charger for a few minutes. I'd imagine there is a point of no return, though, that once you hit won't permit a full recharge in CM.
Same issue here; installing the charge fix caused some error n couldnt boot try using ice buttah n same issue...
Still having an issue with this.
I believe it has something to do with booting up with the charger plugged in.
If I boot-up when it is not plugged-in I can subsequently attach the charger and it will charge.
However if the charger is plugged-in during the boot-up it will not charge and will eventually completely discharge.
It then becomes impossible to re-start cos you are forced to re-boot whilst charging....with the consequent inability to charge.
Catch 22
Hello, I've been using my old x2 as my PDA/MP3 player. I also have put custom ROM on it because... It's fun!!
What's not fun is my locked up phone, here's what occurred... I tried to sbf my phone and received an error flashing (had all correct Motorola drivers/rsd lite. So as it failed and never even cleared out my phone I decided to use my iso boot disk instead. The disk came up, ran normal, said flashing was complete..... nightmare began....
Now I cannot boot into recovery New/old. I can't boot the phone. I can't do anything. The phone starts, I get the Motorola dual core screen (can't hold volume keys to get to rsd/fastboot/etc. The phone will get to the point of booting but will come up with screen which says...
"Failed to boot number 4"
"Starting rsd....."
Then when I go into try anything rsd (iso disk or rsd lite) the phone will either shut off right away and loop sometimes to same screen. Or it will come back when plugged into pc saying battery (which is fully charged) is to low to flash....
I'm going crazy...
Are there any other restore tactics?
I can't erase battery stats because I have no recovery... I've always followed instructions and flash roms for nearly every manufacturer of phones over the years. I am stumped....
Sent from my Galaxy Nexus using xda premium
Disention said:
Hello, I've been using my old x2 as my PDA/MP3 player. I also have put custom ROM on it because... It's fun!!
What's not fun is my locked up phone, here's what occurred... I tried to sbf my phone and received an error flashing (had all correct Motorola drivers/rsd lite. So as it failed and never even cleared out my phone I decided to use my iso boot disk instead. The disk came up, ran normal, said flashing was complete..... nightmare began....
Now I cannot boot into recovery New/old. I can't boot the phone. I can't do anything. The phone starts, I get the Motorola dual core screen (can't hold volume keys to get to rsd/fastboot/etc. The phone will get to the point of booting but will come up with screen which says...
"Failed to boot number 4"
"Starting rsd....."
Then when I go into try anything rsd (iso disk or rsd lite) the phone will either shut off right away and loop sometimes to same screen. Or it will come back when plugged into pc saying battery (which is fully charged) is to low to flash....
I'm going crazy...
Are there any other restore tactics?
I can't erase battery stats because I have no recovery... I've always followed instructions and flash roms for nearly every manufacturer of phones over the years. I am stumped....
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
First, make sure the battery is charged up. You can't RSD without at least 20% battery. Simply plug it in and let it charge, then try again after about an hour.
Also, make sure you are using the correct SBF file. It could've been a bad download, or worse you flashed one for another phone.
I've had nothing but trouble RSDLite and personally only use sbf_flash. So using the iso boot disk is recommended by me.
Yes, I agree that rsd lite will never again be the way I go. The disk had been much handier. Only problem is that I was out of disks, I was also without my CD in the office. I have done plenty of rsd reboot/reflash. Didn't expect this which is why I then went, got my CD, tried again.
Strange thing is the disk is what brought the issue I have at hand to light. So...
I really appreciate the insight for future occurrence avoidance.
How would you suggest fixing problem at hand?
The battery is full charge... It's that 2.3.5 battery glitch still coming back to light. The battery should be full. Now I end up in that strange loop, I don't even know if my battery is now charging or not...
Ugh... I really wish I could figure out exactly where I went wrong as well.
Thanks again for the response!
Sent from my Galaxy Nexus using xda premium
Disention said:
Yes, I agree that rsd lite will never again be the way I go. The disk had been much handier. Only problem is that I was out of disks, I was also without my CD in the office. I have done plenty of rsd reboot/reflash. Didn't expect this which is why I then went, got my CD, tried again.
Strange thing is the disk is what brought the issue I have at hand to light. So...
I really appreciate the insight for future occurrence avoidance.
How would you suggest fixing problem at hand?
The battery is full charge... It's that 2.3.5 battery glitch still coming back to light. The battery should be full. Now I end up in that strange loop, I don't even know if my battery is now charging or not...
Ugh... I really wish I could figure out exactly where I went wrong as well.
Thanks again for the response!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So you still only have access to RSD on the phone? Or did it accept the SBF? I'm thinking that you flashed another phone's sbf file.
Sent from my Nexus 7 using xda app-developers app
Yes, if you could re-read my first post for sake of my key stroke would be great. The phone does not boot I'll try and snap a quick pic with other phone and show what happens. This is only thing which happens in a complete loop... can't get into new or old restore/bootstrap. Can't get it to load any of the basic rsd menu options. If I plug into pc it tells me battery is not charged enough. Or just shuts down with disk or boot CD. It's insane!
It's most definitely the RIGHT folder. All of my phone have their own nearly organized files. None of them flash the same way. Droid X2, HTC EVO 4G, Galaxy Nexus..... Yeah, I know the files ok but good thought!
Sent from my Galaxy Nexus using xda premium
Sent from my Galaxy Nexus using xda premium
Have you tried to turn the phone off, put it directly into RSD mode then run RSD program with the correct SBF file?
That's the problem, I never can "put" it in to rsd mode. I start the phone simply by plugging it in it automatically boot into that loop. Nothing I've found will load such as restore, boot loader, etc.
When it says it's going into rsd, it either turns itself off when in that phase and I start rsd. Or it will give me an error stating battery is not charged enough (it's got a full charge, already tested with multimeter)
Sent from my Galaxy Nexus using xda premium
If you got a spare charger around can jerry rig it. If you know what im talking about. If that don't work with the battery issue then if your under contract I'd go get a replacement. Do it by phone as they will not check your device once you send it back.
I've got plenty of spare charger...
What do you mean "Jerry rig" though?
Sent from my Galaxy Nexus using xda premium
Cut the end off that plugs into your phone, then use the ground and hot wire inside the power cord. Put them on the correct ends of the battery without touching the others, can tape them to it then put the battery back in the phone making sure the wires don't move or touch anything else. Then have the one with wires on your battery plugged into the wall, the usb from your phone to your computer then turn RSD on your phone, then try to SBF it. If you still get that arrow do the other option and call and get a replacement. Ive saved a many of phones doing the jerry rigging of the charge. But if it works and you can SBF then when the steps are complete undo the wires and walla.
I like it!
Let me get some stuff together and put this to the test!
I'll post my results!
Thanks!
Sent from my Galaxy Nexus using xda premium
This is the EXACT thing that happened to me about to weeks ago when trying to SBF back to 2.3.4, a task that I've done many times.
I got the "failed to boot" etc screen that you have. Basically I kept trying to SBF (it still wasn't working) and eventually I got the "battery too low to flash" screen.
Since the battery wasn't actually charging at all because of this weird boot screen, I had to drive down to my local RadioShack where they had some device that would charge ANY battery. It was sweet, AND they let me use it for free at their store. So they popped my X2 battery in and I went to the nearest bookstore to get some work done. Came back two hours later and my battery was charged.
But that's all besides the point. Basically what I did to fix it was I kept trying to SBF and eventually it worked. I downloaded another 2.3.4 sbf file to make sure (even though I've used the same file many times) and I even downloaded a 2.3.5 sbf file and began "alternating" between the three in rsd lite, hoping that one of them would "catch". Eventually I believe my original 2.3.4 file caught and my droid was back to normal.
Sorry for your troubles! This problem sucked and it freaked me out a lot when it happened. But I think you'll be fine. Don't worry too much about it like I did!
Disention said:
Then when I go into try anything rsd (iso disk or rsd lite) the phone will either shut off right away and loop sometimes to same screen. Or it will come back when plugged into pc saying battery (which is fully charged) is to low to flash.
Click to expand...
Click to collapse
I have had problems with my DroidX2 not staying charged while being plugged-in to the a usb port on the computer ... I had to use a usb wall-wart for consistent chargeing.
So, if your battery is haveing trouble staying charged (or not) try connecting it to a usb wall-wart and let it charge for at least a couple (~2) hours.
Also, how old is the battery? (I'm pretty sure this has nothing to do with you issue, but it could affect chargeing and battery-life)
Disention said:
That's the problem, I never can "put" it in to rsd mode. I start the phone simply by plugging it in it automatically boot into that loop. Nothing I've found will load such as restore, boot loader, etc.
When it says it's going into rsd, it either turns itself off when in that phase and I start rsd. Or it will give me an error stating battery is not charged enough (it's got a full charge, already tested with multimeter)
Click to expand...
Click to collapse
The following steps can also be seen here -or- see the original sbf/rsd instructions (note: the sbf files are not available at this time)
key instructions at step #10:
With the X2 in a completely POWERED DOWN state, press and hold the volume up button on the top right hand side of the phone. While still holding the volume up press and hold the power button until the screen turns on. At the top of the screen you should see "Starting RSD protocol support" once this text appears you may release the volume up button.
Click to expand...
Click to collapse
i had flashed CM10 by dragonkiller and all was working fine. i was getting annoyed by minor bugs, so i decided to go to ecplise 2.3 (which was an upgrade from my last rom, eclipse 2.1). ive had it on the phone before and know what im doing.. started by SBFing to 2.3.4, but there was a problem right away. after RSD rebooted my phone i got stuck on the M screen with an error saying "modem failed to power up". since then i have not found a solution and nothing i have tried on my own has fixed the problem. trying to get the stock system recovery to run will display the error "battery is too low to flash" no matter how long i leave the phone charging.. please help! 2 days with no phone already, i cant afford a new one and i rely on this for work!
I've gotten that error message before and gotten out of it fine. First thing you will need to do is charge your battery. Find another Droid X2 or X user and swap batteries, buy an external charger, or take it to the store and *see* if they will charge it for you. After that replace the battery in the phone. With it off, hold volume up and power. When the screen turns on release power and continue holding volume up untill "starting RSD Protocol" appears... plug in and SBF as normal. You could also try the EzSBF but that did not work for me when i got the modem error. RSD should work assuming you have the proper drivers installed.
Likely what happened is your battery died mid flash or you had a bad SBF file and it failed the flash causing the phone to not be able to boot.
Happened to me before. As the software that charges your phone no longer exists, you can't charge the phone to SBF properly. I wound up stripping an old USB cable I had and made a "suicide cord" that I electrical taped to the battery for a few hours. (Red, +; black, -) Worked fine afterwards.
Sent from my MB870 using xda app-developers app
Moral of the story...charge your phone before you SBF.
And post questions in the Q&A thread.
Thread moved to proper section.
jsgraphicart said:
Moral of the story...charge your phone before you SBF.
Click to expand...
Click to collapse
buy a Team BlackHat cable
or
Spare Battery Charger for Motorola Droid X/X2
Yup charge your battery this happened to me as well,even though it was at 50 percent when I tried still wasn't enough to finish.
Sent from my MB870 using xda premium
Hey I seem to be having some trouble with my Nook Tablet. I've got the 16gb version, bought it within the first month or so of the tablets getting released. It's been running fine, i have it rooted, ran cm7 for the longest time on it, switched to cm10.1 more than a few months ago and everything was pretty great, then crap started going downhill.
I noticed that when my battery would get down between 20-30% it would just shut down. The low battery screen would come on for a split second before the "tablet is shutting down" screen would pop up in front of that and it would shut down.
Now, since then it's been happening more and more. When it's at anything lower than 96ish% it'll happen. But it's got some weird symptoms.
- The screen freaks out. Like there's 100 fingers on it pushing a ton of crap at once, when I'm not touching it at all. it's sensing a bunch of false touches that usually ends on the Google Now screen before getting the same old low battery, then tablet shutting down notifications.
- It only happens when it's running on the battery. It's never ever happened while it's plugged in.
- It only seems to happen when the wifi is on. If the wifi is off and i'm at home just reading a book or something, it'll drain all the way down to 15 or whatever before telling me the battery is low, I plug it in, all is fine. If the wifi is turned on the freak out happens.
- If it starts freaking out and I plug it in while it's happening, 1 of 2 things, It either completely stops and everything works fine, or it just turns off dead right there, not shutting down, just turning off.
- I HAVE had it drain pretty low (around 23ish) with the wifi on, but it did do the same freak out thing once it got there. It just seems to be so random when it happens, any time the battery is between 15 and 96%.
- If I turn it back on after a freak out without plugging it in first, it will restart fine, then last about a minute or 2, freak out again and shut off. If I turn it on again after that it'll do the exact same thing. And if i turn it on again after that it'll get to the CM10 boot screen, just about to where it's going to go to the lock screen, then boom, makes the beedoop battery sound and shuts off without ever actually showing the lock screen. THAT happens everytime just like that. If I plug it in first and then turn it on, it runs fine.
I've tried factory reset and reinstalling and all that stuff, nothing seems to be working. I even started from scratch not letting google or titanium backup restore my apps, completely formatted and wiped the sd card when reinstalling, nothing seems to be fixing it.
Basically this thing is useless without being plugged in. Ive even lost a 32gb sd card because of it's constant just turning off screwing it up (i'm guessing) since it's not being properly dismounted or whatever before being shut off. That card cant seem to read/write anymore. I now have a 16gb in there I'm hoping wont get screwed up because of the same thing (although I'm sure it will eventually if this isnt fixed)
Is this a battery issue? A hardware issue? User Issue? Can anyone help? I can provide any information you might need.
I've been searching for months trying to find an answer, but the symptoms are so weird I cant find anyone having the same problem as me..
Also, my fiancee also has the same Nook tablet, bought them the same day, rooted and hacked them the same way that day, and put CM10.1 on both of ours the same way the same day, hers is fine, mine is acting a fool. (I also use mine about 1000x more than her though, I use mine for EVERYTHING, EVERYDAY, she reads Sandra Brown books and watches YouTube movies once every month and a half)
Help? =[
the finger touch thing at random on your screen without touching it is your charger cable , its a crap cable , i had this happen to me too , B&N will swap the cable and charger for free, i highly suggest you do that and get a new one swapped , mine still has issues , when its plugged in and charging , i sometimes cant use the touch screen , its the charger , they are like 1 in 3 garbage and cheaply made ,
take it to the store they will swap the charger for free, if they hassle you ***** up a storm , they are supposed to just swap them , its well known fact the cables are cheap garbage and not easy to get new ones that are not garbage, i use micro usb's it takes longer to charge but i get quality cables from amazon cheap as piss 2.49$ if you want the link ill find it , again takes longer to charge , but i no longer have touch screen issues and can use tablet while its charging ill re read the rest of your post and make an edit if i can help on anything else
spyder
how long are you charging it for at any one time ? i do believe if my memory serves me right , theres a problem with the battery level on both cm 10 and 7 , seven is way worse, the battery level is not reported correctly , its being worked on by better minds than ours , im sure one of em will chip in here shortly ,
if i were you you have cynoboot installed to emmc ? i would turn the thing off completly , and charge the **** out of it , with a good cable , id use your girls cable it sounds like she got a good cable. like leave it over night charging on hers while you sleep , then in the morning boot it check the batt level in cynoboot and then in cm10.1 , im keeping mine juiced up , last time it died it ended in a boot loop that i had to unplug the battery to fix , most people dont want to crack a case even though its easy peasy ,
again , try her charger , if your powered up check how long it takes to charge fully it should be 6-8 hours on the nook 2.1 amp factory charger , i think you need a new charger though , i would try to swap cables until i found a good one , then look at ipad travel charger they are 30$ , but they output 2.1 amp and apple crap is quality which is why its 30$ , or look for a samsung galaxy tab charger USB output 2.1 amp ,
Ahhhh.. see. The battery level being reported wrong makes sense for why it happens so randomly. Another interesting thing you said was it should take 6-8 hours to charge with the stock charger, mine was reporting 100% battery after 2.5 - 3 hours charge time. This could be the problem.
I did what you said, let it charge overnight, and it did the same thing, but, not until it got down to 32%. Which is better than 82% shutdown.
When I get home tonight ill plug it in immediately and not touch it until tomorrow morning, well see what happens. Thanks for the response.
Sent from my Barnes & Noble Nook Tablet using xda app-developers app
I may have figured this out. I switched my rom to aokp 4.2.2 and then flashed the showtime kernel, set cpu tuner to no more than 999mhz and all seems to be running fine. Bbs says 14hrs on battery, deep sleep for 9 of them, and I'm at 69% battery now. (Bbs started collecting at 91% for some reason instead of 100%)
I flashed the rom yesterday around 6pm, let the battery go all the way down to the first time it randomly died, then just charged it back to 100% and I've had it off the charger since then, 14 hours now according to bbs. Ill report back if it freaks out or something later.
Edit: turns out this didn't work.
Sent from my Acclaim using xda app - xdevelopers app
Just did it =[ freakedout and shutdown at 77% battery, then got stuck in a bootloop.
It ran fine yesterday, I was watching podcasts on it no problem. Charged it last night and now today it seems unusable without being plugged in.
Does anyone have any other help they can offer?
Sent from my Acclaim using xda app-developers app
thelivingdead188 said:
Just did it =[ freakedout and shutdown at 77% battery, then got stuck in a bootloop.
It ran fine yesterday, I was watching podcasts on it no problem. Charged it last night and now today it seems unusable without being plugged in.
Does anyone have any other help they can offer?
Sent from my Acclaim using xda app-developers app
Click to expand...
Click to collapse
I might have a solution for the battery problem. Do you have any microUSB chargers lying around? maybe for an old cellphone? If you do, use that to charge your Nook Tablet. It works, but it's slow, takes 8-9 hours for a full charge (5% to 100%) @ 500mA current. My old Motorola flip phone's charger supplies 5V @ 550mA. I'm pretty sure you have one of those lying around in the attic or garage. Anyways, let the NT charge to 100% using a microUSB charger (not the Nook Tablet's stock one, the cable is faulty and I am sure of it).
Once it's charged to 100%, go on YouTube and watch a few videos. If the battery goes down steadily, that's good. If it goes from 100% to 80% or less suddenly, there might be a problem with the battery calibration or the battery's going dead.
I bought a Nook Color off eBay that the seller listed as broken, except it wasn't. The battery was simply dead beyond the capability of the Nook's stock charger to revive it. I used the old Motorola charger. It took 10+ hours, but finally my Nook Color booted up, although with 18% battery life only. No matter what, it would stay at 18% until it shutdown without a warning. The solution to this was to delete a file called max####.bin in the /rom partition, then reboot.
Steps to recalibrate the battery (ONLY try this method if you're sure the battery needs to be calibrated):
Open the terminal (once you are 100% charged. You'll know this if the power adapter isn't warm anymore)
Type in "su", allow root access for once
Type in "cd /rom"
Type in "ls" (that's a lowercase L and S)
Type in "rm max#####.bin" (where ### are the numbers there)
Type in "exit"
Type in "exit" again
Hold down the power button and reboot. Once it reboots, it might show question marks on the battery meter before going away shortly. Hopefully, your battery will be successfully recalibrated.
Hope that helps.
Thanks a lot for the reply. I definitely have a charger lying around so ill try this tonight when I get home.
Sent from my Acclaim using xda app-developers app
thelivingdead188 said:
Thanks a lot for the reply. I definitely have a charger lying around so ill try this tonight when I get home.
Sent from my Acclaim using xda app-developers app
Click to expand...
Click to collapse
Any good news? Did you charge it up?
sagirfahmid3 said:
Any good news? Did you charge it up?
Click to expand...
Click to collapse
Just got done testing it out. I charged it for about 16 hours, pulled it off and powered it up, my battery status said charged, then 100, 99 etc. Once it got down to 87 it freaked and died.
The battery did drop way fast though. Like 100 to 87 in under 15 mins. Not instantly though.
If you search "nexus 7 phantom touch" on youtube, you'll see exactly what my nook is doing, only difference being the nook dies after about 10-15 seconds of the screen freaking out. And it ONLY happens when not plugged in.
If my battery calibration is off, would that mean maybe it could actually be around 15-20%, even though its reported as 100%, and not letting it charge passed that? Or is my understanding a bit off?
Sent from my Acclaim using xda app-developers app
thelivingdead188 said:
If my battery calibration is off, would that mean maybe it could actually be around 15-20%, even though its reported as 100%, and not letting it charge passed that? Or is my understanding a bit off?
Sent from my Acclaim using xda app-developers app
Click to expand...
Click to collapse
Right. My Nook Color was showing 18% charge no matter how charged or discharged it was (until I deleted the max#####.bin file).
Try what I said, delete the max#####.bin file and reboot. That will recalibrate your battery. If after that it still shows the battery draining way too fast, that means your battery is going dead.
Ok, so I reset the battery stats and now I'm seeing this.. this doesn't seem right at all..
I let it hang out for a while and it did the usual freakout/shutdown when bbs said it was at -22%, android showed 69%.
I think ordering a replacement battery or finally just getting a nexus 7 is the fix at this point?
Sent from my Acclaim using xda app-developers app
thelivingdead188 said:
Ok, so I reset the battery stats and now I'm seeing this.. this doesn't seem right at all..
I let it hang out for a while and it did the usual freakout/shutdown when bbs said it was at -22%, android showed 69%.
I think ordering a replacement battery or finally just getting a nexus 7 is the fix at this point?
Sent from my Acclaim using xda app-developers app
Click to expand...
Click to collapse
Or actually, you might find "for parts" Nook Tablets on eBay for <$30. I would use the battery in there instead of buying a cheap chinese made battery (which are always of garbage quality, not to mention dangerous). You could also use a Nook Color battery in there, but you'll trade off 3 hours of usage time. Nook Color batteries on eBay sell for $7 used, but genuine.
Before you buy anything, try doing a complete wipe and reflash of CM10. Boot to CWM > wipe battery stats, wipe data/factory reset, wipe cache, wipe dalvik cache; advanced > wipe system partition; go back > flash CM10, flash gapps, flash CWM (if not already installed).
sagirfahmid3 said:
Before you buy anything, try doing a complete wipe and reflash of CM10. Boot to CWM > wipe battery stats, wipe data/factory reset, wipe cache, wipe dalvik cache; advanced > wipe system partition; go back > flash CM10, flash gapps, flash CWM (if not already installed).
Click to expand...
Click to collapse
Awesome, thanks for all your help man. One more thing, I'm running CWM recovery v. 6.0.2.7, there's no wipe battery stats option in advance (or anywhere else I can see). Is it hidden somewhere I'm not looking or not in this version? Is there a newer version I can flash I overlooked?
Btw, http://www.newpower99.com/Barnes_No...cement_Kit_p/barnes and noble nook tablet.htm this was the battery I was looking at for $40, but the used nook from ebay seems like a better idea. (Cheaper too, which I like)
Sent from my Acclaim using xda app-developers app
thelivingdead188 said:
Awesome, thanks for all your help man. One more thing, I'm running CWM recovery v. 6.0.2.7, there's no wipe battery stats option in advance (or anywhere else I can see). Is it hidden somewhere I'm not looking or not in this version? Is there a newer version I can flash I overlooked?
Btw, http://www.newpower99.com/Barnes_No...cement_Kit_p/barnes and noble nook tablet.htm this was the battery I was looking at for $40, but the used nook from ebay seems like a better idea. (Cheaper too, which I like)
Sent from my Acclaim using xda app-developers app
Click to expand...
Click to collapse
The CWM I used was a bootable microSD one. It had the option to wipe battery stats. At best, it will recalibrate your battery, nothing else.
I followed Ray Waldo's instructions (he's really good at explaining things in non-technical language). Download link also posted there.
You can use any Linux distro with GParted installed to set the boot flags on the card. (I highly recommend Debian, been using it for 4+ years).
http://raywaldo.com/2012/05/root-nook-tablet-with-cwm-sdcard/
I wouldn't buy that battery off the newpower site. It's a scam. You'll get a really crappy battery (3200mAH, probably chinese made, and unreliable). I would much rather buy a used GENUINE battery for the Nook Color or Tablet than a cheaply manufactured one (selling for an unreasonably high price).
If clearing the battery stats and doing a full wipe and reinstall doesn't help, I would buy a Nook Color battery for $7 off eBay. This is the last one supposedly (doubt it) http://www.ebay.com/itm/Nook-Color-...863?pt=LH_DefaultDomain_0&hash=item27d5fc185f
^^It's genuine, has a 4000mAH capacity, compatible with both the Tablet and Color, and wont explode in your face. (You really don't want to take chances with cheaply made chinese li-ions. Look on YouTube for li-ion fires/bloat (expansion)/explosions, not pretty). Be sure you also have a Torx T5 screwdriver to open up the NT. If you don't, order a set off eBay. (P.S. Don't get the chinese made ones, they're cheap and they don't work. Get a set from Craftsman if you can, those have a lifetime warranty).
Gotcha. Will try everything you mentioned and if no luck ill hit up ebay. Thanks again for all your help (and saving me from a potentially harmful choice of battery)
Sent from my Acclaim using xda app-developers app
thelivingdead188 said:
Gotcha. Will try everything you mentioned and if no luck ill hit up ebay. Thanks again for all your help (and saving me from a potentially harmful choice of battery)
Sent from my Acclaim using xda app-developers app
Click to expand...
Click to collapse
Have you have made progress?
Also, let me know if the battery (if you ordered one) works well. I think my Nook Color's battery is about to kick the bucket. It takes like 15 hours to charge from 15% to 100% (compared to 8-9 hours for my Nook Tablet, using the same specced charger).
My 16gb nook tablet with CM10.1 is doing the exact same thing as yours. Random touches and sudden shutdowns. The OS does not know how charged the battery is. I am eager to hear your results.