Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RT new firmware ver.: Ver. 1.2.00.360516 #151

Open
theowlpo opened this issue Sep 17, 2023 · 11 comments
Open

RT new firmware ver.: Ver. 1.2.00.360516 #151

theowlpo opened this issue Sep 17, 2023 · 11 comments

Comments

@theowlpo
Copy link

Hi Team,

I bought a new RT3200 which pre-loaded firmware version is 1.2.00.360516.
Following all steps described, either using the signed or unsigned, the router does not allow to upload and flash the openwrt image (downloaded from this github repo).

Is it possible to update the openwrt image so will be possible to flash the RT3200?

Thank you very much!

@mrkiko
Copy link
Collaborator

mrkiko commented Sep 17, 2023 via email

@theowlpo
Copy link
Author

Hi Enrico,

This was the signed image i have tried to flash:
openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb

unsigned:
openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb

The router replied: invalid image

Both images were downloaded from here: https://github.com/dangowrt/owrt-ubi-installer/releases

Reading the vendors note from the download section, it says that downgrading from current version is not possible. Don't know if this affect openwrt images... website here: https://www.belkin.com/support-article/?articleNum=208567

Thank you!

@dangowrt
Copy link
Owner

Ok, so surprisingly things were working just fine with 1.2.00.273012 but now with 1.2.00.360516 not any more. It looks like the new firmware still uses the same GPG encryption key (which is still contained in the firmware) and even the sbin/fwupgrade executable is still identical. To make sure we are eliminating all other possible causes for problems please make sure:

  • use Firefox Desktop browser for the whole procedure
  • do a factory reset of the router
  • make sure router is not connected to the Internet
  • now upload openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb

I might try myself on my hardware a bit later.

@theowlpo
Copy link
Author

Ok, so surprisingly things were working just fine with 1.2.00.273012 but now with 1.2.00.360516 not any more. It looks like the new firmware still uses the same GPG encryption key (which is still contained in the firmware) and even the sbin/fwupgrade executable is still identical. To make sure we are eliminating all other possible causes for problems please make sure:

  • use Firefox Desktop browser for the whole procedure
  • do a factory reset of the router
  • make sure router is not connected to the Internet
  • now upload openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb

I might try myself on my hardware a bit later.

Hi dangowrt,

I have followed your recomended steps above but no success. Router stills show same message: "The image file is incorrect".

I have tried with both openwrt imagex, signed and unsigned.

Thank you.

@theowlpo
Copy link
Author

Ok, so surprisingly things were working just fine with 1.2.00.273012 but now with 1.2.00.360516 not any more. It looks like the new firmware still uses the same GPG encryption key (which is still contained in the firmware) and even the sbin/fwupgrade executable is still identical. To make sure we are eliminating all other possible causes for problems please make sure:

  • use Firefox Desktop browser for the whole procedure
  • do a factory reset of the router
  • make sure router is not connected to the Internet
  • now upload openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb

I might try myself on my hardware a bit later.

Hi Daniel,

Any news on this subject? Did you have a go in your HW?
Just to make sure that is not my mistake on the procedure to flash the RT3200...

Thank you for your support.

@dangowrt
Copy link
Owner

Any news on this subject? Did you have a go in your HW?

I've tried now all the way: Restored factory flash content with Firmware 1.0.00, then updated to 1.1.01.272918 which does the switch to the new "signed" firmware format, then update to 1.2.00.360516.
From there I uploaded openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer_signed.itb and it worked flawlessly, OpenWrt's recovery system is greeting me seconds later.

However, for the firmware to be able to flash anything (even original vendor binaries) I had to do a factory reset while running 1.2.00.360516 and connect the router to the Internet at least once (probably for NTP to set date and time for signature verification to work...).

@theowlpo
Copy link
Author

Restored factory flash content with Firmware 1.0.00

Thanks for the description. Just one question. How do you restore factory flash with firmware 1.0.00?

@dangowrt
Copy link
Owner

How do you restore factory flash with firmware 1.0.00?

I restore the complete content of the flash from an earlier backup. To make it easier I got the serial console connected while doing that, also so that I can see what goes wrong in case something does go wrong.

@theowlpo
Copy link
Author

Thank you. I'll try to do it tonight.

@theowlpo
Copy link
Author

theowlpo commented Sep 19, 2023

[EDIT]
dealing now with TFTP... opiton 1 from boot...

@theowlpo
Copy link
Author

Hi
Success!!!

  • Option 2 from menu (serial)
  • Downgraded the RT3200 firmware to FW_RT3200_1.0.01.101415_prod.img (via TFTP)
  • From router 192.168.1.1 updated to openwrt using: openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-initramfs-recovery-installer.itb (the signed file did not work...)
  • Reboot
  • From router 192.168.1.1 updated to openwrt using: openwrt-22.03.3-mediatek-mt7622-linksys_e8450-ubi-squashfs-sysupgrade.itb
  • Reboot
  • Done!

Thank you for the support!!!

@ghost ghost mentioned this issue Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants