Hello.
I have a Kyocera FS-C5350DN printer, which showed a message about the need to replace the Y toner. I replaced the toner and even put 3 different ones and it was still the same. Then I took the printer apart and cleaned it properly, the problem was for sure because the powder was killed in all possible places. After cleaning, the toner traveled freely from the container to the developer, but the message to replace the toner remained. The last thing that came to my mind is to clean the developer. There was a powder inside the developer, but it was brown rather than yellow. The developer was flooded with a new one.
The printer now shows Call Service 7404.
I had the same problem a year ago and the printer went to the service - they fixed it, but it seems that the developers did not replace it (because the powder would be in better condition) and the blue cap is broken (so I conclude that they did not even look there). I think they did a developer reset in service mode and the printer came to life.
People who revived their developer and solved a similar problem, please help and give a specific hint. Thank you.
I have a Kyocera FS-C5350DN printer, which showed a message about the need to replace the Y toner. I replaced the toner and even put 3 different ones and it was still the same. Then I took the printer apart and cleaned it properly, the problem was for sure because the powder was killed in all possible places. After cleaning, the toner traveled freely from the container to the developer, but the message to replace the toner remained. The last thing that came to my mind is to clean the developer. There was a powder inside the developer, but it was brown rather than yellow. The developer was flooded with a new one.
The printer now shows Call Service 7404.
I had the same problem a year ago and the printer went to the service - they fixed it, but it seems that the developers did not replace it (because the powder would be in better condition) and the blue cap is broken (so I conclude that they did not even look there). I think they did a developer reset in service mode and the printer came to life.
People who revived their developer and solved a similar problem, please help and give a specific hint. Thank you.