DG16D4S Drive (360 Slim Drive)

[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!!

 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.

 

No no Dexter, I was talking just for test purpose, like I said I did not tested it yet.

One thing is sure, the real spoof does not has anything related to this, the real cause is the inquiry data stored inside the nand!! This I can guarantee. Cheers!!

[morenomdz]

One thing is sure, the real spoof does not has anything related to this, the real cause is the inquiry data stored inside the nand!! This I can guarantee. Cheers!!

Easy to solve, lets start dumping every console´s nand before swapping drives in!

/sarcasm off

T_T

[johnsmith]

Insert a big laugh here...

People who bought the slim already modded with a mutilated drive can start to cry now.
Drive seens to work firne for a couple of days then.. Play DVD.

Got a 5 days old slim in this situation and it only played Lego batman, cod2 and pure.

Poor guys that doesn't have their original drives. And I meant it.

Falow Marcelo da Fera's.. te avisei..

@morenomdz: erm... it's no good. No cpu key, no kv access. Inquiry is prolly stored in keyvault. :p

[xstationbr2]

Insert a big laugh here...

People who bought the slim already modded with a mutilated drive can start to cry now.
Drive seens to work firne for a couple of days then.. Play DVD.

Got a 5 days old slim in this situation and it only played Lego batman, cod2 and pure.

Poor guys that doesn't have their original drives. And I meant it.

Falow Marcelo da Fera's.. te avisei..

@morenomdz: erm... it's no good. No cpu key, no kv access. Inquiry is prolly stored in keyvault. :p

Hey! Stop to say bull$#!t, these problems happens only with any Slim consoles!  Jasper  another way have a new problem too Called  Gray Screen with the Error ( Please insert your disc with System update
Code: C200 - 58D0 - 1003 - E290 - 0013 ) when you use system update in any Jasper mother board. If you windows was buged or using a antvirus or Win 7 the inquiry comes corrupeted anytimes dvdkey too, but compared to Jaspers in the Gray Screen is a New Hell to discover solution. GRAY SCREEN = XBOX BRICKED My Pricipal Xbox Slim Vejle 250 Gb was in the 126.0.11 running like a hell, with a Benq VAD-6039 in LT + 1.0 and my Old Xbox Slim 250gb Vejle was with LG running all fine, well if you think the Slim Vejle is not good for you. Good Lucky For You Brasil é Tudo De Bom.

[johnsmith]

xstationbr2: It's kinda hard to figure out what you're trying to say but i'll try to reply.

I didn't modded ANY slim. They were bought to me.
I have 3 here with the same problem (Play DVD-Video)
All the 3 come from PY previously modded.
One has a BenQ drive the other two have LiteOns 7xxx just key was inserted, no spoofed whatsover and yes, they were working fine... till now. One of them still in 9199 dash.

What did you said about jaspers?

[morenomdz]

Hes saying that some jaspers are failling to update from the game disc and going bricked but I did not see a single one that I wasn't able to recover yet.

Now about the play dvd issue, the only one I saw with that issue was updated online, was working fine for days and now it only accepts the original drive, so yea, good game for that one.

[Yntialan]

[/quote]

Hey! Stop to say bull$#!t, these problems happens only with any Slim consoles!  Jasper  another way have a new problem too Called  Gray Screen with the Error ( Please insert your disc with System update
Code: C200 - 58D0 - 1003 - E290 - 0013 ) when you use system update in any Jasper mother board. If you windows was buged or using a antvirus or Win 7 the inquiry comes corrupeted anytimes dvdkey too, but compared to Jaspers in the Gray Screen is a New Hell to discover solution. GRAY SCREEN = XBOX BRICKED My Pricipal Xbox Slim Vejle 250 Gb was in the 126.0.11 running like a hell, with a Benq VAD-6039 in LT + 1.0 and my Old Xbox Slim 250gb Vejle was with LG running all fine, well if you think the Slim Vejle is not good for you. Good Lucky For You Brasil é Tudo De Bom.
[/quote]


this happens with any system upgrade? im doing updates using AC brotherhood and still nothing happened here. including jaspers MB.

[DeXteR_CwB]

Hey! Stop to say bull$#!t, these problems happens only with any Slim consoles!  Jasper  another way have a new problem too Called  Gray Screen with the Error ( Please insert your disc with System update
Code: C200 - 58D0 - 1003 - E290 - 0013 ) when you use system update in any Jasper mother board. If you windows was buged or using a antvirus or Win 7 the inquiry comes corrupeted anytimes dvdkey too, but compared to Jaspers in the Gray Screen is a New Hell to discover solution. GRAY SCREEN = XBOX BRICKED My Pricipal Xbox Slim Vejle 250 Gb was in the 126.0.11 running like a hell, with a Benq VAD-6039 in LT + 1.0 and my Old Xbox Slim 250gb Vejle was with LG running all fine, well if you think the Slim Vejle is not good for you. Good Lucky For You Brasil é Tudo De Bom.
[/quote]


