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?)
Related
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).
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.
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.
I seen to be the only guy left with this problem. I have burned Nookie FROYO to an 8gb card. Using Mini tool partition wizard i then extend the last partition to cover the unused space. Then the Nook boots fine but gives me the 'damaged sd card' error. I tried the Vold method people used on older NF builds, but that seems just to ruin the image. If i don't resize the partition, everything runs fine and i can use the very limited free space on he card as normal. I wanted to try Easeus instead of minitool, thinking it might be something in the software, but i can't get Easeus to see the card at all after it is burned.
Can anyone help?
any advice on where to go here? I also asked at android central, and not getting any hits there either?
Thanks,
Brian
I've also tried deleting the sdcard partition and recreating it the right size. Since resizing didn't work, I thought this might. But it didn't. Still getting the 'Damaged SD card' error.
How is it that I'm the only one out there having this issue? Very frustrating.
-Brian
had same problem through the sd card in my fascinate and tried to format didn't work then plugged in my phone to my usb cable then unplugged went back and it auto formated for me so now i have my nook sd card all good just a little help
Well, I tried that as well. I plug the NC in, and it shows up as two different USB devices. E and F on my Win 7 machine. After quite some time waiting, I can actually open drive F in windows. Unfortunately, when I unplug my NC and try and remount the SD card, it doesn't do anything different. Still gives me the damaged SD card error.....
What else can I do here?
-Brian
I formatted and re-imaged my nook today from 1.0.1 Rooted to stock.
I then manually updated to 2.1 for flash capability.
Now I want my Root back.
For some reason the NOOK won't boot off of the SD Card anymore, it just ignores it until it's booted and I can see the files on the SD card.
I've imaged my SD Card with multiple versions of CWM, shut off my nook, inserted the SD card and plugged in a USB cable to initiate the process.
Is it possible that it requires the "Nook" USB cable to start the boot off of SD Card process or will the cable for my Droid Incredible work as well?
It's the only thing i can think of at this point that is causing the problem.
I won't get my nook cable till tomorrow so i can't test it.
Thanks,
Turmith
You don't need the cable to boot off the sd card, all the cable does is turn the thing on.
You are probably not flashing your card right, it's not simply a matter of copying files over, there is data that needs to be put on the card that isn't part of the files you can see.
If you are using an old nooter or autonooter card, it's probably corrupted or something. You don't want to use those old rooting processes anyhow.
The rooting process is also different now than in previous releases. You should do some reading on how to make a bootable cwm card and what the new rooting process for 1.2 is.
Thanks,
I believe you are right, the sd card isn't being flashed correctly.
I tried following the instructions here http://forum.xda-developers.com/showthread.php?t=1054027
Still got the issue where the nook would completely ignore the sdcard yet read it once it was booted.
So i tried formatting the sdcard with my Droid Incredible, then flashed it using windiskimger using the instructions provided in the link above.
Now when i try to boot off the card i get a blank black screen(never gets to "Read Forever" screen.
I have to remove SD Card, hold power button in(10 sec), release and then hold Power button in again(10 Sec) to get the nook to boot back into 1.2
I'm considering doing the 8 failed boot thing and seeing if it will restore 1.0.0 or something at this point.
Any suggestions?
Well that's progress ;-) at least it's trying to boot from the sd card now even if it's not succeeding.
are you using your droid as a uSD adapter for your computer, or do you have a dedicated uSD reader? that might be your problem. I'd try using a separate card reader.
You can get something like this basically anywhere for under $10. Try target/walmart/kmart/staples or like i said basically anywhere ;-)
I don't use windows for flashing but i've noticed some people saying they have luck with some programs for flashing more than others, try reading around, maybe you'll find an alternative to windiskimager that works better for you.
P.S. Formatting before flashing doesn't do anything at all. The flash should erase anything on the card and replace it exactly with the contents of the image you are flashing, regardless of whether it's freshly formatted or filled with 10 years of irreplaceable photographs
I'm not so sure it's the sdcard reader(which is internal to my Dell Laptop)
I switched from a 8gb sd card to a 2gb sd card(to make sure the SD card wasn't causing a problem) and pulled down a SD version of Nookie Froyo 2gb(to make sure CWM wasn't the issue either) just to see if i could get the thing to boot.
Same thing as occurred again.
It's become apparent that Winimage is either not doing it's job or I've somehow miss-configured the thing to not work correctly.
Winimage seems to only be writing one partition to the sdcard. In addition the Nook won't even attempt to boot off the sd card unless it's been formatted by either the nook or my droid prior to imaging. To me this indicates winimage isn't actually writing a image as much as it is copying files(and only the 1st partition at that).
Next step is to Uninstall Winimage, removing an left over configuration files and re-installing. If that doesn't work I'm going to try switching computers.
If that doesn't work then i'm going to look for a new Imaging program.
If anyone has any insight, it'd be welcome.
Well I can officially state my opinion that WinImage sucks...
I downloaded WinDiskImage and within 5 minutes I had my Nook 2.1 Rooted.
Thanks for your help.