Well that gave me a few nasty moments!
I'd decided to stay on temp recovery until the update arrived. So it arrives today, I take a nandroid, then by mistake install it before copying the update file (as I'd intended to - just pressed the button in a thoughtless moment). Installs fine, all seems to work but of course I'm not rooted. OK, will fastboot boot recovery.img, take a backup of the unrooted 4.2.2 ROM, then root....
Except all that fastboot boot recovery.img does is lock up my bootloader so that I have to hard shut down. Try newest TWRP, same result. Try CWM touch, same result. Notice that the hboot version has updated, but I'm still unlocked and S-Off, so should be OK. But it is definitely not working.
Bite the bullet, fastboot flash TWRP 2.6 permanently, and yes, it works! Back to rooted and will not be doing any more OTAs
I'm writing this in case anyone else was using a temp recovery and finds that it stops working after the update, just to let you know that a proper install did work.
Also, if anyone is thinking of getting the OTA 4.2.2 update but is interested in S-Off, do not
return to locked & S-On before running the update. To quote these prescient words:
Originally Posted by scotty85
... consider going s off before the exploits are patched,and just enjoy rom flashing and using your phone for now
The 4.2.2 update comes with a new bootloader (1.54 in my case), and revone cannot handle it (yet?). So if you are S-On and accept this update then you won't be able to S-Off using revone, at least for a while. I've not checked the other S-Off method. If you are S-Off when the update is applied, you will still be S-Off afterwards. So right now, if you think you might be interested in S-Off, do it before updating to 4.2.2.