[Nook Touch General] nmyshkin:
I've been waiting around for more than a week for my second "new" NST to update. It finally did so yesterday. The update has been mentioned on the Mobileread forums and one XDA member has already asked about rooting it so I thought I'd see what I could learn. You apparently won't learn anything from B&N as they either respond as if this is something that should not happen (so beware!) or they say it provides minor enhancements. There is no notice of the update on their cobweb-ridden website for the NST, no opportunity to do a manual update. It takes about a week of WiFi on all the time to catch the rolling push.

Edit: B&N has since posted the update zip on their website. For users with non-US firmwares, I recommend flashing US 1.2.1 firmware (see https://sites.google.com/site/xcdguides/nook/nookB&N). You cannot register 1.2.1 but you can update it before registering. At the "welcome" screen connect the device to your PC and transfer the update zip from B&N. Let the device sleep and it will do the update. Then you can register if you desire.

Edit: The time for OTA updates is past and I'm not sure if devices still running 1.2.1 will act up in any way. Certainly you won't be able to contact B&N servers and this could lead to connection error messages when WiFi is turned on.

What's new?

I can't claim to have done a thorough shakedown but there is no obvious change in the device on FW 1.2.2. I suspect this is a security update to keep the devices in line with new security measures on B&N servers so that owners can still spend money at B&N via the devices :) But I was curious to see if the cacerts.bks file had been changed since some certificates have already failed (a few of which have been fixed already by @tshoulihane to keep the Kindle app working). No joy there--not that I was surprised. B&N doesn't need cacerts to ensure correct negotiation with their servers via their own apps. Everything seems exactly the same.

To update or not to update

If, like me, you rooted your device earlier with NookManager, the update will fail and your device will spontaneously reboot. This behavior (occurring every Sunday morning as I listened to NPR on the TuneIn app) is what lead me to the conclusion that it was the update process. If you don't give a hoot about the update but you're not keen on having your device reboot on a whim, here is a fix: https://xdaforums.com/showpost.php?p=34433959&postcount=3

Edit: well, that seemed to work at first, but then the weekly reboots began until I finally updated.

I don't know about other rooting methods potentially interfering with the update process.

If you just

must

have the update, it is likely you will need to restore your device to stock, re-register it, and leave WiFi on for a week or so until the update occurs (I left mine on the Library screen so I would know when a reboot--taking you to Home--occurred).

Edit: at this point, you will have to manually download the 1.2.2 update zip from B&N and manually install it on your device. This will require you to invoke a factory re-image as the update will not work on a rooted device. A NookManager card (even an old one) can be used to start the factory reset. Once that's done and you're at the "Welcome" screen, connect your device to your PC and drag the 1.2.2 update zip to the "Nook" drive. Let the device sleep. Come back in awhile and see if the update zip is still visible on the "Nook" drive. If it's gone, the update has been done. Now for rooting.....

Can I root it?

The short answer is "yes".

NookManager is versatile and wonderful, but it does have a bit of dust on it by now. I plan to look into that and start another thread. For now, there are two files which need to be edited in order to use it successfully with FW 1.2.2. You'll want Notepad++ or similar.

Prepare the NookManager card as described in its thread. Examine the prepared card in your PC. You'll see one partition:

NookManager

In that partition find the folder "scripts". You need to edit these two files:

install_nookmods

install_old_installer

In both files the change is the same. Near the top of the file you will find this line:

if [ "$SYSTEM" != "1.2.0" -a "$SYSTEM" != "1.2.1" ]; then

You want to change it to look like this:

if [ "$SYSTEM" != "1.2.0" -a "$SYSTEM" != "1.2.1" -a "$SYSTEM" != "1.2.2"]; then

Not sure how touchy spaces, etc., are, but try to follow what's already there. Save the files and you're good to go.

Now....there is an issue with a few apps like Opera Mobile and Tasker not wanting to install. They are the only two I have encountered so far. Here is the "fix": https://xdaforums.com/showpost.php?p=76873102&postcount=5