Open JayFoxRox opened 7 months ago
gabriellazarescu
commented
1 month ago Hello! So using the link to the full list gives me the updated content of download.tplinkcloud.com? Because I'm looking for two specific firmwares for my Tapo C220v1 which have been released (1.1.14 Build 240714 Rel.76584n and 1.1.9 Build 240329 Rel.47220n) and they don't show up. Thank you for your support!
JayFoxRox
commented
1 month ago So using the link to the full list gives me the updated content of download.tplinkcloud.com?
It's still only those URLs which were made public (or the ones I archive as outlined here).
I manually run a script every couple of weeks which spoofs different products for which I have the serial numbers / hardware fingerprints (mostly from flashdumps or logs of these cameras which were accidentally or uploaded on purpose) - these are required to login to the tplink update servers (.. but could also be used to hijack the camera remotely, so these details are hard to come by).
However, the server only ever returns the latest firmware. So if I run the script too late, or didn't have the data for a specific model, then the filename is likely gone for good. They contain timestamps, so it's impossible to brute-force filenames.
Because I'm looking for two specific firmwares for my Tapo C220v1 which have been released (1.1.14 Build 240714 Rel.76584n and 1.1.9 Build 240329 Rel.47220n) and they don't show up. Thank you for your support!
I own a C220v1 myself (although I don't use it yet, as I still don't fully trust it), so that always has a priority.
I've just reran the script (previous run before was on 26th of July) to collect firmwares and archived:
It can take a couple of hours for it to appear in the index (due to caching in / slow indexing in archive.org)
For 1.1.9 there should be these 3, which are already part of the index:
Given the different build date for the same version (which you requested) I assume they rolled back the original release (which I missed). Typically these lead to the suffix ".rollback" for the original upload.
However, I don't have these rollbacks archived as I only checked on 5th of February and 25th of February. Unfortunately we lack the timestamp for these rolled back files, so we probably won't find them (unless someone still has the URLs or somehow finds a way to get an index of the tplink server).
There are 3 files, as they represent different regions. They might have different Wi-Fi chips or channel configurations, so running the wrong firmware might brick your device or it might lead to illegal use of certain radio frequencies. For some products the firmware installer checks the region information in the file (and rejects it), for others it doesn't (bricking or illegal frequencies). I'm not sure wether the C220v1 checks it from top of my head.
I originally wanted to run my script on GitHub Actions CI (every couple of hours, so less of a chance to miss new files), but I never found time for it. I'd probably have been more motivated if people had donated more camera data so we could archive for more models. The lack of a custom firmware also contributes to a lack of motivation on my end.
gabriellazarescu
commented
1 month ago Hello, thank you for your quick reply. The 1.1.9 Build 240329 Rel.47220n firmware is a beta and it was made after many complaints about terrible audio on C220. With this beta fw the sound is very good, but the only way to get it is to be pushed by one of the forum moderator of tplink (Solla-topee). So I hoped they published it on tplinkcloud and I can download and store it as a backup. On the other hand, they say that 1.1.14 Build 240714 Rel.76584n have solved the audio issue, but it doesn't pop up on checking for update. Anyway, l've just downloaded it by following the link you provided and I can't wait to try it. Thank you so much for your support!
JayFoxRox
commented
1 month ago The 1.1.9 Build 240329 Rel.47220n firmware is a beta and it was made after many complaints about terrible audio on C220. With this beta fw the sound is very good, but the only way to get it is to be pushed by one of the forum moderator of tplink (Solla-topee)
Very interesting. Didn't know there was a forum (or that they'd even respond / engage with users).
On the other hand, they say that 1.1.14 Build 240714 Rel.76584n have solved the audio issue, but it doesn't pop up on checking for update.
Despite the build date, it only got released 2 days ago in the EU region. US and Korea still didn't get an update (which is also why there's only one archived file so far)
There's probably one more region (China?) as this device has 4 OEM Ids (which appear to represent regions).
Anyway, l've just downloaded it by following the link you provided and I can't wait to try it.
Reminder about what I said above about different regions: The file I linked in my previous post is likely for the EU region, as that appears to be the only one that was released yet.
gabriellazarescu
commented
1 month ago The guy who tried this recent fw 1.1.14 writes in russian on that forum page, so is definitelly for EU. Some say that V1.0 is only for EU, but the strange thing is that it doesn't appear on update check, although I also live in EU region. This is the forum page: https://community.tp-link.com/en/smart-home/forum/topic/648234?sortDir=ASC&page=10
All files listed in this repository (revision be120ec3e36a56d6fac7b30d9586fe2be9861c42) have been added to:
https://web.archive.org/web/*/http://download.tplinkcloud.com/* Actually there's more than 10000 files, so the above only shows some files, use https://web.archive.org/web/timemap/json?url=http%3A%2F%2Fdownload.tplinkcloud.com%2F&matchType=prefix&collapse=urlkey&output=json&fl=original%2Cmimetype%2Ctimestamp%2Cendtimestamp%2Cgroupcount%2Cuniqcount&filter=!statuscode%3A[45]..&limit=100000 for the full list
Some files were no longer available as they had been moved to .rollback files.
Additionally, all URLs from other sources have been added (which includes URLs I found on the internet, but also some based on my own script to fetch updates for known devices - this needs metadata of a donor device for each product model, so I'm only getting these for a small number of devices yet; contact me if you want to help).