Page 1 of 1

TOSHIBA (MK3256GSY) BAD ROM

Posted: 07.02.17, 09:15
by CS DATA RECOVERY
HI,
Seniors,

MY DRIVE TOSHIBA MK3256GSY ITS DEAD CONDITION I TRIED TO CHANGE PCB WITH ROM STILL DEAD CONDITION IF I CHANGE ANOTHER ROM PCB WORKS
MAY BE ROM DEAD ANY SOLUTION FOR THIS CASE .

MK3256GSY(FW:A0/LH013C)

Thanks
Pavan

Re: TOSHIBA (MK3256GSY) BAD ROM

Posted: 13.02.17, 13:05
by Filipp_TS
Hello,

What you mean exactly "bad condition" ?
What a LEDs are light? It' doesn't spin up?

If ROM is damaged then case can't be solved 'cause whole SA (except few modules) on toshiba drives inside the ROM chip.
You can only try to read a dump from ROM chip by programmer device then write itto the donor ROM chip (don't forget to make a backup) then check a behavior.

Re: TOSHIBA (MK3256GSY) BAD ROM

Posted: 18.02.17, 05:10
by Amarbir[CDR-Labs]
Filipp_TS wrote:Source of the post Hello,

What you mean exactly "bad condition" ?
What a LEDs are light? It' doesn't spin up?

If ROM is damaged then case can't be solved 'cause whole SA (except few modules) on toshiba drives inside the ROM chip.
You can only try to read a dump from ROM chip by programmer device then write itto the donor ROM chip (don't forget to make a backup) then check a behavior.


Hi,
why cannot the tool write rom in toshiba drives ,can this feature not be implemented ?

Re: TOSHIBA (MK3256GSY) BAD ROM

Posted: 24.03.17, 11:09
by Filipp_TS
Amarbir[CDR-Labs] wrote:Source of the post why cannot the tool write rom in toshiba drives ,can this feature not be implemented ?

'cause this procedure is not realized in PC-3000 software. Developers are not add it.
You can write it by Programmer hardware device.
Another thing: "For what?" - ROM is unique and if it's OK then drive work correct, but if it's damaged then drive can't be recovered 'cause ROM have unique modules inside.

Re: TOSHIBA (MK3256GSY) BAD ROM

Posted: 02.04.17, 10:17
by Amarbir[CDR-Labs]
Filipp_TS wrote:Source of the post
Amarbir[CDR-Labs] wrote:Source of the post why cannot the tool write rom in toshiba drives ,can this feature not be implemented ?

'cause this procedure is not realized in PC-3000 software. Developers are not add it.
You can write it by Programmer hardware device.
Another thing: "For what?" - ROM is unique and if it's OK then drive work correct, but if it's damaged then drive can't be recovered 'cause ROM have unique modules inside.



Well,
Seagate rom is also unique ,But if we have bad code segments we can import modules " provided they are ok and intact in corrupt rom " . This same features can be provided in Toshiba Roms .We should be able to extract CP's and then we can use same version rom and import those few CP's to it and get a working rom .Is this so hard its very possible IMHO filipp

Re: TOSHIBA (MK3256GSY) BAD ROM

Posted: 26.10.17, 19:06
by pclab
Writing/Reading ROM by terminal for instance (like WD) would avoid to be soldering ROM when a PCB swap is needed (USB to SATA for instance).
As we all now, these chips are fragile to heat...

Re: TOSHIBA (MK3256GSY) BAD ROM

Posted: 27.10.17, 05:03
by Amarbir[CDR-Labs]
pclab wrote:Source of the post Writing/Reading ROM by terminal for instance (like WD) would avoid to be soldering ROM when a PCB swap is needed (USB to SATA for instance).
As we all now, these chips are fragile to heat...


Well,
Not only this the pcb is crap quality if we remove capacitors and try data conversions sometime the whole track comes out of the pcb ,horrible quality