Database Develop

G1 Hero flash strange problems

Alright there are a few people with the exact same problem as I, vr24 is one that can attest..
Basically I flashed JacHero2.63slowSD and it worked, but after flashing to another hero build (non slow sd), it would get to the screen unlock.. but when i pull that screen down all I see is a loading HTC screen. It never goes beyond that!
I have two seperate SD cards that were retabled, formatted, and set up using parted from cynorecovery 1.3.1. Both of them with full wipes and reflashes with any Hero build give me the same problem. Any non hero build works fine. The only big whoops I can remember is that I downloaded and used swapper even though i had it automatically set up?
I reflashed the phone all the way back to fresh start with dreaimg.nbh to rc29, rerooted, and installed everything properly and still have the same problems.
When trying jachero 2.5 i can at least get a root access request for swapper, which i deny. Anyone have any experience with this?

viccyran said:
Alright there are a few people with the exact same problem as I, vr24 is one that can attest..
Basically I flashed JacHero2.63slowSD and it worked, but after flashing to another hero build (non slow sd), it would get to the screen unlock.. but when i pull that screen down all I see is a loading HTC screen. It never goes beyond that!
I have two seperate SD cards that were retabled, formatted, and set up using parted from cynorecovery 1.3.1. Both of them with full wipes and reflashes with any Hero build give me the same problem. Any non hero build works fine. The only big whoops I can remember is that I downloaded and used swapper even though i had it automatically set up?
I reflashed the phone all the way back to fresh start with dreaimg.nbh to rc29, rerooted, and installed everything properly and still have the same problems.
When trying jachero 2.5 i can at least get a root access request for swapper, which i deny. Anyone have any experience with this?
Click to expand...
Click to collapse
Hit the back button, see if that loads up Rosie.

lukekirstein said:
Hit the back button, see if that loads up Rosie.
Click to expand...
Click to collapse
nope :[ just stuck at htc screen. i can hit end phone call to go to screen lock again, but when i pull it down back to htc screen

I would recommend then reformatting your SD card. Hero stores weird things on the SD card and can sometimes cause problems even between Hero builds (like in your case.) See if that works for you :]

lukekirstein said:
I would recommend then reformatting your SD card. Hero stores weird things on the SD card and can sometimes cause problems even between Hero builds (like in your case.) See if that works for you :]
Click to expand...
Click to collapse
i managed to format using both the panasonic SD tool, and tablerm on parted.. any other trhings i could do?

viccyran said:
Alright there are a few people with the exact same problem as I, vr24 is one that can attest..
Basically I flashed JacHero2.63slowSD and it worked, but after flashing to another hero build (non slow sd), it would get to the screen unlock.. but when i pull that screen down all I see is a loading HTC screen. It never goes beyond that!
I have two seperate SD cards that were retabled, formatted, and set up using parted from cynorecovery 1.3.1. Both of them with full wipes and reflashes with any Hero build give me the same problem. Any non hero build works fine. The only big whoops I can remember is that I downloaded and used swapper even though i had it automatically set up?
I reflashed the phone all the way back to fresh start with dreaimg.nbh to rc29, rerooted, and installed everything properly and still have the same problems.
When trying jachero 2.5 i can at least get a root access request for swapper, which i deny. Anyone have any experience with this?
Click to expand...
Click to collapse
does anyone think thtis could be because of an improper flash or when i activated swapper (even though swapper was automatic on jachero doh), it wrote some corrupted files in some god forsaken place that they cant write to now?
and if so, how would i wipe it clean? i reflashed to rc29 nbut im not sure i f that did the whole job

So if i intentionally brick my phone...

...the insurance company wont ever be able to figure out that i rooted it and come for money?
I downgraded to the original bootloader but cant get rc29 back on, i just get the gray screen to flash for a split second (it says 'no file...') i still have cyanogen 1.3.1 and i flashed ion to have something to work with but i read that i can pull the battery during a flash and just brick it. thanks

DMaverick50 said:
...the insurance company wont ever be able to figure out that i rooted it and come for money?
I downgraded to the original bootloader but cant get rc29 back on, i just get the gray screen to flash for a split second (it says 'no file...') i still have cyanogen 1.3.1 and i flashed ion to have something to work with but i read that i can pull the battery during a flash and just brick it. thanks
Click to expand...
Click to collapse
Are you sure that your sdcard is formatted to fat32? The no file found usually indicates that it isn't.

