LITEON DG-16D2S Need opinion on flashing drive to stock from xell dvd key

Status
Not open for further replies.

WildCard007

VIP Member
Feb 27, 2013
285
0
USA
Hey,

I bought 30 16d2s (phat) drives off of EBAY a while back. They came in mixed firmware and some drive cases weren't on. They were supposed to have one issue or another and the repair shop I bought them from just got new drives to replace the "bad" ones that were taken out of the consoles. Then I bought a few Phat 360s that had the wrong dvd drives in the consoles. My plan is to pull the DVD keys then put the correct keys on the drives and sell them as stock consoles that can be used on Xbox Live.

I've pulled one key so far, put it on a console and it plays original games perfectly. I read that in order to have the drive and console work on Live that you need to get the KV (OSIG) information using J-Runner, a Coolrunner Rev.C, and JR-Programmer V2. Then put the DVD key on the Drive using JungleFlasher, X360USB V2, and Probe 3. Those are the items I used.

I pulled the CPU key and DVD key from Xell, put the CPU key in J-Runner, and looked at the KV Tab.
The KV Tab said this:
KV Type: 2
Console ID: 0849264591 (Does not match console ID in Dash)
Serial Number: (Matching S/N)
Region: 0x00FF | NTSC/US
OSIG: PLDS DG-16D2S 8385
DVD Key: (Actual DVD Key)
Jasper 512MB

Next I found a drive that was labeled on the outside as a Lite-On - DG-16D2S - A0A1 - 74850C. When I hooked it up to JungleFlasher and pulled the key it told me it was a Lite-On - DG-16D2S - A030 - 83850C. After that I left the 83850C firmware loaded as the source on the Firmware Tool 32 Tab and loaded the stock FW 83850Cv1 as the Target. I spoofed source to target, then manually spoofed the correct DVD Key, saved to file, then proceeded to the MTK Flash 32 tab to follow the Lite-On Erase steps from the JungleFlasher Documentation. Everything went smooth except it gave me the extra warning of "DVD key doesn't match" because of the correct console's DVD Key instead of the DVD Key I pulled from the DVD Drive.

After that I saved the CFW file that has the correct key with the spoofed information from the DVD drive and flashed it to the DVD drive. I plugged it up and it works.

Here are my questions:
- Based on what I've done will this console work on Live without getting banned?
- If I do not have a DVD Drive that matches the OSIG information would I be safe to just load up the stock FW in the target, manually spoof the Key, save the file, then proceed with erasing the drive?
- Should I redo the DVD Drive using only the stock FW and the DVD Key?

Thank you for your help.
 

ezzda1

VIP Member
Jul 8, 2009
773
0
Bolton, UK
If it works it should be fine.
All phat lite ons are cross flashable with any other phat lite on. Just use the fw the console kv asks for.
They all get updated to the same firmware (02510c) after dash 13141 anyway.
 
Last edited:

WildCard007

VIP Member
Feb 27, 2013
285
0
USA
To Jsinger47:
The console is a Jasper currently on dash 2.0.9199.0. I wanted to leave it at that dash incase someone wanted to mod it.

To ezzda1:
OK, I wasn't sure if the Stock FW was enough on any Lite-On or if it had to match an existing FW on the drive's board. Mainly because of the different FW versions for 8385 and 74850 for Pre 13141 dashes.
 

ezzda1

VIP Member
Jul 8, 2009
773
0
Bolton, UK
With the info you just gave its the right fw for its dash and will be fine.
You just need to watch out what dash the console is on cos the kv will not change it will still say 83850c or 74850c etc even when it's been updated to 02510 with an official update.
 

WildCard007

VIP Member
Feb 27, 2013
285
0
USA
Ok, thanks. So if I update the console with an official update it will update the DVD Drive FW to the latest along with the dash and all is well. However, if i were to pull the same nand from the board after the latest official update to get the key, it will say under the KV Tab in J-Runner it will say 83850C but I need to use the dashboard to confirm what the actualy FW will be, like according the dashboard it will actually be a 02510. Is that correct?
 
Status
Not open for further replies.