yashsingh1/xdaforums huggingface dataset:
[Nook Touch Android Development] jocala:
You're welcome :)
[Nook Touch Android Development] webvan:
And after some problems with TouchNooter I was able to restore to that image too! Thanks again.
[Nook Touch Android Development] guitar_east:
Yeah I had a similar problem. It seems you can't actually factory restore it. It gets rid of the launcher you installed but whenever I've tried doing the restore it's only a matter of time before the "Tap on the Android to begin" part reappears.

So I've re-rooted, and am leaving it as be until better progress comes out. I don't have market or Gmail working, but Kindle and other apps I need to work so I'll make due for now. I don't want to risk bricking the device as I'm in Canada and there's no Barnes and Nobles to return the Nook to,
[Nook Touch Android Development] douginoz:
oops - tried following these instructions for my Nook Color. DOH
[Nook Touch Android Development] guitar_east:
Figured I should post this incase anyone has a similar problem.

After I made my backup, I began the process to restore. I opened the Partition Magic program and deleted all the partitions on the Nook device. I then opened up Win32 Disk Imager, tried to load up my backup and got this error:

"An error occurred when trying to get the devices geometry. Error 8:".

I tried it on another machine, same thing. The workaround for that problem is going into device manager and disabling your Floppy Disk controller and Floppy Drive. Also, moving the Nook backup image you made to the root of your C drive may work.

Or just try the Linux method, much easier
[Nook Touch Android Development] netdc:
who can give me a backed up file, I use linux and use 'dd' command ,but the file is wrong ,so my nook touch can not be use anymore. I need a full backup file to recovery it . Where can I download this file ? Thanks.
[Nook Touch Android Development] guitar_east:
Eek. So far, the backup files are specific to each individual Nook. How is your file "wrong"? Did you follow the steps correctly? How big is your backup file?
[Nook Touch Android Development] BiGbrother13:
Almost bricked

Add here that you should choose "Physical Disc", not the mounted Partition. Because of that mistake, I got 77MB backup img and bricked my Nook after deleting partition.

Happily I had another backup sized 1957616640 bytes made with win32diskimager-RELEASE-0.3-r27 and unbricked my Nook.

After that I rebackuped Nook with Roadkil's Disk Image and got backup sized 1958739968 bytes
[Nook Touch Android Development] BiGbrother13:
In my case, I just assigned disk letter to a 1.82Gb partition using Windows Disk Management, then successfully restored Nook backup img to it.
[Nook Touch Android Development] ApokrifX:
My 2 cents on backup under Windows XP (same applies to Vista & 7)

win32diskimager-RELEASE-0.3-r27 created backup file 1,957,616,640 bytes (wrong!)

while dd (www chrysocome net/dd - I cannot post link, not enough posts yet) made 1,958,739,968 bytes (right!)

To use DD run:

dd --list

===============================

rawwrite dd for windows version 0.6beta3.

Written by John Newbigin <jn@it.swin.edu.au>

This program is covered by terms of the GPL Version 2.

Win32 Available Volume Information

\\.\Volume{9f722258-b624-11e0-b495-001ec9362694}\

link to \\?\Device\Harddisk1\DP(1)0-0+10

removeable media

Mounted on \\.\e:

\\.\Volume{9f722259-b624-11e0-b495-001ec9362694}\

link to \\?\Device\Harddisk2\DP(1)0-0+12

removeable media

Mounted on \\.\f:

NT Block Device Objects

...

\\?\Device\Harddisk1\Partition0

link to \\?\Device\Harddisk1\DR15

Removable media other than floppy. Block size = 512

size is 1958739968 bytes

\\?\Device\Harddisk1\Partition1

link to \\?\Device\Harddisk1\DP(1)0-0+10

Removable media other than floppy. Block size = 512

size is 79675392 bytes

\\?\Device\Harddisk2\Partition0

link to \\?\Device\Harddisk2\DR17

\\?\Device\Harddisk2\Partition1

link to \\?\Device\Harddisk2\DP(1)0-0+12

===============================

Find NT Block Device Objects with size is 1958739968 bytes

And back it up:

dd if=\\?\Device\Harddisk1\Partition0 of=c:\nook.img bs=1M --size --progress
[Nook Touch Android Development] BiGbrother13:
I successfully made backup and restored several times from this image using win32diskimager.

