I think you'll find the problem is with Windows 7 rather than your HD+. Noticed how slooow large file transfesr become when they're going to peripherals like ExtHDs or flashdrives? Lots of info on this Win7 "flaw" on the "Net.
Just a couple of quick clarifications. There is an Odin Mobile app that can be used to flash roms. BUT it only works on selected Samsung devices, notably the older Samsung Galaxy phones. No way to use it to try what you want. No connection to NC at all. Unless your Fascinate is utterly bricked...
Prepping your electronic device can be very frustrating (try out the original Galaxy S for real hairpulling fun), but, failing something severely wrong with your hardware, you should not be having such trouble with your Nook! First, check all the 'duh' stuff. It is a Color and not a tablet, yes...
I've tried 10.1, and it is spiffy looking and very modish, but I still always go back to the microchip with 7.2 Kang (last build). For my money, it's the most stable, useful, and fits the rather antiquated hardware of the Nook best.
What version of CWM is on your boot card? Some earlier versions have trouble with the later issued NCs. Also, make sure it isn't a Nook Tablet (I know, but it is amazing how many don't actually know there is a difference.)
Don't know if this will help since it seems you are running a standard Nook OS (I use CMod 7.2 and run
it off a SD card), but I just looked, and found all the volumes I had downloaded from the B&N site are located
on my emcc (i.e. I believe this is where my stock B&N OS is located) in a file...
If you truly have nothing happening, it certainly sounds like a hardware problem. Pulling battery to reset is worth a try. It's worked for me on several Android devices (never tried it with a Nook, though). Somewhere recently in the forum I read how to do a safe battery pull on a Noo, but don't...
You might also look into using one of the transfer-over-wifi apps to get your data files onto Nook, I use WifiFileExplorer to this effect and never hassle with USB cords/connexions. Quick and sees everything.
For Travladin: You should be able to flash from that screen if you can connect with your 'puter. Try to revert to a stock image (I use Odin KK4), then flash Corn kernel and rom of choice. I think that screen works just like the little android digger...
Check out Ebay under Samsung Galaxy S Captivate. Numerous "broken" Cappys there at low bids; some of them will have what you need if you can disassemble correctly.
You can download CM7 RC 3 from the same source and try to add itfirst. If it loads,then rename your other zip with an update_ prefix, put it on your boot partition, boot into recovery and you should be where you want to be. (You'll prolly need to install GAPPS zip after first load of RC3 to get...
What I might suggest is to discard your original source of instructions and start fresh. Search the xda forum for clear information on 1) proper mSD card to use; 2) proper card burning software; 3) the most appropriate rom(s) to use for what you want your Nook to do for you, and 4) if necessary...
Have you tried a complete restore to stock using ClockworkMod on mSD? I revived my NC twice from what first looked like complete death this way. (you do have the restore card ready, don't you?)
Create a folder on sdcard (mine is 'dumped'). Put any and everything in there you feel you'l lever need to run whatever os you have (mine is racks triple boot). Use Imager to back up your card image to computer. You'll have access to everything on card whatever you boot into, and a spare to...
Another alternative to above Titanium BU tip is to sync your BU to Dropbox, zip it and after reinstall of ROM upload your zipped BU file into the SD folder Titanium makes when first installed, unzip, overwrite, and everything's there. I've never had trouble with this method. And it's fast...
Now that racks' triple boot wil take latest updates, you can run the very stable CM7, still play with latest CM9, and always have the basic B&N available on emcc. Like having your cake and etc...
You have the right card. Go to Verygreen's OP site here on XDA and follow his instructions precisely. You should have no trouble booting from SD with either CM7 or CM9 (I suggest using the Kang version of the former).
Somewhere on the XDA site, I don't recall where, I saw a thread with another 2nd owner who had the same 'previously registered' problem you probably have; he got directions on a workable fix. Do a search; maybe you'll find it...
I generally transfer my update files from PC to NC using Wifi File Explorer Pro. Once on the Nook you can move them to the proper place and Bob's your Uncle.
Yep. Use above method to put your image file on anything up to 32gig card; be sure you are using Sandisk brand, though. Small block read/write speed makes this the Nookers choice.
+1 on CM7.2-RC1 MiRaGe - KANG build, particularly if most of what you will be doing is reading (Aldiko, Kindle and B&N 'droid apps are all good; I use EasyPDF reader for that format.) You may also come to appreciate the updates -- not so many as earlier, but the NC has been out a while now. And...
Are you booting into recovery? It is from there you access your SD gapps files. Reread racks' excellent instructions. It seems you have missed something vital there.
Did you check to see if after you uninstalled the earlier version you still had a "Montano" file on your SD card? I noticed this once when i had trouble updating my version. It balked because presumaly the installation precedure looked and found this file (I could discover no other "turds" i.e...
Using the same setup on one of my cards. It did seem to increase scrolling speed for me in some apps. YMMV, of course. Agree about smoothness. This is also pretty close to the most stable setup I have now, which is a SD card devoted to a single boot devoted to mag666' latest kang.
If you don't want to spring for a new Sandisk class 4 card -- I have five now :-)) -- just use your Win32Disk Imager to write an image file of your current setup to your computer and go blithely on experimenting like crazy. You will always have an image file to write back to your freshly...
Get Wifi File Explorer Pro. It's quicker, allows full browsing on your computer to access files for upload AND it lets you download everything from your NC which can be a godsend when trouble strikes. And you will not have any of those persistent problems using USB connexion.
Any possibility of reverting back to an earlier Market app if this continues? I don't have this problem (yet) but always anticipate the worst from Google. Running racks' triple boot now, everything hunky-dory.
FWIW, I have had the best luck imaging my SD cards so they come out flawlessly when DiskImager and my chosen file (named appropriately) are in the same directory, preferably root of my C drive.
Sorry for the firestorm. Guess I was unclear on precisely what I was asking. Which was: can I use racks' clipped info to install the latest reasonably working Mirage update, and, if so, where could it be found? And, by the way, I did/do read this and most other NC threads, so I'm not really...
Did look there first. Some confusion, at least on my part, re exactly which is which re: CM7 upgrade. Please read dl items for yourself and then, perhaps, you could answer my question rather than polemicizing.
Will this work for CM7 update as well? Mine has somehow gotten hincky and now goes into endless reboot instead of opening.
And where may I find latest version of Dualboot CM7 update? In the OP page?
Please help me avoid a complete overhaul.
RE your apps drawer lag. The one thing I really noticed after adding v6 supercharger script to my CM7 NC was a remarkable increase in scroll time and lack of lag in app drawer and other scrolling tasks. It's definitely worth a try, IMO.
Okay, I never had this one before. I'm running racks' triple boot with most of my time spent using CM7. For the past three days, when I turn the power off on my NC overnight, and that is only after a full recharging -- yep, and I'm obsessively neat, too -- the next morning I show a battery...
Yep. Sounds like a card corruption problem. I had one. Reformat was the only solution. Be prepared to sacrifice your apks. And always drop spare copies onto your computer, just in case.