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.htmlIf 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.htmlI don't have any firsthand experience with HddHackr, so there may be errors.