Bad Magic Number,00000000 (ESR300)

Hello,
My EnGenius Wifi Router model:esr300, but fccid: A8JESR600 i installed openwrt of esr600 which is dlf and bin i tried flashing both of them using tftp server with serial connection but it gets me this err

## Booting image at bc050000 ...
Bad Magic Number,00000000
Enter Senao Recovery Mode

so i get tired of tring to flash it then when i tried to get oem software on it didnt even work saddly
i tried all this softwares
image
and this
image

but its giving me:

## Booting image at bc050000 ...
Bad Magic Number,7F7F7F7F
Enter Senao Recovery Mode

heres the full serial boot log:

U-boot Ver:1.0.3.5 2013/05/21 10:25:24


Board: Ralink APSoC DRAM:  64 MB
******************************
Software System Reset Occurred
******************************
spi_wait_nsec: 28
spi device id: c2 20 18 c2 20 (2018c220)
find flash: MX25L12805D
Flash size 16MB, sector count = 256
============================================
ASIC 7620_MP (Port5<->None)
Product Name: ESR300
EMBEDAD SWITH init

Please choose the operation:
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   9: Load Boot Loader code then write to Flash via TFTP.                     0

3: System Boot system code via Flash.
## Booting image at bc050000 ...
Bad Magic Number,00000000
Enter Senao Recovery Mode


4: System Enter Boot Command Line Interface.

U-Boot 1.1.3 (May 21 2013 - 10:25:24)
        Input Linux Kernel filename
.......Start http[192.168.99.9]..............


 Waitting for RX_DMA_BUSY status Start... done

checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad
checksum bad

and here is the printenv command using U-boot what shows:

MT7620 # printenv
bootcmd=tftp
bootdelay=1
baudrate=115200
ethaddr="88:DC:96:17:80:CD"
sn=142240393
hw_ver=1.0.0
hw_id=01010059
pro_id=000
domain=1
wanaddr=88:DC:96:17:7C:7F
wlanaddr=00:AA:BB:CC:DD:12
iNICaddr=00:AA:BB:CC:DD:22
eth_en=0
snextra=142240393***********
op_mode=0
uboot_ver=1.0.3.5
language_code=uk
sku_table=0
en_ddns_alg=1
filesize=e9e080
fileaddr=80A00000
ipaddr=192.168.1.1
serverip=192.168.1.2
autostart=no
bootfile=openwrt-22.03.0-ramips-mt7620-engenius_esr600-squashfs-factory.dlf
stdin=serial
stdout=serial
stderr=serial

Environment size: 523/4092 bytes

MuntadherTY,

I think you should tell your tftp-server to send the file, not within boot parameters of your router.
openwrt-22.03.0-ramips-mt7620-engenius_esr600-squashfs-factory.dlf
The file may not exceed: 15327360 bytes, as stated in boot parameters.

Which option did you try @ :

Please choose the operation:
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
9: Load Boot Loader code then write to Flash via TFTP. 0

Option 3 does NOT use tftp...
I should start with option 2.

Did you check the following links:

and

Please remove/close the other opened forum item?

DG.

im using tftpd64 to make tftp server on my windows pc, then using the serial communication to fill up the server info to make the router brings up the image which shows this:
image

this is the filename:
image

and this is directory files of tftp server:

image

i tried option 1 which is boot to the image without flashing its not logged i dont know whats the reason for that
also the option 2 for all the images

yee absolutely i checked them

as u wish i did remove it

Thanks for ur respond

MuntadherTY,

Just before the tftp starts, can you ping both other sides? To make sure cables and software are setup right. Not always a eth-patch-cable will work between pc and router, but a eth-straight-through cable will do.
If not possible to ping from router to PC, make sure you can ping the router from windows pc.
Tftp64 is using 192.168.1.2 as its server-ip? Especially when the PC has more ip addresses.
Have you seen tftp filling it's log while sending the openwrt.dlf file?
(Which -I hope- is a copy of the long openwrt-22.03.0-ramips-mt7620-engenius_esr600-squashfs-factory.dlf file, NOT the .BIN file!)

What does this tftp log say?

You wrote: i tried option 1 , which I did not see but that seems to be default boot from image file without flashing.

Normally: First the boot loader code has to be addressed to the router, THEN the image file.
As the .dlf file contains both, this one should be used to flash the router by tftp.

When OpenWrt does work, then use the .bin file to upgrade to latest level.

If you still encounter issues, check the SHA of the .dlf file, maybe something went wrong during downloading?
In short: only use the .bin file when openwrt is running and upgrade by web GUI.
The .dlf file is only used to tftp to router, with or without writing to flash.

Found also the next link, but it's not telling much more:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=3df3bb0dae9e633d843223afb98bd787ad9d6022

Hopefully you get this working.

DG.

MuntadherTY,

Additional info: I searched for your device: EnGenius Wifi Router model:esr300, but fccid: A8JESR600

But cannot find any info about this device! It is or: ESR300 or ESR600 cannot be both.

Could you check https://fccid.io/A8J and tell me which device it really is?
Even all in- and outside pictures are there.
As ESR300 is not supported by OpenWrt, the ESR600 is.

On the mentioned site is nothing to find your device and all EnGenius devices are mentioned there.
Can you copy a photo of your label on the device?

DG.

The EnGenius ESR300 uses a slightly different SOC than the ESR600. The EnGenius ESR300 has a MediaTek MT7620N and the EnGenius ESR600 has a MediaTek MT7620A. Also the correct FCCID for the ESR300 is A8J-ESR300.