Database Develop

Boot loop

And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk

I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.

Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.

Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.

What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App

Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?

sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)

Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?

Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.

Cal you never mentioned if you cleared the user data... Did you?

Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)

cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.

Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?

I ran into the same problem, trying the same solution - any luck the second time?

JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...

confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks

[Q] Help, I think I've bricked my phone!

So, I'm sure there have been about 100000 thread with a title like this, but I did something incredibly stupid.
I was prepping my phone to flash the newest version of aosp's gingerbread mod by wiping pretty much the whole thing (boot,system,cache,data), and when I went to flash the zip (I put it in the sd card while in recovery) I wasn't seeing it in the list of files when I went to look for it in the "flash zip from sd" in clockwork recover 2.5.01. Well, when I was going to go to reboot recovery in the advanced menu, I accidentally had it do a normal reboot, and pulled the battery because I knew there was no rom for my phone to start up on. Now it doesn't turn on at all, no recovery no nothing. This is somewhat expected since the boot.img is gone now, and adb obviously can't see my phone. Is there anyway to save my phone, or am I totally screwed?
Any response is welcome, I'm kind of in a panic right now because I don't want my dad to find out
And please, no bashing, I realize I should have been more careful, but we can't exactly waltz into that time machine and redo it.

Same exact thing happened to me in your post. No recovery,bootloader, nothing. Just HTC screen at boot with no ROM loading.

When you say it won't turn on at all... did you try:
Pull battery
Replace battery
Press and HOLD the Volume Down button on the side of the phone
Press and release the POWER button (keep holding the Volume Down button)
This should get you into HBOOT / Fastboot... anything there?

Plug it into charger and let it sit, I had the same thing happen when flashing mine back to stock, right before I was shipping it to the buyer! I was freaked out, lol. It came back after a few minutes on charger though.

Man I thought the same thing happened to me. But try charging for forty minutes then mess with it
Sent from my HERO200 using Tapatalk

cordell12 said:
Plug it into charger and let it sit, I had the same thing happen when flashing mine back to stock, right before I was shipping it to the buyer! I was freaked out, lol. It came back after a few minutes on charger though.
Click to expand...
Click to collapse
What cordell12 Said... Worked For Me!
Sent from my HERO200 using XDA App

[Q] Is my nook color bricked?

I had FroYo running on eMMc and all was running smoothly until I went to reboot it and now the screen will not turn on. I have held the power button for a long time and tried pretty much every button combination to get it to power on. I also tried plugging it in and still nothing. Is my nook bricked?

Have you tried booting Froyo on a SD card?
If you don't even see anything on the screen maybe it's a hardware failure..
Were you overclocked?

I put froyo on a 2gb card and i still cant get it to boot. Is there a specific key combination i need to use to get it to boot off of the sd card?

Are you sure that battery wasn't almost dead? Try booting it while plugged in for a bit.

I've had it plugged in for about 10 minutes and ill try to boot it in a second. Whats my next course of action if that doesnt work? and thanks for the suggestions so far.

Still a no go on the boot. Im going to let it charge overnight and give it another go in the morning.

when I power my nook on by holding down the power button eventually the screen will "light up" (even though it will stay black, you can tell the backlight has come on). is it doing that, or just never seems to respond?
I had an issue once running Nookie Froyo where I thought my Nook was dead and realized it was actually on after a while. Only way I found it was that I saw it on my network via my router when checking something else. No matter how long I held the power button down it never seemed to do anything. After a while of fiddling the screen finally lit up and I could get in.
If you plug it into the USB port on your computer, does the computer see it and load the driver for it?

digeratix90 said:
I've had it plugged in for about 10 minutes and ill try to boot it in a second. Whats my next course of action if that doesnt work? and thanks for the suggestions so far.
Click to expand...
Click to collapse
Unless you're using the B&N supplied cable, the NC takes a REALLY long time to charge. I inadvertently let my battery drain and tried charging it using my EVO's USB cable and still couldn't use it more than an hour later, with the "try again in 15 minutes" warning on the screen the whole time.
Hope you managed to fix your problem and that your NC is functional again.

