I'm confused by the paragraph that follows step 6:
Code:
The webflash.bin doesn't work on some WNDR3700's and could brick the router, but most are fine. Most likely cause the router is faulty to begin with. To restore from the brick TFTP the stock firmware or a known working build of DD-WRT back from it (-factory.img file).
That file includes the webflash.bin? which is a generic version of sw for the 3700?
Code:
To upgrade to a newer build of DD-WRT, use the web interface and selecting the "wndr3700-webflash.bin" file instead.
Where did I download this 'wndr3700-webflash.bin'? It must be contain within the .IMG file, but the instructions don't clearly align the workflow. (and with so many red warning pixels deployed I'm wanting to be sure I understand the bigger picture up front.
Webflash.bin is the file you flash from the webgui. It is not a special or separate file. _________________ See this:
http://i31.tinypic.com/24mz3ms.png
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.."
With due respect - pointing me to peacock would be fine except that it clearly contains far more information and background than needed. For example, drilling home the importance of the '30-30-30' and 'newer not necessarily better', and 'identify your router model/version then check the wiki for specific instructions' - that's info that clearly belongs.
But expecting me to wade thru a technical discussion of V24 vs. v26 and all that jargon that can't _possibly be digested by someone needing to hear about 30-30-30 (we newbs) - that's just counter productive.
Take this line:
To pick a build, there are three things you need to know.
that's blatantly wrong. In that I've identified my router I've excluded any need to know anything else about which .bin to pick because there's only one for my router. Granted and many other folks arn't as lucky and need further direction but that discussion belongs on the wiki-install page for their particular router.
You guys have a hard job and I respect the work already done. I don't doubt you've taken more than your share of unwarranted abuse by idiots who expect things to be handed on a silver platter and nothing to ever go wrong. (occasionally guilty).
Be sure to understand I'm not whining about being pointed to the newb thread - I'm taking a bit of my own time to try and help make the project better. - cuz I _really do appreciate the time you folks take to help make my home network better.
I'm confused by the paragraph that follows step 6:
Code:
The webflash.bin doesn't work on some WNDR3700's and could brick the router, but most are fine. Most likely cause the router is faulty to begin with. To restore from the brick TFTP the stock firmware or a known working build of DD-WRT back from it (-factory.img file).
That file includes the webflash.bin? which is a generic version of sw for the 3700?
Code:
To upgrade to a newer build of DD-WRT, use the web interface and selecting the "wndr3700-webflash.bin" file instead.
Where did I download this 'wndr3700-webflash.bin'? It must be contain within the .IMG file, but the instructions don't clearly align the workflow. (and with so many red warning pixels deployed I'm wanting to be sure I understand the bigger picture up front.
thx
The wndr3700-factory_NA.img is for going from stock netgear firmware to dd-wrt using a north american model of this unit, after you flash this file, you shouldn't have to flash anything else, just perform your 'reset to defaults' and start configuring. The reason for that file is because it contains header infos which will allow the stock fw to accept it. The webflash.bin is for upgrading to newer or older builds from within the dd-wrt webgui, and is the only time you would need to use those types of files.
I couldn't comment on the WNDR3700v1 and it bricking when using the webflash.bin as i have a WNDR3700v2 and when i use the webflash.bin to upgrade to newer or older builds from within the dd-wrt webgui, it hasn't ever bricked mine, always upgrades and runs its normal course as it should, from what i have read though on the bricking issue, most of the cases seem to be people not performing safe upgrading methods to begin with, over half of the cases i seen is when people try to upgrade builds over wireless, which is a no no - i only recommend upgrading over wireless if its a last choice / or your router switch has becomes non-functional and its the only way you can try minus using a serial connection into the router, and even then i recommend serial the most.
Posted: Fri Aug 10, 2012 14:45 Post subject: Re: Seek clarification of install instructions for Netgear 3
Quote:
The webflash.bin is for upgrading to newer or older builds from within the dd-wrt webgui, and is the only time you would need to use those types of files.
Here's how I'm trying to reason it - Flashing the .IMG file means that DD-WRT is now the interface to the hardware. I could stop there and simply configure according to my needs.
IOW, the .IMG is a baseline implementation of DD-WRT - the .BIN is optional or upgrades that may or may not be relevant to my needs and I shouldn't install it unless I know I want features it addresses, yes?
If the webflash.bin is optional and/or has features considered to be upgrades over stock....where can I learn more about the specific differences contained?
Joined: 14 Oct 2006 Posts: 7 Location: Milwaukie, OR, USA
Posted: Fri Aug 10, 2012 15:14 Post subject:
Hi Steve,
Here is my understanding of the different file versions:
The .IMG file is for when you take a store bought router and replace the vendor firmware with DD-WRT.
The .BIN file is for when you take a router that is already running an old version of DD-WRT and upgrade that.
I partial bricked my WNDR3700v1 by laying the webflash.bin over the top of the .img install, and had to roll back to the vendor firmware and start all over.
Your restatement seems consistent with mine so, on that score, I think I'm making progress. I'd kind of like to put it in terms like:
the .IMG file is the OS that runs the BINs. the webflash.bin can't run on the factory IMG because they are coded to different OS's.
So if flashing to the wndr3700-factory_NA.img means I've installed the new OS but not 'enhanced or upgraded programming'. I'm still left with the question: What's the features to be gained by installing the wndr3700-webflash.bin?
Joined: 06 Feb 2010 Posts: 7016 Location: Little Rock
Posted: Sat Aug 11, 2012 0:37 Post subject: Re: Seek clarification of install instructions for Netgear 3
amSteve wrote:
Quote:
The webflash.bin is for upgrading to newer or older builds from within the dd-wrt webgui, and is the only time you would need to use those types of files.
Here's how I'm trying to reason it - Flashing the .IMG file means that DD-WRT is now the interface to the hardware. I could stop there and simply configure according to my needs.
IOW, the .IMG is a baseline implementation of DD-WRT - the .BIN is optional or upgrades that may or may not be relevant to my needs and I shouldn't install it unless I know I want features it addresses, yes?
If the webflash.bin is optional and/or has features considered to be upgrades over stock....where can I learn more about the specific differences contained?
thx
Your reasoning is incorrect, and you are not reading carefully enough, how could you be on stock firmware and flash from the dd-wrt webgui? Stock firmware doesn't have a dd-wrt webgui..
amSteve wrote:
I'm still left with the question: What's the features to be gained by installing the wndr3700-webflash.bin?
You can learn about it by reading the posts more closely, it answers all of your questions already...you only use those webflash.bin's when you are already on dd-wrt and want to upgrade to a newer or older build, not sure how much more clear i can explain it to you.... _________________ Wireless N Config | Linking Routers | DD-WRT Wiki | DD-WRT Builds | Peacock - Broadcom FAQ
I think I've said the opposite....after flashing the img that i downloaded, I've replaced the stock firmware with DD-WRT. I'm sure my terminology is wrong but that's why I'm using as many words as I am and probably makes me hard to follow. Bu
You say firmware - i say OS. Flashing the IMG gets me to a DD-WRT (you say web-gui, I say 'interface'), right?
This much I've achieved and am logging into Firmware: DD-WRT v24-sp2 (06/08/12) std. But I haven't done anything with the .BIN file. And neither the peacock page nor the 3700 install page explains what additional features are provided by it.
A minimal risk is noted but the reason to take that risk isn't. I'm sure it's clear as day if you already know it. I'm hoping you benefit by watching the reasoning of someone who is trying to understand it because doing would help improve the documentation.
thx - really not trying to be acidic - i've read the stuff you folks have asked me to - i'm just trying to get clarifications.
This much I've achieved and am logging into Firmware: DD-WRT v24-sp2 (06/08/12) std. But I haven't done anything with the .BIN file. And neither the peacock page nor the 3700 install page explains what additional features are provided by it.
If you're successfully logging into the DDWRT version of the firmware you should be done flashing. In the future when the DDWRT firmware is updated, you can use a newer .bin file to update your router if you choose. That's the difference between the .bin file you didn't use and the .img file you did. That's all.
If you're successfully logging into the DDWRT version of the firmware you should be done flashing. In the future when the DDWRT firmware is updated, you can use a newer .bin file to update your router if you choose. That's the difference between the .bin file you didn't use and the .img file you did. That's all.
Now it's clear. That problem i was having related to those couple paragraphs following step 6.(http://www.dd-wrt.com/wiki/index.php/Netgear_WNDR3700)
Making a reference to the webflash.bin before concluding with the sentence ' Now that DD-WRT is full installed....' makes it appear that more work was expected.
