I tried following the wiki guide, but unfortunately failed after replacing the boot loader.
Thanks for coming back with feedback. By their nature these instructions tend to be merged together from a bunch of individual installation processes atop varying firmware versions, so every bit of battle-testing helps.
manufactory mode resets ALL configuration, and default password for both telnet and web becomes "admin": "password".
Thanks. I added some weasel words saying this might be the case with some firmware versions. But were you enabling that out of anything besides curiosity? Since the stock CFE accepts bootloader upgrades before even booting, it shouldn't be necessary.
The sentence "Follow steps 1-7 of [CFE] instructions" left me very confused
But the link goes directly to the section "Using CFE web (http) server" section of the CFE page? Anyway, I added the name of the section. There a balance to be struck; if every router page just included chunks of content from generic instructions pages, we'd have a lot of duplication and improvements to the generic content wouldn't make it back to the router pages.
but after upload complete the router just sits there, not even replying to pings.
But power-cycling it brings you back to being pingable? That is, it's not bricked, right? It just doesn't seem to accept the upload? I guess so since you mention uploading two different images. How long did you wait between upload and ping/http access?
Is it an Orange-/EE-branded box? Where does that number come from? If it's not Orange/EE, yes, a picture would be interesting.
Right now I don't have access to a serial connection, so I can't push it further. I would appreciate tips to make it run without serial.
Serial is immensely useful for debugging all sort of things, and gives you emergency console access if you lock yourself out, so I can't recommend it strongly enough. That said, did you try the technique in the troubleshooting section? If the new bootloader sees anything that looks like a keypress in the first few seconds it'll switch to HTTP firmware upload mode. I'd have built a version that defaults to that method already, but (1) personally I always establish serial access before anything else, so it's easy to work around, and (2) it's not clear to me whether danitool patched the source at all to create the bootloader version being used here, and I don't really care to try unless I know we have complete sources.