Database Users

[Q] NookColor does not boot from SDcard

Hi,
I've ran into a snag that I can't seem to figure out, my nookcolor boots normally but does not boot from uSD. In the past I've always been able to find answers by searching but this time, nothing I've tried has worked. I've been using phiremod on the nook for quite a while and recently updated to v6.1.
The first time I rooted the NC, I used a uSD with autonooter 3.0 and everything worked great. Flashed to phiremod 5.2 and have been using CWR off of the emmc to update versions.
Today, I decided to try a new rom and wanted to start fresh with a stock 1.1. I popped in the CWR sdcard I had from a while back and it didn't work, the NC boots normally in to phiremod.
After remaking a bootable CWR sdcard several times and failing, I thought it might be a corrupted boot partition. So I successfully reimaged the boot and system partitions via ADB and I was back to stock. I thought I was good to go except what I've got now is a stock NC that does not boot from the uSD.
I've tried 3 different perfectly good uSDcards with autonooter, monster's rootpack, CWR sdcards, nookie-froyo sdcards... nothing works. Failbooting 8 times causes the NC to reupdate itself to 1.1.
Has anybody encountered this before or some devs can shed some light why it does not boot from uSD? Any help is appreciated.
Edit: N+power causes the NC to do a Factory Reset. Done this twice already.
TC

This might work....
Look, I'm no expert at uSD's, but try this. Maybe your Nook thinks the sd card is an emmc partition. Try holding down the home button while booting? Like, hold the button and then power on. I hope it works for you. I know the pain as I have had many issues, too.

tuoc65 said:
Hi,
I've ran into a snag that I can't seem to figure out, my nookcolor boots normally but does not boot from uSD. In the past I've always been able to find answers by searching but this time, nothing I've tried has worked. I've been using phiremod on the nook for quite a while and recently updated to v6.1.
The first time I rooted the NC, I used a uSD with autonooter 3.0 and everything worked great. Flashed to phiremod 5.2 and have been using CWR off of the emmc to update versions.
Today, I decided to try a new rom and wanted to start fresh with a stock 1.1. I popped in the CWR sdcard I had from a while back and it didn't work, the NC boots normally in to phiremod.
After remaking a bootable CWR sdcard several times and failing, I thought it might be a corrupted boot partition. So I successfully reimaged the boot and system partitions via ADB and I was back to stock. I thought I was good to go except what I've got now is a stock NC that does not boot from the uSD.
I've tried 3 different perfectly good uSDcards with autonooter, monster's rootpack, CWR sdcards, nookie-froyo sdcards... nothing works. Failbooting 8 times causes the NC to reupdate itself to 1.1.
Has anybody encountered this before or some devs can shed some light why it does not boot from uSD? Any help is appreciated.
Edit: N+power causes the NC to do a Factory Reset. Done this twice already.
TC
Click to expand...
Click to collapse
My guess is the SD Card is not mounted, try going into the settings and make sure the card is mounted. You may want to unmount it, and then format it. Then unmount it, remove it and then reinstall cwr onto the sd card again. If that doesn't work, try another sdcard. If that doesn't work it could be a hardware issue... it could also be an issue with your card reader, they have been known to break at inopportune times, try a different card reader.
migrax

card reader
migrax said:
My guess is the SD Card is not mounted, try going into the settings and make sure the card is mounted. You may want to unmount it, and then format it. Then unmount it, remove it and then reinstall cwr onto the sd card again. If that doesn't work, try another sdcard. If that doesn't work it could be a hardware issue... it could also be an issue with your card reader, they have been known to break at inopportune times, try a different card reader.
migrax
Click to expand...
Click to collapse
+1 to the card reader issue. I have a perfect working cm7 build on my nook now, but it took some trial and error. The card reader on my computer looked like it was working fine, but when I would put the card into the nook it wouldn't boot to it. I finally did the same steps with the same card only this time using my phone (tp2) as the card reader plugged into my computer and it worked great.

It definitely was the card reader. Tried a different one and it booted just fine..
As a SDET by profession, it makes me sad I didn't think of this.
Thanks all.

