Embedded Files
New updates and Part Catalog added for exploded view
Root Cause: A Trusted Platform Module is missing from a printer that previously had a TPM installed.
Recommeded Actions:
1. Perform a Format Disk, hit continue in the Pre-boot Menu, power it up, if the error 33.04.05 or 33.04.01 shows up again, please reseat the eMMC or HDD
2. Perform the Format Disk again, and get the unit to power up, it should boot with the 99.09.67, if this doesn’t happen, the corrupted FW is still in the partition of the HDD or eMMC and cannot get recovered
3. Remove the TPM, eMMC/HDD, access Startup Options, perform a Cold Reset
4. Reinstall eMMC/HDD back, access the Pre-boot Menu, access Manage Disk>Boot Device>Erase Unlock, make sure printer fails 99.09.67 at boot up
5. Access Pre-boot Menu, perform that Download of the fresh FW file
6. Printer will reboot to Ready state, print the Configuration Page and check if the TPM is enabled or disabled
Access Pre-boot Menu>Administrator>TPM Config>select Stop Using. If this option is not available, go to step #2
2. Perform a Format Disk, confirm with OK, go back to main menu, select the Continue option, power up the unit, it should fail with 99.09.67, Disk not bootable, meaning there is no FW available
3. If printer keeps booting up with the 33.04.05 or 33.04.01, reseat eMMC/HDD and TPM, attempt the Format Disk once more, if error persists, FW still remains in the eMMC or HDD
4. As an extra step you can diagnose bootable components, enter Diagnostics and run it for all components
5. If Diagnostics passes, remove the TPM, eMMC/HDD, access Startup Options, perform a Cold Reset
6. Reinstall eMMC/HDD back, access the Pre-boot Menu, access Manage Disk>Boot Device>Erase Unlock, make sure printer fails 99.09.67 at boot up
7. Then access Pre-boot Menu, perform that Download of the fresh FW file
8. Printer will reboot to Ready state, print the Configuration Page and check if the TPM is enabled or disabled
9. If printer is not able to print, go back to preboot and confirm the TPM Config. Then address the new unrelated issue
Page updated
Google Sites
Report abuse