Print

[kiwimods]

QUOTE(halleluia @ Oct 8 2009, 01:03 AM)

Not even news saying that the team is working on this??  

People are working on this don't worry. "giggidy giggidy goo" Glenn Quagmire

[logicwatch]

QUOTE(UnnA^ @ Oct 7 2009, 11:47 AM)

A July drive should flash perfectly fine. This issue seems to be with SOME August's and later. I would keep trying if i were you as your probably doing something wrong. There have been no cases of a July drive failing...

agreed stock from pre august should be ok  ? however working in the retail industry  I do know that the new
elites without hdmi are brand new stocks for the uk and we have only received them within the last few weeks so perhaps these are infact the new firmware ??

[99joe]

QUOTE

A July drive should flash perfectly fine. This issue seems to be with SOME August's and later. I would keep trying if i were you as your probably doing something wrong. There have been no cases of a July drive failing...

Em.. yes there is. I'm sitting with it.
My m8 is pretty much like the op of this thread. He's flashed hundreds of lite on's. He can't get the key. I can't get the key. The drive gives the exact same as the op.
Jungle flash can't get it. Simple as. Even with ck3 it can't be extracted. I'm waiting for the supposed fix like every one else.


Nice to know people here take you at your word   .


Oh, and well seeing none of you have worked on a production line or in a factory before or you'd understand WHY some work and some don't.
Ever see stock and components that have sat for a while being used at a later point to fill a gap? DUH.

[robo989]

QUOTE(99joe @ Oct 7 2009, 03:41 PM)

Em.. yes there is. I'm sitting with it.
My m8 is pretty much like the op of this thread. He's flashed hundreds of lite on's. He can't get the key. I can't get the key. The drive gives the exact same as the op.
Jungle flash can't get it. Simple as. Even with ck3 it can't be extracted. I'm waiting for the supposed fix like every one else.
Nice to know people here take you at your word   .
Oh, and well seeing none of you have worked on a production line or in a factory before or you'd understand WHY some work and some don't.
Ever see stock and components that have sat for a while being used at a later point to fill a gap? DUH.

It is you who needs to do some reading.

1. We don't give a damn what your mate has done.

2. You've only got 2 posts to your name and registered recently.

3. All reports so far and there's a fair few point to july models being fine.

4. We understand fully how they are made on a production line in the context of which drives are used. There are batch numbers on boxes which show what factory they were made in. All boxes of the same batch number have the same components in.

5. The different firmware revisions are programmed near the END of the production process, firmware is SOFTWARE so it doesn't sit around as you seem to think.



Yep, think that's enough to pretty much make you look very silly.

[99joe]

QUOTE

however working in the retail industry I do know that the new
elites without hdmi are brand new stocks for the uk and we have only received them within the last few weeks so perhaps these are infact the new firmware ??

Nice to know... doesn't make me feel any better though ...
On the bright side, hopefully this one doesn't go down as easy as my last two.


I don't think the issue here is the firmware. It shows the same firmware revision because it probably is the same revision. I think the op of this thread and a few others hit the nail on the head. I think they've just changed the encryption key.


Here's something I posted at team xecuter. Hopefully it will explain the production line side of things better for the kids and thickity thicks on this thread.

QUOTE

Nope, this one is July 2009 and it def is the same problem as the op on that thread at XBS. It's sods law and the rule of the production line. How many lines do microsuck have manufacturing these? If one is handed new components, do you think they just ditch thousands of dollars worth of components to bring in the new? Would microsucks agree to the loss of thousands of dollars just to stop someone flashing there firmware? No. NO, NO, NO, NO.
The lines would either finish using the components they have before moving on to the newer ones or they would stick the older components in reserve and pull them out when there short of quota. Hence the reason why some August ones work and some dont and why I've got one thats dated July 2009.

Like I said, it's sods law. I've got one of the first ones.

Why do I know all this? I spent 12 years working for compaq and ibm manufacturing pc's, servers, barebone systems and scanners. I know in intamate detail how these lines work.

Oh, and to word all that above better, microsucks or the drive manufacturers wouldn't waste the components.

[99joe]

QUOTE

1. We don't give a damn what your mate has done.

Well WOOPTY DOO.

QUOTE

2. You've only got 2 posts to your name and registered recently.

Yeah, and thank god with prats and nay sayers like you.

QUOTE

3. All reports so far and there's a fair few point to july models being fine.

And that means there all fine...  

QUOTE

4. We understand fully how they are made on a production line in the context of which drives are used. There are batch numbers on boxes which show what factory they were made in. All boxes of the same batch number have the same components in.

Well maby some people should try to excersise that knowlege a little.

QUOTE

5. The different firmware revisions are programmed near the END of the production process, firmware is SOFTWARE so it doesn't sit around as you seem to think.

And what about all this makes you so adamant that this is to do with the firmware? After all the firmware in use is the same as in drives that do dump there keys...

QUOTE

Yep, think that's enough to pretty much make you look very silly.

You wish robofag. Go drop your gonads and get a life.

[99joe]

Another thing.

QUOTE

5. The different firmware revisions are programmed near the END of the production process, firmware is SOFTWARE so it doesn't sit around as you seem to think.

