When I try to boot my nook, I get past the "Touch the Future of Reading" screen but get caught up on the "n" loading screen.
I've tried to interrupt the boot process physically 8 times to no avail.
I've tried to SSH in the 8 failed resets script, nothing.
I can't boot the nook far enough to be able to shell.
I tried to do a factory reset but it tells me "install failed", and has an image of a nook with a red circle and while exclamation point.
I installed Nookie-Froyo from flash and tried to use that but soon realized I was over my head.
So finally I called BnN to see if they could do something and they offered to replace it. If I send them this wonky device, will it raise some red flags in their system?
I would say try some other methods before returning it if possible. I have read others on the forum in the same situation as you and they have gotten it working again. It will take some time for someone with more knowledge to respond, but I think it is worth it.
If you return it it seems like you might have a high chance of getting one that has hardware/software issues from what many have posted. I would try to stick with what I had even if it took a week of getting help from the forums.
Have you tried booting the AutoNooter 2010-12-25 ? I have heard some boot the sd card and then they can ssh to 192.168.2.2 and do some recovery work on the nook, like I said I am not experienced in this but I have read other's posts on success stories
I've tried the ssh method and it would never make it past the n screen. I've also searched the forums and haven't seen anything about an "Install Failed" screen. If someone has seen something about that and could point me to it, I'll try anything.
If you see an N on the screen it means it is not booting from the we card. Maybe the we card wasn't written correctly? Was this rooted previously?
Sent from my NookColor
It was rooted and then stopped working after I left it in a very cold car all night long. I don't know if that's what caused it, but until I figure it out, correlation will equal causation.
As for the card, I reformatted and re-imaged it 3 times in the process of trying to re-root it; once with auto-nooter for 1.0.0 and twice with 1.0.1.
This is crazy, I have the same issue right now....it's stuck in the boot screen. Mine rooted perfect today, apps installed from market with no problem, I noticed the battery was low but wanted to reboot it after I noticed Youtube stopped working, I shut it back down and restarted it before I put it on a charger.....it hasnt rebooted since.
I did get it to boot into clockwork a few times, I did a factory reset from there but it still didnt help. Anyone have an idea? Did I permently brick this thing?
Related
I rooted my NC yesterday using the auto-nooter 2.12.25. Things seemed OK. I DLed some apps & used them. Got ADW launcher loaded and began setting it up for my preferences. The NC went most of the way through an update cycle even though I had already updated to version 1.0.1. However this time it never got to the green "n" and then it started cycling through the part where it comes up & writes "nook color", continues until the colors quit flashing & then starts back at "nook color".
None of the buttons seem to have any effect. I tried to follow the 'solution' entitled "NookColor Fix Boot Loops". I tried both the auto-nooter SD card and then when that didn't work, I tried the original manual nooter SD card.
Anyone have another idea to fix this. I'd really appreciate some help. A PM would be great or just answer here.
I had the same problem earilier today, I held down the power button until it did a complete reset (about 8 seconds of holding). It is working great since.
Thanks. I had already tried that, several times.
restore to factory and start again?
add http : // www to front of links with out the spaces i don't have the 8 post count needed to post links and
am not going to just reply needless info to 8 post to get rights to post links to help
don't get me wrong i believe it is a very good policy
unrooting
.nookdevs.com/NookColor_UnRooting
flashback to clean stock
.nookdevs.com/Flash_back_to_clean_stock_ROM
i have not tried any of these methods no need to but i do so much messing up
i guess eventually i will with that said this might be a long way around to your solution
read both carefully
Thanks, nookroot but this is not working.
Method 1 for unrooting - Holding those 3 keys together for over 30 seconds has no effect.
Method 2 for unrooting - I can't unroot with method 2 because the NC has to boot before I can go to settings.
Any other suggestions? In fact it seems that if it ever does power off, the only way to make it power on is to plug in its USB cord & this doesn't always work. When it does it just stats cycling. Sometimes it seems to just power up on its own and start cycling.
Whatever happened, since it's rooted I can't return it to B&N and I don't seem to be able to unroot it. Effectively I have bricked it even though many people say that's impossible.
Edit: something new just happened & I was able to go through the method 1 reset. It's booting now & looks like the B&N screen is coming up. I'm not sure how it happened. I'm going to leave it unrooted until I feel adventurous (or foolish) again.
P.S. Came back with version 1.0.0 SW.
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
Have checked as many threads and post as possible - And I think I have royally screwed up. Problem is My HTC Google Nexus One will only vibrate continuously until either the battery or power is pulled. I did root the phone, and installed Clockwork Mod recovery making a full back up of the factory image. This was as far as I got in my quest to upgrade the OS to something more modern.
The phone worked for a day and a half after rooting, and worked fine after installing ROM Manager. But i kept getting prompted to upgrade from 2.1 Eclair to 2.3.6 Gingerbread. So I tried to run that upgrade and it failed with a triangle with exclamation mark. I rebooted and thought nothing of it. Later I installed Snapchat, and an hour after that the phone wouldn't respond to accessing 'settings' or any other system folder. So I had to pull battery. Tried to reboot and it stalled at the starting animation and that was the last action I saw from both the screen or otherwise.
So although I read there is a risk to rooting your phone, I figured it went smoothly as the phone functioned well for a day and a half.
Anyone have any thoughts on this? I read if you can't get to any of the 3 boot screens then you're bricked. I just can't understand how it happened so easily?
Hello;
Sorry to bother anyone and thank you for taking the time to create this site. I have a Nook HD "Humming Bird" and recently Installed CM11 on it. The other day the Tablet's battery went completely dead and I was able to get it charging again the next day, Upon turning it on the tablet turned on and just Displayed the Nook logo on the front, I have tried recreating the Bootable SD cards and even reverting it back to stock Roms, the tablet act as tho everything is completing successfully but the I restart it, nothing happens it just stays on the nook screen.
I'm really running out of idea's it was working fine and I have flashed this as well as about 4 or 5 different phone. I have seen other forums stating that I need to revert back to stock recovery, rom and each attempt I haven't been successful phone show it installing it complete's it with no errors but then when I turn it on nothing happens.
The only thing that I have noticed during the flashes is that it says something Offset5124 (I don't know if these are correct) and I think a message pulls up
Installing Boot... Installing Boot... Installing Boot...
Any help would be awesome and thank you very much
Hi hello howdy!
I'm going to skip the foreplay cose the action here is pretty weird and you'll want to get right in, trust me.
I've a Galaxy S3 Mini GT-8190L, that reboots itself, after it has booted up, and I entered the sim pin and lock pattern I've from seconds to 5 min of grace before the phone restarts itself. I have tried two different batteries and the problem persists. I went and decided to rule out hardware problems (power bttn) and after some tinkering, ruled that out too. So now my best guess is firmware.
The phone is not rooted, does not have recovery mode installed, and is running stock 4.1.2 jelly bean with TouchWiz, no mods, no hack-y stuff, your old regular samsung s3 mini.
I tried installing CM11 with odin, and didn't work. But not because odin threw an error, no, that went on perfectly according to the program. But when the phone booted up, the rom was still stock, nothing changed, and it rebooted itself briefly. Weird. So then I thought "well, maybe at least the recovery mode is there now" since it supposedly was a package install. But no, when I tried to boot onto recovery the phone gets stucked on the boot screen with the samsung brand and model of the phone, and then restarts itself, this happens like four times and then the phone boots normally, the OS starts, everything loads and then goes on to restarting. So this was not a solution either.
Next I though, well lets just install the recovery, no, that didn't work, odin said that the install was successful but it was not. Tried with odin 3.04, .07 and .09, tried CW and TWR, neither of them load, as before, when trying to boot to recovery the phone displays the splash and the reboots itself like four times before starting up the OS.
Next I though well, lets try to root this thing, at this point I was just trying anything to see if anything sticked, but nothing, tried SuperOneClick, and no. Wanted to try TowelRoot but that uses an apk. I tried vRoot against my best judgement, but that didn't work, but not because of the reasons you might think, it did install, the phone managed to stay on for enough time for it to get running, but when it restarted, there was no app there, it was as if nothing was installed just a few second ago. I thought "huhh? That's really weird". So I went and did some testing on this matter.
It turns out that no matter what I do, I can install an app, delete 5 apps, change settings, and nothing sticks, when the phone restarts it goes back to the way it was, its like the phone lost the short memory and its like that Adam Sandler and Drew Barrymore's movie, 50 First Dates. The phone rollsback to the state it was when everything began.
I even tried to change something quick, and restart myself the phone to see if that would make the change stick, but no, that didn't work either.
So, I came up with a brilliant idea, look up a similar case on internet, 'cose you know, it has to have happened to someone else before me. But this is so weird that looking it up is a challenge by itself. I tried a few things here and there but nothing does it. So now I'm here writing my sci-fi story looking for some feedback on how can this story be ended without killing any of the characters, I want everyone to survive and work again. You know, happy endings.
Any ideas on what can be the problem? Seen anything like this before?