1Feb/1023
Updating the firmware on a Virgin WGR614v9 router
Having been a Virgin Broadband customer for almost two years and dealing with the routers frequent drop outs (appears to reach a maximum number of connections) when multiple users are using BitTorrent or likewise I had before searched for fixes for the WGR614v9 router. However, this router supplied by Virgin is locked to their own custom firmware (read: no improvements or even a new graphic). So how to update the firmware. Bit of googleing and came across this thread on how to do it, which is rather lengthy, misses some detail, an app and feedback. So, how to update:
Firstly:
- Only use Internet Explorer (Firefox fails with this router for some reason)
- Know your way around the routers admin panel (default ip is http://192.168.1.1 , username: virgin, password: password)
- Connect via a wired connection, wireless will fail.
- Have a telnet client (default activated in xp, needs activating in vista/win 7 from control panel, 'Turn Windows features on or off'
- Aquire telnetEnable.exe from either mirror or local
Then:
- Acquire the routers MAC Address (Maintenance -> Router status -> LAN port -> MAC Address), then save it somewhere, removing colons ( : ).
- Copy the MAC Address to the clipboard
- Open a command line window, navigate to where you stored telnetEnable.exe and execute: telnetenable.exe 192.168.1.1 *MAC-address-from-clipboard* Gearguy Geardog
- You have now enabled telnet on the router, telnet to the router by executing: telnet 192.168.1.1
- At the prompt execute: burnboardid U12H094T00_NETGEAR
- then execute: reboot
- You have now successfully unlocked the router from the Virgin firmware lock.
- Flash the router using the router admin page, the latest firmware can be located here
April 9th, 2010 - 13:20
Thanks so much for this, worked great! Just one thing, in step 3 in the ‘then’ section, you may want to add that 000FB5A2BE26 needs to be replaced with the MAC address copied from 2.
April 9th, 2010 - 16:40
np Steve and thanks for the info. updated step 3.
May 3rd, 2010 - 09:00
I does not work for me,
I have this line: telnetEnable.exe 192.168.1.1 0024B22BA2E9 Gearguy Geardog
When I click on Enter it comes back very quick without any errors, but when I try to connect to telent 192.168.1.1 it thinks about it for some time then nothing happens.
June 3rd, 2010 - 17:11
This was great. Thanks for the tutorial!
August 11th, 2010 - 15:33
Works …. thanks
August 29th, 2010 - 18:31
“I does not work for me,
I have this line: telnetEnable.exe 192.168.1.1 0024B22BA2E9 Gearguy Geardog
When I click on Enter it comes back very quick without any errors, but when I try to connect to telent 192.168.1.1 it thinks about it for some time then nothing happens.”
Did you use the correct MAC address (e.g. not the Internet one)?
August 31st, 2010 - 19:16
It should all be fine, its the correct MAC address. IP Conflict perhaps?
September 15th, 2010 - 12:27
sweet, cheers man!
September 15th, 2010 - 14:59
Working nice..thanks
November 10th, 2010 - 22:01
I does not work for me,
I have this line: telnetEnable.exe 192.168.1.1 0024B22BA2E9 Gearguy Geardog
When I click on Enter it comes back very quick without any errors, but when I try to connect to telent 192.168.1.1 it thinks about it for some time then nothing happens.
Same here.
January 2nd, 2011 - 04:10
Worked for me. Make sure you’ve copied and pasted the LAN port and not the WAN port
January 25th, 2011 - 22:52
Hi Does not work for me, I get to the “Then stage 4″ the command window it changed to command window to telnet 192.168.1.1 then when I start typing the next command it switches back to the cmd prompt before the first “b” is entered.
Any Help Guys?
January 27th, 2011 - 10:52
This all works for me except that after I reboot, connect to the web based configuration and then try to upload the generic firmware update it says the file is invalid.
February 20th, 2011 - 11:56
This is late but those for who it doesn’t work, you should use the username and password: Gearguy Geardog
Also it’s possible you’re not running with the right priv’s. Create a shortcut to cmd on your desktop, right click -> ‘Run as administrator’
More details here: http://oldwiki.openwrt.org/OpenWrtDocs(2f)Hardware(2f)Netgear(2f)TelnetConsole.html
May 31st, 2011 - 04:53
Is this still valid even though their routers have a CM installed?
Surely flashing the firmware will remove the cert and potentially break your router?
Please advise
August 6th, 2011 - 23:48
Thanks for the very helpful guide, you have saved a router from the bin (VM left it when they installed a superhub). You did miss on step, after installing the new firmware, if you do a factory reset and login in as admin/password, it will reveal all the bits VM hid.
November 14th, 2011 - 17:16
had same problem as Jax, restarted the machine, dragged the cmd from ‘start, all programes, accessories menu’ to desktop, right click select run as administrator, turn off zonelarm, retyped telenetenable line and worked like a dream
December 30th, 2011 - 17:15
After finding out that I needed to turn on Telnet in Program Features, I can now run everything but the Firmware Update.
For some reason it says the file is incorrect and won’t let me do the update. Is there anyway to find out if anything that has been done already has actually worked??
December 30th, 2011 - 17:31
Just sorted it out. Read on another website something to do about Firefox, and thought I would try Internet Explorer. Worked like a dream this time when connecting to Router and then enabling the firmware update to happen.
December 30th, 2011 - 18:17
Hi Lee,
Point 1 says that exact point
Mike.
December 30th, 2011 - 18:36
C:\telnetEnable>telnetEnable.exe 192.168.0.1 30469AD020FE Gearguy Geardog
send failed: 10057
Guys i get this error, I am running the command prompt as an Administrator but no use!!! My router is WMDG280 could this contribute?
December 30th, 2011 - 21:55
Hi Sunn,
I’d say the different router is the issue.
Mike.
January 23rd, 2012 - 13:41
hi, for those having the blank screen on telnet issue, I had the similar problem, here’s how it was fixed…
I copied and pasted the MAC address from the router admin screen, but after several unsuccesful attempts, I checked the bottom of the modem and noticed that the last character of the mac address was incorrect. For some reason, it was changed from a ‘E’ to an ‘F’ – therefore when using the telnetenable.exe command, try using the mac address from the bottom of the router rather than the one in the admin screen. I also rebooted the router after using telnetenable. Not sure if this made any different but it allowed me to get the prompt when using the telnet client
Another thing you might want to check is your windows firewall settings, this can block the telnet too.