V2 installation proposed changes

[gtxaspec]

current method:

1. Run compile script
2. script downloads firmware
3. extracts firmware
4. replace kernel
5. repack firmware
6. flash demo.bin
7. boot wz_mini

The downside to this, is the need to modify the onboard flash with a new kernel image

proposed method:

1. Flash special demo.bin containing kernel only (ONLY ONCE, EVER, PER v2 DEVICE), which will flash a new version of u-boot, able to load a kernel directly from the memory card.
2. download the stock firmware from the vendor
3. flash stock firmware demo.bin ( we need this step since step 1 erases the onboard system, root, and driver partitions )
4. boot wz_mini the same way you boot it on the t31 devices, it will load the kernel from memory card.

The downside to the proposed method, is the risk of potentially permanently bricking the camera if something goes wrong during the u-boot flash procedure. (unless you know how to remove the flash memory chip and manually flash it using a programmer). upgrading the bootloader is always a risky proposition.

The upside is, the camera's flash chip is never touched again, since everything is loaded from the memory card. no modified kernel resides on the camera, making it easier to uninstall wz_mini by simply removing or formatting the memory card.

I will do more testing to see if I can run into this situation.

[Bob-AOL]

Revert what?

[languy99]

@Bob-AOL I tried that firmware as well with the same results. Anyway we can revert this?

same thing for me, gets stuck in boot loop. you can hear the ir lens moving over and over.

[rocket59]

Is this still a valid install process? I'd like to do this without having to use linux.

[Bob-AOL]

Following the 'proposed' experimental directions should still be valid given a cooperative v.2 hardware version. As you've likely read, they don't all necessarily play nice and there are a couple of variants.

If you have a cooperative v.2 you should be fine. Otherwise, you should still have a working v.2 even if it doesn't support the later method of using wz_mini which can indeed be accomplished without using Linux.

[rocket59]

Thanks. What's the later method? The wiki install instructions tell us to compile the firmware image which of course requires linux to run.

[Bob-AOL]

This entire thread addresses the 'later' method consisting of the proposed changes explained in the third post as compared to the earlier 'compile' method.

I was assuming that was the one you were asking about still being 'valid' since it does not involve Linux, though it may or may not be the 'latest' variant of the method, hence my referring to it as the 'later' version discussed here.

I'm unaware of yet another 'later' version, so I guess we can just go with 'latest' for the one dicussed here.

My bad. LOL

[rocket59]

No problem, thanks again!

[Bob-AOL]

Good luck. If you're successful and intend to use the USB/POE/ETH functionality, the v.2s have no data capability on the micro USB connection as do the v.3s. The v.2 USB 2.0 slot has both. I used a micro USB to USB A adapter and the UCTRONICS POE adapter successfully with my particular effort.

[rocket59]

Sadly no joy. I managed to flash the uboot and 1002 bin files successfully. But the mini hacks setup is stuck in the dreaded reboot loop.

The camera will still boot up properly with no SD card fortunately

[Bob-AOL]

Bummer. I feel your pain. I eventually gave up after a couple of weeks trying to figure out why my first try went without a hitch on one v2 but two others simply would not recognize or accept the same identical process.

While my suspicion was different hardware in the working camera than the other two, I never received any actual explanation from anyone indicating why that would matter.

There are indeed at least two distinctly different hardware versions of the v2. Who knows what else may be involved as well. Most would not consider it a very worthwhile cause to explore..., obviously.

I simply reverted back to the Wyze RTSP firmware and eventually ended up selling all my v2s.

[rocket59]

yea, not the end of the world, as the camera still works. I have one more v2 to try it out on later and like you will replace them eventually with v3s. I already have a couple of them working great with mini hacks.

[Bob-AOL]

You do know there is also a v2 RTSP Wyze beta as well as the v3 version? That's what I meant by 'reverting back'. I found it to be pretty solid and certainly worthwhile if attempting to otherwise use wz_mini with the v2s just for the RTSP functionality.

[rocket59]

Yes, that was what I was using before. In any case getting new V3s does make sense with the better low light performance and weatherproofing. The only thing I dislike about them sometimes is the large FOV which isn't always a plus.

[Bob-AOL]

Changing to a different lens is pretty simple with the v3s. Lots of options available. A macro with a adjustable focus is even doable for stuff like aquariums, 3D printer monitoring and that type of thing..., even birdfeeders if well enough protected.

The IR performance is the main reason I still use the v3s. Hard to beat with cameras costing much, much more..., and I have a bunch that get their doors blown off every night by the v3s. LOL