Database Develop

[Q] Ready to Root?

Hi all.
I'm getting my NC in 2 days, and I'm looking to make sure I've got my ducks in a row so I can root it right away when I do get it. Here is what I have resource and hardware wise. Can any of you that have done this already tell me if I'm missing anything?
I have:
- Nook Color (Soon!)
- 16gb SD card
- Card reader
- Windows 7 PC
- This guide from Nookdevs (nookdevs.com/NookColor_Rooting)
- Patience
Am I missing anything? With what I have I should be able to sit down and root it as soon as I have the device, correct?
Thanks very much!

Sounds about right to me. I had the biggest pain in the ass trying to install ADB. It eventually started working, but I have no idea how or why haha.

Perfect. So there should be a USB cable in the box with the Nook then? I dont need to buy any cabling separately or anything?
If so I guess I just get to sit on my hands for a couple days!

Your rooting a Nook not going camping.

Pinesal said:
Your rooting a Nook not going camping.
Click to expand...
Click to collapse
Well, I am working nights this week, so if I *do* miss any hardware I'll be stuck until I can get to a store after the holidays.
Also, it's my first time rooting/jailbreaking anything so I want to make sure I'm aware of what I'll need. I'm not an idiot, (I work as a systems analyst) but it's still a new process for me.

I'd grab a linux bootdisk, if possible. The main reason is that after rooting the nook, it can be hard to get your sd card back to the proper size (it will register as a 40mb device). Win7 wouldn't see the remaining 7.96GB of my device, but ubuntu's Disk Utility did just fine.

That's weird... did the nook still detect the correct size? If you loaded more than 40mb of data on there then put it into the nook what happened? Once you detected the correct size in Linux were you able to access the full card from windows, or have you had to load all your data onto the card via linux since then?
Honestly I dont even really care if the SD card bricks after I'm done with it. I'm getting one just to root the device, (USB key or cloud storage for me thanks) and I guess for extra storage on the Nook itself afterwards. Thanks for the heads up though, I'll look into that solution if I need to.

you can't load more than the 40MB that windows sees, until you fix the partition table of the SD card. It may be due to the software I used to write the image (I think it was Win32 Disk Imager, recommended on nookdevs).
Either way, it's not hard to load up an Ubuntu liveCD, go to System -> Administration -> Disk Utility, select the SD Card, delete the partitions, and then create a new partition (FAT32, I believe), and then re-load it to the nook. It took less than 10 minutes to get my SD card back to the correct size.

Right, gotcha. Thanks much If I run into that I'll make myself a linux disk.

Just use the nook itself to format the microSD and it will read the proper size afterwards. It worked for me anyways.

mob87 said:
Just use the nook itself to format the microSD and it will read the proper size afterwards. It worked for me anyways.
Click to expand...
Click to collapse
Even better! Saves me learning to use Linux

mob87 said:
Just use the nook itself to format the microSD and it will read the proper size afterwards. It worked for me anyways.
Click to expand...
Click to collapse
Seconded. A linux distro is always handy, but unnecessary for the partitioning

I was going to mention the re-formatting of the SD card quirkyness since that was an issue for me, but I see that's been covered already
Oh, and patience is really not something you need much of for this. If you follow the instructions on nookDevs, it's a completely painless process. Seriously.. they've made it that frakkin' easy.

TchnclFl said:
Sounds about right to me. I had the biggest pain in the ass trying to install ADB. It eventually started working, but I have no idea how or why haha.
Click to expand...
Click to collapse
Do you know if the "Install ADB" step is absolutely neccesary? Or is it just Optional? That step looks the most intimidating.

RickHouTX said:
Do you know if the "Install ADB" step is absolutely neccesary? Or is it just Optional? That step looks the most intimidating.
Click to expand...
Click to collapse
RickHouTX, I was wondering the same thing myself. Hopefully someone can chime in and let us know. I'm hoping that step isn't "absolutely" necessary.

AZBrauMeister said:
RickHouTX, I was wondering the same thing myself. Hopefully someone can chime in and let us know. I'm hoping that step isn't "absolutely" necessary.
Click to expand...
Click to collapse
I am more interested in the note at the top
Note: For users who have failed at implementing the instructions below several times, the NookColor community reccomends that you use market and download adb wireless, and perform your adb work over the wifi connection to the NC rather than painfully trying to install and modify the drivers over and over. If you would prefer to do that in the first place rather than the instructions below, we won't be insulted.
Click to expand...
Click to collapse
So... does that mean I can just use Auto-Nooter, then grab the ABD app from the marketplace and it automates everything else? Or am I mis-reading this?

[Q] Is my Nook Bricked beyond all hope

