I need the firmware

[Fabport]

I have a problem with a Toshiba MK1246GSX 120GB HD, was doing a test to use it as a disk storage for a video game, only to do the procedure I did not save the firmware of the HD, the test failed and not has to undo the procedure because I did not backup the firmware. He is working, he is recognized by the OS on the pc but not as open storage. I just need the firmware of the HD to put it in place and re-use my HD, if someone can help me I am very grateful.

Description of HD:
Toshiba MK1246GSX disk drive
And HDD2D91 UK01 T
DC +5 V 1.0A
010 B0/LB213J
capacity of 120GB

[dmarques]

So how is detected now?

I think a few people is using some cracking apps for game consoles and then they have problems

[fzabkar]

Which "procedure" did you use?

[Fabport]

Which "procedure" did you use?

I replaced the original firmware for this "hddss.bin" and did not back up the original, and now I need the firmware of this model to restore my HD, if I get it solve my problem.

[pcimage]

It's not quite as simple as that on hard drives, you cannt simply "reflash" the firmware with one file, that's not how they work.

[fzabkar]

It sounds like you used HddHackr to modify your drive's firmware. However, my understanding is that HddHackr works on WD drives. Does it also support Toshibas now?

The hddss.bin file backs up sectors 16-22. These are in the user area of the drive — they are not part of the firmware.

[Fabport]

It sounds like you used HddHackr to modify your drive's firmware. However, my understanding is that HddHackr works on WD drives. Does it also support Toshibas now?

The hddss.bin file backs up sectors 16-22. These are in the user area of the drive — they are not part of the firmware.

Yes HddHackr was used rather than the Toshiba drives do not support, I did a test that failed, and the procedure time to back up when the procedure calls, but when I did checked the folder, the backup was not done, I believe that if I get the firmware for hd it returns to normal.
By placing it on a computer it recognizes the model, series and everything, but does not open for recording files are stored.

[fzabkar]

The translation is making it difficult for me to understand you, but it appears that the procedure that you used did not touch your drive's firmware. Instead it may be that sectors 16-22 in the user area may have been overwritten by HddHackr. This would normally be of no consequence in a typical desktop installation (because sectors 1 - 62 would be blank), but if the drive were used in a laptop, then this area may have been used by a proprietary boot process to provide access to a Recovery partition, or to Media Direct in the case of Dell.

My approach would be to stop, keep a cool head, and examine the abovementioned sectors with a disc editor, in read-only mode.

HxD - Freeware Hex Editor and Disk Editor:
http://mh-nexus.de/en/hxd

DMDE (DM Disk Editor and Data Recovery):
http://softdm.com/download.html

If you could show us the contents of sector 0 (LBA 0), preferably in hexadecimal mode, then we could narrow down the problem. My feeling is that there will be a relatively straighforward logical DIY solution.

BTW, here is my understanding of how HddHackr works:
http://www.users.on.net/~fzabkar/HDD/Hd ... lysis.html

I don't have any firsthand experience with HddHackr, so there may be errors.

[Fabport]

The translation is making it difficult for me to understand you, but it appears that the procedure that you used did not touch your drive's firmware. Instead it may be that sectors 16-22 in the user area may have been overwritten by HddHackr. This would normally be of no consequence in a typical desktop installation (because sectors 1 - 62 would be blank), but if the drive were used in a laptop, then this area may have been used by a proprietary boot process to provide access to a Recovery partition, or to Media Direct in the case of Dell.

My approach would be to stop, keep a cool head, and examine the abovementioned sectors with a disc editor, in read-only mode.

HxD - Freeware Hex Editor and Disk Editor:
http://mh-nexus.de/en/hxd

DMDE (DM Disk Editor and Data Recovery):
http://softdm.com/download.html

If you could show us the contents of sector 0 (LBA 0), preferably in hexadecimal mode, then we could narrow down the problem. My feeling is that there will be a relatively straighforward logical DIY solution.

BTW, here is my understanding of how HddHackr works:
http://www.users.on.net/~fzabkar/HDD/Hd ... lysis.html

I don't have any firsthand experience with HddHackr, so there may be errors.

I'll do what it says and then return the result.
thank you.