Xval 2.0

[l_oliveira]

Your xbox is fine you cant swap hd's from xenon to new ones you get corrupt data error with new ones like falcon/falcon works perfect

His XBOX isn't fine at all. I have multiple versions of consoles here and the saves/harddisks work on any of them regardless of console version.

Only DRM stuff that kicks in when I move the harddisks around but then logging on XBOX live solves that issue.

[asagoren]

this is useless cuz its not checking the online database of $..

its only checking what youv allready know if you will connect a hard drive and see that its not installing games...

what we need is somthing that tells you if you will get banned the next tume you will connect to XBL

you were right guys this is an awesome tool i didnt understand the principle of it!

i assumed that microsoft baning consoles in the first moment they see the firmware but what you saying here is that they marking the id before the ban.. am i right?

[kartaq]

His XBOX isn't fine at all. I have multiple versions of consoles here and the saves/harddisks work on any of them regardless of console version.

Only DRM stuff that kicks in when I move the harddisks around but then logging on XBOX live solves that issue.

Yes, I agree. There is definately something off with this console, but why do I receive "secdata is clean" when obviously the console has lost its ability to sign content?

[l_oliveira]

Yes, I agree. There is definately something off with this console, but why do I receive "secdata is clean" when obviously the console has lost its ability to sign content?

The console never lost the ability of signing content. Instead it flags it's own data as "this file is dirty" and other XBOX consoles will refuse to load it.
If your SECDATA is clean, there's other files that could be corrupted or missing, like odd.bin and crl.bin.  But some of them being damaged or wrong would be indicated on the XCODE value, I believe.

[zillionare]

kool tool.

thanks.

[Redline99]

Remember though, the xval is only part of a security system. There are other things the console records that will eventually get you banned, NOT EVERYTHING is reflected in the xval.  You have to use your head and use it as only part of your information, you cannot rely on a single app/tool/status/etc.

[lprot]

New dashboards have E value. It looks like well known X value but numbers in hex are different. Does anybody know what it is and how to decode it?

[userix]

Is the e-value found in the system info screen on the console?  That value still works as the xval, because I tried to boot an AP2.5 game and got a secdata flag of "Failed AP25 Challenge" using xval 2.0.  So I believe it's still the same hex values used for the listed violations in the first post.

[gepal]

Redline99:
Just curious, what other bits you discovered in decrypted X-value? Or is it only those two?
I mean: Failed AP25 Challenge and Console Banned

[damox]

Redline99:
Just curious, what other bits you discovered in decrypted X-value? Or is it only those two?
I mean: Failed AP25 Challenge and Console Banned

Possible xval outputs:

Console Serial length incorrect
Console Serial is wrong
Encrypted X Value length incorrect
Encrypted X Value is wrong
Secdata is Clean
Secdata is invalid
Secdata decryption error
Failed AP25 Challenge
Tampered AP25 Table
Reverted AP25 Table
Invalid DVD Geometry
Invalid DVD DMI
DVD Keyvault Pair Mismatch
Invalid CRL Data
CRL Certificate Revoked
Unauthorized Install
Keyvault Policy Violation
Console Banned
ODD Violation
Unknown Violation(s)

[gepal]

Thank you damox, I just reread first post of this thread and there values was already listed (inattentive me).

If console was flagged offline I suppose it is possible to revert secdata.bin to previous (good one) and have clean console.
If not only secdata.bin has been changed then overwriting whole NAND do the trick.

Am I right?

[l_oliveira]

For that to work, currently one need to have a full backup of the nand and don't update the console.