ColinTaylor
Part of the Furniture
Look in the syslog for error messages.V30E3, AC66U. When I put vsftpd.conf in /jffs/configs vsftpd does not start.
deleting /jffs/configs/vsftpd.conf makes everything ok.
Look in the syslog for error messages.V30E3, AC66U. When I put vsftpd.conf in /jffs/configs vsftpd does not start.
deleting /jffs/configs/vsftpd.conf makes everything ok.
V30E3, AC66U. When I put vsftpd.conf in /jffs/configs vsftpd does not start.
deleting /jffs/configs/vsftpd.conf makes everything ok.
I have been trying with empty vsftpd.conf and my previously working vsftpd.conf. Both cases do not work, if /jffs/configs/vsftpd.conf exists.
V30E2 shows the same problem.
All factory reset between firmware changes.
I intentionally don't touch AICloud code without a good reason because it's so fragile. So nothing there has changed recently.AiCloud refuses to connect in the two latest versions, both from the Android app and via the web. Reverted back to v29E2 and everything is working again. I'm on AC66U.
I intentionally don't touch AICloud code without a good reason because it's so fragile. So nothing there has changed recently.
I tested on my AC68P, and cloud access worked, but SmartSync would hang continuously on INIT (I'm assuming that's the problem you are seeing). I was able to fix this on the AC68 by backporting the recent prebuilt binaries from the 384 code where it specifically called out fix with SmartSync. Unfortunately, there is no 384 code for the MIPS routers. I did update the MIPS binaries to the latest 380 base, but am not set up to test SmartSync on MIPS.
I was getting a new release ready, but am going to redo it to pick up these changes. Best I can offer is to give it a try again then.
I think that's a typo? Did you mean 192.168.1.10/255.255.255.0?@Lord Lovaduck you may need to assign it a static IP/mask (try 192.168.10.1/255.255.255.0) to connect.
Thank you! yes....early morning typoI think that's a typo? Did you mean 192.168.1.10/255.255.255.0?
@Lord Lovaduck
It very tough to damage the bootloader. Power down, then remove any USB attached devices and try again to enter recovery mode. Depending on the state of the your PC, you may need to assign it a static IP/mask (try 192.168.1.10/255.255.255.0) to connect. When you do the restore, make sure you give it enough time....the flash in the early MIPS router is VERY slow, and it can take up to an hour for it to complete.
EDIT: fixed static ip
Merlin doesn't make firmware for the N16 anymore. In fact as far as I can see the old versions aren't even available for download.Or try a Merlin as I had before???
Merlin doesn't make firmware for the N16 anymore. In fact as far as I can see the old versions aren't even available for download.
Since you are on 380_7378 you can only go to ASUS firmwares 380_3000 or Merlin 380.60 or above via the gui. Any earlier level requires using the Restoration Tool.My question is more oriented to finding a firmware that would load from the Asus stock one and allow me to jump to this fork. Looking for stepping stones....
Since you are on 380_7378 you can only go to ASUS firmwares 380_3000 or Merlin 380.60 or above via the gui. Any earlier level requires using the Restoration Tool.
One thought you might try loading the 'L' version of the fork via the Restoration tool. For Merlin code, if you can get a copy of 378.55 or 378.56 those would be the best levels to try, again via the Restoration tool.
Try this.....Thanks, John! Trying to do this but don't forget, the crux of this issue is that I cannot enter the recovery mode anymore!!!
Thanks again John, unfortunately no luck with this technique either. I managed to get the router in Recovery mode after letting it unplugged all night. Started the recovery tool, it managed to get past halfway the TFTP portion, then it aborted got a solid power light and could not restart recovery mode again.Try this.....
on your PC with the static ip start a continuous ping to the router address 192.168.1.1
now try to start recovery mode on the router
if you see what looks like recovery mode, kill the ping and try to access the CFE miniserver at
http://1921.168.1.1
I think I can do this with the current ASUS stock firmware 380, would it be safe? I also dumped the CFE from the RT-N16 based on a thread that has a lot of CFE versions unfortunately I couldn't find one for the RT-N16 to use as comparison! If anybody has a CFE for the RT-N16 for me to compare or can read this one and tell me if it is corrupted, I would be very thankful!mtd-erase -d jffs2
mtd-erase -d nvram
reboot
Those commands are usually only necessary for routers that have or had DD-WRT installed which uses a different partitioning scheme that can confuse the asuswrt code. The later versions of asuswrt may also use a different partition naming convention where those commands would not be correct. What is the output ofI found this thread https://www.snbforums.com/threads/going-from-dd-wrt-k3x-asuswrt-merlin.19167/
with the recommendation of doing the following:
cat /proc/mtd
Here it is!!!What is the output of
Code:cat /proc/mtd
Code:RT-N16 login: admin Password: admin@RT-N16:/tmp/home/root# cat /proc/mtd dev: size erasesize name mtd0: 00040000 00020000 "pmon" mtd1: 01fa0000 00020000 "linux" mtd2: 019c2c84 00020000 "rootfs" mtd3: 00020000 00020000 "nvram" mtd4: 00100000 00020000 "jffs2" admin@RT-N16:/tmp/home/root#
@Lord Lovaduck
Interesting that DD-WRT loaded.....
The /proc/mtd output you posted looked normal for an N16, so not sure what the problem would be. You may want to run the same command now with DD-WRT loaded to compare it. the mtd-erase commands may be needed now after you load any asuswrt based code.
(Default Build - All supported routers)
6f96b08b0e301f71088c483d2366aa4f892762c9bdd543c05bc97674862f1cec RT-N16_374.43_31E6j9527.trx
e098cc44769fb29ce4824483f8ed67189104027479ccc89b3b3d69d21572dc4a RT-AC66U_374.43_31E6j9527.trx
b1f3ec16171a8226c25e960a9741b814c10684e593fcb9288901013bf9c4a120 RT-N66U_374.43_31E6j9527.trx
8db9d8157d034402ac01fe53e8060e76492a9b1f9072a07edcd459bb69301cb4 RT-AC68U_374.43_31E6j9527.trx
5ac83930ac1123e48b9aa8611f0d43ed4d7901a421f0dbc30cad961933537bfa RT-AC56U_374.43_31E6j9527.trx
(Legacy Only Builds)
46bc8eaf9f7b195876dad55f6bd2da15fd2e2f2c2d07b08eeb040183d8f739e4 RT-AC68U_3.0.0.4_374.43_2-31L6j9527.trx
a401d38469679cf9376c5e3aea1a8e3ea81a1e4cbbd75bcbf9ed54a348637896 RT-AC56U_3.0.0.4_374.43_2-31L6j9527.trx
4d6c824ea903f108854a4e8bf4efeb555863f9fb3b49a8b0fb1363f5e148be5d RT-N16_3.0.0.4_374.43_2-31L6j9527.trx
0bdaa21d53b2ce040a1c957a882199ff5e4a4ddba20807313bdabab96634f1d5 RT-AC66U_3.0.0.4_374.43_2-31L6j9527.trx
8f8989f892f5c878155e72f597046bcdd3bd5887bd0e6c45274459f39bc1cdef RT-N66U_3.0.0.4_374.43_2-31L6j9527.trx
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!