I had the same problem and I could actually replicate it. I had froyo running emmc. What I did was clear out some cache and data from market, Google framework, and also the download manager since I had the market download unsuccessfully problem. Right after I cleared the cache and data then force close the Google framework application (and of course reboot), I couldn't turn on the nook color anymore. I know the device wasn't dead because I got feedbacks if I do.SSH. I flashed the rom again and it came right back on. Then I did the same steps for the cache and data, the device once again couldn't turn on.

Ok i let it charge overnight with the b&n cable (the light was green this morning) And I tried to turn it on again. The screen still does not turn on and the backlight does not turn on. I do not get any response from the computer when I plug it in. I think that I may have bricked the hard to brick nook color :/

I ran into this very same issue a moment ago, and I just followed these steps:
http://forum.xda-developers.com/showthread.php?t=931720
In your case, you want to install the CWM to the SD with the nook 1.0.1 software zip, insert the SD card into your nook, then press and hold down the power and the N button ... and it should boot into CWM then continue with the rest of the steps.

Thanks for the help everyone. I think I may have had a coincidental hardware failure. I took the nook color to b&n today and they tried everything to get it to work and they were going to try to send me a refurbished one, but I asked for cash instead so they gave me a new one on the spot. I am going to stay away from the froyo stuff until it is a little safer (hopefully I can hold out until CM7 comes out)

