Cisco 7970 Bricked
Submitted by SkykingOH on Thu, 05/15/2008 - 4:21pm.
Has anyone successfully "unbricked" a Cisco 7970? I have read every thread I can find in Forums and Usenet, seems everyone has given up.
The phone was working fine SCCP with Call Manager. During the upgrade to SIP after a factory reset the display would no longer initialize and the line appearance keys flash in sequence (green).
The 7970 obtains and IP address and completes the download of term70.default.loads then just sits there. It never requests the software or a configuration file.
Any insight would be appreciated.
Scott
--
Scott
aka "Skyking"
Did You --
Thu, 05/15/2008 - 7:36pm
Scott,
Not sure what SCCP to What SIP you were doing. But I usally have to go way back, and walk them up slowly using after a factory reset. I alway use a cross over and the TFTPD32 widows client so it can't pickup anything strange anywhere.
Here is the order I used on my last set. The FLASH gets rewritten in different formats along the way.
SCCP_603
SCCP_703
SCCP_822
SIP_833SR2
PhoneBuff -----
Thanks guys, I have tried
Thu, 05/15/2008 - 8:10pm
Thanks guys, I have tried with tfpd32 in an isolated environment (just my laptop and phone) and using atftpd.
No matter what version of the software i am using the phone never gets beyond the defulat.loads.
Nothing is ever displayed on the screen. The line appearance lights flash in order orange until a DHCP address is picked up then green. Do matter how long you hold down the # key you never the option to reset the flash.
Sigh....Scott
--
Scott
aka "Skyking"
Your phone is not dead yet
Thu, 05/15/2008 - 9:33pm
I had a 7970 phone with the same problem before. It end up one of the firmware file was corrupted in the tftp server. I'm sure if you have the right firmware files, it can be back to live. Please post your firmware files name. Let's make sure there no missing file there.
Ok, I will do so. I have
Thu, 05/15/2008 - 10:00pm
Ok, I will do so. I have three version of SCCN and two SIP's. I tried them all.
I even looked at the default file with a hex editor to make sure the right files where referenced.
I left the office and am at home now. Will post in the AM.
Thank you very much. It is very encouraging to hear somebody else recovered from this point.
Scott
--
Scott
aka "Skyking"
Good luck
Thu, 05/15/2008 - 10:10pm
just one more idea. If your phone is able to obtain an IP from DHCP, that means the bootrom is not dead. It just same concept of the all other Cisco equipment. As long as the bootrom is still functional, it can be recoveried. All you need is the right firmware and the right procedure. I havn't seen any Cisco equipment is not able to recovery with a working bootrom in the past 10 years.
Yeah I know and that is what
Thu, 05/15/2008 - 10:17pm
Yeah I know and that is what is most challenging. It seems to be not executing the code. I watched all 570 bytes download on the wire with Ethereal, no errors.
I have brought routers and switches back to life after flash failures. However the rom monitor in a router gives you some interaction, you can upload code over the serial port with xmodem. This is a bit more challenging.
I also tried to watch the serial port. I have never been able to get that to work. I made the cable exactly as called for in the Cisco admin guide under troubleshooting. The admin guide says you have to enter cisco to get into the monitor. Several wiki posts indicate that it just posts the same messages as the syslog output. In either case I have never seen anything on the serial port of any cisco phone I have looked at.
One more thing, I also tried provisioning the phone on a production call manager. No dice.
Thanks again....Scott
--
Scott
aka "Skyking"
Probably already know this,
Mon, 05/19/2008 - 5:44pm
Probably already know this, but just in case:
Be sure to do a factory reset via the keypad (power up device holding # key, then enter 1234567890# -- or something of that sort if I recall correctly). Evidently, if the unit has been on Call Manager previously it can load the encrypted firmware instead or something of that nature making a reflash essentially impossible without the aforementioned reset step.
ksDevGuy
Thanks, got that code.
Mon, 05/19/2008 - 7:21pm
Thanks, got that code. That's how it got bricked in the first place.
For any lurkers in the thread the Cisco manual that details this reset procedure is available on the Cisco TAC website at this link.
Scott
--
Scott
aka "Skyking"
Member Since:
2007-12-17