Bizhub 361 CD203 error.

[mjunkaged]

OK for clarity, if you have a problem with "License management error" in _ANY_ machine type, please follow procedure below.

1. Go to the service mode and change machine serial number to A0R6021006374 (must be uppercase)
2. Reboot the machine (turn off/on main power switch)
3. Go again to the service mode, then [STOP]->[9], then [License Management]->[Initialize]
4. Use following initialization code: 2VRA4-UGGA2-Z2H4K-7AVUH-F58SW-J2Z7U-QVKVK
5. Reboot machine again
6. One more time go to service mode and set back your original serial number
7. Last reboot, and you should have no error


ANY means:
Bizhub 421/501
Bizhub 601/751
Bizhub 223/283/363/423
Bizhub 552/652
Bizhub 224e/284e/364e
Bizhub C203/C253/C353
Bizhub C220/C280/C360
Bizhub C224/C284/C364 also 'e'
Bizhub C454/C554 also 'e'
and so on...

I'm really starting to like this Allan guy!!

[allan]

Credit should go to the original poster.
This has been reposted so many times know one knows...

[mjunkaged]

Credit should go to the original poster.
This has been reposted so many times know one knows...

OK, thanks to the original poster! Wherever you are!!

[allan]

Ok remeber now. If you cant use a cf-card from one machine in the next. That is when you get the password problem.
So when you changed the board and used the existing CF-card you created the problem just do the CF-card recovery again and it should be sorted.

[mjunkaged]

Ok remeber now. If you cant use a cf-card from one machine in the next. That is when you get the password problem.
So when you changed the board and used the existing CF-card you created the problem just do the CF-card recovery again and it should be sorted.

I'm going to fix the license issue first, then what's the latest firmware version for 361, do you know? I'm not sure what my version is, as the executable had a different name. I have ver. 11, and not sure of the version I have that's latest because the executable is named '361US_m1g2100.exe, which when executed shows 'A0R7011m1g21000 (on mfp controller files)'. I got these from a different copytech poster for a previous machine's issue.

[Phil B.]

Credit should go to the original poster.
This has been reposted so many times know one knows...

yes Yoda... but it is the memory and search factors... read yes... forget NOT!

good job Bro!

[Phil B.]

I'm going to fix the license issue first, then what's the latest firmware version for 361, do you know? I'm not sure what my version is, as the executable had a different name. I have ver. 11, and not sure of the version I have that's latest because the executable is named '361US_m1g2100.exe, which when executed shows 'A0R7011m1g21000'. I got these from a different copytech poster for a previous machine's issue.

well please do keep us updated.. but frankly seeing the procedures posted by Allan.. you might have it

[mjunkaged]

well please do keep us updated.. but frankly seeing the procedures posted by Allan.. you might have it

Right, but two different issues, so maybe I can access admin modes after the license snafu gets cleaned up!

[mjunkaged]

Ok remeber now. If you cant use a cf-card from one machine in the next. That is when you get the password problem.
So when you changed the board and used the existing CF-card you created the problem just do the CF-card recovery again and it should be sorted.

To be clear, except for inserting a recovery CF card in place of the existing one, it should normally be flashed using the rear USB and a stick. What you're saying is it's a bad idea to take the cover off with FOUR SCREWS holding it on (two now) and just swap cards from other machines willy-nilly, even the same model #, or password corruption and other issues will occur, right?
If memory serves me, I tried first recovery CF, NG, then when I went back with parts I tried to swap over NRB + CF from existing (bootlooped) OACB and did not work/clear error code. ONLY after I 'borrowed the donor NRB (I think) that kicked it in the butt. Donor was 501, not 361.

[allan]

I would try the CF-card recovery first. And then worry about the license issue is at all.
Don't think its you firmware.
Got no clue about firmware ver on these machines. I would have thrown it with a brick by now!