MS opet salje letnji dashboard update u talasima, kao i uvek C4eva, TX i Jungleflasher upozoravaju da se ne prihvata u koliko se igraju narodne kopije i u koliko zelite da uradite RGH na vase mezimcu!
Reports are flooding in that Microsoft has begun rolling out SystemUpdate version 2.0.15572.0 (Summer 2012 Production Flash). There are no immediate official details from MS regarding it yet, but an announcement from Major Nelson is likely forthcoming. The update is being deployed in waves, so if you haven’t received it yet, give it some time and you’ll eventually be prompted for it. So far, users who have updated are reporting no adverse effects (on the surface) as far as firmware-flashed 360s are concerned. The team will take a closer look and analyze whether there are any important underlying changes that affect firmware or RGH. Our usual warnings apply.
Koliko vidim nista strasno sto se LT-a tice, bas citam po raznim stranim Xbox sajtovima/forumima i vidim da su dosta njih napravili zvanicni update i sve igre im normalno rade kao i do sada.
A bas pre neki dan kontam da nisu odavno nesto ceprkali sa updejtovima kad ono evo ga:)…Verujem da nije nista veliko i opasno…ali prave teren…za neki VELIKI UPDEJT koji ce doci na jesen…Ja cu se kloniti…posto planiram RGH…
Pa u teoriji, pošto prave od boxa sada media center (ove jeseni) po svemu šta se videlo na E3, njima i nije u interesu da rade nešto flešovanim konzolama jer bi izgubili subcriptions i mnogo korisnika ako bi ponovo bio talas bana… Tako da da, RGH im uopšte nije “isplativo” ni u jednom scenariju…
evo i zvanicna potvrda kako je ubijen RGH trenutno
With the new 15*** update, MS has added a new key to their hash calculation for the rc4 key. It’s basically just the first 16 bytes of the header, which include the version number, entrypoint, and size. These are all per-CB, per-version, so we cannot take a keystream from a 15*** CBB and use it to make a 14*** CB because the CBA on 14*** is unable to calculate the rc4 key no matter what we change.
[SIZE=3]What this means:[/SIZE]
In order to RGH2 an xbox with 15***, you need either:
The **cpu_key **
A previous exploitable dump from the SAME XBOX. Must fit one of the following:
Phats: 14717, 14719
Slims: 13146, 13599, 14699, 14717, 14719
Older dumps will NOT WORK with RGH2/RGH3 !
DO NOT UPDATE TO 15*** WITHOUT BACKING UP FIRST!
[SIZE=3]What do we do now:[/SIZE]
We are looking into ways of exploiting the rc4.
To make it clear, the new way of generating the CBB decryption rc4 key is as follows:
Due to hundreds of mind numbing questions from confused members, here are some clarifications regarding the new 2.0.15572.0 update
If you currently use JTAG/RGH do nothing but wait for freeboot / jrunner / xebuild to be updated to 15572. You have nothing to worry about. I’ve already tested the 15572 patched pre release and it works great.
If you don’t use RGH but intend to, make sure you are updated to a split cb version (phats 14717 / 14719, slims ANY version below 15572) and then do a full dump using NAND-X or a J-R Programmer. We also recommend you get your CPU key (using a CoolRunner & JRunner). Do this and you will always be able to glitch.
This does not affect using a DemoN at all. If you do #2 then you can always run a stock 15572 along with Xbox Live and a patched NAND on the DemoN (with correct LDV value).
Slims use RGH2 code, not RGH1. They always have. I hope the questions and confusion about this now stop.
With RGH1 you cannot use Xbox live when using a dual nand, you can with RGH2
LT+ 3.0 fw is working fine. As always revert to stock, update then reflash.
I hope this stops the countless repeated questions.
<!-- / message –>
glavna fama se digla samo za jos uvek nadolazeci DEMON (dual nanad igrackica, RGH + stock sa LIVE podrskom - u prevodu vrlo zanimljiva ali zeznuta stvar)
ko vec ima uradjen RGH miran je, da bi se odradio update na najnoviji dash kao i do sada kroz jrunner pa preko rawflash-a
ko nema RGH a planira u buducnosti ostanite na 14719 do daljnjeg da bi mogao da se izvuce full nand i cpu key kako bi kasnije kogli da odradite rgh ako planirate
demon korisnici buduci naravno su mirni ako se pridrzavaju koraka 2
SLIM konzole su oduvek bile na RGH 2.0 a ne RGH 1.0 - drugaciji metod glitch-a, tacnije CODE samog hack-a se drugacije pokrece kod slima a drugacije na phat konzolama pre 14719 dash-a, odatle pa na dalje i one su na rgh 2.0 (ko razume prvo je isao PLL hack na rgh 1.0 a rgh 2.0 koristi i2c metod ubacivanja koda, da ne zalazimo u detalje nije mesto za to)
ko hoce DEMON a ima RGH 1.0 PHAT konzolu morace da predje na rgh 2.0 (a to povlaci dodatni hardver i malo sporije bootovanje do ne bootovanja uopste zavisi kako koja konzola, rgh 2.0 za phat konzole je vrlo nestabilna stvar falconi skoro pa ne rade uopste, jasperi kako koji)
korisnici koji igraju preko diskova tj koriste LT+ 3.0 i dalje su bezbedni mogu da odrade update, prvo stock fw pa onda update pa onda flesujte opet lt+ 3.0 kao i do sada za maximalnu bezbednost, mislim da ovo zanima 99% korisnika
da sumiramo
**[SIZE=4]LT+ 3.0 JE BEZBEDAN ZA LIVE
KO HOCE RGH I NE ZANIMA GA ONLINE UOPSTE NEKA POGLEDA STAVKE POD 1 i 2 I NEKA OSTANE NA STO NIZEM DASH-u (najbolje na 14699 ili nizima za sto bolji rad)
Pa kao najbolje tako mada mozes ti odmah update da uradis samo sto se ne zna nikad sta te ceka posle. U ostalom nikad se ne zna kada i kome je banhammer za vratom