I found the answer!! This one is cryptic. I was taking shots in the dark and lucked out. Apparently, one of the registers in basic rom monitor mode had been changed. I found a document that happened to list some of the default register settings that you can access when you see the following...
> ?
$ state Toggle cache state (? for help)
B [filename] [TFTP Server IP address | TFTP Server Name]
Load and execute system image from ROM or from TFTP server
C [address] Continue execution [optional address]
D /S M L V Deposit value V of size S into location L with modifier M
E /S M L Examine location L with size S with modifier M
G [address] Begin execution
H Help for commands
I Initialize
K Stack trace
L [filename] [TFTP Server IP address | TFTP Server Name]
Load system image from ROM or from TFTP server, but do not
begin execution
O Show configuration register option settings
P Set the break point
S Single step next instruction
T function Test device (? for help)
Deposit and Examine sizes may be B (byte), L (long) or S (short).
Modifiers may be R (register) or S (byte swap).
Register names are: D0-D7, A0-A6, SS, US, SR, and PC
At the bottom, you can see the register names. Like I said, I found a document that had some default settings for these registers. Basically I decided to enter them one by one. Fortunate for me, I tried the PC register first with its default value of 0x02004adc. I rebooted and bam!! I was back to good old fashioned router>. I hope that this is of no help to anyone, but I will list the default values here any way.
d0 - 0x00000028 a0 - 0x0ff00420
d1 - 0x00000007 a1 - 0x0ff00000
d2 - 0x00000007 a2 - 0x02004088
d3 - 0x00000000 a3 - 0x020039e6
d4 - 0x00000000 a4 - 0x02002a70
d5 - 0x02003e8a a5 - 0x02003f17
d6 - 0x00000000 a6 - 0x02003938
d7 - 0x00000001 a7 - 0x0200392c
pc - 0x02004adc vbr - 0x02000000
I hope that none of you ever find your way to rom monitor hell!!