Related
So I had my tilt for about a month, was happy flashing away ROMs every few days, when it got stuck constantly rebooting, not even making it to where you could see the RGD version numbers. Sometimes it MIGHT get all the way in, but would only last a minute or two before randomly going back into the boot loop.
Also, the only way to get it to boot at all was to plug it into the AC adapter. If I tried to turn it on w/o it being plugged in, it just sat there, black. Then as soon as you plugged it back in it would automatically go right back into the loop.
I figured I had busted it (because i tried EVERYTHING I could find on the forums), so I got it into bootloader mode (which always DID work fine), went back to stock, and did an RMA.
Got the new phone this morning, moved over the battery, cover, stylus, and booted up just fine...... Then after about 8 minutes, boom, back to the restart loop.
(yes i tried no SD/SIM card, same results).
so after plugging and unplugging the AC adapter about 20 times, i managed to get it to where the little orange light came on and it DIDNT try to enter the boot loop. I let it sit for about 2 hours, then successfully booted up. I clicked the battery icon and saw that it was at 0%. Let it sit for about 30 minuted, checked back, 1%.
So I let it sit for about 5 hours, and the battery read 100%. I unplugged it and headed off to my evening engineering class. (still no sim card tho because i wanted to eliminate that as a cause). And eventually, about 2 hours later, click... it tried to reboot once, then went black.
I called ATT and told them, and they will be sending out a new battery. Is it possible the battery has some mechanism busted where it reports to the phone what % charge it is, and wont boot otherwise?
Any ideas will be great, and I will come back and update this thread after I get the new battery.
Thanks!
no thoughts anyone?
hi
I had exactly the same problem...updated radio to 1.65.30.09 and then endless reboot loop. tried hard reset, downgraded radio version, installed another rom, nothing worked. Finally tried hard spl, and booted fine. im feeling very happy, i allready thought that i had ruined my htc polaris. hope it helps anyone. zorry my bad english, I'm from Estonia
I just wanted to get root access and Auto-Nooter 2.12.25 for v1.0.1 seemed to be the way to go, right? Well, after I purchased the last Nook Color from Best Buy yesterday and brought it home, I charged it to 100%, played with it loaded up and ran Auto-Nooter from a Sandisk mSD card. When I plugged in the cable to boot, it came up with the battery low-wait 15min screen. (Battery was at 100%) Tried again, same thing. Re-wrote Auto-Nooter to mSD card and tried again, black screen. Nothing. Bricked. What I do get is a black screen with a flash of backlight every 40 seconds or so. I re-created the boot SD Auto-Nooter (using Win32DiskImager) and boot, nothing.
Today same story, just wasted 5 hours trying: Auto-Nooter, Clockwork Recovery image (2gb & 1gb versions on different cards) with complete restore-1.0.1 and repartition-boot-with-stock.zip, Nookie-Froyo.......nothing brings up any life in the NC.
I did follow RileyGrant's "Dummies Guide to Fixing 'My Nook Won't Boot'" http://forum.xda-developers.com/showthread.php?t=949699 to no avail. I do not believe it is a partition issue. If it were, the mSD would at least try to boot to some screen and perhaps hang then. But CWR is not providing a spark at all.
I do believe it is in a boot loop of some sort, trying to boot, screen flashes, turns off, repeat continuously if plugged in. (It does stop the cycle after a while when not plugged in.)
Is that enough information? Ideas??
When you insert the Clockworkmod Recovery sdcard and turn the nook on, Does it boot into CWR?
RileyGrant said:
When you insert the Clockworkmod Recovery sdcard and turn the nook on, Does it boot into CWR?
Click to expand...
Click to collapse
No. It boots to nothing. Plug in, wait 10 seconds, a white screen flash (less than a second) then black. Repeats in about 40 seconds. I can tell that the backlight is on for about 30 seconds, back lighting a black screen, then it turns off. A few seconds later the screen flashes white and it is what seems to be a boot loop of not booting.
Create this Sdcard with the files here.
http://forum.xda-developers.com/showthread.php?t=922870
When you are done, connect your Nook with the SD card inside and make sure you press the power button until you hear it disconnect even tho its still plugged in. (This means its turned off) Then power it up. You should be in recovery. Make a full wipe and see if it turns back on. If it doesn't send me message. I'll be glad to help. Your Nook is fine.
Here are better instructions:
http://forum.xda-developers.com/showthread.php?t=949699
Fixter said:
Create this Sdcard with the files here.
http://forum.xda-developers.com/showthread.php?t=922870
When you are done, connect your Nook with the SD card inside and make sure you press the power button until you hear it disconnect even tho its still plugged in. (This means its turned off) Then power it up. You should be in recovery. Make a full wipe and see if it turns back on. If it doesn't send me message. I'll be glad to help. Your Nook is fine.
Here are better instructions:
http://forum.xda-developers.com/showthread.php?t=949699
Click to expand...
Click to collapse
Have done all this. Will not go into recovery. Ideas? (PM sent)
Sounds to me like your battery is dead (it would NOT go from 100% to 15% like you say), or you're not burning the cards right.
khaytsus said:
Sounds to me like your battery is dead (it would NOT go from 100% to 15% like you say), or you're not burning the cards right.
Click to expand...
Click to collapse
I followed the Auto Nooter instructions to the letter. I would agree with both except:
1) After the first time I tried Auto Nooter, and it said 15% battery, I took the card out and it booted normal. I checked the battery and it was at 99%. Repeated the process and the same result. (Batt at 15% when trying to root, 99% when not.) I re-built the card and then nook bricked.
2) I have used 2 different cards on 2 computers with 2 different softwares for burning the image. Perhaps the second burn on the uSD card fried something? Perhaps, but the card still was readable by Windoz 7 on either computer. One bad apple can spoil the bunch.......
Heading back to BestBuy is sounding better all the time even though it is 40 min away. That said, I have still not lost faith in XDA and the great help. Anyone with a new suggestion?
IMO you just have a dead battery, plug into the wall and leave overnight. The Nooks ability to boot into sdcard first is built into the hardware, nothing you did could of messed this ability up. If you truly can't boot into clockwork from sdcard it can only really be a hardware failure.
carmicp said:
I followed the Auto Nooter instructions to the letter. I would agree with both except:
1) After the first time I tried Auto Nooter, and it said 15% battery, I took the card out and it booted normal. I checked the battery and it was at 99%. Repeated the process and the same result. (Batt at 15% when trying to root, 99% when not.) I re-built the card and then nook bricked.
2) I have used 2 different cards on 2 computers with 2 different softwares for burning the image. Perhaps the second burn on the uSD card fried something? Perhaps, but the card still was readable by Windoz 7 on either computer. One bad apple can spoil the bunch.......
Heading back to BestBuy is sounding better all the time even though it is 40 min away. That said, I have still not lost faith in XDA and the great help. Anyone with a new suggestion?
Click to expand...
Click to collapse
make sure as well you are creating the SD correctly. WinImage can be a pain at times at times. If the bootable SD isnt created just right it wont boot. Im putting up a post in a few minutes to an IMG you might like to try to recover your NC.
Try this: http://forum.xda-developers.com/showthread.php?p=11321261#post11321261
Its how I have been rooting my devices, as well, I will be adding the prerooted 1.1 to my IMG soon to simplify things for everyone.
forsakenexile, I appreciate this and am downloading the file now overnight. Perhaps this will solve problems of my NC not booting up ANY rom/recovery solutions from SD, despite all the documented methods known to the community so far.
One thing I noticed under Win7 was to get an image to work properly I had to run winimage as administrator. Not sure if this is just an oddity with my computer or common knowledge I had to discover for myself.
I threw in the rowel
I charged the nook over night with the genuine nook charger and genuine nook cable and no difference this morning. I took it back to BestBuy and waked out with a new one. I charged it, powered up, logged in, powered down, inserted a monster root pack 7 uSD and booted no problem!
Thanks to all for the help in troubleshooting.
Note to self: Nook can be a brick!
Been running cm7 for a few months now with no problems. Battery was full when I left my house, came home and it wasn't turned on. Tried for a while and got no response. Plugged in the charger and it keeps restarting after the cm7 logo screen. The farthest it got was the home screen for about 2 seconds before restarting. I noticed the battery was in the red zone before it restarted even though it was full earlier that day. The battery usually last 3-4 days unplugged......
Have you tried to get it into cwm? If you can, download cm7 rom again on your computer and put on sd card and flash the from again, the rom could have been corrupt due to a bad download
NookColor ICS 9 Nightly "Overclocked"
My guess is it SOD'd, and the battery is dead. I have noticed that my NC will not power up if the battery is very low, even if it is plugged in.
I guess we won't know any more until the OP returns, but often when a charged nook just shows a dead screen, and it is actually on, and you just can't tell. There are multiple workarounds for this, but the easiest to my mind being a sdcard with a burned with a bookable image like CWM or a hard reset. Let us know after you have let the nook charge. If thencord is lot and it still won't turn on, try a bootable card.
Thank you to the members on here, reddit, and other Android sites for the helpful insight. I did tons of research because I could just not stomach losing everything on my phone. I'm actually glad this happened because I will never be this careless again. I've been coming on this site to mod my phones since the PPC-6700 and have never heard of this issue. But SD cards fail and drops happen so that's no excuse.
I was able to get my defective phone to boot by freezing it for about 15 minutes in large freezer, and letting it run inside the freezer. I have heard of people being able to recover data by freezing the batteries and one person suggested to run your phone in the freezer. I tried it and it worked.
Before I tried the freezer method I was only able to get to the Android is Upgrading screen maybe 10 times out of over 100 boot loops. The farthest I ever got on that screen was 8 out of 101 apps. With the freezer method it fully booted on the first try.
First I froze the battery alone for maybe 20 minutes. Then I placed the battery in the phone and tried booting into recovery. It didn't work. So I removed the battery, put it back in and and let both of them sit together for about 15 minutes in the freezer. Then I returned and the phone fully booted on the first try. I tried booting into recovery from Nandroid Manager but that just reset the phone. Since it seemed stable and I wanted to keep the phone as cold as possible I just used My Backup Pro and Titanium Backup to back everything up.
I honestly gave up and I am sending my phone to LG today, so this was literally my last resort. Hope this helps someone.
Confirmed, sort of. After about 15mins my phone booted up, but froze again and restarted. Hoping with a few more minutes of freezing it stays put so i can transfer my TB to my SD card (I though it was already there :\)
Thank for useful information. It's happened to my phone too keep rebooting itself then after 100 reboot I got the home screen and use cable to copy all my stuff in laptop . I'm sending mine to tmo store
Sent from my Nexus 4 using Tapatalk
hollywood084 said:
Confirmed, sort of. After about 15mins my phone booted up, but froze again and restarted. Hoping with a few more minutes of freezing it stays put so i can transfer my TB to my SD card (I though it was already there :\)
Click to expand...
Click to collapse
I tried it again to get a nandroid backup and merely freezing the phone did not work. I had to let it run in the freezer, I got the best performance with the back off and the phone resting on a bag of frozen vegetables. The second time I had two reboots but that may be because I didn't get the phone quite as cold as the first time I did it.
Phone is sent off to tmobile and the replacement is working great.
Thanks for the tip, it helps! Confirmed working, left my phone 20 minutes in the fridge => boot but freeze during LG animation (not cold enough)
left the device in the freezer for a moment => success boot, but freeze minutes later once it gets warmer
So... there is a problem with some hardware pieces..
It still took dozens of tries to get everything working over a couple of days but using this method I was able to backup all my data and even wipe the phone! Just keep trying and keep it cold in the freezer. Also, charge your battery to 100% constantly rebooting drained the battery quickly. The CPU gets hot even when it looks like its running fine, keep it in the freezer while it does its commands.
I got the dreaded bootloop back in Dec. Tried the freezer method a few times to recover data, but I still get the bootloop. I got to the T-Mobile screen once, but every other try I got stuck at the LG logo.
Sent from my LG-E980 using XDA Free mobile app
For how long did you put your phone in the freezer?
bel57 said:
For how long did you put your phone in the freezer?
Click to expand...
Click to collapse
First few times like 15 to 20 mins. Then a little bit longer on the next few attempts. I thought it might work if the phone was a little colder, but still no luck.
Sent from my LG-E980 using XDA Free mobile app
It's not *a little*. First time it succesfully booted once put 30-45 mins in freezer, but not enough, since it started freezing after a few minutes of use.
I managed to retrieve my data after leaving it for at least 1-2 hours in freezer.
Going to shop to get back my device and try it..
trying the freezer method but not getting success. i guess it needs a big freezer.
Riiip
Thanks for posting - this method works! It took me a few tries to get it right - put the phone, no cover, in a ziploc, with battery inserted for over an hour in the freezer. Take it out of the bag, and let it boot inside the freezer (door closed), with back/battery resting on icepack or frozen bag of veggies. Once booted, connected the USB to laptop (with freezer door still closed as much as possible), and transferred all data! It seemed pretty stable and fast by that point. Upon taking it out, it went into bootloop again. No moisture damage.
I too tried this method, but no luck..
Tried letting the phone in the freezer for 10-20 minutes, no change
Let the phone in the freezer 40 minutes, nothing at all
Let it for 1 hours, same again
Let it for 2 hours and nothing seems to happen. It keeps bootlooping.
Maybe i'll try one last time putting both the phone AND the battery for maybe 4 hours, then power it on, see what happens...
why not make a KDZ with big cores disabled.. all the ones work but only for 815-815p. no 811 or 810
Well my replacement phone I got from lg has done this again. Yay me!
And my replacement phone broke again.. The freezer method worked again. But the replacement (my 2nd boot looping phone) usually won't even Boot Loop. When I plug it into a charger nothing happens. Insert a full battery and try to turn it on, nothing happens. I had to press on the back really hard to get any power to the phone. Then I was able to use the freezer method for a few days, my replacement has came and I cant get it to work again. I just wanted to double check that everything was backed up, I may be out of luck...
NVM, just realized this is the G4 forum, not the v10. Best of luck with bootloop issues.
celsius0010 said:
Thank you to the members on here, reddit, and other Android sites for the helpful insight. I did tons of research because I could just not stomach losing everything on my phone. I'm actually glad this happened because I will never be this careless again. I've been coming on this site to mod my phones since the PPC-6700 and have never heard of this issue. But SD cards fail and drops happen so that's no excuse.
I was able to get my defective phone to boot by freezing it for about 15 minutes in large freezer, and letting it run inside the freezer. I have heard of people being able to recover data by freezing the batteries and one person suggested to run your phone in the freezer. I tried it and it worked.
Before I tried the freezer method I was only able to get to the Android is Upgrading screen maybe 10 times out of over 100 boot loops. The farthest I ever got on that screen was 8 out of 101 apps. With the freezer method it fully booted on the first try.
First I froze the battery alone for maybe 20 minutes. Then I placed the battery in the phone and tried booting into recovery. It didn't work. So I removed the battery, put it back in and and let both of them sit together for about 15 minutes in the freezer. Then I returned and the phone fully booted on the first try. I tried booting into recovery from Nandroid Manager but that just reset the phone. Since it seemed stable and I wanted to keep the phone as cold as possible I just used My Backup Pro and Titanium Backup to back everything up.
I honestly gave up and I am sending my phone to LG today, so this was literally my last resort. Hope this helps someone.
Click to expand...
Click to collapse
celsius0010 said:
And my replacement phone broke again.. The freezer method worked again. But the replacement (my 2nd boot looping phone) usually won't even Boot Loop. When I plug it into a charger nothing happens. Insert a full battery and try to turn it on, nothing happens. I had to press on the back really hard to get any power to the phone. Then I was able to use the freezer method for a few days, my replacement has came and I cant get it to work again. I just wanted to double check that everything was backed up, I may be out of luck...
Click to expand...
Click to collapse
bel57 said:
Thanks for the tip, it helps! Confirmed working, left my phone 20 minutes in the fridge => boot but freeze during LG animation (not cold enough)
left the device in the freezer for a moment => success boot, but freeze minutes later once it gets warmer
So... there is a problem with some hardware pieces..
Click to expand...
Click to collapse
revo420 said:
It still took dozens of tries to get everything working over a couple of days but using this method I was able to backup all my data and even wipe the phone! Just keep trying and keep it cold in the freezer. Also, charge your battery to 100% constantly rebooting drained the battery quickly. The CPU gets hot even when it looks like its running fine, keep it in the freezer while it does its commands.
Click to expand...
Click to collapse
bel57 said:
It's not *a little*. First time it succesfully booted once put 30-45 mins in freezer, but not enough, since it started freezing after a few minutes of use.
I managed to retrieve my data after leaving it for at least 1-2 hours in freezer.
Click to expand...
Click to collapse
HELLO.
THANK YOU EVERYBODY FOR YOUR INPUT.
I am getting a replacement in 3 days but I still want to get all of my data. It's great that it worked for all of you.
Though, I have not tried it because I'm afraid that it will trigger the LDI (Liquid Damage Indicator, apparently there is a white paper indicator that turns pink/red when in contact with water or moisture. It can be located either above the SIM/SD card slot (circle-shaped), near the battery contact (square-shaped) and/or on the battery itself (circle-shaped) - near the contact, also).
Did your device got wet or moist after you did this method? Any of your indicators turned pink or red?
Is there an extra precautious way to NOT get it moist or wet?
A reply is VERY MUCH APPRECIATED.
Thank you in advance,
Liv
(Please see post #4 as the issue has evolved)
I recently updated my husband's HD from CM 11 to CM 12.1 (the one build in @amaces obsolete folder). This restored some functionality to a few apps that had "moved on" beyond KitKat and preserved the HMDI functionality. Everything else is essentially the same. Except.
Too often on starting the tablet up in the morning it shows about the same battery level as at shutdown the prior evening (maybe 50-ish) and then in a matter of minutes nosedives to 1%. You can see the behavior on the power usage graphic in Settings and it's pretty shocking. There's a vertical line for when it booted up and then *bam*, it drops to essentially nothing. If the tablet is plugged in for just a moment, the battery level returns to normal and everything is fine. It can be disconnected from the power supply and behaves normally the rest of the day.
So this is annoying (moreso because I need to hear about it every time it happens ). I've read the entire (unofficial) CM 12 thread. This issue comes up once or twice and seems to be "resolved" by "calibrating" the battery either with an app from the PlayStore or without. The app seems to just delete a file that would be overwritten at boot anyway from what else I have read on the subject, but the main idea is to drain the battery to an actual 1%, shut down and charge (the tablet remains "off" although the screen is on) until you've got 100% (which has to be judged by the green LED since the tablet is off).
I tried this (with the app), beginning by wiping cache and dalvik cache. It seemed to work for awhile. Then I foolishly suggested doing a backup. I did this with the emmc TWRP and everything seemed to go well except the battery indicator issue started up again...
So we did the battery thing again.... And it was just fine until this morning (not what you want to hear as you sit down to breakfast).
Clearly one could live with this if you always have the charger close at hand, but it's pretty lame. The tablet behaves beautifully in all other respects. I don't think it's a hardware issue as it started right after flashing the new ROM.
One person in the CM 12 thread actually praised the ROM as eliminating this issue which he had from CM 11!
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough. If I reflash the ROM do I have to reflash GApps also?
Suggestions? I'm really at a loss here.
nmyshkin said:
...
Is this a flashing glitch which might be fixed by reflashing the ROM? I'm loath to do a clean install and reconstruct everything again after such a short time, but I wonder if a "dirty" install (don't wipe data, right?) would be enough.
Click to expand...
Click to collapse
I doubt if a dirty flash would change anything, but there does not appear to be any penalty to try it out as a shot in the dark.
If I reflash the ROM do I have to reflash GApps also?
Click to expand...
Click to collapse
Not if you don't wipe /data -- basically same as in the case of a dirty upgrade.
digixmax said:
I doubt if a dirty flash would change anything, but there does not appear to be any penalty to try it out as a shot in the dark.
Not if you don't wipe /data -- basically same as in the case of a dirty upgrade.
Click to expand...
Click to collapse
I finally got around to this after much complaining about the issue and now I've managed to make it much worse. Before, the tablet would drop from the 50's (or lower) to 1% on boot. Higher percentages of charge were usually safe. Now it goes through the boot process up to the animation and then abruptly shuts down UNLESS the power cable is connected, regardless of the state of battery charge. If the cable is connected boot occurs normally and you can disconnect after boot is complete and everything is "fine".
Except, of course, it's not "fine" at all. Unless you have the charger and cable with you at all times, the tablet has to be left on when you're on the go.
Ugh. Any ideas besides going back to stock and starting over?
nmyshkin said:
I finally got around to this after much complaining about the issue and now I've managed to make it much worse. Before, the tablet would drop from the 50's (or lower) to 1% on boot. Higher percentages of charge were usually safe. Now it goes through the boot process up to the animation and then abruptly shuts down UNLESS the power cable is connected, regardless of the state of battery charge. If the cable is connected boot occurs normally and you can disconnect after boot is complete and everything is "fine".
Except, of course, it's not "fine" at all. Unless you have the charger and cable with you at all times, the tablet has to be left on when you're on the go.
Ugh. Any ideas besides going back to stock and starting over?
Click to expand...
Click to collapse
I came across a post that suggested returning all the way to stock and doing a factory reset, then rebuilding the system.
Once at stock I had no trouble completing a boot without being plugged in. So that is not a hardware issue. I didn't stay on stock long enough to see if the battery indicator behaved, but I'm guessing it did. I prepared a completely new SD card with newly downloaded files and proceeded to do the needed flashing for CM 12.1 w/GApps, using CWM 6.045. It all seemed to go well--even no screen flashing--until I unplugged the tablet so I could easily remove the SD card and reboot. As soon as I removed the power cord the periodic screen flashing that seems to be common during CWM use started up.
I rebooted and got only so far with the CM logo before the tablet shut down.
I don't get it. It worked fine before. What about this process could be causing this odd behavior?
Edit: in desperation I tried flashing The ROM again right over the prior installation. This time I booted into the emmc CWM (6.0.4.6) and waited for the tablet to calm down. Then I unplugged it and flashed the ROM from the ext.SD card. No error messages. I held my breath and rebooted. I got to several iterations of the cyan android face and then it shut down again.
Next I flashed TWRP 2.8.7.4 to emmc and tried flashing the ROM from the ext.SD card that way. Same result.
The battery charge shows 80% so it's not like the tablet is running on fumes and it's hard to believe the problem is the battery or the indicator since none of this happens on the stock ROM.
I just don't get it. We don't want to go back to stock but I don't understand any of what is going on. Initially CM 12.1 was working beautifully. Then the battery indicator issue started. I addressed that as best I could and when it seemed like we had that on the run I did a backup. That resulted in this shutdown issue. You can use the tablet just fine if you never turn it off and keep either the charger or a portable power pack handy (don't forget the cable!).
I really need some help troubleshooting. I'm willing to try just about anything.
Edit: indeed, the last resort was to buy another HD... But it turns out the booting issue was caused by an SD card that somehow was not properly prepared as 0x0C FAT32 LBA but was instead something else which I don't remember now (something with a "b"). Anyway, once a new card was carefully prepared, the tablet booted fine without being plugged in. Whether this also solves the battery indicator issue remains to be seen.