[kernel-panic69]

I think you misread, perhaps(?). I'm advising not to flash both partitions to factory via CLI because someone is going to do it and wonder why they bricked, etc. People can be short-sighted and jump the gun.

[lexridge]

No, I tested that. I flashed both partitions without a reboot and all went well. But the caveats I mentioned are the real gotchas.

[kernel-panic69]

You're overwriting the mounted and booted partition when you do that. Didn't think that was possible without something else involved.

[lexridge]

Yes, you are exactly right. This is the case on my EA8500 (or once was anyway). If you overwrite the booted MTD, all your CLI commands and library access disappear (to name but a few). I know this from experience from actually doing it once.

But not apparently the case here, oddly enough, so I would have to assume the entire filesystem gets transferred to RAM (or at least the needed mtd and reboot bits).

I even went back and tested doing this again after you initially brought it up, just to make sure I hadn't imagined just doing it, and it worked.

If there is a better way to prove/disprove this, give me some ideas and I will try them out.

Be as it may, I am the only person so far to have tried this. I expect it will work for everyone if done exactly right. However, once more folks try this method and we get some more feedback in, I will change/correct the guide accordingly if needed.

[kernel-panic69]

Did you switch boot partitions via CLI between? That's the only thing I can think of that would allow it to work, but hey, this is getting interesting.

[lexridge]

[kernel-panic69]

Ok. Still need to add a separate Wiki for this specific device, as well as M*5500 and add info to the Dynalink and EA8250/MR8250/EA-MR8300/MR9000 Wiki. #alwaysplayingcatchup

[dun4cheap]

Revert To Factory Firmware The method that worked for me.

enable telnet in the webif

telnet to you mx4300
fw_printenv -n boot_part
fw_setenv boot_part 1
cd /tmp
wget http://www.yourwebaddres.com/MX4300FactoryFW.img
mtd -e linux2 -f write MX4300FactoryFW.img linux2

fw_setenv boot_part 2
fw_printenv -n boot_part
cd /tmp
wget http://www.yourwebaddress.com/MX4300FactoryFW.img
mtd -e linux -f write MX4300FactoryFW.img linux

When it reboots if the light is flashing red, be sure to hold the reset button on the bottom until the light turns off.

[lexridge]

[dun4cheap]

It was pretty much the method you posted, but ran it through. I may update the first post in the thread with this information.

[lexridge]

Re-setting the boot partition between flashing (you did not show any reboot in between) made no difference whatsoever. Not sure why you did that. Resetting the boot partition is only necessary when flashing back to OEM onto one partition. If you do both, not needed.

[dun4cheap]

Yes, you are correct I did not reset until the end. So the extra lines are not required. I really need the eoip tunnels working. Should I post an SVN. I believe it is only with the mx4300. Very specific, if a tunnel is enabled and internet is plugged in to the wan port and the wan is set to dhcp. If it is set to static then it boot loops even without a cable plugged in if the eoip tunnel is enabled. I have never seen this on any of my other routers, but it is easily reproduceable.

[lexridge]

[kernel-panic69]

If it's particular to this device, the discussion is fine in this thread. x2 on no SVN ticket.

[nightanole]

So i noticed in open-wrt land that if you use the pure open source drivers, you are limited to about 500mbs. But if you use the proprietary blob you get the full 1000mbs because offloading is enabled.

Has anyone done speed tests on the ddwrt builds, or know which blob is used?