LITEON DG-16D4S - SLIM Putting a drive key on to another liteon

[Carlooch]

Ok so I had a slim RGH, that had a liteon in it. I botched flashing it ruined the drive. But I have the Dummy.bin.

How to I use the Dummy.bin or key to put it on another slim liteon. Not sure how to do this in jungle flasher. Can anyone point me in the right direction

 

[BL4K3Y]

The JungleFlasher tutorial explains how to flash your drive if you unlock the PCB.

However, if you buy an Xecuter Unlocked PCB, follow this tutorial.

 

[Spudnutz]

Ok so I had a slim RGH, that had a liteon in it. I botched flashing it ruined the drive. But I have the Dummy.bin.

How to I use the Dummy.bin or key to put it on another slim liteon. Not sure how to do this in jungle flasher. Can anyone point me in the right direction

Newest JungleFlasher Tutorial for JF1.8.7 onwards - http://bit.ly/FPsi9

with alil bit of reading you will have it sorted
:cool2:

 

[Carlooch]

Sorry I forgot to mention I just unlocked the new drive I have for it. I just don't know how to get the correct key on it without having done a full dump. All I have is the old dummy.bin

 

[BL4K3Y]

Read the tutorial Spudnutz linked to.

 

[Carlooch]

Alright thanks guys, just making sure I wasn't screwed outta having a fully functional consoles

 

[Spudnutz]

Sorry I forgot to mention I just unlocked the new drive I have for it. I just don't know how to get the correct key on it without having done a full dump. All I have is the old dummy.bin

load source (dummy.bin)/load target -user defined(pends on drive version and cfw/ofw)/spoof source to target/ensure drive is in vendor mode/write/outro

:cool2:

 

[Carlooch]

load source (dummy.bin)/load target -user defined(pends on drive version and cfw/ofw)/spoof source to target/ensure drive is in vendor mode/write/outro

:cool2:

Link To Image

ok I just did all of the above, at the end of the flash this is what it says, is this ok ?

 

[k0mpresd]

kamikaze fail.

 

[Carlooch]

kamikaze fail.

I dont think so, because if I flash the OFW from the new drive, it seems fine.

 

[Spudnutz]

I dont think so, because if I flash the OFW from the new drive, it seems fine.

Link To Image

what model is the old drive?
what model is the new drive?
what fw did you attempt to flash to the new drive?
why not post the entire log?

DETAILS!

 

[jsinger47]

ok I just did all of the above, at the end of the flash this is what it says, is this ok ?

Link To Image

You have to erase the drive first. That's all

 

[k0mpresd]

You have to erase the drive first. That's all

i have flashed lots of drives and never have i had to erase the drive first. the only erasing done is when jf goes to write the target firmware. the only time i have seen verify failed is on bad kamikazes.

 

[jsinger47]

i have flashed lots of drives and never have i had to erase the drive first. the only erasing done is when jf goes to write the target firmware. the only time i have seen verify failed is on bad kamikazes.

you've never cross-flashed a slim with different firmware then.

it has to do with the way JF read/writes/verifies the key area

therefore, he has to erase the drive before he can flash it with a new key sector

simple

 

[Carlooch]

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

JungleFlasher 0.1.92 Beta (304)

Session Started Thu Apr 26 02:07:31 2012



This is a Wow 64 process running on 2 x 64 bit CPUs

X360USB PRO detected, Version 0.18



Found 1 I/O Ports.

Found 1 Com Ports.

Found 7 windows drives C: D: F: G: H: I: Q:

Found 1 CD/DVD drives D:



Sending Vendor Intro to port 0x0000

Status 0x51

Sending Vendor Intro to port 0x0000

Status 0x51

Re-sending Vendor Intro:

.............

Serial flash found with Status 0x72



Sending Device ID request to port 0x0000

Spi Status: 0x00

Manufacturer ID: 0xC2

Device ID: 0x11

Flash Name: MXIC(MX25L2005)

Flash Size: 262144 bytes



Getting Status from port 0x0000

SPi flash found with Status 0x72



Sending Chip Erase to Port 0x0000

Erasing:

Done !

Loading firmware file C:\Users\carl\Desktop\slim rgh drive\Dummy.bin

MD5 hash: d1ba43aefb40f7ce2bda388d70051930

Inquiry string found

Identify string found

Drive key @ 0xA030 353EEBD79ECDE961D030C68B7796DE8B

Firmware Osig: [PLDS DG-16D4S 0401]

Firmware is: SlimKey Extract

Auto-Loading firmware file C:\Users\carl\Desktop\JungleFlasher v0.1.92 Beta (304)\firmware\LTPlus-0401-v3.0.bin

MD5 hash: 87fba52607d01d3c73722f9f818588c9

Genuine LT plus v3.0

Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Firmware Osig: [PLDS DG-16D4S 0401]

Firmware is: LT-Plus 3.0

Spoofing Target

DVD Key copied to target

Key Sector copied from Source to Target

Target is LT - ID strings not copied to Target



Loading firmware file C:\Users\carl\Desktop\JungleFlasher v0.1.92 Beta (304)\firmware\Stock firmware\LiteOn (Slim)\0272\Orig-0272.bin

MD5 hash: 371cb1cdf0c953534cbca83c6930abb9

Drive key @ n/a FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

Firmware Osig: [PLDS DG-16D4S 0272]

Firmware is: Stock

Spoofing Target

DVD Key copied to target

Key Sector copied from Source to Target

Target is LT - ID strings not copied to Target





Getting Status from port 0x0000

SPi flash found with Status 0x72



Sending Chip Erase to Port 0x0000

Erasing:

Writing target buffer to flash

Writing Bank 0: ................

Writing Bank 1: ................

Writing Bank 2: ................

Writing Bank 3: ................

............

Flash Verification Test !

Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................

Dumped in 3978mS



Write verified OK !



Restoring sector 0x3E000.



Sending Sector Erase to Port 0x0000

Erasing: 0x3E000

Writing: 0x3E000

............

Authorisation Failed!

Restore Verify Failed !

 

[jsinger47]

make sure to power cycle the drive after erasing

 

[k0mpresd]

you've never cross-flashed a slim with different firmware then.

it has to do with the way JF read/writes/verifies the key area

therefore, he has to erase the drive before he can flash it with a new key sector

simple

3e000 is not the key area.

 

[jsinger47]

3e000 is not the key area.

never said it was

 

[k0mpresd]

why when you load the dummy.bin it autoloads 0401 but then you turn around and load orig-0272 and spoof it? obviously orig was 0401 or theres a piece of information missing.

 

[Travo112]

Edit: nvrmnd


Sent from my iPhone 4s using Tapatalk