Registered a URL and setup a forum as the IPCam stuff really needed its own site vs my irregular blog posts about IPCam hacking at

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - TheUberOverLord

Pages: [1] 2 3 ... 16
General Discussion / Re: FI9831W - Linux-compatible WebUI?
« on: October 20, 2016, 12:31:50 pm »
Please see this. It works with many different IP Camera brands and models including Foscam, Axis, Amcrest, Hikvision and virtually any IP Camera that supports pulling snapshots using HTTP and HTTPS methods and does not require any plugins.

It's compatible with any Internet browser capable device that's using any Operating System and browser.

More here with live demos:,748.0.html


General Discussion / Re: Secure Methods Using PHP To display Your IP Camera
« on: September 05, 2016, 07:49:31 am »

Live example of Amcrest IP Camera using automatic refreshed snapshots and Digital Zoom. Totally secure without exposing any IP Camera information. No DDNS, ISP IP Address, Port or User Credentials are ever exposed and is compatible with all Internet capable devices using any browsers from Computers to Tablets to Phones and TV's. Without ever needing to install or download any plugins or media players:

Example of live Amcrest IP Camera with camera controls. Including PTZ, camera zoom and digital zoom:

You can also choose your own unique User Id and Password as well:

User:admin Password:admin

Note: You can use HTTPS as well. The test server running these live demos is using a self-signed certificate so it's normal to see a warning. Which you would not see with a proper HTTPS certificate :


Created Version 5.

Download Link:

Live Demos Using The Software:


1. Faster processing and less overhead.

2. Added digital zoom option.

3. Now supports Digest Authorization.

4. Images/Logos can now be embedded in the cameras image from a local file or from a website using HTTP and FTP.

5. When embedding images from weather sites. A delay can be used that stores the weather image in a local file and only gets a fresh copy when the weather website updates their image. Some weather websites update their weather images every 20 minutes. So this reduces logo/image processing and overhead. By storing the weather image locally and only making a remote request as needed.


-Free IP Camera Software For Websites And Personal Use  -Live IP Camera Demos Using The Software  -About Me


Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 15, 2016, 04:38:37 pm »
Do you read my post ?

I contacted with in December
"I write to support with problem on other IP camera FI9900P in december after firmware upgrade fail
I write all email number in all country I found - they didn't help me
21 december received reply from they will check workaround method
and they doesn' reply to me"

They don't help me !!!

I asked you to use a Specific email address to Foscam.

That said. We can do this your way.

I have sent you a PM ("Private Message") here in this Forum, with my email address. Please forward the emails you have sent to Foscam, to me. So I can see who it went to and what dates it was sent. Then I will work with Foscam using those emails which I will forward to the people I will work with at Foscam.

This will show the people at Foscam that I will work with at Foscam to resolve your issues. That you have tried and have been trying to get help since December, and have not received any help about your issues.



Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 15, 2016, 12:37:58 pm »
This isn't direct contact.

I don't think they help me.

How is the email address, found at that link:

Not a direct contact to the manufacturer? It goes to which IS the manufacturers website.

Please take the time to carefully read/re-read the page where this direct email address to the manufacturer is located:

As I have already stated to you, in the Forum:

I'm a Moderator in the community Forum. I will help you. But you first need to contact them and explain your situation, in detail. That's not asking for much.

If you're not willing to try and do that. Then I can't help you with the manufacturer. So, do you wish to try and get your camera fixed or do you only wish to get the "Root" password for the camera? Time will tell.


Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 15, 2016, 12:19:09 pm »
I don't lie but you

Your reply

you know it load another firmware to camera and you tell him to reset camera

you lied write "Because never have I ever suggested that using a cameras "Hard Reset" button can unbrick a camera. "

Please give me direct contact to peple who send me new board

I write to support with problem on other IP camera FI9900P in december after firmware upgrade fail
I write all email number in all country I found - they didn't help me
21 december received reply from they will check workaround method
and they doesn' reply to me

The Forum thread you reference. The person stated:

Quote from: soaoga
The FOSCAM 9828 does not appear in tool ipcam program! I reseitei and saw that it works[/] , but I can not see .

No, I can not log in because the camera does not appear and do not know how .

