Xbox LIVE Dashboard Update 2.0.16202.0 Rolling Out

Microsoft has begun rolling out a new SystemUpdate that brings the Xbox 360 dashboard/kernel version to 2.0.16202.0.

Backups continue to work fine on LT+ v3.0, LTU v1.0, and xk3y offline and on LIVE. [Admin note: LT v2.01 and LT+ v2.0/v2.0b are fine as well!]

Xbox LIVE's Major Nelson (Larry Hryb) posted this about the update:

"In this update, we are correcting some issues such as displaying the incorrect playlist name when launching a playlist from Xbox SmartGlass to the console, an error with Xbox Video closed-captioning and an error with Xbox Music that some were experiencing."

This entry was posted in Xbox 360. Bookmark the permalink.

» Comments RSS Feed

3 Pinned Responses to Xbox LIVE Dashboard Update 2.0.16202.0 Rolling Out

242 Responses to Xbox LIVE Dashboard Update 2.0.16202.0 Rolling Out (Including 54 Discussion Threads)

  1. Pingback: Xbox LIVE Dashboard Update 2.0.16202.0 Rolling out

  2. avatar Ash says:

    is it safe to play online:)

    Reply | Reply with Quote
  3. avatar Camilo says:

    hey anyone know if the new update it's good or bad?

    Reply | Reply with Quote
  4. avatar CombatTOAD says:

    Hit US same time as UK so am assuming this one isn't a staggered rollout like they normally do.
    I received the update (North East England) within 10 seconds of my buddy (Texas USA).

    System's seem to be updating fine, done seven systems so far in various ways and the only issue i noted in one Xbox 360 phat console so far was that it was unable to update (Error E66) because the system had a replacement Benq drive programmed with the systems correct drive key instead of the original factory-fitted Lite-on, so conclusion would be it is checking the OSIG of the drives during update and gave the E66 error as the OSIG was not what the system expected. Spoofed the Benq drive with a Liteon OSIG and it installed fine.
    So far, no other update issues observed…

    Reply | Reply with Quote
    • avatar triplepurple says:

      curious….Haven't they been checking for this a long while now?

      Reply | Reply with Quote
      • avatar CombatTOAD says:

        triplepurple:
        curious….Haven't they been checking for this a long while now?

        To be honest, i've never needed to look into this further on past updates. As a rule i return the drives to stock before an update anyway, but some of the consoles i have done for people they have chosen not to do that and update regardless, but this one came back to me – E66 error on this update. The guy ran it through other updates without needing me to return it to stock for the process but this time he couldn't get away with it, so it seems it's checking OSIG during the update process.

        Reply | Reply with Quote
  5. avatar Albert says:

    Waiting for c4eva log :)

    Reply | Reply with Quote
  6. avatar Simon says:

    What about the hitachi 78 2.0? can I update to the new dashboard and still play backups?

    Reply | Reply with Quote
  7. avatar BleSSeD says:

    "error with Xbox Music that some were experiencing."
    This means that way which allow to launch games that were writed on 97%, will not work anymore?

    Reply | Reply with Quote
    • avatar CombatTOAD says:

      yeah that raised my suspicions too lol… it's just a polite and discreet way of saying "yes, we've finally stumped those who were getting truncated backups to load again using the music player vunerability".
      I don't use truncated backups so am unable to test that theory but i can easily see them doing such a thing: Note how they couldn't trust the AP2.5 fail flags to ban consoles anymore because of previous false-positives so in update 15574 any systems with an X value that contained a failed AP2.5 flag was issued a new X value and the sec data then shows as clean – well that could only have been done so from then on any further AP2.5 fail flags can now be trusted and acted upon, given them room to console ban systems again for such reasons. I had several systems that only had one or two flags on and were still working on Live that 15574 gave new clean X values too: i'm going to flag one up again to prove a point because i expect after getting new flags it will shortly get banned whereas the other of the two systems will remain ok. Time will tell. They have to try and do something to stop backup and piracy use and if detecting truncated discs is an easy way for them to do such then we have to expect them to start to act on it…

      Anyway, people should know by now that truncating isn't Live-safe. It's a shame there are still outdated guides floating about claiming that's "how to burn XGD3 games correctly" hence why many people still truncate discs in ignorance, simply because thats how the guide said to do them! lol.

      Anyway, as usual it's still all hear-say, theories, and nothing confirmed, but makes for good discussion all the same.

      Reply | Reply with Quote
    • My m8 always updates his console without going back to stock fw, he's been doing this since the Xbox flashed a new fw onto during a update. (can't remember dash no#l) also he's such a cheap skate that he truncates all his games, he's playing assasins creed 3 truncated and blak ops 2 truncated and hitman truncated, all work fine online, plus he's NEVER had to do the music player trick to get 97% to load, as load ok. (obviously this is not the safest way ihas-burner all the way for the pro modder)
      I'm not saying update anyway without returning to stock, but one of these days these people might get caught out (when a new fw incorporated into a update is released) again totally down to the individual – best advice wait for a m8 to do his Xbox before you bust your own one! Or wait for C4evas live log (not much of a wait)

      Reply | Reply with Quote
  8. avatar wnapoli says:

    problems for those who lt 2??

    Reply | Reply with Quote
  9. avatar Slimer says:

    You should always, always, always flash to stock before an update, at least thats what uber told me. Ignore this and most likely you are closer to a ban. Take the effort, wait for the live log and if c4eva says so, you are ready to go!

    Reply | Reply with Quote
    • avatar Anonymous says:

      I always flash to stock but I still have this one question.
      Let's assume that the current dashboard update isn't safe. What the ? There's will be a new firmware?
      In my opinion, besides flashing back to stock, there is nothing more we can do.

      Reply | Reply with Quote
    • avatar randle says:

      Slimer:
      You should always, always, always flash to stock before an update, at least thats what uber told me. Ignore this and most likely you are closer to a ban. Take the effort, wait for the live log and if c4eva says so, you are ready to go!

      I never flash bk to stock on slim or brothers phat for years and never had a ban or anything, but dont update through live, i download update to memory stick and update

      Reply | Reply with Quote
Comments Page 2 of 13« Previous12345Next »...Last »
View all comments

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <img src="" alt="" width="" class="" style=""> <span style="">

DO NOT post comments asking questions like "When will X be released?", or "When will c4eva do X?". All current status information and ETAs, when applicable, are noted in the Status Table on the front page. If it's not listed there, it's not known, so don't ask. All questions of this type will be deleted by the Admins.