Wap54g Linksys (problem:()

[xabre]

no wiec tak mam linksysa model WAP54G wersja sprzetowa v2.0 i niestety jak ostatni osiol podczas "zabaw" z firmware popelnilem mega blad otoz wgralem firmware od wersji sprzetowej v.10 :| a dokladnie v1.09.1 i jak sie nie trudno domyslec ap nie dziala :) a konkretnie swieci sie tylko dioda power i nic pozatym do tego ap nie odpowiada ani po stronie wifi ani po lanie:( poprostu DEATH:( i jesli ktos wie co teraz to bylo by fajnie:) ....myslalem jeszcze zeby zrobic podobny numer jak podczac nieudanego flesha np w plytach glownych tz. zeby czesciowo podmienic biosa z innego ap ale nie wiem jak to w srodku wyglada i czy wogole da sie tak wiec jesli ktos ma lub moze zrobic zdjecie srodka swojego ap to tez bylo by fajnie:) (ja niestety mam swojego ap jeszcze na gwarancji wiec puki co nie chce jej tracic) a i jeszcze znalazlem cos takiego na necie tylko nie wiem czy to wogole do tematu czy nie bo strasznie zamotanie jest to opisane :

 

Dec. 29 2004 After flashing a recent (mid december 2004) snapshot of openwrt-linux.trx

into my WAP54G (v1) the device went dead, no WLAN nor LAN activity and both the power

and diag LEDs permanently on. Yes, I ignored warnings like in this thread, stupid, stupid.

Did some more searching on the net and found the WRT54G trick to short pins 15 and 16 of

the flash memory during power-on. But with my WAP54G this produced after appr. one second

of pinging without reply on 192.168.1.1. indeed some ping responses but then the responses

stop and nothing more can be done, regardless whether the short has been removed during

the ping responses. The device does not enter a tftd wait state. Then searched further on

the net and applied to the WAP54G a trick described for the WRT54G by Sveasoft. I applied

from a windows system from a DOS window the command tftp -i 192.168.1.1 PUT <<PC-local

path to a Linksys recent .trx for the WAP54G v1>> a fraction of a second after applying

DC power to the device. A fraction being literally something around half a second. This

worked !!!! Give the device time to re-install itself after the tftpd has announced a

successful data transfer. Of course make sure that the PC has connectivity to the

192.168.1.x subnet. I was about to trash the device but am happy to have searched a

little further on the net. By the way, also Sveasoft's Freya software was not functional

on this device; the LAN was dead but the WLAN was not. Hence this could be easily

restored from the Freya web interface by forcing a system reset (pressing the reset

button some 5 seconds or so) and accessing the device and web interface from a client

tuned to channel 6 with a 'linksys' ssid and all security turned off. Hope this can

revive your WAP54G !! martin, portugal

[M@r3C3k]

no wiec tak mam linksysa model WAP54G wersja sprzetowa v2.0 i niestety jak ostatni osiol podczas "zabaw" z firmware popelnilem mega blad otoz wgralem firmware od wersji sprzetowej v.10 :| a dokladnie v1.09.1 i jak sie nie trudno domyslec ap nie dziala :) a konkretnie swieci sie tylko dioda power i nic pozatym do tego ap nie odpowiada ani po stronie wifi ani po lanie:( poprostu DEATH:(  i jesli ktos wie co teraz to bylo by fajnie:) ....myslalem jeszcze zeby zrobic podobny numer jak podczac nieudanego flesha np w plytach glownych tz. zeby czesciowo podmienic biosa z innego ap ale nie wiem jak to w srodku wyglada i czy wogole da sie tak wiec jesli ktos ma lub moze zrobic zdjecie srodka swojego ap to tez bylo by fajnie:) (ja niestety mam swojego ap jeszcze na gwarancji wiec puki co nie chce jej tracic) a i jeszcze znalazlem cos takiego na necie tylko nie wiem czy to wogole do tematu czy nie bo strasznie zamotanie jest to opisane :

 

Dec. 29 2004 After flashing a recent (mid december 2004) snapshot of openwrt-linux.trx

into my WAP54G (v1) the device went dead, no WLAN nor LAN activity and both the power

and diag LEDs permanently on. Yes, I ignored warnings like in this thread, stupid, stupid.

Did some more searching on the net and found the WRT54G trick to short pins 15 and 16 of

the flash memory during power-on. But with my WAP54G this produced after appr. one second

of pinging without reply on 192.168.1.1. indeed some ping responses but then the responses

stop and nothing more can be done, regardless whether the short has been removed during

the ping responses. The device does not enter a tftd wait state. Then searched further on

the net and applied to the WAP54G a trick described for the WRT54G by Sveasoft. I applied

from a windows system from a DOS window the command tftp -i 192.168.1.1 PUT <<PC-local

path to a Linksys recent .trx for the WAP54G v1>> a fraction of a second after applying

DC power to the device. A fraction being literally something around half a second. This

worked !!!! Give the device time to re-install itself after the tftpd has announced a

successful data transfer. Of course make sure that the PC has connectivity to the

192.168.1.x subnet. I was about to trash the device but am happy to have searched a

little further on the net. By the way, also Sveasoft's Freya software was not functional

on this device; the LAN was dead but the WLAN was not. Hence this could be easily

restored from the Freya web interface by forcing a system reset (pressing the reset

button some 5 seconds or so) and accessing the device and web interface from a client

tuned to channel 6 with a 'linksys' ssid and all security turned off. Hope this can

revive your WAP54G !! martin, portugal

1272028[/snapback]

Też mam swojego AP na gwarancji. Niestety musisz swojego oddać do serwisu innej rady nie ma (przynajmniej mi się tak wydaje).

[adow]

Czesc Mam podobny problem ,

Dokladnie to samo po wgraniu softu i resecie pali sie tylko dioda power i diag . Czy udalo ci sie naprawic go jesli tak to jak to zrobiles

POMOCY

[WaWrzOL]

Poszukaj na elektordzie tam ktos flaszuje AP.