I would have never initially suggested for this person to re-try using the cameras reset button. Had the person in question not have said and stated "I reset and saw that it works".

After the person in question. Satisfied me that they indeed did hold down the reset button long enough for the camera to complete a hard reset which they said worked the first time ("See their quote above"). After they tried the reset again and it failed. I responded with:

Quote from: TheUberOverLord
Quote from: soaoga
No! Every procedure has been accomplished , but the camera does not appear in IP cam tool !
Please contact your seller to see how they say to proceed.

More details on why you should do this for some issues which may not be easily resolved here:


So your analysis of what I said and why, in that Forum thread. Was and is incorrect.

This link is/was also in my initial response to you, in this Forum thread:,1454.msg5044.html#msg5044

The email address for the manufacturer can be found after going to that link:

Note: I also gave you this same link in another Forum as well and asked you to also contact the manufacturer by the email address found in it. I did that MANY... MANY... times there:

So, now I wonder if you read any of my posts?


Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 15, 2016, 10:51:49 am »
I don't want tool I want password for u-boot

Copy encrypted firmware from one to another is working

You don't know how it works

I read your last messages on Foscam forum with bricked cameras where your solution is reset camera to factory default. You know that this won't work but you write this.
This is the same situation.

Please provide the direct link, to this fictitious post you claim I posted, or stop lying.

Because never have I ever suggested that using a cameras "Hard Reset" button can unbrick a camera.

Camera "Hard Reset" buttons, don't unbrick cameras. They "Reset" unbricked cameras to factory defaults. Nothing more.

The manufacturer in this case, maybe willing to help you. They could easily ship the main ("Working") PCB for the FI9828W camera model to you. Without the need to send a complete camera. That said. If you keep Lying and don't lose the "Attitude". I won't work with or help you with them, to get that possibly done.

When you disrespect and blatantly lie about people. Who are trying to help you because they won't give you Exactly what you want. Yet, their help in their way. Can and will help to resolve your issue. Odds are good, that at some point. Nobody will wish to try and help you. In any way!

If you can't lose the Attitude? I can only suggest that anyone seeking payment for this password. Should get a decent price, as well as make sure you don't/can't contest the payment shortly after getting the password only to have that payment canceled/refunded. Because you claim, that you did not get "What you paid for".

You, doing something like that. Would seem to fit your current disposition.


Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 14, 2016, 07:17:34 pm »
I dont't use DDNS I know what I'm doing
You haven't this password I know you have only tool which doesn't need this password

You don't know how flash from u-boot

please don't reply in this topic

If anyone know this password for u-boot foscam cameras I can donate it via paypal

I'm very aware and have been very aware, on "how to flash from u-boot". One of the many examples I have posted, on this subject matter:,473.msg2577.html#msg2577

Please also see this:

Please Click On This To Learn More About Me

Please carefully re-read my prior post here. Because you are missing some Other very important details about your camera model and what's required for successful serial recovery of the Foscam FI9828W camera model:,1454.msg5046.html#msg5046


Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 14, 2016, 07:09:27 pm »
If anyone know this password for u-boot foscam cameras I can donate it via paypal

please TheUberOverLord don't reply if you don't want help me

Again, I am and have been trying to help you.

Having simply the password to u-boot will not alone be enough to recover your FI9828W using a serial connection to your camera. This is because of the following:

1. All Foscam H.264 based camera firmware is encrypted. In most cases. Every firmware version uses a different encryption key and those encryption keys are not always the same for all Foscam camera models as well. I know of no case where the "Root" password for a Foscam H.264 based camera model matches the encryption key for the firmware version which is encrypted.

In many if not most cases. The firmware encryption key for the system firmware is not the same as the encryption key for the application firmware in any given firmware version. There are even posts here in this Forum for other Foscam H.264 based camera models. That verify this as fact, not fiction.

Those same post found here in this Forum for other Foscam H.264 based IP camera models also verify as fact. That different encryption keys are used for the application and system firmware for each firmware version. That those encryption keys, also change with new firmware releases.

2. A special .bin file is required to do serial recovery for this camera model. Your concept of trying to copy firmware from one of these camera models to the other in two segments. Won't end up working properly.

