Database Users

MT4G stuck at boot

Okay... my MT4G won't boot up.
I rooted my phone. I have s=off. That's not where the problem lies.
The problem is me being a dumbass. I tried getting the Netflix.apk app to work on my MT4G, and I read a guide where you had to mess around with something from the system file to trick the app into thinking your phone was a Nexus S. So, I tried that, and powered down my phone. Now it won't boot up past the "MyTouch 4G" logo.
I tried booting into safe mode, to see if I could go back in and change it, but it won't let me. Any ideas on how to fix this? Tried a factory restore, didn't work. Also not running a custom rom either - was still using the stock rom.

Reflash a stock-type rom?

Driveshaft said:
Okay... my MT4G won't boot up.
I rooted my phone. I have s=off. That's not where the problem lies.
The problem is me being a dumbass. I tried getting the Netflix.apk app to work on my MT4G, and I read a guide where you had to mess around with something from the system file to trick the app into thinking your phone was a Nexus S. So, I tried that, and powered down my phone. Now it won't boot up past the "MyTouch 4G" logo.
I tried booting into safe mode, to see if I could go back in and change it, but it won't let me. Any ideas on how to fix this? Tried a factory restore, didn't work. Also not running a custom rom either - was still using the stock rom.
Click to expand...
Click to collapse
Did you happen to make a backup to restore to? Other than that i think the stock image PD15IMG may be what ya need.

eqjunkie829 said:
Did you happen to make a backup to restore to? Other than that i think the stock image PD15IMG may be what ya need.
Click to expand...
Click to collapse
This will kill root and S=OFF. I wouldnt advise until we know that he OFFICIALLY borked his rom lol
@OP, What exactly did you edit??
Also, if you dont have a backup, i would try flashing this, its the stock rom + root and its debloated.
Also, factory restore would help because it only wipes /data and /cache
whereas you said you edited something in /system
Hope this helps!!

Yeah that sounds like a better idea, just flash a stock like rom after wiping caches data and system. And once you get it fixed make a backup or two, always a good idea to make one before changing anything important in the phones file system.

eqjunkie829 said:
Yeah that sounds like a better idea, just flash a stock like rom after wiping caches data and system. And once you get it fixed make a backup or two, always a good idea to make one before changing anything important in the phones file system.
Click to expand...
Click to collapse
Yep, and with nandroid, if something goes wrong with w/e system edit you are trying, you can restore /system only. opposed to wiping/reflashing or restoring the whole backup.
Basically, skv012a had the right idea here lol

And by stock-type I meant pre-rooted stock, maybe even debloated like Orange Glacier.

JDV28 said:
This will kill root and S=OFF. I wouldnt advise until we know that he OFFICIALLY borked his rom lol
@OP, What exactly did you edit??
Also, if you dont have a backup, i would try flashing this, its the stock rom + root and its debloated.
Also, factory restore would help because it only wipes /data and /cache
whereas you said you edited something in /system
Hope this helps!!
Click to expand...
Click to collapse
Tried to edit the build.prop file in /system - followed this guide and edited what it told me to (ro.product.model=Nexus S, ro.product.manufacturer=Samsung).
Also, tried to follow that guide in the link you posted, but when I go into recovery, I get a red triangle. I have to press volume-up and the power button to get anything to come up. Then when I do, all I get is this in blue text:
Android system recovery <3e>
Use volume key to highlight;
click power key to select
Reboot system now
Apply sdcard:update.zip
Wide data/factory reset
Wipe cache partition
Click to expand...
Click to collapse
And below that in yellow text is:
E: Can't open /cache/recovery/command
Click to expand...
Click to collapse

Driveshaft said:
Tried to edit the build.prop file in /system - followed this guide and edited what it told me to (ro.product.model=Nexus S, ro.product.manufacturer=Samsung).
Also, tried to follow that guide in the link you posted, but when I go into recovery, I get a red triangle. I have to press volume-up and the power button to get anything to come up. Then when I do, all I get is this in blue text:
And below that in yellow text is:
Click to expand...
Click to collapse
uh oh. ok, download pd15img, put it on the root of your sd card, and boot into hboot (volume down and power). it will automatically load the file, hit volume up to confirm when it asks, this will put you back to stock.

