Pyro Phoenix
Printing Apprentice
- Joined
- Oct 14, 2018
- Messages
- 3
- Reaction score
- 1
- Points
- 15
- Location
- Germany
- Printer Model
- Canon PIXMA MG2950
Hey folks,
I recently got an faulty MG2950 who was throwing me the 5B00 Service Code - so clearly a sign of planned obsolescence. After searching a while, I found a tutorial how to reset the Ink Waste counter to 0 - altogether with a service tool. But nobody was warning me about the possibility to brick my device while using an outdated version of this service tool ... so the things went mayhem.
Now I can't start the service mode - the printer will freeze with orange light when trying to.
Now im curious:
First:
Is there a (public accessible!) way of restoring the service mode apart from exchanging the EEPROM or the whole mainboard?
Second:
Where to order an replacement EEPROM, if there is no other way of restoring the service mode?
Third:
Is this "softbrick" an intended behavior added by Canon to hinder people to extend the lifespan of their property or a side effect of trying to alter the EEPROM content with an outdated service tool. (i.e. service tool writing to the wrong memory addresses - thus resulting in corrupting the EEPROM)
Thanks!
I recently got an faulty MG2950 who was throwing me the 5B00 Service Code - so clearly a sign of planned obsolescence. After searching a while, I found a tutorial how to reset the Ink Waste counter to 0 - altogether with a service tool. But nobody was warning me about the possibility to brick my device while using an outdated version of this service tool ... so the things went mayhem.
Now I can't start the service mode - the printer will freeze with orange light when trying to.
Now im curious:
First:
Is there a (public accessible!) way of restoring the service mode apart from exchanging the EEPROM or the whole mainboard?
Second:
Where to order an replacement EEPROM, if there is no other way of restoring the service mode?
Third:
Is this "softbrick" an intended behavior added by Canon to hinder people to extend the lifespan of their property or a side effect of trying to alter the EEPROM content with an outdated service tool. (i.e. service tool writing to the wrong memory addresses - thus resulting in corrupting the EEPROM)
Thanks!