I was reading this thread [RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!). But, since I am new to this forum I couldn't post there. I hope this is the right place to ask for help.
I upgraded my NC to 1.1.0 successfully. I put Autonooter 3.0.0 on a MicroSD card. With my NC off, I inserted the card and then plugged the NC into my PC. I got a black screen for over 5 minutes. It looked like nothing was happening, so, I disconnected the NC, removed the SD card and tired to turn the NC on. No joy, it won't turn on and won't boot at all. I think my Nook is bricked. Any ideas what went wrong?
I've read some other threads about similar problems. It seems there is a fix to get it back to stock (1.1.0). I hope the Recovery thread I mentioned above is where the answer lies. But, I'm a bit confused and don't want to make any more mistakes. I only have one 4GB SD card at my disposal right now.
My questions are as follows:
1. Is my NC bricked beyond hope of recovery?
2. If I follow the procedures in this post can I get it to boot from the sd card even though it won't turn on at all?
3. What is the difference between the Rootpack and the Clockwork Recovery Image?
4. This is the confusing part. Should I download the RootPack? Or, should I download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb)
5. Since I only have a 4GB card, what should I choose?
6. Should I opt for 1.0.1, or 1.1.0 where it was still working.
7. Can I get all of this on one 4GB card?
8. Is there anything else I should be weary of before starting this procedure?
If i have posted this in the wrong place, I am sorry. But, I hope someone can clear things up for me. Thanks.

This is the right place to ask general questions.
1. Most certainly not.
2. Yes, using a bootable CWR SD is the way to go.
3. Totally different. The Rootpack is the name given to a package that helps you root your Nook. CWR image is a recovery image. That means you can boot to this recovery utility and apply changes to you NC (like repairing stuff, making backups, etc.).
4. An image will adapt to the drive. If you have a 4GB SD and burn (dd) a 1GB image to it, your SD will suddenly present itself as a 1GB SD. If you format it with the right tool, your SD will be 4GB again. So don't panick, if it says 1GB after burning, it's jut "adapted to the image". You haven't lost any disk space.
5. 1GB would be enough, but you can go up to 4GB image with a 4GB.. It could sometimes be a problem to apply an image which is the exact same size as the drive. I would use th 1GB, which is plenty for what you are going to do.
6. That's up to you. Both should work.
7. Yes.
8. Just read threads exhaustively before attempting anything..
So what you need to do is read threads about this CWR Bootable img to learn how to burn it to your SD.
Then, find the appropriate .zip files to flash (apply) (1.1 recovery and 1.0.1 are available in dev section.
Copy them to root of SD.
Boot with the SD Card and apply zip files from SD.
If your NC should still have problems booting, you can also apply a boot repair zip file, that you will find on my Nook Color restore to stock tread in dev..
Sam

His Rootpack wont work on 1.1.0 You should have seen that in his instructions. It will only block 1.1.0 and fake it. You need to see this thread to fix your nook. It is 100% NOT bricked, just messed up atm. You can fix it tho. Read here:
http://forum.xda-developers.com/showthread.php?t=949699

Thanks for thr quick reponse Sam. I'm at work now, but will be able to use your suggestions later this afternoon\tonight. So, if I get a 1gb CWR image on my 4gb sd card, plus the 1.1.0 zip file and put it in the root of the sd card, the Nook should boot up even though I can't turn it on now? How long typacally will it take to boot up? What should I expect to see?
I will post results after I try the procedure. Thanks again!!

Thanks Thiboi69. I have printed out the instructions from the link you sent and will follow them to the T. I'll post results later.

It will work. I have never heard of a 100%bricked NookColor to date. And I have read 1,000's of posts here over the past 4 months. IT is just your boot partition that is messed up and B&N made it check the sdcard first for a Boot partition, then fall back to eMMC. Thank you B&N !!!

I downloaded all the files, wrote them to my sd card, and put it in the Nook. When I connected the Nook to my pc, I got a messaage the the battery was too low to turn on. So, I took the sd card out, and put the Nook on charge. After a while, it turned on, booted up and when I checked my OS, I found that I had
version 1.1.0. Apparently, my attempt to root with autonooter 3, never got installed, partially or completely. And, my battery probably got to low to turn the nook on. So, I didn't need to use CWR after all. I apologize to all who have tried to help me. But, all replies were good and contained useful info.
Now, my question is: Should I try to use Autonooter 3 again, or is there an easier
(more foolproof) way to root v1.1.0?

I just got a nook last night with the sole intention of hacking it - and did so in a matter of minutes. Autonooter couldnt be easier! When you get to the part of putting the SD card in the nook and connecting it to USB to make it boot, just plug it in and go get a cup of coffee. Don't unplug or touch anything until it boots up by itself. At 1st I thought it wasn't doing anything as I didn't see a clockwork mod screen come up or anything, but just be patient and it'll tell you when it's done. Just make sure it's pretty well charged when you do it - mine was about 80% or so.
Honestly after less than a day of the rooted stock 2.1 Eclair OS, I'm ready to drop a fully customized Froyo or Gingerbread image on this thing. Autonooter it 1st and run it for a few days 1st and see what you think. I'm still learning the ins and outs of tinkering with this thing, but so far it seems much easier than the Epic and Moment I've been beating on. Seems pretty well unbrickable too thanks to the boot to SD 1st option B&N baked into this puppy.

jostarr said:
I was reading this thread [RECOVERY] Monster RootPack 0.7 / Clockwork Recovery 3.0.0.5 SD (1.1 Compatible!). But, since I am new to this forum I couldn't post there. I hope this is the right place to ask for help.
I upgraded my NC to 1.1.0 successfully. I put Autonooter 3.0.0 on a MicroSD card. With my NC off, I inserted the card and then plugged the NC into my PC. I got a black screen for over 5 minutes. It looked like nothing was happening, so, I disconnected the NC, removed the SD card and tired to turn the NC on. No joy, it won't turn on and won't boot at all. I think my Nook is bricked. Any ideas what went wrong?
I've read some other threads about similar problems. It seems there is a fix to get it back to stock (1.1.0). I hope the Recovery thread I mentioned above is where the answer lies. But, I'm a bit confused and don't want to make any more mistakes. I only have one 4GB SD card at my disposal right now.
My questions are as follows:
1. Is my NC bricked beyond hope of recovery?
2. If I follow the procedures in this post can I get it to boot from the sd card even though it won't turn on at all?
3. What is the difference between the Rootpack and the Clockwork Recovery Image?
4. This is the confusing part. Should I download the RootPack? Or, should I download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb)
5. Since I only have a 4GB card, what should I choose?
6. Should I opt for 1.0.1, or 1.1.0 where it was still working.
7. Can I get all of this on one 4GB card?
8. Is there anything else I should be weary of before starting this procedure?
If i have posted this in the wrong place, I am sorry. But, I hope someone can clear things up for me. Thanks.
Click to expand...
Click to collapse
Joe, I would recommend downloading the 1gb rootpack image and a restore to stock file. Make your bootable clockwork recovery image, place the resotre to stock file on the sdcard, turn your nook off, insert the sdcard, power on and flash the file. All this info and more can be found in my thread here:
http://forum.xda-developers.com/showthread.php?t=949699

