I want to mention that in my testing in some cases going from factory to dd-wrt flashed fine, and the only thing that was needed was after at least 5 minutes or so, (you MUST give the router enough time to both complete the flash AND rebuild the variables = 5 to 10 minutes or you will brick it!) a simple power cycle is needed then the router is fully dd-wrt operational..

I wanted to point this out, just incase someone flashed a new build and thought it bricked there router.. AGAIN a simple power cycle about 5 minutes after initial flash has completed and you are golden.

Enjoy,

-Fractal

Edit: Thanks Murrkf

PS.... A special thanks to EKO for the super fast commits to svn to make these available.

Last edited by Fractal on Sat Apr 07, 2012 16:32; edited 1 time in total

Please be cautious on uploading these builds. Failing to wait is the principle cause people brick their routers. There needs to be either a visual indicator of completed flashing such as access to the webgui, front lights or pinging, that indicates complete nvram rebuild and safe to reboot, or increase the wait time to ten minutes.

My standard comments:

This build thread is for reporting successes and problem with loading this experimental test build. This is important info for developers and users. Always state your hardware and SPECIFIC build. (eg: 18946_NEWD-2_K2.6_mega-nv64k.bin).Do not ask questions about your specific router or how to configure it in this thread; create your own thread to discuss any specific problems you have or need resolved. This thread is to report info, not to seek it. Posts that do not add to understanding this build will be deleted. Make sure you know how to flash properly and the risk before using this build. It is important to adhere to these requirements, to keep this thread from becoming impossibly long and useless. If you don't know what build to flash and how to flash properly and have a means of recovery if things should go wrong, do NOT flash this experimental test build._________________SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor. So See these:

LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."

Last edited by Murrkf on Sat Apr 07, 2012 16:59; edited 1 time in total

Eko can maybe do a clarification about the protection mechanism against flashing wrong type of build.

I take it that routers with 32KB nvram do not understand nv60k or nv64k and will reject upgrade attempts of those.
I assume that an nv60k router does not accet a 32KB nvram build nor does it accept an 64KB nvram build , and that an nv64k router has the same protection against 32KB and 60KB nvram builds.

If my assumption is right then there is no way to brick these routers with the wrong nvram type build as long as you use the web gui for updates.

Eko?_________________You don’t really own a device until you can open it up and tear it apart

Well, after testing for about three hours I haven't been able to get the build to load successfully on an RT-N66U.

What I initially tried:
Using Internet Explorer, I reset the router to as close as stock as possible, running AP Mode. Downloaded the .trx build for initial flashing. Went to the firmware page and flashed the .trx (dd-wrt.v24-18946_NEWD-2_K2.6_mini_RT-N66U.trx) build. After waiting 15 minutes, I saw that the LED Lights for Power, my LAN port, and Wireless 2.4GHz radio was on. Waited 15 minutes, held the reset button for 20 seconds and then it initiated the router recovery mode on it's own. Turned the router off, waited thirty seconds, and then plugged it back in.

Setup a static IP of 192.168.1.2, and was unable to ping 192.168.1.1 (what I assume should still be the default IP Address after reboot). This would either respond back with one of two (or both messages) Request Timed Out & Destination Host Unreachable. I wasn't able to reach the WebGUI either. Nor did I see any wireless signal broadcasting with the default dd-wrt as I have for my other builds.

Then I tried flashing the .trx build using ASUS's firmware restoration utility, this proceeded to the same issue.

I was able to restore the ASUS firmware after testing this so I still have a functional router, just not using dd-wrt.

I didn't see any point in attempting to flash the .bin image via the firmware restoration utility. I can try TFTP'ing however, it seems to me that it wouldn't work. If I am doing something wrong for this build/router, let me know please and will re-work my test.

I was running the stock ASUS 3.0.0.3.108 firmware when I was attempting to flash the new DD-WRT build.

Ok, I went and took my N66U to factory firmware
3.0.0.3.108 - ASUS Firmware

after that I did the firmware upgrade, did the whole 3 minute wait, everything... the router will reboot and boot up as expected... HOWEVER! even doing hard reset and WPS selection does not allow dd-wrt to load successful. I am able to load dd-wrt and get everything working only if I break into the CFE and issue a nvram erase, then nvram commit.

I have attached serial boot log, and it shows everything I did and how it got to work.. I will go over this with Eko and see if there is something that needs looked at.

I was able to flash the firmware no problem, but the 5Ghz radio doesn't show up - should it show up in this build. I've tried a few resets - still doesn't show up.

Linksys E2500
dd-wrt.v24-18946_NEWD-2_K2.6_mini-e2500.bin

I had been following Fractal's other E2500 test build thread and didn't see where he had reported 5ghz working in the built firmware, so I wasn't expecting it to. Confirming that it does not work on my E2500 either.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou can attach files in this forumYou can download files in this forum