Dec 24, 2009

If you're part of the numerous people who bricked their ip camera at any stage, maybe you kept it (as a door stopper, a paperweight or a dummy camera). In that case, there is one last thing you can try to make your camera functional again. It requires a small investment of less than €15 so I think it's really worth trying.

I obtained some information recently, thanks to Foscam tech support for most part, on a serial upgrade method that would fix cameras for which the firmware upgrade went bad.

A word of caution first: - I've only tested this method with the oldest FI8908W, not the Foscam "Logo" FI8908W (fw v.11.14.2.26 and up).
- this should be experimented only if you exhausted your other options, like claiming a replacement under the warranty.
- this is also not guaranteed to work for all. It suppose that the boot loader in the camera is still intact.
- the recovery files are not normal firmware upgrade files and cannot be uploaded to the camera using the normal firmware upgrade procedure.

What you need:

- a USB to serial UART interface that does 3.3v logic (see photos). If dual 3.3v/5v is not specified, assume it does 5v only and don't buy. This should not cost you more than €15.

- some wires and female crimp pins to make the connections easier. I reused those from an audio cable for CD-ROM.

- the Foscam FI8908W Recovery files (+ mirror) - They contain instructions and binaries to upload.2011 Update: I've received these other recovery files (+ mirror) from Foscam and should work with newerFI8908W AND FI8918W
- a terminal software if you don't have HyperTerminal on your version of Windows. I suggest RealTerm.
- I also used some adhesive putty to help keeping the wires in place and isolate the wires from each other.

You have to unscrew the bottom cover of the camera to access the JTAG connector (marked J2). On some cameras the connector is there but without the pins; In this case, add a solder iron to the "What you need" list. The only challenging task will be to achieve a stable connection to it for the length of the operation.

In the documentation, the file IPCAM_PCB_Connection.xls shows where to connect the wires. The 4 pins, from right to left are used as follow:
Pin #1 - INPUT
Pin #2 - OUTPUT
Pin #3 - GROUNDPin #4 - POWER(not needed)

The serial interface you buy may have more than 4 pins but the corresponding ones will usually be labeled as TXD, RXD, GRD and VCC. One important point is that you need to cross INPUT with TXD, and OUTPUT with RXD.

The file IpCam serial upgrade.pdf will tell you how to initiate the connection with the boot loader of the camera and what commands to issue in order to upload the recovery files, linux_4Mx16Bit_new.zip and romfs_cmos_11_14_2_17.img (for FI8908W and FI8904W) into the camera. (included W90N745 uClinux BSP User Manual.pdf documents the uClinux commands).

Once your wires are connected, power on the camera, and if you see a screen like the one below, the rest should be straightforward.

