I can confirm that this does work and I have tested it several times to verify that it would work every time. I take no credit for figuring out this factory reset method as it was dcnarad that seems to have stumbled upon it. I do take credit for figuring out exactly how it is to be performed and have reposted it below correctly. dcnarad's post here is a bit haphazard and it slightly missed the mark as to how this actually needs to be performed so as to get to the factory reset screen properly.
Perform Factory Reset of the Nook Tablet:
PWR off the Nook Tablet.
Hold "PWR" & "∩" & "VOL+" & "VOL-" buttons simultaneously to reboot.
Wait 2-3 seconds after reboot, release only the "PWR" & "∩" buttons upon receiving the "∩ - Contains Reader® Mobile technology by Adobe Systems Incorporated." screen while still maintaining to hold the "VOL+" & "VOL-" buttons.
The screen will blink a couple seconds later and then you will be presented with the Factory Reset screen with the following options:
Do you want to reset your device to the factory default?
Press POWER key to exit
Press HOME key to continue
Are you sure?
This will delete all your content and restore the device to the factory default settings.
Press POWER key to exit
Press HOME key to continue
I even accidentally let go of the "VOL+" & "VOL-" buttons once while testing this a few times but quickly pushed them back down again and was still given the factory reset screen so this method works even with a little goof like that. This worked since holding down "VOL+" & "VOL-" the buttons was found to actually be unnecessary.
ENJOY!
NOTE: "HOME key" = "∩" button
NOTE 2: After some discussion with others, I decided to "take one for the team" and experiment with software version 1.4.1 update. I manually updated my Nook Tablet to software version 1.4.1 via the software download from bn.com. I applied to update and then did a factory reset of the device after booting into v1.4.1. I can confirm that if your NT has been updated to v1.4.1 then a FACTORY RESET will reset your NT to factory default settings of software version 1.4.1 and your NT will not revert to v1.4.0. It seems that B&N has pulled another fast one by over-writing the device's original factory software as well with this update. I was able to revert my NT to v1.4.0 via AdamOutler's Restore Barnes & Noble Nook 1.4.0 from SDCard afterwards with only the one issue. The "∩" button was not working after the device initially booted up into v1.4.0 but applying a second factory reset to the device solved this issue.
Finally someone else try it I have posted this in my tips and trick thread. Thanks ill update later the link to this post as its more detailed
Sent from my LG GT540 Swift using XDA App
Cannot reset to 1.4.0
Getting panicky. I had root previously then got "upgraded" to 1.4.1. Have tried multiple ways of getting back to 1.4.0, all have which have left me with an unrooted Nook with 1.4.1.
The acclaim_update microSD was tried with 4GB, 8GB and 32GB microSD cards unmounted and erased on the Nook - didn't work
All of the combinations of Power, Volume and Home buttons have been tried and all have resulted in a default factory reset but after registration I'm still left with an unrooted Nook with system 1.4.1
Am I the only one having this problem?
Hey RegLinUsr, will this root method restore from ANY root method, like Indirect or Snowball? Or does it have a specific set of circumstances it needs to get you back to factory reset?
In other words, does this unroot the tablet, or does it just reset the tablet to a previous state, root/nonroot notwithstanding?
Sent from my rooted Nook Tablet using Tapatalk 8)
When you do a factory restore, you are basically got a brand new nt from the day you bought it. If it came with 1.4.0, then it will be reimaged to that, but if you got the newer batch that comes with 1.4.1, then you will have to use the acclaim sd method to get it back down to 1.4.0 in order to root.
Right, I got that. What I mean is, if I did this on my Indirect-rooted tablet, would it undo the root and restore it to stock 1.4.0 like it had just come out of the box?
Sent from my rooted Nook Tablet using Tapatalk 8)
It doesn't restore to 1.4.1
My Nook came with 1.4.0 and was rooted. But I can now factory restore only to 1.4.1
rvr350 said:
When you do a factory restore, you are basically got a brand new nt from the day you bought it. If it came with 1.4.0, then it will be reimaged to that, but if you got the newer batch that comes with 1.4.1, then you will have to use the acclaim sd method to get it back down to 1.4.0 in order to root.
Click to expand...
Click to collapse
This would be so much easier if we could use some type of imaging software like clonezilla or acronis to backup or restore.
FWIW, I did a factory reset last night by powering the nook on while pressing the n key only (none of the volume keys). I was presented with factory reset menu and reset the nook. Even though it was originally loaded with 1.4.0, the factory reset did not revert back to that version rather just maintained the current version - 1.4.1 - that was on the nook perior to the factory reset.
nashdude said:
Right, I got that. What I mean is, if I did this on my Indirect-rooted tablet, would it undo the root and restore it to stock 1.4.0 like it had just come out of the box?
Sent from my rooted Nook Tablet using Tapatalk 8)
Click to expand...
Click to collapse
Just as I was saying, you will get an unrooted 1.4.0 stock after you do factory restore, or an unrooted 1.4.1 if you got the newer batch.
It was the ad-hoc way of "unroot" a few weeks back before Indirect got us one click unroot. We have come a long way...
This will not reset an NT to software version 1.4.0 if it already was a software version 1.4.1 from the factory. If the NT was purchased with v1.4.1 as default then that NT will have to wait for a rooting method that completely bypasses B&N bootup.
This method will undo Indirect's rooting method and should undo other's as well but that will have to be verified by people that have used other methods since I've only used Indirect's.
rvr350 said:
Just as I was saying, you will get an unrooted 1.4.0 stock after you do factory restore, or an unrooted 1.4.1 if you got the newer batch.
It was the ad-hoc way of "unroot" a few weeks back before Indirect got us one click unroot. We have come a long way...
Click to expand...
Click to collapse
Nope. Not true. I had 1.4.0 originally and rooted it via the usb drivers/Nook&Zergy method. Having unrooted the device I am still stuck with 1.4.1 no matter what form of Factory Restore I use. And the acclaim_update does not work for me. I'm sending for some 2GB microSD cards. Hope springs eternal!
Thanks for the answers, guys
Sent from my rooted Nook Tablet using Tapatalk 8)
Mine came with 1.4.0 and received the 1.4.1 via OTA. When I reset the device, it reverted to 1.4.0. Did your device come with 1.4.1? That may be why yours is only going back to 1.4.1.
Unless I didn't do the factory restore right, my NT which came with 1.4.0 reset to 1.4.1. My 16GB Sandisk SDHC card would not work with the acclaim_update.zip. I purchased a 4GB Sandisk microSDHC card with adapter at Walmart for $9.88 (cheapest they had) and this worked with the acclaim_update.zip.
Can somebody verify that the factory restore when done right really does restore 1.4.0 rather than 1.4.1?
lessilb said:
Getting panicky. I had root previously then got "upgraded" to 1.4.1. Have tried multiple ways of getting back to 1.4.0, all have which have left me with an unrooted Nook with 1.4.1.
The acclaim_update microSD was tried with 4GB, 8GB and 32GB microSD cards unmounted and erased on the Nook - didn't work
All of the combinations of Power, Volume and Home buttons have been tried and all have resulted in a default factory reset but after registration I'm still left with an unrooted Nook with system 1.4.1
Am I the only one having this problem?
Click to expand...
Click to collapse
No you are not. I received the update on the 26th...and judging by the posts it seems as if the OTA updates that were sent out during that time have a little something extra blocking the downgrade. I tried several different sd cards numerous times (more than 10), factory resets - more than 10. I have tried the register/deregister process and quickly turning off the wi-fi. The process runs,however, when finished it still reads 1.4.1.
No further updates to this method will be post here and any further updates to this method will only be posted in the Developer's Section Thread from now on.
***** Please post no further discussions in this thread! *****
hookedonnook said:
No you are not. I received the update on the 26th...and judging by the posts it seems as if the OTA updates that were sent out during that time have a little something extra blocking the downgrade. I tried several different sd cards numerous times (more than 10), factory resets - more than 10. I have tried the register/deregister process and quickly turning off the wi-fi. The process runs,however, when finished it still reads 1.4.1.
Click to expand...
Click to collapse
Thank you. I was getting paranoid. If we can't get a fix for this, I'll be off to ebay.
Deltam said:
Unless I didn't do the factory restore right, my NT which came with 1.4.0 reset to 1.4.1. My 16GB Sandisk SDHC card would not work with the acclaim_update.zip. I purchased a 4GB Sandisk microSDHC card with adapter at Walmart for $9.88 (cheapest they had) and this worked with the acclaim_update.zip.
Can somebody verify that the factory restore when done right really does restore 1.4.0 rather than 1.4.1?
Click to expand...
Click to collapse
removed...
lavero.burgos said:
I see people is still a bit confused. This is alternative easier way of make a hard reset AKA "8 failed reboot reset" it will reset the /system to factory NOT /data, for wipe data AKA erase/de-register for the nook, AKA factory reset for most android devices you have to go to settings> device info > erase and de-register device. ALL the users that get the 1.4.1 should do the erase/de-register and after that using the acclaim_update.zip will take you back to 1.4.0 (This is the only one that does the job to revert back to stock 1.4.0), after that use this method to bring the "N" button back to life (In replacement of the 8 reboot reset trick), once done all that you'll have a fresh 1.4.0 out-of-the-box. Then go ahead and use the method you feel more comfortable with to root and block OTA.
* Hard reset - reset the /system folder to factory (removing gApps, restoring bloatware, removing root, etc)
* Factory reset - will wipe /data (All your installed apps will be gone)
PS: This thread should be renamed to Hard Reset not factory reset as i know being an android user for long that when you do a factory reset it will wipe /data
Veronica
Click to expand...
Click to collapse
Incorrect and explained in the dev section thread... this thread no longer followed/updated, as posted above.
You may hit me up via private message as well and we can collaborate on each of our trials and errors in real time if you wish.
Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
[How-to] Quick Access to Nook Tablet's FACTORY RESET Screen [w/o "8 Failed Reboots"]
This is an alternate method for accessing the Nook Tablet's Factory Reset screen. This may be used to access this area instead of using the "8 Failed Reboots" method.
I can confirm that this does work and I have tested it several times to verify that it would work every time. I take no credit for figuring out this factory reset method as it was dcnarad that seems to have stumbled upon it. I do take credit for figuring out exactly how it is to be performed and have reposted it below correctly. dcnarad's post here is a bit haphazard and it slightly missed the mark as to how this actually needs to be performed so as to get to the factory reset screen properly.
Perform Factory Reset of the Nook Tablet:
PWR off the Nook Tablet.
Hold "PWR" & "∩" & "VOL+" & "VOL-" buttons simultaneously to reboot.
After reboot, release only the "PWR" & "∩" buttons after 2-3 seconds upon receiving the "∩ - Contains Reader® Mobile technology by Adobe Systems Incorporated." screen while still maintaining to hold the "VOL+" & "VOL-" buttons.
The screen may blink a couple seconds later and then you will be presented with the Factory Reset screen with the following options:
Do you want to reset your device to the factory default?
Press POWER key to exit
Press HOME key to continue
Are you sure?
This will delete all your content and restore the device to the factory default settings.
Press POWER key to exit
Press HOME key to continue
I even accidentally let go of the "VOL+" & "VOL-" buttons once while testing this a few times but quickly pushed them back down again and was still given the factory reset screen so this method works even with a little goof like that. This worked since holding down the "VOL+" & "VOL-" buttons was found to be unnecessary.
ENJOY!
NOTE: "HOME key" = ∩ button
NOTE 2: After some discussion with others, I decided to "take one for the team" and experiment with software version 1.4.1 update. I manually updated my Nook Tablet to software version 1.4.1 via the software download from BN.com. I applied the update, booted up software version 1.4.1 and then did a factory reset of the device afterwards. I have confirmed that once your NT has been updated to software version 1.4.1 then a factory reset afterwards will reset your NT to the new factory default settings of software version 1.4.1 and your NT will not revert to software version 1.4.0. It seems that B&N has pulled another fast one by over-writing the device's original factory software with this update. I was able to revert my NT to software version 1.4.0 via AdamOutler's Restore Barnes & Noble Nook 1.4.0 from SDCard afterwards with only a single issue. The ∩ button was not working after the device initially booted up into software version 1.4.0 [not uncommon] but after applying a second factory reset to my device, this issue was resolved.
I apologize if this is a dumb question, but does this undo root?
jread said:
I apologize if this is a dumb question, but does this undo root?
Click to expand...
Click to collapse
*** SEE NOTE 2 ABOVE ***
This will reset the NT to the Factory Default that it was shipped with [currently B&N Software version 1.4.0] and root will no longer be available until you root the NT again.
Thank you very much. This will be handy if I ever need to unroot.
RegLinUsr said:
This will reset the NT to the Factory Default that it was shipped with [currently B&N Software version 1.4.0] and root will no longer be available until you root the NT again.
Click to expand...
Click to collapse
This seems unclear. Is this the same as a recovery, and thus if you were patched to 1.4.1, you will reset to 1.4.1 with this method, or will this undo a 1.4.1 patch?
I tried this method with cfoesch system on my nook and after the wipe the modified bootanimation i still there.
This thread is incorrect. You only need to hold power button and home button for factory reset. Factory reset does not wipe root. Anyone expecting to reroot will have problem.
I explain this what the start post is: an alternative easier way of make a hard reset AKA "8 failed reboot reset" which will reset the /system to factory NOT /data, for wipe data AKA erase/de-register for the nook AKA factory reset for most android devices you have to go to settings> device info > erase and de-register device.
* Hard reset - reset the /system folder to factory (removing gApps, restoring bloatware, removing root, etc)
* Factory reset - will wipe /data (All your installed apps will be gone)
Sent from XDA using one of my Android Toys
succulent said:
This thread is incorrect. You only need to hold power button and home button for factory reset. Factory reset does not wipe root. Anyone expecting to reroot will have problem.
Click to expand...
Click to collapse
This is confirmed and OP has been updated, thanks.
This method does wipe Indirect's current root method as per the OP. You'll need to justify your statement since it doesn't explain anything at all as to what you're referencing.
lavero.burgos said:
I explain this what the start post is: an alternative easier way of make a hard reset AKA "8 failed reboot reset" which will reset the /system to factory NOT /data, for wipe data AKA erase/de-register for the nook AKA factory reset for most android devices you have to go to settings> device info > erase and de-register device.
* Hard reset - reset the /system folder to factory (removing gApps, restoring bloatware, removing root, etc)
* Factory reset - will wipe /data (All your installed apps will be gone)
Sent from XDA using one of my Android Toys
Click to expand...
Click to collapse
V, this does indeed reset the /data... upon rebooting after this reset, the device must process registration once again, just as it did when it was pulled out of the box after purchase. I have reset my own device several times and every time I rebooted, it begins the registration process all over again, every time.
RegLinUsr said:
V, this does indeed reset the /data... upon rebooting after this reset, the device must process registration once again, just as it did when it was pulled out of the box after purchase. I have reset my own device several times and every time I rebooted, it begins the registration process all over again, every time.
Click to expand...
Click to collapse
So this reset /system and /data at the same time? sure? so far both have not been mixed in Android world as far as i know , if this is the case which is weird then is super cool to have it and very helpful when you want to return back your NOOK
cfoesch said:
This seems unclear. Is this the same as a recovery, and thus if you were patched to 1.4.1, you will reset to 1.4.1 with this method, or will this undo a 1.4.1 patch?
Click to expand...
Click to collapse
*** SEE NOTE 2 in OP ***
worked like a charm for me last night when indirects one click unrooter failed.
jread said:
I apologize if this is a dumb question, but does this undo root?
Click to expand...
Click to collapse
Is it just me or does NO ONE read anything anymore?
Sent from my Nook Tablet.
Novalis31 said:
Is it just me or does NO ONE read anything anymore?
Sent from my Nook Tablet.
Click to expand...
Click to collapse
I think its more a testimony to folks coming into this with little or no understanding of Android and all the "buzz words" that go with rooting, etc. There's a learning curve there where people will see an answer, not understand it, fiddle fart around with the process for a bit and pick up a little experience, then have that AH HAH moment when they finally get what was being said. Problem is, it takes screwing something up twice or three times before they have that common frame of reference.
At least, that's how it was for me. It's getting easiER to find answers the longer that I'm here, but I can't say it's "easy" yet.
Sent from my rooted Nook Tablet using Tapatalk 8)
Novalis31 said:
Is it just me or does NO ONE read anything anymore?
.....
Click to expand...
Click to collapse
Good luck with that!!
As this is operations, and not development, I requested that it be moved to general. I also requested it be sticky'd
woot. post 3000.
Hi.
Just to post my experience.
I had a NT with 1.4.1 software version. I put the 1.4.0 back with AdamOutler method. Then I performed this method to Factory reset, I have gone through the registration. New NT. BUT when I go to check the version it says 1.4.0, which invalidates your NOTE 2, I believe.
Hope this helps, in some way
LacerdaPT said:
Hi.
Just to post my experience.
I had a NT with 1.4.1 software version. I put the 1.4.0 back with AdamOutler method. Then I performed this method to Factory reset, I have gone through the registration. New NT. BUT when I go to check the version it says 1.4.0, which invalidates your NOTE 2, I believe.
Hope this helps, in some way
Click to expand...
Click to collapse
It invalidates nothing. By your own admission, you reverted your NT to v1.4.0; hence, your factory reset will be v1.4.0. Read everything before making assumptions.
Thanks, this actually helped me. As I am absolutely new to the NT.
I tried to follow the new method for booting from the microSD card, but I could not complete the sequence because I was resetting it all the time.
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.
My grandson turned on my Nook while holding down the 'n' button. I don't know why but since I went to CM7 I figured B&N was out of the picture ... WRONG Glad I've got CWM on my SDcard and a good recent backup. I'm back up running again.
Now, if I do an internal CWM install will this prevent B&N from installing if the above every happens again
Do you mean he did a factory reset that brought the nook back to B&N software?
If thats the case then yeah, get CWM internal flashed and you'll be fine for the future.
Yep, BN installed again Time for cwm internal
Hi,
I think I might have bricked my Nook. A (hopefully) brief recap of what I did and have tried..
Tablet - 16gb
I was rooted and running CM10 internally. Decided to retore the factory image (I've done this before with no problems) and it worked fine. Restored, set up Nook with B&N, and re-rooted with zip file.
Check things out and decided to go back to the CM10 back-up I'd done via TWRP and this is where I think I screwed things up...I was on rooted stock 1.4.2 with CWM and restored the back-up from CWM.
Since then the internal set-up has been screwed up.
I tried to restore is back to stock again, it starts, tells me it's loading the software, I get the green check mark, pull out my SD-card, the tablet reboots and I get the wonderful red arrow telling me to restart and I get the arrow again to contact B&N support.
I've tried to flash the factory image, got TWRP up and running, tried to restore my back up and it says it runs except for an error: "E: Unable to mount '/data1.'
Also tried to install CM10 again and get the same error about unable to mount data.
Any suggestions anyone? I can work the Nook from the sd card (though it's interesting going back to CM7 again [will have to create a CM10 version]) but would love to fix this....
Thanks,
NikkieL
Try using Adam Outlet Ubuntu Total Re Flash method. It fixes most problems with bricked devices.
NikkieL said:
Hi,
I think I might have bricked my Nook. A (hopefully) brief recap of what I did and have tried..
Tablet - 16gb
I was rooted and running CM10 internally. Decided to retore the factory image (I've done this before with no problems) and it worked fine. Restored, set up Nook with B&N, and re-rooted with zip file.
Check things out and decided to go back to the CM10 back-up I'd done via TWRP and this is where I think I screwed things up...I was on rooted stock 1.4.2 with CWM and restored the back-up from CWM.
Since then the internal set-up has been screwed up.
I tried to restore is back to stock again, it starts, tells me it's loading the software, I get the green check mark, pull out my SD-card, the tablet reboots and I get the wonderful red arrow telling me to restart and I get the arrow again to contact B&N support.
I've tried to flash the factory image, got TWRP up and running, tried to restore my back up and it says it runs except for an error: "E: Unable to mount '/data1.'
Also tried to install CM10 again and get the same error about unable to mount data.
Any suggestions anyone? I can work the Nook from the sd card (though it's interesting going back to CM7 again [will have to create a CM10 version]) but would love to fix this....
Thanks,
NikkieL
Click to expand...
Click to collapse
I'd suggest that you try flashing afresh a CM10 or CM10.1 build using SDcard recovery, using a method such as described at http://forum.xda-developers.com/showthread.php?t=2056626.
In case you're considering using one of the so-called "unbricking" tools, read this post http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 first before you pick the wrong tool that would permanently wipe out your NT's individual device specific data like WiFi MAC address, security certificate, serial number, etc.
Thanks very much! Worked beautifully! Nook back working again!
NikkieL