JDV28 said:
uh oh. ok, download pd15img, put it on the root of your sd card, and boot into hboot (volume down and power). it will automatically load the file, hit volume up to confirm when it asks, this will put you back to stock.
Click to expand...
Click to collapse
Uh-oh indeed. I did that, and when it went to load it, it said "no image or wrong image". Gives me the same error message it gives this guy (already Googled it to try and find a solution, no luck). I have a 16GB SanDisk memory card, FAT32, only about 1GB left. Would formatting it do the trick? I want to try and avoid that at ALL costs, but if I have to...
Sd Checking ...
Loading ... [PD15DIAG.zip]
No Image!
Loading ... [PD15DIAG.nbh]
No Image or Wrong Image!
Loading ... [PD15IMG.zip]
No Image!
Loading ... [PD15IMG.nbh]
No Image! or Wrong Image!
Click to expand...
Click to collapse
EDIT: Might also be worth a mention - I put my MicroSD card into an adapter, put it into my laptop, and looked around on the SD card. Found the "boot.prop" file that started the problem, opened it in Word Pad, and edited it so the "Nexus S" and "Samsung" were back to "HTC Glacier" and "HTC". Saved it, tried booting, but to no avail.
Which brings me to my next question, I have a boot.prop file in /system on my SD card, and a boot.prop file on the root of my SD card. Should there be two of these files? I looked at one in Word Pad, and it had a lot of mentions of CyangogenMod on it, even though I bought the phone brand new a month ago and NEVER flashed CM on it. Can copy/paste the contents of both boot.prop files and put them on here if it would be any help.

Driveshaft said:
Uh-oh indeed. I did that, and when it went to load it, it said "no image or wrong image". Gives me the same error message it gives this guy (already Googled it to try and find a solution, no luck). I have a 16GB SanDisk memory card, FAT32, only about 1GB left. Would formatting it do the trick? I want to try and avoid that at ALL costs, but if I have to...
EDIT: Might also be worth a mention - I put my MicroSD card into an adapter, put it into my laptop, and looked around on the SD card. Found the "boot.prop" file that started the problem, opened it in Word Pad, and edited it so the "Nexus S" and "Samsung" were back to "HTC Glacier" and "HTC". Saved it, tried booting, but to no avail.
Which brings me to my next question, I have a boot.prop file in /system on my SD card, and a boot.prop file on the root of my SD card. Should there be two of these files? I looked at one in Word Pad, and it had a lot of mentions of CyangogenMod on it, even though I bought the phone brand new a month ago and NEVER flashed CM on it. Can copy/paste the contents of both boot.prop files and put them on here if it would be any help.
Click to expand...
Click to collapse
now the issue unrelated to that file. you are sure you have pd15img.zip on your sd card? it CAN NOT be inside any folders. formatting won't be necessary

Lol, wow. >_> I'm a dumbass. I was unzipping the file, and putting them into the root of my SD card. Not putting just the zip file itself in my SD card.
Deleted all the files off my SD card I put on, re-downloaded the ZIP file, put JUST that on the root of my SD card. It flashed it, saw the bar on the upper-right hand corner do it's work, and pressed the power button when it was done to reboot.
Aaand, still nothing. Phone is still stuck at MyTouch 4G logo, and looping over and over.
'Bout to download this, and try to flash that. Would it matter any? Or have the same effect?

Yea try that then report back GL

Nope, no dice. >_> Couldn't even get hboot to attempt to flash it.

