Database Users

[Q] CM7 boot partition Size

Hello,
Complete noob here and I am not ashamed to admit it. I did create a bootable sd card with CM7 stable on it and the card is partitioned into 4 spaces. The boot space only has a capacity of 117.63 MB, while the 4th partition named CM7 SDCARD has a whopping 28.21GB available.... 112.14MB used..... Im guessing for application. Anyways, I am trying to put books and videos on my NC and there is not enough space that is accessible. Any way to make that boot partition spave larger? Maybe move some of the extra space from the 4th partition? I have EASEUS Partition Master but I have been unable to get it to work..... Any help is greatly appreciated.
I did search for a post like this but did not find any answers which I understood.
Thanks in advance,

What is it that you are trying to do?
Homer

I am trying to put books on my sdcard that I downloaded on my computer for school. When I copy to the directory boot/myfiles/books it says that there is not enough space. So I want to enlarge the size of the boot partition

After you burn the partition image using Win32Image, the size of the boot partition is roughly 117mb. At this point use EASEUS partition to expand the boot partition to the size you want. In my 32gb SD card, I created a 16gb partition. Then I copied CM7.1 and Gapps to the partition, booted NC and CM7.1 was set up in the remaining space, with /data at 5gb and /media at 9gb.

Would you then access the files while booting from the SDcard or internal memory (eMMC)?
If you want to see them when booting from SDcard, don't put them on /boot as you have found out there is not much room. You want them on partition 4. Remember that Windows will not mount partition 4 without some heroic efforts. I use either NookColor UMS (free, see here) or WiFi Explorer Pro (paid, check either Android or Amazon Market).
If you want to see them when booting from eMMC, that is slightly more advanced. You don't have to root, but there is a file on the system on eMMC that needs to be edited to mount partition 4 rather than partition 1. It would take some time to search for it, but someone posted a guide a while back. Search for something like sharing SDcard and/or editing vold.
Homer

Ok...... So I got the boot partition resized to around 20gb and I have copied the books from my hd to the sd card E:\My Files\Books...... Problem is I now cannot acess them when I boot CM7..... Any fix to this or will I have to boot from the eMMC?

Ok....
You're making the easy stuff hard...
You want a large partition that is accessible by CM7 running off the SD and your windows PC. Like Homer said, it is nigh impossible to get windows to mount secondary partitions off of an SD card reader. What he forgot is that CM7 allows you to access partitions 3 and 4 over USB. CM7 can access the boot partition but most apps won't look there and it won't be accessible over USB.
I would recommend that you restart from scratch. Allow verygreens installer to set up the default partitions. Plug your device into your PC and transfer your pdfs to partition 4 that-a-ways. That way you won't have to remove the sd card anytime you want to access your pdf folder.

Even when you plug the CM7 booted NC into your PC, you still need to mount the /sdcard partition to Windows. I find it is easiest to use NookColorUMS on the NC to mount that partition, see above. Otherwise, when you plug into the Windows machine you only get /boot mounted.
Homer

Homer_S_xda said:
Even when you plug the CM7 booted NC into your PC, you still need to mount the /sdcard partition to Windows. I find it is easiest to use NookColorUMS on the NC to mount that partition, see above. Otherwise, when you plug into the Windows machine you only get /boot mounted.
Homer
Click to expand...
Click to collapse
Hmm, when I plugged a nook running CM7 from SD card, I get access to /media and /sdcard. I had to move the gapps.zip from /sdcard to /boot manually using a file explorer.

I'm offering an apology to gall and Homer first so pls don't jump on me.
You guys harden a simple issue and confusing the OP.
To OP,
I assume you got a 32GB uSD card, using verygreen's image. You got 117MB on boot.
LEAVE the boot partition ALONE. The only thing you should put there are the ROM (CM7 zip file) and the GApp zip file. NOTHING ELSE. Your music/ebook/video, etc. should NEVER go there. You will place them in the left-over storage created by CM7, normally called CM7SDCARD.
How do you access CM7SDCARD so that you can transfer files over?
The only way is
+ NC on
+ connecting NC to PC (windows)
+ look at the NC notification bar, usb icon should be displayed
+ tap on it, enable usb mass storage (connect to PC for file transferring....)
+ Windows PC should by now recognized the CM7SDCARD and ready for use.
That's the ONLY WAY and the correct way.
If you use that bootable CM7 uSD and plug directly into PC, you only see the boot partition which only 117MB. Again, the boot partition is NOT meant for personal stuff.

