Database Develop

[Q] Honeycomb not booting from SD card.[1.1.0 issue?]

I have a 16 GB class 4 Sandisk card.
I ran the following command and successfully wrote the img to my SD Card
[email protected]:~$ umount /dev/sdg
[email protected]:~$ sudo dd if=nookhoney04.img of=/dev/sdg bs=1M
Click to expand...
Click to collapse
The SD Card now has a system, boot, data, and sdcard partiton. So I assume it was finished. I also received a confirmation message stating that it successfully wrote 3.7 GB to the card.
All appears well, but when resetting the nook, it almost immediately boots into stock instead of the sd card.
Am I missing something, or is this a card issue?

it might be the card, class 4 is really slow for honeycomb

Would "really slow" cause it to entirely skip the boot.
People claim to have got it working with a class 2, even if it is slow, it should still boot...

I appologize for bumping this, but I would really like a more definitive answer than "slow".

MXIIA said:
I have a 16 GB class 4 Sandisk card.
I ran the following command and successfully wrote the img to my SD Card
The SD Card now has a system, boot, data, and sdcard partiton. So I assume it was finished. I also received a confirmation message stating that it successfully wrote 3.7 GB to the card.
All appears well, but when resetting the nook, it almost immediately boots into stock instead of the sd card.
Am I missing something, or is this a card issue?
Click to expand...
Click to collapse
If they're in that order then somethings wrong. It should be Boot,System,Data,sdcard. Also a slow card shouldn't cause the boot sequence to be skipped but there could just be a compatability issue with your card
I suggest trying again to see if it works (btw I never use the BS=1M but that shouldn't cause any problems)

They're in the orter of boot, system, data, sdcard.
I used the bs=1M when I wrote autonooter, I guess I'll try it without that parameter since that's the only thing I can change.
It's kind of odd that the SD card would not boot... I've booted onto this SD card before when testing Froyo and doing some Clockwork recovery.
There are no buttons I have to hold to force a boot?
I am powering it on via plugging it into my computer, though I have tried a hard power on.

This maybe a card issue. So far all 16Gb cards I installed Froyo/Honeycomb booted successfully as long as you do not repartition the card with default head/sec/cyl (must be 255/63/the rest).
However at this moment neither Froyo nor Honeycomb work on any 16Gb card I tried. It installs fine, and boots ok, but after the first reboot the data partition gets corrupted almost immediately, and remounts read-only. If you eject the card, connect it to a Linux machine and run fsck.ext3 on /dev/sd?3 it will fix it, but it will be broken again during next reboot. Same images/files work fine on the same Nook on a 8Gb card.

No need to unmount the card. And normally your sd card is mmcblk0 or mmcblk1? Format your card, insert it into your computers sd card reader and in a terminal type "sudo fdisk -l" look for the device that is the same size as your card. Also, did you use your nook as the card reader for the computer? Most of the time, using the nook as your card reader when writing images doesnt work, you have to use the computers reader directly.
edit: Possible compatibility issues. 16gb's seem to have problems with corrupted partitions when writing sd images.

Hmm, that's interesting, is there any way to change the cyl-dead-sector data on linux?
If not, I guess I'll buy an 8GB class 6+ soon.
http://www.amazon.com/Transcend-microSDHC-Class-Memory-TS8GUSDHC6E/dp/B0026L7DG0
Would that card suffice?

Yes, that card seems to get really nice reviews as far as running HC goes. That or a Sandisk.

Well that card is under $20 dollars, so it works perfectly for me. Thank you for your feedback

I bought A-Data 8Gb class 10 microSD in Fry's, and it seem to work very well. $13.
Not sure how long it gonna last, but if it lasts a year, good enough for me.
The issue I mentioned, however, is not due to the card quality. 'badblocks' utility consistently showed all those cards having NO bad blocks, and I tested at least three different 16GB cards - Wintec, Patriot and A-Data.

RileyGrant said:
Yes, that card seems to get really nice reviews as far as running HC goes. That or a Sandisk.
Click to expand...
Click to collapse
Well, the card came in.... and no luck, same thing... I'm going to try it on Windows instead of Linux, see if that changes anything...

After I "upgraded" to 1.1.0 it jacked up my ability to boot from external SD card. Lots of random process failures and can no longer read my class 10 card at all. Going to revert to 1.0.1 I think... or else flash a CFW on instead. Seems like they added something nasty to the update.

Just to give some newcomers my experiences with the following two cards:
Lexar Class 10 32GB:
Stuck forever at the black screen with the message "android_" at the lower left. Tried both v3 and v4 of the honeycomb SD image. Neither worked.
Transcend Class 6 16GB:
Tried v4. Same pronlem as the Lexar. Stuck forever at the "android_" screen. Switched to v3. Bingo, it booted!
I should be receiving a Patriots 16GB tomorrow and will put it to test.

xdadidida said:
After I "upgraded" to 1.1.0 it jacked up my ability to boot from external SD card. Lots of random process failures and can no longer read my class 10 card at all. Going to revert to 1.0.1 I think... or else flash a CFW on instead. Seems like they added something nasty to the update.
Click to expand...
Click to collapse
Hmmm... that seems interesting... can anyone else confirm this?

I have two SD cards. One gives me the infamous encrypted file system error and the other just sits there looping on the android splash screen. Before updating, both ran honeycomb fine (CL4 and CL10).

[Q] Stuck at blue android_ booting froyo 0.6.8 from SD

I just got my "new" nook and tried to boot Froyo 0.6.8 from an SD card. It just gets stuck at the blue ANDROID_ screen. I tried Froyo 0.6.7 and redoing 0.6.8 but it never got past ANDROID_. I'm using a new Transcend 4GB class 6 card. I first tried writing it using WinImage and my laptop's built in card reader, but when that card didn't boot I tried using a USB card reader and Win32diskimager. The Nook came with 1.1 on it and I haven't done anything to the internal rom.
Any ideas? How long should it stay on the Android_ screen if its working?

Did you figure this out?

This sounds like the classic failure described with 16GB cards on multiple threads. There's a nice consolidated thread on cards that are known to work. I'd check that. I have froyo working beuatifully on an 8Gb class6 transcend card.
Most likely you have some glitch on the card. I would do a complete deep wipe of the card (e.g. using SDformatter, all options). Then reflash with win32diskimager, then expand the SDcard partition with EASUS
it should boot in a couple of minutes tops the first time round.

I looked at those threads about cards before I bought one and the Transcend 4gb, class 6 I got is one that seemed to work.
I haven't been able to get the nook to boot off any card. I tried doing the format suggested and tried another 1gb PNY card with the bootable clockwork. I've tried writing with the internal SD writer in my laptop and with a Kodak (sakar) usb writer and with Win32DiskImager and WinImage.
I suppose the USB writer I have might not be good, but I don't want to get another one without knowing its one that works. So far I don't know whether the problem is with the cards I'm writing or for some reason this nook won't boot off SD card.
Thanks for the suggestions.

I probably had a flaky 4gb card. Now it won't format or write whatever I do.

dumb Q, but is the 1gb card you ahve also flaky now too... in which case it might well be the reader?
Will your nook stock OS read the SD card? (e.g. throw some photos ont here and see if the nook will show them) that way eliminate the nook.
There's some older threads that suggest first formatting the SD card with the nook stock OS, but I've never needed to do that.
I'd persevere - there's definately some plusses of froyo over the rooted B&N (especially if you use adhoc networks a lot), and you absolutely need nookie froyo as a backup incase you fry something when you take the plunge to CM7 (which is phenomenal, despite being so early in its release)

The 1gb I borrowed seems ok. I managed to boot a card with a bootable clockwork on it. I didn't do anything to Nook stock OS yet. I want to be clear that I can recover if I do first. I did get another reader, but I think it was probably the card. I wasn't able to boot of the 1gb at first because I was making a mistake in unzipping the .tar.gz files.
Do you have any pointers of where to find out about how to use Clockwork recovery?

I am using 0.6.7 on a 8gb class 6 Transcend... it's working great, no issues with booting.

[Q] SD won't boot

I want to root my Nook 1.1.0 but it looks like it doesn't boot from SD card.
I tried couple SDs (2Gb and 4Gb) and burn them with couple images for Autonooter 3 (and 2 too as act of desperation).
I can see files on the SDs in Windows and in Nook.
I power off Nook completely with SD inside and plug it into the PC usb.
It supposed to run some script... I waited an hour and nothing happen.
Then Nook boots in regular Nook mode.
I assume that it's something with my SDs.
4Gb is class 4 SD. I burned it with different burner programs - result is the same.
Is there some way to determine that Nook boots from SD?
Maybe MBR is erased or something like this?
I formatted card in Windows and never did it in Nook.
So, I hope MBR (is it even used?) is OK but I want to be sure somehow.
Any suggestions?

What software are you using to burn the image onto the sd card?
You should be using winimage running in administrator mode.

akizub said:
I want to root my Nook 1.1.0 but it looks like it doesn't boot from SD card.
I tried couple SDs (2Gb and 4Gb) and burn them with couple images for Autonooter 3 (and 2 too as act of desperation).
I can see files on the SDs in Windows and in Nook.
I power off Nook completely with SD inside and plug it into the PC usb.
It supposed to run some script... I waited an hour and nothing happen.
Then Nook boots in regular Nook mode.
I assume that it's something with my SDs.
4Gb is class 4 SD. I burned it with different burner programs - result is the same.
Is there some way to determine that Nook boots from SD?
Maybe MBR is erased or something like this?
I formatted card in Windows and never did it in Nook.
So, I hope MBR (is it even used?) is OK but I want to be sure somehow.
Any suggestions?
Click to expand...
Click to collapse
Um you say the nook didn't do anything and then booted normally..... that sounds like it did everything right. Autonooter dose not show anything on the screen when you boot from it. you will get a blank screen for a bit and then it will boot to normal..... Have you checked to see if your nook is rooted?

I used winimage. I can see files in Windows and Nook.
Funny thing is that *.img file is so big but real files on SD are small.
I assume it's empty space what is in img file.

therealguppy said:
Have you checked to see if your nook is rooted?
Click to expand...
Click to collapse
I assume it should show some Android stuff. Correct?
What I see is regular Nook screens.

therealguppy has a point. You may be rooted and not know it yet. Go into the apps drawer and look for the super user app. If it's there, you're rooted. Autonooter doesn't change your launcher or anything else so obvious.

woot1524 said:
Go into the apps drawer and look for the super user app.
Click to expand...
Click to collapse
You mean EXTRAS?
There is nothing new here. 8 apps from Chess to Sudoku.
No super user app.

hmmmm... that is strange. As unlikely as you may think it would be, you must have goofed up a step. The nook color is, by way of hardware, hard-coded to boot to the Micro SD-card if a bootable partition exists.
It's crazy unlikely that your nook is somehow flawed and cannot boot to a sd-card.
I would first try and download and burn one of the SD-card bootable roms just to make sure that you are able to boot off of it.
Try this thread: http://forum.xda-developers.com/showthread.php?t=989637
OR
Burn a bootable Clockworkmod SD-card to also test that you're able to boot.
go here: http://forum.xda-developers.com/showthread.php?t=922870
and get one of the "Download a bootable Clockwork SD card (128mb, 1gb, 2gb, 4gb, 8gb) here:"
If you want another set of step-by-step instructions, I have the time to write one up.

hi, im having the same problem as akizub and i think it may be booting from the sd card. ive tried rooting from all the different firmwares, ive tried different images, winimage, win32diskimage, ubuntu dd, ive even tried buying a new micro sd. i cant figure out whats wrong. ive seen all the youtube videos and instructions

Same Problem here with 1.1/auto-nooter 3.0.0
I'm having the same problem.
Don't think it's an issue with the SD card as I can see the SD files from the Nook after it boots
Wrote the SD using Win32diskimager. This must be working as I can see the files on the SD on both the Nook and the PC. Don't see how a block copy can miss anything!
I'm using auto-nooter 3.0.0
The Nook nook boot looks identical with or without the SD.
Maybe another level of security by BN ?

Just a crazy thought....are you making sure to have the correct versions?
Autonooter 3 NEEDS to be run on stock 1.1.... not 1.0.1 or 1.0.0.
Just thinking that would explain things.
Sent from my rooted stock 1.1 Nook with XDA Premium.
When all else fails, RTFM.

Versions OK
Yep .. Nook is at 1.1.0. autonooter 3.0.0
SD card is a 4GB SanDisk which other people seem to have used.
I'm assuming there is a low level loader in the Nook that attempts to load a boot block in a certain device order. Is it possible they changed that?

Yeah I am running into the same problem, I returned my nook for a few defects and now my new one won't boot from the sd card. Its running 1.1.0... one thing I have noticed that is different is that it seems to boot up faster than my old one did...
Edit:
Its working now, it wasn't partitioning the sd card for boot, was using my phone as card reader, switch to an actual card reader and new sd card and it worked.

Problem was solved.
It was fact that my SD was not bootable.
I tried something simple and reliable like CW recovery. Win32diskimager didn't want to burn disk complaining that it was too small. I tried to burn 1Gb to 2Gb, 4Gb and 16 Gb SDs and it was telling me - not enough disk space.
Then I used winiamge and was fine.
After I saw that CW was booting fine I burned autonooker again and then it started to work.
So, make sure that your SD is bootable by doing some simple and reliable image burning.

Size-agnostic SD Card CM7 gets stuck while installing CM7

Hi,
I am unable to post in the dev forums. hence opening this thread.
I am facing a problem installing sd card bootable CM7.
I am refering to the folowing thread: [ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater: http://forum.xda-developers.com/showthread.php?t=1000957
I do the following:
1. Burn the 9M image (that would unpack into ~130M disk image)
2. Put the downloaded CM nightly build on the sdcard
3. Put the card in the nook color and boot
4. The nook boots to the installation process...penguin image in a corner and starts the process
However, it gets stuck at "Writing superblocks and filesystem accouting information".
I dunno if its stuck or not......because the cursor keeps on blinking.
Its been about 30 minutes and the screen stays in the above status only.
For information, I am using 16gb Kingmax Class 10 microsd card.
Any help will be greatly appreciated.......

acme2ajax said:
Hi,
I am unable to post in the dev forums. hence opening this thread.
I am facing a problem installing sd card bootable CM7.
I am refering to the folowing thread: [ROM][CM7] Size-agnostic SD Card image and CM7 installer for SD Cards. with updater: http://forum.xda-developers.com/showthread.php?t=1000957
I do the following:
1. Burn the 9M image (that would unpack into ~130M disk image)
2. Put the downloaded CM nightly build on the sdcard
3. Put the card in the nook color and boot
4. The nook boots to the installation process...penguin image in a corner and starts the process
However, it gets stuck at "Writing superblocks and filesystem accouting information".
I dunno if its stuck or not......because the cursor keeps on blinking.
Its been about 30 minutes and the screen stays in the above status only.
For information, I am using 16gb Kingmax Class 10 microsd card.
Any help will be greatly appreciated.......
Click to expand...
Click to collapse
Ummm... did you unpack the image prior to burning it to your Sdcard?
In addition it is not proven yet to work on 16gig cards, it has only been tested up to 8gig cards.
Edit: Others now have posted that 16gig cards do not work.

And Class 10 cards are known to have issue with Nook.
Search TITLES in this Forum only for "card" for threads on sd cards.

ADude said:
And Class 10 cards are known to have issue with Nook.
Search TITLES in this Forum only for "card" for threads on sd cards.
Click to expand...
Click to collapse
Hi Adude...Thanks for the update.
Have a small doubt...
I am able to install and run successfully, the sdcard bootable CM7 bt image...which is for 2gb card.
I, then, expand that partition to the rest of the card.
So is it the size of the card thats the issue?
Can this 'size agnostic' image be modified to write only to 2 or 4 gb and then we can expand the rest. I will like to ask this question to verygreen, but i still have some posts to go till I can paste in dev forums.
Thanks again for the info.......

Bumping an old thread, since I have the exact same problem, and can't post in the proper thread as well.
But I used a 2GB class 2 card( I think, it's a generic card that you get in the bundle when you buy a phone) instead, but got the same message.
Did I harm the card in anyway? Can I use it again for this procedure? Or do I have to reflash it in some way?

BrotherZero said:
Bumping an old thread, since I have the exact same problem, and can't post in the proper thread as well.
But I used a 2GB class 2 card( I think, it's a generic card that you get in the bundle when you buy a phone) instead, but got the same message.
Did I harm the card in anyway? Can I use it again for this procedure? Or do I have to reflash it in some way?
Click to expand...
Click to collapse
Generic Class 2 card. You answered your own question, it's probably too slow.

Pity, that's the only card I have lying around.
I'm very new to this so sorry for some very basic questions. But:
1. How do I restore the card to it's original state? I tried the HPUSBFW.EXE file that is in the link above(how to flash a bootable SD guide) but it says that I need admin rights even though I already am admin. Is there any other way to restore the card?
2. I have another generic 2GB from a Sony X10 mini pro, but no idea to try that then? What kind of SD-card should I buy? Since I saw that too fast SD cards have problem as well.

I also can't post in the dev thread and am having issues with this. I'm using an 8gb sandisk class 4 microsd card. I used win32imager to burn the agnostic iso file to the card. Then I clicked exit, unmounted the drive, and plugged it back in. Now the drive shows as a 115mb drive with 107mb free. In gparted it shows as 2 partitions, 1 as 115mb and another as unallocated with the rest of the 8gb. Windows can't see the unallocated one though.
So right now I'm stuck and can't copy the nightly cm7 build onto the drive. Anyone know why it formatted it like this and what I can do to fix it?
Here's an image of what I'm talking about:

107 MB is enough
gmanpie said:
I also can't post in the dev thread and am having issues with this. I'm using an 8gb sandisk class 4 microsd card. I used win32imager to burn the agnostic iso file to the card. Then I clicked exit, unmounted the drive, and plugged it back in. Now the drive shows as a 115mb drive with 107mb free. In gparted it shows as 2 partitions, 1 as 115mb and another as unallocated with the rest of the 8gb. Windows can't see the unallocated one though.
So right now I'm stuck and can't copy the nightly cm7 build onto the drive. Anyone know why it formatted it like this and what I can do to fix it?
Here's an image of what I'm talking about:
Click to expand...
Click to collapse
The nightly CM7 -87 file has around 91 MB (here: http://download.cyanogenmod.com/get/cm_encore_full-87.zip), so you should have enough space to copy it onto your sd card. Actually, that leaves more than 15 MB available, so I suggest you also put the gapps in your SD card (here: http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110307-signed.zip)
About the unallocated space, it will be partitioned by the installer accordingly once you boot the NC with your SD card in it.

Looks like it's working now. I fit the nightly build on there but couldn't fit gapps(144mb). I messed up my froyo install earlier trying to put cm7 on, so I was worried I'd be stuck with a half functional rom for my upcoming 14 hr flight :/
Ok, now for my next question. How do I install it to the emmc? I tried installing it through froyo, but when I deleted the system folder and reset it to factory settings it messed up the froyo install, so now the rom manager doesn't work.
[Edit:] going to try following this thread:
http://fineoils.blogspot.com/2011/04/nookcolor-with-cyanogen-mod-70-emmc.html

What? Gapps is ~5MB only. If you're trying to install with both at the same time verygreen's instructions say that you should flash CM7 and turn on wifi first, prior to flashing gapps.
To install to EMMC you need to burn a CWM SD card, plop the nightly zip on there, boot up with it, then install zip from SD card (select the nightly). Wipe caches/data. Remove CWM card, hit reboot option in CWM menu. You'll need to either have a fresh SD card or reformat the CWM card since CM7 on EMMC requires an SD card in. Instructions for doing this (step by step) are somewhere in General forum by eyeballer.
(Also of note: the info that 16GB cards do not work with this image is no longer true)

Could anybody use a 16Gb sd card so far? I bought one just for the nook and now I found out that its not working - damn! I can't give it back so what? pls help!

Earymgn said:
Could anybody use a 16Gb sd card so far? I bought one just for the nook and now I found out that its not working - damn! I can't give it back so what? pls help!
Click to expand...
Click to collapse
I used SanDisk 16Gb and everything worked like a charm.

stud_muffler said:
I used SanDisk 16Gb and everything worked like a charm.
Click to expand...
Click to collapse
I did too(both with issues and successfully), the only problem I had with my card is that with the size of cm7 and gapps you ahve to flash them separately, so do cm7 first, put the gapps on the boot partition then reboot into recovery.
if you don't do that you'll run out of space on the boot partition during installation.

I used verygreen's instructions to put CM& on a Sandisk 16 gig class 4. Worked the first time I tried. After CM7 I shut down, put gapps on, then rebooted into recovery.
I think the majority of the problems people are having is NOT READING the part in the verygreen instructions about using Sandisk cards.

Imbroglio said:
I used verygreen's instructions to put CM& on a Sandisk 16 gig class 4. Worked the first time I tried. After CM7 I shut down, put gapps on, then rebooted into recovery.
I think the majority of the problems people are having is NOT READING the part in the verygreen instructions about using Sandisk cards.
Click to expand...
Click to collapse
Sandisk is not required.. I've also used Transcend and Kingston. Class 4 and 6 between the three.
What is required is a card that's not crap, or works like crap in the Nook Color. An OS does a lot of small operations or uses a lot of small files, so even if the card is great at mass transfers but sucks at smaller ones, it's going to be a bad experience.
Sandisk is one way to avoid it. So if you're buying one, might as well make it Sandisk. Any others.... if it doesn't work right, try a different card. That easy.

[Q] I/O errors with cm7 on sd card

I followed the instructions to put cm7 on a sd card and everything installed and worked well but things loaded a little slow. I bought a couple sandisk class 4 cards for mine and a friends nook because those are supposed to be better. well I cant get it to work now! the old card still works but when i insert the new sandisk and the penguin starts loading i get a bunch of i/o errors and the cm7 logo ends up looping and never loads up. ive searched for a while. any help is appreciated.

Sounds like your card got corrupted for some reason. Consider flashing a nandroid and just redoing everything.

thanks for the reply. I dont quite know what that advice means. haha

well, that means, if you have backed up your card somehow, you're going to have to reinstall everything and flash back your entire system.
Considering that you are on a SD card system, there are only 2 ways you could have done this back up, 1 is a full on image via winimage or made a backup (nandroid) of your system+data. The nandroid or backup made by cwm would have to be written to your fake "sd" card after you remake your bootable cm7, then you could reinstall that information, provided that you have backed up what's on your "fake" sd, you can just copy that back over.

I still have a working bootable sd card with nightly 102 on it. I tried 2 new sandisk cards and get the i/o errors. ive tried formatting and redoing the new cards at least a dozen times. using winimage and whatever that other one is called windisk32 or whatever. very confused as to why its not working and where to go from here.

Oh, that's odd. I wish I had a solution for you. At this point, it almost sounds like it's an hardware issue as opposed to your software/sd cards.
You got a friend with a nook color you can test your cards out on? If they work on his nook, maybe your reader is messed up, dust/water/etc?'
Sorry, not of much help at this point.

its really weird. they wont work on the other nook either. but the old one does. is there a best way to format an sd card? when I couldnt get them to work initially i started messing with the partitions in disk management. i generally just use the nook to format them.

Well, get easeus partition manager and collapse them all, so a slow format and then try to write the image.

I was able to load everything onto another card. neither sandisk worked... crazy talk.

Well, I think we've established that it's probably how you're writing to your sd cards.
So assuming your software is good (md5 checksums match), then it's a matter of hardware.
2 suggestions, use another computer and try to burn on that.
Use a different microSD reader/writing device (do you use a usb device or is it built in or is it a SD card that you slip the micro one into?)