pd15iag.img
Sorry about the double post, just wanted to bump this up and update what I've tried.
1. Someone told me to push a recovery image via ADB
- Tried doing this. ADB recognizes my device, but says it's offline. I'm guessing it's because my phone won't actually boot up. I have to go into recovery mode (still getting red triangle) to get ADB to recognize my device in the first place - once I do that, it just says offline next to it. So I can't push anything via ADB.
2. Tried flashing a stock-like rom
- Last night, I tried flashing PD15IMG and it did nothing. Today, I tried flashing Royal Glacier, but it didn't recognize it. I had it on the root of my SD card (nothing else but that on there now) and it still tries to flash "PD15IAG.img" even though it's not on my SD card and I have no idea what it is. :\
EDIT:
Soooo, yeah. >_> I decided to try a new SD card. Brand new, been sitting around the house for awhile. Bought it at Radioshack when they were on sale. Loaded PD15IMG onto it, put it in, flashed it, and now my phone works. I guess it was a faulty SD card? I dunno. Glad it's working now - thanks everyone for the help.

[Q] Can you help a brother out?

I will post the long version here, mainly because I have nothing better to do.
Here is the situation. I bought a NC about 6 months ago. I rooted it using Auto Nooter. I have no idea what ROM I installed to be honest. I'm very much a novice at this. And I'm quite stupid to boot, I might add. It has worked relatively ok since then. The ROM seemed a bit buggy and I had some initial troubles with constant reboots, in addition to some basic things not working and way bogging the thing down, but in general it was ok. I haven't used it much since unless I was traveling.
Today....I was traveling. Traveling to BFE. As such, I decided to bust out my trusty NC and download a new book while I was waiting for my flight. I did so, and something went a bit haywire. It seems that somehow, without prompting, the device has restored itself to the stock B&N ROM (1.1 maybe?). Yet - the Android OS is still there. For example I can click on my task manager app in the lower left corner of the homescreen and it shows that all of my apps are running and I can even switch to them. But my homescreen is defaulted to the B&N one showing my eBooks and I can't figure out how to get my Android launcher back. I have tried to reboot and it does the Droid boot up but reverts to the same B&N home screen.
I was thinking about trying to update to a new ROM since it had been awhile and I figured there must be something better/more stable out there now - Honeycomb or whatever. I guess this is the kick in the ass that I needed.
So now here I sit in a hotel room in BFE. There are no restaurants open past 9. There are no bars. There IS a Super Wal Mart but I think I'm gonna pass on that.
I figured I would look into this. Where to start? Should I re-set this thing to stock and then just pick a new ROM and re-root? Can I do any of this without having a SD card slot in my laptop - just using a USB cable? Will I lose any eBooks that I downloaded?
I await your sage advice.

rooting actually means gaining super user access to the current android rom. B&N, i believe is Froyo, so you did not install any rom so to speak. you were probably just rooted.
I think the issue is with the launcher and not that it is back to stock. What happens when you long press on the home screen?
If you plan to do anything, you will definitely need an sd card reader.

If you autonootered, then you were running stock, but rooted. With a custom launcher replacing the stock launcher, it sounds like.
At any rate, you were probably hit with the automatic update to B&N 1.2 (which is Android 2.2, iirc.) You almost certainly aren't rooted anymore, but it may allow you to run any apps that you already had downloaded, just from the stock app launcher.
When you get an SD card reader, you can check out Manual Nootering. It's basically the same as the old Auto Nooter, but for B&N 1.2. If you change the rom entirely (install CM7) or just run a different rom from an SD card, you'll avoid having B&N overwrite your root access in the future.

Thanks for the responses. I believe that you are correct. I actually was running 1.0.0. I used auto-nooter to root the thing and had it working with a custom launcher. I don't think it updated to 1.2. In fact I know that it didn't update to 1.2. I am trying to get it to do that right now.
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
I could Super Wal Mart tonight for a SD card reader if I'm feeling frisky.

I've got all kinds of problems.
I went to update to 1.2 from 1.0. I removed my SD card and erased and deregistered device. I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Any advice?

I'd do a full factory reset, then try the update to 1.2 again.
A couple of things about the 1.2 update -- do not unzip the update file or rename it. Just drop it as-is into the nook. And make sure to eject the nook from your computer and unplug it.

Thank you aka. I got it to take. I am now at 1.2. Now back to square 1(.2). Any help on this?
Baboontyme said:
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
Click to expand...
Click to collapse

