The current latest blobs for the AC3200 are no longer compatible with the 384.7 GPL code however.
I can do so, there's no technical problem. But there are some concerns:Could you please help others how exactly you've done?
Many got a chinese version and now lost all other languages (leaving chinese and english) with last stock or Merlin.
Hard to believe that allowing other languages could violate anything.I can do so, there's no technical problem. But there are some concerns:
- I've patched the binary thing only for RT-AC86U so far (obviously, had to recompile the firmware);
- It would require manual patching for every model and every time the component changes;
- It's a closed source component, so I guess that it'll become a violation of Asus user agreement (and God knows what else) if I make the hack public...
Hard to believe that allowing other languages could violate anything.
We only would need it for RT-AC86U, others dont have this problem right now.
Maybe @RMerlin can tell us what he thinks about it and if he could implement it in his fork.
Never could understand this obsession folk have with updating firmware every few weeks.
you forget that often security problems come WITH an update integrated in a new "feature".it's the same as other people's obsession of trying to use security exploits daily. newer versions come with security patches.
Asuswrt-Merlin 384.6 is now available for all supported models, except for the RT-AC87U
Make sure you don't mix up the firmware for the RT-AC68U (*.trx) and the RT-AC86U (*.w)... It's a common mistake.The firmware filetype for the AC86U has changed
Is it allowed for him to post his solution for more languages in this forum?I used to remove that limitation, until Asus moved the target code into a closed source binary in a recent update. To me, that's a sign that they don't want me to mess with it, so I won't.
Maybe it's something that could be explained via PM, as the solution would only be of interest to those people capable of patching binary blobs and then compiling their own firmware. And then doing it all again every time a new firmware is released. So probably only applicable to a handful of people.Is it allowed for him to post his solution for more languages in this forum?
1) Understood. ASUS doesn’t appear to support AIMesh very well either... I have an active problem report with them for losing 2.4 ghz band and losing ability to support Airport Express or other models of small routers with audio jacks.1) No, Merlin does not support AiMesh on any router.
2) Just load the firmware through the WebUI as normal. A factory reset is advisable but do not reload a saved CFG file as that negates the purpose of the factory reset.
There might be something in the release notes for a specific release, but generally the installation instructions say:2) Factory reset is mandatory, I believe, when coming from the vendor firmware.
- If coming from a non-Asuswrt firmware, you will have to do a factory default reset.
- While it is generally not necessary to restore to factory defaults, it's not a bad idea, especially if there is a big jump in version number (e.g. from 112 to 178).
You are loading the wrong firmware then. See M@rco's post.The file type is not supported when Load attempted.
Asuswrt is the name of the stock Asus firmware, Asuswrt-Merlin is the name of Merlin's. The CFG file contains a backup of the user and low-level system settings. The point of doing a factory reset is to erase the current settings and let the new firmware generate the new default values. Reloading the CFG file defeats this purpose.I’m unclear about loading a saved CFG after going to Asuswrt? Are the formats incompatible?
Is it allowed for him to post his solution for more languages in this forum?
Ok, will PM him how he did.Maybe it's something that could be explained via PM, as the solution would only be of interest to those people capable of patching binary blobs and then compiling their own firmware. And then doing it all again every time a new firmware is released. So probably only applicable to a handful of people.
On a forum that gets visited by Asus employees? I don't recommend it... It will only drive them into taking more drastic measures to prevent such hacks from happening in the future, which generally results in more headaches for me to deal with.
Users that are affected by this would be better to contact Asus directly, and explain their case, in hopes that if enough legitimate customers complain, they might change their mind.
Exactly that is why I was reluctant to publicly tell how I fixed it for myself...
Although would be really nice if someone (an ASUS employee?) could explain what is the reason of not allowing me to switch to English in a Japanese model.
I am confused by some earlier conversation about 3200 support - will 3200 continue to be supported or has Asus discontinued their support resulting in Merlin discontinuing development of new firmware for 3200 after this release? Thanks...
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!