Samsung TS-H943A - MS28 - grinding noise after LT Flash

[valentin]

Hello guys, i have a Xbox 360 with a Toshiba Samsung Drive TS-H943A. The problem is when i Flash the LT+ v2.01 to the drive the JF log looks good but when i connect the drive to my Xbox 360 and make it on then the drive is making some grinding noise like its spinning and scratching but no disk is inside. When i put original disk in then the Xbox Logo shows like a DVD. Any idea ?

When i FLash it with orig. FW the drive works great with orig. disks. Only on Flash it doesnt work.

JF Log:

Drive is Samsung..


Sending Sammy_Un_Lock to Drive on port 0x0000
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 0x0000
Parallel flash found with Status 0x70


Reading Bank 0: ................
Reading Bank 1: ................
Reading Bank 2: ................
Reading Bank 3: ................


Dumped in 10381mS


Samsung Dump file saved to SAM-OFW Xbox Phat White.bin
Loading firmware from buffer
Inquiry string found
Identify string found
Drive key @ 0x4140 *********************************
Firmware Osig: [TSSTcorpDVD-ROM TS-H943Ams28]
Firmware is: Stock
Key added to database


Auto-Loading firmware file C:*********************************************
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




Loading MTK_Flash source file
Spoofing Target
DVD Key already matches
ID strings already match




Getting Status from port 0x0000
Parallel flash found with Status 0x70
Writing target buffer to flash


Sending Chip Erase request to port 0x0000
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: ................
Reading Bank 3: ................
Write verified OK !


Sending Vendor Outro to port 0x0000


Key found in KeyDB at record (FW)
Key is: *********************************
Key has been tested and verified, thanks C4eva !
Drive is Samsung..

Thanks

 

[Dadko]

It looks like bad flash. But log seems to be correct. What dashboard are you running on? Today I was fixing same problem. Customer was trying to apply update from some low dash. It was making same error. I had to reflash drive. Is it possible that drive was spoofed before?

 

[valentin]

I am running the latest DB 17349 or something like that. The previous DB was 16202 i think. Looked like normal drive not spoofed. I have reflashed it twice. I tried to write stock Then Flash. But Nothing worked, always the same problem.

 

[valentin]

Can you post a solution for this problem as you said you have fixed it. Thanks

 

[Dadko]

Customer had lt2. Tried to update dashboard from some low. It broke his flash and started to behave like yours. I just reflashed drive to lt3. Where city are you from? If you are near Zilina I can try that. But I believe there will be some other problem.