|
jhonnyp0lak
|
 |
« Reply #20 on: October 17, 2009, 01:05:47 AM » |
|
have you tried it on another computer ? Seems the chipset or mobo you're trying this on isn't playing nice with MHDD. And its normal for a different revision of a hdd to have different LBA numbers.
|
|
|
|
|
Logged
|
|
|
|
cfxomega
Newbie

Posts: 3
|
 |
« Reply #21 on: October 18, 2009, 08:50:37 AM » |
|
have you tried it on another computer ? Seems the chipset or mobo you're trying this on isn't playing nice with MHDD. And its normal for a different revision of a hdd to have different LBA numbers.
thanks for the quick reply! the mobo i'm using is an Asus M3A78-EM...I guess i'll have to find another computer to try it on...i'll post my results then...thx
|
|
|
|
|
Logged
|
|
|
|
Erlendsen
Newbie

Posts: 2
|
 |
« Reply #22 on: October 18, 2009, 11:14:37 AM » |
|
Hi,
I am stuck at the MHDD-part. MHDD will not detect my little hard drive. It detects my VIA VT6421 chipset, but the HD is not listed. I`ve tried with both a 20GB HD and a 120GB HD, no luck.
What can I do?
Thanks
|
|
|
|
|
Logged
|
|
|
|
cfxomega
Newbie

Posts: 3
|
 |
« Reply #23 on: October 19, 2009, 10:57:56 AM » |
|
Hi,
I am stuck at the MHDD-part. MHDD will not detect my little hard drive. It detects my VIA VT6421 chipset, but the HD is not listed. I`ve tried with both a 20GB HD and a 120GB HD, no luck.
What can I do?
Thanks
From the first post... Q: Do i have to use my integrated SATA ports or can i use a VIA VT6421A PCI SATA adapter ? A: This trick won't work on a VIA VT6421A adapter. You will keep getting FAIL errors in MHDD.
|
|
|
|
|
Logged
|
|
|
|
theskeels
Newbie

Posts: 3
|
 |
« Reply #24 on: November 09, 2009, 06:58:38 PM » |
|
Can someone who successfully used this technique on a 60 GB please indicate what value should be used during this step: "Native Maximum LBA address: 39070079". The OP indicates that value is only for a 20 GB.
Thanks.
|
|
|
|
|
Logged
|
|
|
|
Platinum
Newbie

Posts: 2
|
 |
« Reply #25 on: November 14, 2009, 06:18:58 PM » |
|
where can i find winhex full version ?
|
|
|
|
« Last Edit: November 14, 2009, 07:07:21 PM by Platinum »
|
Logged
|
|
|
|
|
Arakon
|
 |
« Reply #26 on: November 14, 2009, 07:40:34 PM » |
|
You buy it. Idiot.
|
|
|
|
|
Logged
|
I do NOT give support by email, PM, ICQ or whatever. Anyone annoying me that way will have his balls removed. With a rusty butterknife. Slowly. And I'll enjoy doing it.
|
|
|
Max Platinum
Newbie

Posts: 6
|
 |
« Reply #27 on: November 14, 2009, 08:41:08 PM » |
|
You buy it. Idiot.
sorry 
|
|
|
|
|
Logged
|
|
|
|
Max Platinum
Newbie

Posts: 6
|
 |
« Reply #28 on: November 14, 2009, 10:20:11 PM » |
|
sorry for asking but : 9. Set the following options: - Write pattern for damaged source sectors (unselected) - Simulatenous I/O (selected) - Avoid damaged areas. Skip Range (unselected) - Start Sector: 0 - Copy Entire Medium (selected) where Exactly can i find this ? it didnt show up 
|
|
|
|
|
Logged
|
|
|
|
Max Platinum
Newbie

Posts: 6
|
 |
« Reply #29 on: November 15, 2009, 03:58:03 PM » |
|
god damn it . i was searching for two weeks and now when i finally found a topic that talk about this issue i get no answer !! oh right i forgot am an idoit after all 
|
|
|
|
|
Logged
|
|
|
|
|
jhonnyp0lak
|
 |
« Reply #30 on: November 16, 2009, 08:20:06 AM » |
|
@ Max Platinum I'm sure if you follow the instructions carefully step by step you will get all the necessary prompts. Also keep in mind that the version of WinHEX i used might be different to yours - this is where you need to rely on your intellect to guide you through the process. Tutorials often fall out of date. I've been busy with my personal life and don't have much time to follow the scene these days. But keep trying and you'll get there. Remember, you don't have to use WinHEX, you can use other tools. Learn a freeware hex editor if you cant buy WinHEX and apply the same "prinicples" outlined in this tutorial. One thing you'll learn after being a part of the scene for a while is that every tutorial needs to be slightly altered when you apply it to your own circumstances, because for that very reason, they are your personal circumstances. Nobody will work here fulltime to hold your hand. Just start over and good luck with the process. If others got it to work, you can too 
|
|
|
|
|
Logged
|
|
|
|
Max Platinum
Newbie

Posts: 6
|
 |
