Can't re-flash after update

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
I, like many, suffered the update kill and my drive is now hosed. I have a Lite-On 9345. I previously had someone flash it for me from stock to 1.1 LT+. He sent me the dummy.bin file in case I'd ever want to re-flash the drive myself. Since I can't get to my dash I just wanted to re-flash back to 1.1. Figured I could flash to a newer version once I get back on my feet. Upon having this situation happen I opened JF, connected my drive, saw the drive, placed the dummy.bin as my source, set the 1.1 firmware as the target, and went through the process. Everything seemed to work but when I get to the last step, doing the Outro, I don't see the DVD Key found. The drive appears to stay in vendor mode.

Is there a step I'm missing that I need to add since the update hosed the drive from what it was (and the dummy.bin file is associated with)? Help!:duh:
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
So I basically need to start anew and get a probe? I noticed you had some extra steps involved, like updating the dash from USB. Is that something I should do? I'm really kind a green at this. Can't you tell? :rolleyes:
 

tempora97

Full Member
Sep 28, 2003
87
0
Well, I put in a wave13 game and in turn it started to do the dashboard update, but 1/2 way thru it stopped reading the media (thanks MS). So I was caught in the update loop. Downloaded update to USB media, inserted, finished update, got to dashboard and then probed and reflashed.
 

philou74000

Console Guru
Dec 6, 2003
632
0
If that fails, I find updating the drive straight to lt1.91 and then updating usually gets past the part where it crashes. I've done this on 17 consoles over the last couple of weeks and it's worked everytime.
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
Is it possible to flash to 1.91 from the dummy.bin as the source file with the drive in the state of flux it's in (crapped out in mid update from the game)?
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
Okay, here's a detailed recount of what I'm doing.

Startup JF – the drive is recognized.
View attachment 193

Load the dummy.bin file you sent as the source, load the orig-93450C.bin file as the target since my drive is displaying as the 93450 drive and I’m assuming my drive has not been flashed to the 0251 version. I would think if it were it would be reflected as the F/W Rev in Drive Properties, no?
View attachment 194

Everything appears to match (Model, Rev, OSIG).

If I try to use the Post_13141 OFW I see this:
View attachment 195
The Rev and OSIG don’t match, not to mention the DVD Key looks very wrong.

So I proceed with the Pre OFW, hit the Spool Source to Target:
View attachment 196
Everything looks like it copied properly according to the log. My DVD Key matches now.

I then go to MTK Flash 32. Click on Lite On Erase.
View attachment 197
Everything looks good. The Flash Chip Properties are correct. The Log matches. Then I click Write. To be continued...
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
View attachment 198
Write verified OK. Still think everything is on track. So I click Outro / ATA Reset.
View attachment 199

DVD Key is not found and there’s no confirmation in the log. The drive power light is still blinking too, indicating it’s still in vendor mode. This is where I’m stuck. I don’t know why it’s not completing. Could it be an issue that the Dummy.bin file is no longer accurate and I need to get a new dump from my drive? I'm desperate!
 

ReMix

Console Freak
Nov 4, 2003
3,138
0
that looks normal to me weaponx

it looks like you had a successful flash

what happens when you plug it up to the xbox and try to update?
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
When I hooke the Xbox back up to the TV and turn it on it immediately goes to the screen where's stuck on the update midway. Should I update via USB at that point?

I would have thought I'd see my DVD Key found if the flash had been successful, no?
 

ReMix

Console Freak
Nov 4, 2003
3,138
0
When I hooke the Xbox back up to the TV and turn it on it immediately goes to the screen where's stuck on the update midway. Should I update via USB at that point?

I would have thought I'd see my DVD Key found if the flash had been successful, no?
yes, at that point insert the flash drive
 

nputra

Junior Member
Sep 2, 2003
16
0
You don't have to dump the firmware again, you can use dummy.bin from your old dump providing its good dump.
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
Okay, apologies if this is redundant and overtly thick of me. Trying to follow the adage "measure twice, cut once" before I hose something.

So, at this point I update to the latest drive via USB (which is 13599). After update is good I can hook backup to JF and flash, using my dummy.bin as source and LT 1.9 as Target. Sound correct?
 

GodZilla

Console Freak
Oct 31, 2003
3,682
0
yes - ensure you decline the autoload as your dummy is pre-dash. Then manually load the target buffer and press "spoof source to target" this will ONLY copy your key over! - (which is correct). then LOerase and write
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
No dice. I downloaded the update from MS onto a thumb. Unzipped it's a folder called $systemupdate. I can only assume that's the correct files. Plug that in to the console, fire it up, and it tries to update, only to go right back to the SOB "can't update...." msg. Should I maybe try setting my source file as orig-0251C-1c000.bin in the LiteOn_Post_13141\OFW folder, set the LiteOn_Pre_13141\OFW\orig-93450C.bin as my target and then spoof source to target? Then try the USB update? I'm missing something!
 

rgoodcld

Full Member
Jan 14, 2004
29
0
Central Florida
I set my dummy.bin as source and try to auto load the target. I get an error message that it can't because it can't find the LT 1.1 firmware I was originally trying to use. I had that bin file in my jungleflasher\firmware folder originally. I took it out and put in the LT 1.91 bin before trying this, however it's still only looking for that 1.1 file. So I loaded the file manually. I noticed the drive model doesn't match, which I believe jungleflasher is saying can't be. I hit the spoof keey to make the keys match. I then tried to erase and got this error:
View attachment 200

I stopped there, fearing that would be a bad move. I'm stumped.:mad: