Later on, in October 2016, and facing appreciable backlash attributable to its actions, HP reversed the built-in firmware lock with a software update that pressured customers to search for the suitable software manually on HP’s web site after which install it on their printers. Authentic cartridge authentication is finished by way of an unique HP safety chip, which is checked towards safety programs embedded on the printer in order to verify the cartridge’s authenticity. The corporate itself admitted that “A cloned product with an unique HP safety chip will work,” and that “HP’s dynamic safety acknowledges refilled and remanufactured provides that include the unique HP safety chip.” HP apologized, on the time, for what it referred to as “miscommunication” on their half. Their apology, nonetheless, has been thrown on the weeds by now; we right here at TPU did say that customers ought to “(…) stay cautious of any eventual future replace that may break non-original cartridge compatibility – once more.”
The firmware replace was first noticed earlier this week and impacts quite a few OfficeJet fashions together with the OfficeJet 6800, OfficeJet Professional 6200, 6800, 8600, and OfficeJet Professional X 400/500 sequence. In line with German provider Tremendous Patronen, over 50 clients have reported issues utilizing third-party ink. The issues are made clear by a pop-up window that claims the cartridges getting used are broken, suggesting customers take away them and change them with new ones. Additional throwing some smoke into the combo, some customers are reporting that having a minimum of one HP-branded cartridge put in suppresses the error message.
Apparently, nonetheless, this is not such a draconian scenario as the unique; a comparatively easy repair to permit continued use of cheaper cartridges is offered, by way of the application of a specific firmware update that disables HP’s Dynamic Security feature. The repair is supplied by HP themselves, and is accompanied by documentation. This might merely be a case of a firmware bug that’s bringing this challenge up once more – ought to we give HP the advantage of the doubt?Source: HP Help