Xbox 360 Dash Update 2.0.14719.0 Rolling Out

Hot on the heels of the Valentine's Day update just a little over a week ago, Microsoft is now rolling out yet another SystemUpdate, this time bringing the dash/kernel version to 2.0.14719.0. No indication yet as to what changes it brings, but as usual if you're using c4eva's fw, it's recommended that you wait to update until he's had a chance to generate and analyze a set of LIVE Logs with the new dash.

This entry was posted in Xbox 360 and tagged , , , , , , , , , . Bookmark the permalink.

» Comments RSS Feed

3 Pinned Responses to Xbox 360 Dash Update 2.0.14719.0 Rolling Out

533 Responses to Xbox 360 Dash Update 2.0.14719.0 Rolling Out (Including 112 Discussion Threads)

  1. avatar Pedagogo says:

    I have a question, dunno if someone can answer me.

    If I have a game burned with the topology data and everything else correct (After running it on ABGX), and then I try to run it in an LT2.0+ console… I know the game won't run, but will this mark my console with an AP25 fail ?

    Reply | Reply with Quote
  2. avatar Thanks for the info (or lack of it) says:

    For all those saying the new 14719 update doesn't do anything… guess what:
    I had an Xbox 360 fat with Lite-on DG-16D2S 74850c which was on a very out of date dash, so i expected it to flash the drive to the 0250c firmware like all fat Lite-on's do BUT… firmware is now 0251, yes, 0251 not 0250.
    So thanks everyone who said no changes other than a dash bug fix from the previous update. Even admin's have said it's fine, well i consider that a fairly important issue to raise.
    Obviously it's not flashing 0250's to 0251's but any Lite-ons on the original firmwares before 14699 dash update where it upraded 7's, 8's, 8v2's, and 9's, all to 0250c are no longer flashed to 0250, but 0251 instead.

    ***14719 dash updates any original firmware Lite-on DG-16D2S to 0251. Fact.***

    Reply | Reply with Quote
    • avatar admin says:

      Please refer to the Status table on the front page. You'll see that it's clearly marked as "Lite-On 02510C". There never was an "0250C" as you so claim. If you click to expand the "Show old versions" link, you'll find in the details for LT+ v1.9 that SystemUpdate 2.0.13146.0 flashes all phat Lite-Ons to 02510C. All SystemUpdates from 13146 and onward will flash a phat Lite-On to 02510C if at the time of updating, your system was on a dash/kernel version older than 13146 (and thus the drive still on original 7/8/9 fw). That's been common knowledge since the 13146 update.

      Reply | Reply with Quote
      • avatar Thanks for the info (or lack of it) says:

        admin:
        Please refer to the Status table on the front page. You'll see that it's clearly marked as"Lite-On 02510C". There never was an "0250C" as you so claim. If you click to expand the "Show old versions" link, you'll find in the details for LT+ v1.9 that SystemUpdate 2.0.13146.0 flashes all phat Lite-Ons to 02510C. All SystemUpdates from 13146 and onward will flash a phat Lite-On to 02510C if at the time of updating, your system was on a dash/kernel version older than 13146 (and thus the drive still on original 7/8/9 fw). That's been common knowledge since the 13146 update.

        Your nit-picking at my typing and not at my point…
        Used jungleflasher to read firmware on Xbox fat Lite-on DG-16D2S 74850c that was updated from 14717 to 719. Comes up as FW:0250
        Used Jungleflasher to read firmware on Xbox fat Lite-onDG-16D2S 74850c that was updated from a very very old dash straight to 14719 and comes up FW:0251
        So this update seems to have updated the same model drive as my other with a different revision to previous, agree? Your comment on that please. That's my point…

        Reply | Reply with Quote
        • avatar admin says:

          Thanks for the info (or lack of it): Your nit-picking at my typing and not at my point…
          Used jungleflasher to read firmware on Xbox fat Lite-on DG-16D2S 74850c that was updated from 14717 to 719. Comes up as FW:0250
          Used Jungleflasher to read firmware on Xbox fat Lite-onDG-16D2S 74850c that was updated from a very very old dash straight to 14719 and comes up FW:0251
          So this update seems to have updated the same model drive as my other with a different revision to previous, agree? Your comment on that please. That's my point…

          Nit-picking? How so? I don't think anyone missed your point. You're claiming the existence of a firmware version that doesn't actually exist, and the response is still the same — there is no 0250 fw. Perhaps you're mistaken in what you believe you saw. The only other explanation I can see is the remote chance of it being an unreported bug in JF. That's very unlikely though since 02510C has been around for almost a year, JF has gone through several versions between then and now, and nobody else has reported anything of the sort.

          Reply | Reply with Quote
    • avatar kmoz says:

      dude its ok to be a noob. i believe that many of us were at some point. but coming to this channel to complain to the ADMIN because you did not take the time to read 4 letters. its more than a noobs action. so next time. do your homework and READ a little.

      Reply | Reply with Quote
      • avatar Ucla says:

        HA totally agree. For whatever reason this site at times seems to be flooded with bs complaints from people that can't even read let alone have any business doing a flash themselves.

        Reply | Reply with Quote
    • avatar Stridz0r says:

      Also, when it says "doesn't do anything" or "no changes", it actually means that there's no change from the inmediate previous version, not with some kernel from a year ago – of course there's gonna be changes. You don't have to be a rocket scientist to figure that one out…

      Reply | Reply with Quote
  3. avatar CupZ86 says:

    I flash to stock, updated, and re-flashed 3.0 (phat liteon) and to the new dash and all the games work except Skyrim which stays at black screen when loading fyi…..

    Reply | Reply with Quote
  4. avatar John C. says:

    I have updated many previously modded consoles to LT+ 3.0.

    First updating the dash to currently safe listed dash, then flashing the drive after using a stock firmware of 13599 then spoofing their key to it, extra precaution I take, just in case their drive is spoofed as another drive or something was wrong with the previous flash. Of course, I make sure to get the key beforehand.

    With the above said, I have never had any issues with 3.0 even when playing online, all I can say is well done c4eva, as usual you beat a $ million company once again, game on.

    Reply | Reply with Quote
  5. avatar Whimp says:

    so folks ,

    my xbox 360 is maunfactured ( date 25.7.2008 ) , latest dash update 2.0.14719.0 !!!

    Xbox 360 Arcade date 2008 :

    - Drive ( LiteOn ) with Flash LT+ 3.0
    - all wave 1-14 games still playable
    - all xgd2 games still playable
    - all xgd 3 games still playable

    NO PROBLEMS wit all games … i can play all …

    i burn my games with imageburn 2.5.6.0 with " TRUNCANE " … and after burnprocess , it works…

    i dont need an ihas 124-b burner with – BurnerMax Firmware – , ist works without ihas burner
    after updating my box …

    for all people who had the same old xbox 360 from 2008 , dont be afraid with the dash update 2.0.14719.0 ..

    do it now and it will play all games like before updating smoothly and without crashes or error-messages .

    Whimp

    Reply | Reply with Quote
  6. avatar 504BOSS says:

    My Box just got RROD today after updating yesterday to dash 2.0.14719.0 via usb after returning to stock then reflashed. (LT + v2.0 phat Hitachi 47) with 12v fan mod so heat is not an issue. And no i don't believe it's a coincidence. I've been reading post about others saying their boxes RROD and their claims were down played by others not to be because of the update. Well mine did! I would appreciate if someone could investigate this. Others with this problem please reply.

    Reply | Reply with Quote
    • avatar QuickMythril says:

      it seems very highly unlikely that you could get rrod just from a dashboard update… what's the secondary error code?

      Reply | Reply with Quote
      • avatar 504BOSS says:

        The error code was E74. I reflowed the board and repasted the GPU and CPU. All is good now. But i just found it to be alarming because i was aware of the claims of a few rrod after updating and mine did just after. weird. Thanx for the response.

        Reply | Reply with Quote
  7. avatar Matija says:

    I have a question when will get the newest chip for New Slim Console

    Reply | Reply with Quote
Comments Page 28 of 28« First...« Previous2425262728
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.