It all started when i was thinking about using the linux shell inside my AP, which sounded (and still) like a very exciting idea since i could change things directly from the AP without the need for the very limited web interface.
however, since this required a cable of some sort and due to my poor ability to arrange such a tool i unwillingly dropped the AP shell idea, until i found out of proprietary firmware updates that granted this ability like AP router(http://www.aprouter.com.br) and Wive(http://rtl8186.sourceforge.net/).
i read about those and found wive to be more appropriate since its free and should have larger supporter community.
however after selecting the firmware file from my web interface firmware update choice i was severely disappointed to see my AP didnt came up again. and thought to my self that i have "bricked" my AP and could see those posts on different forums advising people on such issues by suggesting the use of the bricked device as a $xxx paperweight. i was devastated.
however i read aday later that some APs upon holding the reset button before turning them on and keeping on pressing that button for few seconds then letting go of the button, the AP will enter a special mode during which it will start a tftp server(trivial FTP) and assume an address of 192.168.1.6. it will blindly accept anything sent to it (via tftp client, eg try tftpd32) be it a firmware or an mp3 file however, u shouldnt send anything other than firmwares since after the upload the AP will attempt to burn it to its EEPROM and i dont know what will happen if u upload things other than the firmware. Heck, even if u do upload a firmware theres no guarantee that it will work.
anyways i tried that and it worked! i got euphoric and retried that other firmwares and found AP router to be the best in this field...with a major flaw, it is licensed and will kill u to get registered, eg it will make an SSID with UPLOAD YOUR LICENSE or something like it and will not save anything u change and some say it disables the whole radio.
in my effort to activate it and while trying to make it save changes and detect wireless signals around i got my self into a problem i never thought existed!
i managed to get several license files for other users, noticing the file names and the contents of the file, i knew i wouldnt be able to do anything to license my firmware but wat the hell, i decided to give it a shot, i renamed the file to corrospond to my APs MAC address but didnt change any of the contents of the file and uploaded it as a license...thinking the firmware will simply ignore the file and display the invalid license message, i went on and pushed the upload button...but to my surprise the message didnt appear and the file was accepted...upon refreshing the MAC address of my AP was now the one in the license file and if i attempted to change anything and select to apply the changes the all changes would be lost but the MAC woudlnt be changed.
this is when i ruled out AP router as a firmware, returning to my orignial firmware it installed flawlessly but the wireless part of the AP didnt work...it didnt scan networks, create SSIDs or join networks. in the midst of confusion i noticed that the MAC address is still the same as the one i uploaded in the license of AP router firmware, this persisted through several firmware updates and blankings of the EEPROM. attempts to return to AP router failed since it continuously refused to save and apply my changes...this is when i lost hope and the Bricking issue began coming true... later i tried to scan networks with one of the original firmwares and it did scan and showed the available networks but the LED of the wireless activity never blinked and remained off?!!
someday i hope i can figure out wat happened.
Bottom Line: DO NOT GAMBLE ON LICENSING FIRMWARE IF UNSURE, ITS NOT LIKE NORMAL PROGRAMS
Smilar pages
however, since this required a cable of some sort and due to my poor ability to arrange such a tool i unwillingly dropped the AP shell idea, until i found out of proprietary firmware updates that granted this ability like AP router(http://www.aprouter.com.br) and Wive(http://rtl8186.sourceforge.net/).
i read about those and found wive to be more appropriate since its free and should have larger supporter community.
however after selecting the firmware file from my web interface firmware update choice i was severely disappointed to see my AP didnt came up again. and thought to my self that i have "bricked" my AP and could see those posts on different forums advising people on such issues by suggesting the use of the bricked device as a $xxx paperweight. i was devastated.
however i read aday later that some APs upon holding the reset button before turning them on and keeping on pressing that button for few seconds then letting go of the button, the AP will enter a special mode during which it will start a tftp server(trivial FTP) and assume an address of 192.168.1.6. it will blindly accept anything sent to it (via tftp client, eg try tftpd32) be it a firmware or an mp3 file however, u shouldnt send anything other than firmwares since after the upload the AP will attempt to burn it to its EEPROM and i dont know what will happen if u upload things other than the firmware. Heck, even if u do upload a firmware theres no guarantee that it will work.
anyways i tried that and it worked! i got euphoric and retried that other firmwares and found AP router to be the best in this field...with a major flaw, it is licensed and will kill u to get registered, eg it will make an SSID with UPLOAD YOUR LICENSE or something like it and will not save anything u change and some say it disables the whole radio.
in my effort to activate it and while trying to make it save changes and detect wireless signals around i got my self into a problem i never thought existed!
i managed to get several license files for other users, noticing the file names and the contents of the file, i knew i wouldnt be able to do anything to license my firmware but wat the hell, i decided to give it a shot, i renamed the file to corrospond to my APs MAC address but didnt change any of the contents of the file and uploaded it as a license...thinking the firmware will simply ignore the file and display the invalid license message, i went on and pushed the upload button...but to my surprise the message didnt appear and the file was accepted...upon refreshing the MAC address of my AP was now the one in the license file and if i attempted to change anything and select to apply the changes the all changes would be lost but the MAC woudlnt be changed.
this is when i ruled out AP router as a firmware, returning to my orignial firmware it installed flawlessly but the wireless part of the AP didnt work...it didnt scan networks, create SSIDs or join networks. in the midst of confusion i noticed that the MAC address is still the same as the one i uploaded in the license of AP router firmware, this persisted through several firmware updates and blankings of the EEPROM. attempts to return to AP router failed since it continuously refused to save and apply my changes...this is when i lost hope and the Bricking issue began coming true... later i tried to scan networks with one of the original firmwares and it did scan and showed the available networks but the LED of the wireless activity never blinked and remained off?!!
someday i hope i can figure out wat happened.
Bottom Line: DO NOT GAMBLE ON LICENSING FIRMWARE IF UNSURE, ITS NOT LIKE NORMAL PROGRAMS
posted by circoficus at 8:18 PM
2 Comments:
Hey dude, u can now recover your AP:
http://www.areawireless.net/rtl8186/english.htm
hi me like if they could help me get my AP enrxwi-g after having upgrade badly C3 firmware, you can not access the lei can be done via JTAG cable, if someone has information that procedure would be appreciated. now, thanks
Post a Comment
<< Home