Fujitsu MPG3204AT -TC Wrong Firmware...
March 26th, 2007, 14:59
Hi all!:)
One of my friends got a problem with his HDD.
He flashed his Fujitsu drive with wrong FW, and now BIOS won't detect it
(normal...)
I think he's flashed only FW section of flash (if it exist a sectors of FW, like in WDs or Seagates drives) , boot and config should exist so maybe there's an option to fix the drive?
I don't know how to do this, is it possible to fix it even if "user" (i meantTHIS)
level flashing utility won't detect drive??
MPG3204AT -TC
ID: JW YFIP
CA9-90B5
Thank's a lot:)
One of my friends got a problem with his HDD.
He flashed his Fujitsu drive with wrong FW, and now BIOS won't detect it
(normal...)
I think he's flashed only FW section of flash (if it exist a sectors of FW, like in WDs or Seagates drives) , boot and config should exist so maybe there's an option to fix the drive?
I don't know how to do this, is it possible to fix it even if "user" (i meantTHIS)
level flashing utility won't detect drive??
MPG3204AT -TC
ID: JW YFIP
CA9-90B5
Thank's a lot:)
March 27th, 2007, 3:38
Try free drive analysis at "aff repair station" site.
Connect duff drive to secondary master on a good PC, visit site, download software and run the free diagnostics.
Post result here
Connect duff drive to secondary master on a good PC, visit site, download software and run the free diagnostics.
Post result here
March 27th, 2007, 7:09
Okay so as i say, i think the drive is in good condition....
But Update Tool won't detect drive
I think i should use another tool, wich should "force" to flash drive without detection, but wich one??
000008D0 INFO mar 27, 2007. 13:06:54:
000008D0 INFO mar 27, 2007. 13:06:54: Fujitsu MPF/MPG AT/AH diagnostics (gat)
000008D0 INFO mar 27, 2007. 13:06:54: Device Reset...
000008D0 INFO mar 27, 2007. 13:06:55: Identify...
000008D0 INFO mar 27, 2007. 13:06:56: ERROR: Command aborted or ignored
000008D0 INFO mar 27, 2007. 13:06:56: Device SVM...
000008D0 INFO mar 27, 2007. 13:06:57: SVM is OK. Checking system area, it should take about 10 minutes.
000008D0 INFO mar 27, 2007. 13:06:58: SA block #01, result: OK
000008D0 INFO mar 27, 2007. 13:06:59: SA block #02, result: OK
000008D0 INFO mar 27, 2007. 13:07:00: SA block #03, result: OK
000008D0 INFO mar 27, 2007. 13:07:01: SA block #04, result: OK
000008D0 INFO mar 27, 2007. 13:07:02: SA block #05, result: OK
000008D0 INFO mar 27, 2007. 13:07:03: SA block #06, result: OK
000008D0 INFO mar 27, 2007. 13:07:04: SA block #07, result: OK
000008D0 INFO mar 27, 2007. 13:07:06: SA block #08, result: OK
000008D0 INFO mar 27, 2007. 13:07:07: SA block #09, result: OK
000008D0 INFO mar 27, 2007. 13:07:08: SA block #10, result: OK
000008D0 INFO mar 27, 2007. 13:07:10: SA block #11, result: OK
000008D0 INFO mar 27, 2007. 13:07:13: SA block #12, result: OK
000008D0 INFO mar 27, 2007. 13:07:14: SA block #13, result: OK
000008D0 INFO mar 27, 2007. 13:07:15: SA block #14, result: OK
000008D0 INFO mar 27, 2007. 13:07:16: SA block #16, result: OK
000008D0 INFO mar 27, 2007. 13:07:17: SA block #17, result: OK
000008D0 INFO mar 27, 2007. 13:07:19: SA block #18, result: OK
000008D0 INFO mar 27, 2007. 13:07:20: SA block #19, result: OK
000008D0 INFO mar 27, 2007. 13:07:21: SA block #20, result: OK
000008D0 INFO mar 27, 2007. 13:07:22: SA block #21, result: OK
000008D0 INFO mar 27, 2007. 13:07:23: SA block #22, result: OK
000008D0 INFO mar 27, 2007. 13:07:24: SA block #23, result: OK
000008D0 INFO mar 27, 2007. 13:07:25: SA block #24, result: OK
000008D0 INFO mar 27, 2007. 13:07:26: SA block #26, result: OK
000008D0 INFO mar 27, 2007. 13:07:27: SA block #27, result: OK
000008D0 INFO mar 27, 2007. 13:07:28: SA block #28, result: OK
000008D0 INFO mar 27, 2007. 13:07:30: SA block #29, result: OK
000008D0 INFO mar 27, 2007. 13:07:31: SA block #30, result: OK
000008D0 INFO mar 27, 2007. 13:07:32: SA block #31, result: OK
000008D0 INFO mar 27, 2007. 13:07:33: SA block #32, result: OK
000008D0 INFO mar 27, 2007. 13:07:34: SA block #39, result: OK
000008D0 INFO mar 27, 2007. 13:07:35: SA block #40, result: OK
000008D0 INFO mar 27, 2007. 13:07:35: SA block #41, result: OK
000008D0 INFO mar 27, 2007. 13:07:36: SA block #45, result: OK
000008D0 INFO mar 27, 2007. 13:07:37: SA block #46, result: OK
000008D0 INFO mar 27, 2007. 13:07:38: SA block #48, result: OK
000008D0 INFO mar 27, 2007. 13:07:39: SA block #49, result: OK
000008D0 INFO mar 27, 2007. 13:07:40: SA block #50, result: OK
000008D0 INFO mar 27, 2007. 13:07:41: SA block #53, result: OK
000008D0 INFO mar 27, 2007. 13:07:43: SA block #54, result: OK
000008D0 INFO mar 27, 2007. 13:07:44: SA block #61, check failed
000008D0 INFO mar 27, 2007. 13:07:45: SA block #64, result: OK
000008D0 INFO mar 27, 2007. 13:07:46: SA block #65, result: OK
000008D0 INFO mar 27, 2007. 13:07:47: SA block #80, result: OK
000008D0 INFO mar 27, 2007. 13:07:48: SA block #81, result: OK
000008D0 INFO mar 27, 2007. 13:07:50: SA block #82, result: OK
000008D0 INFO mar 27, 2007. 13:07:50: SA block #112, result: OK
000008D0 INFO mar 27, 2007. 13:07:51: This drive can be recovered with Repair Station. To recover this drive please purchase any service plan: http://www.hdd-tools.com/products/rrs/plans/
But Update Tool won't detect drive
I think i should use another tool, wich should "force" to flash drive without detection, but wich one??
March 27th, 2007, 9:06
Hmm, so it would seem drive is physically OK.
Are you using the Fujitsu update tool? And drive connected to Primary IDE and set to Master?
Which ver? I have v2.02a and it usually works OK.
Are you using the Fujitsu update tool? And drive connected to Primary IDE and set to Master?
Which ver? I have v2.02a and it usually works OK.
March 27th, 2007, 9:58
Oh, i didn't know about Fujitsu Recovery Disk
But unfortunately, this tool says that drive won't be recovered because important data was broken :/
What data? SVM are OKs
But unfortunately, this tool says that drive won't be recovered because important data was broken :/
What data? SVM are OKs
Powered by phpBB © phpBB Group.