I wasn't able to get past step 3. The last command in step 3 is to issue a reboot command. Is it really necessary to do the reboot before flashing the out.hex? From what I've seen, many of those with flashing issues, myself included, are simply having difficulty in proceding past step 3.
Exactly the same problem here as with hw0012 and alcuin for 2 foneros here
followed LaFonera - a flashing guide, on the wiki to try and get dd-wrt on -
to SSH I plugged straight into PC via ethernet, followed the step1.htm etc, and followed on to the guide.
did step 1-3, reboot command after step 3, got disconnected, power cycled router as it wouldnt boot back up, now cant ping, telnet, access web admin panel,
power light continuously on, wireless doesnt come on, ethernet led continously flashes when plugged into my linksys, ethernet led flashes then stays on when plugged straight into pc.
Iv got a new max232 adapter which I have hooked up to one of my foneros but there is no output at all in hyperterminal, with 9600/8/None/1/None
Max232 is working ok as I have connected the RX and TX cables together to test and get an echo of what Im typing in terminal
Hi Camicia,
I have the serial adapter, but unfortunately it seems to refuse my attempts to issue the Ctrl-C command to get to the redboot prompt; it then proceeds to run
Code:
RedBoot> fis load -l vmlinux.bin.l7
where it fails and locks up. I've tried a variety of different terminal software with the serial cable; Hyperterminal, Putty, and several DOS clients, while booted into DOS. I don't believe it's an issue not sending the ^C command; rather, the fonera seems to just be ignoring it. I do believe your software works, but like you said, I think there may have been an update that makes your software incompatible with some of the routers that have been issued. I just want to find out what the problem is, so I can more easily and safely flash my next fonera. The one I bricked though said it had firmware of v0.7.0.4, so I would have thought that would have been an earlier revision model.
I just got another fonera delivered. This one is a v0.7.1.1/0.7.1.2. Sticker on the bottom says 0.7.1.1. I immediately hooked it up to the serial console, and it gave me all the proper redboot mesgs, but when it asks to press ctrl-c to get to the redboot, I am unable to do so on this fresh new router. So perhaps there is something wrong with my setup; maybe my machine's serial port is wonky or the speed settings are incompatible, or my max202 ttl converter isnt working properly, or my terminal software(putty) isn't setup right.
i too am having problems. i no longer have fon software on it, and can still access redboot via serial port. my problem is i cant seem to get a tftp or http server to run right. i dont know what i should do i want to get software on it, but i tried debricking it with fon software and dd-wrt but when it boots it stops at cmdline: help! ive been workin on this for a few days and still nothing.
Well, most of this is Greek to me, but anyway......I have 2 new Foneras that I'm trying to put DD-WRT on. I'm using the instructions from the DD-WRT Fonera downloads. I'm able to mount the serial console with no problems using the suggested settings in HyperTerminal. I'm able to use Ctrl C to access Redboot, etc. My problem arises when I try to load root.fs via tftp. I get an error saying that my tftp server cannot be located, some sort of network error has occurred. I was able to set the Fonera IP to 192.168.1.1/24 (/24 assigns the Fonera a subnet of 255.255.255.0 instead of 255.255.255.255), and enter my tftp server IP....which is the IP of my PC. I'm doing this in Windows, and have tried SolarWinds tftp server and tftpd32 from the Skynet utility. I've disabled firewalls, etc. What am I missing? My tftp server confirms that its IP is the same as the PC. Why won't the Fonera/Serial console find/communicate with the tftp server? Do I need to be doing this in Linux? Help is appreciated!! Thanks!!
I wasn't able to get past step 3. The last command in step 3 is to issue a reboot command. Is it really necessary to do the reboot before flashing the out.hex? From what I've seen, many of those with flashing issues, myself included, are simply having difficulty in proceding past step 3.
When I followed the Wiki guide, I also had trouble getting past step #3 under the Flashing section. I ran step1.html and step2.html once again after step #3 and then I was able to ssh into the LaFonera to proceed to step #4. This may be due to the fact that I had not followed the steps correctly in the hacking fonera guide to enable permanent ssh access. This might be the stumbling block to those who reboot at step #3, but then loose ssh access when trying to proceed to step #4.
I wasn't able to get past step 3. The last command in step 3 is to issue a reboot command. Is it really necessary to do the reboot before flashing the out.hex? From what I've seen, many of those with flashing issues, myself included, are simply having difficulty in proceding past step 3.
When I followed the Wiki guide, I also had trouble getting past step #3 under the Flashing section. I ran step1.html and step2.html once again after step #3 and then I was able to ssh into the LaFonera to proceed to step #4. This may be due to the fact that I had not followed the steps correctly in the hacking fonera guide to enable permanent ssh access. This might be the stumbling block to those who reboot at step #3, but then loose ssh access when trying to proceed to step #4.
nope mine was perm enabled for sure.
I think the problem is with me i had to use a diffrent dd wrt do to fact the one listed in the wiki is or was gone from the server. So i had to sub a diff one for it. I got one non bricked fonera left the other 2 i just snagged the antennas off and tossed in the trash.
I'm very happy to report that I got a proper serial to ttl converter with a MAX232 chip, and was able to get working access to redboot, and completely fixed my bricked router, and flashed it to dd-wrt 03/23. Thanks everyone for their help!
I'm very happy to report that I got a proper serial to ttl converter with a MAX232 chip, and was able to get working access to redboot, and completely fixed my bricked router, and flashed it to dd-wrt 03/23. Thanks everyone for their help!
Excellent. What did you use for the Fonera IP address and tftp server IP address? That's where I'm hung up. Thanks. _________________ Clear 4G Wimax.
Linksys WRT54G-TM w/14929 std-nokaid, fan-cooled, 2 GB SD mod, Primary Router.
Linksys WRT54G v.3 w/15230 std-nokaid, Client Bridge.
Linksys E2000 w/15200 "Big"
Linksys WRT54G v.4
La Fonera 2100, fan-cooled
Linksys WRT54G v.3.1
Linksys WRT54G v.1.1
Linksys WRT54GS v.1
2x Linksys WRT54G v.2.2
Hi I've succesfully completed all the steps, however at step 9 "write 'exec'"
So "exec" and then enter, doesn't do anything. It doesn't give any output and nothing changes (have left it on for hours - no output whatsoever). So I plug out the power of my fonera and I can still do a "telnet 192.168.1.254" and redo all the steps. But again it keeps getting stuck at "exec". Does it take such a long time? Am I too impatient or is something wrong?
EDIT2:
How do you update? Do you need to reflash?
How?
Same way as you flashed the fon firmware? Easier way?
EDIT3:
I unplugged the powercable but now I can't seem to ssh into it anymore on 192.168.1.1
I can still do telnet 192.168.1.255... (and get the RedBoot prompt).
Help?
Quote:
bt ~ # telnet 192.168.1.254 9000
Trying 192.168.1.254...
Connected to 192.168.1.254.
Escape character is '^]'.
== Executing boot script in 7.050 seconds - enter ^C to abort
RedBoot> ^C
RedBoot> exec
Can't execute Linux - invalid entry address
RedBoot>
And after a while I can reconnect to 192.168.1.1...
How can I make it save? So when I pull out the power or reboot the device it'll automatically get past RedBoot and be at 192.168.1.1 where I can ssh it then?