I can confirm this is definitely a problem with the current Froyo build (.6.7). After loading it to my EMMC and loading Google Apps, I had the blank screen, no reboot issue after I sent the adb reboot command. Thinking I had bricked it (charging, holding the power button, etc. wouldn't do a thing), I popped in an SD card with bootable froyo on it and now the thing powers on and boots to SD. If I take the card out, it goes back to it's dead state.
I'm downloading the stock FW and going to reflash it, but I just wanted to confirm that this is a problem and it probably wasn't a coincidental hardware failure.

backlund said:
I can confirm this is definitely a problem with the current Froyo build (.6.7). After loading it to my EMMC and loading Google Apps, I had the blank screen, no reboot issue after I sent the adb reboot command. Thinking I had bricked it (charging, holding the power button, etc. wouldn't do a thing), I popped in an SD card with bootable froyo on it and now the thing powers on and boots to SD. If I take the card out, it goes back to it's dead state.
I'm downloading the stock FW and going to reflash it, but I just wanted to confirm that this is a problem and it probably wasn't a coincidental hardware failure.
Click to expand...
Click to collapse
I'm having the same issue. Nookie Froyo .6.7 on emmc. Completely dead and not recognized by computer usb. Will try the SD bootable froyo.
Edit: Ok, I was able to boot off the sdcard, but can't get to recovery. If I remove sdcard it won't boot. I guess I'll have to put the recovery on the sdcard to reflash a rom.

I had the same issue when using Froyo 6.6 to EMMC.
I really thought I had bricked it and out of Desperation I made a CWR card put it in and tried every button combo I could think of and low and behold it booted back up. lol, now I'm back to stock 1.1 rooted. I think I will wait till CM7 is out for the nook before writing to EMMC again.
But man props to the makers of the nook color, 99.9% Un-brick-able

Yeah I had a couple issues with throwing an image on the first time I went to root it, just re-formatted and put a diff image on the SD and everything was fine....

Ugh, I'm glad I'm not the only one having this problem. Now I get to walk through the recovery.
Update:
So after walking through the recovery, I still couldn't get it to boot. It wasn't until I performed step 5 that it finally worked.
http://forum.xda-developers.com/showthread.php?t=914690&highlight=cwm

Random Reboots, unable to complete a boot

OK Guys, here is my issue... I searched the forums and had no luck for what seems to be my problem, nor did a google search return anything.
I got my Nook back in Febraury, and it worked great, right away wound up putting NF 0.6.7 on the eMMC and life was peachy. I hadn't been using it much, had been waiting for CM to get to a stable release so I could put that on there and call it good.
Anyways, I'm using it one night, full battery, I turn the screen off, head to bed. The next day I try turning it on, nothing happens, tried all the key combinations, but wouldn't start. My microSD adapter was broken and was waiting for a new one so couldn't try much.
Just got the adapter yesterday so I went ahead and made a CWR bootable SD card (not ext4) and booted it up, but it was doing the weirdest thing, The whole screen was flashing, like how the screen will turn black if you press the power button while in CWR, it would blank the screen then come back momentarily, and then probably 10 seconds into it it rebooted itself. Thought this was pretty weird so tried booting again with the same results.
My next step was try download the SD image again, reburn it and try the process again. At some point I wound up trying the ext4 image because I wanted to install CM7 anyways. One time I was able to boot to CWR, and it didn't seem like anything was wrong, so I thought life was grand, wiped data/cache and installed the CM7 zip liek the instructions stated. Rebooted, nothing. Rebooted with the SD card in again and it was back to its old antics. Anyways, after many reburns and tries, I was able to get CWR to stay up long enough to flash the repartition boot with stock image. When I rebooted it would get to the N screen, and then bootloop like it's supposed to, did that 8 times, got to where it shoudl Factory reset itself, got the installing screen, and the Nook rebooted right before it was about to finish!
So ever since then it's been a struggle of trying to keep it up long enough to flash a stock zip, but I have had no luck, it literally reboots within 30 seconds of being in CWR. Tonight I'm going to try making a CM7/NF SD card to see if ti will stay booted solely off of the SD card, but not holding my breath since CWR won't stay.
To me it sounds like a hardware problem, all the keys work fine tho, power to boot and turn off, I guess i cant test volume keys but the N works just fine too. Didn't drop a glass of water on it, didn't leave it on top of a furnace or anything, I have no clue.
Crappy part is im outside of BB's return perios, and even if I wasn't, I threw the box away last week So what do you guys think? Am I totally missing something? Is it hardware? Can I send it back to B&N for a warranty claim? Not sure if they'd be able to tell it's been messed with since it appears stock now, and I don't feel like defrauding them, but if it's hardware it would have happend with or without a custom rom on there. Sorry for the long winded post and thanks!

does it behave when hooked up to your computer via usb? is it possible to complete the flashing using adb?

Hi,
It also sounds like the electronics might be intermittent - have you given the
unit a 'thump'?
Cleaned the uSD connections on the card (and maybe on the Nook?)
Probably not it, but in your long description above, you don't mention reformatting
to EXT4 all the correct partitions before installing CM7.
Good luck!
Peter

Animec said:
does it behave when hooked up to your computer via usb? is it possible to complete the flashing using adb?
Click to expand...
Click to collapse
Holy crap, it behaves perfectly when hooked up to the computer, i can mount it and everything, but as soon as i unplug it, it's up to it's old tricks, dimming the screen, going back to the lock screen, acting like the power button was pressed. I don't get it at all.. I'm going to do some research on pushing the partitions via adb...

spoke too soon, back to rebooting every time it gets to the N screen

pmilford said:
Hi,
It also sounds like the electronics might be intermittent - have you given the
unit a 'thump'?
Cleaned the uSD connections on the card (and maybe on the Nook?)
Probably not it, but in your long description above, you don't mention reformatting
to EXT4 all the correct partitions before installing CM7.
Good luck!
Peter
Click to expand...
Click to collapse
What kind of 'thump' do you recommend? lol, i tried cleaning the connectors, no luck, i actually didn't format any partitions to ext4 before i tried flashing the zip, i thought flashing it from an ext4 compatible sd card was the only thing you had to do? please tell me i missed something and we can fix it!

OK one more reply here..it seems to be behaving fine when its plugged into either usb or outlet, its almost like thinks it's dead unless its charging?

HI,
CM7 requires most of the partitions to be formated with ext4.
I found this posting to be the most useful for my install of CM7:
http://forum.xda-developers.com/showthread.php?t=960542&page=16
a little dated, but very detailed!
Looks like /system /data and /cache should be ext4.
I would be surprised if running CWM from external SD, if it is setup correctly
would just crash before you try and access the internal memory though.
-> have you tried a second uSD card?
Could it be a bad card plus badly corrupted mixture of stuff on internal emmc?
You mention in post that device looks ok with USB power adapter connected?
Perhaps intermittent battery connector? (Try holding unit at different angles?)
Thump: whatever you feel comfortable with without doing any damage(?)
Good luck!
Peter
jwood55812 said:
What kind of 'thump' do you recommend? lol, i tried cleaning the connectors, no luck, i actually didn't format any partitions to ext4 before i tried flashing the zip, i thought flashing it from an ext4 compatible sd card was the only thing you had to do? please tell me i missed something and we can fix it!
Click to expand...
Click to collapse

OK, morning report, left it plugged into the Nooks EOM charger cable over night, seems to be working this morning, its almost like the battery was dead...maybe i was using my Captivates charging cable instead of the Nook one? Anyways, everything seems to be better now, thanks for the help!

Nook color will not boot/black screen

my nook color will not boot at all. I formmatted /system and /boot, then it froze. Now I can't boot it up anymore. I was trying to update CM7.
Help please !
Thank you guys.

boot from an SD card. Works every time.

Even backlight doesn'flicker on.
Sorry, but I'll just borrow this thread for my Nook Color nightmare which may be more sinister than anyone else's on this forum.
I've read through Dummies Guide to Fixing 'My Nook Won't Boot' and was unable to come across a post that was able to solve my problem. However, there where three other posters who reported similar symptom as I, and who also were never able to find a solution.
I suspect that my NC, and the three other posters', is truly BRICKED.
Currently my situation is as follows:
- Attempt to power on NC does not yield any response, not even a flicker of the backlight turning on
- Cannot boot from uSD card that had previously successfully booted from in the past (have used it for flashing ROMs to EMMC).
- Attempt to power on while connecting to PC (XP) via USB causes computer to recognise device OMAP3630, but immediately loses it (NC unresponsive as per 1st point).
I had Nookie Froyo 0.6.8 on it for quite some time. And I think I witnessed it die. This is what happened: I turned on the screen using the N button. Everything seemed okay except that it was responding rather sluggishly to my inputs and gestures, and then it just froze (screen still on). I used the power button to try to cycle it but once it turned off that was the end.
I've already followed these suggestions:
- Press power button for 60 seconds.
- Press combination of Power, N, Volume.
- 8 boot attempts (as there is no visible response I press the button for 10 seconds, release it for 5, and then repeat that about nine times)
Hoping that someone could throw some suggestions around before I part with my expensive brick.

It's dead, Jim.
Why not do a warranty replacement?
Rodney

rhester72 said:
It's dead, Jim.
Why not do a warranty replacement?
Rodney
Click to expand...
Click to collapse
My thoughts exactly. Although I don't have extensive android experience, I've got a decent bit of PC time and that sounds like a problem based on faulty hardware rather than improperly installed software.
Sent from my NookColor using XDA Premium App

Other thing is, remember when messing around with flashing roms etc, that your battery is fully charged. Not sure about the nook, but for some phones, they don't charge while in this process and some people have bricked their phones while running out of power doing a flash.
I suspect you might have a battery problem and may not have a charge enough to boot from SD.

I'm in the same boat...
Same thing happened to me. I was fully charged, went to clockwork to boot while trying to update CM7 and now my nook is unresponsive. The only thing I get is the battery too low screen. It has been on its charger for 4 hours. If anyone has any suggestions...

I had the same problem.... wiped the boot and then was unable to boot even with SD card; only got black screen.. Then I decided to hold down the n and the power button at the same time and then after about five seconds I saw my screen flash and I let go of the power button and n buttons. Now the nook is booting fine off of my SD card once again... whew! Won't wipe boot again...

Time to replace this brick
lanje78 said:
If anyone has any suggestions...
Click to expand...
Click to collapse
Well, I've made the decision to exercise the 1 year replacement warranty.
I've been told by B&N customer support that you can simply walk in to a B&N store with the complete package (charger and cable) and they will replace it on the spot. Helps if you take the receipt with you.
For us people who live outside of the US it's a whole different kettle of fish...
UPDATE:
So I sent the NC back to my US seller and had it replaced under the 1 year warranty. I received a refurbished NC, but with the serial number starting with 2010... which I understand indicates a newer version.
I'm still wondering if OCing the NC may have cause the problem on my bricked one... I guess I will find out after I OC it again, which I am certain to do as it improves flash video play...