Thanks for your suggestion Riley, please take a look at my post # 7 above. Seemd my NC
had a low battery. When I charged it, all was ok. It booted up and I was back in 1.1.0.
But, I just now tried autonooter 3.0.0 again. When I pluged thr NC inyo my PC, I got some sort or warning message. I hit cancel and waited a few minutes. The message came up again. It said the device was not recognized. I unplugged, removed the card, and my fully charged NV won't turn on. And, windows explorer can not read the sd card. This is basically what happened yesterday to cause my panic. The sd card had all the files befor I inserted it into the NC. Now, it's unreadable and I can't turn on or boot the NC again.
Is it autonooter 3.0.0, or the card, or the Nook, or me?????

One correction to post # 10. I can read the sd card in windows explorer. But my NC won't turn on.

With sd card out of the Nook, I get a "Welcome to the Found New Hardware Wizzard"
What does this tell anyone about the condition of my Nook?

I am having a problem and don't really know what to do. When I start my NC its stops at the N screen and goes no further. I've tried a lot of the different ways to get it back to stock with no luck. When I try to write CWM to my SD card with win32 it either doesn't have enough room to put the stock file on the zip with it or when I open the SD card it says the card needs to be formatted. The file is a tr.gz or something like that is there a step between that I am missing or just download the CWM and write to SD using win32? I also tried adb with no luck. I am very new to rooting so any super dumbed down instructions would be greatly appreciated.
Sent from my ADR6300 using XDA App

You can put the rom image to a separate SD card. Just swap it after you boot up from cwr. I did it before for flashing froyo to emmc.
Sent from my PC36100 using XDA App

72chevy2k2 said:
I am having a problem and don't really know what to do. When I start my NC its stops at the N screen and goes no further. I've tried a lot of the different ways to get it back to stock with no luck. When I try to write CWM to my SD card with win32 it either doesn't have enough room to put the stock file on the zip with it or when I open the SD card it says the card needs to be formatted. The file is a tr.gz or something like that is there a step between that I am missing or just download the CWM and write to SD using win32? I also tried adb with no luck. I am very new to rooting so any super dumbed down instructions would be greatly appreciated.
Click to expand...
Click to collapse
Have you followed the restore-to-stock procedure outlined in this thread?
http://forum.xda-developers.com/showthread.php?t=914690

Just a noobish advise!
After configure everything and become accustomed to some of the NC behaviors this should not matter, but I remember at my first attempts at rooting the NC, using a Win7 PC was much easier than using Win XP or iOS devices. Might fix your 'not recognized' problems, sd card recognition and formatting problems etc.

It has CWM on it. I can get it to recovery but it will not recognize the SD or not mount it and I go to mount it in the menu and it says something like can not mount SD card so I have been trying to do the CWM SD burn but I keep getting the above errors I am on a vista computer so I will try it on my windows 7 one and see how that goes. And the different SD card one I will try that as well after work thank you for the help.
Sent from my ADR6300 using XDA App

RickOSidhe said:
Have you followed the restore-to-stock procedure outlined in this thread?
http://forum.xda-developers.com/showthread.php?t=914690
Click to expand...
Click to collapse
Yes I did try that one I put the nookie froyo on the SD and put it I'm my turned off NC and plugged it in to my computer and it sat at the N screen forever and after a while I took it off and it was still in the same state could the CWM be the problem?
Sent from my ADR6300 using XDA App

