Thread: rgh 15574

that is true. if you don't have the cpukey, you won't be able to RGH on dash 15572 or higher.

ok then thank you i will just get the jtaged one then thanks agen

I think you don't necessarily need the CPU key, just any old nand dump from before 15XXX. (though, they may not have released the method for it w/o CPU key yet)

any dump before 15xxx without cpu key is worthless. you cannot build a glitch image without the cpu key!

Per TX:
2. 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.

If you have a nand-dump, you're still able to create a xell ECC, and grab your CPU key even on 15XXX and later. The CPU key is not necessary for xell ECC (nor has it ever been).

Originally Posted by Kipper Williams

ok then thank you i will just get the jtaged one then thanks agen

If it's a reliable console, and you have no plans to install a dual nand such as a DemoN, you'll be better off anyway. The Jtag hack is more reliable than RGH overall.

Originally Posted by Maelstrom

I think you don't necessarily need the CPU key, just any old nand dump from before 15XXX. (though, they may not have released the method for it w/o CPU key yet)

Technically, this is half-true. You need the CPU key, or a split CB dump (14717/14719 for PHAT, 14719 or lower for SLIM). However, until they figure out how to get the CPU key from the dump of a console that's already been updated to 15574, you still need the CPU key anyway for all practical purposes.

Originally Posted by Maelstrom

Per TX:
2. 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.

If you have a nand-dump, you're still able to create a xell ECC, and grab your CPU key even on 15XXX and later. The CPU key is not necessary for xell ECC (nor has it ever been).

Originally Posted by charincol

Technically, this is half-true. You need the CPU key, or a split CB dump (14717/14719 for PHAT, 14719 or lower for SLIM). However, until they figure out how to get the CPU key from the dump of a console that's already been updated to 15574, you still need the CPU key anyway for all practical purposes.

Sorry to sound like a noob, but I'm looking for a bit clarification after charincol's reply.

I have a Falcon running 14719. So all I need to do is dump the NAND, then I can safely upgrade to 15574 while still being able to RGH it later using just the 14719 NAND dump and there is no need to explicitly dump the cpu key now while I'm still on 14719, correct? Also, would it be safe to update to 16197 after getting the 14719 dump, or is that too early to say yet?

And so I understand, the reason (oversimplified) is because MS added encryption to the rc4 keystream so it can not be extrapolated by comparison methods anymore and without the keystream you can't encrypt the xell ecc code used to extract the cpu key with, correct?

Finally, is the fact that 15574 is unhackable actually still true? Given the Corona was hacked while back, there have been some well sourced rumors floating around the past 2-3 weeks that Xecuter has found a solution to 15574 but are holding it back pending MS's fall update? Thou I guess we will see now since it has been released as of 2 days ago. Regardless if this is true or not, I'm still going to dump my 14719 NAND before upgrading.

Thank you in advance.

You pretty much got it. No info has been released about the new update and RGH.

Sent from my HTC Incredible Ass

Thank you.

One more question.

Is the LPT method of dumping the NAND still a viable option? Was planning on using Nandpro3 to take 3 or 4 dumps and run them through NandCompare1.4. I know it's very slow and prone to errors if the cable is too long/unshielded, but beyond that, it's still a functional choice right?

Then I can stash that 14719 dump away and update in the meantime till I'm able to get a Demon and CoolRunner 3. Is ModChipCentral reputable (sorry, that was two questions, wasn't it...)?