[NST]Touch-Formatter v2 [Factory restore, reset, update to 1.1 merged]

---

I am not responsible for any damage your nook suffers.

Officially supported by The Nooter Project for Nook Simple Touch
http://code.google.com/p/nooter/

Touch-Formatter
(Tool to return to stock)

• Information:
  
  
  • What it does:
    • Formats: /data, /cache, /system
    • Installs 1.1 /system.
    • Regenerates /data automatically.
    
    
  • Bugs:
    • CWM may not refresh the screen correctly when booted, move the cursor with the right keys so it refreshes the screen.
    • If CWM hangs while rebooting, dont worry, force shutdown, and start your nook again, nothing bad happens.
    
    
  • Future updates: (In order of priority).
    • Update to 1.1.2
    • Be compatible with NSTG (Nook Simple Touch Glowlight)
    • Differentiate between the NST and NSTG (Nook Simple Touch Glowlight) so to make only one zip.
    • Backup /factory + Wipe the complete NST + Recreate the whole NST partition table + Restore /factory

• User manual:
  
  
  • Things you will need:
    1. CWM
       Thread: http://forum.xda-developers.com/show....php?t=1360994
       Direct download links:
       http://forum.xda-developers.com/atta...5&d=1323121399
       http://forum.xda-developers.com/atta...4&d=1323121315
       Download it and burn it to an sd-card, (windows users use this to burn the image https://launchpad.net/win32-image-writer/+download)
       You must have an external microSDCard reader to burn CWM, not the NST.
       
       
    2. The button layout of CWM:
       Both Buttons on the left: BACK
       Upper button on the right: UP
       Lower button on the right: DOWN
       n button: SELECT
       Power button: TOGGLE DISPLAY
       
       
    3. Zips:
       Download http://nooter.googlecode.com/files/A...matTouch-2.zip
       
       Old:
       Download http://nooter.googlecode.com/files/A...ormatTouch.zip and copy it on the sd card burnt with CWM
    
    
  • Instructions:
    1. Copy the zip onto the root directory of the sdcard you burned the CWM.(Don't extract them)
    2. Insert the sdcard on your nook, and boot it.
    3. On CWM select install zip from sdcard
    4. Then select choose zip from sdcard
    5. Select Alpha-FormatTouch-2.zip, click yes and wait till the process finishes.
    6. Go back, eject the sd card, and click reboot.

On future updates I'll try: automatically make a backup of /factroy, recreate the whole nook partition table so that people that screw hard can breathe new life into their NST easily.

• Index
  • Automatic Methods:
    • [NST]MinimalTouch 1.1beta5
    • [NST]Touch-Formatter
  • Manual Tutos:
    • Skip registration (OOBE)
    • Making the manual process LESS PAINFULL
    • Setting up adb manually on the nook touch
    • Setting up root access on NST through adb and installing busybox
    • Improve battery life(testing)
    • Backup bookmarks and annotations(testing)
    • Enable non market app installs
    • Installing XorZone's B&N button modifier
    • Change the powered off screen image
    • Blocking OTA updates
    • Installing new fonts for your nook (testing)
    • Installing Gapps (+launcher, etc)
    • Totally uninstall Gapps (my repack), unrooting, erasing and restoring
    • Interesting or useful specific apps or hacks for Nook Simple Touch
    • nook 1.1 update

• Thanks to:
  • ros87 for n2T-Recovery (http://forum.xda-developers.com/show....php?t=1289233)
  • mali100 for the correct command for the /data restoration and for CWM (http://forum.xda-developers.com/show....php?t=1360994)
  • bisbal for trying it out and giving ideas.
  • meghd00t for pointing out factory.zip is common across more than one NST and researching how to Resize Nook STR Partitions (http://forum.xda-developers.com/show....php?t=1225196)
  • dobbing for the copy of the 1.1 update.

Thanks eded333. Seems Nook touch developers are back on track. Glad to see all the busy posts. Cheer up.

Originally Posted by eded333

As some people where having trouble returning to stock after rooting, this is a semi automatic method, easy to follow, that will leave your nook stock (if you havent erased the unique data, flashing Noogie into the NST, which isnt recoverable ¬¬).

eded333,
Could you tell where unique data kept (what files)?
Hopefully, it’s small enough and easy to backup / zip
If Touch-Formatter can read the file from SD, it can restore unique data easily, right?

Originally Posted by ApokrifX

eded333,
Could you tell where unique data kept (what files)?
Hopefully, it’s small enough and easy to backup / zip
If Touch-Formatter can read the file from SD, it can restore unique data easily, right?

If i'm not wrong /rom and /factory both hold unique info for every nook, as mac, etc.
If you root your device, the only partitions which are touched are /data and /system, so dont worry for that.

Yes, it should be easy to, for example, to create a Backup.zip which did a backup of those files, partitions, or anything you want and then add to this or another zip a way to restore them from the SD.

Anyway there is allready a tuto for something like that, which creates a full backup of your Nook and it should be the first step before playing with it:
http://forum.xda-developers.com/show....php?t=1142983
Edit:
The backup done by CWM dosn't backup /rom and /factory.

So do I have to register again after using this? Or does it stay registered? (I haven't had to wipe my Nook in a while. I'm so proud of myself! xD)

Originally Posted by Googie2149

So do I have to register again after using this? Or does it stay registered? (I haven't had to wipe my Nook in a while. I'm so proud of myself! xD)

This completely erases /data /cache and /system.
So... yes , you will need to register again, after using this.

Originally Posted by eded333

If i'm not wrong /rom and /factory both hold unique info for every nook, as mac, etc.
If you root your device, the only partitions which are touched are /data and /system, so dont worry for that.

Yes, it should be easy to, for example, to create a Backup.zip which did a backup of those files, partitions, or anything you want and then add to this or another zip a way to restore them from the SD.

Anyway there is allready a tuto for something like that, which creates a full backup of your Nook and it should be the first step before playing with it:
http://forum.xda-developers.com/show....php?t=1142983
Or you can use the latest CWM: http://forum.xda-developers.com/show....php?t=1360994

That’s exactly what I want to avoid – to create full 1.8GB backup.
Isn’t it nice to have tiny backup, email to self, just in case?
There is /rom folder, but no /factory one.
/rom “zipped” is 32KB only

Searched both threads you mentioned – cannot find anything related to /factory folder.
Does /rom/devconf backup sufficient?

Originally Posted by ApokrifX

That’s exactly what I want to avoid – to create full 1.8GB backup.
Isn’t it nice to have tiny backup, email to self, just in case?
There is /rom folder, but no /factory one.
/rom “zipped” is 32KB only

Searched both threads you mentioned – cannot find anything related to /factory folder.
Does /rom/devconf backup sufficient?

While your idea with just backing up the unique data (which resides in both the rom partition and the factory one) might seem a good one, what happens when you screw up your NST the way that 99% of the users that asks me for help does?

If you delete/corrupt/overwrite boot, rom, factory or data, then your tiny rom backup won't help you much unless you can get a copy of the other partitions from someone else.

And then there's the problem with alignment of the data partition, which is part of an extended partition.. The first thing people usually kills is the partition table , and simply restoring it from another NST will (in 70% of the cases) not bring back the extended partitions

My vote would be a little yes and mostly no

Originally Posted by ros87

While your idea with just backing up the unique data (which resides in both the rom partition and the factory one) might seem a good one, what happens when you screw up your NST the way that 99% of the users that asks me for help does?

If you delete/corrupt/overwrite boot, rom, factory or data, then your tiny rom backup won't help you much unless you can get a copy of the other partitions from someone else.

And then there's the problem with alignment of the data partition, which is part of an extended partition.. The first thing people usually kills is the partition table , and simply restoring it from another NST will (in 70% of the cases) not bring back the extended partitions

My vote would be a little yes and mostly no

I think a backup of ROM itself should be a yes. Because if you have that and somehow completely absolutely destroy your partition, you will be able to with a little work and kindness from others eventually completely restore your device, in fact you could create a generic copy of the partitions blank or otherwise then use that to restore a device, have a script take the rom insert it write /boot /system etc for you and you're good to go.

However this shouldn't be used in place of a proper backup.

Originally Posted by ros87

While your idea with just backing up the unique data (which resides in both the rom partition and the factory one) might seem a good one, what happens when you screw up your NST the way that 99% of the users that asks me for help does?

If you delete/corrupt/overwrite boot, rom, factory or data, then your tiny rom backup won't help you much unless you can get a copy of the other partitions from someone else.

That’s where you Touch-Formatter helps me.
It’ll restore generic copy, my tiny backup makes it “personal” than.
That’s how B&N does it on factory, right?

---------- Post added at 03:43 AM ---------- Previous post was at 03:39 AM ----------

BTW: Where is factory partition?

#df
/dev: 116512K total, 0K used, 116512K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 217K used, 15899K available (block size 512)
/system: 285583K total, 196911K used, 88672K available (block size 1024)
/data: 808292K total, 313252K used, 495040K available (block size 4096)
/cache: 237987K total, 8344K used, 229643K available (block size 1024)
/sdcard: 7774208K total, 113824K used, 7660384K available (block size 32768)
/media: 241947K total, 759K used, 241187K available (block size 512)

---------- Post added at 03:51 AM ---------- Previous post was at 03:43 AM ----------

Originally Posted by GabrialDestruir

...in fact you could create a generic copy of the partitions blank or otherwise then use that to restore a device, have a script take the rom insert it write /boot /system etc for you and you're good to go.

Gabrial,
Do you think it’ll be possible to connect via adb and push back /rom partition content to restored generic image.
Providing we replaced uRamdisk and can use adb connect via USB.
Would it be sufficient?