TOSHIBA MQ01ABD100V Stuck in BSY

[KiTHardWare]

drive in this topic (TOSHIBA MQ01ABD100V)
This is a quick overview of the steps
1- drive is dead and stuck in bsy and motor doesn't spin (i assume that the problem in the pcb) so i desoldring the rom and make a dump of it and wrote the dump in another pcb and test it but nothing is changed drive stuck in bsy and motor doesn't spin.
2- i desoldering the dononr rom and soldering it on patient pcb drive spin up with clicking and still stuck on bsy no matter how long !? the drive shows id after while only if i isolate hda from pcb.

and here is the weird points
*-original pcb is faulty after testing it on working hard disk
*-patient rom (alot of defrent in hex decimal (27~40 bit) when reading it by 3 defrent models of programmers !?)

the 2nd step of demonstrations tested with 3 different rom dump only one of them working with clicking.

this make no sense at all native pcb and native rom !?

PCB number 003138A
Rom MXIC MX25V400

i attached rom dump for any one can explain or help.

Attachments

TOSHIBA MQ01ABD100V.rar

best dump result

(288.08 KiB) Downloaded 138 times

[fzabkar]

2- i desoldering the dononr rom and soldering it on patient pcb drive spin up with clicking and still stuck on bsy no matter how long !? the drive shows id after while only if i isolate hda from pcb.

the 2nd step of demonstrations tested with 3 different rom dump only one of them working with clicking.

Are you saying that your programmer produced 3 different dumps from the donnor ROM? :-?

I have attached your CPs. They all look OK.

Can you upload all your ROM dumps, both patient and donor? If we compare the dumps perhaps we will see where the problem is.

If the problem is due to a physically bad ROM (ie one where the bits have begun to decay), perhaps we could perform a bitwise AND of all your dumps to produce a good "hybrid" ROM. Otherwise you could search for resources with the same firmware version.

Attachments

CPs_00.7z

(12.49 KiB) Downloaded 140 times

[KiTHardWare]

Are you saying that your programmer produced 3 different dumps from the donnor ROM?

thx fzabkar ( the programmer produced 3 different dump from the patient rom not from donor rom )

I have attached your CPs. They all look OK.

thx

Can you upload all your ROM dumps, both patient and donor? If we compare the dumps perhaps we will see where the problem is.

ok

If the problem is due to a physically bad ROM (ie one where the bits have begun to decay), perhaps we could perform a bitwise AND of all your dumps to produce a good "hybrid" ROM. Otherwise you could search for resources with the same firmware version.

yes i pretty sure the problem in the patient rom i have tested all dump on donor pcb all stuck on bsy also test all of them on donor hard drive same result so the problem in the patient rom

Attachments

Donor.rar

Donor rom

(287.51 KiB) Downloaded 140 times

2.rar

Patient rom

(288.07 KiB) Downloaded 151 times

1.rar

Patient rom

(288.08 KiB) Downloaded 156 times

[Disk Solution]

This Toshiba PCB 003138A only die "power off" nothing else I have experience in at least 1000 drives I have worked.

Something confusing clear this first..

1- drive is dead and stuck in bsy and motor doesn't spin (i assume that the problem in the pcb) so i desoldring the rom and make a dump of it and wrote the dump in another pcb and test it but nothing is changed drive stuck in bsy and motor doesn't spin.

Why you didn't swap the original rom to donor pcb and try may be you missing something?

2- i desoldering the dononr rom and soldering it on patient pcb drive spin up with clicking and still stuck on bsy no matter how long !? the drive shows id after while only if i isolate hda from pcb.

Yes this is what exactly should be no correct head map found from donor rom.

What?? i desoldering the dononr rom and soldering it on patient pcb drive spin up with clicking, patient pcb drive spin up???

[fzabkar]

The "TOSHIBA MQ01ABD100V.BIN" file appears to be the working one. Your programmer appears to be occasionally misreading "1" bits as "0".

Code:

C:\>fc /b 1.bin 2.bin
Comparing files 1.BIN and 2.BIN

00006BFE: FE 7E
000159FD: B5 B4
00015DFE: B5 35
000243FE: 08 28
0002BDFA: D4 D5
0002E5FE: 35 B5
0002EDFE: 9C 1C
0003C1FB: EB E9
0004C3FB: 49 4B
000579FB: 85 84
00068FFE: 3C 7C
0006CDFA: F5 F4
000755FE: BA 3A
00075DFE: B3 33
000773FE: 3C BC

