Hello all,
I've searched the site, but cannot find anyone that has addressed this issue. I have a 8gb patriot class 10 card that is (was) running the Honeycomb Hybrid RC1 and CM7 with Phiremod 6.3 image posted on here. I'm also running the jammr's modified boot menu so I don't have to remove my card to boot stock.
For the second time now, this card has gone from working fine to not being able to boot either OS. Other than rewriting the card, is there any way to repair my ability to boot? I have a good backup, but would like to know if this issue is fixable so I don't have to rewrite my card every single time this happens.
Thank you in advance for the help.
Maybe I've just answered my own question. If I just reload the contents of a clean copy of my boot partition onto this card, that should fix the problem right?
Related
Third time is happens to me... My Nookie Froyo SD installation got corrupted somehow. The first two times I was getting a lot of FC's all over the place so I just decided to rebuilt yet another SD card.
This time, it just stopped booting (stuck on the Android logo in the boot process).
So... I am going to build Nookie Froyo on my SD card yet once more, but I would like to be able to do backup of the whole SD card at various (stable) points.
Ideally I would be able to create an image (using a Windows 7 computer) that I could burn back on the SD card using win32diskimager.
Thanks for any pointers.
Looks like Win32DiskImage has a "Read" button... so the solution might have been just under my nose the whole time... In the process of redoing the Nookie SD card, so I'll try in a little while.
Newbie...
....Acronis True Image do the job....perfectly an without any problem.
Yesterday, I transfer my old 8Gb to new 16Gb after 4ext partitioning and aligning ...all in all 20 min. of work
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.
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.
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.
I have a new 1.2.0 nook color that is preventing me from booting from sd. Tried multiple manual nooter images. The symptom I face is the system does not boot atall, no display, nothing when I have the microsd that is a boot image in the slot. If I take out the microsd, after a few attempts it powers on. With the sd in place, it just does not power up. Tried pressing power, connecting to pc, connecting to power from the wall, all behave the same. It looks like Barnes and Noble went out of their way to block using nook to its full potential . Anyone work around this issue? I have read some of the other posts already, but it seems this problem is happening with only the most recent versions out there.
I can use the same micro sd fine with regular files. if there is a bootable image it stops booting. It looks like the firmware is checking the sd and if there is a boot image there, just suspending the device. Any help will be appreciated. I want to keep the original os on the nook, but need the flexibility of having another android install on a sd.
Maybe an obvious question, have you tried the latest clockworkmod recovery (3.0.2.8) as a bootable image on your sd card? I would first try if you can boot into recovery from the sd card before adding manual nooter into the mix. Manual Nooter is *not* a bootable image.
If all of this is old news for you, ignore my post.
Good luck with your new Nook Color.
Tried multiple versions including 3.0.2.8.
On your recommendation, tried just a bootable disk. That did not work either. I just cannot turn it on. No display at all.. I can only boot it up again if I remove the micro sd card. I tried the 8 gb image first then trying 1 gb image file nookdev-clockwork-0.7 on an 8 gb card then copying the uImage and uRamdisk files. Any problems with this approach? I am fairly new to nook/android, but tech savvy..
Have you tried different models/sizes of uSD cards? How about trying different software, card readers, or PCs to write the IMGs to the cards? At the bare minimum those should be attempted before blaming the Nook.
here is why I thought it may be a nook issue. I may be wrong, but here is the logic. I created the boot disk with win32diskimager-RELEASE-0.3-r27-binary. I can put the same card into the nook when it is already booted and can read these files. When i do this, the nook is creating the standard folders in addition to these files. So I am assuming that the card, writing software, etc may not be the issue since the nook is able to read. Is this assumption wrong? I don't have other size cards handy. I will order some and try in a few days. Meanwhile, if anyone else is facing this issue, please weigh in. Experts, please suggest if I can try something else.
nandsaa said:
On your recommendation, tried just a bootable disk. That did not work either. I just cannot turn it on. No display at all.. I can only boot it up again if I remove the micro sd card. I tried the 8 gb image first then trying 1 gb image file nookdev-clockwork-0.7 on an 8 gb card then copying the uImage and uRamdisk files. Any problems with this approach? I am fairly new to nook/android, but tech savvy..
Click to expand...
Click to collapse
There is an image for a bootable SD with CWM and the correct uImage and uRamdisk files (thanks to DizzyDen). That may be your problem. The SC card you created while it has the correct file structure may not have the correct boot information.
Yeah it's been my experience that the NC is more particular about what it will boot off of vs. what it will read from in normal use. Plenty of posts about this but in general you'll find most Sandisks just work so if you pick one up or borrow a card, try to get a Sandisk just to be on the safe side. Since no one else seems to be having the problem, I suspect it's probably just a card the NC doesn't like or a mostly good card with a bad sector in the wrong place.
Thanks a lot! I used the 2gb image and was able to do it with a 2gb card and 2gb_clockwork-3.0.2.8.rar file.