this happens with any system upgrade? im doing updates using AC brotherhood and still nothing happened here. including jaspers MB.
[/quote]

 I found no problem with Jasper or any Fat, i already updated a lot of this with LT+ and all works fine with dash 12611.

 Only if you use an Disc with a different wave from the original.

[xstationbr2]

[/quote]


this happens with any system upgrade? im doing updates using AC brotherhood and still nothing happened here. including jaspers MB.
[/quote]

[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.

 

No no Dexter, I was talking just for test purpose, like I said I did not tested it yet.

One thing is sure, the real spoof does not has anything related to this, the real cause is the inquiry data stored inside the nand!! This I can guarantee. Cheers!!

 Uff. I updated to 12611 ( by live ) and everything is ok, both drives still working.

 Xval show me Secdata is Clean

[morenomdz]

LOL Stop with the quoting $#!t fest please!

[ZerOneX]

@ Dexter, wait wait, i did not understood one thing!!

We are discussing about those consoles that just stopped working after update from 9199 to 12XXX

1) this is not happening with all slim consoles, there is a lot Xbox 360 S working fine after update, with geremia patch applied or not

2) for those that are not working anymore, the main suspect is this inquiry data protection.

Could you do one big favor for us??

On your slim that is running smooth, could you swap the drives again by the original one, to see with the Xbox will recognize it??!!!

Thanks man.

[DeXteR_CwB]

@ Dexter, wait wait, i did not understood one thing!!

We are discussing about those consoles that just stopped working after update from 9199 to 12XXX

1) this is not happening with all slim consoles, there is a lot Xbox 360 S working fine after update, with geremia patch applied or not

2) for those that are not working anymore, the main suspect is this inquiry data protection.

Could you do one big favor for us??

On your slim that is running smooth, could you swap the drives again by the original one, to see with the Xbox will recognize it??!!!

Thanks man.

 Let me see if i understand your question.

 You want to know what happens if i put the original drive again on the console with error PLAY DVD? Or put the original drive again on the console thats working fine with the old lite-on?

 If i put the original drive again on the console that's working fine, the console will recognize that is original again and only original disc's will work, i know you know this. :b

 I do not have any console with the error "PLAY DVD" here to know what will happens if i put any original drive again. Because i received on my store to try to make working again ( without sucess ), but my client has already picked up the console again.

 Honestely, at the moment, i do believe the most important is know what happened or the mistake made before get error PLAY DVD, i do not believe that the microsoft shipped different models of slim. That's is my opinion of course.

[Pacote-san]

I told every single client who asked my on Messenger if it was a good ideia to buy a slim already unlocked... i said to everytime DONT FUC^#% do it unless you got the original drive with it too!

Any other way and you are going to regret in the future and thats what im seeing the last few weeks.... LOL

PY f***ing hard brazilian customers

[morenomdz]

PY f***ing hard brazilian customers since 1980

Fixt.

[chriswiegand]

F :oCK the inquiry - only put the Original Signature from the tarablinda.bin into the 93450 LT1.1. Then spoof the signatured 1.1 to a lt+ - works on my slim with latest dash !
Sold for $460 !
Cheers.

[XBOX360user]

F :oCK the inquiry - only put the Original Signature from the tarablinda.bin into the 93450 LT1.1. Then spoof the signatured 1.1 to a lt+ - works on my slim with latest dash !
Sold for $460 !
Cheers.

Can you please explain little bit ...
tarablinda.bin ( did you talking about dummy.bin  or fulldump.bin ? )
Did you put Original signature with Hexeditor or ?
How did you manage to spoof signatured 1.1 to a lt+ , jungleflasher don't open maually signatured files

[petas]

hallo everybody...i need some help...i try to take the key from my slim,i have read every post i try everything but i nothing....tarablinda starts and give me that:
unlocking...Error bit after ATA packet.Wrong CDB command!
Error 4:fail to send unlock cmd!Sense 05/55/00
drive unlock failed.
i try it on seven x64  on seven x32 and now on xp nothing,iall the time the same thing...ive  tryed shange sata cable nothing,ports nothing,jungle flasher see the port all good.im trying 4 days now...somebody help.....thank you....

[iateshaggy]

this is a forum for posting your successes, not questions about your failures.

[xstationbr2]

hallo everybody...i need some help...i try to take the key from my slim,i have read every post i try everything but i nothing....tarablinda starts and give me that:
unlocking...Error bit after ATA packet.Wrong CDB command!
Error 4:fail to send unlock cmd!Sense 05/55/00
drive unlock failed.
i try it on seven x64  on seven x32 and now on xp nothing,iall the time the same thing...ive  tryed shange sata cable nothing,ports nothing,jungle flasher see the port all good.im trying 4 days now...somebody help.....thank you....

Back to first page of this Tread, your aks, says you don't do this.
If you back to start of this tread you can able to dump correctly you Slim.
TIP: Dont use JF .
I don't answer you another questions.