Flash Netgear EX6200v2 using EX6150v2 image - Firmware File is Incorrect

Installing and Using OpenWrt
1

I have a Netgear EX6200v2 with the factory firmware. This model is not in the Table of Hardware On a different forum someone suggested to try the firmware for the EX6150v2 model. I compared the hardware specs of the two models and they look very similar.

I tried to do a Firmware Update using the Netgear GUI and the openwrt-18.06.1-ipq40xx-netgear_ex6150v2-squashfs-factory.img image. I got the following error message:

This firmware file is incorrect! Please get the firmware file again and make sure it is the correct firmware for this product.

I wonder if there is a workaround and if what I'm trying to do even makes sense. Thanks!

2

Can you reach somekind of bootloader like uboot using a serial port?
If so make a backup of your current firmware so you can always go back to stock firmware.
I know there are many guides out there on how to make a backup of your stock firmware.

And then try to load the new OpenWrt firmware using uboot or anything similar and tftpd or similar.

Hope this helps you out a little.

3

Blindly flashing firmware images for different devices is always the wrong approach, as at least the hardware IDs (used for checking firmware compatibility) and some further places (DTS, device specific network/ LED preconfiguration) need to be adapted. It might be relatively simple for similar devices, but it still needs source changes (and building from the modified source).

4

As @JeroenL suggested

There might be a serial console header on the board, looking at the FCC internal photos
https://fcc.io/PY3/16100335

Another possibility is to write directly to the SPI flash memory
16 MiB ( Winbond W25Q128)

The board might be very same as the EX6150v2 except for the Ethernet Ports/USB Ports etc

(use same fw image)

https://wikidevi.com/wiki/Netgear_EX6200v2
vs
https://wikidevi.com/wiki/Netgear_EX6150v2

5

I have try to build openwrt firmware for EX6200v2, and result is awesome. only need change devices id on EX6150v2's config file, then compiled firmware can be install directly.

2 Likes
6

@tony

good

could you share the output of ? want to see if the wifi capabilities match the EX6150v2

iw phy
7

Then a forced sysupgrade of the EX6150v2 firmware would also work

8

I have built a LibreMesh firmware for my EX6150v2

9

below is my change list:Your branch is up to date with 'origin/master'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)

    modified:   package/base-files/files/bin/config_generate
    modified:   package/kernel/mac80211/files/lib/wifi/mac80211.sh
    modified:   target/linux/ipq40xx/base-files/etc/board.d/01_leds
    modified:   target/linux/ipq40xx/base-files/etc/board.d/02_network
    modified:   target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata
    modified:   target/linux/ipq40xx/image/Makefile
    modified:   target/linux/ipq40xx/patches-4.14/901-arm-boot-add-dts-files.patch
    modified:   target/linux/ipq40xx/patches-4.19/901-arm-boot-add-dts-files.patch

Untracked files:
(use "git add ..." to include in what will be committed)

    EX6150v2_190128.config
    EX6150v2_190128.config.old
    EX6200v2_190128.config
    target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-ex6200v2.dts
    target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-ex6200v2.dtsi
    target/linux/ipq40xx/files-4.19/arch/arm/boot/dts/qcom-ipq4018-ex6200v2.dts
    target/linux/ipq40xx/files-4.19/arch/arm/boot/dts/qcom-ipq4018-ex6200v2.dtsi

no changes added to commit (use "git add" and/or "git commit -a")

10

My last mesh build was based on v18.06.2 but I actually made mistake choosing the correct model and wrote without issue the EX6100v2 image on my EX6150v2

I have since re-built my mesh firmware for the correct model also EX6150v2

Looks like origin/master only provides a bump up to kernel 4.19 from 4.14 ?

11

iw phy output on EX6200v2 with openwrt:

