Hi all. I could use a little help with a problem similar to the last post about "This disk is not supported", but instead, when I put in my original copy of Halo Anniversary, no picture comes up. It says Play Game. When I hit A to play the game, the screen goes black as if it's loading, but then within 3 seconds, the dashboard comes back on and still says Play Game. When I put my original copy of an older game like The Darkness in, it just says Play DVD. And any backup copy (old or new) I put in also says Play DVD. Basically I read some posts saying that it's just a bad laser, some posts say it just needs to be reflashed, but I did that. This drive was new with very little use before it RROD on me. I left it sit for a year, and finally got it fixed. It had dash 2.0.13599.0 from July of 2011 and worked perfectly before the RROD. I got it back and updated to the current dashboard via USB. I'm aware that it is supposed to revert your drive back to the "new" original firmware. So I went and reflashed it with LT 2.01 for Sammy's. Now, if it's just a bad laser, then I'll replace it. But before I spend the money, I want to make sure that it's not something else. I know this post was pretty long winded, but my question is, was I supposed to read the new firmware that the new dash installed, then inject LT into that? Or is it ok that I used the original firmware that I pulled from the drive back in 2009 that I've been using all along?
Post 13146 Dash Re-Flash Problem
- Thread starter Sayana
- Start date
I didn't save the log, but I also didn't manually load the target. So I will try that tonight. I grabbed the Sammy CFW 2.01 from the firmware package that has all of them in it.
I'm no longer at 13599. Got the 16202 now. Thanks for the help guys. I'll try to reflash tonight when I get home.
I'm no longer at 13599. Got the 16202 now. Thanks for the help guys. I'll try to reflash tonight when I get home.
I have the same exact issue..... tried manually loading the 2.01 firmware but still no good.... any other suggestions?
Well I tried it again 3 times. Each time with the same results. I grabbed a different Sammy drive, and flashed that one back to stock 3 times also, with the same results. On the 4th try flashing LT 2.01...it worked. I really have no idea what I did so I'm still going to post my JungleFlasher results, and maybe someone can figure out what was going on here for anyone else that might be having the same problem. I really don't know why it worked this time. The only thing that I can think of, is the last 2 times, I pulled the stock firmware from a different save location. I saved my firmware in 3 different places (yes I'm that paranoid that I will lose my firmware 
). So maybe one of my firmware backups is somehow bad. Anyway, here's the log and hopefully this will help other people with the same problem.
The first half of the log is the 2nd or 3rd try at the custom firmware that failed. The second half of the log is reverting the second drive back to stock on the 4th and final try which worked. I have blanked out my personal serial info for obvious reasons (no offense...I just would rather not post that in a public forum).
JungleFlasher 0.1.92 Beta (304)
Session Started Mon Jan 01 01:09:18 2001
This is a 32 bit process running on a 32 bit CPU
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 1 Com Ports.
Found 5 windows drives A: C: D: E: F:
Found 1 CD/DVD drives F:
Loading firmware file E:\Documents and Settings\Administrator\Desktop\xbox360\Original Firmware\My Serial\My Serial\SAM-OFW.BIN
MD5 hash: **Private
Inquiry string found
Identify string found
Drive key @ 0x40EC **My Drive Key
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Loading firmware file E:\Documents and Settings\Administrator\Desktop\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LT-sammy-v2.01.bin
MD5 hash: d66252800c1c072bc612f2f72d1e3c76
Genuine LT v2.01
Inquiry string found
Identify string found
Drive key @ 0x4044 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: LT v2.01
Spoofing Target
DVD Key copied to target
ID strings already match
Sending Vendor Intro to port 0x9400
Status 0x51
Re-sending Vendor Intro: ...............................................
Parallel flash found with Status 0x70
Sending Device ID request to port 0x9400
Manufacturer ID: 0xBF
Device ID: 0xB6
Flash Name: SST(SST39SF020)
Flash Size: 262144 bytes
Getting Status from port 0x9400
Parallel flash found with Status 0x70
Writing target buffer to flash
Sending Chip Erase request to port 0x9400
Erasing:............
Writing Bank 0: ................
Writing Bank 1: ................
Writing Bank 2: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ......x....x......
Reading Bank 3: ....x............
Write verified OK !
Key found in KeyDB at record (3 - Samsung_iXtreme_LT_v1.0)
Key is: **My Drive Key
Key has been tested and verified, thanks C4eva ! Drive is Samsung.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Mon Jan 01 01:20:01 2001
This is a 32 bit process running on a 32 bit CPU
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 1 Com Ports.
Found 5 windows drives A: C: D: E: F:
Found 1 CD/DVD drives F:
Loading firmware file E:\Documents and Settings\Administrator\Desktop\xbox360\Original Firmware\My Serial\My Serial\SAM-OFW.BIN
MD5 hash: **Private
Inquiry string found
Identify string found
Drive key @ 0x40EC **My Drive Key
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Sending Vendor Intro to port 0x9400
Status 0x51
Re-sending Vendor Intro: ..........................................
Parallel flash found with Status 0x70
Sending Device ID request to port 0x9400
Manufacturer ID: 0xBF
Device ID: 0xB6
Flash Name: SST(SST39SF020)
Flash Size: 262144 bytes
Loading firmware file E:\Documents and Settings\Administrator\Desktop\xbox360\Original Firmware\My Serial\My Serial\SAM-OFW.BIN
MD5 hash: **Private
Inquiry string found
Identify string found
Drive key @ 0x40EC **My Drive Key
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Spoofing Target
DVD Key already matches
ID strings already match
Getting Status from port 0x9400
Parallel flash found with Status 0x70
Writing target buffer to flash
Sending Chip Erase request to port 0x9400
Erasing:............
Writing Bank 0: .............y...
Writing Bank 1: .....y.....y.....y.
Writing Bank 2: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !
). So maybe one of my firmware backups is somehow bad. Anyway, here's the log and hopefully this will help other people with the same problem.The first half of the log is the 2nd or 3rd try at the custom firmware that failed. The second half of the log is reverting the second drive back to stock on the 4th and final try which worked. I have blanked out my personal serial info for obvious reasons (no offense...I just would rather not post that in a public forum).
JungleFlasher 0.1.92 Beta (304)
Session Started Mon Jan 01 01:09:18 2001
This is a 32 bit process running on a 32 bit CPU
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 1 Com Ports.
Found 5 windows drives A: C: D: E: F:
Found 1 CD/DVD drives F:
Loading firmware file E:\Documents and Settings\Administrator\Desktop\xbox360\Original Firmware\My Serial\My Serial\SAM-OFW.BIN
MD5 hash: **Private
Inquiry string found
Identify string found
Drive key @ 0x40EC **My Drive Key
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Loading firmware file E:\Documents and Settings\Administrator\Desktop\Latest_iXtreme_and_Stock_Firmware_Pack\Firmware\LT-sammy-v2.01.bin
MD5 hash: d66252800c1c072bc612f2f72d1e3c76
Genuine LT v2.01
Inquiry string found
Identify string found
Drive key @ 0x4044 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: LT v2.01
Spoofing Target
DVD Key copied to target
ID strings already match
Sending Vendor Intro to port 0x9400
Status 0x51
Re-sending Vendor Intro: ...............................................
Parallel flash found with Status 0x70
Sending Device ID request to port 0x9400
Manufacturer ID: 0xBF
Device ID: 0xB6
Flash Name: SST(SST39SF020)
Flash Size: 262144 bytes
Getting Status from port 0x9400
Parallel flash found with Status 0x70
Writing target buffer to flash
Sending Chip Erase request to port 0x9400
Erasing:............
Writing Bank 0: ................
Writing Bank 1: ................
Writing Bank 2: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ......x....x......
Reading Bank 3: ....x............
Write verified OK !
Key found in KeyDB at record (3 - Samsung_iXtreme_LT_v1.0)
Key is: **My Drive Key
Key has been tested and verified, thanks C4eva ! Drive is Samsung.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
JungleFlasher 0.1.92 Beta (304)
Session Started Mon Jan 01 01:20:01 2001
This is a 32 bit process running on a 32 bit CPU
portio32.sys Driver Installed
portio32.sys Driver Started, thanks Schtrom !
Found 4 I/O Ports.
Found 1 Com Ports.
Found 5 windows drives A: C: D: E: F:
Found 1 CD/DVD drives F:
Loading firmware file E:\Documents and Settings\Administrator\Desktop\xbox360\Original Firmware\My Serial\My Serial\SAM-OFW.BIN
MD5 hash: **Private
Inquiry string found
Identify string found
Drive key @ 0x40EC **My Drive Key
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Sending Vendor Intro to port 0x9400
Status 0x51
Re-sending Vendor Intro: ..........................................
Parallel flash found with Status 0x70
Sending Device ID request to port 0x9400
Manufacturer ID: 0xBF
Device ID: 0xB6
Flash Name: SST(SST39SF020)
Flash Size: 262144 bytes
Loading firmware file E:\Documents and Settings\Administrator\Desktop\xbox360\Original Firmware\My Serial\My Serial\SAM-OFW.BIN
MD5 hash: **Private
Inquiry string found
Identify string found
Drive key @ 0x40EC **My Drive Key
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Spoofing Target
DVD Key already matches
ID strings already match
Getting Status from port 0x9400
Parallel flash found with Status 0x70
Writing target buffer to flash
Sending Chip Erase request to port 0x9400
Erasing:............
Writing Bank 0: .............y...
Writing Bank 1: .....y.....y.....y.
Writing Bank 2: ................
Writing Bank 3: ................
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !
Hello Cuzzin_al,
when you say stock is that the stork firmware from the firmware pack or the dump you took of your drive after the dash update?
I flashed back to stock using the firmware pack (from xbins) to see if that made a difference but I have the same problem still.... all of it does not make sense at the moment ive flashed 50 odd drives and I've never seen this before?
Mantis
when you say stock is that the stork firmware from the firmware pack or the dump you took of your drive after the dash update?
I flashed back to stock using the firmware pack (from xbins) to see if that made a difference but I have the same problem still.... all of it does not make sense at the moment ive flashed 50 odd drives and I've never seen this before?
Mantis
By stock, I'm talking about the dump I took off of the drive even before I upgraded the dash. But either way, yes, it's the firmware you get from the drive itself. I'm actually not familiar with using the firmware pack to revert your drive back to stock because you still need the key tied to that motherboard. I too have flashed so many drives, but I've been away from it for about a year now. But whatever I did, it's been working great for originals and backups without any trouble. I wish I knew what I did so I could help you. Why don't you try again, then post your JF log in this thread as well. If nothing else, it will give people the opportunity to compare your log to mine, and maybe someone will see something that you're missing.