Ok, if someone happens to come along and suffer the bootloop after rooting ICS, and ICS ONLY, you can try this http://pio-masaki.com/download.php?f...otloop-fix.zip. Just open it and run it the same way as you ran the root tool, it'll do everything else. It's basically a cleanup script for after the rooting of the ICS rom fails to clean up for some reason.
fixme.bat is for windows
fixme.sh is for linux
It should be self sufficient and not need anything else. This is assuming drivers are already installed and working since the root process took place already.
It will revert the temp root put in place by the script with this:
adb shell "echo "ro.kernel.qemu=0" > /data/local.prop"
Temp root was using ro.kernel.qemu=1 which is why it has those odd bootloops and general instability.
It will then finish cleaning up, since the previous root script apparently fails for some reason, with:
adb shell "busybox rm /data/x-root -rf"
Which will delete the temp files used while rooting. Not a big deal, but I may as well include it anyways, right? It may five an error about path not found or similar, if it does that just means the root script did clear it before hand and there's nothing for this to do.
Remember, ADB debugging must be enabled, screen must be on/awake, lock screen must be unlocked (PIN, password, etc, entered and unlocked) for best results.
Hope this helps someone out before doing a factory reset.