Foscam Fi8918w Firmware Download

The U.S. support phone number +1-844-344-1113 will be terminated on March 31, 2019. We will provide customer service through support@foscam.com. Please send emails to us if you need help. You can also leave your phone number for urgent issues and our technical engineer will contact you as soon as possible.

If you have a Foscam FI9821W that failed after you attempted to update the firmware, then you've come to the right place. Mine died a few months back and I finally got around to fixing it, but discovered that the resources were scattered all over the internet in a variety of different languages. So I'll save you a few hours of head scratching and hopefully help you bring that camera back to life.

DOWNLOAD 🔥 https://cinurl.com/2y5SLC 🔥

Set the address in your camera by typing "/etc/init.d/S80network e ifconfig eth0 192.168.0.30 netmask 255.255.255.0 broadcast 192.168.0.255" If it works, you can go back to the DOS box and press the up arrow key and it automatically type in ping 192.168.0.30 for you again, press enter and now you should see a reply. You can try going to 192.168.0.30:88 in your web browswer and you might see the camera. If so, you can just install the latest firmware via the last step and you're done. But I wasn't so lucky so if you're like me, continue on.

At this point everything should be working, but firmware 14 is the last one for this camera and it does have some fixes so I'd recommend you do the update. Just go to System > Choose file > Select the FI9821W_app_ver1.1.1.1.14.bin file and click System Upgrade. Wait for the reboot and you should be all set. You can assign a static IP address so you can keep track of the camera now.

(I hope this isn't a duplicate. If so, I'm sorry. This is my 1st time using this site)

So here's the thing. I can't get the image to load up into the camera at that specific memory location. The terminal does see the camera's text.

First none of the commands work, like:

setenv ipaddr (ip here). For setenv it always says not found.

I did find that using export ipaddr="192.168.15.25" does in fact set the env variables.

So I was able to set all that are shown here.

I can see them all when typing printenv

I can then set the IP manually and get the camera to ping to the network and be seen.

I use:

ip a add 192.168.0.30/24 dev eth0

ip link set dev eth0 up

But, typing:

protect off all

does NOT work. Again, it says, protect: Not Found.

Also, this does not work:

tftp 0x34000000 flash_FI9821W_1.2.1.1_1.1.1.13.bin 192.168.15.70

tftp complains and pops up some info one what parameters should be.

So, I reformed this to:

tftp -gr flash_FI9821W_1.2.1.1_1.1.1.13.bin 192.168.15.70 0x34000000

When I enter that, I can then see the TFTP server showing that it's copying the file to the camera.

HOWEVER, on the terminal screen, it does NOT show any progress at all. Nothing.

Once it completes, the cursor just returns to under that line.

If I reboot the camera, it has not changed at all.

I'm not a Linux user at all, so I don't know that if Foscam's version of

HiLinux is different than what you show here, or if I'm just missing some steps that are perhaps not explained well because I have no real Linux experience.

For the prompt, I see ~ $

When I type the command, protect off all and press return, the prompt changes and I see:

-sh: protect: not found.

I don't know what the significance of -sh means

So, any ideas how I can unprotect the memory and then force the firmware file to the specific memory location if none of the above works for me?

I'd really like to get this camera working, because most, if not all, of the new cameras on the market what paid for cloud services, which I do not want and do not NEED.

Honestly, to me, that's just a money grab.

Thanks in advance.

So here's the thing. I can't get the image to load up into the camera at that specific memory location. The terminal does see the camera's text.

First none of the commands work, like:

setenv ipaddr (ip here). For setenv it always says not found.

I did find that using export ipaddr="192.168.15.25" does in fact set the env variables.

So I was able to set all that are shown here.

I can see them all when typing printenv

I can then set the IP manually and get the camera to ping to the network and be seen.

I use:

ip a add 192.168.0.30/24 dev eth0

ip link set dev eth0 up

But, typing:

protect off all

does NOT work. Again, it says, protect: Not Found.

Also, this does not work:

tftp 0x34000000 flash_FI9821W_1.2.1.1_1.1.1.13.bin 192.168.15.70

tftp complains and pops up some info one what parameters should be.

So, I reformed this to:

tftp -gr flash_FI9821W_1.2.1.1_1.1.1.13.bin 192.168.15.70 0x34000000

When I enter that, I can then see the TFTP server showing that it's copying the file to the camera.

HOWEVER, on the terminal screen, it does NOT show any progress at all. Nothing.

Once it completes, the cursor just returns to under that line.

If I reboot the camera, it has not changed at all.

I'm not a Linux user at all, so I don't know that if Foscam's version of

HiLinux is different than what you show here, or if I'm just missing some steps that are perhaps not explained well because I have no real Linux experience.

