Rooted using Indirect's sd method, installed CM7 to internal using clockwork mod. I installed CM7 around tuesday, and nothing happened for a while. Then, I woke up this morning to try and do stuff with it and it booted up fine. My touchscreen was acting wonky (a hardware problem) so I turned it off to reboot, and when I went to turn it back on it got to the CM7 splash, and turned off and rebooted itself. It kept doing that for a while, and I let the battery run out. I then plugged it into my PC and it gets to the "N" screen (where it says powered by adobe reader technology or whatever) and it reboots. It has not gotten past that screen. It makes my computer spaz out by starting the "Found New Hardware" wizard for "OMAP4430". I have no idea what that is. My computer then thinks I am unplugging the Nook and plugging it back in (It makes that sound when you unplug a USB and plug it back in). Any help would be appreciated.
TL;DR My nook is in what I think is a bootloop, I can't access the internal storage from a computer, omfgwtfbbq.
EDIT: I have taken my SDcard out, that was suggested earlier. Could this possibly have something to do with the fact that I cleared all my SDcard contents from the CM7 options menu? I also cannot access my nook or SDcard by plugging it into my computer, I suspect that has something to do with the unplugging and plugging back in sound mentioned above.
off course will do this
My computer then thinks I am unplugging the Nook and plugging it back in (It makes that sound when you unplug a USB and plug it back in
Click to expand...
Click to collapse
because you have it plugged in to your computer so every time it reboots (bootloop) it unmount your sdcard and mount it again when it start to boot.
You should not "charge" it while plugged in your computer , charge it as normal with the adaptor for a while first (remove your sdcard better) once it's charged start troubleshooting it.
~ Veronica
lavero.burgos said:
off course will do this
because you have it plugged in to your computer so every time it reboots (bootloop) it unmount your sdcard and mount it again when it start to boot.
You should not "charge" it while plugged in your computer , charge it as normal with the adaptor for a while first (remove your sdcard better) once it's charged start troubleshooting it.
~ Veronica
Click to expand...
Click to collapse
Unfortunately, that's where I first figured out it was doing the bootloop thing. The sd card is not in the nook, and it's still in the loop while plugged into a wall adapter. It's almost like it doesn't have enough power to start up, but the charger is giving it just enough to get to the "N" screen.
Maggot226 said:
Unfortunately, that's where I first figured out it was doing the bootloop thing. The sd card is not in the nook, and it's still in the loop while plugged into a wall adapter. It's almost like it doesn't have enough power to start up, but the charger is giving it just enough to get to the "N" screen.
Click to expand...
Click to collapse
No bootloops are cause more for a software issue, and sometimes sdcard can be the root of the problem.
let it charge for an hour at list. Then turn it off boot into CWM and see if you can flash the ROM again. Report back if you get any error while trying to use CWM as normal but please do not take the plunge to format everything you find in there or you will regreat it.
It is safe to wipe data, cache, dalvik cache and format system... that is your limit.
~ Veronica
lavero.burgos said:
No bootloops are cause more for a software issue, and sometimes sdcard can be the root of the problem.
let it charge for an hour at list. Then turn it off boot into CWM and see if you can flash the ROM again. Report back if you get any error while trying to use CWM as normal but please do not take the plunge to format everything you find in there or you will regreat it.
It is safe to wipe data, cache, dalvik cache and format system... that is your limit.
~ Veronica
Click to expand...
Click to collapse
That's the problem, it can't charge. As soon as it gets enough juice to power on, it uses all of it and powers down again.
It's been charging, from a wall charger, with the sd card out, for around 4 hours now and it's still doing the loop thing.
Maggot226 said:
That's the problem, it can't charge. As soon as it gets enough juice to power on, it uses all of it and powers down again.
Click to expand...
Click to collapse
This happened to me a while back. You just have to leave it alone for a while, and it will eventually (~20 minutes or so) power on correctly.
ckevinwelch said:
This happened to me a while back. You just have to leave it alone for a while, and it will eventually (~20 minutes or so) power on correctly.
Click to expand...
Click to collapse
Leave it alone as in unplug it from the charger? Or keep it charging?
Maggot226 said:
Leave it alone as in unplug it from the charger? Or keep it charging?
Click to expand...
Click to collapse
Plugged in.
Left it alone unplugged (After leaving it plugged in for around 3 hours) and it appears there is absolutely no juice left in it. I reinstalled CWM on my SD card and put CM7 on my brother's Nook, and now I'm waiting to see if CWM will boot... Crossing my fingers.
Maggot226 said:
Left it alone unplugged (After leaving it plugged in for around 3 hours) and it appears there is absolutely no juice left in it. I reinstalled CWM on my SD card and put CM7 on my brother's Nook, and now I'm waiting to see if CWM will boot... Crossing my fingers.
Click to expand...
Click to collapse
So you're saying it would not boot after leaving it alone (plugged in) for three hours? I'm assuming you were plugged into the stock charger and cable? Perhaps try plugging into a PC for a while. I'd also try turning it on while plugged in (if you didn't already).
ckevinwelch said:
So you're saying it would not boot after leaving it alone (plugged in) for three hours? I'm assuming you were plugged into the stock charger and cable? Perhaps try plugging into a PC for a while. I'd also try turning it on while plugged in (if you didn't already).
Click to expand...
Click to collapse
It would turn on, but yes, it would not boot to the menu. It wouldn't get past the "N" screen as stated in the OP. I was plugged into the wall charger and using the cable I received with the Nook. I've had it plugged into the computer for around a half hour, and I have attempted to turn it on with no success. I'm really wondering what this "OMAP4430" thing is. My computer is wanting to find software for it, the "Found New Hardware" wizard starts up every time I plug my nook in.
It's fixed, I let the battery run completely out, booted from CWM and wiped everything. I reinstalled CM7 and it's working like a charm. Mods can lock this thread.
Related
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
Hey all for some odd reason once I plug in the usb cable, the NT just reboots and starts bootlooping on cyanoboot screen while loading emmc. if i don't have the usb cable plugged in it will boot just fine with no bootloops whatsoever. have any of you encountered this problem? I had cm10 running on it and thought it was a bad flash, reflashing didn't help and restoring to a cm7 backup didn't do the trick either...
any ideas?
Can you charge with wall socket plug and usb?
demetris_I said:
Can you charge with wall socket plug and usb?
Click to expand...
Click to collapse
determines on your definition of charging. since it keeps on bootlooping endlessly on cyanoboot is it considered charging?
when i had flashed your cm10 rom on the cyanoboot screen it says charging disabled. so i assume that means its not charging?
if i have the usb cable plugged in and i turn the NT off completely by holding the power button, it will shut off but then come straight back on since the usb cable is sitll plugged in.
boots fine without the usb cable, but once the usb cable is inserted it just instant reboots and the bootlooping on cyanoboot starts.
do you think it may be hardware failure?
ShinnAsuka said:
determines on your definition of charging. since it keeps on bootlooping endlessly on cyanoboot is it considered charging?
when i had flashed your cm10 rom on the cyanoboot screen it says charging disabled. so i assume that means its not charging?
if i have the usb cable plugged in and i turn the NT off completely by holding the power button, it will shut off but then come straight back on since the usb cable is sitll plugged in.
boots fine without the usb cable, but once the usb cable is inserted it just instant reboots and the bootlooping on cyanoboot starts.
do you think it may be hardware failure?
Click to expand...
Click to collapse
Cyanoboot screen saying charging disabled is normal.
Before we can say is a hardware failure, if you hold N can you stop Cyanoboot?
If you can stop it select recovery and leave it there 20-30 minutes.
demetris_I said:
Cyanoboot screen saying charging disabled is normal.
Before we can say is a hardware failure, if you hold N can you stop Cyanoboot?
If you can stop it select recovery and leave it there 20-30 minutes.
Click to expand...
Click to collapse
yeah i can stop it and select recovery and it will boot into recovery. this is assuming the usb cable is not plugged in. whatever state the NT is in, once the usb cable is plugged in, it will auto reboot and start bootlooping on cyanoboot.
i have already requested for a replacement from B&N, so i don't know if leaving it on for 20-30 minutes is an option at this point. i plan to wipe the thing completely using adam's total wipe before i send it back to them.
i am afraid that if i leave it on for 20-30 minutes the battery will die and i won't be able to boot from sd to initiate the total wipe by adamoutler.
ShinnAsuka said:
yeah i can stop it and select recovery and it will boot into recovery. this is assuming the usb cable is not plugged in. whatever state the NT is in, once the usb cable is plugged in, it will auto reboot and start bootlooping on cyanoboot.
i have already requested for a replacement from B&N, so i don't know if leaving it on for 20-30 minutes is an option at this point. i plan to wipe the thing completely using adam's total wipe before i send it back to them.
i am afraid that if i leave it on for 20-30 minutes the battery will die and i won't be able to boot from sd to initiate the total wipe by adamoutler.
Click to expand...
Click to collapse
You are right, is a hardware problem. Go get a replacement.
so i got the replacement a week or so ago, and this replacement is now having the same problem... what in the world is going on. i am using your rom with the sgt7 enhancements. is it possible that the governor being on hotplug may be the problem?
EDIT: changed it back to the default ondemand governor... the problem is still there... how is this possible.
All this make me think is a bad flash.
Check your rom for any corruptions
demetris_I said:
All this make me think is a bad flash.
Check your rom for any corruptions
Click to expand...
Click to collapse
i restored to the 1.4.2 factory stock image that i made with cwm when i first got my replacement nook. same problem exists... i think it has something to do with the usb port getting bent or something...
How you manage to bent a brand new usb port?
So, take it back again for a replacement.
demetris_I said:
How you manage to bent a brand new usb port?
So, take it back again for a replacement.
Click to expand...
Click to collapse
thats the plan lol... the replacement nook was a pre-certified one. this time around they say they are going to send me a brand new one....
Same Problem on nook tablet cm 10.1 acclaim
I had the same problem with my tablet after I allowed the battery to drain completely while using it. I have to mention in my situation I had lost the original charger that came with my nook and I've been using a wall charger from my cell phone. When I had the stock barnes & noble nook tablet plugged in I noticed that the device would say that it's not charging even though it really was. It just took a longer time to charge. More than likely i had a voltage difference between the two devices. I too was stuck in that cyanoboot loop where there was not enough power to load the operating system and cyanboot wouldn't indicated if my battery was in fact charging. I had two solutions to this; I left my endless loop on overnight and in the morning low and behold i was booted into cyanogenmod. My other solution was to leave the device off for a long period of time and then try again. Hopefully this helps anyone else out in the future.
I bought three nook tablets, put NT-CWM-SD on a sd card then installed sgt7-10-20121209-meghd00t-acclaim on all three.
All three ran great installed many apps on each one. Once all three battery drained none of the tablets turn back on. The N on the usb charger is green and has been plugged in for 24 hours.
One known/reported issue with many recent CM10 builds is the NT while asleep will not detect USB cable insertion and kick into charging mode; one would have to wake it up with the power button or "N" button for it to go into charging mode (afterward one then put it back to sleep with power button and it will stay in charging mode).
I suspect your problem might have the same underlying root cause.
The only "shot in the dark" thing I can suggest trying is to stick in a bootable SD card (e.g., your CWM SDcard), then insert the powered USB cable -- hopefully with luck that would jolt the NT to boot up and go into charging mode. Please provide feedback on whether this works.
I would also suggest that you report this on the SGT7 development and CM10 support threads -- so that other CM10 users know not to ever let their NT battery completely drain.
If it's anything like mine you cannot plug it in to charge while it's in standby. The "n" turns green right away. I have to "wake it up" and then it starts to take charge. ("n" turns orange)
Edit: LOL! Digixmax posted while I was writing!
asawi said:
...
Edit: LOL! Digixmax posted while I was writing!
Click to expand...
Click to collapse
Great minds think alike
Joke aside, I am now really concerned -- previously it had not occurred to me that the problem the OP reported is a logical and fatal corollary of the problem you/I/others had seen/reported.
If the bootable cwm doesn't do it, try making a bootable cm7 (this rom didn't have the bug)
NT no longer charging or waking up
baberswallet said:
I bought three nook tablets, put NT-CWM-SD on a sd card then installed sgt7-10-20121209-meghd00t-acclaim on all three.
All three ran great installed many apps on each one. Once all three battery drained none of the tablets turn back on. The N on the usb charger is green and has been plugged in for 24 hours.
Click to expand...
Click to collapse
I experienced this type of problem a few days ago on my NT. I replaced my charging cable and it started working fine.
nigelshea said:
I experienced this type of problem a few days ago on my NT. I replaced my charging cable and it started working fine.
Click to expand...
Click to collapse
Could it maybe be that you need to force a reboot or reset or whatever by holding the PowerOn and N keys at the same time? For a 20 second count on my NT 16GB.
It would be great to hear back from the OP if any of the above suggestion works.
Ok i rooted with sd_root_NT16or8gbV4_7 and have go launcher installed. This is my wifes nook so she might have installed something that is keeping it from working i plan to look at it closer tonight. My problem is that it will not connect to the computer and it will not charger while turned on with the wall charger or with the computer. If i turn the nook off it charges fine. When the nook is on the LED is green while in wall or computer. Power off and the led turns orange till its full then turns green. Ill post more info tonight but if youve had this problem please let me know what has helped you.
outridger
outridger said:
Ok i rooted with sd_root_NT16or8gbV4_7 and have go launcher installed. This is my wifes nook so she might have installed something that is keeping it from working i plan to look at it closer tonight. My problem is that it will not connect to the computer and it will not charger while turned on with the wall charger or with the computer. If i turn the nook off it charges fine. When the nook is on the LED is green while in wall or computer. Power off and the led turns orange till its full then turns green. Ill post more info tonight but if youve had this problem please let me know what has helped you.
outridger
Click to expand...
Click to collapse
My nook occasionally does this also, but if the green light is on while charging its still charging the battery. Its not recommended to charge the nook while off(one reason why it will turn on while charging.)
ive left it plugged in over night with the screen off and powered on in the morning it was off and had no battery it had about 50% when i plugged it in.
outridger said:
ive left it plugged in over night with the screen off and powered on in the morning it was off and had no battery it had about 50% when i plugged it in.
Click to expand...
Click to collapse
Maybe just the root method not allowing it. Have you tried any other methods? If you have an SD cards around you can try making a boot able cm10 card and see if it charges. It won't affect any of your nook's internal settings,apps,etc.
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write to an SD card and put it in your nook. If it charges from there then the root method you have is messed up. Make a backup and try another or a custom ROM.
maybe its been rooted for about 6 months though and this is a new problem within the last month. Thats the kicker i guess since it shouldnt update i dont know if there is a setting somewhere that would stop it from charging. Im going to look into the go launcher widges to see if one of them has that option first i think. ill update in about 8 hours once im home. thanks for your help though m8
ok im home and reset go launcher to stock form. my software version in 1.4.0 ota blocked.
still get a greed light on cord and its still not charging. also if i run NookHWTest and try to run the usb/charge it says that the cord is not connected
outridger said:
ok im home and reset go launcher to stock form. my software version in 1.4.0 ota blocked.
still get a greed light on cord and its still not charging. also if i run NookHWTest and try to run the usb/charge it says that the cord is not connected
Click to expand...
Click to collapse
I found a few threads that suggested to restore back to factory reset and re-root your device. You can use a backup app like Titanium Backup to save all the apps, pictures etc.
Something in the /system directory gets messed up, but no one knows why.
My NT will only start charging if I turn the screen on after I plug it in, or plug it in with the screen turned on. After that, I can let the screen sleep, or turn it off right away.
If I don't do this, the light on the charger stays green and it won't start charging.
Connecting to the computer isn't affected by this, though.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
well reset to factory and still doesnt charge while on. The cord works in the other nook so im going to say the port in the nook is going bad. On a side note went to [ROM]{WIP} SGT7+CM10.1+Cherry Picks,By meghd00t. 24/02/13 and it seems to be very stable so far compaired to the others ive tried in the past
outridger said:
well reset to factory and still doesnt charge while on. The cord works in the other nook so im going to say the port in the nook is going bad. On a side note went to [ROM]{WIP} SGT7+CM10.1+Cherry Picks,By meghd00t. 24/02/13 and it seems to be very stable so far compaired to the others ive tried in the past
Click to expand...
Click to collapse
Oh, you should have said something about it working with the other one. The ports for these can get messed up all the time. Happens a lot.
Turn the nook off when charging. This is a known bug.
Sent from my NookTablet using xda app-developers app
I wanted to share this experience in case it happens to anyone else. I rooted my nook tablet and installed CM and everything worked great. This is a full install to the OS, not running from SD card at all, no SD card present. However, the battery ran low into the red zone and shut down the tablet. I plugged it in and it tried to start up without me even hitting the power button, as if it was in deep sleep and tried to wake up when it saw power. But, because it didn't have enough juice it would only get to the CWM menu screen and it would power cycle and start over again. I did the power/volume reset but that wouldn't shut down the tablet completely because every time I would plug it in it would try to restart again. Finally I was able to get it to run long enough to get to the CWM recovery menu and quickly choose power down option at which point it began charging without trying to restart. After I let it charge for an hour it reached about 60% at which point it started fine and has been fine since. It's a reminder to not let the battery drain too low because I'm not sure if this was a one time thing or if it is going to happen every time the battery drains low.
I had the same issue, my solution was to keep powering it on until it drained the battery completely. Finally I got a warning message that the batter charge was too low to power up. At this point you can plug it into the charger and it won't try to auto start.
I have a similar (maybe the same issue). But I have an additional one, because I am using a SD card. 2 Things to care about:
1. Use a powerful enough charger and just plug it in, it might boot cycle automatically, but at some point it will boot correctly... For me the charger of my Motorola Defy (850mA) with the original Nook charging cable works.
2. Leave the SD card removed while booting (I just "click" on it, so it is removed but still "connected" to the case), otherwise I also just get never-ending boot cycles for some reason - but maybe this SD card is "partially bootable" for some reason (though I never used it as a bootable SD card...)