-
If I were you I would wait until you run into the problem before assuming you have one.
Sometimes you come across these little benq gems, I dont know if its from left over stock they're attempting to deplete or what but nevertheless I have seen this type of mix before.
I would try the key on another drive and see what happens.... if its not spoofed as anything it should be the original as it would most likely kick back a e64 (or 65?) with the wrong string ID if I'm not mistaken.
Hope that helped!
-
Oh yeah I forgot about that e64. Thats encouraging. Thanks
-
the Aug'09 dash update means that drives no longer need spoofing, so no e64 error would be present.
-
im sure i read somewhere that one of the dash updates disabled the drive id check(so an unspoofed drive wont throw up an error) , could be wrong , either way tho as traviss63 try the key in another drive:D
^^^^^^^^^^^^^ Doh too slow lol
-
Mother f'er!!
Yeah, my first suspicions were correct. The key doesnt work. This drive dont belong in this console.
How could the guy be so bare faced, I even went round to the guys house to pick it up. He claimed to have no clue about xboxs.
-
Correct me if I'm wrong, but if it has 7363, it can be JTAG'ed and you can recover the DVD key, then revert it back to stock
-
QUOTE(supersdude1691 @ Mar 26 2010, 01:06 PM)

Correct me if I'm wrong, but if it has 7363, it can be JTAG'ed and you can recover the DVD key, then revert it back to stock
Correct. But....
QUOTE(radoman @ Mar 26 2010, 01:07 PM)

The console manufacture date is sept09
Out of luck.
-
What difference does that make? If it's 7363 then JTAG and see if the CB version is exploitable.
-
QUOTE(xbox360sexual @ Mar 26 2010, 03:00 PM)

What difference does that make? If it's 7363 then JTAG and see if the CB version is exploitable.
If it is manufactured after June 18th it is not exploitable.
QUOTE
The console manufacture date is sept09
-
QUOTE(Ranger72 @ Mar 26 2010, 08:22 PM)

If it is manufactured after June 18th it is not exploitable.
Meh, I'd jtag it anyway, manufacture date doesn't mean an awful lot.
-
QUOTE(xbox360sexual @ Mar 26 2010, 11:08 PM)

Meh, I'd jtag it anyway, manufacture date doesn't mean an awful lot.
Erm, yes it does.
Any console made after 2009-18-06 has a patched CB and therefore cannot be JTAGGED!
-
Chances are that is "Service Date" and not "MFR Date"
Either way, what does he have to lose?
-
Indeed.
-
QUOTE(OggyUK @ Mar 27 2010, 06:58 AM)

Chances are that is "Service Date" and not "MFR Date"
Either way, what does he have to lose?
Why would a Jasper need to be serviced? Also, Microsoft doesn't send back "Serviced" consoles that are Jaspers.
So no, that is not a 'Service Date", it's the "Manufacturing Date" which is over three months past what a lot of people claim in the cut-off period.
To me it would be a waste of time messing with it because it's 99.99% not going to be worth it and be a waste of time.
-
What do you think they do to faulty jaspers?? Not service them and send a falcon out ?
Okaaaay
-
jtag soldering really is the easiest thing ever, it takes me a couple of minutes at most and I'm not a professional.
You're mad not to attempt it with your dashboard version, imo.
-
QUOTE(xbox360sexual @ Mar 26 2010, 12:13 PM)

the Aug'09 dash update means that drives no longer need spoofing, so no e64 error would be present.
Really and you believe that why? They don't ever open loopholes they only close them. That would be some pretty big news and know one has ever said anything about it. The OSIG string maybe doesn't need spoofing but you will always have to spoof the key that is embedded in the keyvault and won't ever change without modification.
Of course you also tried saying the MFG date wasn't that big of a deal HA , you know alot don't you buddy. I have found 360s with a dash of 6717 that weren't exploitable , a xenon had a 1940 CB.
-
QUOTE(radoman @ Mar 28 2010, 08:10 PM)

Tell that to the two consoles in front of me which boot fine with unmatching drives and keys
Ok so i tried it and you were right , still doesn't make sense , the CPU key would still have a DVD key attached to it. Then again the drive pairing doesn't matter really just made it harder for us to swap them out from machines to machine the modified firmware had nothing to with spoofing if you were keeping the same drive. That just means they added the check somewhere else , maybe checks your system when it boots for modified firmware , and flags you that way instead of waiting for you to try and sign on too LIVE.
-
QUOTE(juggahax0r @ Mar 29 2010, 12:06 AM)

Really and you believe that why? etc etc blah....
yawn....
-
QUOTE(OggyUK @ Mar 28 2010, 01:26 PM)

What do you think they do to faulty jaspers?? Not service them and send a falcon out ?
Okaaaay
here in portugal they are selling refurbished jaspers with service date of december 2009 ! , so yes they have faulty jaspers and they sell them ! ( after refurb )