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:xiaomi:ax3600 [2024/03/06 12:04] – [TFTP recovery] Add complete info about Windows recovery mcgivergim | toh:xiaomi:ax3600 [2024/04/17 14:12] – [NSS: Qualcomm Network Accelerator] Fix typo mcgivergim | ||
|---|---|---|---|
| Line 43: | Line 43: | ||
| } --> | } --> | ||
| - | ==== Potential | + | ==== Potential |
| - | * The '' | + | |
| - | * Ath11k memory: The ath11k driver needed for the main wireless radios uses a lot of memory when there are few stations connected and low bandwidth traffic flowing. | + | |
| - | | + | * **NSS Acceleration Support:** Currently, |
| - | * The IPQ807x target has not yet support for [[:docs:guide-user:network: | + | * **Ath11k Memory Usage: |
| ===== Hardware ===== | ===== Hardware ===== | ||
| Line 74: | Line 74: | ||
| === Notes === | === Notes === | ||
| - | * Flash chips known are W29N02GZSIBA or GD9FS2G8F2A. | + | |
| - | | + | * Despite |
| - | | + | * Additionally, the stock partitioning assumes |
| + | * OpenWrt partitioning modifies this, allowing the use of all available space, so it is no longer a problem. This partitioning will be reverted when recovering the router to the OEM firmware. | ||
| ==== Flash Layout ==== | ==== Flash Layout ==== | ||
| Line 133: | Line 134: | ||
| ***/ | ***/ | ||
| ==== Firmware download ==== | ==== Firmware download ==== | ||
| - | Latest stable version: | + | === Latest stable version: |
| /* stable table */ | /* stable table */ | ||
| <!-- ToH: { | <!-- ToH: { | ||
| Line 144: | Line 145: | ||
| } --> | } --> | ||
| - | Latest snapshot version (can be unstable, use with caution): | + | === Latest snapshot version (can be unstable, use with caution): |
| /* snapshot table */ | /* snapshot table */ | ||
| <!-- ToH: { | <!-- ToH: { | ||
| Line 150: | Line 151: | ||
| " | " | ||
| " | " | ||
| + | " | ||
| " | " | ||
| " | " | ||
| Line 157: | Line 159: | ||
| Snapshot versions don't have '' | Snapshot versions don't have '' | ||
| </ | </ | ||
| + | |||
| + | |||
| ==== Obtain SSH Access ==== | ==== Obtain SSH Access ==== | ||
| Line 162: | Line 166: | ||
| Are known 4 different methods for rooting this model. Choose the one more convenient to you. Perhaps the easier and safer is the JavaScript method. | Are known 4 different methods for rooting this model. Choose the one more convenient to you. Perhaps the easier and safer is the JavaScript method. | ||
| - | For Manual, Bash and JavaScript methods, first: | + | For **Manual**, **Bash** and **JavaScript** methods, first: |
| - On **both** Chinese and International model variants, roll back to the Chinese OEM firmware version 1.0.17, available [[ http:// | - On **both** Chinese and International model variants, roll back to the Chinese OEM firmware version 1.0.17, available [[ http:// | ||
| - Setup the router admin password (quick way is using the mobile setup app) | - Setup the router admin password (quick way is using the mobile setup app) | ||
| Line 168: | Line 172: | ||
| - Think of a password for SSH logins (8+ chars long, no special chars) | - Think of a password for SSH logins (8+ chars long, no special chars) | ||
| - | For Patch bdata method, you don't need to downgrade the firmware. | + | For **Patch bdata** method, you don't need to downgrade the firmware. |
| <tabbox Manual method> | <tabbox Manual method> | ||
| Line 323: | Line 327: | ||
| === For both the Chinese and International firmware model === | === For both the Chinese and International firmware model === | ||
| - | Installation is done by the '' | + | Installation is done by the '' |
| - Open an SSH shell to the router | - Open an SSH shell to the router | ||
| - Scp or wget the file '' | - Scp or wget the file '' | ||
| Line 342: | Line 346: | ||
| - Sysupgrade the device:< | - Sysupgrade the device:< | ||
| - | Device will reboot with OpenWrt, and then sysupgrade can be used to upgrade the device when desired. Although, see [[ax3600#potential_issueslimitations|potential issues / limitations]]. | + | Device will reboot with OpenWrt, and then sysupgrade can be used to upgrade the device when desired. Although, see [[ax3600#potential_issues_and_limitations|potential issues / limitations]]. |
| + | ==== NSS: Qualcomm Network Accelerator ==== | ||
| + | |||
| + | This SOC has two NSS processors. This NSS processors are able to handle some network / cryptographic functions and offload the main processors of the SOC. Currently, the Qualcomm NSS hardware acceleration is not officially supported in OpenWrt and maybe never will be. The code needed for that is not in the kernel of Linux and the patches provided by Qualcomm are only for very old versions of the kernel, so they can't be imported directly into OpenWrt and adding them require a lot of work and maintenance. | ||
| + | |||
| + | The main processors of the SOC are able to route without using the NSS processors, and this is how the official build of OpenWrt works, but is not as fast as it can be when using the NSS cores. | ||
| + | |||
| + | However, there is an ongoing community effort to enable NSS acceleration. **It's important to note that community efforts do not guarantee official support in the future**. | ||
| + | |||
| + | If your internet speed is near 1 Gbps speeds, you will note that official OpenWrt build will not reach this speeds. Or if you plan to have additional processes running on the router that can consume resources it will hurt your routing speed. In this case maybe you can try to use this NOT official builds, but remember, **they are NOT official and thus they don't have official support**. | ||
| + | |||
| + | If your understand that this versions are not official, but you want to try them, here are some relevant links: | ||
| + | - There is one [[https:// | ||
| + | - There is one [[https:// | ||
| + | |||
| + | If you are not able to build the code by yourself, some users have some repos with some ready to use builds of this NSS versions. Here are some links to his repos, in alphabetical order of the user's name. | ||
| + | - __AgustinLorenzo__: | ||
| + | - __JuliusBairaktaris__: | ||
| + | |||
| + | <WRAP center round info> | ||
| + | <color # | ||
| + | </ | ||
| ===== Debricking ===== | ===== Debricking ===== | ||
| - | The device can be recovered using a TFTP recovery (recommended, | + | There are several options for debricking the AX3600 Router: |
| + | * The device can be recovered using a TFTP recovery (recommended, | ||
| + | * You can use the MiWIFI Repair Tool (instructions below) | ||
| + | * you can try to apply the habitual [[docs: | ||
| ==== TFTP recovery ==== | ==== TFTP recovery ==== | ||
| Line 352: | Line 380: | ||
| * The TFTP server assigns an IP address to the router | * The TFTP server assigns an IP address to the router | ||
| * The router then connects to the TFTP server (where your DHCP server listen, e.g.: 192.168.31.100) and tries to download a file named with the IP address given by the DHCP server converted to hexadecimal.< | * The router then connects to the TFTP server (where your DHCP server listen, e.g.: 192.168.31.100) and tries to download a file named with the IP address given by the DHCP server converted to hexadecimal.< | ||
| - | * For example, | + | * For example, |
| * Because of this quirk we will have to configure the tftp server to assign only one IP and we will set the file name to the only IP address it can receive. | * Because of this quirk we will have to configure the tftp server to assign only one IP and we will set the file name to the only IP address it can receive. | ||
| </ | </ | ||
| Line 365: | Line 393: | ||
| sudo ip address add 192.168.31.100/ | sudo ip address add 192.168.31.100/ | ||
| *Run the server with the following command:< | *Run the server with the following command:< | ||
| + | |||
| <tabbox Windows> | <tabbox Windows> | ||
| - | On Windows you can use any tftp client, | + | On Windows you can use any tftp client, |
| * Connect your computer ethernet port to the router LAN1 port, nothing else connected. | * Connect your computer ethernet port to the router LAN1 port, nothing else connected. | ||
| + | * In Windows, set computer IP as static to '' | ||
| - | * In Windows, set computer IP as static to 192.168.31.100, | ||
| {{: | {{: | ||
| - | * **Allow tftp64 in windows firewall or deactivate | + | * **Allow tftp64 in windows firewall or deactivate |
| * Configure tftp64 like this: | * Configure tftp64 like this: | ||
| + | |||
| {{: | {{: | ||
| {{: | {{: | ||
| - | * Configure tftp64 DHCP server to give the IP 192.168.31.2 to the router: | + | * Configure tftp64 DHCP server to give the IP '' |
| - | {{: | + | |
| - | | + | {{: |
| + | |||
| + | | ||
| </ | </ | ||
| Now, you can start the recovery: | Now, you can start the recovery: | ||
| + | * Power off the Router if you haven' | ||
| * Keep reset button pressed and power on your AX3600. <WRAP round info> | * Keep reset button pressed and power on your AX3600. <WRAP round info> | ||
| * Keep it pressed until you see the system led blinking orange | * Keep it pressed until you see the system led blinking orange | ||
| Line 393: | Line 425: | ||
| * If the recovery doesn' | * If the recovery doesn' | ||
| </ | </ | ||
| - | * Put your interface back to DHCP mode and start again with breaking your device | + | |
| + | Finally you can put the interface | ||
| + | |||
| + | ==== MiWIFI Repair Tool (Windows) ==== | ||
| + | |||
| + | You can download the repair tool from http:// | ||
| + | |||
| + | * Make sure the computer has a static IP address as shown in the instructions above (TFTP recovery) | ||
| + | * On the first screen, select your firmware (recommended is [[https:// | ||
| + | * Click on the button on the right button to continue to the next step | ||
| + | * Select your Ethernet adapter which has the router connected | ||
| + | * Click on the button on the right button to continue to the next step | ||
| + | * Unplug the router if you haven' | ||
| + | * Press and hold the reset button | ||
| + | * Power on the router | ||
| + | * Wait for the orange LED to start blinking and stop blinking again | ||
| + | * Release the reset button | ||
| + | * The MiWIFI repair tool should now show show a dialog indicating that data is being copied to the router. | ||
| + | * When the files have been copied, the router should show a blinking blue LED. | ||
| + | * You may now unplug the router and plug it back in again to restart it. | ||
| + | * The repair should now be complete. | ||
| ===== Photos ===== | ===== Photos ===== | ||
| Line 453: | Line 506: | ||
| " | " | ||
| " | " | ||
| + | " | ||
| " | " | ||
| " | " | ||