well the part of getting into the router control panel works, now all that is left is to re-flash the default netgear firmware. I tried doing that through the openwrt control panel's firmware section, says its the wrong format
I can the tftp server method using tftpd32/tftpd64, but first few times I did kept giving me an error, and I had all my computer firewalls turned off; anything I can change that I am forgetting?
worry not @MonfGeiger, the cap stays where it is.
you had a great lesson with such a small price. i reckon to take a step back, sleep over it and plan forward.
What is it you want out of your router?
once you know, make informed decisions and act accordingly.
OpenWrt is quite powerful and i'm sure you can get almost anything out of it.
and if you are in need of a little help here and there along the process, OpenWrt has a neat and knowledgeable community to discuss it with.
If I decided to keep OpenWRT as my main firmware, I planned on configuring it to be a little more secure than what options the Netgear firmware provided, seeing which packages I would need to install to do so; also, maybe figure out how to get printing working with OpenWRT and my families windows computers
but again, until I can get my father to accept this as a possibility, ill need to figure out how to re-flash the netgear firmware back to the router (tried the tftp deal with windows, keeps failing, will try on the linux side)
I know I appended the title as solved, but I want to "soundboard" this idea here before I really commit to it
I looked through the sub-forum here on someone wanting to re-flash their linksys firmware, and he was told to follow these steps
cd /tmp
wget link-to-stock-firmware
sysupgrade -F -n /tmp/stock-firmware-file
from what I read, this person succeeded, but it also created a second partition, giving the router 2 firmwares (default firmware, and openwrt firmware). I seek to use the syspgrade command, but I want the netgear firmware to be the only one; is there a set of commands I can use to ensure that the netgear firmware is the only one on the router when I go to flash, or if not and I have 2 firmware partitions, can I erase the openwrt firmware afterwards using the wipefs command?
Can you provide that thread?
I think the person(s) you refer to had a device that includes 2 OSes (active and backup) from the OEM.
from what I researched with netgear, it says I need to use the tftp client for windows and/or the tftpd32/64 program from what the netgear knowledge-base says
but if I can use the sysupgrade package to do the same, if maybe with a few extra steps before hand, then al the better, unless I should stick with tftp instead?
Yes, the model in the post has two partitions from the OEM. The OP's subsquent problems were that the device rebooted into the other partition after an issue.
I suggest you use TFTP. It's not that hard. You might brick your router trying to sysupgrade. There's no need to take the risk when a known solution works.
The OP in the other thread also noted that they had flashed both partitions. If you only flash your router once, the stock firmware should still be there, though. Use the procedures to switch to the other partition ( luci-app-advanced-reboot or the 3-failed-boots method).
I installed the luci-app-advanced-reboot, and this is what it told me when I selected it in the openwrt control panel
You want me to risk it anyway, or try and make tftp work? I tried the tftpd32/64 app before, but as before, when I followed the netgear instructions to the letter, it kept changing the server instance box to 127.0.0.1, and when I switched back to my configured ethernet, it says "something something 10025 error something", I forget
maybe I was missing some router packages that would've made it easier; I can try again, but I can't guarantee a success if it keeps messing with me
luci-app-advanced-reboot supports these https://git.openwrt.org/?p=project/luci.git;a=blob;f=applications/luci-app-advanced-reboot/README.md;hb=HEAD routers at the moment, if yours isn't on the list, it isn't supported and would need device specific additions. However, giving the device page in the wiki and the flash layout a casual look, I don't see that your device actually has dual-boot support - meaning that luci-app-advanced-reboot won't be useful here (I think lleachii mixed up the wndr4700 with the wrt3200acm).
Thanks, I didn't mix them up...I took the OP's words implying 2 partitions are somehow there...
I think the OP should better explain this concern regarding:
At this time, is the router flashed with OpenWrt or OEM firmware?
luci-app-advanced-reboot only touches devices for which it knows exactly how their dual-boot settings need to be configured (device white list, with their corresponding mappings), it doesn't try to detect anything automatically (which would be pretty dangerous).
When I did this topic (sorry if I didn't say it good enough), I flashed the OpenWRT firmware onto my netgear router (which before I did so, was running default OEM firmware)
So yes, the router WAS running OEM firmware, but is now running openwrt firmware; if I need to provide anymore details I should've, say so and it shall be done
I tried netgear's way of flashing firmware with the tftp64 program and connected with an ethernet cable, and when I clicked PUT when the power icon was flashing, it said "something error 10054, connection was forcibly closed by remote host"
is it some setting I need to change with the openwrt control panel to allow tftp64 to do what I want it to do, or is it something else?
Your device shouldn't be booted into OpenWrt at the time TFTP begins.
im going to try again while its powering up, but I swear, if that's how I need to do this, and if it works, im going to face-palm myself back to freshman year in highschool for not noticing this earlier
I'm running the tftpd64 flash as its powering up, selecting my ethernet connection, and the progress shows block#0, and no progression, just hangs until I click the break button. Last time this happened and I broke the connection, I could still enter the openwrt control panel fine, so I can only guess that nothing is happening while the program runs the PUT command. So I tried the tftp command-line argument tftp -i 192.168.1.1 PUT NameOfFirmware.img while it was powering up, 30 seconds later, tftp said connect request failed. For some reason, any tftp-argument is not connecting at all; I have one ehternet cable plugged into my computer, and the other end into one of the router's ethernet ports (not the ethernet port designated for internet); could it be a simple port connection snafu, or did something break in a way I can't un-break?
TL;DR tftpd64 and tftp cmd-argument failed, wat do?
Try using the WAN port.
so do the tftpd64 program, but use a wireless connection instead? Ok, ill try that in a bit and reply with results
No! You must use an Ethernet cable. I'm not sure how you concluded that.
I tried the WAN port just now. Couldn't do anything, couldn't connect to the openwrt control panel, couldn't tftp from the command line, and I ran a ping to the router, and it came back with a 50% packet lost. Overall, my attempt at using the WAN port had the same fail results as I've been reporting