3. A Utility is required to reset the cameras MAC Address, UID and DDNS User Id and Password which still requires the Manufacturer to provide those values for the DDNS. Even a Authorized Foscam reseller does not have access to any cameras DDNS User Id and Password.

I have ALL Foscam H.264 based camera models, including the FI9828W camera model. Which is your camera model. To help do Alpha/Beta firmware and recovery testing for Foscam. So, my statements here are not speculation or conjecture. They are fact based.

4. I know this because I have tested serial recovery for this camera model as well as all other H.264 based Foscam camera models. To help Foscam verify that their serial recovery instructions and utilities, in fact worked as the instructions said they will.

5. It's obvious, that your past experiences with using u-boot to install firmware. Have not included dealing with encrypted firmware and the processes required to install that firmware in cameras that use encrypted firmware. Because, you would be asking for much more than simply the password to u-boot if this was not true.

For sure if you had any experience in dealing with using a serial interface to copy encrypted firmware from one camera to another. You would not be saying as you have in another Forum. That if you only had the "password for u-boot" for the camera. That within 30 minutes you would have recovered the camera in question.   

6. Most likely you would also not be using the phrase of "password for u-boot foscam cameras". Because the encryption keys for firmware vary by firmware version and camera model. Secondly, you're really looking for the "Root" password for the camera. Which also is not the same for all Foscam camera models and can also vary by firmware version. It's not just a generic password for u-boot. That always will work with all Foscam camera models and firmware versions.

So, while you think somehow I am not trying to help you. The opposite is true. I am trying to help you do this correctly and not incorrectly. Which by doing this incorrectly. Could brick your camera eternally.

So. Please see this:,1454.msg5044.html#msg5044


Data areas and their memory address locations, that maintain your camera models camera configuration information, are not cast in stone. As they were with older MJPEG camera models or other camera brands and models you may have had experience recovering. They can change from firmware to firmware release for this camera model. So, as an example. Trying to copy firmware from one camera to another that was/is using a different firmware version. Can/could cause unrecoverable results. Due to that fact.

This is why the data area for the cameras settings is normally completely wiped out and re-initialized by using the special serial single recovery .bin file and utilities are used to reset factory default settings. Including but not limited to, the cameras MAC Address.

ALL of the cameras factory settings, including the cameras MAC address need to be wiped out and re-initialized. Which is why
the single .bin recovery file is used. Which overlays ALL of the cameras memory. That was used by the camera before. Trying with this camera model to simply copy firmware and/or factory set camera data. From one camera to another. Is more than asking for trouble. Which is what I am trying to help you avoid.

There is not one single special serial recovery .bin file used for all Foscam H.264 based camera models. In many if not most cases, this special .bin file used for serial recovery is unique for each Foscam H.264 camera model.

I've tried my best to explain to you these facts. Here is Foscam's new policy on using the utilities required to recover your camera model:


Hacking & Modding / Re: Foscam FI9828W U-Boot password
« on: March 14, 2016, 06:10:30 pm »

I need flash my Foscam FI9828W but I don't know password to enter U-boot

Anyone can help me what is this password to enter U-Boot in Foscam Cameras ?

Please see this:

Note: You would need much more than simply the password for u-boot to recover this camera model, via USB TTL. A special .bin recovery file, Windows utilities and so on.

Because of that. Please use the email link directly to Foscam the manufacturer located in the link above.


Firmware / Re: XMeye Hi3518E-based camera module
« on: March 11, 2016, 07:24:32 pm »
The manufacturer of these IP Camera boards does not support using a URL to pull snapshots from IP Cameras that use their hardware.

That said. There are many ways to still get a snapshot. Including pulling one from the IP Cameras that use this manufacturers hardware RTSP video streams. More details here:,1183.msg4630.html#msg4630


I have verified that one can in fact simply re-load the initial snapshot taken prior to actually starting the Windows 7 VM to reset the number of days to another 90. Microsoft allows this. The VM of Windows 7 specifically states ("Desktop Background of Microsoft instructions during Windows 7 VM use") that this is an approved method by them, to re-extend the Windows 7 VM. More details:,1442.msg5012.html#msg5012

Click on image to see larger image of same


