Samsung MS28 Strange Flash?

[foodang36]

First off hello to everyone. Ive lurked here for a bit and Ive learned everything and anything Ive ever wanted to know about flashing from this site. Big thanks to the admins and those that have made the tutorials.

Heres my strange flash problem. I bought a 360 off a friend of mine. He hasnt played it in over a year but said it works fine. I hooked it up and played madden for a minute(worked fine) then took it home to flash.

Its a stock virgin Samsung ms28
I used JF 1.59
and I flashed the drive to IX 1.6

Every thing worked fine and I backed up my key and firmware


Once it got to the Flash Verification Test, bank 1 came back like this
Flash Verification Test !
Reading Bank 0: ................
Reading Bank 1: ...........x.....
Reading Bank 2: ................
Reading Bank 3: ................
Write verified OK !

The x bothered me but I figured if it verified I was fine, so I sent the outro. I hooked it up and It started to play my original copy of madden, then at the start screen it got glitchy or pixelated and froze. Then I tried 2 back ups and they worked fine. Then I tried another original game and it froze after a little bit.

I stepped away and went to dinner with some friends for an hour. I came home and tried all the disks again and everyone worked fine. I tested one original copy for 30 mins.

The only thing I can think of is that either this xbox is on its way to a E74 error and it was just a coincidence with the games first time around, or the bank 1 flash verification is a problem and I need to re-flash. Should I have used JF 1.64 since I was flashing IX 1.6 fw. Would that make much of a difference

Heres my JF log
JungleFlasher 0.1.59 Beta

Session Started Tue Jul 14 18:16:57 2009




This is a 32 bit process running on a 32 bit CPU

PortIO is installed and running.

Found 4 I/O Ports.

Found 0 Com Ports.

Found 9 windows drives.

Found 2 CD/DVD drives.





Sending Sammy_Un_Lock to Drive on port 0xDC00

Stage 1, Complete!

Stage 2, Complete!

Stage 3, Complete!

Done!

Sending Vendor Intro

Requesting Device ID

Manufacturer ID: 0xBF

Device ID: 0xB6

Flash Name: SST(SST39SF020)

Flash Size: 262144 bytes



Getting Status from port 0xDC00

Parallel flash found with Status 0x70



Reading Bank 0: ................

Reading Bank 1: ................

Reading Bank 2: ................

Reading Bank 3: ................



Samsung Dump file saved to L:\Documents and Settings\Admin\Desktop\360 Drives\Samsung 6R5L978432\SAM-OFW.bin



Loading MTK_Flash source file

Inquiry string found

Identify string found

DVD key found @ 0x4116 key is 7CCB135548154E5C14719B614228463F

Firmware is Samsung OSIG: TSSTcorpDVD-ROM TS-H943Ams28

Firmware type is: Stock



Loading target file L:\Documents and Settings\Admin\Desktop\360 Tools\Samsung 1.6 firmware\ix16-samsung.bin

Target File MD5 hash is: 23f5a368839dfc10dabb8231ba64567a

Inquiry string found

Identify string found

DVD key found @ 0x40EC key is 77777777777777777777777777777777

Firmware is Samsung OSIG: TSSTcorpDVD-ROM TS-H943Ams28

Firmware type is: iXTREME1.6-12x-FINAL-TS-H943A



Spoofing Target

DVD Key copied to target

Inquiry strings identical

Identify strings identical

Key data saved to L:\Documents and Settings\Admin\Desktop\360 Drives\Samsung 6R5L978432\Key.bin





Getting Status from port 0xDC00

Parallel flash found with Status 0x70

Writing target buffer to flash

Erasing Bank 0: ................

Writing Bank 0: ................

Erasing Bank 1: ................

Writing Bank 1: ................

Erasing Bank 2: ................

Writing Bank 2: ................

Erasing Bank 3: ................

Writing Bank 3: ................



Flash Verification Test !

Reading Bank 0: ................

Reading Bank 1: ...........x.....

Reading Bank 2: ................

Reading Bank 3: ................

Write verified OK !



Sending Vendor Outro to port 0xDC00

[HaGGardSmurf]

Nope wouldnt have made much of a difference.

I had this same error when I was dumping my ms28... Got an x, that should not effect your drive at all since that was while reading, and not writing.

Also, i think it tried to read a specific location in bank 1, and it failed, so it had an x, then it retried and it succeeded...

All your banks have 16 dots, but bank 1 has 16 dots with 1 x. So that seems to be that it tried to read whatever part of the FW, and failed so it gave you an x, then it retried and it read it fine, so it put a dot.

I think
dots = good
x = bad.
16 dots = read successful
anything less than 16 dots with 1 or more x's should = bad dump

Just my thinking.. Im not exactly sure. If your drive plays backups & originals, you have a good key and the drive has been spoofed correctly.

Nothing really to worry about, just keep this as your OFW.

[foodang36]

I didnt even notice the extra dot on the bank with the x. What you are saying does seem to make sense. I dont know what was up with it freezing on my 2 original copies when I first tried it out. Its seems to be playing originals and back ups just fine now. Like I said in the topic...strange.

I was mainly worried that it might be writing some corrupt data to the 1st bank, which might have been causing issues.
Good eye man and thanks for the help

[HaGGardSmurf]

Yea, np.

Its no big deal, if that tiny bit was corrupt, the rest of the FW should be fine, and you spoof that into a complete FW (ixtreme) if you want to restore to ofw, then you can download the OFW from xbins, and spoof your identification strings to the FW.

[foodang36]

Well it turns out the xbox is in bad shape. It red ringed on me last night while I had it standing up. I layed it down flat and it works now, but its on its way out

[HaGGardSmurf]

ok, well we now know, that's why it was freezing earlier.

Doing an xclamp fix should get rid of your red lights.