Dashboard Update

[BornToDie423]

I'm not sure if this is news or if it has been covered already, but my stock console received a dashboard update.

At first I wasn't sure, because there was only one number change. My dash went from 2.0.16537 to 2.0.16547. I'm not sure what they have changed yet, as I can't find any info on it. But there ya go.

I'm not sure if I should have posted this or not. If not, I won't get offended if it is deleted.

 

[[AD]]

Can confirm mine has just done the same.... No idea whats changed or if its safe so be aware guys.

:Edit: Back ups still work. So no firmware change.

 

[gnommak]

I can confirm. 15 minutes ago I receive dashboard update to 16547
http://f.cl.ly/items/2k2j082X380z3Z2D2i0h/IMG_3948+.jpg

 

[iiRickk]

Quick Question: I don't know anything about this but if the update changes one minor number in the dash it normally isn't any firmware change right?

Also if anyone updated please leave a message here so I and other people can see if anything changed and what is new!

Thanks!

 

[rick48235]

time to got back to stock

 

[stmem]

just updated there now too, not updating my slim incase they do something to stop rgh before i do it lol

 

[RED IMPACT]

I heard it is something to do with policy child protection (for Live) and not a hardware change (for what it is worth)

 

[iiRickk]

I heard it is something to do with policy child protection (for Live) and not a hardware change (for what it is worth)

yeh I read something like that too. Probably safe it is a minor update with only one number changed

 

[nofeloniesyet]

just updated there now too, not updating my slim incase they do something to stop rgh before i do it lol

with the leaked bootloaders we have now thiers really nothing ms can do to stop it tbh.

 

[gavin_darkglide]

with the leaked bootloaders we have now thiers really nothing ms can do to stop it tbh.

Does this cover R-Jtag also, Just asking because i know that you have to update to 15574, so i would assume that they could patch out the R-Jtag hack.

I guess i will try it and get back to everyone with my experience.

 

[RyanAC]

16547 is safe to download on retails with flashed drives. Worked perfectly fine for me anyway.

What are you using to update R-JTAG console Gavin?

Xbox UK site Update File if any use to anyone:
http://www.xbox.com/system-update-usb

Or download on J-Runner which is easier.

 

[daretogo]

Does this cover R-Jtag also, Just asking because i know that you have to update to 15574, so i would assume that they could patch out the R-Jtag hack.

I guess i will try it and get back to everyone with my experience.

Yes, it covers R-JTAG too. The reason 15574 is required is because R-JTAG was designed to work on split CB consoles so you have to update at least to 15574 to be sure you are on a split CB.

 

[playingmax]

does it changes the ldv?

 

[gavin_darkglide]

I have r-jtag with a demon, I use the stock side for netflix, and hulu plus only, which requires xbox live/update. And i use the r-jtag side for gaming. By the way I can confirm that r-jtag still works after update, as i just finished the update and tested it. Havnt flashed drive yet because, A. It isnt really needed with RGH/R-JTAG, and B. I was waiting on my new Probe V3 to get here, as i lost my old one before i got this box.

every update changes ldv, but jtag/rgh images dont really care about ldv, so if you are asking for that it doesnt matter, ldv only matters when creating a stock nand.

 

[gavin_darkglide]

Yes, it covers R-JTAG too. The reason 15574 is required is because R-JTAG was designed to work on split CB consoles so you have to update at least to 15574 to be sure you are on a split CB.

Split CB came in with 14719 update, not 15574.

 

[iiRickk]

So I just read two tweets by XboxSupport to someone on twitter and he said it has something to do with creating a child account and it is to improve the Xbox Live experience. Randomly found that tweet when I was looking for more info

 

[iiRickk]

If you check out the XboxSupport3 twitter and looks back at his tweets you will find him answering to someone the question. Forgot his twitter name so...

 

[RyanAC]

G2G then, thanks for confirming Gavin.

 

[BL4K3Y]

Yes, it covers R-JTAG too. The reason 15574 is required is because R-JTAG was designed to work on split CB consoles so you have to update at least to 15574 to be sure you are on a split CB.

This isn't the case at all because M$ rolled out split CBs on phat consoles with dashboard version 14717.

The R-JTAG exploit requires dashboard version 15574 or higher.

does it changes the ldv?

Every official system update will blow an eFUSE and the LDV will go up by one, but this has no relevance really because the LDV fuse check is patched out in glitch/R-JTAG images.

You only need to know the correct LDV when building a stock NAND image like gavin_darkglide said.

Split CB came in with 14719 update, not 15574.

Read above - dashboard version 14717 introduced split CBs on phat consoles (there is an exception for refurbished consoles on 13599 I think).

 

[gavin_darkglide]

This isn't the case at all because M$ rolled out split CBs on phat consoles with dashboard version 14717.

The R-JTAG exploit requires dashboard version 15574 or higher.



Every official system update will blow a eFUSE and the LDV will go up by one, but this has no relevance really because the LDV fuse check is patched out in glitch/R-JTAG images.



Read above - dashboard version 14717 introduced split CBs on phat consoles.

I meant 14717 not 14719. My neice has been hitting buttons on my computer all morning, so i have been kinda distracted while i type.