Topic: Maybe A New (new) 83850c Firmware Out (Read 2609 times)

xbox360sexual · « **Reply #105 on:** October 06, 2009, 10:36:00 AM »

QUOTE

DVD key found @ 0xA030 key is E8676DB76042D25B18CFF6DD94A8AXXX

Looks like a valid key.. I assume you've "xxx"'d out the last digits, and that when you load the dummy.bin JF prompts you to spoof over to the ixtreme f/w, then you "save target as" lite_cfw.bin

acDCuk · « **Reply #106 on:** October 06, 2009, 11:01:00 AM »

can we please stay on topic?

xbox360sexual · « **Reply #107 on:** October 06, 2009, 11:05:00 AM »

Fair point, but acDCuk until you have moderator permissions or are an owner of the site, please don't PM me telling me to leave the thread. thanks

Frawgg · « **Reply #108 on:** October 06, 2009, 12:42:00 PM »

Just got a box back today from the repair center.

Firmware Revision 8385 in JungleFlasher.

Dumped it like I normally would dump these drives.

Get the same error that Kiwi gets. I've tried everything.

Oh I live in the States by the way. PA to be exact.

janaro78 · « **Reply #109 on:** October 06, 2009, 02:51:00 PM »

QUOTE(xbox360sexual @ Oct 6 2009, 06:36 PM)

Looks like a valid key.. I assume you've "xxx"'d out the last digits, and that when you load the dummy.bin JF prompts you to spoof over to the ixtreme f/w, then you "save target as" lite_cfw.bin

Hi, yes the XXX is me (IMG:style_emoticons/default/smile.gif)

Yes it looks good and the 1.66 tutorial said it was fine, that's where it went all wrong. Just for anybody who might come into the same issue as I did (bricking your 83850C): There is another tutorial out there specifically for the 83850C.

The key I have is apparently encrypted and will never work as it's a "fake". There are many programs out there and even JF has the option (very unclear in tutorial 4 me), so please please get your D609CG925914001NS.bin before bricking it like I did. I'm gonna see if MS will fix it (automatic ban I believe) or see what chip extraction method comes out.

Hope this helps anybody out there and thanks for your answers and I apologies for posting in the wrong area. I thought "Replying to Maybe A New (new) 83850c Firmware Out" was good....

lagerhowen · « **Reply #110 on:** October 06, 2009, 02:53:00 PM »

I got 2 back from M$ yesterday... I had to read about the 83850c fix after wondering why my probe
couldn't find anything at R707, it got hot as hell and BSOD my PC. JF worked great no problems on
the 1st one. Now, this next one has August 2009 83850c I have tried everthing but no go. I used
lo83info_32.exe and JF on same exact machine just 5 min after 1st one was successful, so its not
me or my PC. I tried like 30x.

Lets hope theres a fix soon. I'm in California btw

OggyUK · « **Reply #111 on:** October 06, 2009, 03:38:00 PM »

QUOTE(janaro78 @ Oct 6 2009, 09:51 PM)

Hi, yes the XXX is me (IMG:style_emoticons/default/smile.gif)

Yes it looks good and the 1.66 tutorial said it was fine, that's where it went all wrong. Just for anybody who might come into the same issue as I did (bricking your 83850C): There is another tutorial out there specifically for the 83850C.

The key I have is apparently encrypted and will never work as it's a "fake". There are many programs out there and even JF has the option (very unclear in tutorial 4 me), so please please get your D609CG925914001NS.bin before bricking it like I did. I'm gonna see if MS will fix it (automatic ban I believe) or see what chip extraction method comes out.

Hope this helps anybody out there and thanks for your answers and I apologies for posting in the wrong area. I thought "Replying to Maybe A New (new) 83850c Firmware Out" was good....

No, JF decrypts it for you now thanks to the implementation of Seacrests fantastic OpenKey. You dont need the [BARCODE].bin any more, thats the old, manual method.

I suggest you source a replacement drive and test your key in that.

Its highly unlikely your data was obtained, and corrupted with 2 identical dumps over Sata.

Less panic, more logic.

KingKapalone · « **Reply #112 on:** October 07, 2009, 01:17:00 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.

janaro78 · « **Reply #113 on:** February 03, 2020, 01:02:00 AM »

QUOTE(OggyUK @ Oct 6 2009, 11:38 PM)

No, JF decrypts it for you now thanks to the implementation of Seacrests fantastic OpenKey. You dont need the [BARCODE].bin any more, thats the old, manual method.

I suggest you source a replacement drive and test your key in that.

Its highly unlikely your data was obtained, and corrupted with 2 identical dumps over Sata.

Less panic, more logic.

Thanks, I try a drive switch...but it does seem that key isn't right (the xbox was already open when I got it, but I didn't try it before I flashed)

99joe · « **Reply #114 on:** February 03, 2020, 03:01:00 AM »

I've got one here. Bought it from a tesco store in the uk, less than a week ago. Brand spanking new black elite. No hdmi cable. New box. Was a "special" offer. Elite console plus 2 games for £198.

Drive is liteon dg-16d2s-09c.
Firmware revision 83850c.
Hardware version a0a2.
Manufacture date july 2009.

Can't get the key using jungle flasher or ck3. I've tried for hours. My m8's tried for hours as well. We've used a plathora of hardware and every known method. No joy.

Oh, and a guy who runs a local mod/repair center wouldn't touch it with a barge pole. Said he's seen 4 of these in the past month. He couldn't get any of them.

This post has been edited by 99joe: Yesterday, 11:05 AM

UnnA^ · « **Reply #115 on:** October 07, 2009, 04:47:00 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...

halleluia · « **Reply #116 on:** October 07, 2009, 06:03:00 AM »

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

xbox360sexual · « **Reply #117 on:** February 03, 2020, 05:04:00 AM »

QUOTE(halleluia @ Oct 7 2009, 01:03 PM)

Not even news saying that the team is working on this?? (IMG:style_emoticons/default/uhh.gif)

Read the thread, you'll see that I've quoted C4E saying that he's working on the new 83850c.

halleluia · « **Reply #118 on:** February 03, 2020, 07:02:00 AM »

QUOTE(xbox360sexual @ Oct 7 2009, 05:34 PM)

Read the thread, you'll see that I've quoted C4E saying that he's working on the new 83850c.

Dude I saw that but you know... (IMG:style_emoticons/default/biggrin.gif)

squeakh · « **Reply #119 on:** February 03, 2020, 07:18:00 AM »

QUOTE(xbox360sexual @ Oct 7 2009, 01:04 PM)

Read the thread, you'll see that I've quoted C4E saying that he's working on the new 83850c.

did he say that in a forum somewhere, if so could you please link to the thread?

QUOTE(xbox360sexual @ Oct 7 2009, 01:04 PM)

Read the thread, you'll see that I've quoted C4E saying that he's working on the new 83850c.

did he say that in a forum somewhere, if so could you please link to the thread?

Author Topic: Maybe A New (new) 83850c Firmware Out (Read 2609 times)