DG16D4S Drive (360 Slim Drive)

[chriswiegand]

Geremia, SPI unlocked ? Write PM, m8 ;-)

@bananisch -> Geh zurück zu Boerse, Looser haben hier nichts zu suchen X-D

[chriswiegand]

So what exactly is going to happen when you want to put the original drive back in?

Your console will be in original condition, man. Use ur brain.

[h04ever]

Working on... LTEX v0.4b
Actual - v0.4b

Code:

- read/write/erase 9504 (Lite-On SLIM)
- complete dump 9504 and 0225
- now working on WRITE and ERASE for 0255

[the-green]

Welldone h04ever it's a great news from you...
Can you give us a link to download this software & to use-it please??

[the specialist]

Working on... LTEX v0.4b
Actual - v0.4b

Code:

- read/write/erase 9504 (Lite-On SLIM)
- complete dump 9504 and 0225
- now working on WRITE and ERASE for 0255

is fake, he created and compiled bat to exe. and deceives you



@echo off
cls
ECHO.
echo  
echo  LT SLIM DRIVES DVD KEY EXTRACTOR v0.1a
echo  --------------------------------------
echo  Lite-On DG-16D4S 9504/0225 KEY EXTRACTOR                        
echo  This version read only DVDKEY
echo  LISTEN ON PORT 0x1140
echo  FOUND : DG-164D4S [0225]
echo  DECRYPT DATA! REPOWER DRIVE! <1s>
echo  .................................
echo  Done!
echo  DVDKEY : 6799A33E649B5B9235EDFC8C120EE593
echo  SAVING key.bin......done!
echo.

any noob do it. lol

[l_oliveira]

it's made of rubber ! LaTEX....   

[xstationbr2]

it's made of rubber ! LaTEX....   

Hahaha made of rubber maybe their brain is made of rubber too LOL.

[DeXteR_CwB]

So what exactly is going to happen when you want to put the original drive back in?

Your console will be in original condition, man. Use ur brain.

 

[DeXteR_CwB]

man, it´s not so easy to understand what you write 

now with the new dash, Xbox 360 S expects dvd key + inquiry data, once the inquiry, that was previously recorded, belongs to the new DG16D4S.... the xbox S is expecting this kind of inquiry from original drive, in case of any mismatch... you will face play dvd issue.

btw, inquiry data from DG16D4S it is not only different, it is bigger than inquiry data from DG16D2S!!!

 This problem happens only with the 12611 dash? Because i have a lot of slim with Liteon with LTplus 9xxx with original dummy.bin data put by hex editor and real spoof patch from the page 11 of this topic, working like a charme with 12416.

[mprenditore]

Working on... LTEX v0.4b
Actual - v0.4b

Code:

- read/write/erase 9504 (Lite-On SLIM)
- complete dump 9504 and 0225
- now working on WRITE and ERASE for 0255

Can you post the tool? In this way we can eliminate all doubt!

[ZerOneX]

man, it´s not so easy to understand what you write 

now with the new dash, Xbox 360 S expects dvd key + inquiry data, once the inquiry, that was previously recorded, belongs to the new DG16D4S.... the xbox S is expecting this kind of inquiry from original drive, in case of any mismatch... you will face play dvd issue.



btw, inquiry data from DG16D4S it is not only different, it is bigger than inquiry data from DG16D2S!!!

 This problem happens only with the 12611 dash? Because i have a lot of slim with Liteon with LTplus 9xxx with original dummy.bin data put by hex editor and real spoof patch from the page 11 of this topic, working like a charme with 12416.

i don't know why yet, but this issue is not happening with all Xbox 360 S. Even with "real" spoof will not work. The other suspect is that the Xbox S that are working fine with spoofed drive on dash 12xxx will not recognize the original drive anymore, because the inquiry data mechanism. I did not tested it yet.

[morenomdz]

Yo I ran some tests over the weekend. Moded about 12 consoles so here we go:

* 360`s with 9199 dash, I did run few originals (all pre ap2.5 like halo reach, forza 3 etc), made a profile and saved games, then swapped in an liteon7 drive, then updated to the 12xxx dash with asscreed bhood. Every single one is working fine.

* Two 360`s came already on the newst dash, the owner did update it online, one did play many games online the other only CoD:bo, swapped in an liteon7 spoofing on jf (load lt+1.1 9xxx and add the key), both are working fine.

* Few 360`s I updated online first, never played a single original game on these, moded with an liteon7, then played an original game, saved game etc... Nothing happened. Working fine.

With all xboxes I did re install the original drive after the tests and updates to see if it would still play fine and yes they did. The only thing I did not do and I won`t is play online, even connect to live, with their xbox, as it will most likely be banned asap so yea, not happening.

So, I have no idea why some consoles might start refusing other drives than the original after some time.

[iateshaggy]

i'm sure it is just pebkac, but it is easier to tell noobs they can't do stuff.

[Yntialan]

Yo I ran some tests over the weekend. Moded about 12 consoles so here we go:

* 360`s with 9199 dash, I did run few originals (all pre ap2.5 like halo reach, forza 3 etc), made a profile and saved games, then swapped in an liteon7 drive, then updated to the 12xxx dash with asscreed bhood. Every single one is working fine.

* Two 360`s came already on the newst dash, the owner did update it online, one did play many games online the other only CoD:bo, swapped in an liteon7 spoofing on jf (load lt+1.1 9xxx and add the key), both are working fine.

* Few 360`s I updated online first, never played a single original game on these, moded with an liteon7, then played an original game, saved game etc... Nothing happened. Working fine.

With all xboxes I did re install the original drive after the tests and updates to see if it would still play fine and yes they did. The only thing I did not do and I won`t is play online, even connect to live, with their xbox, as it will most likely be banned asap so yea, not happening.

