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 newer FI8908W 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.
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 - GROUND
Pin #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.
Once your wires are connected, power on the camera, and if you see a screen like the one below, the rest should be straightforward.
bootloader > del 6
ERROR: Image 6 is not existed (there was obviously nothing to delete in my case)
bootloader > del 7
ERROR: Image 7 is not existed
with the new recovery files the address to use below has changed
bootloader > fx 6 romfs_cmos_11_14_2_17.img 0x7f0e0000 0x7f0e0000 -aWaiting for download
Press Ctrl-x to cancel ... (while it waits, you have to select Transfer > Send File in Hyperterminal menu, choose the Xmodem protocol and select the file romfs_cmos_11_14_1_37.img)
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
Flash programming ...
.........
bootloader > fx 7 linux_4Mx16Bit_new.zip 0x7f020000 0x8000 -acxz
Waiting for download
Press Ctrl-x to cancel ... (while it waits, you have to select Transfer > Send File in Hyperterminal menu, choose the Xmodem protocol and select the file linux.zip)
CCCC
Flash programming ...
..........
bootloader > del b31 (Clears the flash parameters)
bootloader > boot
Rebooting the system ...
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.
EasyNP FS 613A M136: Check this very detailed recovery guide from Oskys!
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.
352 comments:
«Oldest ‹Older 201 – 352 of 352@Bubbah
With all FOSCAM Firwares from http://ipcam.intexcz.net/FW/FOSCAM the cam blocked at
Wait for auto-negotiation complete...ResetPhyChip Failed
video0 opened
1
1
1
1
1
1
set resolution 4
set brightness 100
set contrast 4
set sharpness 3
set mode 0
__pthread_initial_thread_bos:320000
manage pid:14
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
Hi Buddah,
Many thanks for that, almost tossed it in the bin :o)
Anyone have any suggestions about the ESC key not interrupting the boot process on my bricked FI8908W? I've tried 3 different Windows laptops, and tonight I even tried my Linux workstation using minicom. I'm still just getting the boot log pasted earlier and no ability to send keystrokes.
I bought a IP Cam from ChinaVasion (Foscam clone IP607) The PCB says: ES_IP607_ARM_2 Without thinking I tried to flash a FOSCAM firmware on it. It is now bricked, I have a RS232 thingy, so I can het into the bootloader and tried different linux.zip and romfs.img files, starting with the obvious one yje "Foscam Clone IP607" recovery. When I try this one the cam accepts the files, but when it reboots it reports the following:
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
inet_sr.c INET_rinput 321
action===1
options==33
inet_sr.c INET_setroute 75
*args===255.255.255.255
*args===netmask
*args===eth0
[29]
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
myreboot
And it keeps rebooting.. can anybody please help me recover this cam?
Thank you,
RvBCrS
@Bubbah
I'm getting pretty desperate out here, I have two dead cams no, two good ones left ;) can you please help me dump the firmware of the cam's that are ok and put it on the ones that are bricked? I really hop you can help me. Please contact me at ramonvanbruggen [@] gmail [dot] com
Thank you.
Good Morning
I bougth two FI8908W, one from Dealextreme and other from Andy.Lig (ebay).
Because a wrong procedure I broke both of them.
I fixed the Dealextreme IPCAM using the Bubbah procedure, thanks a lot Bubbah.
But the ebay IPCAM, I can´t fix, I tried similar recovery packages that exist in this blog.
I uploaded this 3 photos and the last procedure log file:
http://rapidshare.com/files/414043579/LOG.txt
http://rapidshare.com/files/414043574/DSC04174.JPG
http://rapidshare.com/files/414043564/DSC04173.JPG
http://rapidshare.com/files/414043550/DSC04171.JPG
If some one could check the files and help me, i will be very glad.
Please, help me.
Thanks in advance.
AOPerusso
Hi,
I tried to follow these instructions,
after connecting to the J2 connector and starting the terminal i got only gibberish and not the bootloader, i tried to change the baud rate and switch between RX and Tx.
Does anyone can tell me when do i get wrong?
Thanks,
Shuki
Good Morning
My camera is very new and i can´t fix it with the files of this blog. Then i asked Foscam Support Center for new files and they send me.
This new files fixed my camera and evey thing is ok.
Enclosed are the files.
http://rapidshare.com/files/415412021/recovery_fw_files_to_upload_11_14_2_17.rar
MD5: C5962154D624CD1DDFC331601C99E6F2
Thanks,
AOPerusso
Thanks John, curl work here.
@AOPerusso
I've updated my post with these newer files. thanks!
I would first of all like to thank all those that went before and did all the homework on this issue -- particularly Bubbah and AOPerusso.
I have a pair of FI8904W (the outdoor version) cameras and I bricked one when the power failed mid-flash. (btw: these are confirmed genuine by Foscam). A Google search produced this page, I bought the adapter on eBay, soldered wires to J2 and eventually brought it back to life. I say 'eventually' because the first set of recovery files (romfs_cmos_11_14_1_37.img and linux.zip) apparently do NOT work on the 8904 model.
However, I can confirm that the newer set (romfs_cmos_11_14_2_17.img and linux_4Mx16Bit_new.zip) recently provided by AOPerusso do work just fine with the FI8904W.
A couple of random notes for other's interest:
J2 is oriented with the power connection labelled "3.3v". The order is the same: Input Output, Ground, Power. Only 3 pins are actually needed -- it is not necessary to connect a wire to the Power pin.
With the older recovery files installed, the bricked camera did something to the IP Camera Utility program -- the first camera would disappear from the list whenever the second camera was powered up. As soon as the second camera was disconnected from the network, the first camera would reappear. The second camera never appeared on the list though.
At the same time, the hyperterminal screen was showing the boot process up to the point of unzipping and executing the linux shell, then freezing, like so:
"Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...
Executing image 7 ..."
From reading other comments, I knew there should be more, and I tried the newer files. (Now that it's working, hyperterm shows a continuous stream of commands and results whenever the camera is accessed.)
The recovery files do not restore the web interface. I had to use the IP Camera Utility to do that (by right-clicking on the camera) and install the firmware upgrade (2.4.9.14.bin) that way.
Once the camera was working, I was able to upgrade the cmos firmware to the latest version (lr_cmos_11_15_2_17.bin) without incident.
For the technically minded, the W90P710 Bootloader users manual is available at
http://www.karingroup.com/eng/product/_private/W90N745%20uClinux%20BSP%20User%20Manual.pdf
I was looking for a way to copy the image from my good camera to my bricked camera. Doesn't appear to be an XModem file upload utility, but the list of available commands is interesting and may prove useful for someone having trouble.
@youtube
thanks, the only reason I still keep the old set of file is because it worked for my own camera, an early production.
Check my "recommended reading" section on the right column. There are links to other tweakers web sites with interesting findings on the Foscam firmware structure.
@Bubbah
Understood. Keeping the old files available is probably a good idea. The US distributor's website explains they no longer make the cmos firmware publicly available because
"Due to a change in the manufacturing process of Foscam cameras, installing the new Firmware on some older models of the Foscam cameras may cause the camera to malfunction. "
Before they took it down, the firmware came with a warning:
"If your firmware is 11.15.1.46&2.4.9.12,you can upgrade your camera to the new version.
If your camera has another firmware version,not mentioned above,pls contact tech@foscam.com to confirm with our engineers that whether your camera could update. Warning ! Pls do not degrade the firmware!!!"
One of your links is a blog that mostly goes over my head, but he mentions that his newer camera came with an ARM7 processor instead of the ARM5 processor in his old camera.
These *MAY* be clues as to which files are required. Perhaps the newer cameras all have the ARM7 and come with v. 11.15.2.17 or later firmware? If so, AOPerusso's recovery files may not work on older cameras, and older firmware may brick newer cameras.
Is there any way I can send you my FI8908W and let you fix my firmware /UI problem? I tried to update firmware via LAN and am lost as to how to follow the directions in this thread. Thanks a million!
@Mike
that won't be possible, just the shipping to and from Ireland will exceed the price of your camera.
Try to flash the latest firmware (from the firmware page) using the IP Camera tool.
If you really bricked your camera (recovery files cannot be updated through LAN!), the instructions above should make sense once you bought the required UART interface . There's nothing complicated. Give it a try.
@Mike,-
Where in the world are you located?
Near Dallas, TX, USA
If you were more local to me, I'd help you out, but I'm in Canada and round trip shipping would still run between $34 to $58 (depending on delivery options). With no guarantee that it would work (eg: it might not be a genuine Foscam, it might be a hardware issue, etc.) If the camera is new, you should talk to the vendor. If they won't help then you'd be just as far ahead to buy the $15 adapter (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=110583224812 - free shipping) and if your camera does not have the connector soldered to the board, find someone local to you who can solder 3 wires onto your board. Then just download the files from Bubbah's post and try them. If the older ones don't work, use the newer ones.
Look at it this way: the camera is dead right now. You can't hurt it any more than you already have.
Depending on what operating system you have on your computer, the adapter will need some drivers. That eBay auction has a direct link in the listing or Vista will go hunt them down for you over the internet when you first connect the adapter.
The other piece of software you will need is a terminal emulator. The best one for this application is probably HyperTerminal. It is included in versions of Windows prior to Vista. It can be downloaded and will work just fine on Vista -- even Vista64.
The one other piece of hardware that you will need is some wire. Bubbah had the excellent suggestion of cannibalizing an old CDRom sound cable -- any techie friends will have several lying around. Plug the one end onto the J2 connector on the camera board and cut the other end off, connecting the wires direct to the screws on the 3.3v UART port on the adapter. Everything is labeled -- you just have to follow the directions. (If I could do it, anyone can!)
(as noted above: if your board does not have an existing connector at J2, solder 3 stiff bare pieces of wire to the connections labeled J2 on the camera board and the cable will plug right on to those.)
I just got my 8908w clone from dx yesterday, I attempted to flash to the latest foscam firmware and ended up bricking it.
I hooked up the jtag. It looks like I have the one with the smaller flash/ram.
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x1000000 Bytes, Flash Size is 0x200000 Bytes
I started following the directions to recover it (11.14.1.37). I was able to flash the main and linux.zip no problem. rebooted fine. Then I tried loading the webui through the ipcam tool. It loaded, but the ipcam tool never saw it again. I rebooted the camera and it pops back up in the ipcamtool, but still says no webui detected. I tried updating it again, and watched the terminal this time. Right after flashing, some stuff pops up in the terminal then this code pops up and locks up the camera.
"Code: 4282c004 4a00001b (e4913004) e4a03004 e1a0ca00 "
I tried web versions from 2.4.8.8 - 2.4.8.14
I tried for hours last night trying various firmwares and addresses. Has anyone successfully flashed a 8908 with the smaller memory/flash?
If so, what address and firmware did you use?
Thanks!
@Mike,-
(Thought I responded yesterday, don't know what happened to it...)
I would be happy to help you out if you were local, but the cost of shipping puts you half-way into a new camera, there's no guaranty that the camera can be recovered (especially if it's a clone), customs hassles, etc. You are really better off to buy the USB-UART adapter on eBay for $15 (free shipping included) and follow the step-by-step directions above. The hardest part is soldering 3 wires to your board, and that's only necessary on some cameras -- others have a connector already there. If you can't solder, find someone local who can. The other thing you will need is an old CD-Rom audio cable that you can sacrifice to the cause. Computer shops and techies have dozens lying around.
The only software you will need (besides the files listed above) is a program called HyperTerm. It comes with versions of Windows before Vista, and can be downloaded off the web and run in Vista or Win7.
If I can do this, anyone can!
Can I just use a serial port on an old computer instead of something that costs half that of the camera?
@T,-
I wouldn't! RS232 (your PC com port) voltage specifications range from -15v to +15v. The directions above warn to use only a 3.3v UART connection and caution against buying an adapter with only a 5v UART. That suggests to me that the serial port voltages would permanently damage the camera.
The adapter is only $15 including shipping on eBay. I paid $100 for my camera. If you got a camera for $30 then you did well!
Sorry about my English.
i found autoReboot Problem. i only fix it by change one IC after Flash new Firmware and it work OK with new firmware.
That IC i know it like 24Cxx but i can't read out it. i don't know why. When i check pcb found that IC 24Cxx pin 7(WP) is Disable. If this IC not found IP Cam will Autoreboot.
i have try this method for some more IPcam. After up new firmware i change this IC form another IPCam have high version Firmware and it work OK.
I think this IC store info anti clone hardware key. Some China Clone IPcam only work with old firmware. new firmware will detect and lock IPcam if it is Clone version.
This is my IPcam pcb with unkown IC image.
http://yfrog.com/6zimag0035jj
Thanks for the info thanh, nice finding!
Hi all
I need little help here.
I'm trying to recover a bricked clone, but I'm unable to enter the bootloader when it asks to press the ESC key, it just continues the boot process and stucks.
any idea about the ESC key? :-S
Make sure you are using a terminal emulator that supports transmitting the escape code. Some don't transmit the escape sequence (Control-^[) when the ESC key is pressed. I used HyperTerminal set to auto-detect the terminal type and it seemed to work.
Fernando said...
Hi,
I have “general failure” in Xmodem transfer. I think it is because I’ve done “del b31″. Can anyone please give the content of this memory block ? (execute in bootloader “d 31″)
I have a Maygion camera, if possible, give the mem dump of this cam, else, give from foscam.
thanks,
m
@Fernando
They seem to have a specific recovery tool here:
http://www.maygion.com/upgrade.html#repairfw
And this looks like the repair tool they're talking about: http://simpleminders.com/REPAIR%20TOOL/
good luck!
@youtube
apparently the TTL adapter I used first was just bad one.
took another adapter and was able to enter the bootloader.
Tried flashing several firmware's (as its no-name clone), and the one that worked is Foscam's 11.14.1.37.
Now i need to load the WebUI.
Which one I should flash?
I was able to flash to any of 11.14.1.XX firmwares, but when flashed the WebUI (2.4.8.8 to 2.4.8.14) i get this output in terminal:
Unhandled fault: alignment exception (13) at 0x00000001
fault-common.c(97): start_code=0x1e2040, start_stack=0x34bf98)
Internal error: Oops: 0
CPU: 0
pc : [<00158218>] lr : [<00065308>] Not tainted
sp : 0061bf80 ip : 00000000 fp : 0061bfac
r10: 003df260 r9 : 000000e1 r8 : 00012980
r7 : 0061a000 r6 : 00000000 r5 : 0017dba4 r4 : 00000004
r3 : 0017dbb4 r2 : 00000000 r1 : 7f200000 r0 : 0032fc28
Flags: nZCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: 0
Process camera (pid: 21, stackpage=0061b000)
Stack:
0061bf60: 00065308 00158218 60000013 ffffffff
0061bf80: 00000004 00000004 0017dba4 00000000 0061a000 00065308 7f200000 00000474
0061bfa0: 00000000 0061bfb0 000127e0 000652b0 7f200000 0001303c 7f200000 00000004
0061bfc0: 0032fc28 0032fc28 7f200000 00000474 00000000 003df4e8 00408008 00000000
0061bfe0: 003df260 0032fc1c 00000004 0032fc0c 001e8cb4 001e4880 00000010 7f200000
Backtrace:
Function entered at [<000652a0>] from [<000127e0>]
r5 = 00000474 r4 = 7F200000
Code: 4282c004 4a00001b (e4913004) e4a03004 e1a0ca00
As you may guess IPCamTool still says there is no WebUI, and I'm not able to access the camera in web browser, says "do_file: can not find file index.htm" in terminal.
Any ideas?
Great Blog Bubbah!
Odd issue here. I've had the Foscam for a couple of weeks now. Its been working fine almost.
The camera came with Device Firmware Version 11.14.2.26. webui of 2.4.8.14
I've read on some forums that FW was new as of 22/09.
If the leave the camera on its own and check the UI via FF or IE it will work fine. If I connect it to Zoneminder it locks up after a couple of days.
Last night decided to change the lens to a wide angle lens. In the process of removing the lens and unplugging and plugging PS; I thought I bricked the cam. Green light would go on but cam never rotated. No ping.
I made a quick JTAG cable using a nokia USB cable. I opened up the Foscam. The model and date of MFG are on the PC board. So I guess its real. After connecting my JTAG cable watched and noticed that camera is in an endless reboot.
I manually rebooted a couple of times and a couple of times it came back to life; after a few minutes though it starts to reboot. I saw some write errors when it did boot up. Now the errors appear to be related to not opening video.
Before flashing I was hoping to download the current files so that I could re update to current version of FW. It sounds like no one has been able to do that yet.
I am just wondering if anyone has had the same symptoms and when calling the Foscam bricked; is it in an endless reboot mode?
@Pete_C
If you didn't try re-flashing your camera yet, just don't. Your firmware level indicates that it's a Foscam branded (with logo), for which Foscam introduced a new firmware line (from 2.26 onward). This document was made at the time there was only older non-branded-but-genuine-Foscams if you follow me (latest fw is 2.17). I received this information from Foscam only this week and didn't have time to
update this article.
If you really think you bricked your cam(I don't see how this could happen just by changing the lens), contact tech@foscam.com for help, they certainly have the appropriate recovery files for you. But first head to the "FAQ for Ip cams" on this blog and check if you really cannot get the camera back using the IP Cam Utility.
good luck!
Bubbah,
Guess after watching it reboot and wondering why decided to flash it with the:
aw version is 11.14.2.17
aw version is 2.4.8.14
Mistake.
I can get to the Camera's GUI just fine. I left the JTAG cable to watch. Seeing this though:
Buffer overflow: bad data packets 80005 80000
Buffer overflow: bad data packets 80667 80000
Buffer overflow: bad data packets 80083 80000
Buffer overflow: bad data packets 80003 80000
(about 100 lines or so).
When I bring up the video; it doesn't work and resets itself showing the following:
Wait for auto-negotiation complete...OK
100MB - FULL
video0 opened
1
1
1
1
1
1
set resolution 4
set brightness 100
set contrast 4
set sharpness 3
set mode 0
unknown command
__pthread_initial_thread_bos:358000
manage pid:14
video stop
myreboot
It does this every time I access the video. Before I "downgraded" I could get to the video but it would take about 3-4 reboots to start.
Initially my issue was that it ran fine without the connection to Zoneminder but when I connected it to Zoneminder it would only run 3-4 days then lock up.
I don't believe it was changing the lens that caused my issue but rather the unplugging and replugging rapidly a few times in a couple of minutes that may have caused the original issue. The lens works fine (as far as I could tell from the couple of times I've seen video).
I will write to Foscam for help. So I guess its not totally bricked just that the video doesn't work.
Thank you for your suggestions.
Pete
As you can now load the user interface, it's probably just a question of of flashing the proper firmware either from the ip cam tool our the web ui now. Good luck.
My Foscam clone is back to life after flashing CAMHED firmware from IntEx repo.
Thanks IntEx
Thanks Bubbah. I wrote to Foscam earlier.
Hello people,
Problem solved (at least, my problem). The Xmodem file transfer works fine now. I was using a laptop with Linux (and some times a WinXP VM), I think something is wrong with the laptop serial port timers (also used a USB-> serial interface) or maybe its Linux.Now I'm using a desktop with Win7.
Now I have to find Maygion's original files ;-)
Thanks for your support
Foscam tech support has responded to my questions.
They have asked if my camera is still functioning with the downgrade. I have written back to them stating it is but Video is not working.
Funny that the camera is now totally disassembled sitting on my home office desk and wife is asking what it is I have been playing with.
Very nice support. Technical support sent me the FW files today. Only they sent me the .17 ones (old ones). I requested same as I had on the camera.
Hi, anybody knows if this http://tinyurl.com/2brvorf adapter has restrictions to see the booloader?
When I start hyperTerminal the first thing that I can see is:
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #1214 R; 12TB 1
4 19:21:29 CST 2009
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
.. (and other stuffs)
I tried to quickly connect disconnect but nothing, any tips?
Hi.
I'm sitting here and trying hard to unbrick my cam.
I have come so far that I'm ready to upload the system file. But then I constantly get General Error. (Starts to upload)
Anything I can do about this?
It seems to stop at 180K (Uploading any of the two files.) I'm now starting to wonder what version of the cam I have.... Is there any hints on how to hunt down the correct firmware?
I recently purchased a Foscam FI8908W. From the above description I believe it was a Foscam "Logo" camera. It had fw v.11.14.2.26 on it. I bricked mine (assumption) when powering it down and up a few times quickly in succession. I then made a JTAG cable. I watched the terminal session and noticed that my camera was in a constant reboot state. I was able to get to a bootloader prompt and was able to load the binaries as previously discussed bringing the camera down to fw v.11.14.2.17. I wasn't aware that I could not do this. Once at this FW level the camera did boot (with overflow errors) and did enable the GUI. The problem was that I was unable to get to see the video. As soon as I would go to the video link my camera would reboot (watching the terminal session). I wrote to Foscam Tech and they sent me the fw v.11.14.2.26 FW files. They did not send me the binaries. I was able to load the fw v.11.14.2.26 via the GUI FW update page. I am now running again fine with FW fw v.11.14.2.26.
Mao - I am a newbee at this but it appears that you have a good terminal session. Leave your TTL/Serial connection enabled and watch the entire boot sequence. You will notice a prompt to hit "ESC" during the boot sequence. If you hit "ESC" then you should be able to get to a bootloader prompt. I am not familiar though with your TTL to Serial device. I used a modified Nokia Mobile phone cable - cutting off the end exposing 3 wires (RX, TX and Ground) and used this for my JTAG connection.
UngeDanielsen - I've not heard or read of your problem. I knew which FW I had on my camera before the mishap. You might have a clone and simply do not have the memory to load said firmware (2 mb versus 4 mb). You could try lowering your comm buffer values to see if that helps at all.
Bubbah - thank you for your help with my concerns. Foscam Technical came thru with the FW and I am running again. I was going to request maybe that they send me the binaries such that if I do brick the camera I could load these instead.
I did have a heck of a time installing the wide angle lens. I ended up lubricating the threads a bit and using a needlenose plier to turn the lens to the position of a good focus. It is working. The problem is that the top of the lens is even with the LEDs. When they are on all you see is the reflection across the surface of the lens. It would be beneficial to either disconnect the LEDs or put some sort of ring around the lens such that the reflections don't hamper its use. I took apart the original lens. There are multiple parts to it. The top of the lens cover unscrews. The outer most lens is held in place by the top cover. The top cover of the original lens (with teeth) allows simple removal of the original lens and blocks the light from the LEDs some from the lens itself. I wish I could find a wide angle lens with similiar construction or utilize these pieces on the newer lens.
The camera it seems doesn't like being in a constant streaming to ZM state (640X480) locking up after about 12-14 hours. Thinking now of leaving the JTAG connection up via an always open terminal connection.
I did notice a few errors (same as with earlier FW) on the boot up sequence so I'm guessing that the FW is still kind of half baked and needs some more updating.
@PeteC
The problem is that I can't see the boot loader, even if a wait the full boot process, this first thing is:
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #1214 R; 12TB 1
4 19:21:29 CST 2009
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
.. (and other stuffs)
And I understand that, this is after the booloader, so it looks that:
1. Or my bootloader is not enable to show anything (I don't know if this make sense)
2. Or my USB 2 Serial (http://tinyurl.com/2brvorf) is not fast enough to show me the booloader
Mao,
I believe the bootloader has to be present to get to the boot process. Try just hitting the excape key continuously after you plugin the camera with the JTAG connection.
Is your TTL to RS-232 getting its power from the camera?
Try to power the TTL-RS-232 from your converter instead of the camera.
Relating to my endeavor and camera.
Foscam has sent me the binaries for .26. The loading addresses are the same as the .17 binaries.
I am now seeing a whole new batch of issues when booting (and rebooting).
aw version is 11.14.2.26
aw not exist !
aw version is 0.0.0.0
Foscam support has been nice responding to all of my emails.
BTW - ordered the new model Foscam yesterday. Should be a week or so before I get it.
Hi Pete_C,
I tried to use power from camera, from converter and no success.
Now I bought a Serial 2 TTL, in 3 weeks (when it arrive here) I post the results here, so, for me, my converter doesn't work as expected.
Thanks for your answers!
I am at a constant rebooting camera. Nothing is working. I load the newest via JTAG and just watch it boot over and over. Foscam technical support has been great. They said to send the camera back to the vendor. Only thing is that I've taken it apart, installed a new lens and JTAG connector so I cannot at this time. I think prior to all of this there was something going on anyways because the camera would always lock up after 3-4 days. I would unplug it wait a few minutes then plug it back in and it would come back to life. I guess just wait for the new camera for now.
I have received new Foscam and it is working well. If I connect it to Zoneminder at 640X480 for streaming video it will lock up after only a few hours using the streaming CGI. This does not happen with the 320X240 mode. If I do a snapshot cgi pull with ZM instead it doesn't lock up.
This old Foscam is a paperweight and I have brought it back to life a couple of times; it'll run fine until I work it a bit then it goes into its continuous boot state. I don't think there is anything wrong with the HW but am wondering still about what issues would cause it to lock up.
Hi
Please help someone...
Is it possible to tell from the hyperterminal reading what kind of clone this is?
And what .zip and .rom file I need to wake it up again?
I have tried to download different roms and zip files without luck.
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on May 11 2010
Memory Size is 0x1000000 Bytes, Flash Size is 0x400000 Bytes
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:
MAC Address : 00:B8:00:00:07:11
IP Address : 0.0.0.0
DHCP Client : Enabled
CACHE : Enabled
BL buffer base : 0x00300000
BL buffer size : 0x00100000
Baud Rate : -1
USB Interface : Disabled
Serial Number : 0xFFFFFFFF
For help on the available commands type 'h'
Press ESC to enter debug mode ......
Cache enabled!
Processing image 1 ...
Processing image 2 ...
Processing image 3 ...
Processing image 4 ...
Processing image 5 ...
Processing image 6 ...
Processing image 7 ...
Unzip image 7 ...
Executing image 7 ...
Linux version 2.4.20-uc0 (root@maverick-linux) (gcc version 3.0) #1042 Ò» 12ÔÂ 7
05:49:33 CST 2009
Processor: Winbond W90N745 revision 1
Architecture: W90N745
On node 0 totalpages: 2048
zone(0): 0 pages.
zone(1): 2048 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/rom0 rw
Calibrating delay loop... 39.83 BogoMIPS
Memory: 8MB = 8MB total
Memory: 6272KB available (1447K code, 284K data, 40K init)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
PTZ Driver has been installed successfully.
Winbond W90N745 Serial driver version 1.0 (2005-08-15) with no serial options en
abled
ttyS00 at 0xfff80000 (irq = 9) is a W90N745
Winbond W90N7451 Serial driver version 1.0 (2005-08-15) with no serial options e
nabled
ttyS00 at 0xfff80100 (irq = 10) is a W90N7451
I2C Bus Driver has been installed successfully.
Blkmem copyright 1998,1999 D. Jeff Dionne
Blkmem copyright 1998 Kenneth Albanowski
Blkmem 1 disk images:
0: 7F0E0000-7F16CFFF [VIRTUAL 7F0E0000-7F16CFFF] (RO)
S29GL032N Flash Detected
01 eth0 initial ok!
which:0
PPP generic driver version 2.4.2
Linux video capture interface: v1.00
Winbond Audio Driver v1.0 Initialization successfully.
usb.c: registered new driver hub
add a static ohci host controller device
: USB OHCI at membase 0xfff05000, IRQ 15
hc_alloc_ohci
usb-ohci.c: AMD756 erratum 4 workaround
hc_reset
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver audio
audio.c: v1.0.0:USB Audio Class driver
usb.c: registered new driver serial
usbserial.c: USB Serial Driver core v1.4
Pls sby help me...
I've this kind of shit, but can not realize
which exact type... I have two cams. And like to use the same FW / WebUI on them...
Original FW was sth like 0.xx.xx but unfortunatelly I don't remember it... :(
I've tried almost every FW but it doesn't work
for me...
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Dec 10 2009
Memory Size is 0x1000000 Bytes, Flash Size is 0x200000 Bytes
TEXT on PCB: IPCAM_PT2_V3.3f_sc
Pls sby could check the Log and the PCB?
http://rftech.hu/IPCAM/myPCB.jpg
http://rftech.hu/IPCAM/Log
I've tried last time as 607...
A user from another forum (named Lloyd) was kind enough to send me the firmware files (and the instructions) for my bricked Foscam clone, and i was able to bring it back to life. I’ve tried all the other firmwares i could find on the net, but none of them was able to do the job. Only Lloyd’s files were correct for my model.
My FOSCAM Clone has the following info:
————————————————————
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Dec 10 2009
Memory Size is 0×1000000 Bytes, Flash Size is 0×200000 Bytes
Board designed by Winbond
————————————————————-
The PCB is 541_CPU.PCB
I would like to thank Lloyd once more.
If anyone else has the same problem and a similar camera feel free to send me your email and i will try to send you the files.
I have a brute-force method (I told KyleM it was a "stone axe") for extracting files from any _good_ foscam clone.
A couple of guys have used the files I got from my 541_CPU.PCB clone with success.
The method is simple and can be duplicated in any programming environment you wish. To keep it dumb-simple, I did it with a Kermit 95 script.
LLoyd
A follow-up. After talking with Kyle at IrishJesus, I realized that one need not know exactly how long the WebUI image is if you want to store it as an invisible (-nofooter) image on your camera. You can just download everything from flash from the beginning of the image to the end of flash, and subsequently upload that same image. If it's a -nofooter image, it doesn't really _have_ a recorded length.
LLoyd
Does anybody have a working camera with PCB:
IPCAM_PT2_V3.3f_sc ?
It would be a great help if sdy can dump the
working firmware (using LLoyd's method) from
it, and share with us / me....
Robert
Another concept Kyle and I talked about was to go ahead and take the time to extract the _entire_ contents of flash -- for analysis in a friendlier environment, like in your Linux or PC system.
When I get geared up to understand the Foscam software, that's sure the way I will go. It'll be a lot easier than exploring the stuff with the bootloader, or trying out one variant after another of new kernels that don't work.
LLoyd
A friend just purchased a newer 8918W. I've asked him to extract the recovery binaries from it, so they'll be available.
These will be nice for me to experiment on, because this will be the first time I have both the authentic Foscam files and the extracted files (from the same camera) to compare to one-another.
LLoyd
Hi... Please. DO NOT REMOVE THIS POST ! hehehe..
I just bricked my IP Camera bought in DealExtreme (http://www.dealextreme.com/details.dx/sku.26358).
So... now I'm waiting the USB to Serial UART arrive to do the unbrick.
I bought this adapter (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190405467837&ssPageName=ADME:L:OU:US:1123).
Someone already used this adapter to unbrick the camera ?
Thanks in advance !
Hello
a newbie to this blog, so please excuse me if that's not the place to post this question....
2 days ago, my foscam FI8908W stopped recognizing my router (TP-LINK)
i reset the camera, installed new firmware and web ui - still nothing.
after reboot the led indicator is blinking slowly and i cant access the camera. the foscam ip tool doesnt recognize the camera as well. neither is a port scanner.
the minute i connect the lan cable, the led start blinking faster and i can access the cam.
wireless setup and port forwarding on my router looks ok (to me....)
is there a way to know if the wireless module on the camera is functional?
additioanl note - i'm using a 2.4Gz RC transmitter (for a remote controlled helicopter). its a new transmitter and although i cannot base my hunch, i have a feeling that it somehow related (does it even make sense?). can this transmitter effect the cam (and not only the router)?
i will greatly appreciate any comments, ideas on how to tackle this issue.
Kind regards,
-guy
@Guy
I supposed that if your transmitter was interfering, it would only last for the time you use it. There are many potential causes of interferences but I would first question whatever has changed 2 days ago. First thing I think of is: did you perhaps set your router to hidden SSID ? The FI8908W cannot connect if the SSID is not broadcast. Did you change the Wifi channel ?
Did you buy any new electrical equipment lately?
There was an old bug where the camera was constantly disconnecting, but this solved with current fw now. If you feel the need to upgrade, contact Foscam first with your DeviceID and fw versions (tech@foscam.com), to make sure you really have a Foscam and not a clone, and if possible, get the update files from them.
Thank you so much for the quick reply
i can't point on any changes made in the last few days.
- the router is set to enable SSID broadcast but NOT bridges
- the router channel is 6, although i dont know where to set it in the camera interface
- i've upgraded both firmware and web ui to the latest version from foscam
in case of the possible channel change - shouldnt a camera reset to default settings and than firmware upgrade solve that?
if i wanted to verify that the wireless module in the camera is transmitting - can i detect it as wireless network in a laptop?
Thanks again,
-guy
@Guy
as a client, the camera will take the channel from the wifi router. That shouldn't be the problem.
You should be able to monitor any incoming wifi request in your router DHCP section as shown in my start up guide. Try to take this guide from scratch, and also use the IP Camera Tool to help you. Put the camera beside the router in case there was a problem with the antenna maybe?
Hello Bubbah
I reviewd the guide carefully and followed each step.
still cannot connect using wireless. the led indicator on the camera keeps blinking slowly, like it searchs for the wireless network but can find it.
i just dont get it - i've setup the wirless connection several times before and it suddenly stopped working.
yesterday i've opened the camera but it looks ok, no strange smell or something eles that can indicate a problem.
do you find it reasonable that the wireles mudule just stopped working? how can i test that? do you happen to know if i can buy it separately and replace it?
Thank you so much for the help.
-guy
I bought this adapter (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190405467837&ssPageName=ADME:L:OU:US:1123).
How can I use this adapter to unbrick the camera ?
To fyreworx Lloyd, admin, Vagelis or
Hi I have an identical camrea to the one you speak about would it be possible for one of you guys to email me the recovery files (my email is rick_rock@hotmail.co.uk). :-)
It would make me a very happy man. after christmas hopefully you can see the cam working at http://www.tanziemo.com/puppycam.html
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Dec 10 2009
Memory Size is 0×1000000 Bytes, Flash Size is 0×200000 Bytes
Board designed by Winbond
thanks very much
rick
Guys, please help me.
I've tried several times but all the firmwares doesn't seem to work. I always get the annoying "myreboot" message and it boots over and over again.
I've tried the recovery firmware (as above), CAMHED02IPW and EasyNP and no one seems to work.
Is there a way to check if there is an hardware failure or I just have to keep trying different firmwares and try my luck?
PS: If you need a log to help me out, I'll happily post it here.
Cheers,
To fyreworx Lloyd, admin, Vagelis or other
Please send me these files because all the others failed.
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on May 11 2010
Memory Size is 0×1000000 Bytes, Flash Size is 0×200000 Bytes
Board designed by Winbond
Thank you
My email tasgaz@gmail.com
Maybe I have found a solution!! I hope that my tool is going to work, will keep you posted:
http://blog.morrison.nl/2011/01/foscam-clone-recovery-tool/
@Ramon
that looks interesting, yes, please let us know how it works!
Hello,
i read all the messages and tutorial on the web, but still not have a solution for my problem :
i do the unbrick the tutorial, and everithings ok, after rebooting, i have :
system : 11.14.1.37
WEB UI : 0.0.0.0
after, i tried to upgrade system and web UI
i can upgrade only the system like that :
11.14.1.37 to 11.14.1.42 to 11.14.1.43 to 11.14.1.46
but when i try to upgrade to 11.14.2.17, problem :
a lot of code and at the end :
*********************************
Function entered at [<0006bf70>] from [<000127e0>]
r5 = 00000115 r4 = 7F200000
Code: 4282c004 4a00001b (e4913004) e4a03004 e1a0ca00
***********************************
and i must do the unbrick again.
but for the WEBUI, no one worked, i try every version at every system version, but no issue
i use the last verion of ip camera tools :
0.0.7.6
0.0.0.36
any one can help me ?
I have no idea what is happening!! I have completed a dump from a working camera, the linux.zip file seems to be ok because I can unzip it and I get a linux.bin file, the romfs.img I can't verfy because I don't have any reference. I have flashed the firmware from a working camera onto the bricked device... and STILL the device keeps rebooting!!! These are the last lines:
set brightness 100
set contrast 4
set sharpness 3
set mode 0
__pthread_initial_thread_bos:35c000
manage pid:16
2
2
2
2
2
2
audio_dev.state not AU_STATE_RECORDING
wb_audio_start_record
inet_sr.c INET_rinput 321
action===1
options==33
inet_sr.c INET_setroute 75
*args===255.255.255.255
*args===netmask
*args===eth0
[29]
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
write i2c error
myreboot
I have 2 bricked camera's both with the same result, so it is not a hardware failure!
I really am out of options now :(
@Ramon
Depending i fyou have an old (non-branded) or new (branded) Foscam, the address to use would change.
I also think that your problem may be related to some hardware check introduced by Foscam.
If you Google on "write i2c error
myreboot Foscam", you'll find several place dealing with this like this one:
http://dangerousprototypes.com/forum/index.php?topic=1197.0
Hi Bubbah, thanks for you response.. that topic on dangerousprototypes is mine too :) I post under RvBCrS too..
I have zipped my tool and posted it here:
http://blog.morrison.nl/2011/01/foscam-clone-recovery-part-2/
It doesn't work for my, but maybe for others
Using translation tool
Only a important information. I have seen many people having problems with IP camera tools, appears empty with no camera.
I got it, and after much time researching, I discovered the problem ....
I have a fake camera of site DX, with red and white packaging.
I had amended the adapter cable to the other wire, so I had more distance to the outlet, after this, the IP camera Tools did not recognize the camera more. To my surprise, only recognized again after discarding the amendment. Therefore, any bad changes in the power supply cable can give problems in these cameras. I hope that helps.
T-board (Brazil)
Bubbah Hello, thank you very much for the tutorial, my case is this, I have done all the steps and when I send the firmware begins to load, but after a few seconds it gives an error "Download error", it can be?, may be able to download the file is damaged?, it may be shipped to another memory address?.
Thank you very much.
@Gustavo,
you first need to know if you have a Foscam or a non-branded 'clone'. The files to use and addresses can vary. I'm trying to put together a comparative table, but it's very much a work in progress. Utilmately you may need to email Foscam with your deviceID to know what your options are.
Hi Bubbah hello, thank you very much for your reply, I tell you that is a clone of DX (the red box), after much trying to achieve load the first file (romfs_cmos_11_14_2_17.img) by changing the connection speed, but then to try install the second (linux_4Mx16Bit_new.zip), loading the entire file and when it reaches the end gives the following error:
PROGRAMMING FLASH ......
ERROR: Write Failde.
Could it be?
thank you very much.
@Gustavo
Try to update the linux file first.
Thanks !
I just got my 8908w clone from dx .I attempted to flash to the latest foscam firmware and ended up bricking it.
I hooked up the jtag. It looks like I have the one with the smaller flash/ram.
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x1000000 Bytes, Flash Size is 0x200000 Bytes
I started following the directions to recover it (11.14.1.37). I was able to flash the main and linux.zip no problem. rebooted fine. Then I tried loading the webui through the ipcam tool. It loaded, but the ipcam tool never saw it again. I rebooted the camera and it pops back up in the ipcamtool, but still says no webui detected. I tried updating it again, and watched the terminal this time. Right after flashing, some stuff pops up in the terminal then this code pops up and locks up the camera.
"Code: 4282c004 4a00001b (e4913004) e4a03004 e1a0ca00 "
I tried web versions from 2.4.8.8 - 2.4.8.14
I tried for hours last night trying various firmwares and addresses. Has anyone successfully flashed a 8908 with the smaller memory/flash?
If so, what address and firmware did you use?
Thanks to Joao Paulo and Bubbah I managed to fix my ip camera, but now I'm going so crazy, the camera works perfectly, but when I disconnect the UART to USB adapter does not work, if it is dead ........ I reconnect the works again ....... you think it may be, may be the source?, (which I have tested and works, measures 4.5 v), a configuration problem ?...... thanks!!
PS: One more thing, anyone know how to set the number of Mac, is at 00:00:00:00:00:01, I've tried from the bootloader but I could not take the changes ..... thanks ....
Has anyone considered writing an application for this purpose? Like a one click UI? Is that too far fetched?
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. http://img16.imageshack.us/g/20110207014.jpg/
Hi, i have an 7Links Robocam (Pearlcam PX-3309-675). I think, its the same as Apexis J-011-WS (the Webinterface was the same).
A error while i installed the WebUI-Update crashed my cam. With seriell-Uart now i have installed different versions of linux and romfs, but the cam works not correct. I cant install the WebUI.
So i think, i need the original romfs and linux for this cam.
Please, can anybody help me?
Hello, from germany, I need the part,
Where can I buy that.
Pay with PayPal.
Please reply to bauerwk@freenet.de
----------------------------------
What you need:
- Your FI8908W (the recovery binaries I have are only for this model)
- a USB to serial UART interface that does 3.3v logic (like this one or this one). 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.
I am getting an error everytime i try to send files. I have used all hyperterminal programs i know. I get "general failure" error
i have double checked baud rate, and xmodem settings everything... it attemps but after half a second that failure popup is shown.
HElp please
I have also made a "del -all" as shown in the video
this is where i get once i boot and then i send an "ls" to see what is there...
Board designed by Winbond
Hardware support provided at Winbond
Copyright (c) Winbond Limited 2001 - 2006. All rights reserved.
Boot Loader Configuration:
MAC Address : 00:0C:5D:75:13:E1
IP Address : 0.0.0.0
DHCP Client : Enabled
CACHE : Enabled
BL buffer base : 0x00300000
BL buffer size : 0x00100000
Baud Rate : -1
USB Interface : Disabled
Serial Number : 0xFFFFFFFF
For help on the available commands type 'h'
Press ESC to enter debug mode
bootloader > ls
Image: 0 name:BOOT INFO base:0x7F010000 size:0x00000038 exec:0x7F010000 -af
bootloader >
Hi. I got my 8908w clone from dx .I attempted to flash to the latest foscam firmware and ended up bricking it.
I hooked up the jtag. It looks like I have the one with the smaller flash/ram.
W90P745 Boot Loader [ Version 1.1 $Revision: 1 $ ] Rebuilt on Aug 19 2009
Memory Size is 0x1000000 Bytes, Flash Size is 0x200000 Bytes
I started following the directions to recover it (11.14.1.37). I was able to flash the main and linux.zip no problem. rebooted fine. Then I tried loading the webui through the ipcam tool. It loaded, but the ipcam tool never saw it again. I rebooted the camera and it pops back up in the ipcamtool, but still says no webui detected. I tried updating it again, and watched the terminal this time. Right after flashing, some stuff pops up in the terminal then this code pops up and locks up the camera.
"Code: 4282c004 4a00001b (e4913004) e4a03004 e1a0ca00 "
I tried web versions from 2.4.8.8 - 2.4.8.14
I tried for hours last night trying various firmwares and addresses. Has anyone successfully flashed a 8908 with the smaller memory/flash?
If so, what address and firmware did you use?
Recovering PX 3309 from Pearl.de
I debricked the PX 3309 with the following files:
https://rapidshare.com/files/1390576251/px3309.zip
used commands:
fx 7 linux.zip 0x7f020000 0x8000 -acxz
fx 6 romfs.img 0x7f0e0000 0x7f0e0000 -a
WebUI-Update with the updates-files from pearl:
http://www.pearl.de/support/product.jsp?pdid=PX3309&catid=1120
See Help-Text for Foscam clone IP607 recovery too.
@ fredmm
Please where can i find this help text for ip607 recovery?
@ tasos
You will find the link on top of this page
http://rapidshare.com/files/384315178/IP607FINAL.zip
I'm having trouble with a camera FI8904W Foscam (genuine).
After I erased the whole flash except bootloader (del-all), I used romfs_cmos_11_14_2_17.img and linux_4Mx16Bit_new.zip with commands:
fx 7 linux.zip "0x7f020000 0x8000-acxz
fx 6 romfs.img 0x7f0e0000 0x7f0e0000 -a
After boot, I received this error:
(it's part of the code)
.................
Wait for auto-negotiation complete...ResetPhyChip Failed
video0 opened
1
1
1
1
1
1
set resolution 4
set brightness 100
set contrast 4
set sharpness 3
set mode 0
unknown command
__pthread_initial_thread_bos:354000
manage pid:14
inet_sr.c INET_rinput 321
action===1
options==33
inet_sr.c INET_setroute 75
*args===255.255.255.255
*args===netmask
*args===eth0
[25]
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
_i2c_write: write i2c error
_i2c_write: write i2c error
write i2c error
myreboot
The camera keeps rebooting and in IP Camera Tool I have the message: "Web ui does not exist, dbclick to change" for a short time (arround 1 second).
I used alternative, romfs_cmos_11_14_2_17.img, whith the same error.
Can you please help with an advice in this case?
Thanks,
Hi all,
seems like i bricked my Foscam FI8905W when updating to the latest firmware. Unfortunately all howtos I can find concern FI8909.
Can anyone help?
Cheers,
Kai
Hello,
Ich benötige die Recovery-Files von der
FOSCAM FI8918W
linux.zip
und
romfs.img
Firmware: https://rapidshare.com/files/1986117781/Foscam_FI8918W_Firmware.rar
Please Help me :-)
THANKS
@PC-Shark
try these new recovery files and instructions just received from Foscam. The post above has been also updated with this link.
PX-3309 is back to life, thanks very much! I had to use px-3309 firmware files I found in the internet.
Now it says BSS list is empty and does not connect to wifi... Any ideas?
ip607final.zip files didn´t work for my PX-3309.
Camera keeps rebooting on and on.
hello Bubbah, please could you upload the "recovery files and instructions" with FOSCAM FI8918W firmware to rapidshare or megaupload, I can't access, I don't know why. Thanks in advance,
Hi Songokoki,
I added a Filefactory mirror on that page,
cheers!
Hi Bubbah, thank you very much!, I've recovered my camera.
does anybody know why my px-3309 doesn´t connect to wifi any more? looking at ttl interface it says bss list empty. I checked the antenna, the cable is not broken.
Hi, from france
Which files, to upgrade a Hedencam ref: CAMHED02IPW 4.0 (Linux.zip and romfs.img) ?
Thank's for your help
Hi José, I'm not sure for HendenCams, but Paillassou probably knows, did you check his thread on hardware.fr ?
After recovery camera keeps rebooting on and on. I push on ESC but does not whork. Please can anybody help me
Thank you in advance
hi there is this usb to uart suited for the job? or is this not good enough? http://www.dealextreme.com/p/usb-to-uart-5-pin-cp2102-module-serial-converter-81872
@timmerman1985
It looks ok for the job but you could find the same 1/2 price on eBay
i am stuck i tried to unbrick it but when i need to download/send the img to the camera it says general failure. i tried both firmwares any idea? thanks in forward
I bricked my camera while following GeminiMark's instructions from here:
http://club.dealextreme.com/forums/Forums.dx/threadid.770929
I lost the web ui, just after upgrading the system firmware to 11.14.2.17 in step #11 (while following all steps in order).
I didn't freaked out at first, because GeminiMark said he also lost the web UI in his process.
I've tried upgrading it with all versions in the file, but none of them worked. After that I decided to read all messages in the thread and then I got scared with the brick stories.
I tried resetting the unit, turning it off and on, and after a few tries I was able to upload the first web UI (2.4.8.11) though it didn't work (before my upload tries ended up in errors.
Then I went on trying resetting, turning it off and on, and uploading the web UI files in order. It finally worked in version 2.4.8.14, which was exactly the next on in my list during the process.
I went on to complete the rest of the upgrades and it working fine now.
Tks GeminiMark for the very detailed instructions!
Help! I don't understand this? "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"
My cam IS missing the web-ui after I did a firmware update. How exactly do I flash a "normal" web-ui the "traditional way"???
I am tempted to just throw the thing away and be done with it. Hate to waste $60 if it is fixable.
I reset the cam via bottom button. It powers up, does self check, and the led light blinks on/off like it should. Need web-ui to make it work, though.
Any help is much appreciated.
@Matt
The webui file to use is not different from the one that would be flashed through the camera interface. But since your camera (webui) is not accessible you need that "IP Camera Tool", which is a Windows program to perform the firmware update. It is generaly bundled with the firmware files. Get the latest one from here: http://www.foscam.com/down3.aspx
You need to register only once.
Next important thing: never flash over Wi-Fi, always use the Ethernet cable.
Recovering the camera from "Error Web UI '(app_ver = '0 .0.0.0') or other problem. (No needing to buy anything)
windows/linux
If you are unable to access the Web interface of the camera because of an unsuccessful upgrade, you can still perform a downgrade to a functiooal 'firmware/web UI'.
The only requirement is that it is still possible to execute HTTP commands, even for the command line, which is the method used and that you know the cam's IP.
1- First of all reset your camera with a clip (holding the reset button for few seconds)
2- Download the program "CURL" which will be used to send commands to send files to run the camera.
Download here: http://www.gknw.net/mirror/curl/win32/curl-7.23.1-ssl-sspi-zlib-static-bin-w32.zip
3- Unzip the file into a directory eg c:\camera\, and put the files that you wolud like to send to the camera in the same directory.
4- As the program "IP Camera" might not work too, look in the router which IP using your camera is using. Or use a specific program to scan your network to find out. (Google it)
5- Knowing the IP camera, go to the command line prompt and navigate to the directory that you unzipped the CURL proogram and containing the files to be placed in the camera.
eg "cd \camera"
6- From within the directory, execute the following commands in order, replacing the [IP] for to camera's IP and replacing the name o files that you want to put in to the camera. For the exemple will be used the firmware "lr_cmos_11_14_1_42.bin' and the WEB UI "2.4.8.11.bin"
Execute the command in order:
First command:
curl.exe --user admin: --form file=@lr_cmos_11_14_1_42.bin "http://[IP]/upgrade_firmware.cgi"
(Wait for the results of the command, it should be "OK")
Second command:
curl.exe --user admin: "http:/[IP]/reboot.cgi"
(To reboot the cam)
Third command:
curl.exe --user admin: --form file=@2.4.8.11.bin "http://[IP]/upgrade_htmls.cgi"
(Wait for the results of the command, it should be "OK")
Fourth command:
curl.exe --user admin: "http:/[IP]/reboot.cgi"
(To reboot the cam)
THE CAMERA WAS RECOVERED.
by @eduyoshida - eduyoshida.com.br
Recovering the camera from "Error Web UI '(app_ver = '0 .0.0.0') or other problem. (No needing to buy anything)
windows/linux
If you are unable to access the Web interface of the camera because of an unsuccessful upgrade, you can still perform a downgrade to a functiooal 'firmware/web UI'.
The only requirement is that it is still possible to execute HTTP commands, even for the command line, which is the method used and that you know the cam's IP.
1- First of all reset your camera with a clip (holding the reset button for few seconds)
2- Download the program "CURL" which will be used to send commands to send files to run the camera.
Download here: http://www.gknw.net/mirror/curl/win32/curl-7.23.1-ssl-sspi-zlib-static-bin-w32.zip
3- Unzip the file into a directory eg c:\camera\, and put the files that you wolud like to send to the camera in the same directory.
4- As the program "IP Camera" might not work too, look in the router which IP using your camera is using. Or use a specific program to scan your network to find out. (Google it)
5- Knowing the IP camera, go to the command line prompt and navigate to the directory that you unzipped the CURL proogram and containing the files to be placed in the camera.
eg "cd \camera"
6- From within the directory, execute the following commands in order, replacing the [IP] for to camera's IP and replacing the name o files that you want to put in to the camera. For the exemple will be used the firmware "lr_cmos_11_14_1_42.bin' and the WEB UI "2.4.8.11.bin"
Execute the command in order:
First command:
curl.exe --user admin: --form file=@lr_cmos_11_14_1_42.bin "http://[IP]/upgrade_firmware.cgi"
(Wait for the results of the command, it should be "OK")
Second command:
curl.exe --user admin: "http:/[IP]/reboot.cgi"
(To reboot the cam)
Third command:
curl.exe --user admin: --form file=@2.4.8.11.bin "http://[IP]/upgrade_htmls.cgi"
(Wait for the results of the command, it should be "OK")
Fourth command:
curl.exe --user admin: "http:/[IP]/reboot.cgi"
(To reboot the cam)
THE CAMERA WAS RECOVERED.
by @eduyoshida - eduyoshida.com.br
Nice one!
I'll try it and will probably put this method into a dedicated post.
Thanks!
Hello,
I try to do a recovery on a FOSCAM FI8918W.
I have a card "USB to RS232 TTL Converter Module 232 PL2303 Chip PC".
When I run the terminal and I do "esc" nothing happens ...
Can you help me?
http://imageshack.us/photo/my-images/29/p1220641.jpg/
It looks like a RS232, 5v logic based module. What you need is a USB to serial UART based on 3.3v, like this one.
If the 3.3v logic is not specifically mentioned in the product description, consider it is not present.
The module PL2303 enables the 3.3V or 5V.
Bubbah Hello, I have two identical cams, one of them stopped working and make the arrangement as it is indicated in the post, now works fine, but does not detect wifi networks, cable only works, the other camera if it detects wifi networks, that can happen?, is there any solution?
Thanks!!!!
Hi, I have a bricked cam to, so I hooked up the serial interface.
I see what is expected except when I press ESC in the loader nothing happens. I can see the ESC going on the serial interface (mine has leds on it) So I know something is sent to the cam but the bootloader just continues to boot normaly.
Then it reboots in a never ending loop. I hear the relais inside click during the process.
Does somebody have a tip how I can enter the debug mode and revive my cam?
thnx
Andy
David
Do you still have the recovery files for zaapa ciprw (FOSCAM FI8901W)? If the answer is yes, could you send me them to publish an article in spanish about how to recovery? Thank you.
@Admin
Hello, thank you for the guide because I recoverred completely my es-607_arm_2 with your recovery package IP607FINAL.zip but I have only one problem: in the mask "Alarm Service Settings", when I check "Alarm Input Armed", it's not longer possible to select the trigger level (High or Low). I need to connect a motion sensor NC because in case of the light mutation I receave a lot of falses alarms.
someone else knows another firmware for es-607_arm_2?
Thanks
Guys, I need some help.
My IP camera is not booting up (rotate onstart is not happening).
Looks like I need to try reflashing. I purchased IP camera from: http://www.ebay.in/itm/ws/eBayISAPI.dll?ViewItem&item=220801206031
And this looks like fi8908W to me. The firmware/UI versions are: (taken when camera was functioning)
DeviceID: 000C5D782BA9
Current Camera ui version: 12.6.7.3
Current Camera firmware version: 12.22.2.39
Any pointers to the correct firmware will be highly appreciated.
By the look of the UI, it is not a Foscam, but rather an Eyesight IP607, like the ones sold on Chinavasion.com (compare with their menu screenshots). This post contains links to recovery files that could be used for IP607.
If your camera still respond to a ping (try wired to Ethernet), you may want to try this other method with the normal firmware files from Eyesight web site
Before i open my camera ...
Does anyone know if it is possible to change the startup position of the camera ?
I have 3 foscam clones, they loose wifi connection regularly, so they reboot on their own, default startup position of the camera seems to be 45 degress up facing forward
@j
I think you'll find the topic #4 of this FAQ helpful...
@Bubbah
Thank you, but unchecking "Go center on boot" in the PTZ Settings was one of the first things i did after installing the 3 cams.
It changes nothing..
But i need to emphasize there crap foscam clones (wanscam)
Looks like they solved it in that thread from Openipcam forum. See where someone posted a tweaked webui file (June 13, 2012, 08:09:16 am).
Just make sure it applies to your model, an AJ-C2WA-C118 I guess.
Stellar article! Absolutely stellar!! Foscam, in their infinite wisdom, and for whatever reason, has released two different firmwares for the same model camera (FI8918W). Admittedly, Foscam _does_ state you will render your camera a paperweight if you try to update firmware v11.22.2.46 with v11.37.2.46 - I should have read the documentation so that's my fault. But honestly, WHY TWO COMPLETELY DIFFERENT FIRMWARES FOR THE SAME CAMERA?!! Thanks Foscam. **said sarcastically with an eye roll**
And thank you, Bubbah at Gadget Victims, for showing me how to unbrick my camera. **Said very sincerely!** It was so easy, a caveman could do it. :-) The hardest part was waiting for literally 15 days for that USB to UART module to ship from Bulgaria!
I want to thank you for the tip.
Now my IP camera is working again.
I can only figure out why the Wi-Fi does not work, that was the problem I had before.
Thank you.
You're welcome!
If the Wi-Fi stopped working suddenly, it could be a hardware failure. If you're lucky it's just the inner connection for the antenna that needs to be checked.
Also consider that if you changed the password to the Wifi Router, or the Access Point name itself and either contains symbols or special characters, this could be a problem too. Make sure they're both short and simple!
Good luck
Hello Bubbah,
Once again many thanks for the tip.
My password is long and has special characters may be my problem.
I have two cameras with the same problem and I think it happened because I upgraded the firmware (11.22.2.30 - Web UI 2.4.8.15).
The camera was also purchased in DX and is a clone of the Foscam.
I'll do more tests with simple passwords.
Thank you.
Camera: IP607 Eyesight
Connected camera to hyper terminal using usb to ttl and rebooted the camera, but no activity observed in hyperteminal.
Camera is completely dead and on powering ON, just 1 green LED lights up on the 802.11bg module.
No movement on bootup, no lights on LAN port, no LEDs elsewhere, no motor movement.
Should I assume that there might be some non-recoverable hardware error in the camera or is there any other option also, which I should try before starting using it as a paperweight.
Hello Bubbah;
thanks for the tip.
I pulled the WLAN module and used a spray cleaning electronic contacts. Thus the IPCam returned to work via WiFi.
And really not allowed to use special characters in the security settings.
All the best.
Thanks.
Mario
Thank you man! You are The One!
Thank you SO MUCH. I saved my Foscam clone (DealExtreme) thanks to your tutorial.
I'm using Windows 7 64bits and had to copy the hyperterminal from Windows XP as I couldn't upload the files with other terminals...
Again, thank you very much for your help. It was fun to open the cam and revive it.
Cédric
Bubbah, do know how I have to connect the J2 for Foscam FI8918W to the UART ? Greetings
It's exactly like the FI8908w. Using the J2 marking as a starting point, pins are VCC (no used), GND (goes to GND on the USB-RS232 module), TX (goes to module's RX) and last one is RX (to module's TX)
Thanks !
About 'general failure': found on some forums that the private version of hyperterminal on windows 7 (in my case Windows 8 64) worked for connection but not file transfer.
Had to do the whole thing through a Ubuntu VM (wmware workstation) with the minicom software. Connected on port 'ttyUSB0' and xmodem transfer went well through a USB to uart device.
Hyperterminal under Windows XP was also commented as working well but I did not have one at the time.
This will work ?
http://dx.com/p/usb-to-uart-5-pin-cp2102-module-serial-converter-81872
?? Its cheap and simple. Thanks
yes it looks fine
Hi, i have 4 foscam with problem, and was not able to solve problem yet, all not work, only power on leds back (network status), it not power on front green led and not start rotate after power on, when i try to locate it it not is found and i am not able to access GUI. So i bought USB to UART: CP2102, model: http://www.ebay.com.au/itm/New-CP2102-USB-2-0-to-UART-TTL-6PIN-Connector-Module-Serial-Converter-/390568168944?ssPageName=ADME:X:RTQ:AU:1123
I have some doubts, i soldered pins on jtag of camera PCB, but i do not understood, shoul i conect: imput to TXD, RXD to Ouptut and Ground to Ground ? Or i have to cross more than i pint with other ? not shoulld conect 3.3 or 5v ? only 3 pins are necessary on camera board ? i tried conect direct and powered on camera, used hyperterminal, configured bauds and another configurations (drive for UART is fine and on Hyperterminal it recognized COM3) conected, but appear blank screen with any text (as it was not reading), what i doing wrong ? I only want acess part that appears a lot of text, so i can follow instructions on video. I do not know why camera stoped, was not in firmware update, it stoped for no know reason. really would like help to solve it, Thanks a lot !!!
You need to link RX-to-OUTPUT and TX-to-INPUT as shown on the bitmap, GND to GND, no need to use the Power pin. Use 3.3v serial mode only. Power the camera normally with A/C adaptor. When started, don't forget to hit ESC on terminal to enter debug mode.
Terminal settings: 115200Bps, 8-N-1, no flow control.
i have a "IP-CAMERA-ID002" the cam responds to ftp (usermaygion) but , it's reboot every 20-30sec.
i don't have board.dat file.
And i don't have rx tx connector what can i do?
Try the repair instructions from Maygion web site, http://www.maygion.com/upgrade.html#repairfw
apexis apm-j011-ws uses same files as foscam 8909 too it works when i flashed that to mie though usb to serial 3.3 v as ftdi basic programmer module
Thanks a lot!
Works on Wansview ncb541/w or an "b series" ip camera brick, and now it's alive!!!. I use linux, romfs and webui images from http://www.openipcam.com/files/Firmware/NC541/NCB0541W/ , and the best terminal for this camera was Tera Term. Just a little problem, easy to solve, The pcb of wansview dosen't have pins, only holes, so it's a little tricky put a molex or another conector, but works fine.
The files are not found on the server
ZD1211B - version 2.24.0.0
usb.c: registered new driver zd1211b
main_usb.c: VIA Networking Wireless LAN USB Driver 1.20.04
usb.c: registered new driver vntwusb
usb.c: registered new driver rt73
dvm usb cam driver 0.0.0.1 by Maverick Gao in 2010-8-3
usb.c: registered new driver dvm
dvm usb cam driver 0.1 for sonix288 by Maverick Gao in 2009-4-20
usb.c: registered new driver dvm usb cam driver for sonix288
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
Shell invoked to run file: /bin/init
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc
Command: mount -t ramfs none /flash
Command: mount -t ramfs none /home
Command: mount -t ramfs none /tmp
Command: mkdir /tmp/run
Command: camera&
[8]
Command: sh
no support
Sash command shell (version 1.1.1)
/> hub.c: connect-debounce failed, port 1 disabled
new USB device :80fb2004-fed740
hub.c: new USB device 1, assigned address 2
p1[7]:1,j 3,config->bNumInterfaces:4
usbaudio: device 2 audiocontrol interface 2 has 1 input and 0 output AudioStreaming interfaces
usbaudio: valid input sample rate 48000
usbaudio: device 2 interface 3 altsetting 1: format 0x00000010 sratelo 48000 sratehi 48000 attributes 0x01
usbaudio: registered dsp 14,35
usbaudio: registered mixer 14,32
usb_audio_parsecontrol: usb_audio_state at 00ff3800
new USB device :80fb2404-fed740
hub.c: new USB device 2, assigned address 3
usb.c: USB device 3 (vend/prod 0x148f/0x3070) is not claimed by any active driver.
aw version is 11.22.2.30
aw version is 2.0.10.15
Wait for auto-negotiation complete...ResetPhyChip Failed
open video device error
myreboot
FI8918W crashes over and over again after doing this using both new and older recovery files.
ZD1211B - version 2.24.0.0
usb.c: registered new driver zd1211b
main_usb.c: VIA Networking Wireless LAN USB Driver 1.20.04
usb.c: registered new driver vntwusb
usb.c: registered new driver rt73
dvm usb cam driver 0.0.0.1 by Maverick Gao in 2010-8-3
usb.c: registered new driver dvm
dvm usb cam driver 0.1 for sonix288 by Maverick Gao in 2009-4-20
usb.c: registered new driver dvm usb cam driver for sonix288
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
VFS: Mounted root (romfs filesystem) readonly.
Freeing init memory: 40K
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
BINFMT_FLAT: bad magic/rev (0x74202d74, need 0x4)
Shell invoked to run file: /bin/init
Command: mount -t proc none /proc
Command: mount -t ramfs none /usr
Command: mount -t ramfs none /swap
Command: mount -t ramfs none /var/run
Command: mount -t ramfs none /etc
Command: mount -t ramfs none /flash
Command: mount -t ramfs none /home
Command: mount -t ramfs none /tmp
Command: mkdir /tmp/run
Command: camera&
[8]
Command: sh
no support
Sash command shell (version 1.1.1)
/> hub.c: connect-debounce failed, port 1 disabled
new USB device :80fb2004-fed740
hub.c: new USB device 1, assigned address 2
p1[7]:1,j 3,config->bNumInterfaces:4
usbaudio: device 2 audiocontrol interface 2 has 1 input and 0 output AudioStreaming interfaces
usbaudio: valid input sample rate 48000
usbaudio: device 2 interface 3 altsetting 1: format 0x00000010 sratelo 48000 sratehi 48000 attributes 0x01
usbaudio: registered dsp 14,35
usbaudio: registered mixer 14,32
usb_audio_parsecontrol: usb_audio_state at 00ff3800
new USB device :80fb2404-fed740
hub.c: new USB device 2, assigned address 3
usb.c: USB device 3 (vend/prod 0x148f/0x3070) is not claimed by any active driver.
aw version is 11.22.2.30
aw version is 2.0.10.15
Wait for auto-negotiation complete...ResetPhyChip Failed
open video device error
myreboot
FI8918W after using the newer files for it. Any ideas?
The new firmware (FI8918W) The new firmware (FI8918W) is compatible with the Hootoo HT-IP206 clone. I need to recover an ip206 from a broken update
I stumbled across this old article and tried to bring back to life my FI8908W (newer model, with logo) with no success. If anyone here in Italy is willing to try the procedure, I'll be more than happy to give away my paperweight cam :-)
Post a Comment
Note: Only a member of this blog may post a comment.