Baboontyme said:
I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Click to expand...
Click to collapse
ETA: lol, congratulations! I guess just skip to that link at the end.
I'd agree with akaCat that you should do a factory reset, BUT you can only do that if you still have the stock recovery utility, and it seems possible that you do not. Try to get the NC to reset by interrupting the boot 8 times. If it doesn't work, you may have installed ClockworkMod Recovery on your Nook Color in place of the stock recovery utility. You may have done so while rooting, or later from the ROM Manager app, perhaps even by accident.
Have you attempted to boot to recovery by holding down "n" while you power on the device, and continuing to hold power + n for about six seconds (1-one-thousand, 2-one-thousand, etc), then releasing both? If so, do you get a factory reset dialog (series of yes/no options) or a longer menu including items like "mounting and storage" and "flash zip from sd card?" If you get the longer menu, then that's ClockworkMod Recovery, and neither the 8-failed-boots-reset nor the automatic update are going to work.
If you do have ClockworkMod Recovery, don't do anything yet. Hopefully somewhere on the screen it tells you the version number, in the format 3.0.x.x. Just let us know that version number and power off the NC.
If you still have the stock recovery utility, then do the factory reset, boot into the stock OS, connect USB, drop the update file straight on the Nook (not in any folders), safely remove the NC from your PC, and let it sit. Hopefully it will reboot itself.
If not, the next step is probably going to involve preparing a bootable ClockworkMod SD and manually installing a CWM-compatible version of the update, or of a different ROM. This article may help you wrap your head around the different options: http://quinxy.com/guides/how-to-pick-your-nook-color-operating-system-and-install-options/
ETA: lol, congratulations! I guess just skip to that link at the end.

Thank you, Tao. I seem to be a bit stuck, though.
I'm at 1.2 stock. I was able to reformat and erase my sd card. I went to load the .gz image onto the card (for CM7, per instructions here http://forum.xda-developers.com/showthread.php?t=1000957) and I also loaded the nightly build. Then inserted card into NC and booted. Nothing.
Any idea what I'm doing wrong? Should I unzip either file?
One thing that might/might not matter....when I went to eject the SD card from my PC, I wasn't given that option so I just pulled it.
One more thing.....the instructions at the link above instruct you to "write the image to your SD card" but then go on to say "eject the SD card" and then further "insert the uSD card into your computer"
Huh?? Isn't it all on the same card? Why do I need two different cards? What am I missing?

This blog breaks down the same process a little more step-by-step, with videos: http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html
You can skip the long preamble down to "Ready? Let's get started."
You do need to unzip the disk image, and write it to the SD using a program like Win32DiskImager or WinImage. It's also definitely a good idea to safely eject the SD card from your PC.

Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!

Can someone also tell me how to access the book I just purchased and was in the middle of reading? Do I have to go somewhere and re-download?

Baboontyme said:
Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!
Click to expand...
Click to collapse
I should add that though I can get CM7 to boot, I never get "The Power of Reading". It's just kind of a flash.

That's all normal--verygreen had to make a new uboot, which no longer shows "The Power of Reading" and also flies through a recovery boot so fast you could miss it. If gapps didn't install, just make sure the .zip is still in the boot partition and keep trying. I'm pretty sure holding power > reboot > recovery boot works now from within CM7, but I would go into Settings>Accounts and try to sign in to Google before assuming it didn't install.
If the book was a B&N purchase, once you have the market working, just install the Nook app and sign into your account, and you should be able to re-d/l the book, possibly even still synced to where you left off.

Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?

btw, you can also boot into recovery through rom manager, its easier.

Baboontyme said:
Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?
Click to expand...
Click to collapse
You can overclock: http://forum.xda-developers.com/showthread.php?t=925451
Just make sure you grab the version for SD, and install it just like gapps, then set clock speed via CyanogenMod Settings>Performance>CPU
boxcar8028 said:
btw, you can also boot into recovery through rom manager, its easier.
Click to expand...
Click to collapse
Easier than holding power a sec, poking "Reboot," then "Reboot to Recovery?"
Really, it's about the same either way, depending how handy ROM manager is on your system.

