Not sure I can dig myself out of this one.

I noticed that my Incredible kept checking for errors on my sd card. I copied all files on my sd card to my laptop and reformatted the sd card in ClockworkMod Recovery.

I then rebooted and my Incredible was again checking for errors. I'd not noticed this at all before now, so I thought I had not yet solved the problem. I ended up erasing the sd card, and when trying to reboot, my Incredible went into a boot loop. I went back into ClockworkMod Recovery to try to manually mount the sd card, and I could not. My Incredible boot loops with or without the sd card.

I went and bought another sd card and transferred my files from my laptop back onto my NEW sd card. Same exact problem. Card will not mount, and endless boot loops.

What I have is a brand new sd card with all my files on it, and my Incredible refuses to mount it in ClockworkMod Recovery, and will only boot loop endlessly if I try to boot up.

I'm so frustrated. Can someone help with some other ideas? If I could just get my card mounted, I can restore.

Thanks!!

Edit: I feel like a dummy. My sd card was not pushed in all the way. It will mount. However, my overall situation has not improved.

When I try to restore, here's what I see in ClockworkMod:

Checking MD5 Sums
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
E: Can't mount /dev/block/mmcvlk0p1 (file exists)
Can't mount /data/!

As a result, I still cannot achieve normal boot up.


Edit #2:

I went back to my original nandroid and restored, and apparently, that put back whatever files were bad and was able to boot!

Then I went back into ClockworkMod Recovery and flashed the latest CyanogenMod Nightly (#26) as of right now, and she booted up with NO LOOPING at all.

Can anyone say "ALWAYS MAKE NANDROID BACKUPS WHEN ROOTING!!!!!"?

I will admit I was about ready to cry over this!!

Just hope everything runs okay (sd card is still being checked for errors, but I'm more than happy to live with this now).

 

I understand why you say that... but the reason I noticed it checking the SD Card for errors is because there are a series of CM Nightlies that apparently are taking longer to process the *check*. I thought there was a problem with my card, but turned out to just be a process they haven't ironed out yet in CM7.

But you are right about the learning experience. NEVER ERASE AN SD CARD if you want to ever use it again.