-
Notifications
You must be signed in to change notification settings - Fork 1k
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
New Wyze V2 cannot load CFW #1667
Comments
Can confirm that this issue is also happening on my end. I have a Wyze cam V2 purchased from Amazon in December. I have the exact same issues as @pbruen described. Once I write the cfw-1.1.1bin file onto the micro sd card, the flashing process looks like it begins because the light turns from orange to blue, but then it goes back to orange for about 3-6 seconds then turns off, turns back on for another 3 seconds, makes a clicking noise and then turns back off. This repeats until I unplug the device from USB. Steps in order to replicate issue:
The Wyzecam V2 was never able to connect to a router I had setup using simple ssid and password. Also tried with no password. I retried all of the steps above using a different base firmware located from the manufacturer here for V2 -> https://wyzelabs.zendesk.com/hc/en-us/articles/360024852172-Release-Notes-Firmware I tried installing dafang hacks with base firmwares: Info about camera: Micro sd setups were tested on both macOS and Linux I look forward to any help on this since this is the only opensource firmware there is for these kinds of cameras. Thanks! |
Hi guys - the cfw-1.1.bin does work on the newest WyzeCam v2. Purchased one this month (early January 2021) and got it to work. Biggest issue I had was in the
|
If you experience step 9, this is normal. Unplug the camera, wipe the sdcard, then load the config files from your pc or raspi. One more thing to note (assuming you're connecting to homebridge) and after you can see the camera in the browser: be sure to set a static ip:
This last step is necessary to get snapshots into your app and for the rtsp stream to work for video feeds. |
No joy here either. Same as Ardlc0, just yellow light and clicks no matter what I do, different firmwares (including beta RTSP) including the modified wpa_supplicant. |
It's possible this is related to a hardware revision on newer V2s vs newer firmware. |
the 2018 cfw1.1.bin does work on a June 2020 or newer wyzecam v2 (FCC ID 2ANJHWYZEC02) more details in same reddit thread |
Tried it and still no joy.. click.. click.. click. I'll contact the person and see if they can suggest anything. |
I am having a same clicking problem with two V2s that were purchased recently. @rklassen , can you post the link to the Reddit thread about the fix? Thanks. |
I have precisely same issue. I tried the solution posted on Reddit: https://www.reddit.com/r/wyzecam/comments/jyc9jo/does_the_new_version_of_the_wyze_cam_v2_hardware/ But, it doesn't work for me. The author of that post told me that he is now having the same issue with a new camera. |
Currently I have 3x Wyzev2 2ANJHWYZEC2 which all work fine with cfw-1.1.bin. I purchased 4x Wyzev2 last week that were 2ANJHWYZEC02 and they all experienced the bootloop with cfw-1.1.bin. I found users on the Wyze Forums reporting a similar bootloop a few months back when attempting to use the latest RTSP firmware on newer purchased cameras. Subsequently an update to the RTSP firmware was released to fix the issue. At your own risk, here is an updated demo.bin that has been based on the latest RTSP firmware with SD card mounting fixes thanks to @mbevand So far I've flashed this on 2 of the new purchased cameras with 2ANJHWYZEC02 and have successfully booted into the latest |
I'm going to mark this as closed, though I have not personaly tested the fix (I ended up returning my cameras, and went with something that allows RTSP natively - eufy). Hopefully the updated firmware linked here solves this for everyone. |
Thanks so much. My primary reason to choose Wyze was prevent them from communicating with cloud servers outside of US.
I suppose that Eufy mods don't have that capability, do they as far as you know?
Badri
On February 1, 2021 at 11:23 AM, Patrick Bruen <notifications@github.com> wrote:
I'm going to mark this as closed, though I have not personaly tested the fix (I ended up returning my cameras, and went with something that allows RTSP natively - eufy)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thanks @McNutnut !!! The new cfw-1.2.bin saved my two new WCV2's! It works! |
@bshirgur - My experience with Eufy so far is that they survive reboots with no external access (some configs changes seem to need external access to take effect) - and RTSP works out of the box - so it is close enough to meet my needs and I haven't even looked into modding it. |
I have a Neos camera that I'm trying to flash unsuccessfully at the moment. I've just tried to follow the link to 1.2 but I'm getting an error, has this been removed now? 😩 |
Hello, thanks for these firmwares, i can run successfully dafang hack. Thanks for your help. |
Sorry for digging out an old thread here - I have 2 v2 that I am trying to "unbrick". They were on the latest firmware at some point, does that mean there is no way to downgrade now and use Dafang Hacks? I've been unable to flash using CFW 1.1 or 1.2 EDIT: Actually flashing with 1.1 finally worked (despite not having blue LED etc). Still trying to flash back to "stock" firmware somehow. |
Looks like WYZE V2 cameras that have had newer firmware loaded on them do not allow CFW to install properly. Doing so returns:
solid orange light for ~3s. a click, light blinks out briefly after another 3s, and repeat.
Loading an older official firmware prior to CFW does not improve things
If there is a method around this, I'd love to hear it, as these devices are worthless to me with firmware that requires external connectivity (all the official firmware). I've seen a few other people describe this in a few different places, but no one seems to respond and (at least in git) the issue gets closed as stale. :(
The text was updated successfully, but these errors were encountered: