New System Update 2.0.15572.0

[sarah1331]

That would really suck if it some how blocked rgh as i just paid alot of money fot someone to rgh my slim an im just waiting for it to come in now
I couldnt imagine how crappy that would be lol

Your going to update using jrunner so what's your problem your rgh'd no one can stop you now

 

[krazydude4g]

I dont really understand what your saying but ok thanks

 

[tr4ckerz]

If this update is just for maintainance, will it be crucial to reflash a slim lite-on 0272 drive?.
I remember reading that on this drives in particular was safe to update dash w/o reflashing

It has been said hundreds of times that reverting to stock before any major update is highly recommended (no need to go so far - just look at the Uber's signature).

Besides thart, I see no reason to hunt for the update in a minute when it is released, it always worth to wait for closer info from the Team.

 

[smalltylynch]

RGH cant be patched because it glitches to early in the boot sequence they might have half patched it like they did with the trinity but i think xecuter will get around it.

Technical Info:

In the slim boot chain the 2nd bootloader (CB) is split into two pieces. The first part simply starts encryption and loads the second part, which does fuse checks and all the things that the old single CB did. By glitching the first part (CBA), we take control of the system before the fuse checks occur and can patch them out. The slim bootchain has always used this layout and some groups have even tried bringing the slim CBA to phat and using the old single phat (RGH1) CB as CBB. Glitching this way will work if you set it up right, but there are actually phat xboxes that already have their own split CB boot chain which were mostly ones that had been refurbished (CB 5772, 6752, 4577).

What we have done is simultaneously find glitch timings for these refurbs, dump their cpu_key, decrypt the boot chain, and port it to run on every other phat! This means that on phats we can now glitch before the fuse check and thus have an unpatchable hack just like trinity!

 

[axelll]

So, in theory, for this new dash, $$ystemupdate should work on an RGH'ed console, right?

 

[sarah1331]

So, in theory, for this new dash, $$ystemupdate should work on an RGH'ed console, right?

No you have to update your NAND first with a up to date image

 

[Haygar]

So, in theory, for this new dash, $$ystemupdate should work on an RGH'ed console, right?

Keh?? Not directly!

 

[Loukno]

It has been said hundreds of times that reverting to stock before any major update is highly recommended (no need to go so far - just look at the Uber's signature).

Besides thart, I see no reason to hunt for the update in a minute when it is released, it always worth to wait for closer info from the Team.

[2011-10-12 12:51PM UTC] #c4e <c4eva> a locked slim is safe during update, no need to flash to stock.

Phats still need to be reverted back to stock before updating.

I found the post i was mentioning. This is why i ask this question.
As for your second comment, im still waiting to update, i never said otherwise

 

[axelll]

Yes, stupid question, I was thinking at smth else, of course I have to update the nandflash first with J-Runner.

 

[Justice1231]

Originally Posted by JAWS
[2011-10-12 12:51PM UTC] #c4e <c4eva> a locked slim is safe during update, no need to flash to stock.

Phats still need to be reverted back to stock before updating

I found the post i was mentioning. This is why i ask this question.
As for your second comment, im still waiting to update, i never said otherwise

Have you seen the date for when that was released. That info was for the update at that time. This is a new update, whilst it might be safe to update slims, it still might not be safe as nothing has been confirmed.

 

[Dark_Riku]

Still no update on my end. Scotland, UK

 

[Loukno]

Well, he never said it was only for that update. But you are right, it is much safe to roll back. Anyways i guess i will try updating w/o reflashing when c4e team says its safe to update since im too lazy to do all the reflashing process

 

[nosherfj]

think cus the spi is locked on slim drives these will never be reflashed by MS again (obviously the 9504 was reflashed after dash 13146 and locked after 13599) so that's why c4e sai it's ok to system update on these on custom fw. With phat's i think cus they could possibly be reflashed again easily it's best to revert to stock on these. i know of plenty of people tho that stay on LT3.0 and update there phats no problem once they got word from TX/c4e that it's safe to do so.

imo this update is only about updating the dae.bin for this summers releases.

personally myself i updated my slim on LT3.0 no probs but will hold back playing xgd3 untill i get word all is safe.

 

[Martin C]

The reason we advise flashing back to stock is not for the drive being flashed by MS, it's because there's always a chance they are reading the drive during the update and checking for CFW.

 

[sp4rkst4rt3r]

As MartinC has said above.....M$ could/can/do read the FW on the drive as the system is being updated, this is why on occasion some consoles that did not have the correct FW went into an update loop.

Fair enough this all happened at the time when M$ were flashing all the drives but surely it is better to be safe than sorry. 10 minutes work to flash to OFW, update then flash back to LT+ v3.0 (assuming new CFW isn't needed) or a dead/banned console worth £xxx.xx....

If I was a gambling man I know where the Clever money would be....lols

 

[Martin C]

In addition to the above, if any of you are worried about the new dashboard update before C4Eva confirms, just flash back to stock and use originals until such a time

 

[sarah1331]

Be nice of ms to unlock the drives and update them and relock

To only know the unlock secrete mmmmmm

 

[mrdrifta]

come to think of it, i was prompted for an update on my 14719 box last night trying to play black ops, took a [email protected]#Kn age to d/l so i cancelled it lol. Was in the process of switching drives so maybe my drive was just missing 14719 files? doesnt explain the sh*t speed for my 1MB line...

Anyone else in New Zealand get hit for an update yet?

 

[BGAMods]

No update here yet, well none for me anyway


Sent from my iPhone using Tapatalk

 

[Oggy]

As MartinC has said above.....M$ could/can/do read the FW on the drive as the system is being updated, this is why on occasion some consoles that did not have the correct FW went into an update loop.

It doesn't have to be in an updated state to read from the dvdrom.