Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:linksys:e8450 [2024/09/24 11:46] – more additions to the recovery and troubleshooting section tjyrinki | toh:linksys:e8450 [2024/12/05 16:12] – Formatting carlitossuper1 | ||
|---|---|---|---|
| Line 50: | Line 50: | ||
| Read the advice there and download the initial installation image **...ubi-initramfs-recovery-installer.itb** | Read the advice there and download the initial installation image **...ubi-initramfs-recovery-installer.itb** | ||
| + | |||
| + | __**Upgrading an UBI installation to new releases after 2024-02 (Includes ALL SNAPSHOTS, 24.10-SNAPSHOTs, | ||
| + | |||
| + | Since some SNAPSHOTs releases after February 2024, the flash layout of the router moved the FIP and Factory partitions into UBI, and thus, those releases need a new installer. That installer, as of December 2024 is v1.1.3 is available [[https:// | ||
| + | |||
| + | 1. Download the // | ||
| + | 2. Flash the unsigned installer on Luci > System > Backup/ | ||
| + | 3. The router will reboot into a recovery environment and will be accessible at 192.168.1.1. Go again to Luci > System > Backup/ | ||
| + | 4. The router will reboot on the desired image and is ready to be set up. All future releases can be safely flashed using Luci, Attended Sysupgrade or OWUT unless a new installer is required and is instructed to be flashed. | ||
| + | |||
| + | **In case the configuration wants to be preserved: | ||
| + | |||
| + | The configuration between stable 23.05 and MAIN Snapshots and current 24.10-rcX releases is almost identical, but needs some changes, so the procedure to upgrade while keeping the configuration is the following. | ||
| + | 1. On the stable release, SSH into the router and execute '' | ||
| + | 2. Make a backup of said configuration on Luci > System > Backup/ | ||
| + | 3. Delete the following files from the backup file: | ||
| + | * / | ||
| + | * / | ||
| + | 4. Flash the // | ||
| + | 5. The router will reboot in a recovery environment and then, flash the desired sysupgrade image. | ||
| + | 6. The router will reboot on the desired image and the backup file can be uploaded in Luci > System > Backup/ | ||
| + | |||
| + | In the event that those files aren't deleted from the backup, those files need to be modified to match the new flash layout and avoid problems on future sysupgrades: | ||
| + | - / | ||
| + | |||
| + | <webcode name=" | ||
| + | /dev/ubi0_2 0x0 0x1f000 0x1f000 1 | ||
| + | /dev/ubi0_3 0x0 0x1f000 0x1f000 1 | ||
| + | </ | ||
| + | |||
| + | - / | ||
| + | |||
| + | <webcode name=" | ||
| + | |||
| + | config ubootenv | ||
| + | option dev '/ | ||
| + | option offset ' | ||
| + | option envsize ' | ||
| + | option secsize ' | ||
| + | option numsec ' | ||
| + | | ||
| + | config ubootenv | ||
| + | option dev '/ | ||
| + | option offset ' | ||
| + | option envsize ' | ||
| + | option secsize ' | ||
| + | option numsec ' | ||
| + | | ||
| + | </ | ||
| + | |||
| + | More info about those changes in the files [[https:// | ||
| __**non-UBI**__ | __**non-UBI**__ | ||
| Line 127: | Line 178: | ||
| A few caveats to using WED: | A few caveats to using WED: | ||
| - | * Users may experience stability issues | + | * Requires 22.03 or later |
| + | * May be less stable | ||
| * It can be used alone or in addition to other hardware offloading | * It can be used alone or in addition to other hardware offloading | ||
| - | * Requires 22.03.0 or later | + | * It is incompatible with AQL |
| * Only accelerates wireless traffic, not wired traffic | * Only accelerates wireless traffic, not wired traffic | ||
| * Only supported on the 5 GHz radio | * Only supported on the 5 GHz radio | ||
| - | * If used on a [[: | + | * If used on a [[: |
| === Enable WED === | === Enable WED === | ||
| - | == OpenWrt | + | == 22.03 or 23.05 == |
| * Edit ''/ | * Edit ''/ | ||
| * This change requires a reboot | * This change requires a reboot | ||
| * :!: This change will not persist upon updating as the file edited is not the target of a backup tarball. | * :!: This change will not persist upon updating as the file edited is not the target of a backup tarball. | ||
| - | == Development snapshot | + | == 24.10 or Main snapshots onward |
| * Edit ''/ | * Edit ''/ | ||
| * This change requires a reboot | * This change requires a reboot | ||
| - | == Dumb access point configuration == | + | == Dumb Access Point configuration == |
| - | Flow offloading happens in situations where flows are actually being tracked, ie. when using NAT/ | + | Flow offloading happens in situations where flows are actually being tracked, ie. when using NAT/ |
| * [[faq/ | * [[faq/ | ||
| Line 217: | Line 269: | ||
| v2.10.0 (release): | v2.10.0 (release): | ||
| </ | </ | ||
| - | If you are on the v2.9 or 2.10 branch and the suffix of the build is ...a**-1** or ...a**-2** => Device is affected and at risk of OKD on boot, reboot, power up. | + | If you are on the v2.9 branch |
| < | < | ||
| v2.10.0 (release): | v2.10.0 (release): | ||
| </ | </ | ||
| - | You are safe as you have the fixed ...a**-3** build. | + | You are safe as you have the fixed v2.10.0...a**-3** |
| ===Recovery from live OpenWrt main/master snapshot with FIP in UBI layout=== | ===Recovery from live OpenWrt main/master snapshot with FIP in UBI layout=== | ||
| Line 247: | Line 299: | ||
| Example of rewriting FIP = BL31: https:// | Example of rewriting FIP = BL31: https:// | ||
| + | |||
| + | ===Recovery from live OpenWrt 22.03.x or 23.05.x with FIP in MTD layout=== | ||
| + | If your router still boots, you should downgrade bl2 to an unaffected older version via SSH. | ||
| + | * Use opkg install the '' | ||
| + | * Use mtd to rewrite BL2 (preloader.bin). This is the actual fix. Download it from https:// | ||
| + | < | ||
| + | mtd -p 0x0 write / | ||
| + | mtd -p 0x20000 write / | ||
| + | mtd -p 0x40000 write / | ||
| + | mtd -p 0x60000 write / | ||
| + | </ | ||
| + | * Before rebooting, verify with grep (explained above) that mtd0 really contains the unaffected v2.4. | ||
| + | |||
| ==== Serial Recovery ==== | ==== Serial Recovery ==== | ||
| Line 271: | Line 336: | ||
| * Remove the **two (2)** crosshead screws that secure the router body to the internal mainboard slide tray. | * Remove the **two (2)** crosshead screws that secure the router body to the internal mainboard slide tray. | ||
| * Remove the internal mainboard slide tray from the router body by sliding it through the **back** of the router body. It comes out easily, but to initially displace or " | * Remove the internal mainboard slide tray from the router body by sliding it through the **back** of the router body. It comes out easily, but to initially displace or " | ||
| + | * Alternative perspective: | ||
| * Remove the **three (3)** crosshead screws on the **outer perimeter** of the mainboard (one (1) on bottom edge, two (2) on top edge). There is no need to remove the four screws that attach the heatsink to the mainboard. | * Remove the **three (3)** crosshead screws on the **outer perimeter** of the mainboard (one (1) on bottom edge, two (2) on top edge). There is no need to remove the four screws that attach the heatsink to the mainboard. | ||
| - | * Turn the mainboard over and you will have access to the white serial connector and JTAG connector. | + | * Slide the mainboard slightly sideways as needed, then turn the mainboard over (without stretching wires too much) and you will have access to the white serial connector and JTAG connector. |
| === Recovery Steps === | === Recovery Steps === | ||
| Line 296: | Line 362: | ||
| * Linux, when `mtk_uartboot` automatically recognizes the connected serial device: < | * Linux, when `mtk_uartboot` automatically recognizes the connected serial device: < | ||
| * macOS, when `mtk_uartboot` would otherwise use the wrong serial device: < | * macOS, when `mtk_uartboot` would otherwise use the wrong serial device: < | ||
| + | * (The serial device on your system may be different than the one shown above, such as `tty.usbserial-0001` or similar. | ||
| * Windows: < | * Windows: < | ||
| * Power on the RT3200 / E8450 | * Power on the RT3200 / E8450 | ||
| - | * mtk_uart should trigger a boot (if you never get past ' | + | * mtk_uart should trigger a boot (if you never get past ' |
| * From the boot menu, select the option '' | * From the boot menu, select the option '' | ||
| * Note that the current version automatically does the reflashing without further interaction, | * Note that the current version automatically does the reflashing without further interaction, | ||
| Line 307: | Line 374: | ||
| Q: Getting " | Q: Getting " | ||
| - | A: Likely you did not specify the device for the mtk_uartboot like -s / | + | A: Likely you did not specify the device for the mtk_uartboot like -s / |
| Q: Getting "ARP Retry count exceeded; starting again" after selecting "Load BL2 preloader via TFTP then write to flash"? | Q: Getting "ARP Retry count exceeded; starting again" after selecting "Load BL2 preloader via TFTP then write to flash"? | ||
| - | A: You don't have network configured, did you connect the router' | + | A: You don't have network configured |
| Q: Getting "BL2: Failed to load image id 5 (-2)"? | Q: Getting "BL2: Failed to load image id 5 (-2)"? | ||
| A: This is the standard message when trying to boot a broken router - in this case, mtk_uartboot did not send the binary to run on time, you need to kill the existing screen session / mtk_uartboot and try again. | A: This is the standard message when trying to boot a broken router - in this case, mtk_uartboot did not send the binary to run on time, you need to kill the existing screen session / mtk_uartboot and try again. | ||
| + | |||
| + | Q: Getting " | ||
| + | |||
| + | A: Use commands inside console: | ||
| + | < | ||
| + | setenv bootargs | ||
| + | setenv ethaddr xx: | ||
| + | saveenv</ | ||