Originally Posted by sblantipodi
Imho the problem is the root itself. Phones without root does not have this problem.
Not only is that comment utterly untrue, but your opinion is not based on any testing or research.
If you had done any testing you would quickly realize your theory was unsubstantiated.
If you had read thought the official Google support thread you would have seen the problem was reported by unrooted users who were pushed the update by Google.
Root access does not affect the kernel but simply allows greater permissions - you would know this if you understood how the superuser.apk works. Granted, a root user who is running setCPU or some other non-stock kernel modifications could have issues - but this is not the case here.
I have personally re-imaged my device DOZENS of times trying to resolve the issue - using official factory (4.0.1, 4.0.2, 4.0.4) images and radios and upgrading by "official" and forced means.
Making uninformed comments are not just a waste of everyone's time but insulting to those that invest their own time and effort trying to figure out solutions for everyone's benefit.
Sent from my Galaxy Nexus using xda premium