I downloaded win32diskimager from NookTouch_Rooting guide.

So I think, this image size is good.
[Nook Touch Android Development] radicpunk:
Unable to restore using backup img

I have tried the methods (i.e. OS X and Win7) mentioned on this thread to restore N2E to stock but it is not working.

Apparently it reverts to being rooted (rooted by TouchNooter) even after erasing the partitions and writing with the backup img file.

Has anyone experience the same problem or can advise how to resolve?

(I've also tried in vain using the 8 interrupted boots and pushing the power+bottom 2 buttons.)

Thank you.
[Nook Touch Android Development] bobetto1964:
Wrong size backup

I've tried several times with a Mac and with a PC, with Win32diskimager and dd, with the Nook "brand new" and registered, but my image is always 1.962.934.272 bytes long.

The "dd --list" command give the same result, 1.962.934.272.

The firmware revision of the Nook is 1.0.0, Model number BNRV300.

Anyone else have the same result?
[Nook Touch Android Development] mdall:
Yep, I have the same result and the same Model Number, I have not tested to restore the image though
[Nook Touch Android Development] mr.rugrat:
urgent help with installation gone wrong

hello,

my situation is quite embarrassing.

i backed up only one partition, instead of the whole memory of the nook.

when trying to test the backup, i obviously deleted all the partitions.

my nook won't start. it gets to the "install failed" screen and shuts down.

a hard reset doesn't work, and i highly doubt that it should work in such a case.

for now I don't care if my nook is rooted or not, i just wish to god it's at all usable, and that not all is lost.

I would appreciate any kind of help or tips from anyone.

feel free to respond or contact me at

mr.rugrat@gmail.com

thanks in advance..!
[Nook Touch Android Development] densets:
Im trying to make a img backup of my rooted nook. Im on windows and when i try to use roadkil diskimg the nook appears as "Physical Disk 3 (Not Ready) " and wont let me back it up.
[Nook Touch Android Development] pjfry808:
I also got 1.962.934.272 bytes using 'dd' on OSX10.5. My nook is also a BNRV300. Has anyone yet tried to restore from this image size? Is this a consequence of the device model or the BSD version of 'dd' that OSX uses? An obvious difference is that on OSX the block size has to be given as "bs=1m" rather than the "bs=1M" used on linux. I wonder if the implementation really differs at all.

This ROM mounts just fine but restoring an invalidly formated ROM is probably a sure way to brick my nook.

I also just noticed that the 1.0.1 was applied to my nook automatically even though I had rooted.
[Nook Touch Android Development] fatfishycell:
I backed up mine after rooting and a few tweaks. was 251641856 bytes long so I'm assuming it worked since file size is bigger than the orig. hope i never have to use it tho :D
[Nook Touch Android Development] buoy7:
Hi,

I originally posted this on the nook color forum and was directed here.

Here is my problem. I rooted my Nook simple touch and then applied the software update. This somehow froze the device to the point I had to take the thing apart and disconnect/reconnect the battery. Using touchnooter, I was able to then boot from sd card, but I have somehow hosed my internal partitions. Now when I look at the partitions in Finder, I just have 2 - touchnooter (the sd card) and nook. If I boot with noogie.img on the sd card I can also see the boot partition, but the device itself only displays the 'rooted forever screen' I don't know where the other 5 partitions I have read about have gone.

I have a partial backup, but not of all the partitions (yeah, I know how bad this is) and nobody will post a backup img since each touch is unique and the partitions contain some unique files - device no etc.

So my dumb noob qn is - can I use clockwork and insert some of my touch files into the book color rom nook_complete_restore_1.0.1 to rewrite my internals.

You may wonder why not just run of the sd card with touchnooter - well I no longer have any internal storage and the only way to get books onto the device is through calibre putting them on the sd card. To do this I have had to reformat the sd card once booted so it has space for books. Now if I inadvertently shut down or reboot, I'm frozen again until I re-image the sd card with touchnooter and reboot.

I managed to get adb working and set the failed start counter to 8 - but a reboot just leaves everything frozen. There just doesn't seem to be anything on the internal file structure that would let it boot.

I have my serial number. mac address etc written down - could I somehow recreate the unique files knowing these (I'm assuming the unique files are just a text record of these details)

Can anyone help (or point me at an actual touch backup img)

John
[Nook Touch Android Development] buoy7:
Hi again,

Just a little more detail. Booting with noogie.img on the sd card I can see the 7 partitions in Finder using diskutil list - so at least they are still there. Something I have done has meant that the nook will not boot from internal memory only from an sd card. When I boot with a touchnooter img, The file system doesn't show up at all in Finder. The sd card info box in settings is greyed out and shows 0% free. The internal memory shows 0% free and because the file system hasn't mounted the nook doesn't show up in calibre. So at the moment I have no way of getting books on or off the device. This is really frustrating. Can anyone help or suggest a way out of this. Can anyone point me at an image file for the original file structure so I can return to stock and try again?

Help!

Best Regards

John
[Nook Touch Android Development] mdall:
Have you tried a factory reset ? (following the instructions here "for recovery")

It might work.

Can you mount your 7 partitions and see if there is something in there ?
[Nook Touch Android Development] buoy7:
Hi mdall,

Thank you for replying. Yes I have tried the factory reset and nothing happens. Either I have somehow made the boot partition 'unbootable' (I have no previous experience of android development, so have no idea how the file structure works, or even if a partition needs to be bootable) or I have somehow deleted a vital file. I got into this state as a result of touchnooting (at which point everything worked brilliantly and I was very happy) after which I sideloaded the 1.0.1 update to see what it would change. The progress bar for the update went to about 95% then the device froze - for several days. I tried everything I could read on the various forums to try and get it going again - but nothing worked. In the end I bought the special screwdriver needed to take the thing apart and disconnected the battery. After this, I could boot from the sd card only. If I try and reboot without the card in, nothing happens.

On my mac, using diskutil in Terminal I can see the following 7 partitions:

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *2.0 GB disk3

1: Windows_FAT_32 boot 79.7 MB disk3s1

2: Windows_FAT_32 rom 16.8 MB disk3s2

3: Linux 199.2 MB disk3s3

4: Linux 302.0 MB disk3s5

5: Windows_FAT_32 NOOK 251.6 MB disk3s6

6: Linux 251.6 MB disk3s7

7: Linux 840.9 MB disk3s8

only 1 boot and 5 NOOK mount so that I can see what is in there. If anyone could list (or better yet post the files for) the contents of their boot partition that would be extremely helpful.

At the moment my hopes seem to hang on someone pointing me at a restore image, or the cyanogenmod folk producing a nook touch rom.

Anyone able to help from the above?

Best Regards

John
[Nook Touch Android Development] mdall:
I had already posted the content of my boot partition here if you are interested ...
[Nook Touch Android Development] buoy7:
mdall,

Yeeha, I have fixed it. To start with I deleted everything out of my boot partition and copied across the boot files you posted - no difference. Then I noticed that the partition free space didn't make sense. So I went into disk utility, reformatted the partition which got it back to its full size (not sure what had been happening here to be honest) and copied the files over again. Then for the first time in 3 weeks when I pressed the power button without an sd card in, the screen flickered and it rebooted. The screen then showed a couple of messages about rebooting and it performed a factory reset (which took a few nerve wracking minutes) and then I got the registration screens. End result a completely factory fresh nook. I think I will wait a while before rooting again.

Thanks very much for posting the files - I don't know if it was those, reformatting the partition, or both - but now well happy.

Regards

John
[Nook Touch Android Development] esi435sam:
Hi

my nook touch damage after root.I have not backup .can u attach the your factory fresh Nook or ...?

thanks:mad:
[Nook Touch Android Development] buoy7:
Hi,

I can't post the image as each is unique -it has your serial no and account details etc. Have you tried using the boot partition files from the post above mine? - that was all I needed to get going again

John
[Nook Touch Android Development] densets:
is it save to use the noogie.img on my rooted nook to back it up?
[Nook Touch Android Development] XorZone:
It's always safe to backup, not safe to restore tho.
[Nook Touch Android Development] LastSilmaril:
So I'm curious: why is it necessary to use some partition program to delete all the partitions before writing a backup to the N2E? Wouldn't writing the backup destroy whatever is on the nook anyway? What am I missing?

EDIT: nvm. The guide here uses Win32DiskImager. But Roadkil's Disk Image can write to physical drives without regard for their formatting...which I guess is more dangerous, but also more convenient, as long as you know what you're doing. Maybe the guide should be updated to reflect that; other guides already use Roadkil.
[Nook Touch Android Development] ros87:
10chars...
[Nook Touch Android Development] LastSilmaril:
Yeah, I'm gonna stop talking now
[Nook Touch Android Development] case-sensitive:
How big is the backup file for v1.1

I just received my new/refurbished NST, which came with firmware v.1.0.0. I successfully updated it to v.1.1 and then followed the instruction in the OP to back up the NST (on my linux box). However, when I'm done with dd I got the message

239+1 records in

239+1 records out

251641856 bytes (252 MB) copied, 17.7679 s, 14.2 MB/s

Note that the file size reported is quite different from the number cited in the OP. Could anyone verify that this is correct? Thanks!
[Nook Touch Android Development] Kralik:
Should be closer to 2GB. Sounds like you are backing up a single partition and not the whole device.
[Nook Touch Android Development] cceerrtt:
Are you sure you have specified the entire device, not just one partition? I mean, use e.g. /dev/sdb, not /dev/sdb1 in the dd command.
[Nook Touch Android Development] tonyp22:
I just got a Nook Simple Touch with that Black Friday deal. What's the difference between using this method

http://xdaforums.com/showpost.php?p=15115162&postcount=2

versus win32diskimager to create the initial backup?
[Nook Touch Android Development] fns001:
[Solved] Cannot See Partitions with RoadKill or DiskImager

I used RoadKill to write Noogie.img on to my sd card using Windows 7. The Nook would not boot into Rooted Forever.

So I used DiskImager to write Noogie.img on to the sd card and I booted into Rooted Forever. But neither RoadKill nor DiskImager can find the partitions to back up. I can see a bunch of files on the Nook using Windows file manager or RoadKill. Both Programs see a 75.98mb image but there are no choices to select any other image or partition. Also, Partition Magic sees all of the partitions.

What is wrong and how do I back up?

Solved:

After running as administrator, RoadKill had a physical disk of 1.82GB to select.
[Nook Touch Android Development] ros87:
Very very important that people make sure this 1.82GB "Physical Disk" is present and selected before doing a backup, if not, your back up is not only worthless,

but it will destroy your NST if restored

!!
[Nook Touch Android Development] ram100987:
wow! i am glad I made this backup before fooling around with my nook. I made the back up and it was close to 2gb. tried touchnooter and the screen never flashed black like the instructions on the screen stated after waiting a good 5 min. so i removed the card, rebooted and it boot up like normal, but boot looped at the flashing dots.... so i boot into noogie and the first restore gave me an error about a bad file descriptor... so i immediately tried again and this time it worked and i booted into my factory fresh nook! now i can try my luck at rooting again and know that I have a working backup!
[Nook Touch Android Development] ros87:
Doesn't look like a valid NST image to me.

There can be a few bytes in variation, but yours are missing 8192 sectors compared to the "usual" NST images.

This is why people need to check the size of their backup in bytes, not GB ;)

Here's an example from a working image:

Disk nook_1.1.0_roger_reg_root_apps.img: 1962 MB, 1962934272 bytes
128 heads, 32 sectors/track, 936 cylinders, total 3833856 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

There's nothing wrong with your command, the offset is correct for a working NST image, so your partition table is correct but the rest of the image is not.

That error is typical for trying to mount something that isn't a real partition

I.E: (trying to mount a gzip file)

root@ubuntu:/home/develop/Nook/images# mount -o loop -t ext2 nookRestore_1_orig.img.gz mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Try redoing your backup in Linux: (substitute /dev/sdb with correct device)

dd if=/dev/sdb of=nst_backup.img bs=1M
[Nook Touch Android Development] LastSilmaril:
Lol, this is very strange - I've backed-up/restored several times with those backups without issue, and have been able to access all the files via the Linux Reader tool I linked to above. Interestingly, I just made a backup of my brother's nook using the same method (Roadkil) and the resulting file was the correct size (like yours, Rog).

I noticed when I opened RoadKil that the size of my brother's physical disk was reported as 1.83GB, but mine is reported as 1.82GB. Could this be because at some point, I made a backup that was smaller (maybe using win32diskimager, or maybe using roadkil) and have written that image back at some point? I am loath to hose my entire Nook over this when it works just fine (as do the backups I've made). In fact, I don't see why doing a factory restore + reset would even work; I think I'm just screwed in terms of having a truly valid backup, even if I can access all the files :(

---------- Post added at 02:30 AM ---------- Previous post was at 01:56 AM ----------

Interestingly, when I tried the exact same command with the image I made with Roadkil of my brother's Nook, which has the correct byte count, it also didn't work. So then I loaded up noogie and passed through my Nook to Kubuntu, it successfully recognized all the partitions and made an image using the dd command at the end of Rog's post. Then when I tried the same command again on *that* image...got the same error *again*.

So something else is up here, I think?

when I reduce the command to this:

mount -o loop stock_1.1_dd.img /media/n2e

I get:

mount: /dev/loop0: can't read superblock​

...
[Nook Touch Android Development] ros87:
No idea, as I said, while there's shouldn't be, there are variations in size.

I haven't seen any as big as yours before tho..

Strange, I admit. What size were your new image?

That would never work, first partition is at sector 32 so you'd need an offset of 16384.

What happens if you strip the boot partition from your image and try to mount it?

sudo dd if=stock_1.1_dd.img of=p1_boot.img bs=512 skip=32 count=155616
sudo mount -o loop p1_boot.img /media/n2e
[Nook Touch Android Development] LastSilmaril:
Aha, so the issue here seems to have been that I specified the offset for the drive just before the one I wanted - even though I *said* that I multiplied it by the correct number earlier. When I used the correct offset of 295714816, I successfully mounted my system partition from ALL of my backups, including the earlier, slightly smaller ones. Weirdly when I try to mount the first partition of the image I made using dd, I get the 'can't read superblock' error though. Blegh, forget it.

EDIT: Yeah I realized right after posting that I forgot the offset there ros.

New image size from my bro's nook, both with Roadkil and dd, is 1962934272 bytes.

Old image size from my own nook, using Roadkil, is 1958739968 bytes.

---------- Post added at 03:16 AM ---------- Previous post was at 03:00 AM ----------

So I'm not the only one who got the smaller file, but that guy had reimaged from a Win32DiskImager backup. In any case, I think we've established that the image size being different hasn't messed me up.
[Nook Touch Android Development] ros87:
Hehe, ok, I didn't bother to check your offset ;)
[Nook Touch Android Development] LastSilmaril:
lol :)

