How M$ Killed The XOR Hack

[lio_x]

its good that TX brings the news ASAP

 

[WNYConsoles]

I agree with you on SOME of this however I really would like the big man himself or Martin C say that Phat RGH 1.0 needs to be updated to RGH 2.0 to work with DemoN.

Again, these are questions...
If you have 14699 RGH 1.0 with LDV 5 and create 15xxx retail image also with LDV 5 what does that matter? Why is updating the LDV required to use dual-nand retail/xbl. How would MS know that you should have LDV 6 and not 5?

 

[Dublicious]

its good that TX brings the news ASAP- Quote by Lio_X


Like any other thing be patient and when they get an official word Xecuter, Ubergeek or another member of the admin's will post something. Best wait this one out. Like all things you dont want hasty decisions made and bad info given to the scene.

 

[hansolo77]

I just got my glitch working 2 weeks ago. With this new information, does this mean i'll break the glitch if I update to the latest dash say via an onboard update that's included with a new game? Sorry I don't know, I'm still new. I saved my CPU and DVD keys when I dumped, and I also saved a backup of my original unmodified NAND. I just want to know if there's anything I have to do or get prepared to do on my end.

Also, my brother is going to want his glitched. Should I tell him not to update to the new dash if he's prompted? We haven't dumped his NAND yet so I would think so.

 

[Dublicious]

I agree with you on SOME of this however I really would like the big man himself or Martin C say that Phat RGH 1.0 needs to be updated to RGH 2.0 to work with DemoN.

Again, these are questions...
If you have 14699 RGH 1.0 with LDV 5 and create 15xxx retail image also with LDV 5 what does that matter? Why is updating the LDV required to use dual-nand retail/xbl. How would MS know that you should have LDV 6 and not 5?

Well Im sure they know exactly what consoles should have what updates. Its just best wait and get an official word instead of arguing a point that noone at this moment can clarify.

My grandma always used to say - "Never argue with an idiot on the street cause passers by cant tell the difference".

:rolleyes2::rolleyes2::rolleyes2:

---------- Post added at 23:41 ---------- Previous post was at 23:38 ----------

I just got my glitch working 2 weeks ago. With this new information, does this mean i'll break the glitch if I update to the latest dash say via an onboard update that's included with a new game? Sorry I don't know, I'm still new. I saved my CPU and DVD keys when I dumped, and I also saved a backup of my original unmodified NAND. I just want to know if there's anything I have to do or get prepared to do on my end.

Also, my brother is going to want his glitched. Should I tell him not to update to the new dash if he's prompted? We haven't dumped his NAND yet so I would think so.

Thats what they have been saying this whole time.. DO NOT UPDATE UNTIL you have your CPU Key and or an Original Nand from that console.

Xecuter stated this:
1) The cpu_key

2) 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!

 

[WNYConsoles]

As you said, we wait for DemoN tutorial, which will tell us exactly what to do. But if you need to have RGH 2.0 on Phat to run DemoN Hacked/Retail XBL than there will be a ton of upset people, especially those with Falcon RGH 1.0

 

[jsinger47]

As you said, we wait for DemoN tutorial, which will tell us exactly what to do. But if you need to have RGH 2.0 on Phat to run DemoN Hacked/Retail XBL than there will be a ton of upset people, especially those with Falcon RGH 1.0

Then those upset people should have read enough to understand what dual NAND with a stock, LIVE dash entails.

 

[Dublicious]

As you said, we wait for DemoN tutorial, which will tell us exactly what to do. But if you need to have RGH 2.0 on Phat to run DemoN Hacked/Retail XBL than there will be a ton of upset people, especially those with Falcon RGH 1.0

Best wait for an official word. Which Martin_C, Ubergeek, or someone else will be able to clarify this tomorrow. Not like the DemoN is released yet anyways.

 

[hansolo77]

Thats what they have been saying this whole time.. DO NOT UPDATE UNTIL you have your CPU Key and or an Original Nand from that console.

Ok so i'll tell him not to update. What about me? Am I safe and clear since I still have my original dumps?

 

[Dublicious]

Ok so i'll tell him not to update. What about me? Am I safe and clear since I still have my original dumps?

