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

Help reverting back to original firmware on RUTX50 device. #3407

Closed
QRUXEL opened this issue Jun 15, 2024 · 3 comments
Closed

Help reverting back to original firmware on RUTX50 device. #3407

QRUXEL opened this issue Jun 15, 2024 · 3 comments

Comments

@QRUXEL
Copy link

QRUXEL commented Jun 15, 2024

Expected Behavior

A guide to help reverting back to Teletonica firmware

Current Behavior

There is a guide for installing the firmware, but it does not say anywhere how to save a firmware backup of your boot config or firmware. I admit I'm not a firmware developer or well educated in Linux systems, but I really need to get the original firmware back ASAP and I don't know what to do and very afraid of bricking the device. When I try flashing the teltonika original firmware from ssh it says that the device "teltonika, rutx50" is not compatible with the image target "teltonika, rutx"
Should I force the installation anyway with -F?

Specifications

  • OpenMPTCProuter version:
  • OpenMPTCProuter VPS version:
  • OpenMPTCProuter VPS provider:
  • OpenMPTCProuter platform:

Teltonika, rutx50

@Ysurac
Copy link
Owner

Ysurac commented Jun 15, 2024

I never tried.
Maybe something like, but really not sure for the mtd part...:

   $ echo 1 > /proc/boot_info/rootfs/primaryboot
   $ cat /proc/boot_info/getbinary_bootconfig > /tmp/bootconfig.bin
   $ cat /proc/boot_info/getbinary_bootconfig1 > /tmp/bootconfig1.bin
   $ mtd write /tmp/bootconfig.bin /dev/mtd0
   $ mtd write /tmp/bootconfig1.bin /dev/mtd1

@QRUXEL
Copy link
Author

QRUXEL commented Jun 15, 2024

Hello Ysurac and thanks for helping,

The first command results in error "can't create /proc/boot_info/rootfs/primaryboot: nonexistent directory"

Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants