Stuck in Initializing

[Bryan34]

I hope someone has run across this issue and would be able to help. I have a M632h that after replacing the Developing gear for a repeating light print. I put the unit back together and now the unit is stuck in initializing.  The counter/timer keeps going, I have let it run over night as well it just keep counting away.

What I have tried so far...

• Cold Reset 
• Format Disk 
• Reloaded the firmware (2x's)
• Replaced the Hard Drive
• Reloaded the firmware

All to no avail, any suggestions welcome

[Valsimot]

You can access the preboot menu to test printers components ( memory, hdd) maybe something failed. Have you double-checked if you connected all cables and connectors good?

[Bryan34]

Valsimot,

Thanks for the reply, yes tried reseating the board and double triple checked the cables. I even took a picture of the boards before disassembling it. I can access the pre-boot menu and I have replaced the hard drive. I do agree with you that something has failed, just not sure if I have to replace the formatter or not.

In the pre-boot menu I have gone into the administrator/diagnostics and ran everything. Only error is for the eMMC error 99.18.01 but the machine didn't have one to start with and I believe that is why I get this error. If someone can confirm, that would be great.

[Valsimot]

Run an engine test to see will it print. Load tray 2 with paper for running an engine test.

Did you replace the HDD from the same printer model? If you format the disk without firmware upload does printer boot with an error or not?

[Bryan34]

The printer will not run a engine test, it does lift the paper. Format disk and rebooted and the error "99.09.67 Disk not bootable".  The hard drive is a new one from HP.

[Valsimot]

If the engine test isn't printed it's something beyond formatted HDD of the firmware.

Remove formatter and try engine test without formatter. 

It's probably something minor you missed during the first repair.

[Bryan34 · Accepted solution]

Well found the problem, connector J606 on the DC Controller, the ribbon cable was kinked. This caused the unit not to produce a engine test and caused the unit to stay in initializing.  

Thanks for your input Valsimot