Related
This is for the Nook Tablet 16Gig version only. Do not use with 8Gig version
Introduction
Making a magic SDCard which will take you back to stock 1.4.0 is easy!
This method will allow you to restore 1.4.0 firmware onto your Nook Tablet. Personally, I think holding the buttons and halting the device boot 8 times in a row is a bit time consuming. So, here is how you make a "Magic SDCard".
Instructions
Just follow these 4 easy steps to restore your device to 1.4.0.
Download this file: http://devftp.xda-developers.com/files/AdamOutler/NookTablet/acclaim_update.zip (Do not change the file name. Make sure it is named "acclaim_update.zip" without quotes).
Copy the file on a Micro SDCard.
Insert the Micro SDCard into your Nook Tablet
Turn on your Nook and observe a factory restoration.
Conclusion
This will initiate Recovery Mode and flash the entire zip. acclaim_update.zip will restore your device to stock firmware and wipe all user data. I will be working on other methods and I believe it is possible to force the device to boot it's entire firmware from Micro SDCard.
Troubleshooting
"N" Button is inoperative
solution:
Press and hold the Power and "N" Button until the device reboots.
Continue to hold the Power and "N" button until the device reboots 8 times. This will wipe data and restore the "N" button functionality
SDCard method does not work
solutions:
Ensure you have a Nook Tablet, not a Nook Color (funny as it sounds, this is a big problem)
redownload the acclaim_update.zip
Use the Nook settings menu to format the sdcard
Use a different SDCard
Video walkthrough
This video will walk you through switching firmware versions, rooting, backing up, and several other techniques
At the risk of sounding clueless..... How will placing a .zip file on a non-bootable card help? What about the signed bootloader issue? Are we assuming the Nook Tablet is not broken to the point it will not boot on it's own?
Part of the boot process checks the SD Card for this exact file (and checks the contents I assume). If it exists, it gets executed. Someone else has already confirmed this works, though we can't yet get it to work for any other firmware (ICS, etc).
Nice. Use the old 1.4.0 factory image to restore. Brilliant.
Now if only we can do that with custom roms.
Initial registration process with B&N
Does this .zip boots up just as if the NT came out of the box? if so, would the initial registration process with B&N push the 1.4.1 to us, or rather the NT pulls it from B&N?
It will (I believe) reset it to an out-of-the-box condition. The registration process might pull the update automatically...if you set up wifi. Don't set it up (right away), and you won't have an issue. Go in, root, side-load what you need to block the update, and you should be good to go.
according to BN's website, the update takes 5-10 min to download onto your device, and they instruct you NOT to power it off while this is occurring.
I would think you have a few minutes when it comes up to quickly find and install a few apps you may need for the 'fixing' process, (es file explorer, mount /system), then shut off the wifi.
Worst case scenario, you lose 5 minutes and are forced to restore again...
Just to be clear, this doesn't require root right?
Cubanluke88 said:
Just to be clear, this doesn't require root right?
Click to expand...
Click to collapse
No. Root is not required.
A few painfully obvious noob questions. I have a 16gb sd card installed in my tablet. I have sideloaded numerous apps and they show up on my go launcher. Can I use that sd card to install the download you recommend? I assume you mean download the link you provided to my computer and then side load it to my SD card from the usb port on my computer.
Do I need to port all my side loaded apps from the go launcher onto my computer prior to this installation as the factory reset will wipe out all my third party sideloads?
Sorry for the questions. I'm sure this is obvious to most if not all on here but I learned to use a keyboard with a Underwood manual typewriter in 1957 and I'm just now getting comfortable with windows XP.
AdamOutler said:
No. Root is not required.
Click to expand...
Click to collapse
This is the answer I was looking for and I would also like to thank you very much.
this will save many people!
Can this be done over the new B&N update? I don't have a Nook Tablet yet and was wondering before I buy it if I can still root it.
Kazba1626 said:
Can this be done over the new B&N update? I don't have a Nook Tablet yet and was wondering before I buy it if I can still root it.
Click to expand...
Click to collapse
Yes, this is (currently) it's primary purpose.
What if you haven't received OTA yet?
I am really nervous. I bought my wife a NT for Xmas...i rooted it and loaded it with everything she'd like to have on it. Then, i turned it off, wrapped it, and placed under tree.
When she opens it Xmas morning, will it automatically load this 1.4.Bull****? Is there anything that can be done to prevent the update before it happens so that you don't lose hours of work?
Thanks,
Tommy
Voyaging said:
I am really nervous. I bought my wife a NT for Xmas...i rooted it and loaded it with everything she'd like to have on it. Then, i turned it off, wrapped it, and placed under tree.
When she opens it Xmas morning, will it automatically load this 1.4.Bull****? Is there anything that can be done to prevent the update before it happens so that you don't lose hours of work?
Thanks,
Tommy
Click to expand...
Click to collapse
Okay, so i went in Titanium backup and froze the devicemanger and bn cloud service. That will enable me to NOT receive this update, correct?
If you installed the gapps with indirects root script you shouldnt have to worry about the update as it installs FOTAKill.apk as well which should kill ota updates like this.
Edit: Does this mean the tablet is unbrickable if you end up bricking it by messing with its software?
Thanks so much for this file and the information.
Montisaquadeis said:
If you installed the gapps with indirects root script you shouldnt have to worry about the update as it installs FOTAKill.apk as well which should kill ota updates like this.
Edit: Does this mean the tablet is unbrickable if you end up bricking it by messing with its software?
Click to expand...
Click to collapse
Not yet.. we need to prove it.. however, it will take all the root folder files in the update.zip uncompressed and named in a special way to do that.
I just checked and my wife NT is still 1.0.
What is the improvement of 1.4.0? Seems like i missed it.
And can i use this package to upgrade from 1.0?
Much thanks
. . . i use xda app for gtab. . .
Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.
I have been scouring these boards for hours and can't find my exact problem so I think I need to post this as a noob. I did Albert Wertz's method of rooting my Nook Tablet 16GB which he states will void the warranty. Afterwards I showed version 9.9.9 so I think it was rooted however I never saw superuser and such. I did something where the main menu bar no longer appears when pressing the n button too, annoying, I want it back too.
Anyway I booted into CWM from SD and then removed my boot SD and installed another SD with the img files on it. I have about 4 img files on it from throughout the day trying to update to CM7 and then tried a restore and just a CWM flash, every img file I select starts to perform it's update and somewhere around "extracting files" it says "installation aborted". At first I thought I had a bad memory card but both cards behave the same so I think they are good (creating 70MB partition on the CWM). I did a system restore on it and now it reports version 1.4.0 but I still get all the same errors, I'm stuck. I've spent about 9 hours of messing with this today and can’t think straight. I am going to bed and will try tomorrow, but if anyone could please tell me what I am missing I would very much appreciate it. Happy Easter ! Thanks, Mark O
markols said:
I have been scouring these boards for hours and can't find my exact problem so I think I need to post this as a noob. I did Albert Wertz's method of rooting my Nook Tablet 16GB which he states will void the warranty. Afterwards I showed version 9.9.9 so I think it was rooted however I never saw superuser and such. I did something where the main menu bar no longer appears when pressing the n button too, annoying, I want it back too.
Anyway I booted into CWM from SD and then removed my boot SD and installed another SD with the img files on it. I have about 4 img files on it from throughout the day trying to update to CM7 and then tried a restore and just a CWM flash, every img file I select starts to perform it's update and somewhere around "extracting files" it says "installation aborted". At first I thought I had a bad memory card but both cards behave the same so I think they are good (creating 70MB partition on the CWM). I did a system restore on it and now it reports version 1.4.0 but I still get all the same errors, I'm stuck. I've spent about 9 hours of messing with this today and can’t think straight. I am going to bed and will try tomorrow, but if anyone could please tell me what I am missing I would very much appreciate it. Happy Easter ! Thanks, Mark O
Click to expand...
Click to collapse
In CWM, you need to install from .zip files. It sound like you're trying to install .img.
Thanks... I was installing .zip files, not .img. I was pretty useless last night. I used Alberts 4_5SD recovery this morn and got it rooted to 9.9.9 and I had superuser and titanium backup so all was good. I ran NWM from internal on the tablet and told it to install ROM from the SD card. I pointed to the file and told it to backup, then install the new ROM it said an error had occured when I tried this. I then booted from another SD card to go to CWM and after the white screen with the box, it went into backup and then restored the ROM, however it took me back to a unrooted version. It looked for the ROM I wanted to load but that was on the other SD card. Now I am back at square one, frustrated...
I think I might have found the problem but I am not sure. When I was doing the original CM7 update I wrote CWM to the E drive, (MyNook) so now the drive reports a total size of .99GB with 433MB free. So CWM is installed on this drive and I think that is the proplem. Is there a way to get CWM off the E drive? If I can just uninstall it, will that be sufficient enough to get the root back and then correctly install CM7? Thanks again in advance.
I guess this is turning out to be an ongoing update from me, lol... I am back to a rooted Nook Tablet with 9.9.9 So since I am a glutton for punishment I will try again tonight to do the CM7. I simply deleted the CWM file that I found in the internal memory and it seemed to not hurt anything.
This time I am planning to download Indirect’s latest "NOOK Tab Recovery Flasher.apk" directly to my Nook Tablet, (at the inlaws now and no wifi
If I understand correctly it will install CWM direct on my tablet, I am just wondering where it will end up installed? Then I downloaded the file for internal CM7 installation, the file is named "Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed" I have it and nothing else on the sd card. So when I run CWM from the Nook, I point to the .zip file on the SD card. Sounds easy but after three screw ups, I am aprehensive.
If someone could please confirm that this procedure and the files I am using are compatible and should work with my 16GB Nook Tablet. Again thanks very much and I hope all have been enjoying this Easter holiday........
markols said:
I guess this is turning out to be an ongoing update from me, lol... I am back to a rooted Nook Tablet with 9.9.9 So since I am a glutton for punishment I will try again tonight to do the CM7. I simply deleted the CWM file that I found in the internal memory and it seemed to not hurt anything.
This time I am planning to download Indirect’s latest "NOOK Tab Recovery Flasher.apk" directly to my Nook Tablet, (at the inlaws now and no wifi
If I understand correctly it will install CWM direct on my tablet, I am just wondering where it will end up installed? Then I downloaded the file for internal CM7 installation, the file is named "Nook-Tablet-CM7-Alpha-Final-TEAM-B-signed" I have it and nothing else on the sd card. So when I run CWM from the Nook, I point to the .zip file on the SD card. Sounds easy but after three screw ups, I am aprehensive.
If someone could please confirm that this procedure and the files I am using are compatible and should work with my 16GB Nook Tablet. Again thanks very much and I hope all have been enjoying this Easter holiday........
Click to expand...
Click to collapse
The steps that you have listed in this post are correct. If you do this exactly, everything should go according to plan.
Indirect's great app installs CWM to the recovery partition of your device, overwriting the B&N stock recovery. You can always go back to stock recovery if need be, though, so don't worry.
Thanks Solar.Plexus
The procedure worked as I hoped. I don't understand what went so wrong in my first attempt but the main thing is my wife doesn't look at me with THAT look anymore, since she thought I bricked her 12 hour old NT.....
markols said:
Thanks Solar.Plexus
The procedure worked as I hoped. I don't understand what went so wrong in my first attempt but the main thing is my wife doesn't look at me with THAT look anymore, since she thought I bricked her 12 hour old NT.....
Click to expand...
Click to collapse
No problem. Glad to hear your wife's happy again!
installaton aborted while installing clockmodrecovery
hii i am sagar
i want solution to this problem any body have solution means please reply
i am using micromax mad a94
when i am trying to install clockworkmod on my phone it always show like these
install/sdcard.....
finding update package......
opening update package.....
verifying update package....
installation aborted........
anybody have solution to this problem
please tell me
thank you
Did u solve it yet?
Sent from my iPod touch using Tapatalk
Hello,
I've installed CM internal to (2) NT 16GBs without incident, and I got stumbled by the n button not working with 1.4.1 that was on my third. Ultimately - I downgraded to 1.4.0, installed CM7, and then did the dumb thing.
I meant to hit wipe data and cache, and I clicked factory reset in CWM. (And at this point - it is stuck in a state where I can boot to CWM - but cannot get CM7 to boot in any form from the internal rom).
I attempted the following
1) acclaim restore (just tried didn't do anything)
2) backup / restore from alternate nook Tablet 16Gb (man this seemed promising ...)
3) couple of the different unbrick scenarios - but I don't have adb, and it seems like windows 7 is not a happy camper with nook usb devices, (and adb isn't happy either.)
4) meghd00t restores (couple of different variations.)
does anyone have any starter threads that I should start walking down for the same stuff - I have browsed, and it's been a couple of hours and I'm exhausted. will poke back in tommorow, and will get this thing plugged into a linux host.
It didn't seem like adb could be so hard ...
--Adrian
Hmmm interesting... ok first of all doing this "I meant to hit wipe data and cache, and I clicked factory reset in CWM" is not dumb is ok to do but is not good signal the hang actually is very weird. Maybe all you have is a corrupted cwm recovery flash. Now be explicit if you indeed could try some unbrick methods succesfully (the ones running from sdcard) and what methods exactly did you try.
~ Veronica
things I've tried - part 1
1) just try to restore to factory with acclaim_update.zip on non-booting sdcard , (this is the 1.4.0 image) - I get the grey n, a flash of white - (like it's going to boot), and that that "please restart your device and try again..."
(This worked when it was factory), but it seems like the logic to check the sd card and start to recover isn't working.
2) Tried the thread here - http://forum.xda-developers.com/showthread.php?t=1562130 - meghd00tr4-sdimg.zip boots, but first time - get red reverse highlighted line - "booti: bad boot image magic in memory" - s5 in the upper left corner of the cyanoboot screen, and the n button doesn't seem to do anything.
3) same thread different image - repart.img, this runs fine- and after about 30 seconds of boot, I get a green check, (waited a full (2) minutes after that green check before I unplugged it.) - same message after boot.
4) full restore of nook tablet from current good cm7 image (and this is the one that most concerns me) - NT16gbV4_6 based cwm v5.5.04 - attempting restore of backed up alternate nook tablet - and the exact same thing happens at boot - does the image not touch partions that aren't related to the root install -(this seems like maybe there is something the bootloader is looking for in the image that isn't right, and it wedges?)
I am going to work on getting an adb setup going that works and then start working down a couple of fix recovery scenarios today / tonight.
It doesn't seem like this is unrecoverable - and the worst part is -I had cm7 booting fine for a couple of reboots, and then something went awry.
--Adrian
as I think about this ...
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
peril said:
I do have (2) differnt backups, and I wonder if that restore was the wrong thing to do.
I got to thinking this as I saw the restore of the .android_secure file, from the ALTERNATE nook. I have the backup from the 1.4.0 "original working" image of this nook before the cm 7 issues- but I put it on an SD card that is safetly out of my reach. (In a friends cell phone.)
I think an easy thing will be to restore that backup as another test.
-Adrian
Click to expand...
Click to collapse
Right, try that first, dont attempt anything advanced yet. Your problem could be solved easily
Just to make sure you flashed cwm from @Indirect app?
~ Veronica
Sent from my Nook Tablet using xda premium
Wait, can you boot into a CM7 SD ROM? From there you could try reflashing recovery.
Sent from my R800x
FIXED
I used this method - and I was good to go.
http://forum.xda-developers.com/showthread.php?t=1470910
In one of the flashes - must have hit the power prior to something being complete with the recovery.
thanks all for your support - and really appreciate the time in the forum. I'm going to put together a torrent with the recovery stuff in it, and make sure it's available as my little part. (Give me a day or so.)
Thanks again.
--Adrian
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
I also screwed up...Reverting to 1.4.0
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
mr_truevision said:
Tried to revert to 1.4.0, and followed all instructions as showned on a youtube video. Unfortunately, as it was reverting back to older version as soon as it finished the process - the tablet wouldn't start back up. Did any one ever have this happen to them.. Fortunately, I had just bought today at WalMart. So, I'm going to replace it...
Was just curious, if it ever happened to any one. If so what did I possibly do wrong....
Click to expand...
Click to collapse
Hmm i think you have a 8GB Nook Tablet and the acclaim_update.zip is only for 16GB NT.
~ Veronica
ubuntu recovery.
This was strictly for CM7. I have no problem with being locked out of the B&N services. (I use the nook application for that access.)
Wish I would have known the serial number before / after. I was able to login to my B&N account after 1.4.0 was restored from ubuntu.
--Adrian
lavero.burgos said:
The problem with that is that you will lose your original serial ID's and MAC address if you didnt backup your rom partition (mmcblk0p5) first so if you use B&N services you wont be able to register after flash any stock rom.
~ Veronica
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
Hey Everyone,
So here's what's happening:
I have an original Nook Tablet (16GB) v1.4.0 with Blocked OTA updates. Well I did...it's sort of dead now.
Initially, I purchased the device for my son on Christmas 2011. Back then, we only had 'Indirect's' ZergRush exploit to root and install CWM on Nook Tablets. There wasn't a whole lot to choose from. The Bootloader was still locked and there were no Custom ROMs in sight.
This actually worked fine for us, since my son got to enjoy his new rooted Nook Tablet with all the benefits of a 7" Android Tablet, yet he still got to enjoy the 'Nook Tablet Experience', as he's purchased/downloaded over a dozen Nook Books over this past year.
Earlier today, I went to turn on his Nook Tablet and instead of it booting up like normal, it fell into an endless bootloop.
It would power on, I could see the 'n' logo along with the verbage at the bottom that mentions the Adobe Flash technology and that's it. It keeps doing that over and over again.
Now since I do have quite a bit of hacked android devices, in this situation I would normally just manually boot into Recovery and flash my Nandroid.
Well, for whatever reason, I guess that's not possible here. No matter what I do, it's stuck in that horrible bootloop.
I found a thread on here where I can make a bootable MicroSD Card that would boot me into CWM. From there I could restore the Nandroid.
I actually 'made' this MicroSD Card, or I thought I did...but unfortunately the Nook Tablet will not boot AT ALL from it. So if I leave the Micro SD Card in the Nook Tablet, it's pretty much dead. It won't turn on, power on or anything.
As soon as I take out that MicroSD Card, there goes the bootloop once again.
Question(s)
1. - Does anyone have the correct files or a better way, so that I can make this bootable MicroSD Card, so that I can boot into Recovery and flash the Nandroid?
In case this doesn't work, I did make another MicroSD card that contains the v1.4.2 Stock Partition Image. Apparently, I can boot off this and it will do a Factory Restore of the Nook Tablet, running v1.4.2 Stock. It will not be rooted or anything.
2. - If I go this route, what are my options for rooting and installing custom recovery on v1.4.2?
3. - If I do choose to do this, I may just look into a Custom ROM. That said any recommendations?? I would prefer JB over ICS. I would prefer a VERY CLEAN, FAST, lightweight ROM, over heavy mods.
The one consideration is that it needs to still allow us to utilize the native Barnes & Noble functions, where we can sign into our account, download books from our library, purchase and download books and etc.
Again, if I can just boot into CWM and flash his Nandroid, that would be a hell of a lot less work. But if not, then so be it.
Thank you!
BJ
this is cwm
b1ggjoe said:
Hey Everyone,
So here's what's happening:
I have an original Nook Tablet (16GB) v1.4.0 with Blocked OTA updates. Well I did...it's sort of dead now.
Initially, I purchased the device for my son on Christmas 2011. Back then, we only had 'Indirect's' ZergRush exploit to root and install CWM on Nook Tablets. There wasn't a whole lot to choose from. The Bootloader was still locked and there were no Custom ROMs in sight.
This actually worked fine for us, since my son got to enjoy his new rooted Nook Tablet with all the benefits of a 7" Android Tablet, yet he still got to enjoy the 'Nook Tablet Experience', as he's purchased/downloaded over a dozen Nook Books over this past year.
Earlier today, I went to turn on his Nook Tablet and instead of it booting up like normal, it fell into an endless bootloop.
It would power on, I could see the 'n' logo along with the verbage at the bottom that mentions the Adobe Flash technology and that's it. It keeps doing that over and over again.
Now since I do have quite a bit of hacked android devices, in this situation I would normally just manually boot into Recovery and flash my Nandroid.
Well, for whatever reason, I guess that's not possible here. No matter what I do, it's stuck in that horrible bootloop.
I found a thread on here where I can make a bootable MicroSD Card that would boot me into CWM. From there I could restore the Nandroid.
I actually 'made' this MicroSD Card, or I thought I did...but unfortunately the Nook Tablet will not boot AT ALL from it. So if I leave the Micro SD Card in the Nook Tablet, it's pretty much dead. It won't turn on, power on or anything.
As soon as I take out that MicroSD Card, there goes the bootloop once again.
Question(s)
1. - Does anyone have the correct files or a better way, so that I can make this bootable MicroSD Card, so that I can boot into Recovery and flash the Nandroid?
In case this doesn't work, I did make another MicroSD card that contains the v1.4.2 Stock Partition Image. Apparently, I can boot off this and it will do a Factory Restore of the Nook Tablet, running v1.4.2 Stock. It will not be rooted or anything.
2. - If I go this route, what are my options for rooting and installing custom recovery on v1.4.2?
3. - If I do choose to do this, I may just look into a Custom ROM. That said any recommendations?? I would prefer JB over ICS. I would prefer a VERY CLEAN, FAST, lightweight ROM, over heavy mods.
The one consideration is that it needs to still allow us to utilize the native Barnes & Noble functions, where we can sign into our account, download books from our library, purchase and download books and etc.
Again, if I can just boot into CWM and flash his Nandroid, that would be a hell of a lot less work. But if not, then so be it.
Thank you!
BJ
Click to expand...
Click to collapse
this is a link to download cwm "mediafire .com/?tpckcmp9pr5e826" i had to put a space between "mediafire and .com" cuz the forum wont let me post links yet. Just put this file on a micro sd card..turn nook off and insert card... and when you turn on the nook is should boot to recovery..hope this helps
Systems6,
I went ahead and downloaded your .zip, and extracted the files and placed them on the root of the SD Card. I placed the SD Card back into the NT. Still no dice, not booting up at all. Any other suggestions?
Thx.
BJ
hope this helps you out...
b1ggjoe said:
Systems6,
I went ahead and downloaded your .zip, and extracted the files and placed them on the root of the SD Card. I placed the SD Card back into the NT. Still no dice, not booting up at all. Any other suggestions?
Thx.
BJ
Click to expand...
Click to collapse
well it looks like you have to reboot to stock...then root and flash rom again...here is the link to return to stock "http://raywaldo .com/2012/06/make-unbrick-repartition-image/" again i put a space in between the 'raywaldo and .com"...looks like your going to take the long route to fix it good luck hope you get it running again
** UPDATE:
I was able to follow the instructions on the following thread and made a bootable MicroSD Card running CWM v5.0.2.8:
http://forum.xda-developers.com/showthread.php?t=1640958
Once I was booted into CWM, I tried to do a Nandroid Restore, the way I always have. Unfortunately, I got the following error message:
'MD5 mismatch!'.
Now, I have never encountered this. I made sure that MD5 Signature verification was toggled 'Off'. Not sure if that would have made a difference or not.
Unfortunately, it didn't help. Now I'm stuck with a Nandroid that I cannot restore.
Can anyone suggest something for me to try, in order to try to restore this Nandroid? If not, I will go Plan B and restore to Factory v1.4.2.
However, if I go that route, I still would like some answers to my initial questions about which ROM to go with and etc. Might as well go to JB if I have to start all over.
Thanks!
BJ
Plan B starting to look better and better...
Well here another plan B that was tested earlier and it took 15 minutes from start to finish.
If you want to go to JB then I would recommend this rom and the only thing that you can't do on BN app is that you will not be able to use the books that have record your voice in book or play the read to me books (I think once you are not on the stock bn rom, those two parts stop working). I run kindle app for library loans, overdrive other e-readers without problems,
b1ggjoe said:
** UPDATE:
I was able to follow the instructions on the following thread and made a bootable MicroSD Card running CWM v5.0.2.8:
http://forum.xda-developers.com/showthread.php?t=1640958
Once I was booted into CWM, I tried to do a Nandroid Restore, the way I always have. Unfortunately, I got the following error message:
'MD5 mismatch!'.
Now, I have never encountered this. I made sure that MD5 Signature verification was toggled 'Off'. Not sure if that would have made a difference or not.
Unfortunately, it didn't help. Now I'm stuck with a Nandroid that I cannot restore.
Can anyone suggest something for me to try, in order to try to restore this Nandroid? If not, I will go Plan B and restore to Factory v1.4.2.
However, if I go that route, I still would like some answers to my initial questions about which ROM to go with and etc. Might as well go to JB if I have to start all over.
Thanks!
BJ
Click to expand...
Click to collapse
I got the MD5 mismatch error once when I renamed the Nandroid backup directory. I don't think it liked the spaces in the directory name. Try renaming it to the original name (if you even changed it).
There is a link in my signature that works to root at the very least firmware 1.4.3. Anything that you purchased from the B&N store will still be there if you restore to stock, if you install the Android Market again, anything you purchased will still be there (and you can go online and see anything free that you had installed, and install it from there).
If you do choose to install another ROM, same thing. Books purchased from the B&N Market should be available in the Nook app from the marketplace (I have not confirmed this with my own tablet, though).
confirmed on nook color
liquidzoo said:
There is a link in my signature that works to root at the very least firmware 1.4.3. Anything that you purchased from the B&N store will still be there if you restore to stock, if you install the Android Market again, anything you purchased will still be there (and you can go online and see anything free that you had installed, and install it from there).
If you do choose to install another ROM, same thing. Books purchased from the B&N Market should be available in the Nook app from the marketplace (I have not confirmed this with my own tablet, though).
Click to expand...
Click to collapse
I have done this with a nook color and it works.