Page 1 of 1

Help Requested

Posted: Sun May 02, 2010 3:52 pm
by MrMiscellaneous
Well over this past week i jtag'd my falcon.Unfortunately it's cb is 5771. I was wondering if there was a way to replace the cb fuse since it was blown by microsoft. Another question,is the dvd key the same as the cpu key?It has 32 characters and they ONLY include 0's-9's and A's-F's
Any help will be much appreciated :)

Re: Help Requested

Posted: Sun May 02, 2010 5:51 pm
by HaGGardSmurf
dvd and cpu keys are different.

As for the fuse, I dont think so.

Re: Help Requested

Posted: Sun May 02, 2010 6:35 pm
by MrMiscellaneous
I have a xenon that i fixed to play online.Could i unban my banned xbox with the xenon's keyvault or do i need the cpu key of the one i jtag'd?

Now to just wait for a way to make it exploitable....

Re: Help Requested

Posted: Sun May 23, 2010 1:36 pm
by technoe
You can use the key if the banned xbox is also a xenon and jtag-accessible.

Re: Help Requested

Posted: Mon May 24, 2010 2:51 pm
by Han Cholo
MrMiscellaneous wrote:Well over this past week i jtag'd my falcon.Unfortunately it's cb is 5771. I was wondering if there was a way to replace the cb fuse since it was blown by microsoft. Another question,is the dvd key the same as the cpu key?It has 32 characters and they ONLY include 0's-9's and A's-F's
Any help will be much appreciated :)
Did you blow a fuse or did it just get banned? Fuses don't actually get blown the values change, but the only way that would happen is if you attempted to sign on LIVE with the 8955 dash after the 9199 update. If you did that and attempted to update then the values on your fuses would have changed (thus changing your cpu key) That would kill your jtag and make it a normal console. It will also not be jtagable again.

Unless you had the r6t3 resistor removed, then the fuses wouldn't have "blown" in which case you'd just need to redo the jtag on your console.

Re: Help Requested

Posted: Mon May 24, 2010 2:59 pm
by Han Cholo
NM I just noticed that your CB was 5771. So your xbox was not jtaggged.

5771 is not exploitable. There's no way to change that. You might as well update to the newest dashboard.