h.nocturna said:
Are you sure that your sdcard is formatted to fat32? The no file found usually indicates that it isn't.
Click to expand...
Click to collapse
good call thanks, i may have put it on the new card that came with the new phone, which i suppose isnt set to fat32 by default. But the boot flashed ok, would it do that if it wasnt fat32?

DMaverick50 said:
good call thanks, i may have put it on the new card that came with the new phone, which i suppose isnt set to fat32 by default. But the boot flashed ok, would it do that if it wasnt fat32?
Click to expand...
Click to collapse
No problem, seen it before and just passing the info along. I don't think it should affect the boot.img as that is flashed from terminal, and I don't think terminal is as discriminating as the bootloader.

h.nocturna said:
No problem, seen it before and just passing the info along. I don't think it should affect the boot.img as that is flashed from terminal, and I don't think terminal is as discriminating as the bootloader.
Click to expand...
Click to collapse
that worked its updating, however my trackball doesnt work and i think im supposed to use it after the install. wonder if theres a workaround...
edit: i wound up pulling the battery and it booted up just fine so i think im set to send it back in, thanks again for the help it wouldve cost me up to $300 to the insurance if anything went wrong on my end...the build number says "kila-..." i cant remember if thats original

Cyanogen 4.2.11.1 Issues

Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,

D3AD PIX3L said:
Hi there Android people.
I am having some issues with running the current Cyanogen *4.2.11.1*.
Phone: G1 Drea100 PVT 32B with stock 1GB SD
using anmon RA 1.5.2 recovery image
-wipe all available in menu.
-created a new partition- FAT32, Ext1 (upgraded to 4), Swap 32MB
-wiped all again.
-repair SD: ext
-flash signed-dream-devphone-userbug-ota-14721
-Once the flash above completed I did not restart, I simply flashed to update-cm-4.2.11.1
-reboot
Once it boots, my home process stops responding if I touch anything. This last for about 15 seconds, after that it seems to responds fine, but the browser and market place seems to auto-close on me from time to time, and I get random phone reboots, after a few reboots my phone simply stops turning on. I have to wait about 10 minutes to get into recovery and try to flash all over again.
I tried fix_permissions in the terminal, no luck.
I did some reading and noticed a lot of people are running different Radio/SPL versions other than stock, I am no super user, so I don't know if any of this effects ROMs, or if I should be flashing either for any sort of benefits I am missing out on? could this be the issue? Current SPL/Radio below:
HSPL10.95.3000
CDLP-4
Radio-2.22.19.261
Any input would be much appreciated.
Thanks,
Click to expand...
Click to collapse
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83

staunty said:
Why did you use "signed-dream-devphone-userbug-ota-14721"
I'm no pro but I used the base image that cyanogen recommends on his wiki page. The DRC83 defanged located here:
http://wiki.cyanogenmod.com/index.php/Latest_version#Defanged_DRC83
Click to expand...
Click to collapse
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?

cloverdale said:
He used that because it is the proper image to use. A defanged file simply means that it has been rendered safe to download with no fear of infection. The link on his site is to the file used by the OP, so no worries there. Also, your radio is good, so do not worry about that either.
I have to ask, because you did not mention part of the process that should be happening. You flash the HTC image, then you do not reboot and flash the CyanogenROM. At this point you reboot. What happens? It should flash the radio, go to an HTC screen, stay for awhile, then reboot itself back to recovery where it gives a message regarding the cache being cleared. At this point you reboot for the actual boot process. Is this not happening for you?
Click to expand...
Click to collapse
You are correct- after flashing CM the phone will flash the radio and reboot to the recovery screen where I will reboot again. Sorry for not including that detail.

Home process hanging in the beginning is not a problem, most people have that happenning. Eventhough home screen is shown, Android is still booting up, you just have to wait a little bit for everything to finish up.
Problems with stock apps usually indicate that something went wrong with instalation of the rom (i.e HTC 1.6 rom was not installed properly) so you may want to re-flash that again followed by CM rom of your choice.
Next time you phone reboots itself, try to get a log (there's more on how to do it in Cyan's thread), it's the only way to find out what happens.
Last, but not least, stock 1GB card is not advised for swap/apps2sd because if it's slow speed (it's class 2). Get one that's faster (class 6 preffered) and try that out, it may be the source of your problems after all.
Good luck.

