Any solution for a dead wap54g ??

Discussion in 'Other Linksys Equipment' started by NeoSat, Oct 29, 2004.

  1. NeoSat

    NeoSat Network Guru Member

    I've got my wap54g dead, only the Power led (green) and Diag led (red), are on all the time.

    I've red a solution for the wrt54g, is there any for the wap54g


    Neo :?:
  2. u3gyxap

    u3gyxap Network Guru Member

    Few ideas:

    Turn the AP on. Press the reset button and hold it for 30 seconds. Turn the power off, while still pressing the button. Keep it pressed for another 30 seconds. Release and let the device stay UNPOWERED for 36 hours. Then hold the reset button, power on, count to 10, and release the button.
    If it works - remember it will go back to

    If the above steps don't work:
    Just for the protocol - Use it on your own risk. You WILL void the waranty, and you may destroy the device completely. You are responsible for your own actions.

    Open the AP. Find the flash chip. If you cannot, no matter what reason - stop here. If you find it OK - power ON. Short circuit between the flash chip legs with a screwdriver or piece of wire. Make sure you do a good job and take your time doing it. Then power off. Then power on. If it works - remember it will go back to

    If the above steps don't work, you may want to unsolder the flash chip and reprogram it, then solder it back. Usualy done in local electronics shops.
  3. TheRoDent

    TheRoDent Network Guru Member

    Unfortunately, this solution doesn't work for WAP54G V1.0 devices. There seems to be a bug in the PMON configuration where the WAP tries to receive a flash image via TFTP from the vestigial switch, instead of eth1 which is the only actual ethernet adaoter.

    It's very easy to brick a V1.0 device, as there's no way any amount of fiddling and resetting can get it to receive a TFTP image. It's listenening on the wrong ethernet interface :(

    The only possible solution is a serial port, and to then instruct pmon to receive a tftp image from a server elsewhere, after having made some nvram changes to access the correct ethernet device. :(

    Stay away from V1.1 or V1.0 wap54g's...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice