Originally posted by wabashman:

---

i hope they fix it, because i just sent two units into MS for repair, and dont feel like messing around with them when i get them back because i already have them sold pretty much.

---

Originally posted by wabashman:

---

oh ill let you know, because ill be running to bhetrick asking for help since i have no clue how to use hex editor.

---

Originally posted by ApoIIIo:

---

I just ran into this problem last night and all i did was take the firmware that i dumped using dosflash and put it into 360 fw toolbox and copied the key out of there, pasted it into the new 1.6 firmware, saved and flashed and I have no problems. Ill give it a month and update on whether or not the console is banned or not.
If this works then its even easier, no need for a hex editor.

---

Originally posted by leerage:

---

Originally posted by ApoIIIo:

---

I just ran into this problem last night and all i did was take the firmware that i dumped using dosflash and put it into 360 fw toolbox and copied the key out of there, pasted it into the new 1.6 firmware, saved and flashed and I have no problems. Ill give it a month and update on whether or not the console is banned or not.
If this works then its even easier, no need for a hex editor.

---

Firmware tool box also doesn't copy over serial data.

---

Originally posted by ApoIIIo:

---

Originally posted by leerage:

---

Originally posted by ApoIIIo:

---

I just ran into this problem last night and all i did was take the firmware that i dumped using dosflash and put it into 360 fw toolbox and copied the key out of there, pasted it into the new 1.6 firmware, saved and flashed and I have no problems. Ill give it a month and update on whether or not the console is banned or not.
If this works then its even easier, no need for a hex editor.

---

Firmware tool box also doesn't copy over serial data.

---

so does that mean that i will almost certainly get banned? or does it mean nothing really

---

Originally posted by gameover9:

---

how do you know what they check for?

---

Originally posted by JF 0.1.64 log:

---

Removed - not allowing blank serial in for Lite-on Dummy.bin
- previously if serial was blank the iX file serial was left as is
- Warning changed for dummy.bin w/o serial, to mention is possibly ok.

---

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.

---