Page 1 of 1
rebuild mod47
Posted: June 25th, 2018, 1:58
by hitmannaser
hi guru
i have a WD5000AZDX-00SC2B0 harddisk with burned pcb,i changed the pcb and trying rebuild rom from sa but mrt can't rebuild mod47,i have access to mod40 ,is there any way to rebuild mod47 from module40 by hex editor?
Re: rebuild mod47
Posted: June 25th, 2018, 9:30
by unknown
PCB number? 701640-003? Tahoe?
If yes, then rebuilding ROM from SA via MRT should be OK.
What about native ROM?
Re: rebuild mod47
Posted: June 25th, 2018, 9:53
by hitmannaser
pcb number 2060-771824-005 trails family.
the pcb rom,mcu,buffer burned and the harddisk head was clicking i change it with WD5000AZRX-00A8LB0 same family and it works but i have problem with module47.
Re: rebuild mod47
Posted: June 26th, 2018, 2:30
by hitmannaser
can anyone help extract 47 from this 2 module?
Re: rebuild mod47
Posted: June 26th, 2018, 17:01
by fzabkar
Can you upload modules 47h and 40h from your donor? I believe I have worked out the structure of module 40h, but I need a working example of 47h for comparison purposes.
Re: rebuild mod47
Posted: June 27th, 2018, 1:21
by hitmannaser
hi fzabkar
this is from donor to compare
Re: rebuild mod47
Posted: June 27th, 2018, 2:26
by databack
I have the same modules backup...
Re: rebuild mod47
Posted: June 27th, 2018, 16:41
by fzabkar
My preliminary investigation suggests that module 40h consists of several sections, most of which are subdivided into additional subsections, with 1 subsection per head.
This is the module header:
- Code:
Offset(h) 00 02 04 06 08 0A 0C 0E
00000000 524F 594C 0100 3000 4000 BF01 D9FC F252 ROYL..0.@.¨.U•R
00000010 3030 3031 3030 3030 0707 0700 0000 5800 00010000......X.
offset to table ^^^^
00000020 0000 0000 0000 0000 0000 0000 0000 0000
It points to a table which defines the location and size of each section.
- Code:
Table of sections
Offset(h) 00 04
offset size
-------- --------
00000058 58010000 00010000
00000060 58020000 000A0000
00000068 580C0000 F01D0100
00000070 482A0100 E0160000
00000078 28410100 E02E0000
00000080 08700100 98000000
00000088 A0700100 00B70000
00000090 A0270200 D00C0000
00000098 90560300 101F0000
000000A0 70340200 DB210100
000000A8 4C560300 20000000
000000B0 6C560300 24000000
000000B8 A0750300 20000000
000000C0 C0750300 B8020000
000000C8 78780300 D0030000
000000D0 00000000 00000000
This is the layout of one of the sections. There are 8 blocks of data for heads 0 - 7.
head #0 (populated)
- Code:
71CA 0000 0000 7F00 0000 0000 8A00 906A 2F6C 1C00
70CA 0000 0000 7F00 0000 0000 8A00 9069 2F6C 1E00
6FCA 0000 0000 7F00 0000 0000 8A00 9079 2E6C 2000
6FCA 0000 0000 7F00 0000 0000 8A00 9078 2E6C 2100
6FCA 0000 0000 7F00 0000 0000 8A00 9068 2D6C 2300
6FCA 0000 0000 7F00 0000 0000 8A00 9068 2C6C 1A00
6FCA 0000 0000 7F00 0000 0000 8A00 9068 2B6C 1B00
6FCA 0000 0000 7F00 0000 0000 8A00 9068 2A6C 1C00
70CA 0000 0000 7F00 0000 0000 8A00 9068 296C 1E00
71CA 0000 0000 7F00 0000 0000 8A00 9058 296C 2000
72CA 0000 0000 7F00 0000 0000 8A00 9058 286C 1900
73CA 0000 0000 7F00 0000 0000 8A00 9058 286C 1C00
75CA 0000 0000 7F00 0000 0000 8A00 9058 286C 1E00
77CA 0000 0000 7F00 0000 0000 8A00 9058 286C 2100
79CA 0000 0000 7F00 0000 0000 8A00 9068 296C 2500
7BCA 0000 0000 7F00 0000 0000 8A00 9068 2A6C 2900
head #1 (populated)
- Code:
71CA 0000 0000 7F00 0000 0000 8A00 9079 2E74 1D00
70CA 0000 0000 7F00 0000 0000 8A00 9069 2D74 1E00
6FCA 0000 0000 7F00 0000 0000 8A00 9069 2C74 2000
6ECA 0000 0000 7F00 0000 0000 8A00 9068 2B74 2100
6ECA 0000 0000 7F00 0000 0000 8A00 9068 2A74 2200
6ECA 0000 0000 7F00 0000 0000 8A00 9068 2974 1900
6ECA 0000 0000 7F00 0000 0000 8A00 9068 2974 1A00
6FCA 0000 0000 7F00 0000 0000 8A00 9068 2874 1C00
6FCA 0000 0000 7F00 0000 0000 8A00 9068 2874 1E00
70CA 0000 0000 7F00 0000 0000 8A00 9078 2874 2000
71CA 0000 0000 7F00 0000 0000 8A00 9078 2874 1900
73CA 0000 0000 7F00 0000 0000 8A00 9078 2874 1B00
74CA 0000 0000 7F00 0000 0000 8A00 9078 2974 1E00
76CA 0000 0000 7F00 0000 0000 8A00 9078 2A74 2100
78CA 0000 0000 7F00 0000 0000 8A00 9078 2B74 2400
7BCA 0000 0000 7F00 0000 0000 8A00 9068 2D74 2800
heads #2 -7 (not populated)
- Code:
00CA 0000 0000 7F00 0000 0000 8A00 9000 0000 0000
00CA 0000 0000 7F00 0000 0000 8A00 9000 0000 0000
........
00CA 0000 0000 7F00 0000 0000 8A00 9000 0000 0000
Re: rebuild mod47
Posted: June 27th, 2018, 18:22
by fzabkar
I think I've worked it out, but it will take me a little time to write it up.
Re: rebuild mod47
Posted: June 28th, 2018, 1:22
by hitmannaser
wow it's good to know how to rebuild important module in some cases mrt can't rebuild 47 and do that by hex editor i search the module 47 and only found the header in 40.
Re: rebuild mod47
Posted: June 28th, 2018, 3:51
by mrtlabinfo
hitmannaser wrote:wow it's good to know how to rebuild important module in some cases mrt can't rebuild 47 and do that by hex editor i search the module 47 and only found the header in 40.
Hello friend, I would like to suggest you to contact our technical support for a remote check, below are his contact ways:
Email:service@mrtlab.com
Skype:live:service_5567
QQ:2693828612
Have a nice day!
Re: rebuild mod47
Posted: June 28th, 2018, 22:31
by mrtlabinfo
Spildit wrote:mrtlabinfo wrote:hitmannaser wrote:wow it's good to know how to rebuild important module in some cases mrt can't rebuild 47 and do that by hex editor i search the module 47 and only found the header in 40.
Hello friend, I would like to suggest you to contact our technical support for a remote check, below are his contact ways:
Email:service@mrtlab.com
Skype:live:service_5567
QQ:2693828612
Have a nice day!
Or "maybe" you guys can implement a "function" on MRT to rebuild ROM module 47 from SA module 40 ?
Hi, in WD utility, we have the function named "Rebuild ROM from SA", and in this function, we can generate ROM and ROM modules, and we can generate module 47 from module 40 and module 103.
Re: rebuild mod47
Posted: June 29th, 2018, 1:58
by hitmannaser
yes there is a function to do this but not working in this family when i rebuild rom from sa and check the rom module there is a problem in mod 47 and i tested on healty drive sam family to rebuild rom but same result by the way i will call your technical support and i hope help me solving the problem thank you for your attention.
Re: rebuild mod47
Posted: June 29th, 2018, 19:30
by fzabkar
This is the best I can do (see attachment).
That said, if both (?) the PCB and headstack were swapped, then wouldn't it be preferable to import the donor's channel, preamp and microjog adaptives into the patient's ROM?
Re: rebuild mod47
Posted: July 1st, 2018, 11:10
by hitmannaser
thanks fzabkar your generated 47 module it works,after writing 47 and repair damage modules the hard disk go's ready and i can access the data you are the best fzabkar
thank you very much.
Re: rebuild mod47
Posted: July 1st, 2018, 16:14
by hitmannaser
yes dear spildit i tested before that mrt rebuild all modules only the 47 end with error i want to contact mrt support but the case closed by fzabkar great help,really he is good in hex.
Re: rebuild mod47
Posted: July 3rd, 2018, 2:29
by hitmannaser
Dear spildit mrt use two method the first trying load from sa backup and if fail go to method two is rebuilding the 47 from mod40 like the attached picture.
Re: rebuild mod47
Posted: August 14th, 2018, 5:02
by trumanhw
IMAGINE!??? If there was like.... a thing... with.... SQUIGGLES on it... almost like... LANGUAGE! Imagine if there was a book, not written in changlish -- that introduced the way the thing worked sufficiently to where people didn't consistently point out how difficult it is to learn given that absolute non-existence of documentation; video tutorials. Or even a tendency for tech support to reply within 3 days.
....Though I doubt they haven't in 30, I just gave up bothering to get a reply.