I'm not sure what posts 13 thru 18 have to do with my problem???

Just didn't feel like starting a new thread for the couple of questions I had along the same line as yours.
Sent from my ADR6300 using XDA App

What is uNooter?

I just got my Nook Color and am looking into how to go about rooting it for CM7. I checked out CM's Wiki page on it here and it mentioned using uNooter. I haven't read about this tool anywhere else and Google searches for it turn up practically nothing. Is this not the right tool to use? The forums mostly seem to mention ManualNooter, Auto-Nooter, etc. Also is it possible to flash CM7 on the internal memory and avoid using an SD card altogether?

Never heard of unooter and I've been reading theses forums since December. Auto mooter was to root the older firmware 1.0 ,1.01,and 1.1. Manualnooter is for the newer froyo firmware.

Rooting stock is not required to install CM7.
You simply need to create a Clockworkmod recovery microSD card and you can then flash CM7 (which is pre-rooted) from Clockworkmod.

martian21 said:
Rooting stock is not required to install CM7.
You simply need to create a Clockworkmod recovery microSD card and you can then flash CM7 (which is pre-rooted) from Clockworkmod.
Click to expand...
Click to collapse
Thanks. I figured this would be relatively easy compared to rooting and putting CM7 on my EVO but reading on here there seemed to be a few different approaches. Will that method allow me to flash CM7 to the eMMC, and after that point will I no longer need the SD card to boot? I ask because I don't have a card on hand and am considering backing up the contents from my phone's card and using that.

xdp said:
Thanks. I figured this would be relatively easy compared to rooting and putting CM7 on my EVO but reading on here there seemed to be a few different approaches. Will that method allow me to flash CM7 to the eMMC, and after that point will I no longer need the SD card to boot? I ask because I don't have a card on hand and am considering backing up the contents from my phone's card and using that.
Click to expand...
Click to collapse
Correct.
You only need the SD to install a bootable CWM then you can flash CM7 from that. After words when CM7 is installed to eMMC you are able to use Rom Manager to install CWM to eMMC as well, so everything will be set up on the device's internal memory. SD is needed only for the initial boot of CWM to install CM7.

Nburnes said:
Correct.
You only need the SD to install a bootable CWM then you can flash CM7 from that. After words when CM7 is installed to eMMC you are able to use Rom Manager to install CWM to eMMC as well, so everything will be set up on the device's internal memory. SD is needed only for the initial boot of CWM to install CM7.
Click to expand...
Click to collapse
Thanks. From reading around it seems you can't use a phone or the Nook to mount the card and write the image, so I'll have to buy a reader and might as well get a card for the Nook at the same time. Since I'll be flashing CM7 to eMMC does it really matter if I get a class 4 or above card like many suggest? I'm not sure what's in my EVO but that is my benchmark. Class 2 seems to be what comes up in searches the most.

The general consensus it's to stick with Sandisk SD cards for the Nook. There are others that work as well but Sandisk it's pretty much a guarantee of zero issues. You can usually score an 8 GB class 4 Sandisk at Wal-mart for a Jackson.
Sent from my NookColor using XDA App

martian21 said:
The general consensus it's to stick with Sandisk SD cards for the Nook. There are others that work as well but Sandisk it's pretty much a guarantee of zero issues. You can usually score an 8 GB class 4 Sandisk at Wal-mart for a Jackson.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
Transcend 8 GBs have worked beautifully on all 3 NC's in my house.

xdp said:
I just got my Nook Color and am looking into how to go about rooting it for CM7. I checked out CM's Wiki page on it here and it mentioned using uNooter. I haven't read about this tool anywhere else and Google searches for it turn up practically nothing. Is this not the right tool to use? The forums mostly seem to mention ManualNooter, Auto-Nooter, etc. Also is it possible to flash CM7 on the internal memory and avoid using an SD card altogether?
Click to expand...
Click to collapse
I was the one that put together uNooter after being contacted by the individual that maintains the CyanogenMod wiki. They wanted a universal Nooter that would only root the device, install Superuser, ADB, RomManger, and work on all versions of the NC software. They asked that it be called uNooter. It is not released anywhere else, so that is why you did not see any mention of it on a Google search.

martian21 said:
The general consensus it's to stick with Sandisk SD cards for the Nook. There are others that work as well but Sandisk it's pretty much a guarantee of zero issues. You can usually score an 8 GB class 4 Sandisk at Wal-mart for a Jackson.
Click to expand...
Click to collapse
That information is really only relevant to running a ROM from the SD card. If you're only using the card for storage, or to get CM7 on eMMC, manufacturer and card class don't matter.
xdp said:
Thanks. From reading around it seems you can't use a phone or the Nook to mount the card and write the image, so I'll have to buy a reader and might as well get a card for the Nook at the same time. Since I'll be flashing CM7 to eMMC does it really matter if I get a class 4 or above card like many suggest? I'm not sure what's in my EVO but that is my benchmark. Class 2 seems to be what comes up in searches the most.
Click to expand...
Click to collapse
I wrote my image over USB to a card in the NC without a card reader. I've seen wiki guides saying there's a greater chance of the write getting interrupted, rendering the card unusable at least in the short term, but it worked for me. It was only when I wanted to revert the card to storage that I ended up needing a card reader. The links in my sig have a little more info about using the NC as your card reader, but you're probably better off just grabbing one.
Also, while CM7 does not require an SD card, many apps do. Your experience will be somewhat limited without one.

