I've got a lite-on that I'm working on for someone. They burned off the R707 and R708 pads trying to do it themselves. I've been trying to dump the drive and create the dummy.bin and lite-cfw.bin and get it flashed for them. The drive plays originals perfectly, but when I try to get the key with my CK3 w/probe all I get is 0's. It only happens with this drive. I've got other lite-ons that I can dump perfectly, but this one just don't want to give it up for some reason. I've tried putting the tray at different places, half in, 1/4 in, 3/4 in just about every place the tray could be it's been in. But it still won't dump a valid key. I can't see any other physical damage to the drive other than the R707/R708 pads. Could there be anything else that I'm missing on this one?

It would freeze up after the erase. I figured out how to get around it on my computer. I had to use a seperate AT power supply and use that to power cycle the drive instead of using the CK3 to power cycle. Once I did it this way, jungleflasher would work perfect for me.

After clicking the lite-on erase button for me. I've been using the correct port, which is B000 for my via6421a. I had already uninstalled the VIA driver and deleted the file from the system32\drivers folder, rebooted and installed portio32 and rebooted again for good measure. It still froze on me after clicking lite-on erase. It would get the key and such just fine, same each and everytime, but when I hit lite-on erase, it would lock dead up. I can finish it in dos with dosflash and it works just fine. I figured if there was a different chipset that didn't poll the drive after the erase and one that worked with all the drives like this one used to, I'd be better off.

I have a via card that freezes even with the via driver uninstalled and using portio32. I was wondering what sata card, if there is one, that works best for these drives?

The availability of previous drives firmwares was due to the fact that we could dump those on our own. The original firmware was never part of a xtreme or ixtreme release that I know of. Maybe in the very beginning, but I can't remember that far back, but I don't recall it if it was.

I was thinking that D8 was the sector erase opcode for the Benq, not real sure though. I run dosflash in automode.

I have two launch consoles. One of them went RROD after the update but it don't blame the update because it had already went RROD previously. I will resurrect this box again when I get the time to though.

I actually like the idea of this. I don't solder all that well so it would be hard for me to remove the solder bridge when I was done to where it didn't look like a butcher had a hold of it, or possibly kill the drive in the process. Its my understanding that you only need TX anyway since the commands for the dump is sent over sata. I can't remember if its both or one, but then the information is then sent or transmitted back over the rs-232. I could be wrong on that though, but from the looks of the "spear", that must be how it works.

open sfdnwin from a command prompt with this command "sfdnwin.exe -nocheck" without the quotes and hit enter. You should get a small dialog box saying something about no check, click ok and then proceed to flash with kreons firmware.

Thanks caster, I'll let him know.

I've a friend who is having a terrible time replacing his MS-28 with a Benq drive. He tells me that is a VAD6038, but has a FW version os 60141D. Does anyone know if this is from a debug unit or something? If it is from a debug unit, can it be made to work on a retail unit?

Protonus, have you tried unlocking the drive prior to trying your rip? I didn't used to have to do this, but recently, I found it necessary before it would do a complete rip of an original.

This is pretty straight forward since your replacing the old drive with the same version of drive. Just use MTKFlash or iprep 101 to dump your firmware from your old drive. Then create your hacked firmware and flash it, or if you used iprep, connect your new drive and flash it with the hacked firmware that iprep created for you. If you were using two different brands or revisions of drives then the steps would be somewhat different. Just make sure that when you dump the firmware from the old drive that it gives you a valid dump with a good drive key.

Find the right hddss.bin or get a BEVS. hddhacker will only flash the right hddss.bin to the drive that it came from and it won't work at all with samsung or fujitsu drives. If you use the hddss.bin that came from that drive, it will work, but only if you haven't changed anything with that hddss.bin or other monkey business.

How many people do you need to tell you that won't work before you understand that you have to have the key before it will work. You have no key, therefore you can't use the drive. Your new drive will be just like the one you have. It will only be able to play movies. Take the time to read over this thread again and see how many different people was telling you that it simply won't work, it's not just plug and play man, you got to have the dvd key.

Also the security sector is signed so editing it with a hex editor will break the signature and it won't work.

Arakon is correct. I made this discovery not long after I edited the ss.bin I had. Even though the drive was an original 360 drive, the simple fact that I edited the ss.bin that I had to match that of the drive broke the signature and rendered it useless until I found the ss.bin that came from that drive. Once I flashed it with that ss.bin, it worked fine in the 360 again.

I had a similar problem with mine. I had to get a different external usb case than what I had. Seems the one I had worked fine for hdd's but didn't like optical drives at all. You might look into that.

Sorry for the double post, I suppose I waited to long to re-edit. I got the drive flashed, but the 360 will not recognize it. The first time I got it to flash, I didn't check it, I just shut everything down and tried it on the 360, went to the memory section and it said no memory devices detected. Took it off the 360, re-flashed it, got the it should work message. So I restarted the computer and re-flashed it again and I got the it should work message again. Tried it on the 360 and it still wasn't detected. Prior to flashing it, I removed the partition from the drive. Would this have been correct procedure?

ok, I can't seem to get this going properly. I have the original hddss.bin from the seagate drive but when I try to use hddhackr -f, it just tells me that the drive is not supported, make sure it a SATA WD Scorpio BEVS ! and puts me back to the DOS prompt.

Can I do this with a hex editor somehow or something to get this drive back to being a stock 360 drive?

EDIT: Never mind guys, I figured it out. Somehow the serial number from the drive and the serial number from the bin file didn't match. I fixed that and it flashed with no problems. Thanks for the help!!