looking through the thread, at least two people people have had success with both image sizes (made by both dd and roadkil) So maybe it's a hardware revision thing or something?Good thing to know, I think.

http://xdaforums.com/showpost.php?p=15953696&postcount=24OK,

aight, time to crash
[Nook Touch Android Development] ros87:
I doubt there are hardware differences (as in different chips), but there might be differences like bad blocks involved.

The NST partitions ends at sector 3792895, so as long as the image is not smaller than this it shouldn't matter.
[Nook Touch Android Development] met67:
Uhhmm...

I also used Roadkil to make a backup of a couple of refurbished Nook and they both are 1.958.739.968 bytes! I also restored using it and had no problem up to now.
[Nook Touch Android Development] ros87:
Like I said, as long as it's not smaller than 3792895 sectors (1,941,962,240 bytes), it's most likely ok.
[Nook Touch Android Development] :
Hey all,

Just got a NST. Came from NC.

Because I'm a fool/wanted root, I flashed Touch Nooter, and everything is fine.

I know it modded the ramdisk and mlo. Is it "worth it" to still backup? Can I take the mac address I have now and apply it to a general backup I can grab from these forums?

Also, what is the quickest way to enable the "flash to stock" command? NC was 8 failed boots. I know it's similar with the NST, but is there a quicker way (should I want to start "fresh" again?).

Thanks, and I hope the NST people are as awesome as the NC people are :D
[Nook Touch Android Development] LastSilmaril:
Ros87 made this image which triggers an 8-failed-boots restore

http://xdaforums.com/showpost.php?p=18124495&postcount=1

This does NOT delete your data partition; for that you need to select 'erase and deregister nook' from settings or hold L+R bottom pageturn buttons right after beginning to boot up.

There is no general backup. Ros87 was talking about making something like that a while ago, but honestly it's not necessary. Make a full disk backup with dd or Roadkil; I promise you you won't regret it. And then you might wanna install CWM while you're at it...
[Nook Touch Android Development] erreur404:
the nookie.img is not available !!

Can you repost it please ?

:)

thanks in advance
[Nook Touch Android Development] erreur404:
I was found it here:

http://cloud.addictivetips.com/wp-content/uploads/2011/06/Nook-touch-rootkit.zip