[Q] Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report"
Hi,
First let me say - YES, i have searched all of the forums here (and a number of other sites) and seem to have tried almost every option.
I have Chronic "Unexpected Lack of Boot Partition on the SD card! Please Report" problems. The farthest I get guaranteed is the cyanogenmod boot and menu (if I try and bring it up). I'm simply trying to get the SD card with cm7 to boot reliably and not eventually loose the boot partition.
Off and on since spring I was able to burn a CM7 image (verygreen's size agnostic, and one or two others I have since lost track of) to a SD card; have had it boot to cm7 and it work for awhile - but then eventual degraded into the no partition found error. the majority of the time it just doesn't work and results in that annoying purple black screen.
When it does work, it only works for awhile and then the boot partition can't be found; a few very small 3 of times - if I copied a new update it woke back up ad worked for a couple of reboots then lost the partition again.
Anybody got time to take pity on my melted brain and take a few guesses?
Clearly I'm not only missing something - but as things have gotten worse, am now missing more (if that is possible) as I'm going backwards to see why it no longer works at all.
At this point wrong has happened so often, I'm just lost on what even worked way back when I started.
I'm trying to backtrack to where it at least worked a little for a few days...but noob world is decaying into worse world.
I tried a couple of other, older processes and a multiboot menu one that seemed promising (plus could handle the new naming conventions for 7.2 CM7); but that one never even got past the missing boot partition.
I have tried approx 10 2gb SDCards, Sandisk, Kingston, Unknown; Class 4 and mixed.
I have tried 3 8GB SD Cards, Sandisk, class 4
I have tried 1 16gb SD Card, Sandisk, class 4
I have tried a Vivitar Micro SD Card Reader
I have tried the micro SD card Adapters in a laptop, and then in a sandisk USB adapter.
I even tried doing it all using the Nook color via a USB cable.
I even tried leaving the nook color off and connecting the USB cable to the PC to initiate a boot.
Using Windskimager
Using SD formatter
Have formatted Full erase and overwrite.
Tried leaving partition size alone
Tried partition resizing up to 250mb
Tried cm7 zip alone and with gapps
WinXP on 2 desktops and a laptop
It sounds like you have run the gamut of attempted resolutions.
That message is part of the verygreen partitioning script that runs every time the verygreen recovery is run. So, that means the normal boot kernel for CM7 is not loading.
The way the verygreen SD should operate is it starts with uImage and uRamdisk on the boot partition. Those are verygreen's recovery files. The first time it is booted, it looks at your emmc to be sure it is a nook. Then it looks at the SD to see if it has been partitioned yet. If it is not, it partitions it into those partitions necessary for installing ROMs. After partitioning, it looks for a zip to install. If it does not find one, it shuts down and the next time it boots it does the same thing until it finds the first ROM zip to install. If it finds one, it installs it. The first time it installs a ROM, it renames those uImage and uRamdisk verygreen files to uRecImg and uRecRam and they become the verygreen recovery files. And it installs new uImage and uRamdisk files from the zip to become your CM kernel and ramdisk. These are what normally will load in the future to start CM.
Now, with the disk partitioned and CM installed, ordinarily, after the cyanomod logo comes up, it boots by default to CM via the uImage and uRamdisk files. If you intercede with the boot menu and tell it to boot to SD recovery, it looks for uRecImg and uRecRam to load the verygreen recovery. If that is loaded, the verygreen script does all its checking again, it verifies that emmc is a nook, then tries to verify if the SD is partitioned. If it is, it looks for a new zip to install. If, in checking to see if it is partitioned, it cannot find partition 1, it gives that message that has been bugging you.
So I see two things that are happening to you.
First, it is booting to the verygreen recovery first instead of CM. That could be due to a recovery bootloop happening. Look at my tips thread linked in my signature to see an explanation as to what that is and how to possibly get out of it.
Second, after it boots to the verygreen recovery, it does its checking and cannot find partition 1 of the SD and gives you that message.
What I cannot understand is, if you have no partition 1 on your SD, how is it booting to the verygreen recovery?
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Ditto on that - especially as it boots happily to that error message time after time after the green cyanomod screen appears and I can also do the menu trick to get it to go into recovery.
Just as a clarifier: A number of times it tried to do the install (text flowing by) and at the end claims it can't find the boot partition - odd (unless I have less of an idea of what I am doing than I think) as isn't all that running from that partition? A fairly even number of times it doesn't even run the install and just errors out right up front.
Once in a great while it all works, and I'm good for a few days - but eventually upon rebooting to get it back to normal (either by menu choice or by pulling the sd card) - all I get is that lack of partition again.
leapinlar said:
What you have not told us is what you have on emmc. Stock? Does it boot properly without the SD installed? Or does it go to stock recovery?
Click to expand...
Click to collapse
Yes with the SD card out it boots to stock, although a few time what looked like the CWMod menu came up after I shut down and started up without the SD card installed. Maybe only 2 or 3 times out of WAY to many boots to stock so the kids could read their books while I went to work.
I have even tried resetting the nook to factory on the off chance I did something dumb while mucking about to cause that.
leapinlar said:
After this happens to you again, take the card out and put it in the PC. Tell us what you see. What files are there? Maybe look at it with Mini-Tool Partition Manager and see what partitions it reports.
Click to expand...
Click to collapse
Will do so later tonight and will read the notes in your signature as well.
I saw something go by about the boot partition having to start at the 63 block or something - I can't believe ALL my SDcard adapters / writers are bad, but could the nook reader be screwy? Anyway to do a real test? I've been using the Easeus Partition Manager, but will try the Mini-Tool Partition Manager.
Thanks for the step by step explanation of exactly what happens in the process so I can again get a handle on what it's all doing. That all makes sense to what it looks like it tries to do. Deeply appreciate the time!.
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
leapinlar said:
You know, I am beginning to suspect something is wrong with your card reader built into the nook. Some sort of intermittent thing like a pin not making a good connection to the card. Put an ordinary SD in it and see if your stock can consistently read it.
Is your unit still under warranty? You might want to explore seeing if you can get it replaced.
Click to expand...
Click to collapse
I had thought of that too - at stock it seems to have no problems reading consistently; I've done surface tests using partition manager - but haven't located any real other options of hard testing like once done for hard drives.
Plus the fact that sometimes, it will work for days before it craps out.
j8048188 said:
Your downloaded verygreen image might be corrupted. Have you tried re-downloading it?
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
A number of times - I went through and wiped all my downloads for the latest try.
Okay So As I mentioned I went back and wiped everything I had downloaded and restarted (again).
Current status is it's working BUT:
suspiciously too easy this time, worked first shot
- (having said that, I've had looking stupid and asking suddenly means it all starts working - so if it's that I'm good with this)
I've only rebooted into CM7, not back to stock at any time
Have not removed the SD card
I've not had time to load up the apps I like, just the kids games
- (sometimes I think it's the more wanted, the less reliable)
Obviously because I haven't removed the SD card, i haven't been able to retry things enough to recreate the other problems of boots right, yet can't find the partition when it really counts.
Changes (listing stupid things too, just because):
-Went back to my sandisk class 4 16gb HC card
-changed USB adapter back to sandisk one, using a sandisk micro to SD adapter that specifically says sdhc (although I think that is really just marketing
-Formatted the SD in the Nook x2, and did not use SDformatter
-Looked at the partition on the card with MiniTool not Easeus partition manager
-There is a step in verygreen's where you pop the card out and reconnect to the PC BEFORE adding the cm zip, made sure to do that - but could swear I had done it before.
Full painful boring steps that SO far has gotten it past the first stage of creation (again the full test is when I boot into stock a few times, or remove the SDcard for anything, or load my really wanted apps on the android side):
--Also note my lack of class 4 Sandisk cards, I only had one after all. BUT I have had this all work to this point with the 16gb only to have it go south.--
Painful details is so I can catch what is really worthwhile different as even WHEN I get it to work, I'm going back to try all the other cards because it worked so oddly and failed so oddly and differently - but that's just me.
> The 2GBs are:
6 Sandisk SD, don't see any class Rating
2 no brand SD, don't see any class Rating
1 Kingston SD, don't see any class Rating
> The 8gb are SDHC "Adata" Class 4 SDHC
> The 16gb is a Sandisk Class 4 SDHC
Using the 16GB Sandisk Class 4
--------------------------------
> Nook booted to stock
Inserted SD Card
Unmounted
Formatted sucessfully
unmounted and removed
> Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
> Mounted as E Drive
E Drive shows standard Nook Folders:
.amdroid_secure
B&N Downloads
LOST.DIR
My files
> MiniTool Partition Wizard
Surface test = all good.
>Write the image on your SD card
Used Win 32 Disk Imager
After done with writing, eject and then re-insert the uSD card into your computer.
Two Partitions - 118 and 14.72gb
>Copied to card:
update-cm-7.1.0-encore-signed.zip
Installed correctly
configured wireless
Rebooted = OK
Rebooted = OK
>Turned off
Removed SD Card
Put in Red SD / SDHC Adapter
Put in Sandisk MicroMate SDHC to USB Adapter
Put in Front USB spot
copied gapps
>Boot into Recovery
Gapps installed
> boot
all good
did all set ups like before
added apps (7 games for kids)
rebooted twice
started using
added one app I really like (newshog)
Listening for drumming... nothing so far (Dr. Who reference)
I'm going to go the weekend before rebooting to stock as I can do some adding, and rebooting to android.
Maybe backup the droid side this time around.
THEN the death tests on Monday
-thanks for listening_
p.s. - Yes, I still suspect the card reader somewhat as REMOVING may be where it breaks down.
However, once or twice when I had the Unexpected lack of boot partition error - I was able to bring it back by doing a CM7 update via recovery, despite it refusing to find the boot partiton immediately previously - of course that means the SDcard was removed and reinserted. Most time reinsertion = no help.
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
leapinlar said:
You do not need to remove the SD to test booting to emmc. Just press and hold the n button during the boot until the boot menu comes up. Then select emmc/normal and boot. It will boot to stock. The only problem with doing that is now your SD boot partition is 'sdcard'. But should work for testing stock.
Click to expand...
Click to collapse
Yes, I know - but it's two separate tests to see which one caused the problem.
Turns out that neither was needed - it was easier to create; my son simply turned it off (not a reboot cycle as I had been doing which worked).
When it was turned on, it no longer boots - it goes straight to BSOD (actually deep purple).
Booting into recovery gets me:
Penguin Logo
rcS!
Populating /dev using udev: done
Initializing random number generator.... done.
modprobe: chdir(2.6.32.9): No such file or directory
Starting Network...
Detected Standard B&N nook layout, emmc first
Error! Unexpected lack of boot partition on the SDCARD!
Please Report!
Poweroff when ready
Since I'm till held to the noob reposting limit of once every 5 minutes and the captha I can barely read - I'll post MiniTool result in about 5 minutes. I'll link a screen capture if i can here.
I tried to boot per menu to the EMMC stock; Clockworkmod Recovery v3.2.0.1 came up. I know I did emmc and what ever the second default is (which should be normal) - I'm pretty sure it was normal.
I offed it and did the same and confirmed it was the default; THIS time it came up Nook stock.
Is there some way I installed something to the stock NOOK and didn't remove it when I restored to factory? The other day I did the restore from that same clockworkmod screen NOT from the stock Nook environment.
I'm wondering if I somehow created my own monster way back when I first started this and was playing in the android environment.
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Just for Ha, Ha's I hooked the Nook via USB to the PC.
G Drive "Removable Disk G" (wants a disk to be inserted)
E Drive "MyNookColor" ( Lots of what I assume to be standard Nook folders.
See my edit above.
Attachement # 1 SD Card from Mycomputer:
Attachment # 2 MiniTool View of SD Card
Boot Partition
Properties using Minitool Partition Wizard (attached):
Used
Partition Info
File System Info
Surface Test of Boot Partition:
Perfect - so no picture.
This is SO aggravating - I almost would accept just knowing why rebooting wrecks something if I knew WHAT).
leapinlar said:
I just edited what I wrote a few seconds ago. The reason it went to emmc recovery is because the recovery flag was not reset when that SD Recovery told you that error. Did you read my tips about recovery bootloops? When you exited 3.2.0.1, it cleared the flag and booted normally.
I still suspect hardware issues.
Click to expand...
Click to collapse
Sorry, apparently not closely enough - got lots of time again.
....didn't expect that anyone would be watching, was busy posting pictures so I could go away and read and think...
Probably is hardware - wish I had some way to vigorously test that, I get that basic use in Nook Stock doesn't really prove everything is good.
Plus I bought refurbished and I have to go dig up the warranty, it was months ago, so not too hopeful and boxes long gone. Don't know how nice B&N is, free replacement charger and cord is one thing - whole another refurb unit is different if I can't show stock SD card reading is an issue, not sure how much they check, but I don't think they care about CM7 off a SDcard not working!
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
If you registered your nook, the serial number is all you need. Refurbished usually have a one year warranty. Mine did. Just tell them card reading is intermittent. Which it is. They are pretty generous. You still have stock on there.
Edit: Try just an ordinary SD and power off, reboot, and repeat many times and in between check card reading ability.
leapinlar said:
Everything looks perfect on that card. All the right files, partition sizes, etc. You have stock on emmc, CWM 3.2.0.1 on emmc recovery.
I still suspect hardware issues. Powering off makes card semi-unreadable. Can still boot to it but when checking for partition information on SD fails.
Click to expand...
Click to collapse
Yup, it's really the only thing that hasn't been able to be changed through all of this.
I've mostly gotten these results - I've managed to make it worse as I redid things and apparently got sloppy. But when going back to methodically following instructions I have what I had months ago. I had hoped buying other cards would make it at least act differently.
Thanks for all of the reviews and double checking, at least I now it's not something obvious (but wasn't obvious to me) that I missed along the way!
I'll have to call B&N and see how strict they are and if they take the "It just has trouble reading any SD card consecutively".
Now where was that review of the Nexxus 7.... and I wonder how all the tablet prices are going to drop especially for the Galaxy Tab. Buying is not as fun but I am completely beat with modding failures.
We are too fast with each other. Lol. See my edit above.
Related
So I originally asked this in Amon_RA's recovery thread, but was kindly asked to move it here. So here's my issue.
My G1 is not recognizing or creating any ext partitions using either the manual parted method or the automatic script include in Amons recovery. Using the manual method to make ext2 I get the following error:
Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel
Fat32 gets created fine.
I used fdisk on my laptop to create the partitions and it seems to take, but once I put the sd card back into my phone it disappears. Taking the card out of my phone and back in my laptop, the ext and swap partitions are gone. Anyone have any idea as to what the problem could be, or is my card just pretty much bricked?
SpiggidyBob said:
So I originally asked this in Amon_RA's recovery thread, but was kindly asked to move it here. So here's my issue.
My G1 is not recognizing or creating any ext partitions using either the manual parted method or the automatic script include in Amons recovery. Using the manual method to make ext2 I get the following error:
Error: Input/output error during write on /dev/block/mmcblk0
Retry/Ignore/Cancel
Fat32 gets created fine.
I used fdisk on my laptop to create the partitions and it seems to take, but once I put the sd card back into my phone it disappears. Taking the card out of my phone and back in my laptop, the ext and swap partitions are gone. Anyone have any idea as to what the problem could be, or is my card just pretty much bricked?
Click to expand...
Click to collapse
try paragon partition manager 9.0. see if that works for you. if not hit up newegg or meritline for a new card
Bad SD Card
b0ricuaguerrero said:
try paragon partition manager 9.0. see if that works for you. if not hit up newegg or meritline for a new card
Click to expand...
Click to collapse
I've been pulling my hair out for the last day trying to figure out why it would act like it partitioned fine, but then when I did a 'print' in parted it would only show one FAT32 partition. I had the EXACT problem the OP was having.
Half my day spent looking for some other resolution and then realized I had another SD card with me (just half the size) and tried it in the Recovery with that one with complete success. No errors or anything. I'm trying Paragon Partition Manager for my larger card, but not finding an option for the ext2 (or other UNIX) formats. It's the free 2010 version so I'm not sure if that makes a difference.
Bad SD Card - Paragon Killing USB Drivers?
vwyankee said:
I've been pulling my hair out for the last day trying to figure out why it would act like it partitioned fine, but then when I did a 'print' in parted it would only show one FAT32 partition. I had the EXACT problem the OP was having.
Half my day spent looking for some other resolution and then realized I had another SD card with me (just half the size) and tried it in the Recovery with that one with complete success. No errors or anything. I'm trying Paragon Partition Manager for my larger card, but not finding an option for the ext2 (or other UNIX) formats. It's the free 2010 version so I'm not sure if that makes a difference.
Click to expand...
Click to collapse
So, version 9.0 has the options for the needed Linux partitions. With that, it would appear I have a bum 8GB card. As stated, the 4GB works just fine - both Transcend Class 6 cards. On one PC it was having a difficult time in the formatting process after creating the partition and I had to kill the application via task manager in Windows. Then it got to where my USB port drivers couldn't start so I couldn't read via SD card adapter or USB cable to the phone with the card mounted. I'm in IT so I've dealt with drivers failing before, but I'm finding myself having to ask my friend Google now as even after uninstalling the drivers I have the same result. I'm afraid it might be due to the Paragon application. More on that below.
I installed Paragon on another laptop at home and it went through the process successfully (at least appeared to) with the 8GB card. Joy had returned to my frustrated being and I proceeded to use the restore image to upgrade from ext2 to ext3 - success! - Then it was wipe and flash. All seemed well in the world until I went into the settings after getting into the OS for the first time (again) to look at my secondary SD Card space and found it at "unknown." Looking at the card via Paragon Partition Manager once again it was showing as only two partitions instead of three with the ext3(2) being "unformatted." Just to be sure, I put in the 4GB card to verify in Paragon it's showing as expected (three partitions in correct formats).
Being the stubborn sod I am, I came to work determined to get the 8GB card working and installed Paragon on a test machine (I run a large testing lab) and redid the partitions. Removing and re-adding the partitions on the 8GB with "success" then simply unmounting and mounting the card to the PC revealed the card is definitely the major flaw all along. After mounting it came up as just the two partitions again - FAT32 and unformatted for the 2nd, even though it was only 10 seconds ago it showed successful creation of the three and formatting. Because I'm one to verify a verification I repeated my steps to see the same result. However, not only did I see this same result I now DIDN'T see the SDCard via Explorer, but could via Paragon. Inspection of Device Manager showed the exact same thing as on my home laptop that stopped being able to read the Android phone with card or adapter with card.
So, my last couple days of fighting and frustration were all because of the SD card of which I've never had a problem with it storing data for the last year with many times reformatting and re-applying data. Odd, to say the least. I am back up and running, but now I have USB drivers failing to start problem on two PC's! This is not a concern with the one at work since I'll just restage it, but I'm afraid it might take restaging my laptop for this to be fixed which as we all know is just not very convenient.
Anyhow, the lengthy explanation was more for those like me that were Googling/searching for a long time for a similar situation.
Cheers.
I have a similar problem. One of my SD cards of 1 GB has ext 2 and 3. But the main one of 2 GB can be partitioned only with ext 2. I am using Amon Recovery 1.5.2. When I press create ext 3 I get an error and not even from console it doesn't work, I get upgrade_fs not found.
adair said:
I have a similar problem. One of my SD cards of 1 GB has ext 2 and 3. But the main one of 2 GB can be partitioned only with ext 2. I am using Amon Recovery 1.5.2. When I press create ext 3 I get an error and not even from console it doesn't work, I get upgrade_fs not found.
Click to expand...
Click to collapse
I would say it IS the same problem and that your card is not being partitioned properly. The reason it can't upgrade from ext2 to ext3 is because there isn't ext2 to begin with even though the partition process gave a "success" result in the Recovery. I'm using the same Amon 1.5.2 as well. It somehow will not format as the space will be there unformatted if you open the card in a partition application with GUI.
Going to the SD Card settings from within the OS you'll see the SD Card secondary use grayed out and showing "unknown."
So what is the solution? What if I buy a new card Class 6 that can't be partitioned?
adair said:
So what is the solution? What if I buy a new card Class 6 that can't be partitioned?
Click to expand...
Click to collapse
I would say keep your receipt and return it for another. I've had issues with SD cards before where they kept going corrupt within a day of use and just returned them for another (same brand, same model) that would work fine.
It's not a hardware problem, I managed to partition it after some tries. I think that Amon RA recovery does not recognize the sd card sometimes. It worked after I hit the reboot button in recovery and pull out the battery. After that I went back to recovery and I could partition it.
vwyankee said:
So, version 9.0 has the options for the needed Linux pblah blah blah blah
.... windows .....
blah blah blah
Googling/searching for a long time for a similar situation.
Cheers.
Click to expand...
Click to collapse
bug a friend with a linux///mac machine and partition it with that. i've seen lots of problems with usb/partitioning on windows ,and never had the same problem on mac/linux. 3 microsd cards were 'unusable' according to vista, reeformated just fine with osx.
give it a shot.
adair said:
It's not a hardware problem, I managed to partition it after some tries. I think that Amon RA recovery does not recognize the sd card sometimes. It worked after I hit the reboot button in recovery and pull out the battery. After that I went back to recovery and I could partition it.
Click to expand...
Click to collapse
You verified it worked with looking in the SD card and Phone storage settings?
I've also discovered that the 4GB card that I was able to partition without a problem was one I should've thrown out as I couldn't remember where it came from until after dealing a couple days of constant lockups on the phone (now that things are running off the SD). It was thrown in a drawer due to going corrupt every few days where the data on it was lost/gone/unreadable. Going out to get a new SD card today.
To the statement about bugging someone with a mac/linux, that doesn't appear to be the issue here since it won't work with using Gparted either (at least in my case).
Just an FYI update, that after buying a new (not the lowest end) SDHC class 6 8GB card, it partitioned just fine in the recovery image along with being able to upgrade the ext2 to ext3 then ext4. Now I'm finally seeing the speedy benefits running Cyanogen's latest ROM. No issues since replacing with a good card.
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.
I tried to create a CM7 bootable SD card per the thread entitled "Size-agnostic SD Card image and CM7 installer for SD Cards. with updater."
I used WinImage to create the supposedly bootable SD card with the installer, placed it into my Nook which was fully off, and the Nook booted as usual instead of from the SD card.
Am I missing something? How do you boot from an SD card?
Is there such a thing as a boot choice menu like on my PC or is the default always to boot from the SD card?
Does the Nook have to be rooted for this to work?
Thanks
ETA: My PC shows the uSD card as nearly full, but my Nook shows the SD card as nearly empty (1.74 out of 1.84 GB available).
When you bought your Nook, did it have a blue sticker on the box? And does internal storage show 1GB or 5GB for you?
Also, you did drop an update CM7 zip file onto the imaged uSD before you tried booting off it right?
angomy said:
When you bought your Nook, did it have a blue sticker on the box? And does internal storage show 1GB or 5GB for you?
Also, you did drop an update CM7 zip file onto the imaged uSD before you tried booting off it right?
Click to expand...
Click to collapse
No blue sticker was on the box. The internal storage shows 5GB.
Yes, I had a CM7 zip file on the imaged card. (The latest encore nightly)
Interestingly, my PC shows the uSD (2 GB) as nearly full. The Nook shows it as nearly empty (1.74 out of 1.84 available).
JowBe said:
No blue sticker was on the box. The internal storage shows 5GB.
Yes, I had a CM7 zip file on the imaged card. (The latest encore nightly)
Interestingly, my PC shows the uSD (2 GB) as nearly full. The Nook shows it as nearly empty (1.74 out of 1.84 available).
Click to expand...
Click to collapse
When you burned the installer img, did you run WinImage as administrator? Also, when you put it in your reader it comes up as boot (drive letter in Windows, with files like uImage, uRamdisk, mlo, u-boot.bin, right?
angomy said:
When you burned the installer img, did you run WinImage as administrator? Also, when you put it in your reader it comes up as boot (drive letter in Windows, with files like uImage, uRamdisk, mlo, u-boot.bin, right?
Click to expand...
Click to collapse
Yes, I ran WinImage as administrator. And yes, it shows up in Windows explorer as boot and yes those files are there.
Could it be because my Nook operates in "factory mode," in order to skip initial registration?
You should run it and register it and setup wifi and everything first. Get the stock software working fine and dandy (its not half bad actually). Then, checkout this guide for installing CM7 onto an SD card:
http://clubnook.com/forum/showthread.php?953-Rooting-Instructions
It has worked for some rooting rookies so far and includes both windows and mac guides specific to SD cards.
JowBe said:
Could it be because my Nook operates in "factory mode," in order to skip initial registration?
Click to expand...
Click to collapse
I'm not sure, because I ran through initial registration on stock prior to running CM7 off SD --- I used the same image (verygreen's agnostic at http://forum.xda-developers.com/showthread.php?t=1000957) as you did without a hitch.
If you decide to run CM7 off internal sometime you're going to need to register the nook anyway.
You could try an alternate bootable SD (e.g., using an image from here: http://forum.xda-developers.com/showpost.php?p=13283643&postcount=34) to eliminate one of the two: a) your nook having issues booting from SD or b) your SD install is not set up correctly.
An update: I decided to try to create a bootable SD from another bootable image (MonsterRootPack with CWR). This time the nook wouldn't even turn on. I'm going to try to create a third bootable SD as angomy has suggested to see what happens.
I need to add that when I removed the uSD card, it booted normally.
Also, when I create the bootable SD with winimage, I get a dialog box that tells me that the format of the SD card is not right and asks me if I want to resize the image. But this happened on both the images. I don't know if this has anything to do with it.
angomy said:
You could try an alternate bootable SD (e.g., using an image from here: http://forum.xda-developers.com/showpost.php?p=13283643&postcount=34) to eliminate one of the two: a) your nook having issues booting from SD or b) your SD install is not set up correctly.
Click to expand...
Click to collapse
Ok, I tried the CWR image in the link you gave. Same problem - no-go. Just sits there dead. I remove the uSD and it boots normally.
FWIW you do not have to boot into stock B&N at all before you setup and install to CM7 SD card. One of my NCs has never ever booted into stock ROM at all, I installed CM7 onto SD card and running off that from the moment it was unboxed.
The NC will always boot off the SD card first, so if it's booting off eMMC instead then there must be something wrong with the img that you wrote to your SD card.
Make sure that you have a freshly formatted SD card, preferably one with good small random block r/w speeds (eg Sandisk class 4 8G). Follow the instructions in verygreen's "Size Agnostic..." OP to the letter. Re-download all the files as you may have a corrupted one. Make sure to check MD5 this time. Try using Win32diskimager instead, the 0.1 version works better.
It should work. Good luck.
ebubar said:
You should run it and register it and setup wifi and everything first. Get the stock software working fine and dandy (its not half bad actually). Then, checkout this guide for installing CM7 onto an SD card:
http://clubnook.com/forum/showthread.php?953-Rooting-Instructions
It has worked for some rooting rookies so far and includes both windows and mac guides specific to SD cards.
Click to expand...
Click to collapse
Thanks for the link. I have given this some thought, and it doesn't seem reasonable that booting from an SD card should depend upon the state of registration of the device because the whole idea of booting from an SD card means that the content of the SD card is loaded in the place of the stock software.
robot8 said:
FWIW you do not have to boot into stock B&N at all before you setup and install to CM7 SD card. One of my NCs has never ever booted into stock ROM at all, I installed CM7 onto SD card and running off that from the moment it was unboxed.
The NC will always boot off the SD card first, so if it's booting off eMMC instead then there must be something wrong with the img that you wrote to your SD card.
Make sure that you have a freshly formatted SD card, preferably one with good small random block r/w speeds (eg Sandisk class 4 8G). Follow the instructions in verygreen's "Size Agnostic..." OP to the letter. Re-download all the files as you may have a corrupted one. Make sure to check MD5 this time. Try using Win32diskimager instead, the 0.1 version works better.
It should work. Good luck.
Click to expand...
Click to collapse
Thanks. Yes, I just replied to another poster that I didn't think that the state of registration of the device should matter since the whole purpose of a bootable SD card is to load the contents of the SD in place of the stock.
I have followed the instructions in verygreen's thread to the letter - several times. Also, I have tried to make other bootable SDs without success. But that's a good idea about trying Win32diskimager. Also, I will try a Sandisk class 4 card SD as soon as I can get to a store.
I do have a question. When I format the SD card what "allocation unit size" should I be using? (formatting through Windows) The default is 32 kb.
PROBLEM SOLVED!
Thanks to everyone for trying to help me figure this out. The winning idea belongs to robot8.
When I switched from using WinImage to using Win32diskimager, it worked immediately. I am now running CM7 on my Nook Color! Took forever and a day to boot though.
Congrats!
Re: allocation unit size, do you mean cluster size? Depends on how big the FAT32 partition is --- larger clusters used means more actual space used but too large a size can reduce access speed. Generally Windows defaults to suggested 4k for up to 8GB, 8GB-16GB = 8k, 16-32GB = 16k, and 32+ = 32kb.
Also the first boot is the longest --- shouldn't take as long after that. Welcome to CM7 - I don't regret installing it over stock after waffling for weeks on whether or not I'd use stock at some point -- CM7 is just too much faster with too many more options and tweaks for my impatience to deal with stock Froyo.
THANK YOU OP!
I had the same issue, tried 20x various ways, 2 different computers, 2 different SD readers, and it was WinImage that wasnt working correctly. Win32DiskImager solved it.
Thanks.
JowBe said:
PROBLEM SOLVED!
Thanks to everyone for trying to help me figure this out. The winning idea belongs to robot8.
When I switched from using WinImage to using Win32diskimager, it worked immediately. I am now running CM7 on my Nook Color! Took forever and a day to boot though.
Click to expand...
Click to collapse
Thanks so much! This finally got it to work for me too. Loving my new Android tablet
FWIW, WinImage does not work. Maybe it used to work, but it does not now. I posted about this a few days ago here.
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.
Hi, so I've tried everything I can think of to restore my Nook to the stock 1.4.1 but nothing has worked and I've given up before I break anything else...
This all started when I was trying to install the CM7.2/CM9 dual boot from SD card - I burned the image to the SD card and booted but the device just hanged at a black screen (for a lot longer than it should have) after the CM "loading" startup screen.. I tried removing the SD card after holding the power button to turn it off but it then refused to boot to the EMMC stock OS... Somehow (I've only ever used SD card CM ROM's) an old CWM install (v.3.0.2 or something) was installed on the internal memory that booted when I tried to launch a factory reset (Power + N + vol+).
I then followed an older guide to restore to stock by formatting the /system and /data and installing a .zip from sd card (the nookcolor_1_4_1_signed.zip) but it failed with a (bad) error....
Now I don't know what to do. The device now hangs at "Read Forever" and the internal CWM is gone, as well as everything else I'm assuming... It will boot into CWM if it's installed on an SD card, but without that it will just reboot into Read Forever when I try to turn it off...
An aside, but now that I've checked with external CWM again, it appears there is now a "/system1, /system2, /data1, and /data2" file on the EMMC...
TL;DR: How do I restore Nook Color to stock 1.4.1 from CWM installed on an external SD card without flagging a "(bad)" error with the install?
Thank you for any help and I hope I haven't bricked this device... Hopefully this is just a case of ignorance on my part
EDIT: I've tried re-downloading the 1.4.1 and even a 1.2 signed ROM with out success. I haven't rooted the device, but I do not know how the internal CWM got there, as well as the fact that the external SD dual boot didn't work.. I'm using a new SanDisk Ultra 16GB SDHC Class 10 card if it makes a difference..
Could not having rooted the Nook be the only cause?
I had successfully dual booted the CM7.2 and CM9 for months until my old 16GB card broke... This was the new card I bought last week and it's been nothing but problems, exacerbated by myself, probably :/
I
cekren said:
Hi, so I've tried everything I can think of to restore my Nook to the stock 1.4.1 but nothing has worked and I've given up before I break anything else...
This all started when I was trying to install the CM7.2/CM9 dual boot from SD card - I burned the image to the SD card and booted but the device just hanged at a black screen (for a lot longer than it should have) after the CM "loading" startup screen.. I tried removing the SD card after holding the power button to turn it off but it then refused to boot to the EMMC stock OS... Somehow (I've only ever used SD card CM ROM's) an old CWM install (v.3.0.2 or something) was installed on the internal memory that booted when I tried to launch a factory reset (Power + N + vol+).
I then followed an older guide to restore to stock by formatting the /system and /data and installing a .zip from sd card (the nookcolor_1_4_1_signed.zip) but it failed with a (bad) error....
Now I don't know what to do. The device now hangs at "Read Forever" and the internal CWM is gone, as well as everything else I'm assuming... It will boot into CWM if it's installed on an SD card, but without that it will just reboot into Read Forever when I try to turn it off...
An aside, but now that I've checked with external CWM again, it appears there is now a "/system1, /system2, /data1, and /data2" file on the EMMC...
TL;DR: How do I restore Nook Color to stock 1.4.1 from CWM installed on an external SD card without flagging a "(bad)" error with the install?
Thank you for any help and I hope I haven't bricked this device... Hopefully this is just a case of ignorance on my part
EDIT: I've tried re-downloading the 1.4.1 and even a 1.2 signed ROM with out success. I haven't rooted the device, but I do not know how the internal CWM got there, as well as the fact that the external SD dual boot didn't work.. I'm using a new SanDisk Ultra 16GB SDHC Class 10 card if it makes a difference..
Could not having rooted the Nook be the only cause?
I had successfully dual booted the CM7.2 and CM9 for months until my old 16GB card broke... This was the new card I bought last week and it's been nothing but problems, exacerbated by myself, probably :/
Click to expand...
Click to collapse
Easy solution. Go to my tips thread linked in my signature and make a bootable CWM card per item A10. Then flash my format 567 zip. Then go to item A15 and download my 1.4.3 stock ROM and flash that. Boot up, register and you are golden.
If you want to put a ROM on SD go to my updated SD instruction thread also in my signature.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
I
Easy solution. Go to my tips thread linked in my signature and make a bootable CWM card per item A10. Then flash my format 567 zip. Then go to item A15 and download my 1.4.3 stock ROM and flash that. Boot up, register and you are golden.
If you want to put a ROM on SD go to my updated SD instruction thread also in my signature.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Thanks! I'll try that right when I get home..
EDIT - Awesome - It works! The dual boot card also works!
EDIT 2 - so... booting from the SD card still doesn't work... It just hangs at the Cyanogen7 boot video looping over and over (left to go to the store, got back and it was still looping)... holding power button down just resets the device while the SD card is in, doesn't actually shut down for more than 4 seconds or so....
Should I post this as a new thread? I'll try searching for anybody else having this problem in the mean time...
cekren said:
Thanks! I'll try that right when I get home..
EDIT - Awesome - It works! The dual boot card also works!
EDIT 2 - so... booting from the SD card still doesn't work... It just hangs at the Cyanogen7 boot video looping over and over (left to go to the store, got back and it was still looping)... holding power button down just resets the device while the SD card is in, doesn't actually shut down for more than 4 seconds or so....
Should I post this as a new thread? I'll try searching for anybody else having this problem in the mean time...
Click to expand...
Click to collapse
Are you using Racks' dual boot SD? If so, how recent is it? You might want to go to his special CWM and clear dalvik cache and try rebooting again.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
Are you using Racks' dual boot SD? If so, how recent is it? You might want to go to his special CWM and clear dalvik cache and try rebooting again.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
Yeah, I used the Dual Boot image I downloaded a couple days ago from Techerrata (I used the one at the top of the list that had the most downloads, connection I'm on is blocking Techerrata so I can't get the exact name ATM) with burned with Win32DiskImager, popped in the card and turned on but it just hangs. I'll try clearing the dalvik cache with his CWM image and see if it fixes anything..
EDIT - Ok, I tried clearing the cache, but it gives me the following error:
E:unkown volume path [/data]
I checked the Mounts and Storage Menu, and it looks like I still have "/system1, /system2, /data1, and /data2" directories, did the 567 format.zip not take care of whatever file structure or partition these were kept on in the EMMC?
cekren said:
Yeah, I used the Dual Boot image I downloaded a couple days ago from Techerrata (I used the one at the top of the list that had the most downloads, connection I'm on is blocking Techerrata so I can't get the exact name ATM) with burned with Win32DiskImager, popped in the card and turned on but it just hangs. I'll try clearing the dalvik cache with his CWM image and see if it fixes anything..
EDIT - Ok, I tried clearing the cache, but it gives me the following error:
E:unkown volume path [/data]
I checked the Mounts and Storage Menu, and it looks like I still have "/system1, /system2, /data1, and /data2" directories, did the 567 format.zip not take care of whatever file structure or partition these were kept on in the EMMC?
Click to expand...
Click to collapse
The format 567 zip was for clearing the partitions on internal memory (emmc). Those partitions you are looking at are on the SD card (system1, etc).
You might just try clearing cache with his cwm rather than dalvik cache. You also might get a better response posting your dual boot question on the dual boot thread. I don't know a lot about the dual boot.
leapinlar said:
The format 567 zip was for clearing the partitions on internal memory (emmc). Those partitions you are looking at are on the SD card (system1, etc).
You might just try clearing cache with his cwm rather than dalvik cache. You also might get a better response posting your dual boot question on the dual boot thread. I don't know a lot about the dual boot.
Click to expand...
Click to collapse
Sounds good, I'll try that. Thanks again for all the help, though!
One thing to note... the initial boot does take a while and sits on a black screen while the cache image and formatted. Racks has put that into the dual boots with loop mounting so each bootable system will have its own cache space and avoid overwriting cache data from nother ROM.
DizzyDen said:
One thing to note... the initial boot does take a while and sits on a black screen while the cache image and formatted. Racks has put that into the dual boots with loop mounting so each bootable system will have its own cache space and avoid overwriting cache data from nother ROM.
Click to expand...
Click to collapse
Good to know, but should it really take more than 90 minutes to initially boot? I let it boot up to CM7 on a freshly burned Class 10 card and left for the store, when I got back it was still at the boot video, watched it for another 5 minutes and it still didn't do anything... I don't really know what the problem is, could it be the card?
I have seen it take up to10 minutes, but 90 is definately excessive... I would suspect the card being the issue... class 10 cards are not good for running any operating system from. While they have exceptional sustained read/write speeds... they (generally) have poor random small read/write speeds, and this is the types of files used by an operating system.
DizzyDen said:
I have seen it take up to10 minutes, but 90 is definately excessive... I would suspect the card being the issue... class 10 cards are not good for running any operating system from. While they have exceptional sustained read/write speeds... they (generally) have poor random small read/write speeds, and this is the types of files used by an operating system.
Click to expand...
Click to collapse
Oh.. ok, well good to know! I'll pick up a different card today and see if that will work.
I got the Mirage 7.2 to work, by writing the "generic_sd.img" to the card, the coping the .zip download to the boot partition (renaming it to "update-cm7-mirage.zip" so the generic loader would see it)...
I inserted the card, booted, and Tux showed up and it ran through partitioning the card, expanding the mirage zip, and shutting down. However, when I turned it back on, it showed the Cyanogen mod bootloader, and I selected "SD Normal" but Tux showed up again and it went through trying to partition again (which it said was not needed, so it skipped) and finding an update- / .zip file (which it deleted when it expanded it before), same with the SD recovery boot option... Should I just try a new card?
EDIT - So, I was sick of messing with SD card booting, and realized I really don't care if I have the stock OS on it anymore since my warranty is about to run out anyway, I just rooted it an installed Mirage 7.2 and it works! Thanks for the help with the SD Card problems, though!