-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reflash old Firmware #4
Comments
Thanks to @kubik369 (https://github.com/nervous-inhuman/tplink-tapo-c200-re/issues/1#issuecomment-1027194068) You can actually downgrade the camera with older firmware through SD card.
Good luck :) |
Does it work for you with only a single partition? As I mentioned in my notes, the card needed to have two partitions (second of which didn't matter, it just had to be there) 🙂 |
@kubik369 Yes it worked with only one partition. |
Great news! I will be doing this today with the one that you linked back to, not sure there is a way to find other versions because tplink does not allow index on their website so we would need the whole url.... I can only assume or hope that the version that you found the URL to will still support the features that I am looking for, namely auto-track, auto mode for light/dark, etc. but it is not too far from what I know does.... chances are good. Thank to both of you! |
@ThongSong7 If you were able to give me the exact version string you see in the app for v1.0.14 (with the rel. number), I may be able to give you the download URL for it. |
Well ok I'm not sure if I can anymore.
The only part we can't know from the app is the part after last underscore, which I assume is the date and time the FW is uploaded to the server in millisecond since Linux epoch. |
Thanks for the offer, I am going to try first with the one you already found: 1.0.10, not far from the 1.0.14 that is on the original one with auto-track '"free". |
Thanks again, it worked. Small feedback, when flashing via a FAT32 SD - you will see the green LED start to blink showing that it is flashing the bin file via the SDCard. When it is done it remains steady green: this you will know that it is done.... unplug, remove SDCard and replug and it starts normally. This is a God-send, now they cannot get out to WAN to check fir updates.... not having that problem again :-). Hats off to @kubik369 for having found it! Auto-track working well, have not yet seen any negatives for what I use the cameras for. Even if you had enabled the auto-track prior to flashing, you will need to disable and enable it again, for some reason it did not work otherwise. |
Hello! Someone can send me the firmware for Tapo C200 v1? Last update brick my camera and I would try to restore the old one... |
https://drive.google.com/file/d/1SVJYUs2HYI2gzeeUhk8ow6YteLrQmhgP/view?usp=sharing |
Would anyone in here have or know where to get the firmware version v1.0.14? I have two that I flashed back to: "Firmware: 1.0.10 Build 200520 Rel.45325n(4555)" based on above, but they do not follow movement as well as "Firmware: 1.0.14 Build 200720 Rel.38552n(4555)" @DrmnSamoLiu : any chance of finding out the URL to get FW v1.0.14 directly from TPLink? |
Thanks Probeerka. Unfortunatly my Tapo was blocked during last firmware update. There are infrared led on and no sign of life. I was hoping to fix the issue with a downgrade but couldn't. I tried to put the firmware in to a SD card but no solve the problem. Do you know some procedure for unblock the device? |
Hello! Someone can send me the firmware for Tapo C200 v3 ? |
Can anyone help me find 1.1.9 firmware for tapo light L530. I upgraded all my lights to 1.3.0 and now they are not working in iobroker. |
If somebody else reads this discussion years later, but can't find the specific firmware version you are looking for. I have published a directory of all downloadable firmware, etc., over at https://github.com/tapo-firmware You should be able to find firmware for most TP-link products, but some might be missing. If you have trouble downloading specific files just send me a message. Firmware for hardware version C200v3 is likely encrypted and I have not gotten the downgrade procedure to work yet. |
I could not find any firmware matching you specific request. Maybe Tapo uses the same firmware for multiple models or they have removed older firmware? Please take a look at https://github.com/tapo-firmware/Directory/blob/main/all_keys.txt to find your best matching firmware and download from https://download.tplinkcloud.com/<your_firmware> |
Hello @frigorino |
Hi @khalilsouldi and @tapo-firmware, I have a C200v3 also. I managed to downgrade the firmware by first resetting the camera and then doing the downgrade process. I had some problems with setting up the camera again after the downgrade (couldn't find the wifi) but another reset solved it. Might be unrelated, but thought would be good to mention. |
Since the last firmware upgrade I have the same issue with the c200. Only ir lights are on. Cam don't respond for reset and is not accessible via wifi. I tried to downgrade with the SD card method but it does not work. |
Hello |
No not really. The support answered me to do a full reset by holding the reset button over 30 sec, still hoding it and removing the cam from the power supply, and still holding the reset button for another 30 seconds, then turn the cam back on, by still holding the reset button for more than 30 seconds. But that didnt worked either. I still have a valid warranty on it so i wait for a replacement. |
Think it is a hard brick with the firmware, have same issues with mine. |
The sd method wil not work on C200 in this case. The internal flash are broken/corrupted and then the recovery are broken too since the recovery sd flash are part of the firmware. The only access are to U-Boot rlxboot shell Have tried to boot it up with bootm command, with fails with "Firmware check failed!" The web tflash recovery will need a cable for cable network, wifi does not work. Are not sure how to set the U-Boot env to boot from the sdcard, it might be possible, but the reset and sd flash run from the firmware, it is also why it is broken as it is, somthing is very wrong in that update there corrupt damage data on the flash so U-Boot are not able to start the device up. But here is the console log. U-Boot 2014.01-v1.2 (Nov 11 2020 - 20:29:43) Board: IPCAM RTS3903 CPU: 500M :rx5281 prid=0xdc02 Autobooting in 1 seconds Firmware check failed! Running command httpd!--Debug by Mazexiong flash status is 0, 2 |
This worked for me. |
Could you please specify which firmware version you used? I formatted the sd according to the instructions, but two of the firmware versions didn't work. There were no problems with 210v2. |
Also i used a new SD Card for the C210v1 |
Hi @DaHubsi Maybe they added a no-rollback ability in their last upgrade ? Which would seems to say "We don't want you to access them anymore from outside tapo app" ? Thanks in advance |
Hi, I've just downgraded my C210s to reenable them in Home Assistant. I had a mix of v1s and v2s, all on a 1.3.11 firmware. The v1 devices downgraded cleanly to 1.3.7 build 230823, but did need a factory reset to get them back in HA. The v2 devices wouldn't downgrade to 1.3.7 directly. The LED would blink green a couple of times, then stay solid red. It would downgrade to 1.3.8 build 230913, and from that to 1.37 build 230823 though. The v2s didn't need a factory reset, they just reauthenticated. |
For anyone who's failing to downgrade, I'd encourage you to an adventure of simple hardware hacking: Here I described how I get console access on a C200 v1. Having console access means you can see the console messages to know exactly why your camera is not downgrading. Here's a great video I found that shows how to identify UART pads on C210 cam: Just keep in mind that the console logs may contain some sensitive data like MAC address, your Wi-Fi SSID and the "alias" you gave your cam in the app.... etc. So be careful to remove those information before you decide to share your console log here. |
Hi,
That worked for me and I downgraded to firmware 1.0.4. I took the last one. |
After downgrading several C100 and C200 I had the same connection problems. They lost connection randomly in time. |
I tested this morning after connection lost just to reload the integration. That worked and I had the connection again. |
Just in case someone gets the same issue: I've successfully downgraded several C105 cameras to firmware 1.3.7. However, I have had to reformat the microSD card and put the firmware file every time, otherwise the next camera would not initiate the firmware flashing. It appears that the camera marks something either on the filesystem (although I haven't noticed any new files after a brief check) or in the firmware file itself post update. |
Hi there, I think downgrade worked, but it was never able to boot again, it is maybe bricked. Before downgrading, I formatted my SD card based on DrmnSamoLiu's guide. As it does not boot, I tried to reflash with some other firmware versions and another SD card, but still having the same issue. I also tried resetting by pushing the reset button, but still the same. Does someone have a similar issue ? |
Do I have to reset camera to factory settings before starting the whole downgrade process? |
Hi, Facing the same issue on my side. I've tried multiple other firmware but no luck so far. Have you found a solution ? |
@sfritz67 @AntoineGauthier @fmarzocca |
@DrmnSamoLiu Any help would be truly appreciated. |
@sfritz67 & @AntoineGauthier |
Hello, |
I've managed to downgrade my EU C200 V3 to Prepare the sdcard
Downgrade the camera
Strange bugFunny thing is, I had to re-prepare the sdcard again when downgrading my other - exactly the same ! - cameras. If not, it would stay red instead of downgrading the camera. |
I've managed to downgrade my EU C200 V3 with latest firmware 1.3.15 to 1.3.5 |
@paulv888 I'm trying to do the same. Any tips? I thought I formatted my card correctly, but I'm not 100% sure. My camera is a C310 v2 |
Segui exatamente esses passos com minha C200 e deu tudo certo pra mim. |
Unfortunately it didn't work for me with my camera C210 V2.2 (EU). |
I have 2 C210 V2,0 with firmware version 1.3.11 Build 240427. I have tried the downgrade process repeatedly but the camera never gets beyond a solid red led and does not perform the auto-calibration. I get the Very frustrating and disappointing now that I bought them and cannot get them into HA. :( |
Hello, |
@m0n4 Did you ever find a solution? I've just ended up with a soft-bricked camera today as well |
I never found a solution. My Tapo_C210v2.2 came from Amazon, I sent it back for refund. |
I haven't found a solution either. |
This is from the creator (I think) of the integration. |
Hopefully smooth sailing in the future then, but I still have one camera that won't boot. I had another v2.2 in a box that's still on 1.3.7 from the factory. This is the URL it receives when it checks for updates: Unfortunately this build doesn't revive the other camera though. It installs, but still doesn't boot. This at least implies there are no separate v2.2 firmware builds. |
Not really an issue, moreover a query to know if possible. This seemed like a great place to ask since everyone here knows the intricacies of the C200v1.
I have 3 of these, made the mistake of updating two to firmware 1.1.15 from their original 1.0.14.... I say mistake because TPLink made the decision that many of the parts accessible via api (HomeAssistant) became paying.... shame, shame, shame!
I cannot AutoTrack any longer with the two updated, however the original on 1.0.14 still can (which is what I would like to keep). I learned that since 1.1.7 many features are no longer available for free.
An idea I had was to publish the firmware that I found (thanks to https://drmnsamoliu.github.io/firmware.html) on an internal webserver, rewrite DNS entries for download.tplinkcloud.com for it to ota upgrade - but I do not know the mechanics of where/how it reads what is the latest firmware... maybe someone here knows? Either way maybe there is another way to ota flash a bin (or at least the one found here)
Thanks in advance!
The text was updated successfully, but these errors were encountered: