search

HclX / WyzeHacks

Hacks I discovered allowing Wyze camera owners to do customizations
MIT License
786 stars 75 forks source link

remote_install.sh RuntimeError #132

Open yqin opened 2 years ago

yqin commented 2 years ago

Wyze Cam v2 with FW: 4.9.6.241 Failed with wyze_hacks_0_5_07 and wyze_hacks_0_5_08

Pushing firmware to this device? [y/N]:y INFO:root:Serving firmware file './firmware.bin' as 'http://192.168.0.1:11808/firmware.bin', md5=11567104604de4f4cc8f4633bc6c33f4 Traceback (most recent call last): File "./wyze_updater.py", line 362, in args.action(creds, args) File "./wyze_updater.py", line 260, in update_devices push_update(creds, dev_info['product_model'], mac, url, md5) File "./wyze_updater.py", line 163, in push_update return run_action(creds, model, "upgrade", mac, {"url": update_url, "md5": md5, "model": model}) File "./wyze_updater.py", line 160, in run_action custom_string="", action_params=params) File "./wyze_updater.py", line 140, in device_api raise RuntimeError('Request failed, error %s:%s' % (rsp['code'], rsp['msg'])) RuntimeError: Request failed, error 3005:UnauthorizedOperation

47bob47 commented 2 years ago

Hi j-justice - As you can probably tell from this thread the wyze hack has become a moving target with wyze continually trying to prevent new boot firmware from being installed onto the hardware they produce. As far as I can tell, cameras made after Sept 2020 or so are much harder to hack. I have a couple of v2 and v3 cameras sitting in front of me that just won't load the new firmware. Great cameras that are missing a lot of functionality. Much respect for the guys on this thread and the folks working on the github who are trying to get this to work.

virmaior commented 2 years ago

@i-justice

  1. v3 make no noise on install
  2. do you get a message indicating that a request was sent for the firmware from the camera (ip - - [date time] "GET /wuv2/upgrade/WLPP1/firmware/1.2.0.80a.bin HTTP/1.1" 200 - )?
  3. if you can telnet to the device (regardless of whether you can successfully login), then it did successfully install. Can you telnet them?
  4. the script will just keep waiting as if something is going to request download.
j-justice commented 2 years ago

@virmaior I tried using telnet to login and got the below message... https://i.imgur.com/36XyDDc.png

I also don't get any message after any camera install attempt https://i.imgur.com/5jqrHs9.png https://i.imgur.com/1wbeJcw.png

jk111 commented 2 years ago

@HclX here is the POST from app for v2 upgrade.. if you need to see specific values from it, let me know. Took anything out I thought might be sensitive. MAC address is in format 2CAA00112233

POST URL: https://api.wyzecam.com/app/v2/auto/run_action

{
    "access_token": "token-val",
    "app_name": "com.hualai",
    "app_ver": "com.hualai___2.23.21",
    "app_version": "2.23.21",
    "phone_id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa",
    "phone_system_type": "2",
    "sc": "32-character-value",
    "sv": "32-character-value",
    "ts": 13-character-value,
    "provider_key": "WYZEC1-JZ",
    "action_key": "upgrade",
    "instance_id": "CAM-MAC",
    "custom_string": "CAM-MAC",
    "action_params": {
        "url": "https:\/\/d1fk93tz4plczb.cloudfront.net\/UpgradeKit\/1625707411\/Upgrade_4.9.7.798_07071601.tar",
        "md5": "6bb9aceedc951c9f2a4190da8af57385",
        "model": "WYZEC1-JZ",
        "firmware_ver": "4.9.7.798"
    }
}
HclX commented 2 years ago

I got the same traffic on my capture. I think there is something in the new firmware preventing it from working. We will have to wait for wyze to release a new firmware to see what the app sends...

On Mon, Aug 9, 2021, 13:57 jk111 @.***> wrote:

@HclX https://github.com/HclX here is the POST from app for v2 upgrade.. if you need to see specific values from it, let me know. Took anything out I thought might be sensitive. MAC address is in format 2CAA00112233

{ "access_token": "token-val", "app_name": "com.hualai", "app_ver": "com.hualai___2.23.21", "app_version": "2.23.21", "phone_id": "aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa", "phone_system_type": "2", "sc": "32-character-value", "sv": "32-character-value", "ts": 13-character-value, "provider_key": "WYZEC1-JZ", "action_key": "upgrade", "instance_id": "CAM-MAC", "custom_string": "CAM-MAC", "action_params": { "url": " https://d1fk93tz4plczb.cloudfront.net/UpgradeKit/1625707411/Upgrade_4.9.7.798_07071601.tar ", "md5": "6bb9aceedc951c9f2a4190da8af57385", "model": "WYZEC1-JZ", "firmware_ver": "4.9.7.798" } }

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-895540931, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNWDZYRYKH2QJT6ET4RNTT4A6NFANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

mpatton125 commented 2 years ago

I had to rollback to a prior software version, and then the spoofing operation worked.

HclX commented 2 years ago

Exactly. There must be something on the latest firmware side restricting this behavior.

On Mon, Aug 9, 2021, 17:26 Michael Patton @.***> wrote:

I had to rollback to a prior software version, and then the spoofing operation worked.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-895639490, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNWDZ23RP2RVEFSFLMXZLT4BW4VANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

47bob47 commented 2 years ago

So, which version did you roll back to?

HclX commented 2 years ago

Any version before 798 should work.

On Mon, Aug 9, 2021, 17:35 47bob47 @.***> wrote:

So, which version did you roll back to?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-895642380, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNWD5YOX2WFPMZ26DGL33T4BX3XANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

47bob47 commented 2 years ago

This is working well on a Wyze Pan Cam I just purchased using the wyze_update script. Question: In the nfs directory it creates a time_lapse directory. I don't see anything in the wyzehack documentation regarding time lapse - is that an unimplemented feature for the future? Getting a snapshot every few minutes would be helpful and probably easier than the way I am planning on implementing it by grabbing a frame from a recent video.

jdkadel commented 2 years ago

Create a basic Linux server and install dnsmasq. The server could be a Raspberry Pi, Hyper-V, dual boot, what every you have. I installed dnsmasq using the info at Debianhttps://wiki.debian.org/dnsmasq on the Raspberry Pi I am using to update the cameras with. Then added "192.168.1.xxx s3-us-west-2.amazonaws.com" (xxx address of the Pi) to the /etc/hosts file. This made the Pi a DNS server.

To make the camera's see the new DNS server I changed my DHCP settings on my IOT router to the Pi's address. Normal DNS calls work but when a camera asked for s3-us-west-2.amazonaws.com it's redirected back to the Pi.