root@OpenWrt:~# iw phy
Wiphy phy1
        max # scan SSIDs: 16
        max scan IEs length: 199 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 2:
                Capabilities: 0x19ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                VHT Capabilities (0x339959b2):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        TX STBC
                        SU Beamformer
                        SU Beamformee
                        MU Beamformer
                        MU Beamformee
                        RX antenna pattern consistency
                        TX antenna pattern consistency
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: not supported
                        4 streams: not supported
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
                Frequencies:
                        * 5180 MHz [36] (23.0 dBm)
                        * 5200 MHz [40] (23.0 dBm)
                        * 5220 MHz [44] (23.0 dBm)
                        * 5240 MHz [48] (23.0 dBm)
                        * 5260 MHz [52] (23.0 dBm) (radar detection)
                        * 5280 MHz [56] (23.0 dBm) (radar detection)
                        * 5300 MHz [60] (23.0 dBm) (radar detection)
                        * 5320 MHz [64] (23.0 dBm) (radar detection)
                        * 5500 MHz [100] (23.0 dBm) (radar detection)
                        * 5520 MHz [104] (23.0 dBm) (radar detection)
                        * 5540 MHz [108] (23.0 dBm) (radar detection)
                        * 5560 MHz [112] (23.0 dBm) (radar detection)
                        * 5580 MHz [116] (23.0 dBm) (radar detection)
                        * 5600 MHz [120] (23.0 dBm) (radar detection)
                        * 5620 MHz [124] (23.0 dBm) (radar detection)
                        * 5640 MHz [128] (23.0 dBm) (radar detection)
                        * 5660 MHz [132] (23.0 dBm) (radar detection)
                        * 5680 MHz [136] (23.0 dBm) (radar detection)
                        * 5700 MHz [140] (23.0 dBm) (radar detection)
                        * 5720 MHz [144] (23.0 dBm) (radar detection)
                        * 5745 MHz [149] (30.0 dBm)
                        * 5765 MHz [153] (30.0 dBm)
                        * 5785 MHz [157] (30.0 dBm)
                        * 5805 MHz [161] (30.0 dBm)
                        * 5825 MHz [165] (30.0 dBm)
                        * 5845 MHz [169] (disabled)
        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
                   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Device supports VHT-IBSS.
Wiphy phy0
        max # scan SSIDs: 16
        max scan IEs length: 209 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 1:
                Capabilities: 0x19ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Frequencies:
                        * 2412 MHz [1] (30.0 dBm)
                        * 2417 MHz [2] (30.0 dBm)
                        * 2422 MHz [3] (30.0 dBm)
                        * 2427 MHz [4] (30.0 dBm)
                        * 2432 MHz [5] (30.0 dBm)
                        * 2437 MHz [6] (30.0 dBm)
                        * 2442 MHz [7] (30.0 dBm)
                        * 2447 MHz [8] (30.0 dBm)
                        * 2452 MHz [9] (30.0 dBm)
                        * 2457 MHz [10] (30.0 dBm)
                        * 2462 MHz [11] (30.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)
        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
                   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Device supports VHT-IBSS.
root@OpenWrt:~# |
12

My LibreMesh build output for my EX6150v2

As suspected the wireless part of the EX6200v2 and EX6150v2 is exactly same

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 18.06.2, r7676-cddd7b4c77
 -----------------------------------------------------
  ___   __ __                _______             __
 |   |_|__|  |--.----.-----.|   |   |-----.-----|  |--.
 |     |  |  _  |   _|  -__||       |  -__|__ --|     |
 |_____|__|_____|__| |_____||__|_|__|_____|_____|__|__|

 ------------------------------------------------------
 LiMe 17.06 DaybootRely (17.06 rev. 704029c 20190302_1915)
 ------------------------------------------------------
 http://libremesh.org
 ------------------------------------------------------

=== System Notes =====================================
======================================================