C:\>fc /b 1.bin "TOSHIBA MQ01ABD100V.BIN"
Comparing files 1.BIN and TOSHIBA MQ01ABD100V.BIN

000031FE: 7F FF
000081FE: 73 F3
0000A1FE: 0C 8C
00011DFE: 29 A9
00016BFE: 20 A0
000219FE: 07 87
000231FE: 41 C1
000237FE: 00 80
000243FE: 08 A8
00029BFE: 52 D2
0002BDFA: D4 D5
0002C9FE: 20 A0
0002CDFD: 12 16
0002CDFE: 1F 9F
0002E5FE: 35 B5
0002EFFE: 20 A0
00031FFE: 2B AB
0003BBFE: 74 F4
0003BDFE: 15 95
0003D5FE: 2C AC
0004C3FB: 49 4B
000573FE: 41 C1
00068FFE: 3C 7C
000767FE: 7D FD
000773FE: 3C BC

C:\>fc /b 2.bin "TOSHIBA MQ01ABD100V.BIN"
Comparing files 2.BIN and TOSHIBA MQ01ABD100V.BIN

000031FE: 7F FF
00006BFE: 7E FE
000081FE: 73 F3
0000A1FE: 0C 8C
00011DFE: 29 A9
000159FD: B4 B5
00015DFE: 35 B5
00016BFE: 20 A0
000219FE: 07 87
000231FE: 41 C1
000237FE: 00 80
000243FE: 28 A8
00029BFE: 52 D2
0002C9FE: 20 A0
0002CDFD: 12 16
0002CDFE: 1F 9F
0002EDFE: 1C 9C
0002EFFE: 20 A0
00031FFE: 2B AB
0003BBFE: 74 F4
0003BDFE: 15 95
0003C1FB: E9 EB
0003D5FE: 2C AC
000573FE: 41 C1
000579FB: 84 85
0006CDFA: F4 F5
000755FE: 3A BA
00075DFE: 33 B3
000767FE: 7D FD

[KiTHardWare]

This Toshiba PCB 003138A only die "power off" nothing else I have experience in at least 1000 drives I have worked.

Something confusing clear this first..

1- drive is dead and stuck in bsy and motor doesn't spin (i assume that the problem in the pcb) so i desoldring the rom and make a dump of it and wrote the dump in another pcb and test it but nothing is changed drive stuck in bsy and motor doesn't spin.

Why you didn't swap the original rom to donor pcb and try may be you missing something?

I already try this after my 1st attamp but i didn't mention to sorry i prefer to making dump of the original rom and wrote it to donor rom but after my 1st attamp dosnt work i soldering the patient rom on the donor pcb and same results stuck in bsy and motor dosent spin.

2- i desoldering the dononr rom and soldering it on patient pcb drive spin up with clicking and still stuck on bsy no matter how long !? the drive shows id after while only if i isolate hda from pcb.

Yes this is what exactly should be no correct head map found from donor rom.

Soldering donor rom after wrote dump file to it thats what i mean

What?? i desoldering the dononr rom and soldering it on patient pcb drive spin up with clicking, patient pcb drive spin up???

After making 3 dumps file by using 3 deferent programmer i noticed that there is a defrence in some bit in hex decimal all dump isn't the same so i try all of them and all of them give same result on donor pcb but when i try on patient pcb one of them give different result drive spin up with none stop clicking !? So i test patient pcb on donor hard disk and same result none stop clicking after that i soldering the donor rom to the patient pcb after wrote donor dump on it and test it on donor hard disk and same result none stop clicking !? So i maked sure of the the patient pcb doesn't work as it shoul be

The problem in the patient rom and pcb
After wrote dump file on donor rom give different result on the patient pcb !? And i maked sure of that patient pcb is faulty.
One more thing i test donor pcb with its native rom on patient hard disk and its start spin up normaly no clicking

[KiTHardWare]

The "TOSHIBA MQ01ABD100V.BIN" file appears to be the working one. Your programmer appears to be occasionally misreading "1" bits as "0".

Code:

C:\>fc /b 1.bin 2.bin
Comparing files 1.BIN and 2.BIN