« Reply #31 on: November 16, 2009, 11:42:41 AM » |
|
i forgot to select restore img  ok this time i did what u said .. and it worked .. all i need to do now is to find MMHD USB bootable EXE hmm (i dont have a empty cd right now lol) BTW thank u 4 this Tutorial its going to help pepole like me alot
|
|
|
|
|
Logged
|
|
|
|
Max Platinum
Newbie

Posts: 6
|
 |
« Reply #32 on: November 18, 2009, 09:30:57 PM » |
|
my xbox hdd is seagate and i cant find hddss.bin for it and all my backup 4 my hdd is gone 
|
|
|
|
|
Logged
|
|
|
|
theskeels
Newbie

Posts: 3
|
 |
« Reply #33 on: November 20, 2009, 12:39:09 PM » |
|
Even if someone hasn't successfully tested it, does anyone know what "Native Maximum LBA address" value should be used for a 60 GB? I hope someone can provide an answer, as my HDD is out of commission until I can perform this fix and I do not know what value to try.
Thanks for the help.
|
|
|
|
|
Logged
|
|
|
|
nikiyah
Newbie

Posts: 1
|
 |
« Reply #34 on: November 22, 2009, 03:27:09 PM » |
|
uuuuuummmmmmmmmm i need help on how to register for some reason i cant do it
|
|
|
|
|
Logged
|
|
|
|
lucas_sfc
Newbie

Posts: 1
|
 |
« Reply #35 on: December 17, 2009, 03:22:13 PM » |
|
WOW MAN...THANKS! i though my hd was dead...i was trying to find a solution everywhere and finally found it here..thanks for the tuto..i followed tuto #2 and it worked perfectly...thanks again! u saved my hd haha;
edit: my hd was an original TOSHIBA, 60gb hdd
|
|
|
|
|
Logged
|
|
|
|
brinkofdoom
Newbie

Posts: 1
|
 |
« Reply #36 on: December 28, 2009, 09:33:15 PM » |
|
How can i go about getting my original hdds.bin file? Most of the data on the drive has been wiped.
Also when following guide 1 step 34. Type NHPA (and press Enter) It says "Drive is not ready" then moves to 35. Do you want to set Native LBA address (y/N)? - type: Y And says "Read NHPA" (been there for about 20 minutes now) is this because im not using my original hdds.bin file?
Thanks in advance, and the tut is very good
|
|
|
|
|
Logged
|
|
|
|
|
4cc3ss
|
 |
« Reply #37 on: December 29, 2009, 09:13:45 PM » |
|
I've just finished doin a original hitachi 60gb hdd with no problems, thanks for the great tut.  Winhex, bootable iso, original hdds.bin.
|
|
|
|
|
Logged
|
|
|
|
wwwpop
Newbie

Posts: 8
|
 |
« Reply #38 on: January 02, 2010, 12:59:22 AM » |
|
I found this post and spent the day trying it. I love it. It works great and is easy for a nube like me to follow.I read and fully understand the statements about the hddss.bin and the fact that the drive has to match it. But I am a stuborn old coot who just won't give up. If you can grab a hddss.bin from an xbox drive why can't you grab a hddss from another drive and combine the two so you can replace a broken drive for which you don't have a hddss.bin with a cheap laptop drive. There must be a way to extract the info needed. I am so sorry I don't posess the knowledge to do this.  From 6, 20 gig seagates to 1 Fujitsu 60 gig. the generic hddss just don't work. If the wd numbers can be written the other mfgr's can be some how we just haven't found it yet.
|
|
|
|
|
Logged
|
|
|
|
|
jhonnyp0lak
|
 |
« Reply #39 on: January 02, 2010, 11:25:48 PM » |
|
wwwpop, you cant just use any hddss.bin because its signed to a particular serial number. Let me give you an example to make it clearer.
So say you have two drives, the first is an original working drive and the second is the one you lost your hddss.bin for ....
Drive 1: Samsung 20GB Serial Number 00000001 ......... hdssbin expects serial number 00000001 and is signed with a key making it have a checksum of: AAAA Drive 2: Samsung 20GB Serial Number 00000002 ......... hdssbin expects serial number 00000002 and is signed with a key making it have a checksum of: BBBB
If for drive 2 you loose your hddss.bin and put in the hddss.bin from drive 1 your xbox is expecting a drive with serial number 00000001 and checksum of AAAA. Instead its getting a drive with serial number 00000002 and a checksum of AAAA. This is not a valid configuration. Each hddss.bin contains the drive's serial number and is signed with a key (which we dont have). The moment we change the serial number it breaks the signature and xbox doesnt want to read the drive. So if you do alter the hddss.bin file for example, your xbox expects a drive with serial number 00000001 and gets a drive with serial number 0000001 but gets a weird checksum like CDCE, because its not signed with the right key.
The only way to counter this is to change the serial number on the hard disk. This has to be done in the drive's firmware. Normal motherboards cant access that part of the hard drive, you will need a special hdd programmer.
|
|
|
|
|
Logged
|
|
|
|
|