I run Ubuntu 15.10 on a Laptop that is a triple boot system for Windows 8.1, Windows 10.1 and Ubuntu 15.10. Using this Windows 7 VM from within Ubuntu 15.10, also allows me besides accessing the IP Cameras interface. To now have access to four different Operating Systems on the same system. For testing.

For the curious. The laptop is a Dell 3541 64 bit based Inspiron running Windows 8.1 and guaranteed to be upgradeable to Windows 10 ("Which it was") , 4GB ram, 500GB drive, 8X DVD +/- RW Drive, 4 CPU cores clocked at 1.8 - 2.4 GHz (With turbo boost) with a touch screen and 15.60 screen size.

Which I was able to purchase from the Dell Outlet on Jan 24, 2016 as a "Scratch and Dent" refurbished laptop from Dell that includes a 1 year warranty ("Which I could have paid extra to extend") for $212.68 U.S. Which included tax and shipping. Original price was $199.00 U.S. Which included shipping, but did not include tax. It was delivered on Jan 29, 2016. Five days after ordering it.

Interesting enough, I  could find no "Scratches or Dents". I checked the Dell outlet laptops being sold daily for 2 weeks before finding this deal. It works well and being a developer which includes developing applications for IP Cameras. I now use this laptop as my primary system yet I have 4 other systems which I was using that each had individually and standalone Operating systems of Vista, Win 7, Win 8.1 and a Win 10 with Ubuntu 12.04 LTS as a dual boot.

I can upgrade to 8GB ram max and may in the future, but my highest ram usage currently is in the high 60 percentiles. Even while running Ubuntu 15.10 with a Win 7 VM running along side it, at the same time. While I have the 500GB disk partitioned to support each Operating System. I have plenty of free disk space. For each disk partition.

I partitioned the 500GB disk:

Win 8.1 300GB
Win 10 75GB
Ubuntu 15.10 50GB - The Win7 VM uses disk space from here.

I can reallocate disk space as needed in the future as well.

I installed each Operating System using the same 8GB USB memory card/stick. Reformatting it after each install. Making sure that all my Windows versions were installed first. Using a Microsoft Utility called "Windows USB/DVD Download Tool" for converting the latest Microsoft ISO for the Windows 10 version. Then finally, converting the ISO for Ubuntu 15.10 with "Rufus" to install Ubuntu 15.10.

Most people don't realize that because Win 7, Win 8 and Win 8.1 can upgrade to Windows 10 for FREE. That if one chooses. One can install Windows 10 and it will activate using the Key for the prior Operating System while running as a dual boot and not replacing that Operating System. Allowing you to run what you have and also use Windows 10. One simply needs to choose the "Custom Install" option and choose a disk or a disk area on the same disk of where Windows 10 should be installed, during the USB memory card boot.

I quote. From the link below:

"WARNING: If you are still using Build 10240, do not use the Windows 10 ISO to format your PC. Upgrade first from an activated Windows 7, Windows 8, Windows 8.1, ensure the Windows 10 installation is activated, then you can perform a clean install. If you are using build 10586 or what is known as the November Update (1511), this rule does not apply, read below.

UPDATE: Previously, Windows 7, Windows 8.0 and Windows 8.1 users needed to have either of those versions of Windows installed and activated in order to qualify for the free upgrade offer. For persons who needed to perform a clean install of Windows 10 from the outset, it was a two step process of first validating the machine through the upgrade routine, ensure the Windows 10 Upgrade was activated, then proceed to perform a Reset. With the latest November Update (1511), users no longer have to go through this process."

The answer above, by Microsoft. Was updated due to the new Windows 10 ISO's, which I reference here.

More details:

The FAQ ("After confirming the Windows 10 ISO you want") from the above link:

Even the tool used to convert the Microsoft ISO provided by Microsoft to use in a USB Memory stick for Windows 10. Which I reference here. Is produced and provided by Microsoft. It's also suggested in the FAQ above under "I've download an ISO file, now what?":

Nothing nefarious was done. All accomplished, by using and following only explicit Microsoft instructions from Using a unmodified Microsoft ISO and their Tool. BOTH directly downloaded from No editing or changes of any kind, were done. No commands were used, of any kind. No deviations, of any kind for the Windows 10 Installation instructions provided by Microsoft, took place. As in EVER.  The Windows 10 installation was activated automatically while maintaining the activation for Windows 8.1 ("As shown below"). As stated and confirmed above. All sanctioned by Microsoft using their latest Windows 10 ISO:

Click on image for larger view of same

Click on image for larger view of same

As you can see by the above images. The Windows 8.1 Dell OEM product key is different than the automatically assigned Windows 10 product key during the install of the latest Windows 10 ISO downloaded from from a USB memory stick which was created by the ISO to USB tool downloaded from and provided by

Activation in Windows 10 ("With updated notes for latest ISO's provided by")

I quote from the link below: "Digital entitlement is a new method of activation in Windows 10 that doesn't require you to enter a product key"

Windows 10 Eula

The EXACT words you see above. When using the Microsoft Windows 10 FREE upgrade. After installing Windows 10. From Windows 10. Can be found here:

All Settings -> System -> About ("Read the Microsoft Software License Terms")

Click on image for larger view of same

Click on image for larger view of same

Click on image for larger view of same

Nothing minus using Microsoft's own latest released ISO for Windows 10, was done to install Windows 10 along side of Windows 8.1 as a dual boot and it was activated automatically by Microsoft afterwards. So, it works and is legal. You need to get certified as a "Para Legal". Because your claim to be licensed to "Practice Law" at this stage. Is laughable, at best.

Everything was taken care of automatically. I did not need to edit any Windows boot-loader options or change any Ubuntu GRUB configuration.

My Bios allows me to choose which boot loader to use. Ubuntu or Windows. I chose Windows. Because I can use F12 during boot to select Ubuntu to boot from at any time and when using the Windows boot-loader, there is an option to boot from Ubuntu. By selecting the choice to boot from another device. The Ubuntu boot-loader also has an option to go to the Bios F12 boot selector as well. So, I have many different options to get to any Operating System.


If you have a Linux system or a Mac system which has not been able to access your IP Cameras. Due to your IP Cameras Plug-in or Interface only supporting Windows. Here are methods that will and do work.

Note: Using the Windows 7 VM ("Virtual Machine") is suggested. Because these VM's created by Microsoft, were built in 2014 and Windows 8, 8.1 and 10 were less stable than Windows 7 at that time.

Please go here from a browser in Linux. This will work for a Mac as well if you select the Mac tab:


Virtual Machine: IE 9 on Win7

Select Platform: VirtualBox

Download the file onto your Linux system.

Then click on "View Installation Instructions" ("From the web page at the link above") and read it and also save the .pdf to your Linux system as well. For future reference.

In Linux. Use the Linux Archive Manager to extract the .zip file after the above download completes. Once done, there should be a *.ova file in the same folder as the .zip file.

In Linux, install VirtualBox. In Ubuntu for example, you can use the "Ubuntu Software Center" to do this by searching for "VirtualBox" and then installing it.

After installing VirtualBox. In Linux. Right click on the *.ova file and then choose open with VirtualBox. It will show default settings. I would stick with the 25GB and change memory from 512 MB to 1024 MB. ("It will work with the 512 MB default but it's slow to load the cameras web interface"). Then create the Virtual machine.

This will allow you to use a Windows 7 VM with both Linux and Mac systems emulating a Windows 7 System a using IE ("Internet Explorer") 9 browser which is compatible with the cameras plug-in. You can then start/stop the VM as needed to access your IP Cameras.

While this is not a perfect solution, due to the additional disk space and memory resources it requires. It does work well to access your IP Cameras from a Linux system or if you have a Mac and you have been unable to access your IP Cameras from your system. At minimum, it will allow you to setup and configure your IP Cameras. From a Linux or Mac system.

Note: You will need to recreate the VM every 90 days because Microsoft forces this VM to expire after 90 days.

After the VM starts. The desktop background will always contain instructions on how to activate and extend the VM. Please read those instructions carefully.

You should be able to also create a "Snapshot" in VirtualBox to reset the expiration. If you take that snapshot prior to initially starting the VM for the first time, after you have set the defaults for the VM. But I have not had it running for 90 days yet to expire. So not sure about that actually working or not.

If that works as claimed ("Update: It does work as claimed") would allow you to delete the .zip and .ova file that were required to initially setup the VM. Freeing up near 8 GB of disk space. By simply loading the VM from the initial Snapshot whenever the VM expires.

