I just noticed a new firmware version for Ex on the flir support site:
FLIR Ex (3.9.0) Update Pack
Last Updated: May 9, 2017
... FLIR Ex series cameras (S/N prefix: 639). ...
I don't know if that applies to the wifi model but I assume it does as they don't seem to have a separate download for wifi. My E4 hardware 1.2L (non-wifi) has S/N prefix: 639.
I wish you all luck in improving the wifi model.
BOGET,
Thanks for the
detailed pictures
The ASCO was always considered to be a versatile platform that likely had parts not fitted, such as WiFi. Your tear-down has confirmed that belief. The ASCO design was always intended to support Wi-Fi and the Ex chassis even has the location for the Wi-Fi board as you have shown.
You have to wonder whether the Wi-Fi capability was removed from the Ex series at one of the marketing meetings, as either too expensive or 'too capable' for the intended market.
Fraser
BOGET,
Thanks for the detailed pictures
The ASCO was always considered to be a versatile platform that likely had parts not fitted, such as WiFi. Your tear-down has confirmed that belief. The ASCO design was always intended to support Wi-Fi and the Ex chassis even has the location for the Wi-Fi board as you have shown.
You have to wonder whether the Wi-Fi capability was removed from the Ex series at one of the marketing meetings, as either too expensive or 'too capable' for the intended market.
Fraser
Hi Fraser,
I suspect that wireless features doesn't contain Bluetooth, but I didn't teardown that much more detail.
BTW, when you turned the bluetooth section's Boolean function to true at conf.cfc in "ui.d", the WiFi menu will disappear.
Maybe that is signature checksum's problem.
@BOGET
thanks for sharing the images
Unfortunately only the third image is visible.
I checked it with Chrome / Safari / Firefox.
Please check your permissions ...
That is odd. They were all present this afternoon as I looked at every one. Something has gone SNAP !
Fraser
Hi everyone
I have FLIR E4 3.5.0
Please help to make a full backup of the software.
What program to use TeamViewer, maybe TIconfig
@BOGET
thanks for sharing the images
Unfortunately only the third image is visible.
I checked it with Chrome / Safari / Firefox.
Please check your permissions ...
I changed place to store photos, if you still can't see that,
here is the link to album:
https://www.flickr.com/gp/150854135@N06/55Ps0Q
Hi guys,
Because the hardware is basically the same, maybe replace manually all files by FTP to others old E4 backup files,
let FW downgrade to 2.3.0(like be cover the others older E4 backup files, and install the 2.3.0 update pack again).
Is there any possible?
This was considered way back when the first encrypted firmwares were deployed. IIRC you would need to do a hardware memory chip clone for it to work. Sadly this was not deemed possible with the ASCO computer architecture. There is also the issue of the camera specific calibration files that are essential for the cameras correct operation.
Fraser
I made a mistake. I try downgraded firmware to 2.11 and camera (hardware 2.0L) is bricked. On screen is show Flir logo, and not boot. Camera isn't visible in Flir Tools. Only drive named ASCO. It's possible recovery firmware?
From similar stories with the standard E4, it sounds like you have killed your camera. IIRC you are just seeing some sort of boot loader and the camera firmware you have loaded is incompatible with your version of the camera. Other owners have had to return the camera to FLIR for repair at a cost of around 400 Euro's.
I have not read or heard of a way to do a fresh firmware install from your current situation. Sorry the news is not better.
I cannot say whether your camera will be repaired under warranty or whether you will be charged.
This is one of the dangers of installing an older firmware onto a new platform. The firmware you loaded is only part of the equation, there are different boot loaders and different hardware revisions to be considered as well. If the boot loader is incompatible with the firmware version, you get a bricked camera with no recovery route.
Fraser
I made a mistake. I try downgraded firmware to 2.11 and camera (hardware 2.0L) is bricked. On screen is show Flir logo, and not boot. Camera isn't visible in Flir Tools. Only drive named ASCO. It's possible recovery firmware?
Did your camera run finish the all downgrade process?
If it did, you can try to connect 192.168.0.2 via FTP in default setting (don't login with flir/3vlig), and recover it by your backup files.
Otherwise, sent it back to manufacturer.
Did your camera run finish the all downgrade process?
If it did, you can try to connect 192.168.0.2 via FTP in default setting (don't login with flir/3vlig), and recover it by your backup files.
Otherwise, sent it back to manufacturer.
"Update"/Downgrade finish normally, but not boot and not possible connect to device via FTP.
I just got my E4 (non wifi) back from repair with the HW 2.0L and FW 3.9.0. If I can help testing in any way, please let me know.
how it works
Would a live RAM dump be useful for extracting the private key, and would it be unique per device? It's not impossible.
The point of public-private key encryption is that the private key is not needed to be on the device EVER. The device holds the public key, which can be used to verify that whomever wrote a given file had possession of the private key when they signed/encrypted it.
My bad, i saw RC4 and got ahead of the next paragraph. Question still stands though.
Hello all! Any progress on the hack?
I have not tried that, not sure I would know how to go about it honestly. As always if there is anything I can do to help the cause I still have my E4 Wifi running the original firmware as one uploaded in the first post of this thread.
Please forgive my interruption.
I have looked at
MANY of the posts on this thread. And do not see a definitive answer. I want to buy and modify a new E4 which as I understand is now shipping with 3.9.0 firmware. Dropping nearly 1k on a maybe is no option for me. CAN the mods be applied successfully at this time? If so, is there a place where I could download all the files and procedure? Still a work in progress? Perhaps a updated summary post for the layman?
Thanks!
p.s. The work all of you are doing is AWESOME!
If that's the case, then we may have to resort to hardware mods. They can do a lot of things that software mods can't do. Of course, that's probably more trouble than it's worth for most people.
Well, you could always resort to social engineering and try to get someone to leak the keys for signing the firmware.
