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.
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.
I have 2 SanDisk 4 GB Class-4 uSDHC that I can't install using evergreen's installer (V1.3) http://forum.xda-developers.com/showthread.php?t=1000957. (I'm installing to the card)
I have tried using 2 NCs (OS 1.2 / 1.3).
I also have a PNY 2GB Class-2 (unmarked) which works well (CM7.1.0 and CM7.1.0-rc1), and a PNY 8GB Class-4 which doesn't work.
I tried cloning the installed PNY 2GB to a SanDisk but that loops during boot (which others have experienced). My guess is some of them have had write failures during install, which they have not seen on the screen. The install does not stop - so you would need to watch carefully.
The issue is write failures during the install. The output is identical to many posts on the web for other devices, and as discussed in http://forum.xda-developers.com/showthread.php?t=1122185, and http://openpandora.org/pipermail/firmware-dev/2011-May/000140.html.
http://68.183.106.108/lists/linux-omap/msg40248.html is also interesting.
Is our mmc built from public source - if so could you point me to the appropritate file?
Thanks
I do not think you can just move your files to a new card... Have you tried just making a fresh card and then restoring your apps and data using titanium?
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
I didn't move the files, I cloned the card.
ie Use Win32DiskImager to read the disk into a file on computer and then use that image to write the new card. That preserves all of the structure of the device. In the case of a larger card you can stop at that, in which case the space beyond the 4th partition is wasted. Or you can extend the 4th partition using something like Paragon Partition Manager 11 (free). I have used that same (2GB) image file to rebuild and boot the PNY card without problem.
When the cloned card was booted, the CM7.1.0-RC1 kernel and everything else was known to work on the PNY card - the only thing that had changed was the brand of card.
The point of this post is not about the cloning, it is that the Install to card fails on SanDisk 4GB Class-4 (the kernel that is running at that time is the installer).
I have used 2 new SanDisk cards that work when inserted in the NC running B&N NookOS. I have also given them a thorough check with ChkFlsh.
I believe these cards expose some timing information that the MMC can read and use to determine timeouts.
Is it possible to configure the vergreen installer to log such that I can capture it with adb logcat, so you can have a clear picture of what is happening during the install. I had adb logcat running during the install, but there is no output (it didn't attach).
Out of curiosity, I rebooted the broken install with adb logcat attached. Looping is around the skateboarder running in and doing a couple of cicuits. The log is attached. There are lots of files not found (/data/data seems to be missing), in line with the errors during install.
I also attach an anaysis of the SD card done from linux. The 3rd partition was completely hosed (failed fsck).
Interestingly, I have just repeated the clone experiment. (2gb PNY -> 4gb Sandisk with no extension of the 4th partition - but this time using CM7.1.0 (Release)). It has booted cleanly. Has anything changed in the kernel to address this problem? If yes there may be a need for verygreen to update his loader. I will leave the SanDisk running for the next few days.
HTH
I have a new-to-me Nook Color running the 1.4.2 firmware. I did a factory reset and set up my Barnes and Noble account. Yay me. However I can't FOR THE LIFE OF ME get it to boot off the SD card.
I've tried two 2GB cards (Samsung & SanDisk) and one 8GB SanDisk card. Also used three different card readers to burn the .IMG. What am I missing? I stick them in the Nook and the Nook just boots up as normal without hesitation. I've been rooting cell phones for years but this tablet has me stumped.
Is there another option I can use to flash CWM? Once I get it flashed I'm sure flashing the ROM is a breeze...
EDIT: After more and more digging, it might be an issue with writing to the wrong partition. How can I check to see if I'm installing to the write partition? I've formatted my cards multiple times. This is the stuff I see in a lot of answer posts:
of = /dev/disk# (good)
of = /dev/disk#p# (bad)
Click to expand...
Click to collapse
have you wrote an sd card that will boot (ie. Clockwork 4 gig et al). Can you read and write to it from within stock? More data please, what were you writing to what partition?
When I use the uSD card to boot and it is plugged into the computer you should hear three da-da-das.
n8nmad said:
have you wrote an sd card that will boot (ie. Clockwork 4 gig et al). Can you read and write to it from within stock? More data please, what were you writing to what partition?
When I use the uSD card to boot and it is plugged into the computer you should hear three da-da-das.
Click to expand...
Click to collapse
I have never successfully created an SD card that will boot on the Nook. Outside of the Nook, I have no way of testing to see if works or not.
You asked what partition, but I only have one partition on the card. If I open up the card in Disk Manager, there's just one allotment of space. When you burn the Image, is that supposed to create a separate partition that's visible in My Computer? If so, that's not happening because all the data is in one spot on the card (from what I can tell)
You need to flash the card. I suggest starting here:
http://forum.xda-developers.com/showthread.php?t=922870
or any of the other dev threads dealing with dual boots or whatever it is you are trying to accomplish.
Does your stock nook format sd cards to write books and such? If not that would be a big clue that it is a hardware issue
n8nmad said:
You need to flash the card. I suggest starting here:
http://forum.xda-developers.com/showthread.php?t=922870
or any of the other dev threads dealing with dual boots or whatever it is you are trying to accomplish.
Does your stock nook format sd cards to write books and such? If not that would be a big clue that it is a hardware issue
Click to expand...
Click to collapse
Yes, the stock Nook picks up the cards and formats them when installed. I've used these cards for all my smartphone rooting without any issues.
I've also formatted the cards and burned the CWM images using the windiskimager tool. It's just not bootable for some reason
The very first fundamentally step is to check whether it is a NOOKcolor or Nook Tablet.
votinh said:
The very first fundamentally step is to check whether it is a NOOKcolor or Nook Tablet.
Click to expand...
Click to collapse
Holy balls, I feel like an idiot. I had no idea the two were so similar. I am almost certain I have the Color (going by what it says on the case) but I'll look closely when I get home
It's the Nook Tablet. Wow....just...wow
On the bright side, at least my technical experience isn't the problem. My common sense on the other hand...
I believe you still can root the NT or run the pre-alpha ROM from it.
Unsure if it's able to run from uSD yet or not.
[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.