You can delete the VM and VirtualBox afterwards. Any time you wish. If you simply want to try this method and change your mind later. Regaining any disk space used by the VM.

If desired. Once you use the VM to setup and configure your IP Camera. You can/could also use methods like this to check on your IP Cameras using any Internet  browser capable device which is using any browser. From within your local network and/or remotely. Without any need to start and run the VM to do so. Just another possible access method for your IP Cameras, once they have been configured:


Firmware / Re: Unpacking Firmware
« on: January 07, 2016, 05:23:22 am »
None of those are useful in decrypting the Foscam C1 Firmware. They all give bad decrypt. It's a different type of firmware. Has anyone made any progress? This camera has been out for about a year.

Here's the current firmware

I need to get into that and rewrite the web interface. Thanks!

Use openssl with the passwords supplied in the firmware hacking forum to decrypt the original .BIN file, then use binwalk -e (extract) to break it into its parts.,687.0.html

Not sure WHY your focus is NOT with creating other methods to do same? Like below. Unless you are trying to make it appear, that YOU are the manufacturer of these IP Cameras and not Foscam?


This Interface shown below. Can be used with any IP Camera/NVR/DVR/VMS that supports pulling snapshots using HTTP and/or HTTPS and is accessible from any Internet browser capable devices. From Computers to Tablets and Phones to TV's. That are using any Operating System and Browsers. Without downloading/installing any Plug-Ins or Media Players and IP Camera image refresh bandwidth can be controlled as well. Which makes it great for web pages in websites as well as for personal use from any of your Internet browser capable devices.


Added live Axis IP Camera demos. Here's one that even allows you to start a train with all IP Camera controls:

Another without IP Camera controls but with digital zoom:

Another without any IP Camera controls and with a thermal image from the IP Camera above:

The Interface supports both HTTP and HTTPS and optionally prompting for access. Even if the IP Cameras does not support HTTPS. Unique User Id and Password that has nothing to do with the IP Cameras can also be used. The example below is using a self-signed certificate so you will see a warning. User: admin Password: admin


Point being. You could and can create the Web Interface of your choice doing anything the default interface can and does and even more. With or without full motion video and/or audio. Without requiring you to modify firmware to do same. That said, without your ("Custom firmware") being installed. Your custom interface would INSTANTLY disappear. Whereas with the approach shown above, it would not.

If you want to take on the chore of constantly creating custom firmware versions. Each and every time that official firmware versions are released by Foscam or by any other IP Camera manufacturer? Then you WILL have a very daunting task. That never ends.

If you assume that any current decryption methods of firmware will remain the same ("Forever") in order to create your custom firmware versions in the future. Then you are sadly mistaken as well. What happens when any decryption methods that you found to work today, fails in the future to work with newer firmware releases, using your approach?

What would you do when an emergency firmware release ("Which you suddenly can't decrypt") is made due to a security exploit of older firmware releases so that those IP Camera owners will now be protected from that exploit? Which generally happens, more than you maybe aware of with All IP Camera brands and models from different IP Camera manufacturers.

Note: I have in the past. Modified IP Camera firmware, to support a custom Web Interface. While it was fun to experiment with and play with. It's nothing short of a complete nightmare to maintain, as new firmware releases are released. Even for personal use only.


Last, but far from least. If you would intend to distribute your ("Custom Firmware"). It best be 80+ percent different than the original firmware. Because firmware is copy written and most likely the IP Camera manufacturers you infringe upon, have much more deeper pockets than you have to throw money at suing you because you created a "Derivative Work" violating their copyrights on the original firmware in question.

I won't even go into one also using firmware version numbers for your custom firmware. Normally used by the IP Camera manufacturer in question and/or what additional monies that manufacturer could be awarded based on how you marketed your custom firmware.

So. Why take on the support overhead and potential legal burdens of creating custom firmware? When you can do the same things using methods, like the above?

Even if, these custom changes you wish to make are for personal use. Using the above shown methods, will generally survive and function as they did, after a firmware upgrade/downgrade. Allowing you and/or others to be able to use the most current firmware for your IP Camera equipment or to even remain on older firmware releases if desired.


Pages: [1] 2 3 ... 16