GMPOWER said:
I was the one that put together uNooter after being contacted by the individual that maintains the CyanogenMod wiki. They wanted a universal Nooter that would only root the device, install Superuser, ADB, RomManger, and work on all versions of the NC software. They asked that it be called uNooter. It is not released anywhere else, so that is why you did not see any mention of it on a Google search.
Click to expand...
Click to collapse
Great to hear directly from the source, thanks! I'm surprised more people don't point to your tool on the forums given that it's right on the CM Wiki. At this point I'm a little confused about the various approaches to do this. Does your tool install ROM Manager directly into the stock Nook interface, and then I flash from there, versus booting CWM off the SD as people mentioned earlier in the thread? Sorry if that's completely off-base.
Taosaur said:
That information is really only relevant to running a ROM from the SD card. If you're only using the card for storage, or to get CM7 on eMMC, manufacturer and card class don't matter.
I wrote my image over USB to a card in the NC without a card reader. I've seen wiki guides saying there's a greater chance of the write getting interrupted, rendering the card unusable at least in the short term, but it worked for me. It was only when I wanted to revert the card to storage that I ended up needing a card reader. The links in my sig have a little more info about using the NC as your card reader, but you're probably better off just grabbing one.
Also, while CM7 does not require an SD card, many apps do. Your experience will be somewhat limited without one.
Click to expand...
Click to collapse
Yeah, I thought about this as well and figured I'd want a full-time card for the device so I ordered a card with SD adapter. I figured the specs didn't matter at all for a data card but picked up a class 4 Sandisk anyway.

xdp said:
Great to hear directly from the source, thanks! I'm surprised more people don't point to your tool on the forums given that it's right on the CM Wiki. At this point I'm a little confused about the various approaches to do this. Does your tool install ROM Manager directly into the stock Nook interface, and then I flash from there, versus booting CWM off the SD as people mentioned earlier in the thread? Sorry if that's completely off-base.
Click to expand...
Click to collapse
I received notice this past Monday that the cleaned up version of the CyanogenMod wiki was online, so not a whole lot of exposure for people to talk about it. I believe the old wiki had listed the different Auto-Nooter and Manual-Nooter that went with each software version, thus taking up a lot of space and confusion. AN and MN are more tailored to people that want to stick with the stock software, but enable full Android Market access. People that want to go from stock to CyanogenMod don’t need all the extra software that is bundled with AN and MN just to be able to flash CyanogenMod. By eliminating all the version specific software I was able to create a version that would work on all current, and hopefully future, software versions.
Yes, my versions will install Rom Manager directly into the interface. You would then allow Rom Manger to install CWM Recovery, and then you can download and install CyanogenMod from the device. You could also take a full backup of your current stock rom. Using uNooter or bootable CWM will both get you to where you want to go, it is really up to you on how you want to get there.

Instructions for installing CM7 to the eMMC using CWM on a SD card (which can later be reformatted for storage) is in this thread: http://forum.xda-developers.com/showthread.php?t=1030227.

GMPOWER and bigbob23: Thanks for the info, that was exactly what I needed to clear everything up. I suppose backing up the stock ROM would be useful in case I ever needed to restore it for warranty purposes or anything. I'm not sure which approach I'll go with, my SD card came today so I'll be reading over both techniques and giving one a shot!
Thanks again.

I went through the process with uNooter as outlined on the CM Wiki and it went perfectly. The only thing was I had to use SD Formatter and the earliest 0.1 version of Win32 Disk Imager to get the image to write to the SD card. Not sure if that problem is specific to Win7 64-bit but maybe I can mention it on the wiki.

xdp said:
I went through the process with uNooter as outlined on the CM Wiki and it went perfectly. The only thing was I had to use SD Formatter and the earliest 0.1 version of Win32 Disk Imager to get the image to write to the SD card. Not sure if that problem is specific to Win7 64-bit but maybe I can mention it on the wiki.
Click to expand...
Click to collapse
I am glad that you got everything to work right. I think the problems that you might have experienced are more associated with win7 x64. My replacement laptop with win7 x64 will not be here for another two weeks for me to test it on, but in the past I have had to use Unlocker almost every time to unlock the usb drive before I could proceed with flashing using Win32 disk imager. On my current windows 7 x86 setup, I have yet had to use Unlocker to be able to flash an image with the win32 program. HERE is a post with people having problems in the past with win32 disk imager on win7 x64, they took the same path that you did with Panasonic SD Card Formatter to fix it.

uNooter
I guess this worked for the latest firmware of 1.2.0? (I am about to root one soon!) thanks in advance!)

AF9210 said:
I guess this worked for the latest firmware of 1.2.0? (I am about to root one soon!) thanks in advance!)
Click to expand...
Click to collapse
I just got my nook last week so I'm assuming I had the latest factory firmware when rooting, but I didn't check.