[Q] So I got myself in a bit of a jam trying to update to the newest nightly...

A few days ago, I received my Nook and used a youtube tutorial to install CM7 to SD. All went well (i'm in love with the thing), however I decided I wanted update past the last stablae release that I initially installed in order to use the Nook Tweaks app. Here's where the problem came in...in my Noobishness, I didn't yet know there were differences between updating on the image that I was told to use on youtube (Generic Nook-2GB-SDCard-CW3010-VGCM7InstallerAsALTinMultiBoot-v6.zip) and the other ones i've seen around. This led to mass confusion and a really silly error...and this is where I need help.
I ended up taking the update, and putting it on the same partition that my media is on and installing it from Clockwork Recovery. Don't ask me where I got the idea, because I don't know. I've since read enough to understand that that was NOT the correct thing to do. It updated and messed up my emmc. I can boot up CM7 just fine from SD card, however when I boot into stock Nook, it doesn't happen and boots into Clockwork Recovery. What's the best way to get the emmc back to stock, and still keep my SD Card in tact and then upgrade to the latest nightly? From what I understand, installing updates is actually really simple with this image...drop it on /boot, then boot up in SD/Alternate? Also, is there any reason I shouldn't update to newest one?

I know what you are going through.
A lot of the information out there regarding the installation of CM7 is outdated, unintentionally cryptic, or in rare cases just plain wrong. It is because of this that I have been very reluctant to move from a stable SD based CM7 to EMMC.

@OP, your case, 2 separate issues
1. Getting your NC back to stock
2. Getting CM7 update on your uSD.
Item 2 is fairly easy and a lot less hassle than item 1.
Item 2: assuming yr bootable uSD is still good, copy the CM7 nightly build into the root folder ("boot" partition), remove the uSD off the PC, insert it into the NC, booting up.
It will go straight in CM7, wait until it finishes loading, then reboot and select "recovery" option. Now, sit tight and let the NC does it own thing (you do not have to do anything else) until it shut down. You then power it back on. That's it.
Item 1: search for the "Stock 1.2" thread in this forum, download the file, read the instructions how to restore.

votinh said:
@OP, your case, 2 separate issues
1. Getting your NC back to stock
2. Getting CM7 update on your uSD.
Item 2 is fairly easy and a lot less hassle than item 1.
Item 2: assuming yr bootable uSD is still good, copy the CM7 nightly build into the root folder ("boot" partition), remove the uSD off the PC, insert it into the NC, booting up.
It will go straight in CM7, wait until it finishes loading, then reboot and select "recovery" option. Now, sit tight and let the NC does it own thing (you do not have to do anything else) until it shut down. You then power it back on. That's it.
Item 1: search for the "Stock 1.2" thread in this forum, download the file, read the instructions how to restore.
Click to expand...
Click to collapse
Thanks so much, man. This all seems pretty simple, i'll fix it all tonight. One question though, i've got the part where I drop it in boot...but when I power it back up, I select to boot it in SD/Recovery? Or do I boot it in SD/Alternate like what I used to put the stable version in?

[q] excited to see twrp 2.0 recovery on our beloved nookcolor!

Ok. Let me start by saying, I'm obviously not an expert on hacking/developing and stuff like that. I just love to tinker stuff so I learn in the process. So definitely not an expert. Just posted this thread hoping that someone whose possibly a lot more knowledgeable than I am would notice it and hopefully shed a light on this question.
Is TWRP 2.0 which can be seen here, working/compatible/available/will be available on our beloved NookColor?
All we are using right now is the ClockWorkMod Recoveries, right? Which I believe the latest is 3.2.0.1. I'm not saying at all that CWM is not sufficient enough to do whatever it needs to do, I just thought it would be awesome to be able to get your recovery things done THAT MUCH COOLER, navigating the device via the touchscreen rather than hardware buttons.
Hope this sparks more awareness!

+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.

majorpay said:
+1 - I would like to see TWRP on our devices as well, BUT ... I would definitely miss the convenience of being able to install the nightlies directly from ROM manager.
OK, saying that, I also just had a perma-brick on my Nook and am getting a replacement due to an issue that occurred in recovery. I was stuck in the infamous CWR boot-loop, so did a restore, when I went to reboot, screen itself would never come on again - not after charge, not after holding buttons, nothing.
Is it related, I don't know, maybe not, but makes you think.
Click to expand...
Click to collapse
Oooh, that's too bad. And scary. Makes you worry about doing something that's not tried on the NookColor before. I wont dive in unless the devs really says that it's safe.
Hey, about your NC being bricked. I had something pretty similar happened to my NookColor before. Got stuck into a boot loop. Now before, I had my TitaniumBackup folder stored in the eMMC and I didn't want to do anything that would delete it. What I did is, I had another microSD card and created a bootable CWM. I installed a CM7 nightly on the microSD. Upon booting to the microSD build, I went and have adb wireless transfer my eMMC files to my PC. Now that I've recovered my TitaniumBackup folder, I formatted everything on my NC using the bootable CWM. Then what I did is I flashed the stock NC Rom which was 1.2 version. I did a factory reset. After that I had everything back to normal again. I flashed the nightly build on the eMMC again and from then on, had my TitaniumBackup folder on the microSD. Have you tried creating a bootable microSD?

A little late...
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.

fr4nk1yn said:
Did you try a formatted bootable sdcard? The nook is near indestructible. I had the same issue and recovered.
Click to expand...
Click to collapse
Same here, I put together a nookie froyo card, and got bootloops.I took the memcard out and still got bootloops. I put a cwm card in, and STILL got bootloops. Then I made a new cwm card, and it booted just fine.

[Q] Cannot boot into anything, including CWR

Well, after a few weeks of reading posts, even opening up the hardware and taking the nook apart, here I am asking a question. I figure I would go to the source rather than those other place I was reading and tryign to get info from (mot os those places link here anyway). I know that everyone says that the nook is "unbrickable;" while I want to believe it, I may be in a place where it may be true.
I do want to add a thanks as well, since the NC "tablet" has been very handy, and my wife and I have really enjoyed it. Wouldn't have happened without you all. I wish I had more time to participate in developing, but working 80+ hours/week in a hospital limits my free time, as you can imagine.
I rooted the NC and installed Cyanogenmod 7 back in July 2011. It was a 1.1 model (if I recall correctly). I installed the mod to EMMC, along with CWM. Things ran fine for 6 months. Literally no issues. Then, one night the battery was dead, so I plugged it into the computer USB to charge while the machine was off. Didn't touch it at all. When I went to turn it on again, I was stuck in a bootloop. It would go to the cyanogenmod screen and say "Loading" then would start over again. So, I naturally made a bootable SD card, and tried going into CWR to fix things. However, the SD card had the bootloop as well. It would get to the two skulls and "Loading", flash blank, then start over again.
That went on for a while. I couldn't boot into anything, not into recovery, alternate images, literally nothing. So, I tried different images --- nothing. Finally, I did the power+n and got into the only screen that wouldn't keep resetting. It has blue text and says "Entering boot menu". The menu says "Encore U-boot Menu by j4mmr. 1.2 port+ extras by fattire." From this screen, I can navigate and change the boot options. However, once again, whatever I try does not actually boot, regardless of what I set it to. The only thing that I got from getting here was no more boot loops. After getting it to this point, I can try loading anything, and it will start, then the screen goes black/blank, and nothing happens. Left it on for hours to test.
Since that point, I have switched cards (SanDisk 2 GB class 4, Patriot 8 GB and a generic 8 GB microSD). I know that cards work correctly because I got a hold of a second nook, and they work fine on it. Below are a list of all the images I have tried to run off the SD. Again, nothing will boot, not even clockwork recovery/clockworkmod.
128 mb rootpack (IOMonster)
clockwork 3.0.2.8
clockwork 3.2.0.1 eyeballer
Nooter
Mirage_CM7_ICS_CM9_DualbootSD (this card works great on the working NC)
TWRP 2.0 RC0
Generic SD
Clockwork 0.7 -> starts boot loops again
I also tried ADB, connecting to the computer and using putty over SSH. Didn't work. 8 interrupted boots with 9th holding power+n. Nope. I even took the nook apart and disconnected the battery. Still no go.
If I recall, I think I had CWM 3.0.0.5 installed to the card and to the emmc.
If anyone has any other ideas, I could really use the help. I consider myself pretty computer literate (build my machines, coded in my spare time in the past, hacked a lot of my electronics). I have read many guides/sites and even tried the outdated stuff. Once again, I cannot get into clockwork recovery, so any guide that says to do that as the first step will not work. I also cannot boot off of the SD on cards that I know function.
Would using an older version of CWM (prior to 3.0.0.5) work? I think I remember reading a bunch of stuff about problems people were having with that version. The thing is, I wasn't installing or flashing anything new. I wish I was, because then I would know what was happening when everything got screwed up.
Thanks a bunch in advance for your guy's (gals?) time. This has been really painful.

Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP

Yeah, it has been frustrating, especially not knowing what happened in the first place. I actually did try the version from that first link (where I put 3.0.2.8). Again, the big issue I am having is that I cannot even get into the CWM. If I could, I could fix it. I also saw and read through that xda thread you kinked to (open right now in my browser), but the problem remains that I cannot even get to the point where I can flash something.
Thanks at least for responding. I'll try a few more things and see if it works, but I am running out of ideas.

In theory creating a bootable CWM card will get you into recovery even though you can't access the Recovery on the internal. Once you reach Recovery from the SD card you can flash whatever you need. It is just a matter of making a bootable recovery card that boots far enough to get you there.

In theory, yes, but as I said in my first post, I tried all the bootable cards without any luck. When I try to set the SD card as primary boot from that one screen from fattire, it locks and never restarts.

J515OP said:
Wow, that must be frustrating. First make sure you didn't change the boot settings to something other than the SD card when you were in the boot menu. As long as the Nook is powering on and doing something you can probably save it from being a brick.
I would start with a newer version of ClockWork Mod Recovery here: http://mrm3.net/blog/2011/03/11/nook-color-updated-clockwork-recovery-bootable-sd/
There is a contradiction in the file names but the actual version should be 3.2.0.8. If that doesn't work then you may want to go back to an older version. In that case I would still load a newer version's zip file onto that card, so that if you do get the older version to boot you can use it to flash the newer version.
Before going back to older CWM versions though give this a try if the new CWM above doesn't work http://forum.xda-developers.com/showthread.php?t=958748
JP
Click to expand...
Click to collapse
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.

DigitalMD said:
This happened to me a couple of times on CM7. Don't know why, but I believe I used the last method listed to repair it. There was an older version of CWM that would cause this sometimes. When you get it going again, you must update CMW to the new one.
Click to expand...
Click to collapse
How did you get it to boot into CWM in the first place in order to flash? That is my current problem. Any method of fixing relies on the ability to boot into CWM from the SD card, which (for whatever reason) isn't working at the moment.
Well, tried to use the native Nook u-boot. Get the "Touch the Future of Reading" screen, then black, just like with any of the other cards. On the good nook, it boots into a linux file and runs the recovery script, so it is not the card reader or the SD card.

Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.

czarofthefrozentundra said:
Well, still doesn't work. I guess I officially bricked it without even knowing what happened. Bummer.
Click to expand...
Click to collapse
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.

leapinlar said:
You said you tried eyeballers 3.2.0.1 CWM. Did you mean the 1GB image file he posted on his thread? And how did you burn the image to the card? You should be using win32diskimager running in administrator mode on Windows. And it is best to use a cheap card reader rather than any card reader built into your PC. The nook can be really finicky about how the card is written.
Click to expand...
Click to collapse
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.

czarofthefrozentundra said:
Yes, I tried that image from his thread. I always use win32diskimager and use a card reader. I have working cards (I have a second NC that runs fine); there is just something wrong with the boot process, and I cannot get into CWR to fix it. It starts, but then never makes it in or reboots. Only time I can keep it from rebooting is by holding "n" and going into the boot option menu.
Click to expand...
Click to collapse
It goes to the boot menu when you hold n with eyeballers image burned to SD? What happens when you select SD and normal? Just a hang? With 'loading' showing?
Edit: I just thought of another reason that could be causing this. There is a flag set in /rom that tells the system to try to boot into recovery. It tries no matter what you tell it to do in the boot menu. ROM Manager uses that flag to boot to recovery when you tell it to. Then after you successfully get into recovery and exit it by telling CWM to reboot, CWM clears that flag. If your recovery is borked up, you never get that flag cleared and it's an endless loop.
There are two solutions I can think of. First, use racks dual boot SD that you already have and go into the boot menu with that. Tell it to go to SD and recovery. Hopefully his recovery will load. Then immediately exit by the menu. That should clear the flag. If that fixes it and it boots to CM7, go to ROM Manager and flash a new CWM to emmc.
If that does not fix it search xda for 'fix recovery'. There is a nook thread telling how to fix the recovery on emmc.
Edit2: I just thought of a third way to try to get it to boot. Take eyeballers 3.2.0.1 CWM SD and put it in your PC. There should be two files there named uImage and uRamdisk. Make a copy of them on the SD and rename the copies to uRecImg and uRecRam. Then put back in nook and reboot to see what you get.

Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.

czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
See my edit2 above for a third way to try to clear the flag.
Sent from my NookColor running ICS and Tapatalk

czarofthefrozentundra said:
Hmm. Thanks. I'll definitely give it a shot (got nothing to lose at this point). I'll get back and let you know if it worked or not.
Click to expand...
Click to collapse
Hello? Feedback?
Sent from my Nook Color running ICS and Tapatalk

Ha, I tried the quick reply function, and it didn't work. Here is what I wrote yesterday (verbatim, since I still had the window open):
"Well, so far no luck. Here is what I have tried, and the new information that I learned.
Used dual boot SD that I know works and booted into bootloader menu. Tried all different options on the SD card. What happens is that it thinks for a bit, then turns the screen black, but the boot screen never comes up (i.e. the Cyanogenmod logo that usually starts before things boot). So there must be some problem there.
If I hold down power, it will restart. Again, the screen turns black after the loading screen is on for a while (happens no matter which image I burned to the card).
I still need to try the other method (eyeballer one). I don't think the EMMC reset will work with my particular issue, as I had read that thread earlier."

czarofthefrozentundra said:
I still need to try the other method (eyeballer one).
Click to expand...
Click to collapse
If the problem is the recovery flag, the mods to the eyeballer CWM SD should work. If it does not work, it may be something else. If it does work you can flash a new CWM to emmc using another eyeballer zip. Get it here:
http://forum.xda-developers.com/showthread.php?p=21932561
You would want the first choice.
Sent from my Nook Color running ICS and Tapatalk

Cool. Will give it a try tonight and report back. Just have to find my spare SD card.

So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?

czarofthefrozentundra said:
So, tried with the eyeballer, and I couldn't get it to work. One thing I did notice, though (actually by chance) is that even though the screen is black, the nook is on. I saw this because it all of the sudden started flashing the low battery screen and then turned off.
Anyhow, still looks like I am in the same position. The EMMC fix doesn't work for me because I cannot even boot of an SD card.
EDIT: Actually, I just reread your post. I didn't do it right. I am going to try again and report back.
EIDT 2: Nope, didn't work. Do I need to hold all the buttons down while booting or do something else special?
Click to expand...
Click to collapse
I'm not sure what to tell you to do next. I guess I am going to send you to a post that tells pretty plainly how to do the 8 failed boots. I know you tried that, but timing is very critical with that procedure. Worth a try to me.
http://forum.xda-developers.com/showthread.php?p=25405429

How do you do the 8 failed boot deal with the cyanogenmod screen running. I am not sure about the timing of things. Also, which buttons? I have seen people do it with just the power button. Other places say with the power+n+vol up.