Why does this happen? Installer has "setuid" permissions, which means it executes as root. It is the only application on SpringBoard that executes as root. On a freshly restored iPod/iPhone, none of the databases for things like keyboard autocomplete have been created. If Installer is the first thing that you run on your iPod touch, it will create databases owned by root. However, because they are owned by root, and every other application (including the application that manages keyboard autocomplete!) runs as "mobile", none of the other applications will be able to read those databases. What happens is that they discover that they can't read those databases, try to change the permissions on those databases, fail, try again, over and over in an endless loop. That's why the iPod freezes. If you read this, you should be able to deduce the answers to the rest of the FAQ, including how to fix the issue. But here it is anyway: In 1.1.3, why did it happen for Dev Team's release but not natetrue's? Because natetrue's release runs everything as mobile. All applications will naturally be able to read and write everything, so the crash condition is no longer there. However, running everything as root is unwise in the long run for obvious reasons. I used ZiPhone/iLiberty/something else in the past. It did not freeze the keyboard. Why does PwnageTool have this problem? That's because you were actively using your device before you used the jailbreak apps, meaning the correct files were already created with the correct permissions. Those files do not exist on a freshly restored device (like PwnageTool generates), which is why Installer creates them with the incorrect permissions. I used ZiPhone/iLiberty/something else in the past. It did not freeze the keyboard. After using PwnageTool, I restored and used ZiPhone, etc. again. Why doesn't the problem go away? Because this time, you ARE using those apps on a freshly restored device. =P It's not that they don't "have" the same "problem", it's that the problem was not visible to you until the correct situation arose. What can I do to fix this? DO NOT RUN INSTALLER THE FIRST THING AFTER YOU RESTORE. First, go type some stuff in contacts, play a song. That will initialize all the databases properly. After that, you can use Installer, which will then use the already created databases (readable by both mobile and root) instead of creating them, and everyone will be happy. If your device has already started freezing, you will have to restore unless you want to use the advanced method. Typing stuff in contacts won't fix the problem if it's already started (for reasons that should be obvious to you if you read the rest of the FAQ). How can I fix this problem without restoring? In OpenSSH, if you can install it, type this: chown -R mobile:wheel /private/var/mobile/Library/AddressBook Can't these jailbreak apps automatically include the fix for you? Well, no, because we can't be sure the AddressBook is the only thing that has the issue (at least, yet). I've had experiences where no music would play as well. Best bet is to mess with you device for awhile before running Installer.