how do i install this Cyanogen on my G1 with 1.6 firmware ?

simple007 said:
how do i install this Cyanogen on my G1 with 1.6 firmware ?
Click to expand...
Click to collapse
http://tinyurl.com/yjuy6u3

But in all seriousness
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
This would work. Please use search, this is such a n00b question.

Did another fresh install, so far no issues.
I will get a log the next time I install to see if I can track down the issue.
Also had time to install Enoch 4.2.11.2 theme. <3 this theme.
I will be heading to Frys today to pick up some cooling fans for the old PC, I will take a look for new mini SD
thank you to everyone that responded.

Just got home from Frys Electronics.
Purchases an A-DATA 8GB Class 6 microSD.
wiping/flashing again.
I am having a hard time learning about the swap file part of all this... I can find guides on how to create a Swap Partition, but not sure how to make it work and/or optimize it.
So I created a 32MB Swap- Previously I read the commands to enable Swap through the terminal- "linux_swap_en=1" I have used this and it does indeed turn on swap, but is there some sort of command to optimize? I believe tweaking the swap files is adjusting the "swappiness"?
The other way I enabled the Swap file was from the spare parts menu- Enabling Compache enabled my Swap file. Does this need adjustment? for size? or any other parameters? Or is this kind of an auto on for Swap?
Sorry I am a total noob, and want to know if I am missing out, I just keep loving this phone more and more.
I will be buying Cyanogen some beer soon ^_^

I've played with swap a long time ago and never quite understood it neither. As of lately, I've been running 10mb hack (in the developement section) and it works great. If you're inclined to get the swap thing going I suggest you read this thread. This will give you an idea of how to enable and tweak swap-related tasks.
Glad to hear that you have original problems taken care of (so far at least).
Good luck.

I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.

D3AD PIX3L said:
I think I just may have bricked my phone...
I did all the steps stated in my first post while flashing to 4.2.12.2 and got things going great. Flashed Enoch's Theme 4.2.12.2. Everything was rocking.
Then today, it shut it self off, I rebooted. Got to Enoch load screen then shut off, tried it again, and it won't even get past the G1 splash screen. I have had this happen a few times before, where it would power off randomly and I had to pull the battery, wait like 5 minutes and then get into recovery and clear/flash again. Now I am getting into recovery but after a minute or so it just shuts itself off again.
Can't wipe, Can't flash, cant even get into Cam+power to flash back to previous RC...
Not really sure what to do at this point...
If I do manage to get it running again, I do wonder why its doing this.
I use Cachemate to clear my catche and task killer to kill apps. Could Cachemate be the culprit in this mess, its the only app that I own that uses root? Not sure what else to blame it on other than the G1 one being one big POS and is only good if you can even get a ROM to run on it. I am 5 minutes away from ordering a Nexus.
once again thanks in advance for any input you can provide.
Click to expand...
Click to collapse
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.

cloverdale said:
This sounds like a hardware issue, and not a bricking. Try a new battery, this may fix it, otherwise I am not sure.
Click to expand...
Click to collapse
I will try the other battery I have at home in my other G1 and report back

D3AD PIX3L said:
I will try the other battery I have at home in my other G1 and report back
Click to expand...
Click to collapse
I tried it.
Same issue.
I did noticed that the batter pins were abnormal... One was sticking out more which was normal according to my other G1, the other 2 were shoved down. I tried to mess with the 2 to get them to pop back up to their normal position with no luck.
I am thinking about ordering a replacement.

okay, so tonight I am going to take the G1 apart and see if I can get those pins straightened out. Not sure if it will help, but its better than declaring it a paper weight.
will post the outcome.

Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?

borodin1 said:
Just out of curiousity (and I don't exactly know where I'm going with this) will your phone turn on and stay on if you plug it in (usb or charger)?
Click to expand...
Click to collapse
It does not.
I think i will take both phones apart and swap out the screen since that is why I don't use the one. I watched a visual walkthrough seems easy enough
Has anyone disassembled their G1 and reassembled successfully? any tips?