Below is the documented procedure as it worked for me. In bold is what you type and in italic what is returned (don't forget to press ESC to enter debug mode as told on screen).

The camera will boot and probably start moving during the initial check up phase, it's back !

The camera may report that no Web-UI is present. In that case, use the IP Camera Tool to flash a normal WebUI file the traditional way (don't use the recovery file for this). Something for non-Foscam devices:
I don't want to be Foscam-centric, it's just that I only have Foscam devices at the moment, so I'll put here similar recovery packages for non-Foscam cameras when available and to the limit of my free storage (mainly FileFactory & Google Docs). They're provided as is and I have no way to test them.

IP607 (EyeSight) found @ Chinavasion: This recovery package is the result of concerted efforts of the ip cam hackers
commenting below this post. It's been made available by Admin (mirror) and contains the adjustments to the fx 6... line. Please follow the instructions in the help.txt.

Changing the MAC address
Some clones, mostly from DealExtreme.com apparently came with the same MAC address, making it impossible to use them together in the same network. An easy way is documented here (mirror). I didn't test it, but according to the feedbacks on Ted's blog, it seems to work great.

353 comments:

I have seen the documentation is very complete. But I do not have the skills to understand exactly how to do, and then, I do not speak English. I did the firmware update to version 1.14.1.43. . Simple. There is no FW that can easily load and change the MAC? Thanks for the answers.

I want use my original foscam FI8908W buyed from andy.lig.I must use upnp but I have this message in administrator panel: UPnP Failed: Errors in Chat with UPnP Device.The firmware is Device Firmware Version 11.14.1.46 Device Embeded Web UI Version 2.4.8.12

Dyndns is ok. I have enabled upnp on router and use a lot of varius port (80, 81, 8080, 8005) but I don't access the ipcamera in internet.I add a virtual map function on router Dlink G604t dls but I don't access the ipcamera in internet. How can I solve?

Hey Bubbah! Love reading the blog! I'm considering purchasing the Focam camera but don't really want to spend $100USD and be disappointed when I get it. Is there anything I should know prior to buying it? Is there anyway I could view someone's live feed to get a sense of how it is? All the demos I can find online seem to be dead.

@Aaron,You can have a good idea of the features and bugs in the firmware history page.One of the most ennoying pending issue is the camera being unable to re-connect by itself when the connection has been lost for any reason (router restart, interference,...). There were many complains about the colour rendering in the early production but Foscam said they now fitted a better lens. I have only older fi8908w but I replaced the lens for 5 bucks and it imporved the image quality a lot! see here. There's also some screenshots on that page.

As it's difficult to know if you're really buying a Foscam on eBay (some advertise openly Foscam products and their screenshots show a completely different UI, like this guy here), they posted the names of some resellers on this page.

I'm in process setting up a live cam at my place! I will post the link here, as soon the cam is mounted to the roof and the wifi is working ;-)But I still fight with the webpage, because the javascript on it does not submitt the username and passwort for the cam-user. I will post my code later. Maybe somone can help me solve the problem.

@BubbahAre there any (original) lenses with IR Filter so we can get the "regular" color from outside?? I do not need the IR since the cam is on top of our house :-)

@Stefan,the only alternative lenses I know are the ones from DX (and eBay) mentioned on this page. They give a much better image but have IR filter. It's not perfect for colors, but I found the tree to render a bit less pinkish.

Since I updated my camera, I can see with the “IP camera tool” that the device firmwire is loaded to the system 11.14.1.46 and the Web UI shows 0.0.0.0.the camera from the network (ping). The camera is restarting everything 15 seconds. I have 2 seconds to connect with

@Rob,If you're going UART, the files linux.zip and romfs_cmos_11_14_1_37.img which are part of the recovery files downloadable in the post above must be used, the usual firmware files won't do.Before that, you could try the cgi command upgrade_htmls.cgi(url would look like http://ipcam/upgrade_htmls.cgi) to try re-uploading the webui file (all versions available here)

@Rob,yes, that's true, it's POST only, I think there's an example of code in the ip camera manual (see firmware page again). Firmware-wise, these cameras are different, but I believe it's possible to jtag it with the recovery files from this post (it would turn it into an illegal Foscam copy, but that'd be just one more in a million :)) .

You could still run this through Chinavasion under warranty, but don't tell them you flashed your camera with a 3rd party fw of course.

@orionsm,that bootloader is the only way (afaik) to get some control over the camera when things go wrong. I recovered mine from a very bad flashing experience, so it looks like the bootloader is likely to survive to that.It took me some time to get a stable enough connection. Make sure that you connected all the wires properly (and crossed tx with rx's) and that your ttl module does 3.3v, not 5v like many. Don't give up too quickly.Good luck.

@BubbahThanks for the quick reply. I am using the USB to serial UART as you linked to on e-bay. Connecting a serial cable from the pc to a serial socket on the UART. Then using a hard wired connection as shown in the above diagrams and downloadable .PDF to the cam. I hope I have followed the instructions correctly? Once connected all I seem to get in Hyperterminal is a few random and strange letters & shapes.Thanks for your help and time on this.

@orionsmIt took me quite a while to get a clean connection. I was about to use a solering iron (could still be an option for you) but I eventually manage to keep the 4 wires on the pcb by using some blu-tack putty. Quite a dirty job, but it worked. I too got scrambled letters at times, but that's probably when the wires a in contact with each other. Of course, don't forget to power the camera on only when you think the wires are in place and the terminal ready.

@Bubbah Thanks for all your time and knowledge on this one. I'm glad I wasn't the only one getting scrambled letters. The wires have been soldered onto the camera board whilst it's still attached to the camera. Would this pose a problem? I still can't believe I was foolish enough after all these years with PC's to attempt firmware over WIFI..... A lesson I should of known better.I'll persevre with the above instructions and hopefully get past the scambled letters

the specification of RS232 on your PC are not compatible with the TTL level in the camera. So you need a TTL level converter. Also make sure that you get a module that does 3.3v. If it's not specified, assume it's 5v and don't buy.

My camera was not bricked, but i buy the interface posted by bubbah for testing purposes (http://cgi.ebay.ie/CP2102-USB-TTL-RS232-Serial-Port-Converter-Transceiver_W0QQitemZ350292739492QQcmdZViewItemQQptZUK_Computing_NetworkingCables_RL?hash=item518f1305a4) for about 9-10 euro with shiping to Spain and work great, i conect only 3 wires Tx,Rx and GND, because it drain power from usb. This interface is another gadget for me, and it is userful for comunicate with other devices because it convert USB to: db9Male, db9Female, Rs232 pinouts, ttl3.3v pinouts and ttl5v pinouts.

Rob, Looks like I have similar issue to you. I have (had) Foscam clone, which I tried to upgrade over wifi (very stupid thing). Currently it turned into piece of brick, however what you can do - you can create simple html page with 5 rows inside put you ip address of your camera there and you can try to upload web gui. I can post this html here if it's OK. For me it does not work anyway, I'm waiting my adapter USB 2 UART 3.3v adapter to put firmware.

@orionsmmy operation described in this post was done using USB with item #160380454276 from eBayIn a comment earlier here, I understand that villamany made a successful connection to his camera with this other item.It's quite plug 'n play, the drivers are generally installed automatically through Windows update and the virtual COM port appears. Just make sure it's set for 115200 bps 8N1 and no flow control.

yes, sureelectronics interface work fine with only 3 wires conected. Bubbah do you know any way for download/upload files to uClinux filesystem by serialPort? I want to modify the web interface files located on /home folder.

Great I'll give it a spin using the USB on the same item that Villamany used. Still trying to get past those random symbols & letters and I'll be there (hopefully). Lesson learned, NEVER flash over wifi again, however good the wifi connection is. :-D

@villamany,I've included the file W90N745 uClinux BSP User Manual.pdf with the recovery files but I didn't really look much into it. Maybe something of use in there?I was wondering if it could be instead possible to mount and tweak the linux.bin to enable telnetd, then flash it back to the camera. That would give some access to the files... but just thinking.

Many thanks for all your help on this, finally got the cam up and running after using the USB UART block. Used a USB cable and followed the supplied instructions, after finding the correct COM port on Hyperterminal and the step by step instructions finally performed the resurection. Couldn't of done it without you ...... Thanks again!

Hi mate, Can you do a favour? Can you please go to your bootloader and type i. It will show WBL information (number, board information and processor name) of your camera board. I'm trying to use Foscam firmware, but it looks like my camera not compatible with Foscam. Just wondering do you have the same hardware like mine or not. PS. With this problem I can change my Oracle DBA position to Linux embedded software designer soon...

XMODEM can not send LINUX.zip and romfs.img :-(Look at photo:http://tinyurl.com/yjm3qfjand photo before delete img and linux from camerahttp://tinyurl.com/yb6lma2could you help me? My camera is broken :-(

@Komornick,Flash size if half of what I have on my Foscam. I guess you need a specific recovery file from the manufacturer of your camera. You'd probably also need a specific address to flash the files with the fx command.

@orionsmThere's still the option of having one camera wired and the other one wireless, so 2 different MAC addresses are reported. Also, in the recovery package from the post above, I've included an auto-translation of a txt file with upgrade instructions, and at the end of it it says something like: "Press ESC to set MAC addressset-mac0 00:11:22:33:55:66"So it seems possible but I'm not sure which Wi-fi or Ethernet address it changes and if it works at all.

@Dragonset_misc.cgi has actually been implemented from 11.14.1.41. Your version is from April last year, but it's a good sign already if it responds to a command like get_params.cgiIn doubt of the origin, contact Foscam with your DeviceID to find out.

I have a Foscam clone (Maygion/DX SKU29918) which has turned it's back on me. I tested the camera some time ago and probably must have changed the deafult user /password as the camera will not let me log on any longer. There is no error message, the logon screen just reappears.As this is an outdoor edition, there is no Reset button to be found. Anyone having hints/tips how to get past this?

@Biscaya: If this is the IP-603, I would assume that you have 3 ends to the cable coming from the camera: one is for the power, another is Ethernet and on the third one should be the reset button? This is the case for the Foscam FI8904W.

Bubbah, the Maygion manual is somewhat on the poor side. I was at the impression that the third cable was for motion detection alarm output. Will try to short the two ends of the third cable and see if the camera defaults back to factory settings

@Biscaya:they probably decided to assign this cable to the +5v alarm output instead. You'll probably find an unused connector on the camera pcb marked something like RST, that you could try to short (for 5 sec) to factory-reset the device.

Hm, I was hoping to be able to distinguish reset button wires from alarm output by voltage. I'll see if I can find a suitable resistor to short circuit the connector, just in case if wires are alarm output in stead of Reset.

Hi,I'm Having trouble with the uart way after a bad Wi-Fi upgrade!!This how far I got so far,Deleted 6&7,Re FX'ed Recovery Files,Re Booted,and this is what I get in the Hyper terminal Window See Below thanks Erik

Are you pressing ESC quickly after you power on the camera?? I believe that you are NOT entering on the bootloader... Because, if you do not press ESC, the serial connection act as a console and displays the boot process.. and it seens that your romfs.bin is broken, causing the kernel oops that you are seening on the console. Read carrefully the serial upgrade instructions to check when to press ESC and enter the bootloader.

I had similar problem like Pfauto (same HW = same flash size = probably same clone), but erasing flash settings (by using "del b31" in debugging bootloader console) helped me to move next. Now the camera makes initial movement but after that the "myreboot" command is self executed and the board reboots in infinite loop - boot, initial movement, reboot.

During initial boot the camera requests IP address from DHCP server and strarts responding to ping. Also the IP Camera Tool detect the camera with no Web GUI installed...but it takes some seconds and camera reboots.

There is no difference between flashing the romfs image into Foscam advised address space and Fernando's advise.

The message [27] is normal. See above(snipet from a normal boot):(...)*args===255.255.255.255*args===netmask*args===eth0[27]ntpc.c: can not resolve ntpserver(time.nist.gov)'s ipntpc.c: can not resolve ntpserver(time.nist.gov)'s ip(...)

Probably this is from an internal process called by the "camera" app running in background (I can check it later).

The message "myboot" is used during the firmware update process, after the firmware has been received and burned into flash; As far I understood, somehow your cam thinks it has been upgraded and is looping into this process.

Have you tried to erase the linux.zip and romfs.img from flash and sending it again?

I'm cooking some new firmware to this cam (with a better watchdog, telnet and busybox)... and I can send you another version of linux.zip and romfs.img if you want to try to see if it fix your cam.

I have tried to flash both files many times to standard and to different address spaces but with same result. I think that there is any flash parameter that causing the "camera" process to think that the state is not standard and it tries to reboot (as you said).

I have been making firmwares for similar embedded platforms (RTL8181 and RTL8186 - wireless AP's) so I have some experience with compiling customised binaries with linux SDK's (with BusyBox) but I did not find any useful information about compiling the uClinux for this kind of devices (and absolutely no info about the "camera" process).

I will very appreciate if you send me another precompiled linux.zip and romfs.img to try recover my camera. And I will be very pleased if you'll share your knowledge about this platform and its SDK for me to help you make the firmware better than it is ;-)

My contact e-mail is intex@seznam.cz .

I would like to publish the firmware to some public storage if I will successfully recover my camera with it.

I'm having some really weired problems with my FI8908W camera from DX. The image it produced turned completely white at some point and adjusting brightness or contrast did not help. Rebooting (soft/cold) did not return the image. I decided to restore factory defaults via web GUI and now the camera works OK, except that it can no longer connect via WLAN using WPA/WPA2. Yes, I'm pretty certain the WLAN setting are correct, as I have tried about everything.

My Fonera AP which used to work just fine with WPA & FI8908W now reports: "Fonera user.warn kernel: Replay Counter Different in pairwise msg 2 of 4-way handshake!" and no connection is established.

So I just ordered a USB to serial UART in order to try if the procedure described here would do the trick and restore normal operation. Firmware upgrades or downgrades via the web GUI have no impact on the WLAN behavior.

Hi fernando,Sorry for not replying sooner ,sometimes I have alot of play time and then not so much at times.Yes I have entered the bootLoader before and have deleted the img and re uploaded the recovery files as stated in the first post,I just posted my log of a normal boot to show someone my problems and codes ,but I'm not into uclinux at all so error codes I'm at a loss,looks like a address space alignment problem or something like that,there is no info on how a person determines the correct address apace to load the files for me to check against so I 'm just going by what was on this site ,this all happened after a wifi update,and before I upgraded everything was fine and I had the foscam user GUI and firmware identical to foscams I did buy this from a ebayer(world_brands)or something lilke that,but mine looked like a foscam to the TEE.After messing around one night I'd try too tim tyler it so I upgraded the firmware and now a Brick for the firePlace so here I am trying to fix the oops :)

Hi, I already had an USB to UART interface that I've used for another application. I connected to my FI8901W and it works, I can have the communication.My problem is now to find the recovery file for this camera. I have contacted Foscam, but I don't have any answer yet.

Could the #2 (Output) pin from the IP Cam's circuit board (seen in the image on top of this page) be used to recover the serial bit-stream from a command such as http://[ip_addres]/comm_write.cgi?port=&baud=&bytes=&data= as shown in the SDK ? This would be a very useful thing. This command works for me, however there is no serial (RS232) port/connector on the camera and therefore I cant recover this serial data.Thx. Joel

@DavidSorry David I mis-read the model. All i know about my recovery files is that they can work on FI8908W and FI8904W. the model FI8901W is particular as there are 2 hardware versions requiring different firmwares.You should contact Foscam directly with your DeviceID to get the appropriate files.

@BubbahFoscam has been very helpful with me. I have exchange a lot of emails with Doris from their sales support who has sent me A LOT of different recovery files.You're right, there has been a lot of different models and mine is the Zaapa version. My camera was like dead, but thanks to your information I succeeded to reload a similar firmware to be able to update the right firmware and Web UI.Today I did the last update and now it works again. Thanks to your Blog and big thanks to Foscam!

Glad to find out that my foscam clone is not completely useless yet!I bricked it trying to updat over WiFi, grrrr...

Now, when I connect it, the IP Cam tool does see it after a few seconds, and it says 'wrong subnet mask'. By right clicking, I can change that quickly, just before the camera resets itself. Then, I shows up again, saying that the UI is not present. I can try to update, but it gets to about 75% as it resets itself again. This resetting can go on for hours!Is there any other option than your rescue method?

I've been too brave and flashed my Foscam clone with Foscam firmware...got a brick..I flashed the FW, never got to flash the web UI.It comes up in the IP camera Tool for a few seconds, and complains that I need to flash the webui, but I can never finish the flash as the cam resets before it can finish.

Photos of the cam and the PCB:http://www.imagebam.com/gallery/bae3a5053b91854549e8c1bd223e006c/

I should also add that the original firmware had a version number 3.23.2.4 or very similar. I have no idea how or where to get a compatible firmware...Maybe one of you guys who have clones could contribute.

To sum it up: flashed FW, now turns on for 3-4sec, reboots, turns on and reboots.Visible in IP cam tool at moments.

I have a Max3232 chip (needed it for flashing my BT GPS) I could use to flash it through jtag but need help on how to wire it (have serial ports and a usb->serial dongle).

Hi,I looked at he firmware zappi posted and the version number don't correlate with mine.Could someone please take a look at the photos I posted a few posts before and help me identify the camera?Thanks

for Jasper:I have two easynp FS-613A-M136 cameras with different version of firmware:1.firmware 4.23.2.5 and webUI 4.3.3.392.firmware 4.11.2.5 and webUI 4.3.3.38I want to save somehow the firmware 4.23.2.5 firmware from the first camera and flash to second camera.I already have webUI 4.3.3.39 from your link http://www.dolkfm.tk/webcamrecovery/click.php?id=1 .is there a easy way to extract the firmware :) ? Or ,do you have the 4.23.2.5 firmware?I don't know if the 4.3.3.39 webUI works with 4,11,2,5 firmware.Pls help...

Hi all,got my cam back running after using easynp files from intex website,only thing is this isn't the firmware and webUI that was on the cam,seems all the cams are the same maybe one MFG making them as thought of by others as well ,My UI was identical to foscams except it was on the opposite side as foscams,other than that looked identical,now this easynp ui is nothing like what I had befor it's red with a slide out window for the pic.anyone have any clue to what is going on here??Also to get this to work I had to use a different linux.zip from lawerences site to make it boot ,it kept locking at image 7 for a while then after the new image it booted,although it takes longer after image 6 gets processed then to 7 is where it takes a while,but does boot.Thanks Erik

@ vlad,This is the only firmware i've got from easynp. I think it would be possible to download the romfs and linux.zip from your working camera. You shoud connect it the same way that's described on the top of this tread. (i used an old nokia data cable from a cel phone). If you manage to receive the files from the camera.. i would like to try them in my cam too.. and update the download link with this newer version.My cam now runs on fw 4.11.2.15 and webui 4.3.3.39

I wonder how I had a foscam looking web UI that looked Identical,or is there another oem with a FosCam look A Like Web Ui ,That I might of had installed when I got the cam,Which will also take the EasyNP Files??

Also forgot to mention in last post,I wonder why I had to use larwerences Linux.zip inplace of the Easynp,also now I don't have sound or acess to the mic,it says no such feature on the cam from within the web UI?

@allI've updated my post above with the recovery package from Admin for the IP607 clone. I don't know if the same is usable for EasyNP (It seems to share the same flashing addresses as the IP607 but I don't know for the firmware files). Would someone (Intex?, pfauto?,...) make a specific ready-to-use package? Also added a "Recommended readings..." section with some remarkable links mentioned in the comments.Thanks guys!

Bubbah, thanks very much for your help. Upgrading the webUI using the IP Camera Tool worked!

I did try doing it yesterday aswell, except at that time I was getting an error message saying image refused by camera or words to that effect. But I did have the browser running yesterday at the same time. Whatever it was a reboot and a fresh try worked.

Thanks Bubbah ;)it works fine for me for an other clone.My clone camera has a "LOW" white LED instead of the normal green LED MODEL: APM-J011-WShttp://www.apexis.com.cn/Products_List.asp?id=1385I've used your tools-package with the FI8908W recovery files => OK.IPCamTool has found the clone over the LANI've upload, with IPCamTool, into the Winbond CHIP,the correct fw files from the manufacter:http://www.apexis.com.cn/dow.asp=> J011_Upgrade System Firmware.rar=> Upgrade Web UI Firmware.rarThere are 3 versions into the rar package correspondingto the 3 versions of PCB of clone, so be careful...GOOD ;)Bye

@Paillassou, nice one Paillassou. I think I'd have to start building some sort of database with all these cameras and their respective recovery procedure & files. Might be a delicate and lengthy process though.So far I have EasyNP, EyeSight, Heden, Maygion,...

I have same problem as Uplitaar (var app_ver='0.0.0.0') except IP Camera Tool does not detect the camera. Having trouble figuring out to reinstall the WebUI firmware using the "upgrade_htmls.cgi". I understand "http://192.168.1.104/upgrade_htmls.cgi?next_url=" it is what goes after "url=" I cannot figure out. Something like..."http://192.168.1.102/upgrade_htmls.cgi?next_url=\Documents and Settings\AAA\My Documents\Foscam\WEBUI\2.4.8.14.bin"Thank you in advance for any help.

I'm having the same problem as Dan and Uplitaar. After upgrading my Cam i can no longer access the UI and it errors me with a 404.

Accessing the cam by CGI works fine, the get_params.cgi shows the following Firmware and web UI:var sys_ver='11.14.2.17';var app_ver='0.0.0.0';

Accessing the cam with the IP Cam Tool works but when i try to upload a new UI version i get the following error: Error File of web UI. And when i try to upload an older Firmware or UI it says: Refused by camera!

Seeing i also have very little experiance with CGI commands i was hoping someone could tell Dan and me what the upgrade_htmls.cgi command should look like or how to use it...

I have a clone wich I think it is an Easynp but its the B-series it seems. Thats what the manual says and everything I can find seems to reflect that. Does anyone have the firmware for this, the fosscam firmare is the similar as I at least get a small pan and tilt action but then it just reboots again. I've tried all other firmware with no luck.

I would like to try the Serial method of accessing the camera but cannot seem to find the serial update document stated in the above article. Please point to the right direction to get the document. I am not sure if the document name written in bold is supposed to be a link but it doesn't work for me.

"I have forwarded this to our software engineers,they said it is impossible to use cgi strings to update firmware in rencent software.If Web UI is lost,pls dbclik the error information appeared in the IP Camera Tool and update the web UI."

Guess they missed the part in which I said IP Camera does not recognize the camera at all, so no ip address populates the list.

I have received another two cameras (real Foscam) for my friend and I must say, that Foscam's Web UI is total crap in comparison with EasyNP's UI.

It has only ActiveX and Push interface (instead of additional JavaScript interface for mobile phones in EasyNP's UI) with stupid method of authorization (need to re-login after page refresh instead of browser authentication)...furthermore you cannot define in Foscam's UI the speed of movement as in EasyNP's FW.

So I am working on porting EasyNP's Web UI into Foscam cameras for the best experience of these great gadgets ;-) (but it is relatively problematic, because UI is dependent on the "camera" process of the FW which is not inter-compatible)

Does anyone have any clue what my cam is. Like I said I get pan and tilt for a couple seconds with the Fosscam firmware but it reboots with the code [27] and then Myreboot. I got it on Ebay all I know is it says B-series I believe it's and EasyNP but it doesn't work with the EasyNP firmware.

Identify the cam http://picasaweb.google.ru/shel32/NoNameIpCam#5478551678508500322. Tried all the firmware, none is not suitable.All but sees only 8 megabytes of RAM should be 16 megabytes.CAMHED02IPW sees 16 megabytes but crashes with an error: (Before rebooting the relay clicks.

Hello everyone,could someone tell me what IPcamera clonehas this interfacehttp://3.bp.blogspot.com/_m16_YxsBJsw/Spz7r7ZV-zI/AAAAAAAAKc8/tIOyVl8GT8g/s1600-h/notFoscam2.jpgand what is the manufacturer?THANK

To aurilius, Dan, and others who have experienced the problem where the system firmware is successfully updated, the Web UI is wiped out in the process, and the IPCamera tool no longer finds the camera on the network... I found a solution after the same thing happened when I flashed the new 8908w I got today.

First, confirm you have this problem by accessing http://YOUR_CAM_IP/get_params.cgi (replace YOUR_CAM_IP with the IP address of your camera). You should see something like this in the report:var sys_ver='11.14.2.17';var app_ver='0.0.0.0';If you do not receive any response at all, then the below fix is probably not going to work. Double check the IP address you used. Otherwise, if app_ver reads 0 as above, then that is a clear indication that (somehow) the Web UI got wiped out and needs to be restored. Hopefully the fix below will work for you as it just did for me...

The fix (note: Foscam was mistaken that it is "impossible" to use cgi to update firmware):1) Download curl (http://curl.haxx.se) for your OS. I'm running Windows, so I used this one: http://www.gknw.net/mirror/curl/win32/curl-7.21.0-ssl-sspi-zlib-static-bin-w32.zip.2) Extract the curl .zip file to the same directory as the Foscam firmware files that you downloaded and used to flash your camera.3) Open a command prompt and navigate to the directory containing curl and the firmware files.4) Type the following command (be sure to substitute your information as appropriate):

curl -u admin -F file=@2.4.8.14.bin YOUR_CAM_IP/upgrade_htmls.cgi

Obviously, you must replace the username "admin" with your own if you have changed the default. You will be prompted for your password when you enter the command. Also, be sure to replace "2.4.8.14.bin" with the filename of the Web UI firmware included with the version you downloaded.

If everything goes well, the result of the above command will be a simple "ok." You can verify that it worked by checking to see if the "get_params.cgi" command now reports a non-zero "app_ver" and by trying to access the Web UI of your camera. With any luck, you will be back in business!

Can someone help me, I have a clone cam that I think I may have finally gotten the firmware for as the ones already listed wouldn't work with mine. Can someone email me a cyberm1477@aol.com as I need someone to extract the firmware files so I can upload them via serial link.

OMG, after reading the entire comment list and developing my soldering skills :D ! i tested EVERY linux.zip and romfs.img of Intex site (Thank you so much for your efforts!) Finally, i found that my camera is a CAMHED02IPW ! I sucessfully restored the camera ! Thanks to Bubba, Intex and all other members involved =D !

PS. To those who have problems sending the linux.zip and romfs.img, try to switch the fx 6 for the fx 7 instead, linux and then romfs or romfs and then linux.

Good MorningSomebody can verify these two devices and to verify if they communicate with the Foscam?http://cgi.ebay.com/USB-2-0-UART-TTL-6PIN-Module-Serial-Converter-CP2102-/180528593122?cmd=ViewItem&pt=LH_DefaultDomain_2&hash=item2a0857b8e2http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=110423840510&ssPageName=ADME:X:AAQ:US:1123Thanks in advance.

Hello! This is my first post in this blog. A month ago I bought three cameras W90P745 model (from Chinavasion.) Everything worked perfectly until one day a camera stopped working.The camera turned on, but the green light on the front is not lit, either with the cable or wifi.I decided to buy the cable and try to come back to life using your method.

I can connect successfully to the camera, I have completed the first two steps:

del 7del 6

But both the rise of file romfs.img linux.zip as 30% I get a message "General failure" (I select the file and put Xmodem protocol.That may be happening?

@Jose,did you download the recovery files suitable for your IP607 (EyeSight)? (See the paragraph for non-Foscam models)Your ipcamera uses a smaller firmware and can't hold the Foscam files. Also you need to adjust the fx commands as per the provided help.txt

@Jose,I don't have this model so my experience with it is limited, but I see these two hackers web sites where you may get some help:http://www.computersolutions.cn/blog/tag/foscam/http://irishjesus.wordpress.com/2010/03/30/hacking-the-foscam-fi8908w/There are several ref to W90P745. I hope they can help you,good luck

@sanbruceYou need one usb-to-uart interface as presented in the article. The usb side goes to the PC usb port where it will create a "virtual serial port".With the other side, you need to connect wires from TX,RX and GND to the J2 port on the camera board (you need to open it to see this). The 3.3 power is facultative since your camera has a power source already.Only for illustration purpose, you can see a bit more pictures in this other article

@sanbrucehave you check that other article I indicated earlier ? There's a clear picture of the cabling there!I'm afraid I can't do much better myself. I'll try to add pictures on my post next time I jtag my camera.

please see where I am wandering:http://img443.imageshack.us/img443/4743/dsc08279a.jpghttp://img835.imageshack.us/img835/3350/dsc08284.jpghttp://img832.imageshack.us/img832/9025/dsc08286s.jpghttp://img832.imageshack.us/img832/9025/dsc08286s.jpghttp://img299.imageshack.us/img299/3456/dsc08285s.jpg

@sanbruce(omg!) well yes, that much clearer now!You are trying to interface a TTL directly to the RS232 of your PC. This is not gonna work.That's why I mention those converters at the top of my article. You can find them eBay. You need to ensure that whatever model you buy will do 3.3v logic and not 5v like most of them.

This site is great, i built the serial interface max232 and tried all the firmware on the site h**p://ipcam.intexcz.net but all do not work and the camera is reset continuously.The camera is identical to this one (same colour too):http://www.netwave.cn/en/productShow.asp?ArticleID=Q7R07RU638But in the site there is no way to download anything !!!Here are the logs from the terminal:....*args===eth0[27]write i2c errorwrite i2c errorwrite i2c errorwrite i2c errorwrite i2c errorwrite i2c errorwrite i2c errorwrite i2c errorwrite i2c errorwrite i2c errormyreboot

I have not tried the firmware for the apexis, anyone can divide me in linux.zip and romfs.img?That's my last chance :(Thanks a lot!Giampaolo

A few weeks ago I found this site and had hope for my recently bricked FI8908W (bricked updating via LAN.) I picked up a SURE CP2102 USB to RS232 gizmo, opened the Foscam up today, got a terminal going, and this is what I see when I power up:

And it freezes up there. Try as I might, I can't get "ESC" sent to the device to stop the boot process and follow the debrick instructions. I find it suspicious that the boot message says "Baud Rate : -1" but I've seen boot logs from working Foscams posted here and there and it seems like a common thing. However, the fact remains that I can't send any keystrokes down the wire. Any suggestions?

Purchaced a FI8908W about 6 months ago and set up all the users and wrote them down, since then I have lost said account details so resorted to pressing the reset button so I could use the factory set username 'admin' with no password. But this does not work and I can no longer login. Anyone came across this before and if so what was the fix.

@ken.nessworthyIt's not just pressing the reset button, the right procedure is:- with camera not powered, keep the reset button pressed- power on the camera while keeping the reset button pressed!- do not release the reset button before the camera starts giving signs of booting (self rotation, green led on, click from the speaker ...)It should then be set to factory state

Hi people,I bought a camera in dealextreme, http://www.dealextreme.com/details.dx/sku.26358could someone tell me which is the model of my camera?My camera is bricked, im trying to flash with a lot firmwares, but nothings happens.This is mi camera.http://picasaweb.google.es/joseramonlopez/IpCamara#

@J.RamonIf they didn't change the specs of this camera, it was able to use the Foscam firmware. The bootloader should then report Mem Size 0x800000 Bytes and Flash size 0x400000 Bytes.I'd say you should try the recovery files + instructions made for Foscam.