00006BFE: FE 7E
000159FD: B5 B4
00015DFE: B5 35
000243FE: 08 28
0002BDFA: D4 D5
0002E5FE: 35 B5
0002EDFE: 9C 1C
0003C1FB: EB E9
0004C3FB: 49 4B
000579FB: 85 84
00068FFE: 3C 7C
0006CDFA: F5 F4
000755FE: BA 3A
00075DFE: B3 33
000773FE: 3C BC

C:\>fc /b 1.bin "TOSHIBA MQ01ABD100V.BIN"
Comparing files 1.BIN and TOSHIBA MQ01ABD100V.BIN

000031FE: 7F FF
000081FE: 73 F3
0000A1FE: 0C 8C
00011DFE: 29 A9
00016BFE: 20 A0
000219FE: 07 87
000231FE: 41 C1
000237FE: 00 80
000243FE: 08 A8
00029BFE: 52 D2
0002BDFA: D4 D5
0002C9FE: 20 A0
0002CDFD: 12 16
0002CDFE: 1F 9F
0002E5FE: 35 B5
0002EFFE: 20 A0
00031FFE: 2B AB
0003BBFE: 74 F4
0003BDFE: 15 95
0003D5FE: 2C AC
0004C3FB: 49 4B
000573FE: 41 C1
00068FFE: 3C 7C
000767FE: 7D FD
000773FE: 3C BC

C:\>fc /b 2.bin "TOSHIBA MQ01ABD100V.BIN"
Comparing files 2.BIN and TOSHIBA MQ01ABD100V.BIN

000031FE: 7F FF
00006BFE: 7E FE
000081FE: 73 F3
0000A1FE: 0C 8C
00011DFE: 29 A9
000159FD: B4 B5
00015DFE: 35 B5
00016BFE: 20 A0
000219FE: 07 87
000231FE: 41 C1
000237FE: 00 80
000243FE: 28 A8
00029BFE: 52 D2
0002C9FE: 20 A0
0002CDFD: 12 16
0002CDFE: 1F 9F
0002EDFE: 1C 9C
0002EFFE: 20 A0
00031FFE: 2B AB
0003BBFE: 74 F4
0003BDFE: 15 95
0003C1FB: E9 EB
0003D5FE: 2C AC
000573FE: 41 C1
000579FB: 84 85
0006CDFA: F4 F5
000755FE: 3A BA
00075DFE: 33 B3
000767FE: 7D FD

Thx you fzabkar for this hard work but this is so wierd if the 1st dump file looks good so why it doesn't work and stuck on bsy after testing it on donor pcb and the result is same if test it on donor hard disk or patient hard disk !?

[fzabkar]

Try to find a donor with the same firmware version (SN CP). Then we can patch your patient's CPs into the donor ROM.

Otherwise, read the patient ROM 10 times, say, and then perform a bitwise OR to create a hybrid ROM. I'm assuming that the errors are random, and always cause a 1 to be misread as a 0, never the other way round. If you upload your dumps, I can do the OR-ing for you.

This tool will bitwise-OR two files:

https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.bas
https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.exe

[fzabkar]

Is it possible that there is an additional problem? If the drive was installed in a DVR, then it could be firmware locked, or it could be configured to Power Up In Standby (PUIS). If the latter, then HDAT2 could be used to disable PUIS.

MQ01ABD-V Series:
https://toshiba.semicon-storage.com/us/storage/product/internal-specialty/video/articles/mq01abdv-series.html

Applications

Video Editing Systems
Set-Top-Box (STB)
Digital Video Recorders (DVR)
Network Video Recorders (NVR)

[KiTHardWare]

Try to find a donor with the same firmware version (SN CP). Then we can patch your patient's CPs into the donor ROM.

Otherwise, read the patient ROM 10 times, say, and then perform a bitwise OR to create a hybrid ROM. I'm assuming that the errors are random, and always cause a 1 to be misread as a 0, never the other way round. If you upload your dumps, I can do the OR-ing for you.

This tool will bitwise-OR two files:

https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.bas
https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.exe

Thx you fzabkar i will search for matching donor in my stock. and thanks for sharing this useful tool.
i will read patient rom 10 more times with using lowest speed in the programmer's ( mini pro 866 plus & REVELPROG-IS & Mrt ver 3.0 programmer )
One more thing the 1st dump that i attached readed by mrt programmer

[KiTHardWare]

