After you have unzipped and flashed this you can then update with
dd-wrt.v24-K3_AC_ARM_STD.bin. Located on the next page of this thread.
It will then report as being an R6250.
After that to update see EDIT 2.
EDIT 2: 4/3/2019 I was able to update this router on <Kong>bin file by engaging recovery mode, hold reset button while powering on until flashing power light.
Set static IP on client, TFTP--> R6250 factory-dd-wrt.chk.
Edit 4-16-21: Apparently the reset button may be disabled by DD-WRT. See page 3.
Posted: Sat Apr 28, 2018 18:13 Post subject: Re: Possible to upgrade r6200 v2 for KRACK?
bushant wrote:
I have R6200 V2 Netgear with firmware noted below in my signature. This firmware was obtained from myopenrouter website I think (it has been a few years). I am wondering if any build with krack fix possibly from: ftp://ftp.dd-wrt.com/betas/2017/11-04-2017-r33679/broadcom/ or elsewhere or newer might be applied?
Attached is from wikidevi. I have no idea how to process this info and no experience whatsoever with Broadcom so please be gentle.
According to the officially supported devices list, your device is not supported yet:
I hope it is OK to reopen my own old thread.I have been researching this device and see that it has the same hardware as a few devices that are supported. Although with different memory values.
DIR860L
EA6200….EA6300 (V0.1?)….EA6350
TEW811DRU
These all have BS builds with their own build names.
Also noted that the supported devices page and wikidevi do not agree on one of the radios included:
wikidevi says BCM4352 while DD-WRT says BCM4360 (Attached screenshot)) .I have no clue which is correct except 6200V1 has the 4352 and the 6250 has the 4360 according to DD-WRT supported devices.
So, the new question is do I (would you) dare flash the Kong K3_STD or maybe just try the dd-wrt.K3_R6250.chk? The R6250 has Broadcom BCM4708A0 CPU instead of BCM47081AO and has its own BS build.
Do I make a brick or just toss this box? It has good enough specs to spend a little work on.
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Fri Jul 06, 2018 15:01 Post subject:
Oddly enough, the EX6200 has identical hardware, but I am not entirely sure if that would be a safe bet, to use that firmware, as I am not sure if there is a difference in extenders and routers when it comes down to DD-WRT. Only thing I can suggest is to PM Kong and/or BS directly and ask.
So, the new question is do I (would you) dare flash the Kong K3_STD or maybe just try the dd-wrt.K3_R6250.chk? The R6250 has Broadcom BCM4708A0 CPU instead of BCM47081AO and has its own BS build.
Sorry man, I've been on vacation; the broadcom_K3X builds are only for NOR flash routers, and will not work on NAND flash devices (like the R6200v2) whose builds are in separate folders. The SoC is less of a concern, so long as you are comparing MIPS to MIPS (k3.10), or ARM to ARM (k4.4, like the R6200v2).
I would follow kernel-panic69's advice to ask BS or Kong about it; that myopenrouter link lists source code, so maybe that'd help w/ the header info.
If you really want to mess w/ it, try copying the header from the old working file onto a NAND build of a device with the same mtd partition layout. Wikidevi or openwrt wiki's are a good start to find the mtd. For the v2, you can get the layout directly from serial output or dmesg. Just keep in mind that the CFE will show a different layout from OEM or DD (etc.) application code partitioning. Make sure when you're comparing the same thing. The BCM47081 is just a single core version (I assume hardware-disabled from dual-core chips that have a faulty core) of the BCM4708 SoCs, so using any BCM4708 build should be fine; but the mtd layout is more important, so you don't overwrite a partition that CFE uses to validate boot. I probably sound confident, but you should really ask BS or Kong. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
If you really want to mess w/ it, try copying the header from the old working file onto a NAND build of a device with the same mtd partition layout.
I would have no idea where to begin to do that.
It's not worth spending anybody's time or effort on. I am mostly just playing with it. I will probably screw around till I brick it good. But if you have extra free time I will drive to Indy and drop it off...
Copy and paste your entire serial boot log (or dmesg output if serial isn't stilled connected) to a file and attach it, and I'll take a look.
If there is space [1] (Netgear likes to put important partitions in the middle or end of the flash), as a wild guess that R6250 has the same layout, you could then try flashing it's webflash file. Or in case the MOR file is sketchy, you could hexedit [2] the board ID in the R6250 factory flash file from:
U12H245T00_NETGEARHDR0
...to:
U12H264T00_NETGEARHDR0
I.e. change the 45 (ascii: 0x34 0x35) to 64 (0x36 0x34)
Probably won't work, but that's all part of the fun...
[1] Example: I found an R7000 log that shows this:
The available space is after nvram and before board_data (the 6200v2 may be very different). Thus 0x2200000-0x200000 = 32 MB.
[2] I use notepad++ w/ hex-editor plugins; alternative is HxD, or many others. I recall in some (not np++) you have to ensure you're in overwrite (not insert) mode. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
I never got close to having serial hooked up, thought I was doing good to just get the box apart without breaking it. It's still mostly apart.
Don't spend a lot of time on this, Might be easiest if I try the R6250 file first and see what happens. I downloaded it the other day.
I don't have windows machine here, if you can't open this file I will do it again at work on her windows 10 machine.
[sic on the 'Settiing']
Interesting, so it added the ddwrt partition after everything else. Then again, I don't research ARM stuff much, hopefully that's normal. Anyway, the mtd partitions are otherwise very similar to the r7000 I posted before, except the start of rootfs; nvram to board_data is the same, at 32 MB, so if official DD installs there it ...should... be safe...? Would be nice to see a 6250 boot log. Good luck... /winces
_________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
I decided to try the Kong 5-31-18 dd-wrt.K3_R6250.chk 36070 and BS 36247 for the R6250 using GUI.
First I did erase nvram via telnet then Restore Factory Defaults via GUI. Both upgrades failed quickly with
Code:
"This site can’t be reached The connection was reset."
I decided to try the Kong 5-31-18 dd-wrt.K3_R6250.chk 36070 and BS 36247 for the R6250 using GUI.
First I did erase nvram via telnet then Restore Factory Defaults via GUI. Both upgrades failed quickly
I would try the .bin file there; but ya, not looking good at this point. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Joined: 08 May 2018 Posts: 14249 Location: Texas, USA
Posted: Thu Jul 12, 2018 2:30 Post subject:
jwh7 wrote:
bushant wrote:
I decided to try the Kong 5-31-18 dd-wrt.K3_R6250.chk 36070 and BS 36247 for the R6250 using GUI.
First I did erase nvram via telnet then Restore Factory Defaults via GUI. Both upgrades failed quickly
I would try the .bin file there; but ya, not looking good at this point.
Maybe if neither BS nor Kong has it already, get the cfe.bin and boot log and pass it up the food chain to provide 'official' support for this device if no workaround is doable.