xdp said:
I just got my nook last week so I'm assuming I had the latest factory firmware when rooting, but I didn't check.
Click to expand...
Click to collapse
If you see "Read Forever" when booting (stock) then "Yes" you have the latest firmware.

ADB after uNooter?
Above, GMPOWER mentioned ADB as one of the items uNooter installed. I've rooted with uNooter in part because *nothing* *else* I could find would actually boot on my NC and in part because I liked the idea of a relatively minimal root. I figured I could then push any apk's I wanted to add with adb.
Unfortunately, that doesn't seem to be working. I used "NookColor Tools -> All Settings -> Development" to enable USB debugging, but 'adb devices' shows nothing. If I plug in my G2 with CM7, adb finds it just fine, so I'm pretty sure I've got the computer side of things working. Any hints about getting the NC to play nice?

[Q] Rebooting issue (Nook HD+, CM10 build from 1/19 from verygreen)

Hey all,
I got a Nook HD+ a few days ago and started doing some of the things listed here on the forums. One of the issues that myself and others have in the Android Development forum (which, because I am a new user, I cannot post to) is that the ROM will randomly reboot. The file /proc/last_kmsg was requested, so I'm posting it here in the hopes that it helps track down the issue (attached).
The best I can tell from that is that it seems to be freaking out about an I/O error and then losing track of the filesystem.
The SD card I'm using is the SanDisk Ultra 32GB Class 10 card.
Let me know if I need to add any other information.

GameSageZB said:
Hey all,
I got a Nook HD+ a few days ago and started doing some of the things listed here on the forums. One of the issues that myself and others have in the Android Development forum (which, because I am a new user, I cannot post to) is that the ROM will randomly reboot. The file /proc/last_kmsg was requested, so I'm posting it here in the hopes that it helps track down the issue (attached).
The best I can tell from that is that it seems to be freaking out about an I/O error and then losing track of the filesystem.
The SD card I'm using is the SanDisk Ultra 32GB Class 10 card.
Let me know if I need to add any other information.
Click to expand...
Click to collapse
That is good info. I will pass on to that thread.
Sent with XDA Premium from my Nook HD+ running CM10 on SD

GameSageZB said:
The SD card I'm using is the SanDisk Ultra 32GB Class 10 card.
Click to expand...
Click to collapse
Thanks for the report.
Unfortunately this is kind of a known problem, which is Sandisk class 10 cards (U1 really I think?) do not work stably, I have one myself that's like this. (actually they are hit and miss, works great for some, does not work for others including myself).
Class4 is what bullet proof.
I get these io errors on my U1 sandisk card even in stock, seems to be something hw-related.

GameSageZB said:
The file /proc/last_kmsg was requested, so I'm posting it here in the hopes that it helps track down the issue (attached).
The best I can tell from that is that it seems to be freaking out about an I/O error and then losing track of the filesystem.
Let me know if I need to add any other information.
Click to expand...
Click to collapse
Apparently I got the same issue. However mine occurs usually after device wake up. It reboots to stock.
Got 64gb Sandisk class 10 ultra, cm10 build 20130108.
Checked kmsg file did not find any io errors..

verygreen said:
Thanks for the report.
Unfortunately this is kind of a known problem, which is Sandisk class 10 cards (U1 really I think?) do not work stably, I have one myself that's like this. (actually they are hit and miss, works great for some, does not work for others including myself).
Class4 is what bullet proof.
I get these io errors on my U1 sandisk card even in stock, seems to be something hw-related.
Click to expand...
Click to collapse
Hello verygreen, I have a sandisk micro-sd same as yours (IIRC) and what I did was to replace it with another. The newer sandisk u1 that I got doesn't throw any I/O errors but still occassionally reboots with all your kernels except than with the 12/31 one (even though I haven't checked it as extensively as the others).
So what's with that? Do you think the instability isssues we're encountering are at least partly due to the kernel?

Stevethegreat said:
Hello verygreen, I have a sandisk micro-sd same as yours (IIRC) and what I did was to replace it with another. The newer sandisk u1 that I got doesn't throw any I/O errors but still occassionally reboots with all your kernels except than with the 12/31 one (even though I haven't checked it as extensively as the others).
So what's with that? Do you think the instability isssues we're encountering are at least partly due to the kernel?
Click to expand...
Click to collapse
What SD card image do you use with that? Is it version 4 or 3? I want to give it a try as well

greenya said:
What SD card image do you use with that? Is it version 4 or 3? I want to give it a try as well
Click to expand...
Click to collapse
Ver 4

verygreen said:
Thanks for the report.
Unfortunately this is kind of a known problem, which is Sandisk class 10 cards (U1 really I think?) do not work stably, I have one myself that's like this. (actually they are hit and miss, works great for some, does not work for others including myself).
Class4 is what bullet proof.
I get these io errors on my U1 sandisk card even in stock, seems to be something hw-related.
Click to expand...
Click to collapse
Thanks for responding. I'll look into getting a different SD card. I mainly got this one because it was on sale at Best-Buy and with the ~30 minutes of research (I really, really wanted to do some toying with my Nook that night), seemed to be the best one.
I'll also take a look at the "working SD card" thread and respond if I have any extra info.