Is it possible that there is an additional problem? If the drive was installed in a DVR, then it could be firmware locked, or it could be configured to Power Up In Standby (PUIS). If the latter, then HDAT2 could be used to disable PUIS.

MQ01ABD-V Series:
https://toshiba.semicon-storage.com/us/storage/product/internal-specialty/video/articles/mq01abdv-series.html

Applications

Video Editing Systems
Set-Top-Box (STB)
Digital Video Recorders (DVR)
Network Video Recorders (NVR)

The hard disk installed in laptop. the customer told me that when he was using laptop its suddenly hang then he force shutdown by pressing power button and then drive doesn't detected after power on again. then he bring hard disk on my office

[KiTHardWare]

Otherwise, read the patient ROM 10 times, say, and then perform a bitwise OR to create a hybrid ROM. I'm assuming that the errors are random, and always cause a 1 to be misread as a 0, never the other way round. If you upload your dumps, I can do the OR-ing for you.

i uploaded all dump files in singl link. thx for help fzabkar https://mega.nz/file/dZQ2VSSB#YaEBG-aIM ... -KQFbzlyIo

[Amarbir[CDR-Labs]]

Try to find a donor with the same firmware version (SN CP). Then we can patch your patient's CPs into the donor ROM.

Otherwise, read the patient ROM 10 times, say, and then perform a bitwise OR to create a hybrid ROM. I'm assuming that the errors are random, and always cause a 1 to be misread as a 0, never the other way round. If you upload your dumps, I can do the OR-ing for you.

This tool will bitwise-OR two files:

https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.bas
https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.exe

Thx you fzabkar i will search for matching donor in my stock. and thanks for sharing this useful tool.
i will read patient rom 10 more times with using lowest speed in the programmer's ( mini pro 866 plus & REVELPROG-IS & Mrt ver 3.0 programmer )
One more thing the 1st dump that i attached readed by mrt programmer

Hi,
the first 2 programmers are not bad ,try reading rom by cleaning legs on each of those, read 10 times so you will have 20 files 10 from 1st programmer and 10 from second one ,Make sure you clean legs first

[KiTHardWare]

Try to find a donor with the same firmware version (SN CP). Then we can patch your patient's CPs into the donor ROM.

Otherwise, read the patient ROM 10 times, say, and then perform a bitwise OR to create a hybrid ROM. I'm assuming that the errors are random, and always cause a 1 to be misread as a 0, never the other way round. If you upload your dumps, I can do the OR-ing for you.

This tool will bitwise-OR two files:

https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.bas
https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.exe

Thx you fzabkar i will search for matching donor in my stock. and thanks for sharing this useful tool.
i will read patient rom 10 more times with using lowest speed in the programmer's ( mini pro 866 plus & REVELPROG-IS & Mrt ver 3.0 programmer )
One more thing the 1st dump that i attached readed by mrt programmer

Hi,
the first 2 programmers are not bad ,try reading rom by cleaning legs on each of those, read 10 times so you will have 20 files 10 from 1st programmer and 10 from second one ,Make sure you clean legs first

Thx Amabir but there is some thing wrong with this rom
I already cleaned the rom and examined it under microscope. same result different checksum crc every time when i reading it

[fzabkar]

I have attached a hybrid ROM made by OR-ing all your dumps. If this fails, I have created another ROM by using your donor's code and patching the patient's CPs. This will only work if the donor's ROM code is compatible with the patient's SA.

Attachments

Donor_code_Patient_CPs.7z

(326.26 KiB) Downloaded 137 times

hybrid.7z

(262.28 KiB) Downloaded 137 times

[KiTHardWare]

I have attached a hybrid ROM made by OR-ing all your dumps. If this fails, I have created another ROM by using your donor's code and patching the patient's CPs. This will only work if the donor's ROM code is compatible with the patient's SA.

thanks fzabkar i will test both of them and inform you with result

[KiTHardWare]

I have attached a hybrid ROM made by OR-ing all your dumps. If this fails, I have created another ROM by using your donor's code and patching the patient's CPs. This will only work if the donor's ROM code is compatible with the patient's SA.

thanks fzabkar i will test both of them and inform you with result

very very thanks fzabkar i realy appreciate you help (Donor_1_Patient_CPs.bin) works efficiently
after analysis i have found g-list error and bad head 0 but it doesn't matter anymore. i can handle it