That only applys to the drive manufacture. Remember these drives are custom talored for the 360. So the actual build of the 360 involves a certain amount of prebuilt components which are stocked by the variouse factories in there thousands.

About the only thing the microsuck guys are doing is locking it to the hardware.

[Ranger72]

Both of you need to quite arguing and keep on topic.

A mod needs to clean this mess up and keep this thread open so that if and when new info becomes available there will be a good place to post it.

[KingKapalone]

QUOTE(KingKapalone @ Oct 7 2009, 12:17 AM)

I have a new holiday bundle elite and this is my first flash, but I might have the new firmware also. I just have a question about an error message.

I have 64-bit Vista so JF 1.66 doesn't detect the drive because I can't install portIO. I ran DosFlash64 from DosFlash 1.8 instead and it detected the drive. I then tried to do the Lite-On Read Key method. I don't have the Connectivity Kit, so I followed the JF guide instructions about pulling the drive's power cable as it's closing to get the halfway open state. I then did Step 2 of just closing and opening the drive. I then got an error saying the data from my drive was invalid.

Is that the error people get when they have the new firmware or did I not get the drive halfway open correctly? I did this twice and I can't remember entirely, but I think the first time I did it I got an error that said something along the lines of "Can't read key" which would make me think I have the new firmware.

I'm quoting myself from the last page.

I'm just wondering if the errors I'm getting in DosFlash are because I'm not getting the tray at halfway or if it's because I have the new firmware. I'm posting here because the people here might know as they are attempting to flash their new firmware as well. Anyone get similar errors in DosFlash?

[dougiegillam1357]

What is the manafacturing date on drive and the console plus the F/W revision number that is on the drive?

[KingKapalone]

QUOTE(dougiegillam1357 @ Oct 7 2009, 11:29 AM)

What is the manafacturing date on drive and the console plus the F/W revision number that is on the drive?

It's an August 2009 Lite-on from an 08/12/2009 360. It has the 83850c firmware. I know lots of the August drives are the new ones, but some people are getting them with the old f/w. This is my first flash, so I don't know if DosFlash is failing because I'm doing the Read Key method wrong or if it's because it's new.

[dougiegillam1357]

There a good possibility you do have the new f/w with that date, having said that theres no way tell for sure. First thing first DOS64 isnt the best way to go, i'm sure that there people out there that have used that to read and flash 83850c drive but I cant say ive seen any such posts. The best way for you to tell is to use a program called iprep 10.7 which makes a bootable USB stick for you, that way you will be able to boot into true dos not dos64 which uses the cmd prompt within windows. Now having said all that you couldnt have picked a harder method for powering the drive, the 360 can be used but requires you to be quick when powering the drive back on/off ( ithink if i remember about 3 seconds) you should also plug the av lead into the 360 as this will make it a bit easier. One last thing is what sata chipset are you using? Below is the link to where you can download iprep and there's also a video tutorial on the site, but i reccomend you follow this tutorial instead. One last thing to mention is I always push the tray a tad more than half way in.

http://www.youtube.com/watch?v=jfYpOer_-tk


http://www.klutsh.com/

Hope this helps

[KingKapalone]

QUOTE(dougiegillam1357 @ Oct 7 2009, 12:53 PM)

There a good possibility you do have the new f/w with that date, having said that theres no way tell for sure. First thing first DOS64 isnt the best way to go, i'm sure that there people out there that have used that to read and flash 83850c drive but I cant say ive seen any such posts. The best way for you to tell is to use a program called iprep 10.7 which makes a bootable USB stick for you, that way you will be able to boot into true dos not dos64 which uses the cmd prompt within windows. Now having said all that you couldnt have picked a harder method for powering the drive, the 360 can be used but requires you to be quick when powering the drive back on/off ( ithink if i remember about 3 seconds) you should also plug the av lead into the 360 as this will make it a bit easier. One last thing is what sata chipset are you using? Below is the link to where you can download iprep and there's also a video tutorial on the site, but i reccomend you follow this tutorial instead. One last thing to mention is I always push the tray a tad more than half way in.

http://www.youtube.com/watch?v=jfYpOer_-tk
http://www.klutsh.com/

Hope this helps

My friend also suggested using DosFlash 16 and making a bootable DOS USB stick. He said he doesn't like iprep, but I'm not totally against it.

I imagined lots of people aren't using connectivity kits now with the 83 firmware because it's not necessary. Is that not the case?

I'm using my onboard SATA from my Abit IP35 Pro motherboard. That is an Intel ICH9R chipset.

When trying to get the drive tray at halfway, is it ok to pull it back out to halfway if when I pulled the plug it was at about 1/4 of the way?

[wlintek]

i've got the same problem here. the drive comes from the xbox that has just been sent back from repair centre. have tried everything still can't dump the key, but no problem doing the same in the past. pictures attached for those interested. cheers

[AbsoluteZeroInc]

QUOTE(UnnA^ @ Oct 7 2009, 06:47 AM)

A July drive should flash perfectly fine. This issue seems to be with SOME August's and later. I would keep trying if i were you as your probably doing something wrong. There have been no cases of a July drive failing...

I have  a July drive that will not read as well, I think i've done everything right, I posted it early in this thread.

Thanks,

AbsoluteZero