I successfully flashed a Netgear WNDR3800 with no problem. Sadly, at some point it stopped working.
After a lot of trial and error, I was able to get it into failsafe mode and connect in a terminal window by telnet. I see the Gargoyle screen, but cannot enter anything on the command line because the keyboard inputs are not accepted at the root@(none):/# prompt. If I send the escape sequence, I get back to the telnet> prompt, and the keyboard input displays once again.
Why can't I enter anything at the router's command line?
Thanks.
No Keyboard Input in Failsafe
Moderator: Moderators
Re: No Keyboard Input in Failsafe
If it is prompting you for a password, key strokes are not shown on screen but are still registered.
If it is any other prompt you may need a serial recovery.
If it is any other prompt you may need a serial recovery.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
Please be respectful when posting. I do this in my free time on a volunteer basis.
-
- Posts: 22
- Joined: Wed Apr 27, 2016 6:14 pm
Re: No Keyboard Input in Failsafe
Thanks.
It worked a little oddly. I did not know the password. But when i went back to access it again, it didn't ask for it. Go figure.
Not showing the password caused all sorts of problems; can't tell what is going on, can't tell how many keystrokes were entered, can't figure out what the password should be, etc.. Perhaps not as well thought out as one would wish.
Anyway, I got in and then just restarted the device. It appeared that just getting into failsafe and restarting was all that was needed to unbrick it.
Someone may wish to mention these facts in the failsafe instructions.
It worked a little oddly. I did not know the password. But when i went back to access it again, it didn't ask for it. Go figure.
Not showing the password caused all sorts of problems; can't tell what is going on, can't tell how many keystrokes were entered, can't figure out what the password should be, etc.. Perhaps not as well thought out as one would wish.
Anyway, I got in and then just restarted the device. It appeared that just getting into failsafe and restarting was all that was needed to unbrick it.
Someone may wish to mention these facts in the failsafe instructions.