@Flashadmin, I truly understand how frustrating this situation must be, and I appreciate your patience and the detailed troubleshooting steps you’ve already tried.
Since your HP Smart Tank 530 is stuck in an update loop and is being detected as "HP Firmware Update Device," it appears the printer is in a recovery mode but is unable to complete the process. At this stage, let’s explore a few advanced recovery methods:
Perform a Forced Firmware Recovery Mode Update
Download the Latest Firmware
- Visit the HP Software & Drivers page and enter your printer model (HP Smart Tank 530).
- Download the latest firmware update utility for Windows.
Prepare the Printer
- Ensure the printer is powered off.
- Connect it to the computer using a USB cable (avoid using hubs).
Enter Recovery Mode
- Press and hold the Power + Cancel + WiFi buttons simultaneously.
- While holding the buttons, turn the printer on.
- Wait until the printer is recognized as HP Firmware Update Device.
Run the Firmware Update Utility
- Open the firmware updater and check if the printer appears in the list.
- If it does, proceed with updating the firmware again.
Try a Semi-Full Reset (If Screen is Responsive)
If the touchscreen is responding:
- Go to Setup > Printer Maintenance > Restore and select Restore Factory Defaults.
- If you can’t access the menu, try pressing Power + Cancel + Resume for 15 seconds to reset the printer.
Check for Firmware Recovery Tools
Some HP printers have a hidden Recovery Tool that can be triggered:
- Turn off the printer.
- Hold down the WiFi + Resume buttons and turn it on.
- Release the buttons once the HP logo appears.
- If successful, the printer may enter a firmware recovery mode and allow you to reload the firmware.
If the Issue Persists
Since you mentioned removing the CR2032 battery, it’s clear that some settings are still retained. This could indicate a deeper firmware corruption. Unfortunately, HP does not provide public tools for direct NAND flashing or JTAG recovery, and any third-party tools could risk permanently bricking the device.
I appreciate your patience, and I sincerely regret the inconvenience this has caused. Please let me know if any of these steps help!
Did we resolve the issue? If yes, Please consider marking this post as "Accepted Solution" and click "Yes" to give us a helpful vote - your feedback keeps us going!
Best regards,