Cannot restore the original firmware from REDBOOT

[jlj]

I passed many times to restore my system after a misconfiguration.
I followed the procedure described here: onbeat.dk/thecus/index.php/N2100_Recovering_from_a_bad_config_change

I do not know how i was able to restore the original firmware because i can not say that the procedure worked for me..

I was in that case: i was not able to connect via SSH ,nor via the web interface after restarting my box.A reset did not fix the issue..
So , i tried to restore my firmware via redboot..Fortunately the last applied firmware was the 2.1.05 and then i was able to telnet my box..

with this script running on a Windows XP based computer:
Set objShell = Wscript.CreateObject("Wscript.Shell")
Set objExecObject = objShell.Exec("cmd /c ping -t -w 1 192.168.1.100")

Do While Not objExecObject.StdOut.AtEndOfStream
strText = objExecObject.StdOut.ReadLine()
If Instr(strText, "Reply") Then
Exit Do
End If
Loop
objShell.Run("Telnet -t vt100 192.168.1.100 9000")
Do Until Success = True
Success = objShell.AppActivate("Telnet")
Loop
Wscript.Sleep 500
objShell.SendKeys "^C"

Wscript.Quit

The window available to stop the boot process in order to telnet the Redboot code is very very small...That was the only working way to access Redboot .
I tried a debian kernel, pointed in the main link of the document (N2100 Recovering from a bad config change), and the kernel available from the orginal n2100*.bin file.

Each time these 2 commands worked properly:
Redboot> load -r initrd -b 0x00800000
Redboot> load -r vmlinuz -b 0x00200000

but even after 10mn waiting i was not able to have something else than a blink cursor after typing this command:
Redboot> exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=
128M@0xa0000000"

No feedback, no reports of a kernel being launched..And of course not able to connect to the web portal in the meantime ..
I changed the speed to 38400, i changed the terminal emulation mode: same thing..I killed each time my session after 10mn waiting for something.

My 5th try was successfull surprisingly..I rebooted forcefully again but this time i was able to access the web interface after the reboot.
It did not work perfectly in fact ..for example i was not able to get some information about the temperature from the system page.A message reported a missing page..But i was able to upgrade my firmware .
The upgrade worked properly and all the services have been restored.

Unfortunately everything has been restored, even an issue i have had before breaking my box.
The SSHD do not launch automatically at startup.I have to start the daemon manually by disabling and enabling the module via the web ui.

So, my question is: do you have an idea why did the exec command report anything in my case?
A faulty initrd or vmlinuz file?

[dbridges]

Without knowing how you broke it i cant say how you managed to fix it.

In redboot the exec command should have worked however it may need to be altered to take into account that you're not using a console (console=ttyS0,115200) and are in fact using telnet.

Not something i know about but you are welcome to send a polite email to the people doing the debian port and ask them.

If your playing around with the config and new to linux i recommend creating a samba share to the root folder but dont edit any executable scripts through it because they will lose their execute permission.