From: endertable @.> Sent: Thursday, August 12, 2021 9:18 PM To: HclX/WyzeHacks @.> Cc: jdkadel @.>; Mention @.> Subject: Re: [HclX/WyzeHacks] remote_install.sh RuntimeError (#132)

  1. it won't ever work with ssh because there's no sshd on the device. Instead, you have to use telnet or netcat. on osx, this looks like: nc 192.168.3.101 23 (substitute ip as appropriate)
  2. Can you confirm that the camera is also operating from your spoofed DNS server and not just a change to the DNS on your computer (e.g. editing /etc/hosts on a desktop or laptop will only change the DNS for that local computer)?
  3. The camera should reboot either when it successfully gets the wyze_updater delivered firmware or after a few minutes automatically. If neither is happening...

Thanks @virmaiorhttps://github.com/virmaior!, I verified everything again and now it's working. I didn't have the dnsmasq working correctly. Thanks!!

@jdkadelhttps://github.com/jdkadel Hi, I don't have a local DNS server and prefer not to, Can you tell me how to get a quick dnsmasq up and running specifically for this purpose.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/HclX/WyzeHacks/issues/132#issuecomment-898112251, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4J2QALXKO3BOBYFS7YU33T4R6GRANCNFSM5AID5EYA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

HclX commented 2 years ago

Just reversed the 798 firmware and it seems they now enforces "https" for update:

Aug 13 23:42:24 test_UP: [UPGRADE2 TESTUP] url:http://d1fk93tz4plczb.cloudfront.net:18080/UpgradeKit/firmware.bin md5:04984f084a54d18e85702162f07a028a 
Aug 13 23:42:24 test_UP: Ready to download file[downloadfiles.c:41]Download file URL must be https http://d1fk93tz4plczb.cloudfront.net:18080/UpgradeKit/firmware.bin
HclX commented 2 years ago

btw, they also removed telnetd from 798 firmware....

mpatton125 commented 2 years ago

I guess that pretty much confirms stuck on 4.9.6.241... Unless someone can find a way around the TLS requirements on the download?

jk111 commented 2 years ago

That's what I was afraid of... I tried a few different methods to see if it would fall back to http but it wouldn't. It does check certificate validity as well, so spinning up a simple web server with a self signed cert does not work.

C1ARKGABLE commented 2 years ago

If you don’t have telnetd, you could always open up your WyzeCam to access the debug port via a UART to USB cable and the screen program on a separate computer. Once you log in, you’ll have access to terminal (not unlike the one you get with telnet) and can use the installer/telnet_install.sh script to install WyzeHacks from an SD card.

dudududodododedede commented 2 years ago

Does this mean WyzeHacks is essentially dead (unless we want to take apart our camera and solder)? Does the same limitation apply to all firmware versions or can we still load WyzeHacks onto older firmwares?

HclX commented 2 years ago

There is a big weakness or attack surface for the wyzecam which is the SD card recovery: so what we lose for now is the ability to install custom software using OTA update. But we can still flash firmware with SD card recovery. It's not as easy/convinent as OTA approaches, but still possible.

It can be problematic for those who mount the camera to hard to reach locations though: if wyze send another breaking update, you will have to pull your ladder out to fix it.

On Sun, Aug 15, 2021, 21:20 dudududodododedede @.***> wrote:

Does this mean WyzeHacks is essentially dead (unless we want to take apart our camera and solder)? Does the same limitation apply to all firmware versions or can we still load WyzeHacks onto older firmwares?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-899202449, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNWD52P6AFK4UFRJHBSDTT5CGXZANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

endertable commented 2 years ago

Cool @HclX, I was under the impression that they started encrypting SD card firmware updates and that OTA was the only way we could do it. SD card is still a good option then?

Semag commented 2 years ago

Also @HclX - i think your original blog post about renaming the custom firmware as "demo.bin" (i think that's how we used to do it) was patched. I honestly haven't done an SD Card recovery in a long time. Also - can you still compile wyze hacks into the new firmware to work with an SD card update?

famewolf commented 2 years ago

Any version before 798 should work. … On Mon, Aug 9, 2021, 17:35 47bob47 @.***> wrote: So, which version did you roll back to? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#132 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNWD5YOX2WFPMZ26DGL33T4BX3XANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

SO what is the most direct rollback procedure? As someone else mentioned am I going to have to break out the ladder and put sdcard's into the cam's with the previous firmware and where can that version be found? I am using adguard so I'm pretty sure I can assign that amazon domain to point to my local pi which is where adguard runs anyway. It's the designated dns server for my router.

mpatton125 commented 2 years ago

Any version before 798 should work. SO what is the most direct rollback procedure?

Yes I had to get out the ladder and rollback via sdcard.

Procedure is here: https://support.wyze.com/hc/en-us/articles/360041676711-How-do-I-revert-my-webcam-back-to-a-Wyze-Cam-

It says it's for reverting from webcam to Wyze cam, but it's essentially just the manual install process.

Older firmware versions found here: https://support.wyze.com/hc/en-us/articles/360024852172-Release-Notes-Firmware

Direct link to V2 4.9.6.241 firmware: https://download.wyzecam.com/firmware/v2/demo_4.9.6.241.bin.zip

Edit: might be able to roll back via the app. Settings -> Device info -> Firmware upgrade -> Have problem? -> Choose Version

MomosX commented 2 years ago

I received 4 new Wyze V3 from Amazon, firmware 4.36.25. While i was able to install the hack on my other V3 with the same firmware, these do not work at all. Getting the 3005 error.

I read all the comments about DNS spoofing but to be honest this is above my paygrade :(

Is it possible to go the SD card route to install the hack with no need of DNS spoofing and such ?

If yes, could someone explain how to do that please ?

Thank you

famewolf commented 2 years ago

@mpatton125 Thank you for instructions!

jdm0 commented 2 years ago

Gentlemen: I'm desperate to get something like WyzeHacks working on the Eufy Indoor Cam 2K (model T8400), but I lack the sharpened Linux hacking skillz you all seem to have. I can tell you that the Eufy cam uses the exact-same SoC as the Wyze V3 — namely, the Ingenic T31 — and I've spent countless hours running operational experiments and examining log files from the cams. If you know of anyone who's working on a project like this — which I suppose one might call "EufyHacks" — or if you would be interested in working on it yourself, PLEASE message me!! ~ Apologies for the tangential comment. Thanks.

HclX commented 2 years ago

As we all know that wyzehacks is pretty much blocked by latest wyze server and client sides fixes. I'm thinking of alternatives to get hack installed on the latest version firmware. The current thinking is to use their sdcard recovery method and I have a prototype working well. However that means you will need physical access to your camera to install the hack for the first time. Luckily once installed, you should be able to update wyzehack remotely, until they decided to update the rootfs during OTA, hopefully that won't happen too often.

Anyway, the installation process will be a little bit more complicated comparing to previous method, especially for v3 camera since they also have signature check for sdcard recovery. Stay tuned...

On Thu, Aug 19, 2021, 12:53 famewolf @.***> wrote:

@mpatton125 https://github.com/mpatton125 Thank you for instructions!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-902197906, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZNWD4LWRQMUPYDWVYJEQTT5VOMFANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

nowherenone commented 2 years ago

I was able to install it by downgrading my v3 camera to 4.36.0.228 and following these steps: https://github.com/HclX/WyzeHacks/issues/132#issuecomment-881862247 But at first few tries nothing actually happened - camera turned on a purple light and stuck. I tried to turn it on and off and finally maybe from the 5-th try it actually got rebooted and I've got telnet access. Thanks to everyone in this thread!

47bob47 commented 2 years ago

That is great news @nowherenone
I tried it a few times and couldn't get it to work and gave up on it but you encouraged me to keep on trying. Will do so in the next few days.

I don't know if anybody from WYZE reads this github topic but I really don't think that this hack and WYZE's CAM-PLUS product are competing with one another. The CAM-PLUS is great at streaming real time and especially about instant alerts of activity and viewing short clips on a small mobile device but it is absolutely horrible at going back in history and viewing or downloading timelines. Every one of my cameras with this "hack" also has a CAM-PLUS subscription which is totally worth it at $1.25 a month. The "hack" and the CAM-PLUS subscription work very well together.

Vendo232 commented 2 years ago

I was able to install it by downgrading my v3 camera to 4.36.0.228 and following these steps: #132 (comment) But at first few tries nothing actually happened - camera turned on a purple light and stuck. I tried to turn it on and off and finally maybe from the 5-th try it actually got rebooted and I've got telnet access. Thanks to everyone in this thread!

this is great news, could you please tell me more about telnet? Can I use Putty app on Windows ? Once I connect is there a password? what would be the next step? thank you kindly

I was able to get to this point the dnsmaq is running from 192.168.1.245 PC where the script is running from is 192.168.1.76 V3 is 192.168.1.174

V3 while in this DNSMASQ loop is blinking orange ( red + blue ) image

Semag commented 2 years ago

@Vendo232 that camera model isn’t one that I recognize (CAKP2JFUS) - I believe that’s why it’s skipping.

To add myself to the success on this thread, I got a new ?3 from Amazon yesterday and downgraded using the SD card method to 4.36.2.5. I then took my little rg router running a version of openers, and it is already running dnsmasq so I added the /etc/hosts entry and did a “killall -HUP dnsmasq”. Seems to work like a charm.

Vendo232 commented 2 years ago

I was able to install Wyzehack using the DNS spoofing then I was able to login via Telnet using root/WYom2020 credentials Than I was apparantly able to install the Stream Hack via Telnet Command

All Works!!! but remember on Windows to open "RUN" program and enter "vlc http://192.168.1.174:12345 --demux h264" to check your stream!!!

image image

Semag commented 2 years ago

@Vendo232 - what version is your camera running? I have 4.36.2.5 on my V3 camera and installed the FiveLeaves Streaming mod, but my camera started rebooting every 20 seconds like here: https://github.com/FiveLeavesLeft/WyzeCameraLiveStream/issues/12

I was able to grab the uninstall script and run it on a quick telnet session - but i'll have to dig into why it was rebooting.

Vendo232 commented 2 years ago

@Vendo232 - what version is your camera running? I have 4.36.2.5 on my V3 camera and installed the FiveLeaves Streaming mod, but my camera started rebooting every 20 seconds like here: FiveLeavesLeft/WyzeCameraLiveStream#12

I was able to grab the uninstall script and run it on a quick telnet session - but i'll have to dig into why it was rebooting.

Downgraded to 4.36.0.228

nadigo commented 2 years ago

same with me - rebooting every 1/3 a min or so. Had to revert in between reboots.

Any advice ?

On Tue, Sep 7, 2021 at 12:21 AM Semag @.***> wrote:

@Vendo232 https://github.com/Vendo232 - what version is your camera running? I have 4.36.2.5 on my V3 camera and installed the FiveLeaves Streaming mod, but my camera started rebooting every 20 seconds like here: FiveLeavesLeft/WyzeCameraLiveStream#12 https://github.com/FiveLeavesLeft/WyzeCameraLiveStream/issues/12

I was able to grab the uninstall script and run it on a quick telnet session - but i'll have to dig into why it was rebooting.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-913979237, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABOQZBNJV5WT24PIR4YBZ33UAWHN5ANCNFSM5AID5EYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

47bob47 commented 2 years ago

Anybody have any clear instructions on how to set this up using an SD card on a CamPan running version 4.10.6.199
The web page with instructions is pretty light. Hold setup button? Unplug? Do we need to rename the FIRMWARExxxx.bin file to demo.bin? Tried various ways but never getting the "installation finished, remove sd card" message. Holding down the setup button with the sd card inserted just eventually gets the "ready to connect" message.

Semag commented 2 years ago

@47bob47 - Not sure if you just mean a basic firmware flash or the hack install? If you're talking about the hack install, it's no longer possible to do it (as far as i know) without spoofing DNS and a linux server with python installed.

47bob47 commented 2 years ago

I know the over the air update is pretty much dead so I'm trying to install the hack by plugging in an SD card which may still be a work in progress according to this previous post? https://github.com/HclX/WyzeHacks/issues/132#issuecomment-903036478

Current instructions for SD Card install are most of the way down the page here: https://github.com/HclX/WyzeHacks

Semag commented 2 years ago

@47bob47 - you need to downgrade your PAN to 4.10.6.156 first based on the notes on HclX's main page

SD card install only works when your camera is running firmware before version 4.9.6.156 (WyzeCamV2) or 4.10.6.156 (WyzeCam Pan). You will need an SD card for this purpose. Size of the SD card doesn't matter.

After that, you can download the wyzehacks firmware and install it via the sdcard install method on the main page.

Here's the general method for firmware via SD Card: https://support.wyze.com/hc/en-us/articles/360031490871-How-to-flash-your-Wyze-Cam-firmware-manually

47bob47 commented 2 years ago

Downgraded to 4.10.5.111 and still no luck. Tried with just unzipping everything onto sd card. Tried deleting everything off sd card and renaming FIRMWARE_xxx.bin file to demo.bin. Tried with pushing setup button and without pushing setup button. Nothing on the sd card install is working for me so unless some clearer and more specific instructions appear on the main page I'll assume for right now that the sd card install is also broken.

Too bad because this modification to use a remote file system works well on my other cameras.

47bob47 commented 2 years ago

Just for reference here is my install.log:

FiveLeavesLeft commented 2 years ago

Edit: might be able to roll back via the app. Settings -> Device info -> Firmware upgrade -> Have problem? -> Choose Version

@mpatton125 , I don't see this in the current or beta android app. Where did you see this in? Thanks!

Semag commented 2 years ago

@FiveLeavesLeft it's not there as far as i can tell - i had to end up with the DNS spoofing.

To clarify, for roll back i did it via SD card (and hold the reset button).

mpatton125 commented 2 years ago

Edit: might be able to roll back via the app. Settings -> Device info -> Firmware upgrade -> Have problem? -> Choose Version

@mpatton125 , I don't see this in the current or beta android app. Where did you see this in? Thanks!

Yeah it looks like they have removed it in current versions of the app. It might still be possible with older app versions.

mpatton125 commented 2 years ago

I went back to v2.19.15 of the app and the "Have problem?" link is there - no idea if it will still work. My camera is on 4.9.6.241 and the "Have problem?" link says it can revert my firmware to: 4.9.6.199 4.9.6.193 4.9.6.156 4.9.5.39

FiveLeavesLeft commented 2 years ago

@mpatton125 , thanks for that info. It's a shame that wyze doesn't embrace developers, we could do some cool stuff.

famewolf commented 2 years ago

I went back to v2.19.15 of the app and the "Have problem?" link is there - no idea if it will still work. My camera is on 4.9.6.241 and the "Have problem?" link says it can revert my firmware to: 4.9.6.199 4.9.6.193 4.9.6.156 4.9.5.39

When you used this older software were you actually able to connect and view your cams? I'm on the newer 798 firmware and I'm not sure if I'm just having connection issues or if the older client won't connect to the newer firmware.

satmandu commented 2 years ago

I'm on 4.36.14.

On Mon, Sep 27, 2021, 5:35 PM famewolf @.***> wrote:

I went back to v2.19.15 of the app and the "Have problem?" link is there - no idea if it will still work. My camera is on 4.9.6.241 and the "Have problem?" link says it can revert my firmware to: 4.9.6.199 4.9.6.193 4.9.6.156 4.9.5.39

When you used this older software were you actually able to connect and view your cams? I'm on the newer 798 firmware and I'm not sure if I'm just having connection issues or if the older client won't connect to the newer firmware.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-928306223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAILX7N3EANEYBPSLFBJAKLUEDPRPANCNFSM5AID5EYA .

satmandu commented 2 years ago

Correction : 4.36.1.4

On Mon, Sep 27, 2021, 5:53 PM Satadru Pramanik @.***> wrote:

I'm on 4.36.14.

On Mon, Sep 27, 2021, 5:35 PM famewolf @.***> wrote:

I went back to v2.19.15 of the app and the "Have problem?" link is there

  • no idea if it will still work. My camera is on 4.9.6.241 and the "Have problem?" link says it can revert my firmware to: 4.9.6.199 4.9.6.193 4.9.6.156 4.9.5.39

When you used this older software were you actually able to connect and view your cams? I'm on the newer 798 firmware and I'm not sure if I'm just having connection issues or if the older client won't connect to the newer firmware.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/HclX/WyzeHacks/issues/132#issuecomment-928306223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAILX7N3EANEYBPSLFBJAKLUEDPRPANCNFSM5AID5EYA .

mpatton125 commented 2 years ago

When you used this older software were you actually able to connect and view your cams? I'm on the newer 798 firmware and I'm not sure if I'm just having connection issues or if the older client won't connect to the newer firmware.

Yeah I could connect but my cams weren't on newer firmware - 4.9.6.241 as noted previously.

famewolf commented 2 years ago

python3 ./wyze_updater.py --token ~/.wyze_token --debug update -m WYZEC1-JZ -m WYZECP1_JEF -m WYZE_CAKP2JFUS -m WYZEDB3 -f ./firmware.bin -p 80

Where is "firmware.bin" coming from? The downloaded .241 firmware renamed or the FIRMWARE_660R.bin that comes with wyze hacks renamed? I've already done the dns spoof and the url = edit.

Ok so maybe I'm misunderstanding and this hack allows OTA if you are on a compatible firmware already? Is there anyway to downgrade to the .241 firmware using this method?