Hi all, i am new to Openwrt, i have played around with DD-WRT on my Netgear r7800.
My friend has purchased a second hand Linsys WRT1900acs from eBay nice router,
Hes dropped it around to me because he knows I've played around with routers.
from my understanding it is supposed to have Linksys firmware on one partition, it seems someone has installed Openwrt on both partitions.
I am first looking to get the stock firmware .img back on to the router in to one partition or the other or the correct one if someone can tell me which one?
Can this be done?
its an .img file I've downloaded from Linksys website.
thanks for any assistance you can give to a newbie please be kind lol
regards
foz

I recommend reading these two sources of information, as well as the various links from them:

https://openwrt.org/toh/hwdata/linksys/ … 1900acs_v1
https://forum.openwrt.org/viewtopic.php?id=61904

hi thanks for your response, i am not one to be spoon feed in forums and i thank you for your reply, I've had a quick scan around before posting originally, and again just but cant seem to find the answer, do you know if there a thread that particularly talks about with putting stock firmware back into one partition.
Thanks again

partitions, you may have to

sysupgrade -F -n image

to get OEM back on to one of them, does not matter which.

Thanks for your reply, i am assuming then i would need to ftp the firmware in to the router eg. /tmp then run the putty command sysupgrade -F -n FW_WRT1900ACS_1.0.3.182461_prod.img ?
or am i completely wrong? maybe firmware goes on usb flash drive or mount a drive?
i dont mind reading how to do it just need pointing in the right direction
thanks again

here

thank you ill give that a go

May i ask how to transfer the firmware to /tmp the wget link seems dead, i have the firmware so i could sftp it in
I've tried sftp using winscp but says "Cannot initialize SFTP protocol. Is the host running an SFTP server?"
thanks again

I usually scp from or to

well i though it had worked but seems its an invalid image odd
output from putty
login as: root
root@192.168.1.1's password:

BusyBox v1.24.2 () built-in shell (ash)

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
DESIGNATED DRIVER (Bleeding Edge, r49377)
-----------------------------------------------------
  * 2 oz. Orange Juice         Combine all juices in a
  * 2 oz. Pineapple Juice      tall glass filled with
  * 2 oz. Grapefruit Juice     ice, stir well.
  * 2 oz. Cranberry Juice
-----------------------------------------------------
root@OpenWrt:~# cd /tmp
root@OpenWrt:/tmp# wget http://downloads.linksys.com/downloads/ … e/FW_WRT19
00ACS_1.0.3.182461_prod.img
Downloading 'http://downloads.linksys.com/downloads/ … 1_prod.img'
Connecting to 54.231.114.129:80
Writing to 'FW_WRT1900ACS_1.0.3.182461_prod.img'
FW_WRT1900ACS_1.0.3. 100% |*******************************| 32000k  0:00:00 ETA
Download completed (32768256 bytes)
root@OpenWrt:/tmp# sysupgrade -F -n image
Invalid image type.
Image check 'platform_check_image' failed but --force given - will update anyway!
killall: watchdog: no process killed
Sending TERM to remaining processes ... logd rpcd netifd odhcpd crond snmpd uhttpd ntpd dnsmasq ubusd askfirst
Sending KILL to remaining processes ... askfirst
Switching to ramdisk...
Performing system upgrade...
Upgrade completed
Rebooting system...

should i have changed the word image for the file name?
the router is model wrt1900acs does not say v2 in the model sticker
i grabbed the correct shortcut from linksys website to v1

Added sorted thank you for your help

(Last edited by foz on 30 Mar 2018, 20:31)

I worked through this here with someone who had the same issue; I'm the dog face. This post would be the one of relevance, long way around the tree, but... Not sure what the actual issue was, but as stated early on in the thread, there once was an issue...