Linux Issue
I know this is rather an old thread, but just in case someone has this problem and is running Linux (I'm running Ubuntu) here is what happened to me. After dd'ing the CWR image several times, I could not get the NC to boot to the sd card. I tried multiple cards and multiple readers, no joy. I thought perhaps something was wrong so I looked at the card in gparted. What I found there was that there was a 1mb of unallocated partition space before the CWR partition. I used gparted to move the partition to be at 0 position and it booted up like a charm.
Don't know if I was doing something wrong the command I used was
Code:
sudo dd if=2gb_clockwork-3.0.1.0.img of=/dev/sdd1 bs=1M
At any rate, if any other linux users run into this, that's how I fixed it.
Randy

rwreed said:
I know this is rather an old thread, but just in case someone has this problem and is running Linux (I'm running Ubuntu) here is what happened to me. After dd'ing the CWR image several times, I could not get the NC to boot to the sd card. I tried multiple cards and multiple readers, no joy. I thought perhaps something was wrong so I looked at the card in gparted. What I found there was that there was a 1mb of unallocated partition space before the CWR partition. I used gparted to move the partition to be at 0 position and it booted up like a charm.
Don't know if I was doing something wrong the command I used was
Code:
sudo dd if=2gb_clockwork-3.0.1.0.img of=/dev/sdd1 bs=1M
At any rate, if any other linux users run into this, that's how I fixed it.
Randy
Click to expand...
Click to collapse
Yeah, the problem is you put it on the first partition rather than the card itself. Note the instructions in the forum say device of card. ie: /dev/sdd

I also had an issue where I could create the SD card, and the Nook could see it, but it wouldn't boot from it. It turns out this was because I was using the internal card reader in my laptop to write the card. Once I switched to an external USB card reader, the Nook booted from the card just fine.

I've just come across the same problem.
I started two days ago with this: [ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard.
I liked ICS so much, I asked the developer how could I just stick with CM9?
He pointed me to this tutorial: Installing CM9 on Nook Color microSD.
It seems as though all the steps are going fine, up until step#10, where I am supposed to reboot INTO a freshly installed nightly.
I have Ubuntu 11.10 reliably running in VirtualBox. Plenty of memory and space.
I run GParted and view the partitions, and they are as expected.
I know Ubutu well enough to follow well-written directions.
The sdcard in my Nook is properly mounted - I think.
After reading this thread, I went to Amazing and bought a new SD card reader.
OH, and all this has been done on a new SD card, 8GB, class 4.
Hopefully it is due to an aging card reader. I'll get the new one in a couple of days and report back.
I really hope that's it!

OrganizedFellow said:
I've just come across the same problem.
I started two days ago with this: [ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard.
I liked ICS so much, I asked the developer how could I just stick with CM9?
He pointed me to this tutorial: Installing CM9 on Nook Color microSD.
It seems as though all the steps are going fine, up until step#10, where I am supposed to reboot INTO a freshly installed nightly.
I have Ubuntu 11.10 reliably running in VirtualBox. Plenty of memory and space.
I run GParted and view the partitions, and they are as expected.
I know Ubutu well enough to follow well-written directions.
The sdcard in my Nook is properly mounted - I think.
After reading this thread, I went to Amazing and bought a new SD card reader.
OH, and all this has been done on a new SD card, 8GB, class 4.
Hopefully it is due to an aging card reader. I'll get the new one in a couple of days and report back.
I really hope that's it!
Click to expand...
Click to collapse
Rather than a card reader, I use Kingston uSD usb stick adapters for my uSD card writing, and they've worked flawlessly. Just an option , if your new card reader doesn't solve your problem. The adapters were "dirt cheap".

brentb636 said:
Rather than a card reader, I use Kingston uSD usb stick adapters for my uSD card writing, and they've worked flawlessly. Just an option , if your new card reader doesn't solve your problem. The adapters were "dirt cheap".
Click to expand...
Click to collapse
Great idea.
They're small enough to carry worth me. Thanks.

[Q] Help pls: Nook booted from SD w/CM7 good 4 3 days then started to boot to stock

Ok, I've been reading the forum until my eyes are popping out. I can not find my situation. So please forgive but I've been searching.
Bought a NC for my daughter for the purpose of Rooting it using the SD method. I followed the routine install last Monday:
1. Using WinImage, I burned the Size-agnostic SD Card image on the SDcard (Transcend 8GB Class 6 SDHC) using my HTC Incredible as my card reader.
2. Downloaded cm_encore_full-131.zip and moved it to the card.
3. Installed the SD card and bam! Everything was working and I was happy as hell!
4. I went through the process and got gapps-gb-20110307-signed.zip installed and I was working away downloading apps and stuff.
5. Downloaded update-CM7-dalingrin-OC-sd-063011.zip and got that loaded and our NC was flying high. And since we have the right kernel, downloaded Nook Tweaks and we can use a case with a USB keyboard with no issues playing Angrybirds and everything. LOVING IT!
I was happy as hell cause I wanted to be done in my limited time before tomorrow because my daughter is staying with my mom and this will give her something to do.
THEN today after powering it off. I powered it back on again and the following happened:
1. It appears to attempt boot from the SD card.
2. The green Cyannogen logo comes up and under it it says "loading..."
3. However, instead of the Android on the surfboard coming up like before, it will boot up to the stock Android with the N splash screen first then to the stock interface???
I tried several times powering it on and off to see if it was just a glitch but it still did it. Soooo, I redid the whole process again. But once I tried to boot from the SD card with CM7 loaded, the same thing happens. Green logo, loading..., then back to the NC stock OS.
I tried downloading the image a few times to make sure it wasn't corrupt and reburned the img on the SD card, tried booting it again and still the same results. (I did this whole process at least 5 times!)
Sorry for the long read but I am frustrated and disappointed that i will have to tell my girl that it's not working like it was earlier. Can someone give me any advice to try? Or what can I possibly doing wrong? I'm beyond my skill sets at this point. The only thing that I can find on the forum is that it maybe the Transcend SD card but it worked find for three days. Can it really suck that bad after 3 days? I only have tomorrow to work it during the day so If I have to I'll go to Costco and get a Scandisk over there as some have mentioned, I will. But if there is something someone can tell me to try, please let me know.
Thanks in advance!

You are probably on the right track with getting a new SD card. One of two things happened: the SD card failed during the initial "burn-in" period or the Nook's reader slot did. The card is thebmore likely point of failure.
If the problem persists with a new card, get your Nook back to B&N for warranty replacement. Just don't let them have your SD cards an you won't lose all your work
P.S. Yes, ANYthing electronic can "suck that bad after just 3 days". If an electronic component is going to fail, it will either be DOA (and even cursory quality control will catch it) or it will fail shortly after being placed in regular service (burn-in). If it survives the first 60 to 100 hours of use, it will PROBABLY last for years.

Thanks DiDGR8!
I hear you on the electronic part. I was also really tired when I posted. I guess I just didn't want to believe that the card was the issue or rather could be the issue specially when I can read the card from my phone and read it from the NC in the stock interface. It had to be something I did or forgot to do. But I've seen stranger things happen. LOL Things can break.
As soon as I can, I will run out and get a new (Scandisk) card and I hope that it resolves the issue. I hope it is not the NC's reader slot because I hate going through the "returning process" plus we have to leave tonight.
I'll post my results as soon as I can today.

I often not to believe the uSD card itself is the problem but I guess this time, I believe it.
I have the same card as yours (Transcend 8GB class 6), testing random read/write small block and the result were about 0.08 (meaning bad). Sure enough, running CM7 off it last few days then I got ton of FC errors. I now then boot CM7 from eMMC and use the card as an external storage, the card still gives me some problems.
Try Sandisk and keep yours fingers crossed.

Well at least I'm not alone. Thanks votinh!
I wanted to avoid running it from eMMC so that if i wanted to I can do the warranty thing.
Well, I got me a Scandisk 4Gb Class 4 this morning in addition to a card reader/writer to eliminate my phone as a card reader.
Followed the steps and still the same thing. However, I did noticed this time some I/O errors come up during the installation process.
So, I let it go to stock so i can test my phoness SD card (Scandisk 2GB) and it worked just fine. So, I'm really stumped now.
I'm going to try flashing it again a couple of more times. I can go to B&N and tell them it is not working but if i show them it does work reading my phone's SD card. unless i just push them for an exchange.

OK, tried the the latest stable and now the Driod comes up and it is in a loop. I abandoned that all together. Need to stay focused.
So, I went through the process again using #133 on my Scandisk 4GB and tried to boot with it. Same results again Green logo, loading..., then back to the NC stock OS.
However, this time I was able to take a pic of the screen so I can copy what I saw when I saw I/O errors during the installation. So at one point I got:
end_request: I/O error, dev mmcblkl, sector, <insert number>: this flashed down the screen quite a bit
also
JB2: DetectedIO errors while flushing file data on mmcblk1p2-8
Ok so I went back to the Transcend card and did #132 but using my new reader. This time it seem to install clean. When I powered it back up, this time str8 to the "Read Forever" splash screen and back to stock. Weird.
So, I redid the 4GB card again and got the I/O errors again same thing the "Read Forever" splash screen and agian back to stock. It's like it's telling me to go F*** myself.
At this point, I'm thinking its the NC reader reading off the card itself. I tried 2 brand new cards, dif brand, dif reader/writers, multiple downloads of the img and installers...I don't know what to say. I should just root it to eMMC but if i'm having trouble with the SD method and I go eMMC and that messes up I won't be able to return it on Warrenty. What am I doing wrong? Can anyone give me anything else, I'm desperate and ready to fling it out the window. LOL

LOL I love the way I'm bumping my own thread here.
So, I went to B&N and got me a new replacement NC without any hassles.
I ran through the routine from scratch with CM7 #133 (which I believe has the OC kernel in it) on my new Scandisk 4GB Class 4 without the gapps.zip just to take it one step at a time.
I powered it on and prayed to the CM7 gods. I see the same I/O errors on the install and I also saw chown: cannot access '/tmp/backuptool.sh' : No such file or directory which I've seen before as well. However, this time the droid came up refreshing itself in a continuous loop. Like when I tried the stable version earlier. I did this twice and the same results.
At this point I'm thinking it maybe the WinImage. I'm using Winimage V 8.50? So, I downloaded Win32disk imager to give it a try and using my phone as the reader again because that was the last known combo. Again, the same errors. Then the Logo, loading…, this time blank screen…crickets…
I’m out of ideas…I had a clean install once on Monday worked fine until yesterday and I can’t do a damn thing.
Different SD cards, 2 brand new NCs, different readers, multiple downloads of image, installer, etc. Two dif imagers as well…Someone please tell me you are missing a step or doing something working because this does not make any sense… Booting in recovery mode maybe?

The only idea I have is a longshot. When you were getting the looping bootanimation (the blue Andy on a skateboard), or the "crickets"; how long did you wait before aborting the boot?
I have seen it take a LOT longer in those steps than I ever remembered (or thought reasonable). I'm talking 5 or 10 minutes.
It has something to do with recreating internal partitions and the dalvik cache (IIRC). It's been so long since I booted off the SD card, I'm not really sure what is supposed to happen that way.
Sorry that I can't offer more than "just let the first boot take all the time it wants".

It's all good. I understand.
So, Truth be told I think the first time with the "stable" image I let it go for 3 rotations before I said jumped ship. As I type now, I tried going back to #128 and it's doing it again. Andy has done skated across it at least 20 times...21... I'll let it run for a bit since you say that while I research the recovering to stock in emmc in case I decide to chuck it up and go emmc. This is driving me crazy. I would guess that emmc maybe more stable than running it from an SDcard.

You have got to be s***ing me. So I staied persistant and used my 8GB Transcend card again. This time it installed clean (I was taking pictures so I can read the damn thing) and booted clean. WEIRD!!!
I'm going to see if I can get my Scandisk to do the same.

I have seen mention that using the latest winimage is not a good idea, something about it not working right.
Version 8.1 is the usual recommendation.
I have been using the dualboot image racks11479 put together, and i've burned it with winimage a handful of times without issue, but always used winimage 8.1
Not sure if that's your issue, as i've never forayed into the realm of recent nightlies, but it could be a contributing factor.

Win32Disk Imager works perfect for me, even on win7 x64 and winimage would write, but the disk wouldn't boot.

[Q] Any hope for my SD Card?

Short story: Was running the latest (as of Dec. 4-5) ICS ROM(s) - the ones with the SD card bug - and my SD card appears to be shot.
Long story:
-----
I had been using the various betas of the ICS ROMs since I noticed Tytung's first Alpha was out and the ROMs had been improving rapidly. I guess when the headphones issue was fixed it caused problems with reading the SD Card which was documented and seems to be well known.
The constant SD messages didn't bother me much, but eventually I noticed launch icons missing and went to the Market to re-download one of the apps I use (I've been flashing so much, I wasn't sure which apps I didn't bother restoring). The Market app tells me I need a SD Card to install apps, so I just figured it's just the instability of the sd card mount for this latest batch of ROMs and I'll flash an older ROM off my SD card when I get the chance. I also noticed the messages started saying I inserted a blank SD Card but I brushed it off (couldn't look into it at the time).
I get home and find out Clockwork refuses to mount my card which means I can't easily wipe and install something else, so I switch to USB storage mode in CWM to simply transfer a ROM from my PC and my PC only sees ~30mb of my 16GB SD! I initially thought it was just some corruption but I tried all sorts of format and partitioning programs and nothing recognizes more than 30mb of space and none have even been able to format that little space that's showing.
I've been Googling for a while and came up with nothing I haven't already tried so I finally decided to post here. Is there any hope for my SD card? Being the holiday season and for once I've got most of my Christmas shopping done early, I'd rather not waste the little money I have left to run out and buy another SD card right away if it's not necessary.
-----
Does anyone have any ideas how I could fix this? I'd greatly appreciate it because I now stuck with WM6.5 and realize how much I didn't miss it for the past year
This is also a heads up for testers to be sure to upgrade their ROM ASAP (or at least to the kernel that fixes this) if they're on a ICS ROM with an SD card bug. I'm not complaining - I know this is a part of testing early builds (please ignore my sorry post count; I've been flashing for quite a while) - but there's no reason for others to go through this issue if it can be helped.

Have you tried EaseUS?
Sent from my LG-VM670 using Tapatalk

Yes,
Try Easus Partition Manager and/or MiniTool Partition Manager.
They can help but you will have to format your SD card I think.
Good luck!

I had the same problem. I plugged my card into a USB reader after it working error free, it then said it needed to be formatted and was only showing 30mb. After formatting repeatedly it still doesn't read. I haven't retired any positioning software but i think the card may just be done with.
Sent from my HD2 using XDA App

probably you'll need a replacement.
have you tried the SD formatter? there's like a 0.000001% chance it will work in your case, but why not try it?

Only for GURU's

I have a droind X running .605
for some reason i cannot access the internal memory
i originaly rooted with z4root on stock rom never did anything with it after that
i updted to .605 and wanted to install ubuntu but i cant seem to be able to access the internal memory. I did not uninstall z4root i simply upgraded 0ta .605 and figured this would unroot my phone and bring it back to stock ota .605. then tried to connect phone in pc charge pc sync and usb storage the only thing is see is my sd card 32 GB I tried mounting sd unmounting plugging phone without sd no go im out of ideas i even rerooted and reflashed still no go. anyone else have this problem and a solution. am i even supposed to see to drives i recall having two drives show up in the past. Anyone isntall backtrack or ubuntu on the droid x? any help is appreciated.

I don't believe the Droid X supports chroot, and booting Ubuntu from internal memory is impossible.
Sent from my DROIDX using Tapatalk

I can also confirm that chroot is not possible on the DX. I've spent a long time on this and was not able to get it to work. If you search around the DX forum you'll see a lot of other people saying the same thing.

[Q] stuck on rooting my NC 1.4.2

I have been trying to root my NC for some days now, and im getting to the point of shooting myself in the face.
i've rooted multiple phones before, i started out with my g1 a really long time ago, now i am trying to root my tablet and i cant get it to boot from the sd card into CWM, i have an 8gig hd micro sd, might it be my card or something? i formatted it, wrote the image onto the sd card and loaded everything in the exact same order that the instructions tell me to do, ive even tired other methods and none work. any help plz?
i just want to read my comic books!

neoxtian said:
I have been trying to root my NC for some days now, and im getting to the point of shooting myself in the face.
i've rooted multiple phones before, i started out with my g1 a really long time ago, now i am trying to root my tablet and i cant get it to boot from the sd card into CWM, i have an 8gig hd micro sd, might it be my card or something? i formatted it, wrote the image onto the sd card and loaded everything in the exact same order that the instructions tell me to do, ive even tired other methods and none work. any help plz?
i just want to read my comic books!
Click to expand...
Click to collapse
It could be how you are writing the image to the SD. You should be using win32diskimager if you are running Windows. And you should be running that program as administrator. Also sometimes it makes a difference whether you are using the card reader in your PC. Sometimes it is best to use a cheaper card reader to put it in the PC.
Sent from my NookColor running ICS and Tapatalk