The one on the sticker label is for eth0.1
1 Like
From what I have read 3GV2 and R4GE have identical hardware but different bootloader, which R4GE seems better in recovery to stock.
If I have both 3GV2 and R4GE, using CH341A dump their flash for backup safety reason.
Is it good idea to make a copy of R4GE dump file, edit the file to match 3GV2's MAC address with hex editor then write it down to the 3GV2 so it become the R4GE and have the same bootloader?
Maybe that way I can make 3GV2 much easier back to stock from OpenWRT or even bricked situation with R4GE firmware as it's now a 'R4GE'?
Some people has PM'ed me about this file for using on their Xiaomi Router 4A gigabit edition, and after flashing it with CH341A , their router is detected as R3G v2.
I reckon, you can also do the opposite. But no promises though, and if I were you, I would make backup of my router before doing anything..
1 Like
Of course as I stated before about making backup.
There is a possibility I might receive faulty CH341A like you did, so it best make more than 1 file each chip then hash them right?
Is using windows okay as long as I got good CH341A?
Even if I failed to flash using R4GE dump image file, still have image of 3GV2 from you (edited MAC Address to match my sticker), many thanks for that..
Yes, my new ch341a and (also new) clip works fine under Windows.
1 Like
Just want to inform you, I succesfully flash my 3GV2 with 4AGE dump image from post link above. I Edited Mac Address to match my sticker (eth0.2 = 0x5E006), default SSID to match the label too. I don't edit the serial number because there is 1 length difference between 3GV2 and 4AGE.
My device become 4AGE with factory firmware 2.28.132, upgrade it to 3.0.24_INT, and later OpenWRT 19.07.4 r11208.
I also backup my spi flash running openwrt and realized it exactly the same as file combined from OpenWrt.mtd0.bin to OpenWrt.mtd7.bin I got from luci (using hash).
1 Like
@unbricker probably not important, assuming that you already have SPI Flash Programmer such as CH341A and the device is 3GV2 not 4AGE you can take it further to edit the CTEI Number, Serial Number, and SSID to match your device (printed on the box and router lable)
Offset locations
CTEI=1800xxxxxxxxxxx offset are: 0x3017A , 0x4003C , 0x11EDB2 , 0x11F66A , 0x1413B2 , 0x141C6A , 0x142386 , 0x170336SN=23xxx/A9RA8xxxx offset are:
0x3013A , 0x40004
In case of @abdulaziz.amar dump file
ssid=Xiaomi_D42D_2BD2
D42D is from EC 41 18 C8 D4 2D (4 last digit of mac address/eth0.2)
and 2BD2 = FFFF - D42D (Just use hex calculator), offset are:
0x300BB , 0x300EA , 0x40055 , 0x4006D , 0x11ECF3 , 0x11ED22 , 0x11F5AB , 0x11F5DA , 0x1412F3 , 0x141322 , 0x141BAB , 0x141BDA , 0x1422C7 , 0x1422F6 , 0x170277 , 0x1702A6
Note: Even after edited the SSID and all other data from @abdulaziz.amar dump file to match mine the factory firmware still don't give me the correct SSID that match my mac address in initial router setup.
For people that want to use 4AGE stock firmware on 3GV2 there is an unofficial patch to firmware 2.28.132 which I got from
This Post
Which are from
This Forum
This 2.28.132 patch really helpful not only in upgrading 3GV2 and 4AGE with any 4AGE official firmware (After patched to 2.28.132),
3.0.24 INT Note
Upgrading with 3.0.24 INT Official firmware will revert your edited "bootdelay.....5" (0x19690 62 6F 6F 74 64 65 6C 61 79 00 00 00 00 00 35) back to "bootdelay...off" (0x19690 62 6F 6F 74 64 65 6C 61 79 00 00 00 6F 66 66)we can also using this patch to flash OpenWRT to 3GV2 and 4AGE in Windows x64 with sysupgrade.bin file without using OpenWRTInvasion in linux discussed here and 4A Gigabit Thread.
Instead of using 2.28.132.bin I select the desired sysupgrade.bin file placed in firmware folder of that script.
Unofficial 2.28.132 Patch include full memory backup and restore function
CAUTION for using that script backup & restore
This script function AFAIK for Xiaomi router with factory firmware. The file created have the same size with SPI Flash dump.DO NOT USE that created backup file to flash with SPI Flash Programmer (Already tried that for experiment LOL), the inside value between that and dump file created from SPI Flash Programmer are totally different.
Only use that backup file with the script restore function.
If you already run non stock firmware (OpenWRT) and want to restore to factory firmware using that script backup file, but never dump your SPI Flash before using Programmer tools.
It's time to get SPI Flash Programmer, write someone else dump file, then after set up the router run the Restore Function of that script.
Another Note:
Patching 3GV2 with 2.28.132 and 4AGE bootloader will change some value such as "ssid=Xiaomi_" and "ssid=Xiaomi__5G", this don't affect if initial device real 4AGE (or 3GV2 flashed with 4AGE dump with heavily edited values)..
1 Like
Hello,
The version of my Xiaomi WiFi Router 3G V2 is:
I used the fimrware of @Gingernut (November 2019).
How to update my router to the last version ?
Use this latest version
Well it should be but I won't guarantee anything sorry.
I obtain that:
Normal ?
Yes, the naming was changed so you have to force upgrade and wipe configuration.
OK, so I uncheck the box "Keep settings and retain the current configuration" ?
Yes and then reconfigure.
Hai tmomas....i have a problem...i only can flash fw v 19.07.3 on my mi3gv2....i can't flash the snapshot version and latest....may i know how you can make it done?
What do you mean you cannot flash snapshot?
Did you mean that you don't get the web interface (luci) back after flashing, or something else?
If you mean that you don't get the web interface (luci) back after flashing a snapshot release, that's normal. You can still access the router via SSH.
If you want, you can try flashing the 21.02.0-rc3 release, which include luci by default.
Thanks for respond @abdulaziz.amar .Which part i have to update first? Kernel or sysupgrade? Because, the router cannot respond anymore from putty and webui as well...network error:connection timed out...
Try resetting your r3g v2 first, if it still cannot be accessed from SSH or web interface, I think you need to reflash openwrt from TFTP.