Hi, I might have found a reason why HD+ reboots when using CM10.
The reason is WiFi (or its driver),
when WiFi goes to sleep it sometimes cannot reactivate the driver, well Android tries to load this driver, but fails for some reason and this results in kernel panic.
So workaroud for it is to disable WiFi sleep in Wifi advanced settings (make it always on or something), and turn off manually if needed.
However after the tablet wakes up there is a chance it still fails to load a driver and fail miserably when you try to activate WiFi manually.
But until wifi is off, it will not reboot.
I am using:
-0108 build of CM10
-sd boot image ver 3
-SanDisk 64gb class-10 (UHS1)
This has nothing to do with sd card though, cause people with Class 4 getting reboots as well.
I think removing Wifi driver from CM10 kernel and re-building it from the stable source should fix this problem. Sorry don't have kmsg logs, will attach later.
p.s cannot post to dev, so posting here.
Thanks!

SD Card Install Setup
I'm trying to get CM10 on my Nook HD+. I downloaded and installed the img file (#3) fine and put in in the Nook and CWM came up and followed the instruction for the install. 16 gig Sandisk class 4. It created the 4 partitions. I then poped out the card and put it in my Windows machine. The boot partition came up with 100+ meg and couldn't see the other partition unless I used the Partition software. In the notes it says to copy the cm*.zip into the SD10CARD partition..I CAN'T SEE IT IN WINDOWS? I tried to install Andriod tool kit (adb) with no luck.. Says it can't find the Android devices.... Would this work any better with Apple or Ubunto. Ideas?

Rpimcguirk said:
I'm trying to get CM10 on my Nook HD+. I downloaded and installed the img file (#3) fine and put in in the Nook and CWM came up and followed the instruction for the install. 16 gig Sandisk class 4. It created the 4 partitions. I then poped out the card and put it in my Windows machine. The boot partition came up with 100+ meg and couldn't see the other partition unless I used the Partition software. In the notes it says to copy the cm*.zip into the SD10CARD partition..I CAN'T SEE IT IN WINDOWS? I tried to install Andriod tool kit (adb) with no luck.. Says it can't find the Android devices.... Would this work any better with Apple or Ubunto. Ideas?
Click to expand...
Click to collapse
Yup, a Windows limitation. You can use mini-tools partition app for windows to see them, or better yet, Ubuntu, which will identify all partitions and allow you to transfer zips to the CM10SDCARD partition.
---------- Post added at 05:25 PM ---------- Previous post was at 05:23 PM ----------
greenya said:
Hi, I might have found a reason why HD+ reboots when using CM10.
The reason is WiFi (or its driver),
when WiFi goes to sleep it sometimes cannot reactivate the driver, well Android tries to load this driver, but fails for some reason and this results in kernel panic.
So workaroud for it is to disable WiFi sleep in Wifi advanced settings (make it always on or something), and turn off manually if needed.
However after the tablet wakes up there is a chance it still fails to load a driver and fail miserably when you try to activate WiFi manually.
But until wifi is off, it will not reboot.
I am using:
-0108 build of CM10
-sd boot image ver 3
-SanDisk 64gb class-10 (UHS1)
This has nothing to do with sd card though, cause people with Class 4 getting reboots as well.
I think removing Wifi driver from CM10 kernel and re-building it from the stable source should fix this problem. Sorry don't have kmsg logs, will attach later.
p.s cannot post to dev, so posting here.
Thanks!
Click to expand...
Click to collapse
Hope you're onto something. I will copy this to dev thread

RustedRoot said:
Yup, a Windows limitation. You can use mini-tools partition app for windows to see them, or better yet, Ubuntu, which will identify all partitions and allow you to transfer zips to the CM10SDCARD partition.
---------- Post added at 05:25 PM ---------- Previous post was at 05:23 PM ----------
Hope you're onto something. I will copy this to dev thread
Click to expand...
Click to collapse
I actually just registered to make this same observation. I'll keep tracking on my own nook, but wanted to add my experience as well. Nook HD+' sandisk ultra 16gb uhs1. Used cwm early 3 and 12/31/12 build. Takes three or four reboots to get back in after crash.
Thanks!
Replied to wrong post... was supposed to be the post about the WiFi... sorry for confusion...

Rpimcguirk said:
I'm trying to get CM10 on my Nook HD+. I downloaded and installed the img file (#3) fine and put in in the Nook and CWM came up and followed the instruction for the install. 16 gig Sandisk class 4. It created the 4 partitions. I then poped out the card and put it in my Windows machine. The boot partition came up with 100+ meg and couldn't see the other partition unless I used the Partition software. In the notes it says to copy the cm*.zip into the SD10CARD partition..I CAN'T SEE IT IN WINDOWS? I tried to install Andriod tool kit (adb) with no luck.. Says it can't find the Android devices.... Would this work any better with Apple or Ubunto. Ideas?
Click to expand...
Click to collapse
No no no. For copying CM10 zip to SD you must do it over adb and your nook connected to PC (win, mac, linux). I seen that many guides here lacks this info and this confuse users. Basically you do it this way:
Make SD card for CWM
Boot up you nook to cwm
On cwm mount SD card
Attach with usb cable nook to pc
Copy CM10 zip to sd (look to command example). You can copy additional zips on this step too (GAPPS or other needed stuff) After copy you can remove cable
Reboot command on CWM
You Boot to fresh CWM