What may confuse some people is that when they plug the device into PC then it does not by default auto-mount so you don't get a drive in the PC until you use the USB notification and turn on USB storage.
For non-techie users I normally install the automount USB app from JRTStudio so the drive pops up straight away on the PC and there is no confusion over this point.
The other good reason for using the USB (or alternatively wireless connections like ES File Explorer) is that it reduces taking the SD card in and out and any risk of damaging the socket.

My apologies, I never checked out the USB notification. I sort of ignored it. It seems a handy implementation of the basic functionality of NooKColorUMS.
What is MyNOOKColor though? CM7 SDcard is the one I typically use. Nevermind: it is the eMMC. I never bothered with that one since going to SDcard boot.
Homer

[Q] Can I have partitions that can be accessed from both NC Stock and CM7 on SD card?

Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

andrandom said:
Hi everyone!
I just got CM7 (latest stable release) installed on on external sdhc card. I have wifi issues with CM7 (and looking around the forums tells me that CM7 can be finicky with certain routers) so I would love to be able to use Nook's stock ROM (4.1.4) when I am having issues.
But, when I am on NC ROM, I don't see anything except the small boot partition on the SD and when I am on CM7, I don't get access to this boot partition. I am wondering if there is a way to either create another partition or make the currently existing partitions accessible on both ROMS so that I can share data between them.
I am a n00b without any Android experience so thanks in advance for your patient responses.
Click to expand...
Click to collapse
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).

leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
*That's* the one I wanted to point them to.

leapinlar said:
Look in my signature for a link to my tips thread. I explain there how to make the SD media partition available to both ROMs (item B3).
Click to expand...
Click to collapse
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?

andrandom said:
Thanks.
Do you mean step #3 in Section B? I could edit it without running your script too, can't I?
Click to expand...
Click to collapse
If whatever you have on emmc is rooted, you can manually edit it. If you have unrooted stock, then you need to flash the zip since without root you cannot edit those files manually. And I did mean item B3. Each item is a different topic, they are not steps. One topic does not depend on another. Just do B3 and no others if you want.

Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?

andrandom said:
Yes, item B3. My mistake...
I should be able to do flash the zip from my current CM7 SD card's boot partition, shouldn't I?
So I put the update-stockemmc-vold-fstab-modified-for-partition4.zip file in the boot partition of the SD card, rebooted to Recovery mode and then booted to NC's stock ROM. NC is still using the tiny boot partition on the SD card as my external storage instead of the much larger CM7 partition. This was the same partition that was under 'My Files / Memory card' before I flashed so nothing has changed. I did this twice to double-check.
Am I doing this wrong?
Click to expand...
Click to collapse
Yes you are doing it wrong. You need to flash that file with a CWM card, not put in the boot partition of your SD. And since you did that, you need to re-flash your latest ROM on SD to correct your mistake. (I will edit my instructions to make it a little clearer that you use CWM to flash that file.)

I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.

