Seems there is more trouble in store for those who forced the NoDo update with Chris Walsh's work around with the May security update, but there's a 'simple fix' that's going to be provided by Chris himself. Some users are reporting success while others are being hit by errors (80180048 included) and there's currently no information available as to what the problem is and how the 'simple fix' is implemented without re-flashing.

If you're having issues updating on a "Walshed" handset, be sure to comment on his blog post to let him know, comment below to inform us and stay tuned for the solution. Does this remind anyone of the whole discussion surrounding NoDo and the Chevron Updater?

Source: Chris Walsh