Related
First of all let me say hello to everyone as I am new to here and that if there is a thread about this please point me there as I have searched far and wide and tried everything imaginable and nothing helped whatso ever.
I recently got myself the HTC touch with these specs
sapphire pvt 32b ship s-on g
hboot-1.33.0006 (sapp10000)
cpld-10
radio-2.22.19.261
I tried a tutorial I had found on how to flash it (Sorry in my frustration I lost the link for it) everything went well I know I had to get a file manager to activate an apk program for it then type in a code...after that it prompted to restart which I did and now it wont go past the vodafone loading screen.
its not bricked as I can get to the hboot screen still and I can go to the other screen the black one where you can wipe the card/ use the update.zip etc.
I took the sd card out of my phone to put the files needed onto it as my phone couldn't be mounted anymore and now when I put it back in I get the
can't mount SD card error (cant mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0) (no such file or directory)
so now it seems like I am royaly screwed here as my phone doesnt even read its own sd card...could I have accidently removed something from the SDcard which was needed for it to be recognized or is there a way to work around this
please can someone help me as I have been searching for a good 14 hours straight as I need my phone for work...
thanks in advance
Is the sdcard formatted as FAT32? Most come partitioned as FAT but all the tutorials say updating rom requires FAT32.
sorry I forgot to mention that yes it is formatted to FAT32, I did the format on the pc so I lost all the files that were on it, but as it is an sd card and not the internal memory it shouldn't have had any information on it required to mount it otherwise if I would get a new sd card it wouldn't work
the sd card that came with mine btw is an 8gb micro SD HC
I have a normal 2gb Micro SD but it doesn't read that one either.
so in otherwords I have just flashed my phone with the flashrec-20090815.apk which then asked to restart...I did that and then wiped before the backup, which should only mean I cannot go back to the stock settings unless some other dutch vodafone magic user would be so kind as to send me his nandroid backup
but other than that I would really like to figure out why my phone can't mount the SD card, either of them
EDIT: When I searched around the net about can't mount SD card error (cant mount /dev/block/mmcblk0p1 or /dev/block/mmcblk0) (no such file or directory)
I found that every other person that has this problem is a HTC dream user which makes me think I accidently got a Dream file flashed to my phone, yet wouldn't just the right sappimg.nbh be able to return things to normal? Or is this just wishful thinking...
Well second this story from me. I have the exact problem as you have. Hope someone will stumble upon this thread and give us guidance..
//N
well I don't know how much of a difference it makes but I just got both fastboot AND ADB to work, at first only fastboot worked for me, so now when I am in the recovery screen I can put adb commands in even though it is not started up fully (Cant get past loading screen yet)
hmm...latest update, I think I did something horribly wrong now...it no longer goes into the recovery-RAv1.2.1G screen (The black screen with green words) it now brings me to a different recovery screen, the one with the phone and the exclamation (!) mark
As long as you can go into fastbood hope is not lost.
Did you already do an SPL update? if yes you can just install any rom you want.
try to put an rom (lets say cyanogenmod) via microsd to usb adapter on the drive and call it update.zip.
Get this tools: http://www.megaupload.com/?d=EZU065GP
You need to install the USB driver for the phone if you not already have.
Connect the phone to the PC and boot you phone by holding "Back" and "On" into fastboot.
then run the "Boot Modified Recovery" script. Select "Apply sdcard:update.zip", make an wipe and the Phone start normally with the rom you selected.
It would be very helpful if you write would you already did to the phone.
ok, first things first...tired the program you sent me (Awesome by the way thanks) but the SPL I am using is a non engineerings spl meaning I cannot actually DO anything in fastboot
so without being able to start my phone up fully or use adb (I Lost that option once the recovery part disapeared for some reason) it would be great to know if I can still change the spl to an engineering one.
and now for a long list of what I did in the order I did it in so you can tell me just where I went wrong and tell me if I screwed up my phone completey or not (if not I have a special insurance on this that I pay extra for and might...JUST might cover this problem)
anyways.
At first I looked for a theme for the phone when realizing it wasn't going to be easy, I needed to flash them which is nothing I had done before (Should have realized then an there not to do it, knowing my luck)
anyways.
I turned on the usage of unkown applications and turned USB debugging on.
I put the flashrec-20090815.apk and recovery-RAv1.2.1G onto my sd card as told by the tutorial I downloaded linda file manager (Or something around those lines) to activate the flashrec thingy...followed by using the recovery thing and then it said it needed to be restarted.
I restarted it into the recovery like it told me to do, everything was going perfect.
This tutorial did not say to make a backup first so I never did (ARGH i hate that part the most) it told me to do a wipe, so I did...followed by sending the update.zip (This part confused me as they did not tell me to have the update.zip on it.
So I popped the sd card out (This may be where I went horribly wrong) put it into the SD card reader and put the update.zip rom on it I wanted to use.
Put the SD card back into my phone, and then it went wrong, I tried to run the update.zip and it said that it could not mount the sd card do to the dev/block thingy I posted above.
I have tried everything against that, I wiped the card...tried to format it through the phone (Same thing, could not mount) I formatted it on the pc to FAT32 (I made sure it was 32) and still, no matter what I do it wont mount...
strangely though someone suggested using the sappimg.nbh somewhere else, I got it...put it onto my SD card, started up hboot and it read it, tried to apply it but it said something about my CID or something being incorrect...but that DOES mean that the phone reads my SD cards (Since I have a 2gb sd and an 8gb sd HC (The one it came with)) and both of them work for doing that, but the sappimg part doesnt work.
after trying that sappimg.zip one though also with no good results, I tried to get back into the recovery part for the adb so that I could try something someone suggested about mounting the sd card image thingy through that...but when I booted up the recovery I got the normal android recovery (the one with only three choices and the phone with the exclamation mark) meaning I somehow lost my recovery RAv.......
so that is what has been done, please, please, please tell me I didnt horribly screw things up...if someone can help me I promise never to mess around with things I don't know about...
odanion said:
hmm...latest update, I think I did something horribly wrong now...it no longer goes into the recovery-RAv1.2.1G screen (The black screen with green words) it now brings me to a different recovery screen, the one with the phone and the exclamation (!) mark
Click to expand...
Click to collapse
I was wondering what happen when you press both Home and Power buttons at this moment. What the phone shows. Is there any menu we can use?
Is the ADB recognizes the phone in recovery mode in this moment?
I am also having similar problems with my sapphire. I can fastboot to recovery rom but cannot mount the SD card I can use adb
/dev/block/mmcblk0p1 no such file or directory when I try to access sdcard.
I have tried 4 different sd cards with different partitions on them but it will not read any of them.
I have tried to restore a nandroid backup by using adb push to put the img files in /sdcard. I assume it is just using the phone internal memory as the sdcard does not mount. I have used adb shell to flash_image the nandroid img files but it still does boot up succesfully. Just hangs at vodafone screen...
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.
[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.
Alright, some of you may remember me because I show up once every few months trying to fix my Nook STR.
what happened:
I have the first gen Nook STR 1.0 bought it when it came out
used one of the first TouchNooters and had a permanent "Rooted Forever" screen
used some recovery tools but nothing worked other than me being able to have "Read Forever" back
I can boot some stuff from the sd card like Clockwork recovery and even the TouchNooter but can't get past that. Touchnooter does not "flash black" and I never get past the "starting up..." screen no matter what I do.
I have tried the 8 failed boots (several times) but no menu EVER comes up. I even tried a tool that used to be on here that simulated the 8 failed boots. Nothing.
It's 1.0 right now and I'm not sure if it can be updated to 1.1 just via sdcard. It'd be awesome if I could flash 1.1 on there and try that out though
Anyways, I would appreciate any help. If nothing works out, I'm willing to just ship to whomever wants to try it out, fix it up, and sell it.
With ADB over USB using CWR you can do some forensics and see what the damage is.
You may need to repartition and format some parts of the internal SD card.
The important thing is not to make things worse and destroy the personalized info in the /rom (p2) or /factory (p3) partitions.
Then you can fix up what is damaged, install the 1.1.2 update and restore the /rom
Renate NST said:
With ADB over USB using CWR you can do some forensics and see what the damage is.
You may need to repartition and format some parts of the internal SD card.
The important thing is not to make things worse and destroy the personalized info in the /rom (p2) or /factory (p3) partitions.
Then you can fix up what is damaged, install the 1.1.2 update and restore the /rom
Click to expand...
Click to collapse
I tried mounting USB via clockwork recovery but it didn't work. is that what you were referring to or is there a different method?
I mean ADB:
http://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Installing_ADB
http://forum.xda-developers.com/wiki/Android_Debug_Bridge
If you have a Linux system you can also mount the internal SD card over USB.
Alright, I'm giving it a shot right now
Actually, I have a question. The guide says that I need to have an adb daemon installed on the Nook and that the stock Nook doesn't come with it. Does CWR provide the adb daemon running on it?
There are a couple of versions of CWR floating around.
They all have adbd and have it enabled.
Some use ADB over WiFi, which is problematical, there being no way to select an Access Point.
The ADB over USB needs a driver installation on the host and cinfiguration.
I'm trying to figure out where my adbd came from.
This does not seem to be in any of the update images from B&N.
In any case, installing adbd is one thing.
It must also be enabled in init.rc and default.prop (inside uRamdisk).