Started to take apart the non-cracked bricked G1.
Once I removed the motherboard and started on the next step, I realized how bad it would be to end up getting the parts swapped and then have it not work... Put it back together and loaded up the latest Cyanogen on my working cracked G1.
*shrugs* it will do for now.
Waiting till the end of next month to order my Nexus 1, then I will have fun ripping apart both G1's and hopefully end up with one great looking, fully functional G1 to possibly sell or keep as an extra phone...
thanks to all who replied!

[Q] Stuck at Clockwork Recovery screen? HELP!??!

I am currently stuck at the clockwork recovery screen. BTW i did the one click root...didnt break stock bootloader. not sure if this makes a difference or not. i was told it didnt...? i cant get back to stock firmware and i cant load zx2.1 sense i keep getting errors on both and i really have no idea what the hell to do from here. error on zx2.1 is as E:cantchown/mod/system/xbin (no such file or directory)
E:failure at line 17: set_perm_recursive 0 2000 0755 -6755 system:xbin
installation aborted

If you have stock SPL those roms will not fit ito your system partition. They need danger spl or the recent mtd partiton hack.
You can also try a donut rom without sense, they usually fit stock spl system.
€: If you want to go back to stock rom, you need the correct dreamimg.nbh for your device on your sd card and flash it via bootloader. This will obviously break root.
Sent from my HTC Dream using XDA App

mblaster said:
If you have stock SPL those roms will not fit ito your system partition. They need danger spl or the recent mtd partiton hack.
You can also try a donut rom without sense, they usually fit stock spl system.
€: If you want to go back to stock rom, you need the correct dreamimg.nbh for your device on your sd card and flash it via bootloader. This will obviously break root.
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
How can i get it flashed via bootloader when i cannot load anything on it? i cant get past the clockwork recovery screen. ive downloaded the dreamimg and i just dont know wth to do

BenDiesel said:
How can i get it flashed via bootloader when i cannot load anything on it? i cant get past the clockwork recovery screen. ive downloaded the dreamimg and i just dont know wth to do
Click to expand...
Click to collapse
This is the guide I used to downgrade. Make sure you have the right image file for your phone, and make sure your battery is fully charged and the process is not interrupted.
http://forum.xda-developers.com/sho...&highlight=original+spl+downgrade#post5640154

oldnoob said:
This is the guide I used to downgrade. Make sure you have the right image file for your phone, and make sure your battery is fully charged and the process is not interrupted.
http://forum.xda-developers.com/sho...&highlight=original+spl+downgrade#post5640154
Click to expand...
Click to collapse
ive given up. my computer will not read my g1. its like its not there. and ive downloaded 5 dreamimg's and for some reason the g1 says theres no image file. i just boot to clockwork recovery and thats it...

BenDiesel said:
ive given up. my computer will not read my g1. its like its not there. and ive downloaded 5 dreamimg's and for some reason the g1 says theres no image file. i just boot to clockwork recovery and thats it...
Click to expand...
Click to collapse
The computer doesn't need to see the phone. Put the file on the root of the sd card, the name of the file has to be correct and is case sensitive, DREAIMG.nbh IIRC. Power down the phone, insert the sd card, press and hold the camera button while you power it on until you see the bootloader screen. The phone should see the file and take it from there.

oldnoob said:
The computer doesn't need to see the phone. Put the file on the root of the sd card, the name of the file has to be correct and is case sensitive, DREAIMG.nbh IIRC. Power down the phone, insert the sd card, press and hold the camera button while you power it on until you see the bootloader screen. The phone should see the file and take it from there.
Click to expand...
Click to collapse
It was already in all caps...exactly as you said it had to be. not sure what the iirc means but it still is doing the same. some people have said it could be corrupted but how the hell can it be corrupted after 5 different ones. i feel like throwing the damn thing in the furnace!

BenDiesel said:
It was already in all caps...exactly as you said it had to be. not sure what the iirc means but it still is doing the same. some people have said it could be corrupted but how the hell can it be corrupted after 5 different ones. i feel like throwing the damn thing in the furnace!
Click to expand...
Click to collapse
Sorry, IIRC = If I Remember Correctly.
The file name is upper case, the .nbh is lower case. To check the validity of the file you can search for and download an MD5 sum checker, but after 5 attempts I doubt that would be it. The only things I can think of is either a problem with the card, or something with the phone. Try reformatting the card making sure it's a FAT32 full format, not a quick format. Hopefully one of the Android gods around here will see this have some better ideas.

