Database Users

[Gparted] Nook Simple Touch resize partitions non-destructive

!! Important: Make a backup of your Nook device first !!
Resize partitions
1. Download Gparted LiveCD
2. Extract onto FAT / FAT32 USB memory stick or burn to CD-ROM
3. If on a USB memory stick, run \utils\win32\makeboot.bat from the memory stick.
Do NOT run makeboot from a hard disk!
4. Boot computer from USB device into Gparted
5. Connect your Nook running Noogie of a Micro USB card (this will make the partitions visible to Gparted).
6. Resize the last partition (nr 8) labelled "data" (= Barnes & Nobles content)
Make sure to move the partition to the far right.
7. Move the next-to-last partition (nr 7) labelled "cache" without resizing it.
8. Extend the next-to-next-to-last partition (nr 6) labelled "nook" (Side loaded content) to fill the gap.
9. Remove USB cord, Micro USB card and boot your Nook.
10. In Settings you can inspect the amount of storage space.
I received errors when the partitions were about to be moved on the disk.
I changed the partitioning resize to field where it says "Align to:" from "MiB" to "Cylinder". After a 2nd attempt and doing each partition individually all worked out well.

For those only with Windows, download Gparted LiveCD iso image and use virtualbox to boot from it. It still worked well.
Edit: I successfully repartitioned two of my Nook Simple Touch using the method above + virtualbox + Gparted LiveCD iso.
Surprisingly, the size of partitions in my two NST were slightly different, suggesting that the physical size and location of partitions don't matter as long as their order and type in the partition table are as expected and the size is big enough to hold files there. I resized and moved the last three partitions as I wanted several times and made sure they work well.
Factory reset, upgrade to 1.2.1 (this seems to require the cache partition to be big enough to hold the firmware update file: something like 128MB worked for me), rooting all worked well with resized partitions. I ended up shrinking the cache partition down to 32MB and the data partition to 128MB, reserving 1.11GB for the side-loaded contents. I'm sure the system partition can also be shrunken, but I didn't go that far.

Why a live cd? Does installing gparted to whatever linux flavor you're using not work?

I don't use linux on my PC... only on hacked router & nas.
Goggles2114 said:
Why a live cd? Does installing gparted to whatever linux flavor you're using not work?
Click to expand...
Click to collapse

So dump Noogie on a microsd card run noogie and while noogie's running plug nook into pc? Do you just plutg it in and it does everything auto, or does something in noogie need to be run? Does this work on a nook touch glow?
Sorry to sound so dense but rooted using NookManager.
Edit more to the point it's throwing up an error when trying to move sdb8 around. It shrank fine just won't move. Not sure why. Not getting any useful error messages. Just 'can't have overlapping partitions.'
Odd. I was able to move it twice and get it to behave. Yet do the same n one move and Nothing. Apologies for the rinning Log just. Meh. The rest of the partitions resized in one step. sdb8 was the one that needed two steps.
Aaaand Success. Showing up as having 913MB free as opposed to like 212 or whatever.
Edit: now I'm getting a constant 'low space' warning from nook (understandable.) And installing apps is hit/miss on if they'll actually install. Keeps claiming space issues.
Query. Do apps install to the BnN partition or where?

Good to hear another success story. In my case I squeezed all the way to 1.45GB for the side-loaded contents. boot/rom/system/cache/data partitions are shrunken, and factory partition is busted. I had to use fdisk instead of GPartED to completely recreate the partition table, though.
I think, apps are installed to the data partition (the 8th one) under /data/app. Before being installed it's downloaded to cache partition (the 7th one). In my case I gave 16M for cache and 128M for data. If you are low on the data partition and have some space left on the system partition, you can move apps from /data/app to /system/app.
Goggles2114 said:
So dump Noogie on a microsd card run noogie and while noogie's running plug nook into pc? Do you just plutg it in and it does everything auto, or does something in noogie need to be run? Does this work on a nook touch glow?
Sorry to sound so dense but rooted using NookManager.
Edit more to the point it's throwing up an error when trying to move sdb8 around. It shrank fine just won't move. Not sure why. Not getting any useful error messages. Just 'can't have overlapping partitions.'
Odd. I was able to move it twice and get it to behave. Yet do the same n one move and Nothing. Apologies for the rinning Log just. Meh. The rest of the partitions resized in one step. sdb8 was the one that needed two steps.
Aaaand Success. Showing up as having 913MB free as opposed to like 212 or whatever.
Edit: now I'm getting a constant 'low space' warning from nook (understandable.) And installing apps is hit/miss on if they'll actually install. Keeps claiming space issues.
Query. Do apps install to the BnN partition or where?
Click to expand...
Click to collapse

What's the point of doing all this?
You gave a list of instructions, but not the goal they achieve.

L_R_N said:
What's the point of doing all this?
You gave a list of instructions, but not the goal they achieve.
Click to expand...
Click to collapse
Which post are you referring to?

Troute said:
Which post are you referring to?
Click to expand...
Click to collapse
.c0.'s original post.

His instructions describe how to use gparted to resize the partitions on the NST to make full use of the memory available after you have rooted it. I've used gparted before so maybe they were clearer to me than to others but the thread title was the main clue.

