Was working fine with 1.4.3 when I got it yesterday (boy that firmware was damned slow, good lord), then I worked out how to get CM7.2 on it and that worked fine for a bit, then I figured I'd give CM10.2 a shot and that worked fine (albeit slow which is seemingly just how the NC is), then even the latest snapshot M7 build of CM11 and even that worked somewhat (constant FC's of gapps, etc, known problems I suppose - yes I did use CWM 22.214.171.124 to install it).
So I did some more research yesterday and found out about MiRaGe CM7.2 being hailed as the best performing ROM for the NC and figured ok this could be just the ticket.
To get CM11 installed I used a Sandisk Class 4 8GB card, the 1gb_clockwork-126.96.36.199-eyeballer image, the snapshot M7 build of CM11, the most current gapps for KitKat (20140606) and then CWM 188.8.131.52, data/factory reset, reboot, worked fine until I decided to get MiRaGe CM7.2 on it.
To install MiRaGe CM7.2, I used the same SD card (the Sandisk), only placed the MiRaGe zip and the gapps-gb-20110828-signed.zip file on the card. Booted the NC to the recovery (CWM 184.108.40.206) and then inserted the SD card, chose to install zip from SD card, browsed for the MiRaGe zip and then started the install - it got to roughly 80% or so and then just hung there for several minutes, then the NC powered itself off and back on again, getting to the Cyanoboot screen, then a flash, then nothing but the display and backlight were obviously on.
Ok, not good, so then I held the power button till it shut off, ejected the card, started it up again, went into CWM 220.127.116.11 again (it was installed to the eMMC), put the SD card back in, factory wipe/etc, install zip, same thing: hung at 80% for a minute or so, then an NC reboot.
It did that twice, and after the third time when I shut it off thinking ok I'll just try the plain old vanilla CM7.2, I pulled the SD card out, put it in the laptop, copied over the CM7.2 zip, popped out the card, back in the NC (but not inserted since I needed to get Cyanoboot up to hold N to get recovery.
That's when the NC wouldn't power back up. Dead, nothing, no response of any kind. Plugged in the charger (factory charger and cable), got the typical colored light (orange or amber or whatever the hell color it is) - before I started this process the NC was 95% for battery, it wasn't plugged in during the attempts to get MiRaGe CM7.2 on it, however.
But even so, no response whatsoever. I held power for 15 seconds or so, pushed in the SD card to try and boot from that, same thing: no response of any kind whatsoever. Popped the card out completely, then decided to try Power+N (nothing), Power for 30 seconds, then let go, power for 5, no go, nothing.
Decided to plug the NC into the computer direct using the factory cable, no response of any kind - the computer is not recognizing anything whatsoever (I know some folks report they get a hardware detection of the OMAP device, I'm not that lucky). Unplug it, hold power for 15 seconds, let it go, wait 10 seconds, plug in the USB cable, still no response, no sound, no activity, no backlight, nada, zip, zilch, zero, null and void, "It's dead, Jim..."
But, I kept trying, using 2 other SD cards I have (a 1GB Sandisk and a 2GB Sandisk), same results: totally dead nothing.
Decided to make this post just for the hell of it but I'm fairly confident that it truly is totally toasted dead. I've tried different CWM bootable images from leapinlar and others, still nothing, no response of any kind, no activity.
I kinda figured that it's truly totally absolutely dead when I plugged it into the laptop and it wasn't detected at all. Holding Power+N while plugging it in (a trick of sheer physical ambidexterity, I assure you) has no effect. Not sure what I may have done, maybe the eMMC is just totally hosed - but then again, it won't boot from SD card either. I've read many posts that say if the boot partition on the eMMC is hosed, it's a dead device but then someone else will say that doesn't matter 'cause you can just put in an SD card (which has boot priority) and it'll fire up but that's not happening with mine.
Went from working device to brick, and I don't know how unless something just totally died in the process that shouldn't have. Oh well, I only paid $25 for it from someone that just didn't use it anymore. Did require a 45 minute charge to get it to wake up yesterday when I got it - previous owner said it had been in a drawer for like 9 months, hadn't been touched at all and I figured it was cheap and would give me something to do.
I know it's dead but, there's always some hope... right?