andrandom said:
I got NC stock ROM to see my SD card partition by following item A10. That is most excellent and thanks again!
Unfortunately, I no longer see the boot partition when I attach NC to my computer whether NC is running off stock ROM or CM7. My guess is that this is due to my failed attempt to flash from my CM7 SD card yesterday. Am I right?
I thought I could reverse that by copying the update-stockemmc-vold-fstab-return-to-stock.zip file to CM7's boot (and then booting to the recovery mode) but that seemed to have nothing.
If I understand your previous message correctly, I should re-do my entire SD card but... I have already spent a few hours downloading and customizing the Android apps. Is there a way to preserve all that before Win32diskimager destroys the contents of the SD card?
Is there a way to manually mount the /etc folder from a unix prompt and alter the file?
Does it even matter if I don't see boot while I attach NC to a computer? Are there any caveats to 'let it be'?
Questions, questions and more questions...
That leads me to the obvious question, is there a book that explains Android to someone who is not interested in programming it but wants to understand the architecture and design of the OS (and custom ROMs)?
Thanks for being patient with all these n00b questions.
Click to expand...
Click to collapse
You do not need or want to re-set up the whole SD installation. Just put the same CM7 zip file back in the boot partition and boot to SD recovery. It will put the correct vold.fstab back on the SD. You will not lose any settings or apps you have already set up. (And putting the return to stock zip there was also the wrong thing to do. The vold.fstab for stock and CM7 are different. But don't worry, it will fix that too.)
You are not supposed to see the boot partition on the PC when you plug the nook in with the cable. You are only supposed to see 'emmc' and 'sdcard'. Under the original setup, your stock system thought the boot partition was 'sdcard' and that was why you saw it on your PC. Since you modified stock to see partition 4 as 'sdcard', partition 4 is what the PC sees, not the boot partition.
Most people have to physically take the card out of the nook and put it in the PC to see the boot partition on the PC. If you don't want to do that, use my script in item B4. But since you are on CM7, you will not be adding many things to the boot partition to install with SD recovery in the future. So it is probably best to leave things be.
And I don't know of any books to help you.
Sent from my Nook Color running ICS and Tapatalk

That is excellent news!
A bit of playing around with Astro tells me that I was wrong about seeing the 'CM7 SDCARD' partition when I was on CM7 ROM. I am only seeing the boot. Anyway, I am going to flash the CM7 ROM again and I am hoping it would fix everything.
Also, yes, I can see the boot partition when I put the SD card directly on my computer but I was also able to see it when I hooked up the NC to my computer via USB before I did my unintended tweaks but... I'll survive.
I'll be back after I flash. (Famous last words??)

Mission accomplished!
Thanks again for all your help.

For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot

DizzyDen said:
For future reference after you alter stock's fstab... all you have to do is:
mkdir /sdcard/boot (only have to do this one time)
mount /dev/block/mmcblk1p1 /sdcard/boot (do this every time you want to put something on the boot partition)
put anything you want on boot partition in /sdcard/boot
Click to expand...
Click to collapse
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.

leapinlar said:
Yes, there is one big advantage to using that method. I think it allows the boot partition to be seen not only on the nook, but also on the PC when you plug in the usb.
Click to expand...
Click to collapse
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.

DizzyDen said:
We could probably come up with a symlink to /dev/block/mmcblk1p1 to /sdcard/boot and avoid having to mount it everytime as well.
Click to expand...
Click to collapse
Thank you Dizz, your suggestion got me to thinking and I was able to come up with an init.d bash script that does the trick. I just temporarily mounted sdcard and created the sdcard/boot directory and the mounted the boot partition to it, then unmounted sdcard so it could be mounted again by the system later in the boot sequence.
The only problem is now sdcard will not mount on the PC using UMS mass storage. Must be because of having a second mount within the mount. But it does mount with MTP. But that may be acceptable. I will test some more, including using Goo Manager tomorrow.
EDIT (6-21): Goo Manager works. But I think I have figured out why sdcard is not mounting in UMS. Once it is mounted in my script and the boot partition mounted under it, it cannot be unmounted. And since it cannot be unmounted, it cannot be mounted later by the system as vold. If it cannot be mounted as vold, it does not show in UMS. For now I think I will leave it as I have it in Rev 2 of my script (symlinking to the root directory with full r/w permissions). If people want to see the boot partition on the PC, just use my modified for CM9 NookColorUMS available in my tips thread.
Sent from my Nook Color running ICS and Tapatalk

Help!
When CM7 is running, my computer is no longer mounting any of the partitions when I connect NC to my computer via the USB cable.
If the NC stock ROM is running, my computer mounts all three partitions (MyNook..., boot and CM7SDcard) but calibre is not recognizing the external partitions for transfers.
Further, when I boot to my NC stock ROM, I am no longer seeing my SD card's contents in the NC's library.
This may have something to do with the fact that NC stock ROM seemed to have updated itself to 4.1.3.
Should I re-run the scripts again or am I missing something else?

When it was updated to 1.4.3, you lost the emmc mods. Just re-flash my zip with the CWM SD. You may have lost CWM on emmc too.
On CM7, you have to select the turn on storage button after you plug it in. It is not automatic like stock. Pull up the notification area and touch the turn on button.

Darn, I forgot about that 'USB' option under notifications. Enabling it allows me to find the partitions. I will run your scripts again when I find a spare mUSB card.
Thanks again for your help!

"live" version of root for Nook Touch

I have done multiple searches and not found anything like this, apologies if I missed it. Here goes ...
Is their a version of rooting for the Nook N2E that can be run completely from the SD card? (Think a Linux LiveCD) I would like to try some of the other eReader software available to see if I like them before I decide to fully root my Nook. If I knew enough about Android, I would attempt this myself, but I don't want to brick my device.

Currently, no. It is possible, and is widely used on the Nook Color, but the work just hasn't been done on the Nook Touch. There was someone working on it a while ago, but it seems to have been dormant lately...

WIP thread
There appears to be a semi active thread about this here. At least is should provide a starting point.

David0226 said:
There appears to be a semi active thread about this here. At least is should provide a starting point.
Click to expand...
Click to collapse
I can't post on the development forum yet, so I am posting this here hoping others working on an SD boot image will see it.
I have been working on this myself.
I made a backup of my NST and then wrote that image to an SD card (4GB).
I changed the init.rc file and change all the mmcblk0p? file names to mmcblk1p?. I also changed the booting.png image so that I could confirm that my NST was booting from the SD Card.
I than inserted the SD Card and powered up. The booting.png image from the SD card showed up, but the device hung right there.
So I started looking at some other files. There is a file called env.txt that contains the following string:
root=/dev/mmcblk0p2 rw rootdelay=1 mem=512M
so I changed that to
root=/dev/mmcblk1p2 rw rootdelay=1 mem=512M
and attempted another boot. It still hung at the booting screen.
I suspect that it may not be able to access all the partitions on the SD card (after writing the backup image to the SD card, it contains 8 partitions, the 7 partitions from the NST and an eighth unallocated partition with the remaining 2GB from the card.)
My next idea is to attempt to get all the files off the SD card and create one partition that contains all the files in their correct directories and comment out the mount and mkdir commands from init.rc to see if I can get it to boot. (My problem is I have no easy access to a Linux system and WinBLOWS will not access the Ext2 and Ext3 partitions.)
Any comments or suggestions would be appreciated.
My goal here is to attempt to get it to boot the "standard" NST firmware and if I get that working, then attempt to set up a "rooted" OS on the SD card.

Progress????
Okay, now I got it to start a boot from the SC card and eventually I got a message that said failure to install.
Here is what I did.
After inserting the SD card into a linux machine, I mounted all the partitions.
I then copied all of the data into a single directory preserving the directory structure from the mounts.
I tar'd up this directory and ftp'd it to my windows machine.
On the Windows machine, I used bootutil to unpack the init.rc and env.txt files from uRamdisk.
I modified the files as can be seen in the attachments and repacked them.
Then I renamed the directories to correspond with the device file names they were supposed to mount from.
Then I created a single FAT partition on the SD Card and copied the directory structure to it.
It did not hang this time, so perhaps I am getting closer.

[Q] no boot: used TouchEraser.zip get message can't mount /cache/recovery/

Dear Members!
I did the stupid thing of using a tool, not completly knowing what it does.
After using TouchEraser.zip I installed Alpha-FormatTouch-2.zip using clockwork.
I tried to boot the device, no luck...
Clockwork says:
can't mount /cache/recovery/log/log
can't open /cache/recovery/log/log
can't mount /cache/recovery/log/last_log
can't open /cache/recovery/log/last_log
Please help!

Stupidly enough I don't have the devices own factory image.
What to do now?

ok , first boot with noogie image and lets see what partion u got , if u have got rom partions so take a copy all files from it and take backup from the whole nook and do this steps in this post
http://forum.xda-developers.com/showpost.php?p=30722156&postcount=2
but u must try to recovery ur nook partition rom especially cuz very important ..... before do anything above .... i will keep continue active in this thread
good luck

only one partition on on gParted...
Do You think theres any way to fix it? how?

If CWR came up that far then the /rom partition must be ok.
All we know is that the /cache partition has a problem.
That's a disposable partition, you can format the /cache partition.
Be careful, don't make anything worse.

auerg said:
Do You think theres any way to fix it? how?
Click to expand...
Click to collapse
as Renate say ..... dont make anything more worth .... so can u type fdisk for ur nook to see all ur partition table info???

Pretty screwed...
speedman2202 said:
as Renate say ..... dont make anything more worth .... so can u type fdisk for ur nook to see all ur partition table info???
Click to expand...
Click to collapse
I did but what it listed is ONLY ONE 1,8 gb partition. Toucheraser probably wiped the whole table (
I'd need a tool to restore the original filesystem or a factory image ( I don't have my own...).
I found one for glowlight, but probably I shouldn't write that to my mormal NST.
Alpha-FormatTouch-2.zip using clockwork.didn't work.
I'm pretty screwed...

Get Clockwork Recovery working on an SD card.
Get ADB setup and connected to CWR.
Run nookpart.sh from a shell (download the script from my signature).
This will recreate the partitioning without formatting or writing any of them.
You can then see if/what you can mount.
Use either the mount options in CWR or the mount command in ADB.

U kidding with me. Did u format the whole partition.? I suggest u try again and boot ur nook with noogie image and the all sevsen partition will show to U?
Tru agan man. Good luck
Sent from my NOOK using xda app-developers app

resurect nook
Renate NST said:
Get Clockwork Recovery working on an SD card.
Get ADB setup and connected to CWR.
Run nookpart.sh from a shell (download the script from my signature).
This will recreate the partitioning without formatting or writing any of them.
You can then see if/what you can mount.
Use either the mount options in CWR or the mount command in ADB.
Click to expand...
Click to collapse
I even can`t do that!,"my" nook simple are "dead" after, i delette all the memorie intern with MINI TOOL PARTITION WIZARD, without make backup or copy room, very nervius then, with CLOCKWORK RECOVERY in a sd card y instal a program call ALPHA FORMAT TOUCH2, after that my nook are iresponsive .no sd card function
any more no usb conection just charge, ¿can is posible resurrect it by some way?

dummy56 said:
...
i delette all the memorie intern with MINI TOOL PARTITION WIZARD, without make backup or copy room,
...
¿can is posible resurrect it by some way?
Click to expand...
Click to collapse
The only way I can think of to quasi-resurrect your Nook is if you can obtain a full image backup of another Nook (e.g., boot it up with noogie and read/save its entire drive as an image file) then write the backup image file back to your Nook (after booting it up with noogie) -- but then the two Nook devices will have identical device-specific data (e.g., encryption keys, WiFi MAC address, etc.), which can cause Internet access/communication problems of various sorts.

The batery are charged but it won't power on , after i install ALPHA FORMAT TOUCH2
maybe i kill him.

Wow, this is an old thread!
The Nook Simple Touch was/is a simple device.
With its SD card it's almost completely unbrickable.
Add in the stuff we've learned in the last few years about booting over USB and it's almost unsinkable.
First, whenever somebody says "dead", it's never clear what the state is.
Until you get to the point where the screen is initialized you don't know what's going on.
If you have Windows where it goes "bong" when you plug in a USB device, see if it "bongs" when you connect/power up/power down.
As said above, you'll probably need to find a full NST image somewhere.

similar to this http://forum.xda-developers.com/showthread.php?t=2322762
-------------------------------------------------------------------------
the batery are charged the machine have no image and whent i plug in a usb, no screen are inicialized just windowsXP said "OMAP3630 - No driver found". :silly:

Dear Renate, may I kindly ask you to provide the command prompt syntax here for dummies like me: "Run nookpart.sh from a shell (download the script from my signature)"? I know how to use adb, but with a ready syntax only.
And I have a spare completely bricked NSTGL, it was brought to me bricked already, managed to write an image from my current NSTGL using MiniTool Partition Wizard, and was able to open it in Windows Explorer, could see all files and folders, could add, copy and delete anything, but never succeeded in seeing any sign of life at the Nook's screen (nothing at all, never), and tried everything with a battery - disconnected it, pressed the switch button at the mainboard for some time, charged fully etc., then one unhappy day I have tried to overwrite it with a new image, but forgot to delete all partitions first and it crashed during the writing process in MiniTool Partition Wizard and now it is recognized by Windows (bang) and shown as a (some) drive but I cannot open it. Obviously I have damaged the partition table, and since then was unable to restore it, and now came across your messages here. Although, I am afraid restoring the partition table will do me no good, as it already showed no sign of life with a healthy image onboard. And I would appreciate it if you provide here a syntax for adbsync too

Mnurlan said:
Dear Renate, may I kindly ask you to provide the command prompt syntax here for dummies like me: "Run nookpart.sh from a shell (download the script from my signature)"? I know how to use adb, but with a ready syntax only.
...
And I would appreciate it if you provide here a syntax for adbsync too
Click to expand...
Click to collapse
I think a simpler, more expedient alternative to any adb-based method would be:
Use a disk-imaging tool (such as win32diskimager) and write to SD-card the image Noogie.img
Boot your live NSTGL off the Noogie SD-card and connect it to your PC via USB
Use the disk-imaging tool to read/save the NSTGL drive image to a file on your PC
Disconnect your live NSTGL from your PC
Boot your bad NSTGL off the Noogie SD-card and connect it to your PC via USB
Use the disk-imaging tool to write the file containing previously saved image of the live NSTGL drive to the bad NSTGL drive.
When writing out a disk image, make sure that you select the correct target drive (in particular don't select by mistake your PC "C:" drive).
Afterward you will have to figure out how to resolve the issue of the two Nook devices having identical device-specific data (e.g., encryption keys, WiFi MAC address, etc.), which can cause Internet access/communication problems of various sorts.

@Mnurlan I think @digixmax has it about right.
Just copying a whole image over is probably the easiest way.
If you have a raw image of the whole disk then the partitioning comes over just like all the other data.
@dummy56 if your device is IDing as OMAP3630 then what you have there is the bootloader.
The easiest thing to try would be just like above, with noogie and a full 2GB image from a friend.
Depending on what got overwritten, you might be able to fix things with just a recovery and ADB.

2 digixmax and 2 Renate
This is exactly what I did, remember I said that I received the "bad" NSTGL bricked already, so of course I took an image of my healthy (live) NSTGL FW1.2.0 to overwrite (re-write) whatever was left on "bad-dead" NSTGL, and I know in details how to write-read-save an image with win32diskimager, just during the second attempt I forgot to delete all partitions first and that resulted in damaged partitions - that is my educated guess. I would like to point out that my first attempt was successful (I have copied a healthy image of my live NSTGL to a bad one) and I was able to read-see-delete-add anything to NSTGL in Windows Explorer whenever I connect that dead NSTGL to PC directly, without a Noogie.
I am afraid, the screen has been damaged somehow (although it looks visibly intact), as it never showed any sign of life, no matter whatever I've tried.
And now the problem is that no Nook's partition appears in the MiniTool Partition Wizard window, only SD-card with Noogie, so I have nowhere to write an image. This is why I thought the culprit is - a damaged partition table. I have tried to use the GParted Live CD, but my notebook failed to boot on it, so I just postponed it for a while, as I had to leave for my rotation. Currently I am away from home and I left that "bad" NSTGL at home, and won't be able to do anything about it until I am back on Feb. 18.
And having two Nook devices having identical device-specific data is the least of my problems as I am pretty sure that I can easily do without W-Fi functionality of that Nook should I manage to revive it somehow, which I doubt.

Mnurlan said:
This is exactly what I did, remember I said that I received the "bad" NSTGL bricked already, so of course I took an image of my healthy (live) NSTGL FW1.2.0 to overwrite (re-write) whatever was left on "bad-dead" NSTGL, and I know in details how to write-read-save an image with win32diskimager, just during the second attempt I forgot to delete all partitions first and that resulted in damaged partitions - that is my educated guess.
...
And now the problem is that no Nook's partition appears in the MiniTool Partition Wizard window, only SD-card with Noogie, so I have nowhere to write an image. This is why I thought the culprit is - a damaged partition table.
Click to expand...
Click to collapse
Since Wiin32DiskImager can read/write from/to a raw physical device, there is no need to clear/fix the partition table of the bad NSTGL using MiniTool or GParted before re-imaging it.
As long as your bad NSTGL when booted on Noogie appears as a raw physical drive in Win32DiskImager's drive-selection menu, you can re-image the bad NSTGL using the raw drive image of the good NSTGL.

NSTGL in question appears as (some) drive in Windows Explorer window, but does not appear in the Wiin32DiskImager's drive selection window, and I run it As Administrator

Nook Color with CM7 - Boot-looping

I changed the Android ID on my Nook Color (with Titanium Backup Pro) and now it is boot-looping, at the point where the arrow head moves around in a circle. It is running CM7, but I'm sure the rom is at least a year old. I think it has CWM recovery. How do I get to recovery and what should I do?
[edit] I found this thread and will see if there is something I can use.[/edit]

I pulled the microSDHD from the device and I can read the boot partition on my PC. Before I attempt repair, I want to copy a few data files from the SDCard's data partition, but I do not see it. How do I mount the SDcard partition so that I can copy the files? I know how to do this once I can successfully boot to the Android desktop, but not without the desktop.
I looked through verygreen's SDCard installation instructions here and I can execute boot into recovery, but that just looks for update files and shuts down. I did not get a menu to allow me to mount the data partition via USB for the PC to read or for any options at all.

I have a bootable SDCard (verygreen's) and removed it to boot from emmc. That works, so the problem is on the microSDHC. When I insert the microSDHC (8GB) card in the card reader on my PC, I see the first three partitions are healthy and the last (5.9GB) is not. The only partition that I can assign a drive letter to is the first partition, Boot. Is there any repair I can do to that forth partition?