"Sorry, I'm not quite following 100% because you have a lot going on in your posts. I'll try and read more carefully but it appears you are getting it to boot into CM7 and then when you start trying to install apps it dies and you get stuck at a black screen. I am wondering if you have good downloads of both CM7 and Google Apps. Have you checked the MD5 Sum to make sure you have a good download of each? You may want to try deleting the files you do have and downloading from scratch. Also take a minute to check the files to make sure you are not getting corrupted downloads.
Once you get booted to CM7 you should be good to go. It is unusual to have problems once you get that far. Also just to make sure once booted into CM7 you are leaving the card in correct? If you take it out you will crash since the OS is actually running off that card.
JP"
Yeah, too much info; I meant to come back and slim it all down when I had nailed down my notes. Been busy getting my taxes done.
Yes leaving the card in. Also tried redownloading the files. Checked the downloads as well. I was also going to wait a week or so for new versions just to make sure.
basically what happens is it all works fine for a awhile, but when I reboot the 2nd or 3rd or 4th time (despite cyanogen coming up), the boot partition can't be found whether I try to go to Android or recovery. once in a great while I get get it back to boot into android (I'm developing attraction issues about robots on skate boards) all is happy but then on the next boot gone forever. this happens regardless of whose process I use (agnostic sdcard, dual boot, triple boot) or what SD card I use (16gb, and a couple of 2gb cards). The cards are all sandisk class 4 bought at various times over the last year or so
I was originally adding the apps in later and thought that was the problem, so I added them in at the same time following yet someone else's other process - worked for a longer time, but rebooted a couple of times and back to black. I eventually left the apps out completely (thinking it was them), and have the same problem with no apps at all. So it's at the earliest step after the boot that actually builds the andorid OS and the first time wizard.
Have tried all the sdformat, format in the nook and then burn, different burn progs and even a different PC processes; and it still works/fails the same way.
From what I had read it may be my micro SD adapter setup; I have the sd card the micro plugs into, and then a sansdisk sd card to usb.
Going to try today from a laptop that can use just the SD adapter to micro and see if that helps; that at least removes the SDCARD to USB.
NOW I wish I had bought some of those cheapy MicroUSB readers off a deal site, I've seen a couple of posts where the poster said using one of those worked when the better ones failed.
Haven't fond one at a dollar store or wallyfart, but after today I may try that.
YEARS ago I have a memory of some other system (sadly could have been really old DOS, it's that dim of a memory) where you would get intermittent boot problems because the boot partition wasn't actually marked primary and/or active. You could get boots, but the deal was THAT was the fluke, not when it failed. Failed was actually the way it should have worked because no primary and/or active had been correctly set.
This is exactly like that, but when I check with Easeus the first partition is active and I don't know how to check the android two.
Once you get booted to CM7 you should be good to go. It is unusual to have problems once you get that far. Also just to make sure once booted into CM7 you are leaving the card in correct? If you take it out you will crash since the OS is actually running off that card.
JP"
Yeah, too much info; I meant to come back and slim it all down when I had nailed down my notes. Been busy getting my taxes done.
Yes leaving the card in. Also tried redownloading the files. Checked the downloads as well. I was also going to wait a week or so for new versions just to make sure.
basically what happens is it all works fine for a awhile, but when I reboot the 2nd or 3rd or 4th time (despite cyanogen coming up), the boot partition can't be found whether I try to go to Android or recovery. once in a great while I get get it back to boot into android (I'm developing attraction issues about robots on skate boards) all is happy but then on the next boot gone forever. this happens regardless of whose process I use (agnostic sdcard, dual boot, triple boot) or what SD card I use (16gb, and a couple of 2gb cards). The cards are all sandisk class 4 bought at various times over the last year or so
I was originally adding the apps in later and thought that was the problem, so I added them in at the same time following yet someone else's other process - worked for a longer time, but rebooted a couple of times and back to black. I eventually left the apps out completely (thinking it was them), and have the same problem with no apps at all. So it's at the earliest step after the boot that actually builds the andorid OS and the first time wizard.
Have tried all the sdformat, format in the nook and then burn, different burn progs and even a different PC processes; and it still works/fails the same way.
From what I had read it may be my micro SD adapter setup; I have the sd card the micro plugs into, and then a sansdisk sd card to usb.
Going to try today from a laptop that can use just the SD adapter to micro and see if that helps; that at least removes the SDCARD to USB.
NOW I wish I had bought some of those cheapy MicroUSB readers off a deal site, I've seen a couple of posts where the poster said using one of those worked when the better ones failed.
Haven't fond one at a dollar store or wallyfart, but after today I may try that.
YEARS ago I have a memory of some other system (sadly could have been really old DOS, it's that dim of a memory) where you would get intermittent boot problems because the boot partition wasn't actually marked primary and/or active. You could get boots, but the deal was THAT was the fluke, not when it failed. Failed was actually the way it should have worked because no primary and/or active had been correctly set.
This is exactly like that, but when I check with Easeus the first partition is active and I don't know how to check the android two.
Last edited:
