Related
FLASHABLE ZIP, (1)RESTORING NC TO STOCK/FACTORY OR (2)CWR REMOVAL ONLY
What you will find here: files to restore to stock (v. 1.0.0 or 1.0.1) and files to remove CWR and thus restore stock recovery (8 failed boots and factory reset [power+n]).
______________CAVEAT________________
Keep in mind that the Nook is really hard to brick. By that, I mean almost impossible. The reason is simple: it has a boot priority on uSD, which means you can always boot your NC from the uSD with, for example, Nookie Froyo (see thread in Dev section). From there you can install Clockwork recovery and other applications (ibid) and repair almost anything. So please, don't panic.
If you ask for help, explain yourself exhaustively on what you have done to require attention. Thank you.
All the usual warnings apply. I cannot guarantee that the following won't have side effects, although I'm pretty sure it won't. Please read complete thread before attempting anything.
Do not attempt flashing files unless you really need to or absolutely know what you are doing.
____________________________
______________UPDATE-01/23/2011_______________
There is another method to restore to stock. If you know your way around ADB, please read this thread: click here, as it will guarantee a clean restoring of your partition. The below files only copy files, but cannot "recreate" your partitions. Both methods can work, but the one linked above (shad0wf0x's thread) will work without exception. Only requirement is that you can use ADB. Thank you.
_______________________________________________
I know a few people out there are struggling after having messed up their Nook's partitions (boot, system, etc.). Hope this will help.
Requirements:
- Rom manager / Clockwork Recovery. This can be easily installed through Nookie Froyo booted from uSD, or through rooted NC. See Clockwork Recovery thread for more information.- A uSD with enough free space (at least 175 MB). Make sure uSD is mounted (see mounts option in Clockwork Recovery). If it doesn't read your uSD, format from an Android device (Memory settings, unmount-> format).
Files to restore NC to stock (1):
If AND ONLY if you choose to restore completely your NC, /data and /system partitions must be formatted before flashing. See mounts and storage option in CWR.
LINKS ARE DOWN: please refer to the following post: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148
BEWARE: These files will reset you Nook Color to stock and remove Clockwork Recovery, by replacing /boot, /system, and /media with stock
If you choose to flash one of the two files above, formating /data and /system is required BEFORE flashing the file (see mounts and storage in CWR) ! After flashing, resets (8 failed and power+n) shouldn't be necessary, everything should work straight "out of the box" after flashing the file.
Or,
File to remove CWR and restore stock recovery (2):
If you simply wish to remove CW Recovery, use this file, which restores /boot only:
EDIT: files are not available anymore. Sorry for the inconvenience.
Size: 6.1MB, md5sum: 6d00a461a221e69195440355f6706104
Note that this last file will affect your rooting of the NC.
If you should choose to keep your NC rooted, try this:
EDIT: files are not available anymore. Sorry for the inconvenience.
Keep in mind this last file has not been tested on my NC. It's necessarily less dangerous than the other files (which already aren't very dangerous). But still, please give me some feedback on whether it works or not. Cheers.
5. As a last attempt to fixing your NC, if your nook never gets passed the "Touch the future screen" or simply doesn't boot, try this file:
EDIT: files are not available anymore. Sorry for the inconvenience.
________________________________
Comments are welcome.
Sam
Very handy - Thanks for your effort
dude this is just what i needed after my little nook color break down. Thanks!!! a ton!!! also its 11:56 eastern and the downloads are available yet...
Jamdat33 said:
dude this is just what i needed after my little nook color break down. Thanks!!! a ton!!! also its 11:56 eastern and the downloads are available yet...
Click to expand...
Click to collapse
File is now available.
quick question, if we removed cwrecovery then will the 8 boot reset work again?
Yes, it will. That's the point.
beautiful! Thats just what i wanted, thanks alot man
Thank you. I was worried that I wouldn't be able to check out the B & N 2.2 update coming out soon. It worked great. After flashing I had to factory reset the data (three finger salute) and everything worked out great. Now I'm in the process of installing the 1.0.1 update and then will probably go back to where I was before (autonooter with clockwork recovery). I have a nandroid backup and titanium backup of everything so won't take long. Thanks again. Great job!
Tried out method 2. Looks like i have a corrupted recovery now It wont go past the "Touch the future of reading" and when i do the 2 button salute it brings me to a screen that says the install failed
EDIT: Nvm. just magically worked again.
Edit 2: I used the 2nd method and it wasn't smooth sailing. I'm gonna relate what happened and what I did so that samuelhaff can help others if they have the same problem:
I originally auto-nookered the device and then installed CWR. I foolishly tried to do the 8 hard resets and was met with the recovery screen. I also foolishly wiped the data and cache hoping that would do the trick and alas it just left me with a "touch the android" homescreen that didn't work.
At this point I used the second method after I tried froyo and when I reset the nook the nook it would get stuck at the the "Touch the future of reading." So to fix it i tried to get into recovery by holding the N button and the power button and it showed me a screen that said the install failed and then the nook started booting normally again. Not smooth sailing but it worked so thanks a lot!
you're awesome. Wish I had this last week. haha
tytdfn said:
Tried out method 2. Looks like i have a corrupted recovery now It wont go past the "Touch the future of reading" and when i do the 2 button salute it brings me to a screen that says the install failed
EDIT: Nvm. just magically worked again.
Edit 2: I used the 2nd method and it wasn't smooth sailing. I'm gonna relate what happened and what I did so that samuelhaff can help others if they have the same problem:
I originally auto-nookered the device and then installed CWR. I foolishly tried to do the 8 hard resets and was met with the recovery screen. I also foolishly wiped the data and cache hoping that would do the trick and alas it just left me with a "touch the android" homescreen that didn't work.
At this point I used the second method after I tried froyo and when I reset the nook the nook it would get stuck at the the "Touch the future of reading." So to fix it i tried to get into recovery by holding the N button and the power button and it showed me a screen that said the install failed and then the nook started booting normally again. Not smooth sailing but it worked so thanks a lot!
Click to expand...
Click to collapse
Thank you for your contribution.
I don't understand why your NC wouldn't boot pass the splash. Will have to see if that happens again.
But on the other hand, I have noticed that the first boot after restoring may show up an "install failed" notice. Which, again I don't understand just yet. But everything should work if you boot a second time.
Anyway, I'll look into it. In the mean time, both files should help quite a few hot-headed nookers, like myself.
If I new you better, I would fall in love with you. Maybe we should take this slowly.
Is it possible to make a 1.0.1 version
This is a huge step forward. Thanks for posting this. It makes experimentation much more possible.
I'm so happy. I think I'm going to be able to stop crying now.
Good job, sir...
If i can stop screwing up all of my technical endevours, i'm going to start trying to make a rom kitchen, now that there is a streamlined way back...
Nevermind, I can't seem to do anything correctly this weekend...
Sent from my LogicPD Zoom2 using XDA App
straby187 said:
Is it possible to make a 1.0.1 version
Click to expand...
Click to collapse
Most certainly.
Sent from my HTC Desire using XDA App
Ok... I have absolutely no clue what happened... All went well... Flash went through without a hickup... Booted up fine... And then... No wi-fi... I absolutely can not enable wifi now...
ourprisonplanet said:
Ok... I have absolutely no clue what happened... All went well... Flash went through without a hickup... Booted up fine... And then... No wi-fi... I absolutely can not enable wifi now...
Click to expand...
Click to collapse
Ok. Which method did you use? (1) or (2)? Before flashing, were you using v. 1.0.0 ou 1.0.1? Try updating to 1.0.1. See if Wifi is working. If not, try method (1) (again?). Do both resets (8 failed and power+n).
samuelhalff said:
Ok. Which method did you use? (1) or (2)? Before flashing, were you using v. 1.0.0 ou 1.0.1? Try updating to 1.0.1.
Try method (1) (again?). Do both resets (8 failed and power+n).
Click to expand...
Click to collapse
OH THANK GOD :-D I did the power+n and it brought it back... Thank you SOOOO much for such a quick response... I have no clue what the heck caused that... that was weird...
Hi everyone.
I've tried to read as much as I can here, but I haven't been able to make any solutions work.
I have the gtablet. It had the latest OTA update (Apr 15). I tried to install the clockwork mod.
When I first did the Volume+Power boot, it brought up the menu as expected.
I then tried to apply the update. It rebooted.
But since then, when I Volume+Power boot, it says the following:
"Recovery key detected"
"Booting Recovery Kernel Image"
BUT then it just sits there forever. I let it sit for over 30 minutes ... no change.
If I boot normal (just hit power) everything works fine as before. No data loss, etc.
But I wanted to get root access so I could use Titanium Backup (that's what started all this).
If anyone can give me some advice/help on this, I'd appreciate it very much.
Thanks in advance!
The standard ClockworkMod is not compatible with the latest update (1.2-4349). If you're familiar with nvflash you can probably pull the recovery image out of the 4349 update.zip and reflash it back onto your tablet. If you're not familiar with it then you'll need to start reading up on it...
http://forum.xda-developers.com/showthread.php?t=861950
K J Rad said:
The standard ClockworkMod is not compatible with the latest update (1.2-4349). If you're familiar with nvflash you can probably pull the recovery image out of the 4349 update.zip and reflash it back onto your tablet. If you're not familiar with it then you'll need to start reading up on it...
http://forum.xda-developers.com/showthread.php?t=861950
Click to expand...
Click to collapse
Thanks for your reply. I appreciate it.
What I don't understand is -- I've tried doing the "downgrading" and other approaches that use the "update.zip" and "command" files, but it's as if my gtablet doesn't read those now. Yet - as I said - if I boot normally it loads/runs everything fine.
Well, I guess I'll try the NVFlash. It's still a new tablet so even if everything gets wiped out, I haven't really lost much.
Thanks again for your reply.
barnell,
Your G-Tablet uses the "Recovery" function and software to load software, updates, etc.
When you tried to load CWM, it messed up the recovery software (or didn't re-load it, I
think) and so while the rest of your tablet works fine -- any call for recovery functions
go unanwered.
When you NVFlash as KJR said, it will restore the "Recovery" software along with the
rest.
Rev
butchconner said:
barnell,
Your G-Tablet uses the "Recovery" function and software to load software, updates, etc.
When you tried to load CWM, it messed up the recovery software (or didn't re-load it, I
think) and so while the rest of your tablet works fine -- any call for recovery functions
go unanwered.
When you NVFlash as KJR said, it will restore the "Recovery" software along with the
rest.
Rev
Click to expand...
Click to collapse
Rev,
Thanks very much for your reply.
I suspected it may be as you said, but being new to the gtablet and its architecture, I couldn't be sure.
I guess NVFlash is the way to go. I'll keep you all posted.
Thanks again.
barnell said:
Rev,
Thanks very much for your reply.
I suspected it may be as you said, but being new to the gtablet and its architecture, I couldn't be sure.
I guess NVFlash is the way to go. I'll keep you all posted.
Thanks again.
Click to expand...
Click to collapse
After totally trashing my g-tab yesterday with the new update and spending about 8 hours trying to get things back to where they were, I can say with all honesty.... NVFLASH IS YOUR FRIEND!!! Learn to use it.
Hi everyone, I'm new here, and I'm experiencing the same issue. The only difference is that I don't even see "Booting Recovery Kernel Image"
When I tried to use the nvflash method, my computer (Acer Aspire Revo) doesn't even detect my Gtab when I connect it to my tab. So, I'm at a loss, seeing as how both using an SD card and the nvflash method hasn't worked. Any help would be greatly appreciated, as I'm certain I may have completely bricked my device.
If you're using windows you'll need the appropriate driver for your tablet to be seen in APX mode. I don't use windows myself and the driver is version dependent so I can't really point you in the right direction on that without more information.
Actually, with a reboot of my coputer, it could detect my tab in APX mode, so I was able to run through nvflash. Phew, though now it can't load the update, so I'm stuck with the stock for now. Thanks for the reply!
IndyLateNite said:
After totally trashing my g-tab yesterday with the new update and spending about 8 hours trying to get things back to where they were, I can say with all honesty.... NVFLASH IS YOUR FRIEND!!! Learn to use it.
Click to expand...
Click to collapse
Indy (or anyone who cares to respond),
I wonder what you think of this ...
If I do nothing (ie, I don't nvflash back) and wait for another gtablet update, maybe the next update will 'fix' the problem of not working with the CWM?
I have no real pressing need to change anything at the moment - though I would like to get rooted (so I could use Titanium Backup) -- but I'm not keeping anything that critical on the tablet (yet). So I'm just thinking I might wait it out and see what the next update does (assuming there'll be one).
I'd appreciate your thoughts, as you seem pretty knowledgeable about all this.\
And, again, I appreciate your responses, so thanks in advance.
Hey, fellas. As you may or may not be aware, I am in dire straits. Recently I had been browsing the XDA forums for the first time in a long time, and lo and behold there was a magnificence I had thought to never see in our own development forum... a Honeycomb alpha! In my haste I tried to follow every instruction to the tee and discovered that I need the stock bootloader/ROM to do this.
Well, coming from cyanogenmod7 and a first time nvFlasher, I followed the instructions from one thread to flash back to stock 3588(I think it was)? So after fiddling with the drivers for about 5-10 minutes, I start flashing and everything is going great, no errors whatsoever. Then the tablet starts to boot up and what happens? A bootloop at the TapNTap screen. So, I tried to boot into recovery thinking it might be fixable with a factory/data reset...and recovery no longer works, it just reboots back int pthe TnT bootloop. And then I came to the this forum, particularly the Q&A, to ask one question...
Is my G-Tablet well and truly forked?
Sincerely, this guy.
[edit]P.S I am also currently trying a bunch of stuff atm to see if I can fix it myself, but just reply if anything I do is futile and I should consider recycling my new hunk of silicone and plastic.
Load cwm .8 via update.zip and repartition your tab. Then try nvflash again.
"Select the advanced option at the bottom of the ClockworkMod menu, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. This erases data on your tablet. Be prepared. "
Or try loading it by nvflash with instructions from this thread
http://forum.xda-developers.com/showthread.php?t=1058649
Here is a thread on how to easily flash to the 1.2 bootloader.
http://forum.xda-developers.com/showthread.php?t=1039000&highlight=guide
Holy heck, thanks man. Do you have a paypal or something so I can send you like 5 dollars?
Nope, just mash the thanks button ;-)
Good luck!
No offense to the OP, but from my observations it seems that NVFlash is more of a breaker than anything. Everybody says to know NVFlash in case you end up with problems...that's fine, people can apparantley use ot to help fix errors that may have happened...
The fact is, most of the "I've bricked my G-Tablet" posts usually contain the line "So I NVflashed..."
I know that the developers use NVFlash for it's ease of use to go between roms, and see what it is that they need to see (I've never used it, so I don't know)
The fact is, the instructions that Mantara posted do not require NVFlash at all. In fact, after flashing 3588, they don't even require CWM.
If I ever softbrick, THEN I'll mess with NVFlash...but until then, it seems that NVFlash might actually cause me to have my first softbrick.
Nvflash is a handy tool to have and yes it can cause errors. Most of the time those errors occur because the partition table on the tablet don't match the partition table for the Rom being flashed. About half the gtabs have different partition tables from what is considered standard. That's why I have been pressing the issue of repartitioning when you first get your gtab and also when you move from 1.1 to 1.2. It helps make sure your tab and the software are on the same page.
Hello everyone,
i just recently purchased a gtab and tried to install clockwork recovery on it. that didnt seem to work so i tried to do a factory reset. my guess is it tried to boot to CWM but the files were messed so now its stuck at "booting recovery kernel image". can someone assist me? my plan was to put cwm on it, and then put Vegan on it, but that foiled.
Thanks!
Hubblemuffin said:
Hello everyone,
i just recently purchased a gtab and tried to install clockwork recovery on it. that didnt seem to work so i tried to do a factory reset. my guess is it tried to boot to CWM but the files were messed so now its stuck at "booting recovery kernel image". can someone assist me? my plan was to put cwm on it, and then put Vegan on it, but that foiled.
Thanks!
Click to expand...
Click to collapse
What version of CWM did you try to install? Do you know what bootloader you're on? I'd imagine that you tried flashing the 1.1 BL CWM and ended up in a softbrick because you have a 1.2 BL G-Tablet...
G-Tablet for Dummies is your friend...google it, read every page, then decide what you want to do. At the start here page, you're on a code red, I believe.
If you happened to install a wrong CWM bootloader version, you are in BIG trouble. The "stuck bird sign" is not a good sign
Last time it happened, I used code DETOX to set it straight in viewsonic gtablet for dummies.
THis thing is unbrickable (virtually unbrickable), so no worries~
I have to agree. I got my gtablet about a month ago. Nothing I did seemed to work, until I found the gtablet for dummies site. Within about two hours, I was up and running with a real android operating system with full market.
That site ROCKS!
Thank you all so much for the reply. I just got it today and knew I didnt want TnT but i guess i rushed with the process and did the wrong bootloader. Im gonna look in to that when i get home to my own PC and see what happens. Thank you!
ok. i read over the Gtablet for dummies website, and that reminded me that there must be something wrong with the install of CWM. all it does is say ANDROID in orange on the left of the screen and then a grey triangle shows up. im going to attempt to be the Triple Code Red tonight and hope that works.
Humblemuffin,
Don't give up! I totally messed up the g tablet shortly after taking it out of the box. After much research and trying various steps/techniques, I eventually was able to bring it back.
I posted the exact steps I used here on xda and on slatedroid.
They can also be found on the Viewsonic Gtablet For Dummies site under "How-To". Follow the steps exactly and I am confident you will get your g tab restored.
http://viewsonic-gtablet-for-dummies.webs.com/
Same steps, but recently added some content about APX and NVFLASH
http://forum.xda-developers.com/showthread.php?t=1167944
djab67
Sent from my ADR6400L using XDA Premium App
thaks for the advice. im quite grateful that theres people able to help me here. ive been reading gtablet for dummies, but i seem to be at even more of a standstill. i think my CWM is corrupt or something. after it says "Recovery Key Press Detected", it shows ANDROID in yellow/orange letters on the left of the screen for about a second, then a grey triangle with an exclamation mark pops up. i think using the wrong bootloader kind of screwd me over. i always try and rush with my technology like this. thank you!
Here is another potential solution for you to consider. It does not require the use of ADB which makes it a little easier than my steps. If it you think this one will work for you, then I would recommend doing it before mine.
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Thanks for the reccomendation! I sent you a message about it and maybe we could get it up and running. My main concern now is that my CWM still doesn't work. That's kind of worrysome to me because all the potential fixes I see envolve using it at one point or another.
Blank Screen, background light
I went to GTablet for Dummies as well, to install CWM and then a new OS. Unfortunately, my GTab would not accept the installation of CWM. I have a 1.1, and tried installing the version 1.1....following the directions exactly They then suggested I install nvflash, which I tried with no success. Now, my GTab just shut down...blank screen with background light. Prior to the shut down, it had over 40% battery life left. Any help would be greatly appreciated.
Well, when I first got a gtab, i messed up the bootloader (installing the wrong version of bootloader), CWM doesn't work. Etc...etc...luckily apx mode still work. This is what I do. I think it is sorta the ultimate wipe.
Edit: I wasn't allowed to put link outside since I was a new user. But you can just go to viewsonic gtablet for dummies website
USE THE CODE DETOX. The code detox invovles you nvflashing your rom with this format.zip file. It might look similar to other nvflash at first glance except when you use the format zip nvflash, you will see "magic-value -mismatch" in red color.
After you nvflashed your tab with format.zip. Do another Nvflash, but this time, Nvflash your tab with "NVFlash to Stock with CWM pre-installed" . Get the right bootloader, and follow the steps described later in viewsonic gtab for dummies, and you have a smoking gtab soon enough
Um... guys, just download my nvflash with cwm pre-installed and use that. No need to put cwm on separately.
To goodintentions, TJEvans, fury7, tidbit, djab76, SM Daly, ahandlen003, and goodintentions again.
Thank you so much. i know the task is yet to be complete, but i finally was able to get past the bootloop and in to TnT to do the OTA update. im going to be much more careful with any more modding. for the record, the NVflash with CWM pre installed for BL 1.2 was the ticket. CWM looks so beautiful after being in the pits for a few days.
if all goes to hell again, ill let you all know.
Thanks again!
Hubblemuffin.
Hubblemuffin said:
To goodintentions, TJEvans, fury7, tidbit, djab76, SM Daly, ahandlen003, and goodintentions again.
Thank you so much. i know the task is yet to be complete, but i finally was able to get past the bootloop and in to TnT to do the OTA update. im going to be much more careful with any more modding. for the record, the NVflash with CWM pre installed for BL 1.2 was the ticket. CWM looks so beautiful after being in the pits for a few days.
if all goes to hell again, ill let you all know.
Thanks again!
Hubblemuffin.
Click to expand...
Click to collapse
Before I bought my gtab, i spents hours reading up on roebeets and others @ xda, blogspot and slate. took tons of notes. had everything laid out step by step. even had nvflash files set up. Had minimal prblems.
In the last month or two, found out about goodintentions website. he pretty much compiled everything you would need to know.
spend some time there reading up and you'll be on your way.
Probably should send him a donation also...he deserve it
I have a question I think I jump the gun on this one. I tried to install ClockWorkMod for my G tab 1.2 I got the file from GTablet for dummies but everytime I tried to install it it will just sit on the "Recovery key detected" and then it says "Booting recovery kernel image" and with the 3 birds and it just sits there! I can't get into recovery mod. either but I can turn it off and it boots fine to the homepage. What can i do? The person I bought it from had it rooted but he said he returned it back to stock rom. Thanks for the help.
Can someone help me, please.
Big Thumbs Up to Goodintentions...
qkster said:
Before I bought my gtab, i spents hours reading up on roebeets and others @ xda, blogspot and slate. took tons of notes. had everything laid out step by step. even had nvflash files set up. Had minimal prblems.
In the last month or two, found out about goodintentions website. he pretty much compiled everything you would need to know.
spend some time there reading up and you'll be on your way.
Probably should send him a donation also...he deserve it
Click to expand...
Click to collapse
I donated to goodintentions...
you should too.
jjq13 said:
I have a question I think I jump the gun on this one. I tried to install ClockWorkMod for my G tab 1.2 I got the file from GTablet for dummies but everytime I tried to install it it will just sit on the "Recovery key detected" and then it says "Booting recovery kernel image" and with the 3 birds and it just sits there! I can't get into recovery mod. either but I can turn it off and it boots fine to the homepage. What can i do? The person I bought it from had it rooted but he said he returned it back to stock rom. Thanks for the help.
Click to expand...
Click to collapse
If it were my Gtab, I would nvflash it back to stock myself just in case. Just pay attention to the requirements of the custom ROM you want to flash: some are for 1.1 and some for 1.2 -- nvflash accordingly. Anyway, learning and setting up nvflash is a good thing if you plan to flash custom ROMS with any regularity.
Brian
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.