Yeah i agree this is going to be alot to learn. With little and no understanding i have figured how to edit the xam.xex and change the kernal version to the latest. This will allow me to conect on a older dashboard and spoof as the 12625 while having the 12611 kernal.
I have been scrolling through the data looking for anything that pops out, a shot in the dark to be honest. I have found these challenges and think they are the correct ones.
Im rather exited and started to learn ppc but it mega hard, if anyone wants to take a look and maybe give some advice if im right or wrong i have attatched my xam.xex below to look at.http://www.megaupload.com/?d=DXRCQAD1
The information i have been using is his quote
"More for you guys to look at,
The challenges are sent back to M$ and it carries them info to do checks on your console.
There is value's in place, look into the challenges, one challenge should be getting edited with alot of sub routes that lead up to that one challenge, there is challenges in more areas then the hypervisor.
Console return value's it may be the value being a mis match which then leads to your JTAG not connecting at all.
They can detect everything on your console unless removed/spoofed so the value's get detected, if it is a match to the set default value then connecting will occur, if say there was a modified console and it tries to connect, it is modified and the server checks would be able to detect it considering its modded, it is sending back a different value.
That is just another thing for you guys to look into, look into what info is being sent back from the challenges, and where they are being executes, where the return and response take place also.
There is many many things that need to be looked at, the only way you will find the exploit is through testing and searching.
+All the hypervisor talk does not mean the actual function getting modded is pulled directly from the hypervisor, the hypervisor contains no actual online whole functions. Other functions from places out side the hypervisor use its imports. Some functions grab info out of the hypervisor but the whole function is not directly locate din the hypervisor, it is just re directing info from it".