Troute said:
His instructions describe how to use gparted to resize the partitions on the NST to make full use of the memory available after you have rooted it. I've used gparted before so maybe they were clearer to me than to others but the thread title was the main clue.
Click to expand...
Click to collapse
I kind of thought that Nook's internal 2GB flash is already sanely formatted (i.e. most space is dedicated to the partition that is mounted at /media). If that is not the case, then that should be noted in the first post. It would also be cool if it said exactly how much space each partition has (I think i saw these partitions back when i've used Noogie to make initial backup of my device, but i don't remember the details), and how much space you would gain, and on which partition (and where it is mounted).

L_R_N said:
I kind of thought that Nook's internal 2GB flash is already sanely formatted (i.e. most space is dedicated to the partition that is mounted at /media). If that is not the case, then that should be noted in the first post. It would also be cool if it said exactly how much space each partition has (I think i saw these partitions back when i've used Noogie to make initial backup of my device, but i don't remember the details), and how much space you would gain, and on which partition (and where it is mounted).
Click to expand...
Click to collapse
Thanks! i did the work 880MB for side loaded content now!!!
on one of my NST i had an issue resizing the FAT32 partition and i had to format it to make it work.
Other than that all went ok!
Thanks

How to maximize RAM available for apps
I found this easy to read table here.
I doubt that I will ever download books from B&N. I want to minimize the space for that. I infer that I should minimize partition 8 that gets mounted to \data. Is there a practical / actual minimum for this?
I see that anything I copy in from my PC over USB is going into media. 100MB should be more than I need. I could put in an SD card for this sort of thing if it grows.
My question is, which partition do I want to increase to make the maximum available to apps downloaded from the google marketplace?
If an application requires a minimum of 512 MB of RAM, which partition(s) do I need to set >= 512?
New additional question: Upon some further research, I see that you can use sd cards for swapfiles to increase system RAM up to a maximum of 4GB. Does anyone know if it is possible to use this built-in storage for the same purpose?
.c0. said:
!! Important: Make a backup of your Nook device first !!
Resize partitions
1. Download Gparted LiveCD
2. Extract onto FAT / FAT32 USB memory stick or burn to CD-ROM
3. If on a USB memory stick, run \utils\win32\makeboot.bat from the memory stick.
Do NOT run makeboot from a hard disk!
4. Boot computer from USB device into Gparted
5. Connect your Nook running Noogie of a Micro USB card (this will make the partitions visible to Gparted).
6. Resize the last partition (nr 8) labelled "data" (= Barnes & Nobles content)
Make sure to move the partition to the far right.
7. Move the next-to-last partition (nr 7) labelled "cache" without resizing it.
8. Extend the next-to-next-to-last partition (nr 6) labelled "nook" (Side loaded content) to fill the gap.
9. Remove USB cord, Micro USB card and boot your Nook.
10. In Settings you can inspect the amount of storage space.
I received errors when the partitions were about to be moved on the disk.
I changed the partitioning resize to field where it says "Align to:" from "MiB" to "Cylinder". After a 2nd attempt and doing each partition individually all worked out well.
Click to expand...
Click to collapse

I have a little (maybe big?) problem. Can't partition with Gparted Live, as gparted scans my /dev/sdb (nook) infinitely. If I plug out my nook, other partitions (in my case: /dev/sda) become visible and ready. Looks like my nook hangs gparted. Tried on 2 different PCs and no effect. Tried different version of Gparted Live (i486 & amd64) - still nothing.
Of course noogie is inside the nook unit, ready and steady. Already made a backup of (non-rooted) device, plus partitions are visible in Minitool Partition Wizard on Windows 7.
What to do in this situation? Is Linux the only safe way to repartition device? Or maybe Minitool would be as effective and safe?
If Linux is the only way to go, how to make nook visible to Gparted?
Please, experts.

DJ Athlon said:
I have a little (maybe big?) problem. Can't partition with Gparted Live, as gparted scans my /dev/sdb (nook) infinitely. If I plug out my nook, other partitions (in my case: /dev/sda) become visible and ready. Looks like my nook hangs gparted. Tried on 2 different PCs and no effect. Tried different version of Gparted Live (i486 & amd64) - still nothing.
Of course noogie is inside the nook unit, ready and steady. Already made a backup of (non-rooted) device, plus partitions are visible in Minitool Partition Wizard on Windows 7.
What to do in this situation? Is Linux the only safe way to repartition device? Or maybe Minitool would be as effective and safe?
If Linux is the only way to go, how to make nook visible to Gparted?
Please, experts.
Click to expand...
Click to collapse
If Gparted doesn't work for you, I'd highly recommend Minitool Partiton Wizard - it's what I used to partiton my Nook. Nice, easy UI, too.

Yeah, I often work with Minitool, but is it as safe as Gparted when it comes to nook?

DJ Athlon said:
Yeah, I often work with Minitool, but is it as safe as Gparted when it comes to nook?
Click to expand...
Click to collapse
Yeah, it is. Just make sure to make a Noogie backup before repartitoning.