Never safe and clear mate. Since Im not part of the big picture, I would say wait until you get an official word from one of the higher ups stating if its ok to update and how to go about that update. Until than you could dump your brothers box and get his Key and get that box going for now.

 

[WNYConsoles]

That's REALLY a shame then, makes Falcon DemoN a pipe dream for most. Looks like Slim DemoN will be the superior method, provided 15xxx doesn't have a negative effect.

We shall wait and see.....

 

[jsinger47]

I'm not sure how much more clear you can make it than the original post.

Get your CPU key and a 14719 dump of the console before you update to 15572.
If you have these two things, you are all set to take the update.

 

[talby71]

I just got my glitch working 2 weeks ago. With this new information, does this mean i'll break the glitch if I update to the latest dash say via an onboard update that's included with a new game? Sorry I don't know, I'm still new. I saved my CPU and DVD keys when I dumped, and I also saved a backup of my original unmodified NAND. I just want to know if there's anything I have to do or get prepared to do on my end.

Also, my brother is going to want his glitched. Should I tell him not to update to the new dash if he's prompted? We haven't dumped his NAND yet so I would think so.

you don't update an RGH EVER using the official update or especially an ingame update, you use J-runner to create an updated nand and flash that your console...you only use the official update (renamed $systemupdate )once your dash is updated to update avatars and kinect

 

[WNYConsoles]

EDIT: Ill just wait for official tut, this is going no where.

 

[jsinger47]

EDIT: Ill just wait for official tut, this is going no where.

can you explain how you manage to boot a split-CB nand on RGH1?

you keep implying that its possible

 

[sarah1331]

I do get the whole rgh
Just to be clear??

In the op it says you need either before updating to 15***

1) cpukey
2) NAND dump of phat 14717/14719 slim down to 13***

I have always known it to be both not either can someone clear it up

 

[jsinger47]

I do get the whole rgh
Just to be clear??

In the op it says you need either before updating to 15***

1) cpukey
2) NAND dump of phat 14717/14719 slim down to 13***

I have always known it to be both not either can someone clear it up

1) if you have the CPU key, you can use a donor decrypted keystream and your 15572 dump to recreate a glitch image

2) if you have the 14719 dump, but not the CPU key, you can create an .ecc (using the XOR hack) to glitch into xell to get your CPU key

EDIT: if you have both, the process is much easier

 

[TilVl]

Okay he is basically saying

Dual nand -
nand 1 Updated to latest dash
nand 2 Old Dump with Single CB

Okay REASON it will not work is because of the revocation list. It blows a fuse that will not allow the single CB from the nand to boot.

Now building a retail nand through j-runner or something similar i'm sure it will use the new CB, which the newer CB wouldn't match the fuse of the old CB causing black screen.

I don't think it would be possible to run dual nand that is updated on one nand for XBL then use a older nand for RGH1 due to the fuse being burnt.

Fuseset 02

"
This is the lockdown counter for the 2BL/CB (The 2nd Bootloader, stored in NAND Flash) One of these are burned everytime the console updates it's bootloader (Which isn't very often) this is the reason that there is no way to recover a JTAG that has been updated to 2.0.8***.0, even is you have the CPU key, (2BL is encrypted with the CPU/1BL key, but is signed with Microsoft's private key so you can't change the lockdown counter in the NAND. The bootloader will fail signature checks, and panic)
"


Wish I had a phat here. Would glitch it then update and check fuseline 2.

 

[WNYConsoles]

Okay he is basically saying

Dual nand -
nand 1 Updated to latest dash
nand 2 Old Dump with Single CB

Okay REASON it will not work is because of the revocation list. It blows a fuse that will not allow the single CB from the nand to boot.

Now building a retail nand through j-runner or something similar i'm sure it will use the new CB, which the newer CB wouldn't match the fuse of the old CB causing black screen.

I don't think it would be possible to run dual nand that is updated on one nand for XBL then use a older nand for RGH1 due to the fuse being burnt.

See, now this is what you should of said before, not "I don't believe that's true".

Thank you for explaining it better.

 

[jsinger47]

See, now this is what you should of said before, not "I don't believe that's true".

Thank you for explaining it better.

are all those falcon owners still going to be very upset with Team Xecuter?