[Q] SD Install has bricked my HD+

I have an issue that seems to be similar to those suffered by a number of people. I'm just having difficulty understanding the cause of it, and the solution. I have a nook hd+ that no longer boots as a result of trying CM11 on an SD card.
I installed CM11 to an SD card (as I was nervous of altering my nook) using bokbokan's excellent instructions. Initially it seemed fine but this morning it was unexpectedly out of battery and will no longer boot.
The symptoms are similar to this: http://forum.xda-developers.com/showthread.php?t=2611769, this: http://forum.xda-developers.com/showthread.php?t=2736347 and this: http://forum.xda-developers.com/showthread.php?t=2649061&page=2 except that the posters there had previously replaced the stock software and overwritten the emmc.
When the SD is in, it locks up on the Cyanoboot screen, when the SD card is out I only get to the black screen with 'Nook' on it and no further. It looks like the SD install has messed something up on the internal emmc. Hard resets and multiple failed boots don't appear to help.
I can occasionally (but not always) get it to reboot to CWM recovery by reinserting the card and holding down N and lock, but I get a lot of errors such as "E:Can't open /cache/recovery/last_log", "W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache failed:No such file or directory" and "I:Can't partition non-vfat: /emmc (ext4)". When I go to 'Mounts and Storage' in CWM, I cannot mount anything (e.g. "Error mounting /boot!").
I chose to go down the SD card install route (using ) in order to avoid touching the stock install on the emmc, but now the whole thing is dead.
Reading other threads, it sounds like either:
1. The emmc is bricked due to some firmware bug. The impression I get from reading around is that CM11 was supposed to incorporate a workaround for the issue. If the emmc is the problem, I have to return the Nook and hope to get a working one.
2. The emmc has (somehow) become corrupted, I have to put a different version of CWM on my SDcard (so it will install to the EMMC rather than the SDcard, and because CM11 uses a different version), using the instructions here: http://forum.xda-developers.com/showthread.php?p=35811322 and then reinstall a stock rom to my emmc. I then have to reregister the Nook (not sure if this is essential) before being able to use my CM11 SDcard install again.
If it is the first problem, I would like to know how I can check to see if the emmc is indeed broken.
If it is the second, I would be grateful for any help in understanding how and why the SD install has messed up the emmc, and whether the steps above are likely to bring it back to life.

It sounds like your emmc is indeed bricked. I would go for the warranty exchange now. Just because you installed CM11 to SD does not mean it does not use emmc partitions. It still accesses and uses many of them (cache, rom, bootdata, /data/media, etc.). So there is opportunity for a brick. I would exchange it now while the cyanoboot logo does not show when booting without the SD.
Sent from my BN NookHD+ using XDA Premium HD app

Mf123 said:
I would like to know how I can check to see if the emmc is indeed broken.
Click to expand...
Click to collapse
You may find links and info in this post helpful http://forum.xda-developers.com/showthread.php?p=44810400

Thanks to both for replying. I feared that was the case.
I'm a bit disappointed that the SD card install (generally the option for those who want to leave the nook untouched) can in fact ruin the machine.
I've contacted the Nook website and will see what happens.

Mf123 said:
Thanks to both for replying. I feared that was the case.
I'm a bit disappointed that the SD card install (generally the option for those who want to leave the nook untouched) can in fact ruin the machine.
I've contacted the Nook website and will see what happens.
Click to expand...
Click to collapse
Just take your device to a store. They will exchange on the spot once they verify your registration on their computer. Of course don't tell them you were running CM, even on SD.
Sent from my BN NookHD+ using XDA Premium HD app

leapinlar said:
Just take your device to a store. They will exchange on the spot once they verify your registration on their computer. Of course don't tell them you were running CM, even on SD.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but there are no BN stores in the UK. They don't even sell the Nook directly from their uk website anymore. I have to post it to the Netherlands and see what happens.

So, after 2 months, and a lot of arguing with customer services, I have finally got a replacement Nook through the post.
I am still keen to try CM, but want to be really sure that my Nook doesn't get bricked again. Is there any way of checking whether an sd card install is likely to trigger an emmc failure on my new Nook?

Mf123 said:
So, after 2 months, and a lot of arguing with customer services, I have finally got a replacement Nook through the post.
I am still keen to try CM, but want to be really sure that my Nook doesn't get bricked again. Is there any way of checking whether an sd card install is likely to trigger an emmc failure on my new Nook?
Click to expand...
Click to collapse
The best way to avoid bricking by CM11 is to not try CM11. I run CM 10.1.3 and have heard of no one bricking when running that.
Sent from my BN NookHD+ using XDA Premium HD app