Sorry for bugging you, but can't shrink userdata(ext3). What to do? Delete that partition and re-create it or...?

DJ Athlon said:
Sorry for bugging you, but can't shrink userdata(ext3). What to do? Delete that partition and re-create it or...?
Click to expand...
Click to collapse
Yes, delete and recreate is the way to go.

Please, people, help me
Write step to step guide for work with Minitool Partiton Wizard
I want to free the reserved space for B&N books of my NST ver. 1.2.1
The device is already rooted.
I installed Minitool Partiton Wizard on my PC, but after connecting it thru USB cable with my Nook, it only see "official" 240MBs.
Cannot find other around 750 MB reserved storage for B&N books ?
What to do
Explain to me, please

[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]

Note: This guide is geared toward the Samsung Captivate. If you have a different device, try your device's forum, or search this thread.
Are you using ICS and pulled your phone out of your pocket only to find that it had this screen, saying "Encryption unsuccessful" and your only option a button that said "Reset Phone"? Don't press it! Try rebooting a few times with your external sdcard out first. Sometimes that will fix the issue. If not, take a deep breath and follow the guide below to get your phone usable again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Too late? Already hit the button? Then you know this screen:
Here's the bad news:
Your partitions for /data and /sdcard are no longer accessible. Latest news points to a bug in the firmware for the memory card in your phone. ICS uses a new function that doesn't work correctly with the affected phones.
Good news:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9-11 every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Here were my steps to get your phone working again:
Realize that you may have just lost whatever was on your sdcard and it's your own fault. For me, this was acceptance that *I* installed ICS on my phone and now CWM backups, photos, and more were gone. Once your realization has set in, move forward.
Acquire an micro SD card that you will put into your phone. This will contain your new /data partition as well as your new /sdcard partition. I recommend at least 8GB. If you already have a card, backup whatever is currently on your micro SD card - you *WILL LOSE* everything on this card in the next few steps.
Boot into clockwork mod, using either 'adb reboot recovery', or some other combination of buttons.
Partition your mircosd card through CWM. This will be 'advanced' then 'Partition SD Card'. The first size you choose will be the size of your /data partition. I have a 16GB card and chose 2GB for /data. This will leave me with (16GB-2GB) 14GB for /sdcard. You can choose a different size if you like, depending on how big you want your internal data partition to be. Choose 0M for swap. This process will take a few minutes, so keep waiting, you impatient jerk.
Download the latest build of ICS for your phone and put it on your micro SD card. (You can mount it to your computer at this point in CWM with 'mounts and storage' 'Mount USB storage')
Create a full backup. Just in case. Put it on a computer, dropbox, whatever. Your phone isn't a safe place for backups.
Wipe user data, cache, & system. Now install the ICS package you just put on your card and reboot.
The first boot will take a while, as all first boots do, but after a while you should be back in ICS. Exhale (If you're not exhaling at this point, post something in this thread and I or someone else will help get you running)
Check Settings > Storage and see if your new /sdcard partition (For me it was about 14GB) shows up as 'USB Storage' or 'SD Card' If it's USB storage, then your micro sd mounted to /sdcard successfully and you're done. You should be able to take a picture and have it save. If not...
Edit etc/vold.fstab with whatever you use personally (root explorer for me) and swap paths for /emmc and /sdcard (the part that starts with /devices/platform...). Someone more intelligent than me can probably make this a CWM zip. This step is telling ICS to swap your /sdcard (broken internal sdcard) and your /emmc (working external sdcard). It will probably look like this when you're done:
Code:
# internal sdcard that is no longer working
dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
Reboot with your new vold.fstab and check your storage amount in ICS and test your camera (easy test to see if Android can write to the sdcard). Hopefully now this is working for you.
Let me know if you have any questions or (hopefully not) problems!
Notes for myself and devs:
ICS is a lot pickier about mounting filesystems, and if it can't mount /data correctly, it assumes it is encrypted. It really isn't, firing off https://source.android.com/tech/encryption/android_crypto_implementation.html an misleading encryption message.
In ICS and in CWM, when I look at /dev/block/platform/ I only see s3c-sdhci.2 and s5pc110-onenand. The s3c-sdhci.0 block is missing completely. I'm not sure how to even touch the /data or /sdcard filesystem at *ALL*
Oh well.

the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?

edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.

edecan said:
the camera does not work. The main memory is corrupt.
Using 8gb memory card. Do you have any suggestions for the camera?
Click to expand...
Click to collapse
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
chmod 644 /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot

TRusselo said:
#1 dont quote a post that is un-related (especially huge 1st posts)
#2 dont ask unrelated questions in a thread
#3 dont ask questions PERIOD in development threads.
Click to expand...
Click to collapse
Actually, the question he asked is extremely relevant to my post, specifically step 9. I agree with you #1, though.

cgugino said:
This is happening because your phone is still trying to use your internal sdcard, but it isn't accessible. You will need to trick your phone to use the external sdcard as if it was the internal.
You will need ADB working and your phone in USB Debugging mode (Options>Development) for this part:
Code:
adb pull /system/etc/vold.fstab
This will put your vold.fstab file in the directory you have command prompt running. Open this file and swap the references of 'mmc2' with 'mmc0' and 's3c-sdhci.2' with 's3c-sdhci.0'. It should look something like the example in step 10 of post #1 when you're done. Save and close the file.
Now use these commands:
Code:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
Code:
adb push vold.fstab /emmc/vold.fstab
adb shell
su
mount -o remount rw /system
cp /emmc/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
adb reboot
Click to expand...
Click to collapse
Thank you! Everything is working now thank you.
ICS currently using 4.0.3 version of the Onecosmic's ROM version 2.1.
I want to use version 3.1 or CM9 KANG, this time when the boot screen remains. Have his solution

when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot

kwhee07 said:
when i follow the steps to pull the file through adb, i get "remote object '/system/etc/void.fstab' does not exist"
phone boots, but when changing via root explorer, the files revert back when I reboot
Click to expand...
Click to collapse
Make sure you're using vold and not void, as in VOLume Daemon.
OR
Make sure you're remounting the file system with Root Explorer (press the button to change R/O to R/W)

roms kernel glitch does not work.
Boot screen does not turn on the device remains.

edecan said:
roms kernel glitch does not work.
Boot screen does not turn on the device remains.
Click to expand...
Click to collapse
What ROM are you on?
Did you flash a ROM update? If so, this overwrites the vold.fstab and you'll have to fix it. If you're on CM9, try reinstalling the latest update package, then perform steps 9 and on from the first post.

cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb

kwhee07 said:
cgugino: i tried again via root explorer(both of the things I did wrong, you called out perfectly, thanks for keeping me in check!), but now the phone wont leave boot animation. I guess I'll flash again, and try to edit the document on my computer via adb
Click to expand...
Click to collapse
Let me know if it doesn't work. Did you partition your external sd card?

no, have not understood me.
Just set up onescomics rom. Install another rom.

Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.

edecan said:
no, have not understood me.
Just set up onescomics rom. Install another rom.
Click to expand...
Click to collapse
The only way I know how to make this work is with the CM9 ROM -- I don't know what onescomics is and if you can't get your phone working, I would recommend staying on ICS.

iperezru said:
Thanx!! I was starting to think i was the only person in the world i have this issue.
In my case, I found several weeks ago my first "encrypted unsuccessful" screen and of course, I push de button. However, I didnt loose all the information in the internal sd card, only system one. I did all wipes and factory reset, but issue continued there. I fixed it connecting the phone to PC during boot.
Nowadays, the problem happens always the phone boots and conecting to the PC is enough to fix it and restart normally.
I understand your guide is in the case you have lost TOTALLY your access to internal Sd Card, isnt it?
However, this is not a permanent solution.
Click to expand...
Click to collapse
That is the case for me where the internal sdcard and data partition is totally lost.
I cannot say for sure how the guide would affect you if you followed it. If CWM thinks that your partitioned external sdcard has the /data partition on it (you could use the mount command and see), when you install ICS, it would install to your actual external sdcard. You may have to edit the vold.fstab in the installer zip file before you install, so that on the first boot, the phone won't try to boot to your internal partitions. Honestly, if you're still under warranty, I'd just flash to stock and try and exchange it.
I know that the 'Encryption unsuccessful' message is triggered because the phone has trouble mounting the /sdcard partition, and with ICS, it assumes that the partition is encrypted. It may be that your partition is taking too long to load, or that it is having issues reading. Either way, I'd make regular backups of *everything* onto your computer, in case one day the whole thing craps out.
As for me, even after I went back to stock Eclair, up to Froyo, and up to GB, I could never get the /sdcard or /data partitions to recognize.
See the section on 'Booting an encrypted system' here for more about how ICS detects 'encrypted' filesystems: https://source.android.com/tech/encryption/android_crypto_implementation.html

cgugino said:
I found a *workaround* to get my phone to at least work again. Note: You will need to perform steps 9 and on every time you flash a ROM or ROM update, because flashing overwrites the vold.fstab file.
Click to expand...
Click to collapse
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?

raz123 said:
Do you mean to say that the phone will thereon permanently have to use a microSD when updating ROMs?
Click to expand...
Click to collapse
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.

cgugino said:
Sadly, yes. You will have to use a microSD card for *everything.* With my phone, I basically don't have an internal SDcard anymore. Completely inaccessible.
I keep a modified vold.fstab file in my /backup folder, and whenever I update CM9, I replace the one that is included and installed in the update with my modified one. This weekend, I might make a CWM-flashable zip file that does this as a side project.
Click to expand...
Click to collapse
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466

raz123 said:
Hmm.
How strange.. Just a few hours ago, this phone was rocking under ICS and the internal SDcard was great.
EDIT: Do you think using AdamOutler's (HW) unbricking method could help?
http://forum.xda-developers.com/showthread.php?t=1242466
Click to expand...
Click to collapse
I agree with you on the strangeness! I wish I could offer a solution to get your internal sdcard files back, but there doesn't seem to be one at the moment. The other interesting thing is that the encryption guide for 3.0 says that encryption isn't even usable with the YAFFS file system, which I believe the Captivate uses.
If your phone is under warranty...there may be another option for you. I contacted about 3 other people that had threads related to this issue and everyone that responded said that Samsung replaced the motherboard.
What's your phone build? Mine is 1012 Rev 0.4
Edit: I haven't tried Adam's unbricking mod, and don't think I will. For me, the phone is now working perfectly and has full functionality, outside of the loss of the original /data and /sdcard partitions. I'm not going to crack it open and start soldering. However, if you do try his mod, please let us know the results!

Urgent ..... i cant restore my NST :(

guys , iam very shocked
i have make and image from boot partion when i boot with noogie and i was about 289 MB , but when i root my device and minimaltouch and i set some mistake in steps then i decide to backup my device again , when i download partiotion wizard and delete all 7 partition and when i write my image to my device when i had boot up with noogie image ..... when i try use my nook ... it's just say start up ur nook then stopped to load
any urgently help :crying:

Sorry, I have no experience with any of these automatic tools.
Generally speaking, it's a bad idea to delete partitions.
Yes, I know that's a bit late to say now.
I'd really like to know why so many people have problems with these things.

when i write the image to my nook device , it's appear that there's 5 partions not 7 partions , may that the reason , i can upload my image if anybody can help with that
i just need any solution to run back my nook again

Don't you have an old full backup with a size of about 2 GB?
If you have that, writing it will restore all your partitions.
The standard Nook factory recovery does not do partitioning.
It requires that the partitions be set up and working already.

ok , let me tell u how i make backup
first i do noogie image on my memory (2GB) and then boot with it and my nst screen say rooted for ever when i connect my device to pc then there's a partition named (boot) and other partition cant be opened..... then i used diskimage and take image from the memory it self (partition named boot) then i saved to my pc and compress it and was about 300MB
when i root my device with minimaltouch and crashed with me , then i deceide to use my recovery , then i boot my nook with noogie image and then open partitioning program then i found 7 partions in my nook , then i del them all ( i didnt format but after many times i failed to make recover then i make format with fat32) and then used diskimage to write the image to sd disk and there's another disk cant bemount ...... when i run my nook , it's just stop at screen "your nook device start up" ..... then i tried many times , no hope , so ....... what the mistake i do
and when i write the image , i checked my device partitions , it's just 5 (4 partitioned and the 5th one unallocated .... )
when i back to home ..... i post an image about my partitions after do image and if u want check my image , i can upload it
and for check how u make back/restore NST , check this
http://forum.xda-developers.com/showthread.php?t=1142983
i hope anyone provide me any info/help
thx to Renate for supporting me

When you are using Noogie and a Windows desktop, only the first (boot) partition will be visible.
You will get a drive letter for it.
If you go to disk management in Windows, you will see that there are 7 partitions, although only the first has a letter.
I would have suggested that you use Win32DiskImager.
It will take a drive letter but save the entire physical device, including all 7 partitions.
You will end up with a file on your desktop of 2 GB.
I'm not sure whether your 300 MB is a full backup or not.

there's some pic of my device after every time i write backup image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
there's another pic from original backup i must have when i do write image
so , i need nook , cache and userdata partions
if they comment in all nook devices , so anybody can write this image that i have to flash and add this partitions from another original nook and save back up .....is this will work or anyone get what i mean???
anybody can do it , or can help me and need my back up , i can upload it for him
thx at advanced

I'm getting really confused what is going.
I have no idea what you have for backups.
Do you have anywhere a file like something.img with a size of 1,9XX,XXX,XXX?

speedman2202 said:
there's some pic of my device after every time i write backup image
Click to expand...
Click to collapse
The good thing - you have you factory partition, so you can restore generic image, then roll your unique settings.
I'm not giving you any details - you need to do lot's of reading yourself.

Renate NST said:
I'm getting really confused what is going.
I have no idea what you have for backups.
Do you have anywhere a file like something.img with a size of 1,9XX,XXX,XXX?
Click to expand...
Click to collapse
Renate , i told u in the previous post how i i make recovery ,and the image i take was about 300MB only , not 2 GB as u say ...... i just provide u an pic of my nook partition after i write my backup image ( the first pic) and i provide u the partitions i must have when i write the image on my nook , i just show the deference between my nook partitions and normal nook partitions .... i only missed 3 partitions ( nook , cache and userdata partitions) beside my other 5 partitions then i guess my nook work again
did u get what i mean?????
ApokrifX said:
The good thing - you have you factory partition, so you can restore generic image, then roll your unique settings.
I'm not giving you any details - you need to do lot's of reading yourself.
Click to expand...
Click to collapse
i have think about that , that the first 2 partitions (boot , factory) is very important to my nook device and have all unique info , so can u help me or provide me a full recovery image with my unique info that i can run back my nook??
also if u provide me any links or thread i will be thankful to u
ty all

I wasn't clear from that 2nd image whether you had such a backup.
You have to recreate the partitions.
The easy way would be to restore a full physical backup.
The other way is to manually recreate the partitions.
Your boot is bombing because there is no data or cache partition.
They don't need anything in them, but they have to exist.
Maybe somebody can tell you an easy way to recreate them.
On my Nook, the partitions are as follows:
Code:
[b]Partition Type Start End Size (bytes) Mount[/b]
--------- ---- ----- --- ------------- --------
Total 0 933 1,958,739,968
mmcblk0p1 vfat 1 38 79,691,776 /boot
mmcblk0p2 vfat 39 46 16,777,216 /rom
mmcblk0p3 ext2 47 141 199,229,440 /factory
mmcblk0p4 142 926 1,646,264,320
mmcblk0p5 ext2 142 285 301,989,888 /system
mmcblk0p6 vfat 286 405 251,658,240 /media
mmcblk0p7 ext3 406 525 251,658,240 /cache
mmcblk0p8 ext3 526 926 840,957,952 /data
Unused 927 933 14,680,064

Based on what you're showing in the restore, you have a good shot at recovering. You have a partition called /factory, and there are files in it.
What happens if you let it fail to boot 8 times (ie, power it on, let it 'get stuck,' power it off, power it back on again) ?
I don't know if the recovery scripts can get your extended partition and its sub-partitions working for you again or not. If they can, that's the way to get them to do it.
If not, you will need to learn the tools for doing it. I would recommend either setting up vmware player and linux in that, or finding a USB-bootable linux distribution, booting from that and then using it to work on fixing that extended partition.
In either case, you will need to boot from Noogie so that you can use fdisk or gparted to create the remaining partitions you need. Hopefully, the recovery file available in the partial restore you've done has the ability to do that for you, though I don't know if it does.

speedman2202 said:
i have think about that , that the first 2 partitions (boot , factory) is very important to my nook device and have all unique info , so can u help me or provide me a full recovery image with my unique info that i can run back my nook??
also if u provide me any links or thread i will be thankful to u
Click to expand...
Click to collapse
I haven’t been through full restore from generic image fortunately (for me!).
I can neither give you detailed instruction and nor help if something goes wrong.
I don’t even know if we have the detailed instruction on how to restore from generic image and roll in unique factory setting (in one place)
But I’m sure forums have all those questions answered.
Search is you friend.

i am think about if i got an nook backup and modified the factory partions that i replaced all files , then i burn it
i guess my nook will run back?
how u think about it guys

speedman2202 said:
i am think about if i got an nook backup and modified the factory partions that i replaced all files , then i burn it
i guess my nook will run back?
how u think about it guys
Click to expand...
Click to collapse
Yep. That's exactly how is should work.
Once you restore it, don't forget to write step-by-step instructions for others

the main problem , from where i can get an original backup nook device that i will work on???
anyone have an backup for it's nook (before he start use it or even root is preferred) and upload for me , i will be thankful for him
anyway i have another question to u Renate
u say cache and userdata partitions they must be exist but they r empty , how about the nook partitions???
i guess it's have the file system , it's it????

I've been waiting for somebody to jump in and tell you how you can partition your Nook's internal card.
If you have a Linux desktop system you can boot with Nookie and partition it, I believe.
ClockworkMod can't partition the internal card.
You need all seven partitions set up in the right order.

speedman2202 said:
the main problem , from where i can get an original backup nook device that i will work on???
anyone have an backup for it's nook (before he start use it or even root is preferred) and upload for me , i will be thankful for him
Click to expand...
Click to collapse
"original backup nook" was posted somewhere on this forum, I just can't formulate search string to find it.
I guess, I'm trying hard enough.
Try instruction from this post.
http://forum.xda-developers.com/showpost.php?p=27893293
And read whole thread as well
---------- Post added at 02:20 PM ---------- Previous post was at 02:19 PM ----------
Renate NST said:
I've been waiting for somebody to jump in and tell you how you can partition your Nook's internal card.
If you have a Linux desktop system you can boot with Nookie and partition it, I believe.
ClockworkMod can't partition the internal card.
You need all seven partitions set up in the right order.
Click to expand...
Click to collapse
If you like GUI, you can use "parted".

i am ask about if anyone have unrooted nook and take an backup of it's device ..... can he upload it for me that i can edit it that i use for my own nook?

UP

[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

Can I unbrick my nook2 after write noogie.img directly to the NOOK2 istead of SD card

I made a big and foolish mistake and wrote noogie.img directly to the NOOK2 istead of SD card. So evereytime I boot the nook2, the screen shows 'rooted forever' even I remove the SD card. Because the windows doesn't recognize the nook2 in the usb mode, I cannot use roadkil's diskimage to write my bakcup image.
Maybe I'll buy a new one for my fault.:crying:

Did you ever backup your /rom partition?
If you only wrote Noogie (~79 Megs) you may be alright.
That would trash the partition tables and the /boot partition but /rom, /factory and all the rest of the partitions should be ok.
Since it's booting ok with noogie right now, the thing to do is to do a full backup.
That way you can save the chance of recovering the /rom or /factory partition.

Renate NST said:
Did you ever backup your /rom partition?
If you only wrote Noogie (~79 Megs) you may be alright.
That would trash the partition tables and the /boot partition but /rom, /factory and all the rest of the partitions should be ok.
Since it's booting ok with noogie right now, the thing to do is to do a full backup.
That way you can save the chance of recovering the /rom or /factory partition.
Click to expand...
Click to collapse
Yes, I messed up the Noogie (~79 Megs) stuff as you said.
I used to restore my nook system using a file 'NOOK ROOT ROM v2.4.img'(1.82Gb). Could you instruct me how to unbrick it safely? Thanks alot.:good:

You're not very clear.
Did this 'NOOK ROOT ROM v2.4.img' get saved directly from your Nook?
Nooks have unit-specific data on them, including serial number, MAC address and various security keys.
If you just clone somebody's info over you may cause problems for them or you.
That's why I asked if you had backed up your /rom partition. Did you?
So far, you might not have destroyed things too badly.
If you copy a ~1.9GB image that you got from somewhere else, then you will have lost forever the unit-specific data.
That's why I asked you to use noogie to copy what is left of the internal memory on your Nook to a safe place on your PC.

http://reviewhorizon.com/2011/07/how-to-restore-nook-touch-n2e-to-its-default-factory-state/
cached:
http://webcache.googleusercontent.c...y-state/&client=firefox-a&hl=en&gl=uk&strip=1
http://forum.xda-developers.com/showthread.php?t=2608815
http://forum.xda-developers.com/showthread.php?p=53545426
http://forum.xda-developers.com/showthread.php?t=1475613
http://forum.xda-developers.com/sitesearch.php?q=factory reset nook touch

Renate NST said:
You're not very clear.
Did this 'NOOK ROOT ROM v2.4.img' get saved directly from your Nook?
Click to expand...
Click to collapse
Yes, I've backup my system as soon as I got my nook. It's a 1.86Gb img file.

wozhere said:
http://reviewhorizon.com/2011/07/how-to-restore-nook-touch-n2e-to-its-default-factory-state/
http://forum.xda-developers.com/showthread.php?t=2608815
http://forum.xda-developers.com/showthread.php?t=1475613
http://forum.xda-developers.com/sitesearch.php?q=factory reset nook touch
Click to expand...
Click to collapse
I'll do some research on your links. Thanks dude.

With the CWM and Touch-Formatter v2, I've done the following steps --- "Copy the zip onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select install zip from sdcard
Then select choose zip from sdcard
Select Alpha-FormatTouch-2.zip, click yes and wait till the process finishes.
Go back, eject the sd card, and click reboot.
But after reboot, the nook is stuck in 'Read Forever' sopt.
I have my original img file, but I don't know how to restore the image using DiskImage because there's something wrong with USB(maybe nook's system is messed up) and I CAN'T find the 1.82 drive.

leewaye said:
With the CWM and Touch-Formatter v2, I've done the following steps --- "Copy the zip onto the root directory of the sdcard you burned the CWM.(Don't extract them)
Insert the sdcard on your nook, and boot it.
On CWM select install zip from sdcard
Then select choose zip from sdcard
Select Alpha-FormatTouch-2.zip, click yes and wait till the process finishes.
Go back, eject the sd card, and click reboot.
But after reboot, the nook is stuck in 'Read Forever' sopt.
I have my original img file, but I don't know how to restore the image using DiskImage because there's something wrong with USB(maybe nook's system is messed up) and I CAN'T find the 1.82 drive.
Click to expand...
Click to collapse
the back up u got if it was before write noogie image to ur nook directory .. so u saved ur nook ..... i will repeat ... if u got back up from ur nook directly with (1.8 GB size almost) before u write noogie image on ur nook ... so u ok!!!
from that point follow my instructions to recover ur nook:
1- get sd card and write noogie image to it ( dont mess ur hard disk drive ... i do it once and i got recover all my HDD files )
2- insert the sd card that on nook and power on ur nook and rooted for ever logo will show as soon as u do ( if ur nook doesnt power on so far then plug ur nook in charger cuz need to charging)
3- connect ur nook to ur pc and will show as a SD card
4- download this program "Roadkil's disk image" (go google search and download)
5- install/open the program and u will see all partitions and all disks on ur pc ... let say u only connected 1 HDD with capacity 500GB then u will find that Disk 0 (500 GB) and Disk 1 (1.89 GB) and Disk 2 (removable) , then choose that disk "Disk 1 (1.89 GB) " and make sure disk size 1.89 GB
6- choose the image directory from ur pc and then Hit start
7-and after it finish ..... do safely remove and unplug the SD card from ur nook and power on ur nook and it should be working fine
but before do anything .... how u do backup for u nook and got this file .... if u read recovery/restory ur nook and read and know how u do recovery then proceed the steps i said to u .... but plz if there more details u want tell us , go a head before do anything
thx

I've saved my nook.I wish to express my gratitude to speedman2202,wozhere and Renate NST for your immense practical help.:laugh:
To conclude the experience that I learn from unbricking my nook touch, there're 2 issues to mention:
1.In my first step,Nook can be formated to restore factory system With the CWM and Touch-Formatter v2.http://forum.xda-developers.com/showthread.php?t=1475613
2.In my case,after reboot, the nook is stuck in 'Read Forever' sopt and windows cannot recognize Nook USB drive.Do the following steps as speedman2202 directs
speedman2202 said:
the back up u got if it was before write noogie image to ur nook directory .. so u saved ur nook ..... i will repeat ... if u got back up from ur nook directly with (1.8 GB size almost) before u write noogie image on ur nook ... so u ok!!!
from that point follow my instructions to recover ur nook:
1- get sd card and write noogie image to it ( dont mess ur hard disk drive ... i do it once and i got recover all my HDD files )
2- insert the sd card that on nook and power on ur nook and rooted for ever logo will show as soon as u do ( if ur nook doesnt power on so far then plug ur nook in charger cuz need to charging)
3- connect ur nook to ur pc and will show as a SD card
4- download this program "Roadkil's disk image" (go google search and download)
5- install/open the program and u will see all partitions and all disks on ur pc ... let say u only connected 1 HDD with capacity 500GB then u will find that Disk 0 (500 GB) and Disk 1 (1.89 GB) and Disk 2 (removable) , then choose that disk "Disk 1 (1.89 GB) " and make sure disk size 1.89 GB
6- choose the image directory from ur pc and then Hit start
7-and after it finish ..... do safely remove and unplug the SD card from ur nook and power on ur nook and it should be working fine
Click to expand...
Click to collapse
Everything shall be retored and the Sun will rise tomorrow again
another important thing to mention is that u can resore system with every correct IMG file as long as the model match. i actually write my system with a img file i download from another guy's img. Now my system is a android version in which i can install some apps.
Thanks guys again. Have a nice day!!:good:

leewaye said:
I've saved my nook.I wish to express my gratitude to speedman2202,wozhere and Renate NST for your immense practical help.:laugh:
To conclude the experience that I learn from unbricking my nook touch, there're 2 issues to mention:
1.In my first step,Nook can be formated to restore factory system With the CWM and Touch-Formatter v2.http://forum.xda-developers.com/showthread.php?t=1475613
2.In my case,after reboot, the nook is stuck in 'Read Forever' sopt and windows cannot recognize Nook USB drive.Do the following steps as speedman2202 directs
Everything shall be retored and the Sun will rise tomorrow again
another important thing to mention is that u can resore system with every correct IMG file as long as the model match. i actually write my system with a img file i download from another guy's img. Now my system is a android version in which i can install some apps.
Thanks guys again. Have a nice day!!:good:
Click to expand...
Click to collapse
did u download nook image from website and write it to ur own nook??!!!
i hope not!!!! :\ , if u do ... ur wifi wont work .... just u can use ur nook as a e-reader only and no benefits to root :|

speedman2202 said:
did u download nook image from website and write it to ur own nook??!!!
i hope not!!!! :\ , if u do ... ur wifi wont work .... just u can use ur nook as a e-reader only and no benefits to root :|
Click to expand...
Click to collapse
My wifi still works well except that my nook shop account is a issue. But I think I can solve it with my own .pmf file to restore my account info.

I finished a utility for recovering files out of a saved Nook backup.
It should be able to recover the /rom partition even if you overwrote the first 79 Megs.
Is anybody interested in trying this?

leewaye said:
My wifi still works well except that my nook shop account is a issue. But I think I can solve it with my own .pmf file to restore my account info.
Click to expand...
Click to collapse
if the image u downloaded and burn it to ur nook contain rom partition of the image publisher ... then when u try his image u now own another device details ( another serial number , Mac address and other changed details) .... so i think when u burn/write the image to ur nook ... it was successfully registered and no need to register again ......anyway the main issue that u have the same Mac address from other device and that may do conflict with u and for sure ..... try get ur own Unique nook device Rom files By Renate utility and thx to her she still keep on developing such these things
thats why i said " i hope not do that" cuz there is another ways for recover deleted/formatted partition
thx
UPDATE: try and check this utility by Renate .... it will help u
http://forum.xda-developers.com/showthread.php?t=2643687
Renate NST said:
I finished a utility for recovering files out of a saved Nook backup.
It should be able to recover the /rom partition even if you overwrote the first 79 Megs.
Is anybody interested in trying this?
Click to expand...
Click to collapse
ummm .... try publish beta test ... and lets see other user says about ur new utility ....and when it success .... publish a full thread about recover ur nook with/with out backup image
thx to Renate
best regards ^^

wozhere said:
http://reviewhorizon.com/2011/07/how-to-restore-nook-touch-n2e-to-its-default-factory-state/
cached:
http://webcache.googleusercontent.c...y-state/&client=firefox-a&hl=en&gl=uk&strip=1
http://forum.xda-developers.com/showthread.php?t=2608815
http://forum.xda-developers.com/showthread.php?t=1475613
http://forum.xda-developers.com/sitesearch.php?q=factory reset nook touch
Click to expand...
Click to collapse
I tried all this methods but they are dont work for me. I havent got a working backup. I can create backups now, manage the particions etc... I think i need a backup file and i need to overwrite the root particion with my own stuff. :S Is this possible?

Backup now what you do have.
Try to extract the /rom partition files using this: http://forum.xda-developers.com/showthread.php?p=53347856