Removing openwrt from linksys Velop V2

Hello mates

I am going to sell my Velop V2 and I want to remove the openwrt and replace it with stock firmware. I tried a lot with tftp method but couldn't manage to restore router stock firmware..
Any hint for helping me flashing this router is highly appreciated.

Cheers

this ?

Most Linksys dual-firmware routers have a file format where the OEM image has ID header at the end of the image. That would mean that you could just sysupgrade flash the OEM image with force flag (when the image metadata fails in OpenWrt image check). And do not keep settings.

Looking at the commit adding support for the device, there is also a TFTP possibility that you could use, apparently. But it requires serial access. (did you have that in your trials?)

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=9e4ede8344d60d4837e047e9275c21fd2a8f130b

Thanks for reply mate, but I don't want to open the router and connect serial cable.
Is there any other way for example to scp the stock firmware in /tmp following mtd it and then force sysupgrade?
Actually I saw this but to be honest I afraid doing it as it may brick the router

yes mate this is my router and I read all wiki, but no clear instruction for reverting back the stock firmware

1 Like

May you please let me know if this will modify the second partition or directly will write on the current partition? Is there possibility to write the image to second partition and then just swap them with 3 boot failures method?

Practically all sysupgrade flashing either from OpenWrt or OEM firmware in these dual-parition Linksys devices cause the new firmware to be written to the alternative partition, and boot then switched to that.

Thus you are always left with the currently running firmware as the fallback.

It will replace both partitions. You have to find out on which partition you are currently on, then flash the alternate partition. You can switch partitions by rebooting 3 times or you can use luci-advanced-reboot after flashing.

1) cat /proc/mtd 
2) cat /sys/devices/virtual/ubi/ubi0/mtd_num 

This is print out from cat, so it means on which rootfs I am right?

root@Master-Room:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "SBL1"
mtd1: 00100000 00020000 "MIBIB"
mtd2: 00100000 00020000 "QSEE"
mtd3: 00080000 00020000 "CDT"
mtd4: 00200000 00020000 "APPSBL"
mtd5: 00080000 00020000 "ART"
mtd6: 00080000 00020000 "u_env"
mtd7: 00040000 00020000 "s_env"
mtd8: 00040000 00020000 "devinfo"
mtd9: 0a100000 00020000 "kernel"
mtd10: 09b00000 00020000 "rootfs"
mtd11: 0a100000 00020000 "alt_kernel"
mtd12: 09b00000 00020000 "alt_rootfs"
mtd13: 00200000 00020000 "sysdiag"
mtd14: 0b500000 00020000 "syscfg"
root@Master-Room:~# cat /sys/devices/virtual/ubi/ubi0/mtd_num
12

You are currently on the "alt" partition. Flash the other partition, and you should be back to stock.

Tnx bro, so as somehow last question, the $FIRMWARE_IMAGE should be the bin file name or mtd will chose the bin file automatically from /tmp? Sorry as this is the first time I am doing this

It should be the .bin file name of the stock firmware.

1 Like

But seems I am on current partition 2, shall I still write the image on 01 which is alternative? confused as my running version is 125

Yeah its a bit confusing to due the naming scheme. After flashing use reboot to alternative.

Done bro, tnx a lot for your help, hats off :star_struck: :innocent:

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.