MT3000 4.9 beta6 can only be updated via u-boot

MT3000 4.9 beta6 can only be updated via u-boot, and resetting will fail; it can only be reflashed through u-boot again

The previous 4.9 betas worked normally. Is it a firmware issue or a hardware issue?

Hello,

We tested locally using the MT3000 v4.9.0 beta6 firmware. At present, upgrading to beta6 via the Web Admin Panel and performing a Firmware Reset both complete normally, so we are temporarily unable to reproduce the issue you encountered.


To further pinpoint the issue, could you please confirm the following information:

  1. What firmware version was the device using before the upgrade?
  2. Are you able to import the beta6 firmware file normally, but the upgrade fails?
  3. After the upgrade fails through the Web UI, what is the LED indicator status, and can you search for the MT3000 WiFi?

Thank you for your assistance.

  1. Currently 4.9 beta6, flashed via uboot

  2. Imported normally, upgrade failed

  3. Blue light, blinking, unable to detect mt3000’s WiFi

Hello,

Thank you for your reply.

Since the device can still enter U-Boot and can be flashed with beta6 via U-Boot, the device is still usable for now.

To confirm whether this issue occurs only in 4.9 beta6, could you please help perform the following tests:

  1. On the current 4.9 beta6 version, is it possible to use the web management page to locally upgrade to another firmware version?
  2. Please flash a previously working official firmware version via U-Boot, then upgrade again to 4.9 beta6. After that, does it work normally, and can the upgrade proceed successfully?
  3. Could you please let us know the firmware version used before the initial upgrade to 4.9 beta6, and which method was used to upgrade to 4.9 beta6 at that time, such as local upgrade via the web management page, LuCI, or U-Boot, and whether “preserve settings” was enabled during the upgrade?

Thank you for your understanding and cooperation.

The official version 4.9.0 released today can now be upgraded to normally.

Additionally, I’d like to ask:

Since VPN-related features cannot be used in the Chinese version due to domestic policies, could you make a streamlined firmware?