Originally posted by obliquefd:

---

I also just received my 360 back from Microsoft with a BenQ drive. I get the same error you have. Your computer is reading the firmware file correctly, however it appears Microsoft is using a larger key now. If you open the firmware file in a hex editor you will see what I mean.

Use the tutorial to get an idea.
http://caster420.360mods.net/verifybenqfwhex.pdf

I'm still trying to figure out this new key, but I'll keep you updated.

---

Originally posted by bhetrick:

---

Yeah, that's definately one I haven't seen before. I just edited an ix16 for the benq and emailed it to you.

Toolbox can detect your key (@ e0c0), but JF won't. So I just copied/pasted the string from e030 to e0c0 in to the ix16 fw. Now JungleFlasher will detect the edited version, with the key reported in the same location as Toolbox does, but yet it won't detect it in your original.

It's worth a shot flashing it and seeing if it works. You got the original to go back to if it doesn't.

And now that I'm thinking about it, I wonder if it'd work just reading the original with Toolbox, copying the key, then opening ix16 with Tb and pasting it in. You wouldn't have that entire string, just the key.

LIVE-wise, I'd imagine you'd want the entire string, or course. I'm just wondering if the "short" key would still work?


edit... I should have said to me it's worth a shot. I'd do it myself. But I'm not telling you to do it and not worry about it. Benq's are easily erased and flashed, so I believe it shouldn't be a problem.

But if that console is not yours and the owner is a LIVE user, I'd ask him first. You may want to wait until the ix team releases more info.

---