For the prompt, I see ~ $

When I type the command, protect off all and press return, the prompt changes and I see:

-sh: protect: not found.

I don't know what the significance of -sh means

So, any ideas how I can unprotect the memory and then force the firmware file to the specific memory location if none of the above works for me?

I'd really like to get this camera working, because most, if not all, of the new cameras on the market what paid for cloud services, which I do not want and do not NEED.

Honestly, to me, that's just a money grab.

Thanks in advance.

I was just reading your post in regard to connecting to and uploading the new firmware for a Foscam camera that had previously been bricked and it is an absolute lifesaver. Thank you.

I do have a quick question, however, if I could bother you? I am trying to do the same thing on my Foscam IP camera, but mine is a fi9828p and if you are not familiar with that model it has "dongle" style connectors that come out of the body of the camera through the neck. one of these connectors is for I/O alarm connectivity. Is this by chance the same one that you would use to connect the uart cable, or is it yet a different connector inside the housing of the camera? I'm sorry to bother you with this, but I cannot find any literature or even images online to show me if I have to open it or if it is indeed the I/O cable connector?

Thank you very much in advance, and thank you again for the awesome instructions!

Jason Paluszak

I have a faulty camera from a friend: FOSCAM model FI9821W, engraved on PCB FI9820W-MAIN V1.3 2011-12-25 FR4020A2. He attempted a firmware upgrade but did not succeed, the camera was making some PTZ moves, I

went through putty to put a firmware according to the tutorial

" -a-Bricked-Foscam-FI9821W/fi9821w-v1-broken-after-firmware-upgrade-1-1 -1-14-t8575-780.html # p70383 ", but I think I messed up harder.

Now

it connects to the serial port with PUTTY, Hiperterminal, Tera Term Web

3.1, but nothing appears on the display, no information, I think I

managed to break the bootloader.

I'm asking you

to provide me with information, steps and software to help me get back

into operation, it's a good room and it's worth repairing.

Don Kennedy, a camera enthusiast and active member of the Foscam support forum who helped to diagnose and report the firmware problem, also posted a workaround for the bug until Foscam issues an official fix. Kennedy said the vulnerability comes on the heels of another Foscam flaw that drew widespread media attention in August 2013, in which some creep reportedly used a similar vulnerability to shout obscenities at a sleeping toddler.

The second file, the WebUI firmware, was much easier to tame. A few simple guesses about what the header information in the file meant, and a couple hours of validating my theories produced the following truth table.

Is lr_cmos_11_14_1_46.bin an archive file with another archive or executable inside ? When i tried to rename lr_cmos_11_14_1_46.bin to lr_cmos_11_14_1_46.zip and just try to open it using winrar, i saw the linux.bin file inside tho winrar throws an error. This could not happen if firmware is an executable .. right.

Also, the recovery file (from -your-fi8908w-paperweight-back-to.html) seems to consist of romfs_cmos_11_14_1_37.img and linux.zip( which has linux.bin inside). Could an expert view on the romfs_cmos_11_14_1_37.img help us to find more about the core firmware file ?

Hi Raymond, I got the same cam as you: Board: ES_IP607_ARM_2 I managed to brick it. I still have a good one, can you tell me how to transfer the good firmware to the bricked one? or do you have good recovery files for this cam?

I have 2 clone foscam FI8908W Wireless IP Camera and the problem is that they have the same mac adress so on my Lan i can not see both of them.

Is there any solution for that problem ?

Thanks

Hi,

has a big problem with clone fosca camera, I tried a few firmware or i / o error or i2c error. at this link some photos of the boards and boxes. If anyone of you have similar or knows a solution please help.

everst said:

Hello all,

I seem to have brick my Tenvis IPRobot 3 after loading their frimware 1.1.6.2 that is linked on the tervis forums. They post it voids the warranty if you try the use their forum firmware. Contacting their support was disappointing in all they would say was the camera was now broken. After a few emails and pointing out the bootloader was still intact, they offered a discount for a new camera or to send the camara to china if I pay the shipping round trip. They would not help when I pointed out I could get into the boot loader myself. I found that J9 on the main board is the serial console and with a USB to 3.3v TTL, it works great. The baud rate is 38400 and the pin order is 3.3v, gnd, rx, tx on the pcb. They are using U-Boot as the bootloader. What I need help is is decoding their firmware file. It looks to have multi parts that I can see with a hex editor. The file has a .pk2 extension which is just their own extension. I have more data I have collected and would be happy to share it. Does anyone have any experience with the IPRobot3 or know of any websites that do? What I need are the bin files and the memory locations so I can load them via the bootloader.