So, I have no idea why some consoles might start refusing other drives than the original after some time.

 I ran all tests cited by morenomdz.xboxes working fine

[DeXteR_CwB]

man, it´s not so easy to understand what you write  

now with the new dash, Xbox 360 S expects dvd key + inquiry data, once the inquiry, that was previously recorded, belongs to the new DG16D4S.... the xbox S is expecting this kind of inquiry from original drive, in case of any mismatch... you will face play dvd issue.



btw, inquiry data from DG16D4S it is not only different, it is bigger than inquiry data from DG16D2S!!!

 This problem happens only with the 12611 dash? Because i have a lot of slim with Liteon with LTplus 9xxx with original dummy.bin data put by hex editor and real spoof patch from the page 11 of this topic, working like a charme with 12416.

i don't know why yet, but this issue is not happening with all Xbox 360 S. Even with "real" spoof will not work. The other suspect is that the Xbox S that are working fine with spoofed drive on dash 12xxx will not recognize the original drive anymore, because the inquiry data mechanism. I did not tested it yet.

 I have no problem with this, both drives works fine after update here ( Dash 12416 )

 The update has been made with the spoofed drive first

[ZerOneX]

man, it´s not so easy to understand what you write  

now with the new dash, Xbox 360 S expects dvd key + inquiry data, once the inquiry, that was previously recorded, belongs to the new DG16D4S.... the xbox S is expecting this kind of inquiry from original drive, in case of any mismatch... you will face play dvd issue.



btw, inquiry data from DG16D4S it is not only different, it is bigger than inquiry data from DG16D2S!!!

 This problem happens only with the 12611 dash? Because i have a lot of slim with Liteon with LTplus 9xxx with original dummy.bin data put by hex editor and real spoof patch from the page 11 of this topic, working like a charme with 12416.

i don't know why yet, but this issue is not happening with all Xbox 360 S. Even with "real" spoof will not work. The other suspect is that the Xbox S that are working fine with spoofed drive on dash 12xxx will not recognize the original drive anymore, because the inquiry data mechanism. I did not tested it yet.

 I have no problem with this, both drives works fine after update here ( Dash 12416 )

 The update has been made with the spoofed drive first

try to update to 12611 and see what happens!!

[morenomdz]

try to update to 12611 and see what happens!!

My B but does any of the newest games come with that dash rev already?

[DeXteR_CwB]

try to update to 12611 and see what happens!!
[/quote]

My B but does any of the newest games came with that dash rev already?
[/quote]

 This version is only from Live at the moment ( i think )

[DeXteR_CwB]

man, it´s not so easy to understand what you write  

now with the new dash, Xbox 360 S expects dvd key + inquiry data, once the inquiry, that was previously recorded, belongs to the new DG16D4S.... the xbox S is expecting this kind of inquiry from original drive, in case of any mismatch... you will face play dvd issue.



btw, inquiry data from DG16D4S it is not only different, it is bigger than inquiry data from DG16D2S!!!

 This problem happens only with the 12611 dash? Because i have a lot of slim with Liteon with LTplus 9xxx with original dummy.bin data put by hex editor and real spoof patch from the page 11 of this topic, working like a charme with 12416.

i don't know why yet, but this issue is not happening with all Xbox 360 S. Even with "real" spoof will not work. The other suspect is that the Xbox S that are working fine with spoofed drive on dash 12xxx will not recognize the original drive anymore, because the inquiry data mechanism. I did not tested it yet.

 I have no problem with this, both drives works fine after update here ( Dash 12416 )

 The update has been made with the spoofed drive first

try to update to 12611 and see what happens!!

 Look, i not believe that the problem is rev 12611, because this guy had the problem with rev 12416 ( See the post 5 )

 All consoles that i swapped the drive and updated to 12416 is working fine, i only see this error on two 250gb consoles from my clients, spoofed in Paraguay.

  I believe the problem is firmware without data from original dummy.bin and without spoof to 9504.

 

[xstationbr2]

man, it´s not so easy to understand what you write  

now with the new dash, Xbox 360 S expects dvd key + inquiry data, once the inquiry, that was previously recorded, belongs to the new DG16D4S.... the xbox S is expecting this kind of inquiry from original drive, in case of any mismatch... you will face play dvd issue.



btw, inquiry data from DG16D4S it is not only different, it is bigger than inquiry data from DG16D2S!!!

 This problem happens only with the 12611 dash? Because i have a lot of slim with Liteon with LTplus 9xxx with original dummy.bin data put by hex editor and real spoof patch from the page 11 of this topic, working like a charme with 12416.

i don't know why yet, but this issue is not happening with all Xbox 360 S. Even with "real" spoof will not work. The other suspect is that the Xbox S that are working fine with spoofed drive on dash 12xxx will not recognize the original drive anymore, because the inquiry data mechanism. I did not tested it yet.

 I have no problem with this, both drives works fine after update here ( Dash 12416 )

 The update has been made with the spoofed drive first

try to update to 12611 and see what happens!!

 Look, i not believe that the problem is rev 12611, because this guy had the problem with rev 12416 ( See the post 5 )

 All consoles that i swapped the drive and updated to 12416 is working fine, i only see this error on two 250gb consoles from my clients, spoofed in Paraguay.

  I believe the problem is firmware without data from original dummy.bin and without spoof to 9504.

 

Well a friend of mine have no lucky in this case because their Xbox 360 S 250Gb is with the same problem before dump their 9504 and spoof a 93450 won't work not in the 93450 and in their 9504 the two drives is only in Play Movie Discs their Slim goes to Hell, i dont take their console yet to see wath i can do but im here seens yours post maybe i can try something to help when i take their console i bake say anything...