QUOTE(majinsoftware @ Nov 6 2009, 10:17 PM)

Yeah but even doing the connection test and if it comes up your banned it will trigger the disable hdd flag.
So you still end up losing all the same things as if you connected when signed in to a profile.
So by cancelling the request to install the update (as described in the steps) you aren't negating the flag that nukes your HDD functionality? I figured that process, and thus the point of the tutorial, was to avoid all that.
As for me, I initiated a repair on my console 2 days ago which worked fine and was not banned at the time (went to pull down and price etc) but when trying yesterday I get the "Service unavailable - id=54420" message. I try the same thing on a virgin arcade also under my login and voila goes right through to pull-down and price.
Here's what I'm speculating (
PURE speculation):
The system they use for registering, initiating repairs, changing your console is all an 'app'. Webserver talks to --> app server --> makes call to DB issuing a select statement of some kind that returns an unknown value because your console_status flag has been flipped to whatever they use to designate a ban. The 'app' has no idea how to interpret this value. If the active status is something it recognizes it knows how to proceed but in the case of a banned console it simply defers to "service unavailable". This is one of those "overlooked" items as the team that supports the xbox.com application infrastructure could be completely different than the ban hammer folks. It would have made sense for them to patch this (IMG:
style_emoticons/default/smile.gif)
It saved my HD and much aggravation, so for that I'm thankful.