Recover a bicked Device without access to redboot
Posted: Sat Sep 03, 2011 1:59 pm
I had yes "had"(it´s working now) a bricked fonera .
At some point of testing several firmwares there was one that bricked my fonera.
The symptoms were no boot,no access to redboot and i don't have a rs232 ttl cable.
First approach.
Packet capture to try to understand what is going on for this i used Wireshark, connected a direct cable to the fonera and started the capture in promisc mode.
5 sec after I powered the fonera I saw:
From the mac adress of the fonera.
Meaning the fonera did not had an ip address and it was looking for a dhcp server to giver her one.
I started a dhcp server( tftpd32) configured the start ip 192.168.1.254 and the pool was 1 (only one ip) this way the fonera will get the default ip of redboot (192.168.1.254).
After powered the fonera again and had a ping to 192.168.1.254 and it started to reply
Opened putty to the ip 192.168.1.254 and voila redboot working,but all messed up.
I had to changes this values because some were not set.
After this i no longer needed the DHCP server because i forced the ip 192.168.1.254 to be responsive for 10 sec.
Just used the Gargoyle flash toll and its working again.
I hope i did not miss any step because i did not save the log of putty
Hope this helps some one with a bricked device without access to redboot.
At some point of testing several firmwares there was one that bricked my fonera.
The symptoms were no boot,no access to redboot and i don't have a rs232 ttl cable.
First approach.
Packet capture to try to understand what is going on for this i used Wireshark, connected a direct cable to the fonera and started the capture in promisc mode.
5 sec after I powered the fonera I saw:
Code: Select all
source address:0.0.0.0 destination:255.255.255.255
Meaning the fonera did not had an ip address and it was looking for a dhcp server to giver her one.
I started a dhcp server( tftpd32) configured the start ip 192.168.1.254 and the pool was 1 (only one ip) this way the fonera will get the default ip of redboot (192.168.1.254).
After powered the fonera again and had a ping to 192.168.1.254 and it started to reply
Opened putty to the ip 192.168.1.254 and voila redboot working,but all messed up.
I had to changes this values because some were not set.
Code: Select all
fco -d bootp
false
fco -d bootp_my_ip
192.168.1.254
fco -d bootp_my_ip_mask
255.255.255.0
fco -d boot_script
true
fco -d boot_script_timeout
10
Just used the Gargoyle flash toll and its working again.
I hope i did not miss any step because i did not save the log of putty
Hope this helps some one with a bricked device without access to redboot.