oldnoob said:
Sorry, IIRC = If I Remember Correctly.
The file name is upper case, the .nbh is lower case. To check the validity of the file you can search for and download an MD5 sum checker, but after 5 attempts I doubt that would be it. The only things I can think of is either a problem with the card, or something with the phone. Try reformatting the card making sure it's a FAT32 full format, not a quick format. Hopefully one of the Android gods around here will see this have some better ideas.
Click to expand...
Click to collapse
ya its jus like this DREAIMG.nbh man i did the one click root didnt break bootloader....tried to boot load the regular rom and nothing man. im done with it. its tottally effed in my opinion....ive tried everything i can think of...

You really have to make sure you got the right DREAMIMG.nbh. If you have e.g. a T-Mobile G1 get the newest for T-Mobile. Be sure to have the newest, as it is possible that older versions are not flashable either. There are lots of those images around, and if you try them at random they are quite sure not to work.
Also there might be problems if the SD-Card is not formated properly. If you have an external reader, take it out and format it on your pc. Then put the (correct) image on it.
Perhaps if you tell us the brand of your mobile, we can try to guide you to the right image.

mblaster said:
You really have to make sure you got the right DREAMIMG.nbh. If you have e.g. a T-Mobile G1 get the newest for T-Mobile. Be sure to have the newest, as it is possible that older versions are not flashable either. There are lots of those images around, and if you try them at random they are quite sure not to work.
Also there might be problems if the SD-Card is not formated properly. If you have an external reader, take it out and format it on your pc. Then put the (correct) image on it.
Perhaps if you tell us the brand of your mobile, we can try to guide you to the right image.
Click to expand...
Click to collapse
no longer a newb....got this f'er working again and boy flashed a rom! back in the game!

[Q] I have totally messed up my Nook Color

Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.

MentalDragon said:
Ok so I have totally messed my brand new device, this is second day I have had it. I got it yesterday and first thing I did was install DeeperBlues HC v4 on my eMMC. It was easy. I had to use Autonooter first. I was on 1.0.1. Well after playing with it all night. I started to not like the functioning of apps on the platform. They were great but was in my opinion, no greater than when it was just rooted. So I decided to bring it back to stock. I accidently placed wrong sd card in it, the one with Autonooter on it. Now when it boots up it says Loading.... then I get the word ANDROID in lower left had side of screen in landscape. I am a noob when it comes to this. Now I flash and mess with my phones rom and themes and kernels all the time kind of a junkie, but this is no walk in the park.
Please can someone help me.
Click to expand...
Click to collapse
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.

BarryR1 said:
I think you rooted your Nook which could be a fine thing. If that's not what you want, getting it back to stock is very easy.
Here's a link: http://nookdevs.com/Flash_back_to_clean_stock_ROM
The tricky part is to get the timing right so that you get the 8 failed boots (that took me a while). If it looks like it's about to boot up up, hold down the power button till it goes off (at least I think that's what I did). If you have adb installed (or install it) you can get around that.
Click to expand...
Click to collapse
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838

khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Is this going to help me. My original firmware was 1.0.1.

Just grab the CWR 1.1 Recovery image from the development forum. Burn that onto an SD Card and reboot. Wipe data boot system cache and flash. done.

Find rootpack in dev section, write that to sd card, add the flashable restore to stock zip from samuelhalffs restore to stock thread in the dev section to your sdcard, boot to sdcard with the rootpack on it, flash the restore to stock zip after formatting system and data. Wala, fixed! All info can be found in my dummies guide to my nook won't boot a few threads down.

Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.

MentalDragon said:
Thank you Thank you Thank you. This worked. I now have my Nook back. Thanks.
Click to expand...
Click to collapse
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?

khaytsus said:
Yeah, but that's not going to work, he installed HC on the internal eMMC the first day he owned it.........
Probably the fix is here: http://forum.xda-developers.com/showthread.php?t=945838
Click to expand...
Click to collapse
Oops. My bad. Sorry for the misinformation.

MentalDragon said:
Ok still need help. I seem to have installed CWR but now i am watching the Nook Color boot animation looping over and over. I tried to reboot but it is still looping. What do I do again? Do I reinstall sd card? And reflash the rom?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=949699
Try this Thread, "Dummies Guide to Fixing 'My Nook Won't Boot'""
This should work and get you back to stock so you can start all over.