Related
Yes, I searched, but nothing I found seemed similar to my situation.
Here is the timeline of events:
Rooted my nook with autonooter a long time ago.
Decided last weekend that I wanted to install CM7.
Installed Rom Manager, CWM, etc. Then installed CM7.
Decided that I wanted to bring my nook back to stock so I could check out the 1.2 update.
Restored it back to stock using Option #1 in this thread: http://forum.xda-developers.com/showthread.php?t=914690&highlight=reset+stock
It worked fine the past few days.
Then last night I decided I would try this: http://forum.xda-developers.com/showthread.php?t=1045018
I burned the image to the SDcard, expanded the partition in order to be able to use the SDcard for storage. Placed the sdcard in my nook.
It wouldnt boot at all. The screen refused to turn on.
I tried it many different ways, holding the 'n' button while turning it on, holding the volume buttons, etc.
Then i took the sdcard out of the nook and tried booting it.
It still wouldnt turn on. The screen simply would not turn on. Finally after a few tries, it did turn on. So I shut it off for the night and thought I'd try again today.
I tried to turn it on again today (without the sdcard in the nook) and it will not turn on. I've tried it about 25 times. Holding the power button for many different time intervals.
And yes, its charged. It was fully charged last night.
Any idea what I can do here??
Connect it with power cable (no matter if its charged) and try to turn it on by Power button.
Then restore it to original rom.
RASTAVIPER said:
Connect it with power cable (no matter if its charged) and try to turn it on by Power button.
Then restore it to original rom.
Click to expand...
Click to collapse
Unfortunately, I'm at work and dont have my power cable with me.
I have a compatible USB cable that I can plug into the computer, but I already tried that and it didnt work.
Also, the nook should be on the stock rom already. It was on stock 1.2 before I tried the dualboot sd card last night.
OK, so I just tried turning it on for the 50th time today, and for some reason it worked.
It was not plugged into anything, I didnt do anything differently.
Just held the power button.
Anyone have any idea what could be causing this?
My nook is stock 1.2.
I had a similar problem, and I thought mine was bricked. I used WinImage to create a ClockworkMod boot microSD card. Holding the power button for ten seconds performs a manual power down, release, then hold it for another three to five seconds. It will boot to ClockworkMod Recovery.
Now, I had installed HC update RC3 from a week ago, and it worked just fine. The dev releases a hybrid with the Asus Eee Pad Transformer this week, and I tried updating to it. It caused my Nook screen to not turn on just like yours.
Once in ClockworkMod, I can reinstall the zip files, but it still won't turn the screen on unless in Recovery. When I try to restore my backup of CM7, it says there is an "MD5 error." Not sure what that is or how to fix. Maybe you can help me?
jlscarpa said:
I had a similar problem, and I thought mine was bricked. I used WinImage to create a ClockworkMod boot microSD card. Holding the power button for ten seconds performs a manual power down, release, then hold it for another three to five seconds. It will boot to ClockworkMod Recovery.
Now, I had installed HC update RC3 from a week ago, and it worked just fine. The dev releases a hybrid with the Asus Eee Pad Transformer this week, and I tried updating to it. It caused my Nook screen to not turn on just like yours.
Once in ClockworkMod, I can reinstall the zip files, but it still won't turn the screen on unless in Recovery. When I try to restore my backup of CM7, it says there is an "MD5 error." Not sure what that is or how to fix. Maybe you can help me?
Click to expand...
Click to collapse
Well it sounds like our problems are very different. However, I have some experience with your problem with my thunderbolt.
When I got an MD5 error, it meant that there was something wrong with the name of my backup. Does your backup have spaces in the name? Or did you change the name of it after creating it?
Unfortunately, I was never able to recover the backup with the MD5 error.
If you can get into recovery, it sounds like you should be able to restore your nook to stock via this thread: http://forum.xda-developers.com/showthread.php?t=914690&highlight=reset+stock
If I were you, I would return my nook to stock and start over.
A couple weeks ago I bought a Nook Color on ebay. The first thing I did was turn it on and let it fully charge overnight. I noticed that it was in normal condition, but didn't bother going past the intro screen since an off the shelf Nook Color was not what I was interested in anyway.
The next day I flashed phiremod 6.2 on it with no problems (I have done this process successfully to two other Nook Color's by the way). I am able to connect to my wifi, setup my google account, and open the market. Life is good so far. Then I notice in ROM Manager that there is a phiremod 6.3 version out. I try to download phiremod 6.3 from ROM Manager for an entire day with no luck. The download just kept stalling on me. No problem I'll just download phiremod 6.3 onto my sdcard and flash it through clockwork recovery as normal (performing a full wipe first of course).
Then boot loop for no reason I can tell. Just a boot loop at "Touch the future of reading" with no way to get into recovery without restarting it with the sdcard.
So I put the sdcard back in and wipe and reflash phiremod 6.3 with the same results. Then I wipe and reflash phiremod 6.2...boot loop again. I repeat this process until my eyes start to bleed.
At this point I'm thinking, "There's no reason this should be happening. I wish I could just go back in time and start over." That's when I find this link: http://forum.xda-developers.com/showthread.php?t=914690
Ok, I'll just restore everything back to stock. No clockwork, no phiremod, just Barnes and Noble software just like the day it was born. So I go down the road of restoring the device to stock and instead of bootlooping at "Touch the future of Reading" it bootloops at the "N" screen. I'm running out of ideas so I perform the 8x method, get the OTA install, and still bootlooping at the "N" screen. Oh yeah, and "power + n" wont take it into recovery of any kind.
Now that it seems that I've failed to restore the device to stock, I try to flash phiremod 6.3 again because this is really my end goal anyway. This time it is a success. I connect to my wifi. The device says I am connected and the wifi signal is strong, but I can't establish a reliable data connection with google, or open the market, or browse the web. I turn the wifi off and on, I tell it to forget my connection and add it again, but nothing seems to work until a day later when it suddenly establishes a connection.
So everything seemed like it might be ok at this point except strange things started happening with the device. Power + n doesn't take it into recovery, and never did at any time it has been in my possession. When I try to go into recovery from ROM Manager after flashing CWR I go into a bootloop. This is even after updating Rom Manager and doing things like rebooting after flashing CWR. Wifi always says it's strong and connected but any app with internet access is often times painfully slow to the point of being unusable or at least impractical. Downloading a single app from the market is like pulling teeth, and I regularly get the "retry or cancel" popup over and over again. Sometimes when I tell it to reboot or shut off, I get the "rebooting" or "shutting off" message and it just grinds away endlessly.
The device is currently in a bootloop after just telling it to reboot (normal reboot not reboot into recovery), and I know how to pop in my sdcard with CWR and get out of it. However, my problem is that this is a gift for my sister, and I just cant seem to get this device into a normal working state that I can give to her.
I know that there are plenty of threads answering all of the little problems I have outlined here, but none have resolved them for me nor have I found a single thread that deals with a whole host of problems like this device seems to have.
Thank you for your patience in reading this.
Try restoring to stock 1.2:
http://forum.xda-developers.com/showthread.php?t=1050520
It can't hurt at this point, and it may get you fixed.
Thanks for the reply.
No dice. I tried both of those files. I made sure to format the system and data before flashing each time, and I'm still stuck at the "n" screen.
Alright so here's what I just did:
1) Format system
2) Format data
3) Flash B&N v1.1 "old" 1GB "/data", 5+GB "/media" partitioning zip from:
http://forum.xda-developers.com/showthread.php?t=1094371
4) Reboot
5) Flash Stock 1.2 update.zip from:
http://forum.xda-developers.com/showthread.php?t=1050520
6) Unmount sdcard
7) Reboot
8)Still stuck at the "n" screen.
The story so far:
I was forgetting to do the 8 reboots after repartitioning and flashing stock apparently.
I performed the 8 reboots, and my Nook did a factory reset and OTA update. Now it boots into stock v1.1.0. I see the pretty lady, there's a video, I get to accept a B&N agreement, I connect to either of my wireless connections, but after I enter my account name and password it always says "Error sorry we're having trouble setting up your Nookcolor. Please shutdown the device and try again...." It gives me a number to call so I do. After a long bewildering conversation with tech support, I'm told that my device was once registered to someone else (which I already suspected having purchased it on ebay). I'm told that in order to fix the problem they are going remove the old account from the device, and that when I restart it in an hour I will be one with the Nookcolor universe. It has been many hours, and I am still getting same error message.
Should I continue down this path with customer service (who are failing to inspire me), take it into the Barnes and Noble store this weekend (I don't have a receipt but it at least it boots into stock now), or just go ahead and load phiremod 6.3 (which is my end goal, but I want to make sure I don't take one step forward and then two steps back now that I've gotten this far)?
"Device Info" only has "back," "power off," and "reset."
I just tried holding the "power + n" for 10 seconds as demonstrated here Nook blocked after downloading latest software - Barnes & Noble Book Clubs. This guys seems very happy that this solution worked for him. I don't know why it wont work for me seeing as I have the exact same problem.
Barnes and Noble tech support came through and reset my device. It appears that I have a stock 1.1 Nook Color and all is well. I am even connected and able to browse the internet. Does this mean I am ready to start flashing new ROMs onto it, or should I do more testing while it is still stock?
So I made a nandroid backup of the stock system with no problem. Then I flashed phiremod v7 test. Everything was going well until I went to ROM manager, flashed CWR, and tried to make a backup. It went into a bootloop so I put in my sdcard with CWR. Immediately it started putting my backup on that card. I rebooted it through CWR, but it still went into a bootloop. I then did a factory reset, full wipe, and flashed phiremod 6.3... still bootlooping away. This is one of the problems I was having before I started this thread. The CWR on my sdcard is ClockworkMod Recovery v3.0.0.6.
Sorry to read that you're having so much trouble. FWIW I'm having one hell of a time using Phiremod on my NC, too. I've found solace with CM7 nightlies and the latest Dalingrin kernel.
CWR 3.0.0.6 is very outdated at this point. I use CWR 3.2.0.8 on my recovery SD. I think it was V3.0.0.6 that had problems formatting the data partition, but I could be wrong.
Hope you get it sorted out.
Thanks for the support. Do you know where I could find the latest versions of Clockwork?
There's a typo in my post above. The current version is 3.2.0.1
I read about it and got the files from androidforums.com, although I'd be surprised if they weren't on this forum, too.
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR, and now it is endlessly scrolling through the CWR menu on its own. The log at the bottom says "ClockworkMod Recovery v3.2.0.0," then "Back menu button enabled," then "Back menu button disabled," then "Back menu button enabled," and seems to be continuing like that without end. After powering off, removing the sdcard, and holding the power + n buttons for about 8 seconds, the screen shows the cyanogenmod logo and says "booting into recovery" but does nothing. I've repeated this entire process several times while holding the power + n buttons for varying times and it still doesn't actually boot into recovery.
Wulfie6 said:
I downloaded recovery-clockwork-3.2.0.1-bravo.zip, put in my sdcard, flashed the new version of CWR
Click to expand...
Click to collapse
This is the problem. The nook color is the encore not the bravo. You have the wrong recovery image. Its a good thing its unusable...you might fubar your device if you were actually able to use that recovery.
Sent from my Phiremod Nook Color using XDA Premium App
I created a new boot disk with CWR 3.02.8 and successfully flashed Phiremod 6.3 and CM7 nightly 107. I was still essentially unable to use the internet on both of these ROMs even though my wifi connection said it was good. I did not try using my phone as a hotspot with these versions.
I'm on CM7 108 at the moment. I'm still getting sporadic internet access even though my wi-fi is pretty good (usually just shy of full bars). I connected to my phones wi-fi hotspot which produces full bars on the Nook with good internet results. This isn't practical though because I can't always have my phone creating a wi-fi hotspot. Doesn't this seem odd that my Nook is only internet reliable when it's connected to an excellent wifi connection, but functionally wont work when it's on a good wifi connection?
Also when I go into ROM Manager and try to flash the current version of CWR, it pulls up the "confirm phone model" (when it is actually connecting to the internet) but as soon I put my finger on the menu to scroll through, it selects the first one I touch. This is one of the problems I was having before on all ROMs.
So I just went into ROM Manager, flashed the latest version, then tried to make a backup through ROM Manager, and now I'm in a boot loop again except this is the kind of bootloop where I can't get it to turn off. It just sits there with the cyanogenmod logo saying "Loading..." When I hold the power down, it turns off and then comes right back on. When I hold power + n, it does the same thing but instead of saying "Loading..." it says "Booting into recovery..." I don't understand why this time it's different. If I take out the card that's in there now and put in my bootable SD card while it's in the boot loop, will it fry my cards?
Wulfie6 said:
S When I hold the power down, it turns off and then comes right back on.
Click to expand...
Click to collapse
sounds like it's plugged in
TheAmazingDave said:
sounds like it's plugged in
Click to expand...
Click to collapse
It's not plugged in.
Return to stock 1.2 - Stuck at n screen fix.
After you flash the 1.2 image with a clockwork recovery sd boot card, and are stuck at the n screen, you will need to restart and have the Nook software reset to default.
1. Hold Power+n for 8 seconds, release n, then power (it may take a couple of tries to get it right).
2. At the "Factory Reset" screen, confirm your intention to reset to defaults (press "home" n).
3. At the "Are you sure?" screen, confirm again (press "home" n).
It will then go to a "Clearing data..." screen and reboot to the stock nook software.
This procedure will reset your device to stock 1.2, just as it was when it shipped.
I second what JoeInternet says. You NEED to be on stock B&N 1.2 to be able to run the latest CM7 builds and ANY .32 Dalingrin kernels or it will not work.
Quick thought... The first thing that should have been done is an ATO 'deregister' to get that nook's ID dis-associated with the original BN account.
Hello,
So i've tried to root the nook. Copied the touchnooter on my card, booted the nook. And then : forever stuck on the "root forever" or the "read forever" (when i get the card off)..
The hard reboot (20 sec on power off) doesn't work and i'm stuck at this "read forever" screen.
Is there a way to recover the nook ?
Thanks.. !
When doing the hard power off (long press) the screen doesn't usually change and you might be fooled into believing nothing happened.
Have you tried to let the unit settle for 10 seconds and then press power for a few seconds to see if it tries to boot?
Hey,
thanks for replying. I have tried a 30 sec hard boot + a reboot try but nothing happened. It freezes on the "nook is starting screen".
I afraid i have broke my device... But strangely i followed the rooting steps and nothing seemed to do wrong.. I guess.
Bye
If you can in fact get the unit to start booting, just long press power (10s +) as soon as you see the unit try to boot to interrupt the boot, then power it on again and repeat this procedure for 8 times (sucks, yes I know) and you should drop into factory reset.
Ok so i have to say : WTF !
So this morning i looked at my nook and saw that it still was on the "reading forever"/"starting" thing. As i saw your advice i tried to boot 8 time..
On the first boot attempt : it worked ! So maybe is was the eighth..
The nook started and asked me if i wanted to continue with android guy or "es something"... so i pressed android guy..
SO now i don't really know if the procedure went well ? Is it supposed to be rooted now ?
Thanks anyway for the time you took replying !
I hope my english is not too hard to read.
Bye,
By "android guy" I guess you're referring to the Android Welcome screen?
That would suggest that the Touchnooter went trough successfully.
Did you get Go Launcher and ButtonSavior up and running?
IIRC, whenever you do a fresh boot and try to use ButtonSavior you'll get a notice saying ButtonSavior has been granted superuser access, which would indicate that you're successfully rooted.
I had a similar problem, using touchnooter 1.11.20 and it was too quick. Maybe 45 seconds, removed card and restarted. Stuck in a boot loop, on tne "Nook" screen with the little blocks move across the screen and just keeps restarting. Fortunately I made a backup and was able to restore. Not sure what the problem is but I tried TouchNooter 5 times, downloaded it twice, wrote it to the SD cars 3 times and same result, Stuck on the nook screen, animation gets to the 4th dot and restarts. Tried salsichaNooter .4 with the same result. Any ideas on what the problem could be? It would be really nice if I could get a decent reader on this thing.
I made my life a little easier by having 2 micro SD cards to use, nookie on one and touchnooter on the other. I also made sure I had a good backup of my original ROM by opening the image with 7zip and the nook with partition wizard and verifying they were the same. At least I can gat it back to a working stock rom.
Why dont you try my new method?
http://forum.xda-developers.com/showthread.php?t=1346748
PS:
..... insomnia Sucks......
Thanks, I'll see if this works.
Not really insomnia, trying to get this fixed before I have to put my wife on a plane. It's her nook touch, I have a color, it was so much easier.
I'm having a similar problem: I used SalsichaNooter, I let Rooted Forever to be on the nook screen for an hour, there were no messages on the screen no progress indication of any sort. I did a hard reboot after an hour and it seems at least some part of the rooting script worked - but how do i know the nook was rooted all the way through since it didnt reaboot during the rooting process as it should?
I have a rooted, but otherwise stock nook that I was having trouble installing apps from the amazon appstore on. I was trying to find some settings to fix this when all of a sudden it said something about an "authorization error" and reset. When it came back up, it was resetting data and I had to go through all the setup again. When I get to the point where I set up my account, I get the message "Sorry, we're having touble setting up your NOOK. Please shutdown sthe device and try again". Every time I reset it goes back to the same thing. Can I do something to fix this, or do I need to go throught the "restore to stock" and start over?
This happened to me and is the reason that i was driven to install CM7 to emmc.
It was a while ago, but i think i was able to fix this using the debug bridge. I would have to say that restoring to stock is probably your best option, especially if you don't have a recovery rom.
Ok, it's been a while since I've had a chance to look at this (and since the pad works with my CM7 boot card it's not been a priority). I have this to restore to stock: http://nookcolorrooting.com/RestoretoStock.aspx, but when I get to the 2nd step booting with the n key held in doesn't seem to do anything....it just boots up as normal. Is there some trick in how long to hold the button down?
Are you continuing to hold power + n while it's booting?
I've tried it several different ways, including holding the n button down until it has completely booted up.
I did find some instructions for using the clockwork mod recovery to flash the original files and am in the process of working through that.
ThinkPad Tablet A400
Android v. 4.0.3
Have an app that needs to run on Android 4.1 and quickly found out this 2 year old device was pretty much left unsupported since about 3 months after I bought it in May of 2012. So, I located the links to xda-developers and dove into the install process.
Got the device to Root following install directions etc.
Cannot get the device to reboot into recovery mode from ROM Manager nor via ROM Installer.
Tried installing the CyanogenMod v0.9 anyway from inside either aforementioned utility (from the .zip file), just reboots back to the normal state.
I'd pay to download & install Android 4.1 on this device, seriously...just lost 6 hours of time attempting to do this ROM upgrade.
any suggestions?
First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.
pwstein said:
First thing that comes to mind is that you should use the volume up button multi-press on device power-up to get to Recovery Mode.
Click to expand...
Click to collapse
I've tried various combinations of that Vol button....still stubbornly refuses to go to CWM.
Now, I am running Android 4.0.3..perhaps that is the issue, ie. perhaps the CWM image file was intended to be used on TPTs running Android 3.x.
It'd be nice to go to a site and buy a $50 OS load....
Well....wonders never cease. I happened across a post talking about the TECHNIQUE to reboot the TPT into CWM...so, sure enough...I got the puppy into CWM.
HERE 'tis for the rest of us nuves out there:
Entering/Booting CWM Recovery on the Thinkpad Tablet
Shut down your Thinkpad Tablet
Press the power button until the Tablet vibrates
Keep pressing and releasing the volume up button until you see Booting Recovery Kernel Image in the upper left corner. It's all about timing of when the volume up button is pressed. That's why it's a good idea to just keep on pressing and releasing the button until the message appears.
Well i continued on with the Jelly Bean load from the xda-developers...and after reboot to ver 0.92 the tpt seemed to freeze on the os boot screen.
So, i fell back to the 4.0.3 os and will read-up on what can freeze the reboot into 4.1 android.
CWM is a cool program..gotta say it.
Can't get it to install CWM
Tried numerous times but now I have lost my original recovery and it just loops,
Changed permissions but won't go and when I am in the recovery boot after pushing the volume button it just reboots as there is nothing there suggestions?
Honestly, the best thing you could do is get something newer/better supported. I hate saying that, because I bought the 64gb version right around the same time you did. The tablet had so much potential with the pen, USB, sd slot, and even pci-e, but it suffered from non-existant Lenovo support, and very little dev support. Koshu's work on it was amazing, but without trim I feel like I have to constantly wipe and start fresh to do anything with it. Clearing dalvik from time to time helps, but not as much.