root@LiMe-90e2a6:~# iw phy
Wiphy phy1
	max # scan SSIDs: 16
	max scan IEs length: 199 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
	Band 2:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-15
		VHT Capabilities (0x339959b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			SU Beamformer
			SU Beamformee
			MU Beamformer
			MU Beamformee
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: not supported
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Frequencies:
			* 5180 MHz [36] (23.0 dBm)
			* 5200 MHz [40] (23.0 dBm)
			* 5220 MHz [44] (23.0 dBm)
			* 5240 MHz [48] (23.0 dBm)
			* 5260 MHz [52] (23.0 dBm) (radar detection)
			* 5280 MHz [56] (23.0 dBm) (radar detection)
			* 5300 MHz [60] (23.0 dBm) (radar detection)
			* 5320 MHz [64] (23.0 dBm) (radar detection)
			* 5500 MHz [100] (23.0 dBm) (radar detection)
			* 5520 MHz [104] (23.0 dBm) (radar detection)
			* 5540 MHz [108] (23.0 dBm) (radar detection)
			* 5560 MHz [112] (23.0 dBm) (radar detection)
			* 5580 MHz [116] (23.0 dBm) (radar detection)
			* 5600 MHz [120] (23.0 dBm) (radar detection)
			* 5620 MHz [124] (23.0 dBm) (radar detection)
			* 5640 MHz [128] (23.0 dBm) (radar detection)
			* 5660 MHz [132] (23.0 dBm) (radar detection)
			* 5680 MHz [136] (23.0 dBm) (radar detection)
			* 5700 MHz [140] (23.0 dBm) (radar detection)
			* 5720 MHz [144] (23.0 dBm) (radar detection)
			* 5745 MHz [149] (30.0 dBm)
			* 5765 MHz [153] (30.0 dBm)
			* 5785 MHz [157] (30.0 dBm)
			* 5805 MHz [161] (30.0 dBm)
			* 5825 MHz [165] (30.0 dBm)
			* 5845 MHz [169] (disabled)
	valid interface combinations:
		 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
		   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports VHT-IBSS.
Wiphy phy0
	max # scan SSIDs: 16
	max scan IEs length: 209 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Available Antennas: TX 0x3 RX 0x3
	Configured Antennas: TX 0x3 RX 0x3
	Supported interface modes:
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
	Band 1:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-15
		Frequencies:
			* 2412 MHz [1] (30.0 dBm)
			* 2417 MHz [2] (30.0 dBm)
			* 2422 MHz [3] (30.0 dBm)
			* 2427 MHz [4] (30.0 dBm)
			* 2432 MHz [5] (30.0 dBm)
			* 2437 MHz [6] (30.0 dBm)
			* 2442 MHz [7] (30.0 dBm)
			* 2447 MHz [8] (30.0 dBm)
			* 2452 MHz [9] (30.0 dBm)
			* 2457 MHz [10] (30.0 dBm)
			* 2462 MHz [11] (30.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
			* 2484 MHz [14] (disabled)
	valid interface combinations:
		 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
		   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	Device supports VHT-IBSS.
root@LiMe-90e2a6:~# 


root@LiMe-90e2a6:~# iw wlan0-mesh station dump
Station e4:95:6e:41:cd:14 (on wlan0-mesh)
	inactive time:	10 ms
	rx bytes:	1399186
	rx packets:	15890
	tx bytes:	1162372
	tx packets:	2283
	tx retries:	0
	tx failed:	0
	rx drop misc:	13
	signal:  	-39 [-40, -47, -95, -95] dBm
	signal avg:	-38 [-39, -45, -95, -95] dBm
	Toffset:	18446744073356811890 us
	tx bitrate:	72.2 MBit/s MCS 7 short GI
	rx bitrate:	65.0 MBit/s MCS 6 short GI
	rx duration:	287206 us
	mesh llid:	29627
	mesh plid:	26290
	mesh plink:	ESTAB
	mesh local PS mode:	ACTIVE
	mesh peer PS mode:	ACTIVE
	mesh non-peer PS mode:	ACTIVE
	authorized:	yes
	authenticated:	yes
	associated:	yes
	preamble:	long
	WMM/WME:	yes
	MFP:		no
	TDLS peer:	no
	DTIM period:	2
	beacon interval:100
	short slot time:yes
	connected time:	569 seconds


root@LiMe-90e2a6:~# cat /tmp/sysinfo/board_name 
netgear,ex6150v2
root@LiMe-90e2a6:~# cat /tmp/sysinfo/model 
Netgear EX6150v2

root@LiMe-90e2a6:~# uname -a
Linux LiMe-90e2a6 4.14.95 #0 SMP Wed Jan 30 12:21:02 2019 armv7l GNU/Linux
13

Is the image for EX6200v2 that you have built available for download?

14

I just acquired an EX6200v2, and am interested in if and how support for this model is progressing. Any updates?

15

Hi Tony, I have been hoping and praying that someone does something with the 6200v2 for a while now as the standard firmware is rubbish. I personally don't use the USB port on mine so it doesn't matter to me if that isn't working. Are you able to share the firmware file you have created so far? Is there anything else that isn't working at this stage?

1 Like
16

Link: https://pan.baidu.com/s/12vJbMxFg5yzzZGn5qIgJbg Password: biv4

Below link is openwrt for EX6200v2, that build by myself, LED and USB cannot work.

17

have you tried loading this module to see if it helps ?

dwc3_qcom - DesignWare USB3 QCOM Glue Layer

I saw this module being used with a recently added IPQ4018 device I have, but it only has a USB2.0 port accessable

Cell C RTL30VW
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=c30220d458c0771013f21a16148baa4ea723027b

155 tcsr@194b000 {

156 /* select hostmode */

157 compatible = "qcom,tcsr";

158 reg = <0x194b000 0x100>;

159 qcom,usb-hsphy-mode-select = <TCSR_USB_HSPHY_HOST_MODE>;

160 status = "okay";

161 };

162

163 ess_tcsr@1953000 {

164 compatible = "qcom,tcsr";

165 reg = <0x1953000 0x1000>;

166 qcom,ess-interface-select = <TCSR_ESS_PSGMII>;

167 };

168

169 tcsr@1957000 {

170 compatible = "qcom,tcsr";

171 reg = <0x1957000 0x100>;

172 qcom,wifi_noc_memtype_m0_m2 = <TCSR_WIFI_NOC_MEMTYPE_M0_M2>;

173 };

174

175 usb2@60f8800 {

176 status = "okay";

177 };

178

179 usb3@8af8800 {

180 status = "okay";

181 };

dts
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/ipq40xx/files-4.19/arch/arm/boot/dts/qcom-ipq4019-rtl30vw.dts;h=2f17424e552c64f0b43c9381148d196601785da3;hb=c30220d458c0771013f21a16148baa4ea723027b

root@LiMe-f9c49e:~# lsmod | grep dwc3_qcom
dwc3_qcom 16384 0
root@LiMe-f9c49e:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1690:7588 Askey Computer Corp. [hex]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@LiMe-f9c49e:~# lsusb -t
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/0p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 2, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 2, If 2, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 2, If 4, Class=Vendor Specific Class, Driver=qmi_wwan, 480M
|__ Port 1: Dev 2, If 5, Class=Mass Storage, Driver=usb-storage, 480M

18

Im thinking of Switching my EX7000 with a EX6200. It seems like a gamble to see if you get a V1 or V2 these days... I want to try openwrt for the first time and get a little more into networking. Is it worth getting one to try it out? It seems like its not 100% don't want to have a bad go with it. Wish I had the funds for a WRT1900ACS but baby steps!

19

Can you also send file via anonfiles.com. I cannot download from baidu

20

OKļ¼please get from hereļ¼šhttps://anonfiles.com/p4SaB4A8o7/openwrt-18.06.0-ex6200v2_img

1 Like